agentleFS
gaznilgaznil/seo-skills-by-gaznil/skills/indexnow/SKILL.md

indexnow

Skill0 starsChanged 3 months agoMITView on GitHub

When the user wants to implement IndexNow, notify search engines of new/updated URLs, or speed up Bing indexing. Also use when the user mentions "IndexNow," "Bing indexing," "URL notification," "instant indexing," "sitemap IndexNow sync," "share URL list with sitemap," or "IndexNow API." For sitemap SSOT, use xml-sitemap.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site URL.

    line 21
  2. Very specific:

    Create verification file: https://example.com/{key}.txt

    line 37
  3. Very specific:

    Use same config as sitemap: Import URL list from central config (e.g., site-pages-config.ts) or sitemap generation logic.

    line 67
  4. Distinctive:

    Feed: If you have RSS/feed, it can also consume from the same config to stay in sync.

    line 69
  5. Distinctive:

    Google: Does not use IndexNow; use Sitemap + Search Console

    line 75
  6. Distinctive:

    Check Bing Webmaster Tools for indexing status

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SEO Technical: IndexNow

Guides IndexNow protocol integration for faster search engine indexing (primarily Bing).

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)

  • IndexNow: Submit URLs to Bing/Yandex for faster indexing
  • URL notification: Notify search engines of new or updated URLs

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site URL.

Identify:

  1. Site URL: Base domain
  2. URL source: Config file, sitemap, CMS, etc.
  3. Deployment: CI/CD, manual, or both

Overview

IndexNow notifies search engines (mainly Bing) of new or updated URLs to speed up indexing.

Implementation Steps

1. API Key and Verification

  • Generate API key (e.g., UUID)
  • Create verification file: https://example.com/{key}.txt
  • File content: the API key string
  • Configure key and URL in your IndexNow client

2. Submission Methods

MethodWhen to use
Single URLNew or updated page
BatchMany URLs at once (e.g., after deploy)
Relative pathsConvert to full URLs before submitting

3. Best Practices

PracticeNote
When to submitNew pages, major content updates, meta changes
When not toMinor edits; let natural crawling handle
FrequencyOnce per deploy; avoid excessive submissions
PrioritySubmit high-value commercial pages first

4. CI/CD Integration

npm run build
npm run indexnow:all

5. Single Source of Truth (URL List)

  • Use same config as sitemap: Import URL list from central config (e.g., site-pages-config.ts) or sitemap generation logic.
  • Avoid: Separate hardcoded URL lists for IndexNow—leads to inconsistency and missed URLs.
  • Feed: If you have RSS/feed, it can also consume from the same config to stay in sync.

Supported Search Engines

  • Bing: Primary support
  • Yandex: Supports IndexNow
  • Google: Does not use IndexNow; use Sitemap + Search Console

Verification

Common Issues

IssueFix
Domain verification failsEnsure URL uses correct domain
API key errorVerify key and verification file match
Network errorsRetry; API can be intermittent

Output Format

  • Setup steps: Key generation, verification file
  • Submission flow: Single vs. batch
  • Integration: CI/CD or manual script
  • References: IndexNow docs

Related Skills

  • xml-sitemap: Share same URL list from central config
  • indexing: Broader indexing strategy

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.