Google SEO APIs
AgriciDaniel/claude-seo
Pulls real Google data for SEO work: Search Console, PageSpeed Insights, CrUX field data, the Indexing API and GA4 organic traffic, through /seo google commands.
When the user wants to fix indexing issues from Search Console, use noindex, or implement Google Indexing API.
Install Indexing
$ npx skills add kostja94/marketing-skills --skill indexing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kostja94/marketing-skills indexing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo/technical/indexing .claude/skills/indexing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "indexing" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/technical/indexing into .claude/skills/indexing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indexing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/kostja94/marketing-skills/tree/main/skills/seo/technical/indexingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add kostja94/marketing-skills --skill indexing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kostja94/marketing-skills indexing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/seo/technical/indexing .agents/skills/indexing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "indexing" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/technical/indexing into .agents/skills/indexing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indexing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kostja94/marketing-skills --skill indexing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kostja94/marketing-skills indexing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/seo/technical/indexing .cursor/skills/indexing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "indexing" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/technical/indexing into .cursor/skills/indexing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indexing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/kostja94/marketing-skills.git --path skills/seo/technical/indexing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add kostja94/marketing-skills --skill indexing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kostja94/marketing-skills indexing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/seo/technical/indexing .gemini/skills/indexing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "indexing" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/technical/indexing into .gemini/skills/indexing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indexing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install kostja94/marketing-skills indexingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add kostja94/marketing-skills --skill indexing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/seo/technical/indexing .github/skills/indexing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "indexing" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/technical/indexing into .github/skills/indexing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indexing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kostja94/marketing-skills --skill indexing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kostja94/marketing-skills indexing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/seo/technical/indexing .opencode/skills/indexing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "indexing" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/technical/indexing into .opencode/skills/indexing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indexing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
indexing- GitHub stars
- 1k
- Token cost
- ~2.1k tokens
- SKILL.md length
- 1,009 words
- Files
- 1
- Skills in repo
- 102
- Repo updated
- First seen
- Licence
- MIT
At a glance
When the user wants to fix indexing issues from Search Console, use noindex, or implement Google Indexing API.
- Works in 4 steps: Remove deleted URLs from XML sitemap;… → Update internal links to point directly… → For 301 redirects, ensure the target URL… → …
- Wants to fix indexing issues from Search Console
- SKILL.md covers Scope (Technical SEO), Initial Assessment, Crawled - Currently Not Indexed and Other Issue Types (from GSC…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Indexing is an agent skill from kostja94/marketing-skills. When the user wants to fix indexing issues from Search Console, use noindex, or implement Google Indexing API. Also use when the user mentions "fix indexing," "not indexed," "Crawled - currently not indexed," "discovered - currently not indexed," "index coverage," "noindex," "noindex tag," "pages not indexed," "why not indexed," "request indexing," or "Google Indexing API." For sitemap, use xml-sitemap.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Technical SEO. It works with Google Search Console. The repository describes itself as: Agent Skills for Marketing — SEO, Social, Influencer & More. 160+ open-source skills for SEO, content, 40+ page types, paid ads, channels, and strategies. Add project context… The licence is MIT.
When your agent uses it
- Wants to fix indexing issues from Search Console
- Implement Google Indexing API
- The user mentions fix indexing
- Crawled - currently not indexed
Example prompts
- “fix indexing,”
- “not indexed,”
- “Crawled - currently not indexed,”
- “/indexing”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Remove deleted URLs from XML sitemap; update and resubmit
- Update internal links to point directly to the final URL (avoid relying on redirects)
- For 301 redirects, ensure the target URL is in the sitemap
- In GSC, use URL Inspection to verify important pages; use Removals tool for temporary quick-hide (not permanent — use proper HTTP status…
What it can do on your machine
Read from SKILL.md and the folder at commit 8dd89c5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
support.google.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Indexing loads about 2.1k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 1,009 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from kostja94/marketing-skills at commit 8dd89c5, republished under its MIT licence (© kostja94). 1,009 words, ~2,098 tokens.
Download SKILL.mdSave it as
.claude/skills/indexing/SKILL.md (or your agent's skills folder).- name
- indexing
- description
- When the user wants to fix indexing issues from Search Console, use noindex, or implement Google Indexing API. Also use when the user mentions "fix indexing," "not indexed," "Crawled - currently not indexed," "discovered - currently not indexed," "index coverage," "noindex," "noindex tag," "pages not indexed," "why not indexed," "request indexing," or "Google Indexing API." For sitemap, use xml-sitemap.
- metadata.version
- 1.0.1
SEO Technical: Indexing
Guides indexing troubleshooting and fix actions. For how to find and diagnose issues in GSC, see google-search-console.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Scope (Technical SEO)
- Fix actions: noindex, canonical, content quality, URL Inspection; verify robots.txt does not block (see robots-txt)
- Noindex: Page-level index control; which pages to exclude and how. Complements robots-txt (path-level crawl control) and google-search-console (Coverage diagnosis)
Initial Assessment
Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
Identify issue from GSC (see google-search-console for Coverage report, issue types, diagnosis workflow). Then apply fix below.
Crawled - Currently Not Indexed
| Cause | Action |
|---|---|
| Low quality, duplicate, off-topic | Improve content, fix duplicates, set correct canonical |
| Static assets (CSS/JS) | See below |
| Feed, share URLs with params | Usually OK to ignore; or noindex, canonical to main URL |
| Important content pages | Use URL Inspection, verify canonical/internal links/sitemap, Request indexing |
Static Assets (Next.js / Vercel)
Vercel adds unique dpl= params to static assets per deploy, creating many "Crawled - currently not indexed" URLs.
| Do | Don't |
|---|---|
Keep robots.txt allowing /_next/ | Do not block /_next/ (breaks CSS/JS loading). See robots-txt |
| Accept static assets in GSC as expected | Do not block /_next/static/css/ or ?dpl= |
| Use X-Robots-Tag for static assets | CSS/JS should not be indexed; no SEO impact |
Static assets in "Crawled - currently not indexed" is normal and expected.
Other Issue Types (from GSC Coverage)
| Issue | Fix |
|---|---|
| Excluded by «noindex» tag | Remove noindex if accidental; keep if intentional |
| Blocked by robots.txt | See robots-txt; remove Disallow for important paths |
| Redirect / 404 | Fix URL or add redirect |
| Duplicate / Canonical | Set correct canonical; usually OK |
| Soft-404 | Page returns 200 but content says "not found" or empty—Google may treat as 404. Fix: return 404 status for truly missing pages; or add real content for 200 pages |
Soft-404
A soft-404 occurs when a page returns HTTP 200 but the content indicates the page doesn't exist (e.g. "Page not found" message, empty state). Google may treat it as 404 and exclude from index.
| Fix | When |
|---|---|
| Return 404 | Page truly doesn't exist; use proper 404 status |
| Add content | Page is intentional (e.g. empty search results); ensure substantive content or use noindex |
| Redirect | If URL moved, use 301 to correct destination |
Noindex Usage
- How:
metadata.robots = { index: false }or<meta name="robots" content="noindex">or X-Robots-Tag - Rationale: Not all site content should be indexed; noindex is a valid choice for many pages
- Caution: Avoid noindex on important content pages
- With robots.txt: robots.txt = path-level crawl control; noindex = page-level index control. Do not block noindex pages in robots.txt—crawlers must access the page to read the directive. Use both: robots for /admin/, /api/; noindex for /login/, /thank-you/, etc. See robots-txt for when to use which.
- nofollow ≠ noindex: nofollow controls link equity only; it does not prevent indexing. To exclude from search, use noindex. See page-metadata for meta robots implementation.
Page Types That Typically Need Noindex
| Category | Page Types | Typical Meta | Reason |
|---|---|---|---|
| Auth & Account | Login, Signup, Password reset, Account dashboard | Login: noindex,nofollow; Signup: noindex,follow | No search value; login indexed = security risk; signup follow allows crawl of Privacy/Terms links |
| Admin & Private | Admin, Staging, Test pages, Internal tools | noindex,nofollow | Not for public; avoid discovery |
| Conversion Endpoints | Thank-you, Confirmation, Checkout success, Download gate | noindex,follow | Post-conversion; no SERP value; allow link equity |
| System & Utility | 404, Internal search results, Faceted/filter URLs | noindex,follow or noindex,nofollow | Thin/duplicate; 404 = error state |
| Legal | Privacy, Terms, Cookie Policy (optional) | Often noindex,follow | Low-value indexed; reduces clutter |
| Duplicate & Thin | Printer-friendly, Parameter URLs, Near-duplicate | noindex,follow or canonical | Duplicate content; canonical preferred when possible |
| Low-Value | Media kit, Feedback board (external), Thin press | noindex or index for brand queries | Case-by-case |
noindex,follow vs noindex,nofollow: Use noindex,follow for most cases—excludes from SERP but allows link equity. Use noindex,nofollow only for login (security), staging, or temporary test pages.
Show full SKILL.md (338 more words)Show less
Page Removal Decision Framework
When intentionally removing a page from the web, choose the method based on whether a relevant alternative exists and whether the page should remain accessible:
| Scenario | Method | Rationale |
|---|---|---|
| Has a closely related replacement page | 301 redirect | Preserves accumulated link signals and user flow |
| Content merged into a new page | 301 redirect | Direct old URL to the new canonical location |
| Permanently deleted, no alternative | 410 Gone | Explicitly signals permanent removal to search engines |
| Deleted, uncertain if permanent | 404 Not Found | Safe default; can reinstate later if needed |
| Still accessible but should not be indexed | noindex | Page remains available to users; excluded from SERP |
Before removing: Check the URL's search traffic, backlinks, internal links, and conversion value. If the page has value, consider updating or merging rather than removing.
Common mistakes:
- 404-ing pages that have relevant alternatives (wastes accumulated signals)
- Redirecting all deleted pages to the homepage (breaks user intent)
- Creating redirect chains (A → B → C) instead of direct redirects
- Removing pages without cleaning up internal links pointing to them
- Using
robots.txtto block noindex pages (crawler must access the page to read the noindex directive)
Post-removal cleanup:
- Remove deleted URLs from XML sitemap; update and resubmit
- Update internal links to point directly to the final URL (avoid relying on redirects)
- For 301 redirects, ensure the target URL is in the sitemap
- In GSC, use URL Inspection to verify important pages; use Removals tool for temporary quick-hide (not permanent — use proper HTTP status or noindex)
Google Indexing API
| Type | Typical use |
|---|---|
| JobPosting | Job boards |
| BroadcastEvent | Live platforms |
Requirements: Enable Indexing API, create service account, add owner in Search Console, request quota (default 200 URLs/day).
Output Format
- Action items: Prioritized fixes
- References: Page indexing report
Related Skills
- google-search-console: Find and diagnose indexing issues in GSC
- robots-txt: Path-level crawl control; when to use robots.txt vs noindex; do not block /_next/ or noindex pages
- page-metadata: Meta robots implementation; noindex vs nofollow
- xml-sitemap: Submit and maintain sitemap
- indexnow: Faster indexing for Bing
- canonical-tag: Resolve duplicate content
© kostja94, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/seo/technical/indexing of kostja94/marketing-skills.
Open the folder on GitHubat commit 8dd89c5
Compare with similar skills
Indexing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Indexing this skillkostja94/marketing-skills | 1k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Google SEO APIsAgriciDaniel/claude-seo | 19k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| SEO Coachakseolabs-seo/seo-coach | 146 | — | ~2.8k | Automated safety check: Pass | None | |
| SEO Setupalisamadiii/Portfolio | 180 | — | ~1.7k | Automated safety check: Pass | None | |
| Google Search SEO Guidelittleben/awesomeAgentskills | 188 | 2 repos | ~4.2k | Automated safety check: Pass | MIT | |
| SEO Googleseranking/seo-skills | 160 | — | ~4.8k | Automated safety check: Pass | MIT |
Similar skills
SEO Coach
akseolabs-seo/seo-coach
Beginner-first SEO coaching for people who want to learn by doing one safe, verifiable step at a time.
SEO Setup
alisamadiii/Portfolio
Full SEO/metadata setup and audit for client websites (Astro, Next.js, any static site).
Google Search SEO Guide
littleben/awesomeAgentskills
Answers Google Search optimization questions from reference files covering crawling, indexing, structured data, Search Console and site visibility, drawn from Google's documentation.
SEO Google
seranking/seo-skills
Direct access to Google's own SEO data via Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, GA4 organic…
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
More from kostja94/marketing-skills
All 102 skills in this repoGrokipedia Recommendations
kostja94/marketing-skills
When the user wants to add recommendations, links, or content to Grokipedia.
AI Traffic Tracking
kostja94/marketing-skills
When the user wants to track AI search traffic in GA4 or GSC.
Analytics Tracking
kostja94/marketing-skills
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions).
Brand Visual Generator
kostja94/marketing-skills
When the user wants to define, audit, or apply visual identity (typography, colors, spacing, design tokens, frontend aesthetics).
Canonical Tag
kostja94/marketing-skills
When the user wants to configure canonical URLs, fix duplicate content, or consolidate URL signals.
Content Strategy
kostja94/marketing-skills
When the user wants to plan content for SEO, create content calendar, or build topic clusters.
Related
Works with
Categories
Questions about Indexing
What does Indexing do?
When the user wants to fix indexing issues from Search Console, use noindex, or implement Google Indexing API. Indexing is an agent skill from kostja94/marketing-skills. When the user wants to fix indexing issues from Search Console, use noindex, or implement Google Indexing API.
When should I use Indexing?
Indexing fits situations like: wants to fix indexing issues from Search Console; implement Google Indexing API; the user mentions fix indexing; crawled - currently not indexed.
How do I install Indexing in Claude Code?
Run `npx skills add kostja94/marketing-skills --skill indexing -a claude-code`. Or copy the skill folder (skills/seo/technical/indexing in kostja94/marketing-skills) into .claude/skills/indexing in your project. Claude Code loads it when a task matches its description.
How do I install Indexing in Codex?
Run `npx skills add kostja94/marketing-skills --skill indexing -a codex`. Or copy the skill folder (skills/seo/technical/indexing in kostja94/marketing-skills) into .agents/skills/indexing in your project. Codex loads it when a task matches its description.
Can I use Indexing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kostja94/marketing-skills --skill indexing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/indexing, .gemini/skills/indexing, .github/skills/indexing and .opencode/skills/indexing in your project.
What does Indexing need to run?
SKILL.md names no scripts, command-line tools or credentials: Indexing is instructions for the agent only.
Does Indexing access the network?
SKILL.md names 1 domain. As links in the text: support.google.com. This is read from the text; nothing was executed.
Is Indexing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Indexing use?
Indexing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Indexing use?
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Indexing?
Skills that share tags, products or a category with Indexing: Google SEO APIs (AgriciDaniel/claude-seo, 19k stars), SEO Coach (akseolabs-seo/seo-coach, 146 stars), SEO Setup (alisamadiii/Portfolio, 180 stars) and Google Search SEO Guide (littleben/awesomeAgentskills, 188 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Indexing?
kostja94 (a GitHub user) maintains it in kostja94/marketing-skills, which has 1,025 GitHub stars. The repository holds 102 skills in this directory. The repository was last updated on October 6, 2026.
Source: kostja94/marketing-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.