Indexnow
Wire up IndexNow so new or changed URLs notify Bing and Yandex faster after you ship site updates.
Overview
IndexNow is an agent skill for the Launch phase that implements the IndexNow protocol so Bing and Yandex are notified of new or updated URLs on your domain.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill indexnowWhat is this skill?
- Generate an API key and host the `{key}.txt` verification file at your site root
- Assess site URL, URL source (sitemap, CMS, config), and CI vs manual deployment
- Submit new or updated URLs to Bing/Yandex via the IndexNow API
- Pairs with xml-sitemap skill when sitemap is the single source of truth for URL lists
- Scoped to IndexNow and URL notification (not full sitemap architecture)
- 3-part initial assessment: site URL, URL source, deployment mode
Adoption & trust: 774 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You publish pages on a schedule but Bing still discovers changes slowly because nothing tells the index when URLs go live.
Who is it for?
Solo builders with a known site URL and deployment path who care about Bing/Yandex indexation latency.
Skip if: Teams that only target Google Search Console ping workflows or need full sitemap design without URL submission—use xml-sitemap and broader technical SEO skills instead.
When should I use this skill?
User wants IndexNow, Bing indexing, URL notification, instant indexing, sitemap IndexNow sync, or IndexNow API integration.
What do I get? / Deliverables
You end with a verified API key on-domain, a defined URL source, and a repeatable IndexNow submission path aligned with your deploy workflow—then use xml-sitemap when the sitemap should own the URL list.
- IndexNow API key and hosted verification file
- Documented URL source and submission workflow (manual or CI)
Recommended Skills
Journey fit
Faster crawl discovery sits in Launch where technical SEO and indexation speed matter right after publishing. IndexNow is a technical SEO protocol for URL notification—not content writing or distribution campaigns.
How it compares
Technical URL-notification integration for Bing, not a content generator or GSC-only indexing playbook.
Common Questions / FAQ
Who is indexnow for?
Indie developers and small teams running content or marketing sites who deploy frequently and want faster Bing-side discovery via IndexNow.
When should I use indexnow?
At Launch when you add IndexNow, notify engines of new URLs, sync submissions with sitemap exports, or automate post-deploy indexing signals in CI.
Is indexnow safe to install?
Review the Security Audits panel on this Prism page and inspect the skill bundle before granting network or filesystem access in your agent.
Workflow Chain
Then invoke: xml sitemap
SKILL.md
READMESKILL.md - Indexnow
# 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 | Method | When to use | |--------|-------------| | **Single URL** | New or updated page | | **Batch** | Many URLs at once (e.g., after deploy) | | **Relative paths** | Convert to full URLs before submitting | ### 3. Best Practices | Practice | Note | |----------|------| | **When to submit** | New pages, major content updates, meta changes | | **When not to** | Minor edits; let natural crawling handle | | **Frequency** | Once per deploy; avoid excessive submissions | | **Priority** | Submit high-value commercial pages first | ### 4. CI/CD Integration ```bash 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 - Check [Bing Webmaster Tools](https://www.bing.com/webmasters/indexnow) for indexing status - Monitor submission logs for errors ## Common Issues | Issue | Fix | |-------|-----| | Domain verification fails | Ensure URL uses correct domain | | API key error | Verify key and verification file match | | Network errors | Retry; 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](https://www.bing.com/indexnow/getstarted) ## Related Skills - **xml-sitemap**: Share same URL list from central config - **indexing**: Broader indexing strategy