IndexNow and Indexing APIs in Vue
- IndexNow pushes URL changes straight to Bing, Yandex, Naver, Seznam.cz, and Yep; Google does not participate
- The Google Indexing API only works for pages marked up with JobPosting, or livestream VideoObject containing BroadcastEvent; use supported procedures for ordinary pages
- Publish the verification key and notify through a controlled publishing workflow; notification does not prove indexing
Search engines discover content changes by crawling on their own schedule, and Google won't commit to a timeline for how long that takes. Notifications provide another discovery signal. Engines still decide whether and when to crawl or index.
IndexNow Protocol
IndexNow is an open protocol that notifies search engines instantly when URLs change. Instead of waiting for crawlers to discover updates, you push notifications directly to participating engines.
Supported search engines:
- Microsoft Bing, the protocol's primary backer
- Yandex, a participating engine
- Seznam.cz, a participating engine
- Naver, a participating engine
- Yep, Ahrefs' privacy-focused search engine
Google does not support IndexNow. Use Google Search Console's manual "Request Indexing" feature, or one of the tools covered below.
IndexNow can notify Bing about changed URLs, since Copilot answers draw on Bing's search index. Bing has said sitemaps and IndexNow both feed how it surfaces content in AI-powered search. Whether Perplexity benefits isn't confirmed by any of its own documentation, so treat that as speculative rather than a reason to adopt IndexNow on its own.
When to Use IndexNow
Use IndexNow when:
- Publishing new content (blog posts, product pages)
- Updating existing pages (price changes, corrections)
- Deleting pages (discontinued products, removed content)
- Fixing critical errors on important pages
- Running time-sensitive content (news, events, flash sales)
Use notifications for meaningful public content changes. Do not submit private URLs. Notification does not override noindex or access controls.
Setting Up IndexNow
Generate an API key. The spec requires 8 to 128 characters, using only letters, numbers, and dashes:
openssl rand -hex 32Create a key file in your public directory:
abc123def456The key must be accessible at https://yoursite.com/{key}.txt for verification.
Submitting URLs
Submit changed URLs through your controlled publishing workflow. Each URL must belong to the verified host. Replace all example fields with your public host, key, and actual URLs:
{
"host": "yoursite.com",
"key": "abc123def456",
"keyLocation": "https://yoursite.com/abc123def456.txt",
"urlList": ["https://yoursite.com/page"]
}Save the replaced JSON as payload.json, then POST it to the IndexNow endpoint:
curl --request POST https://api.indexnow.org/indexnow \
--header 'Content-Type: application/json; charset=utf-8' \
--data-binary @payload.jsonDo not expose an arbitrary unauthenticated input-to-submission server route. The protocol documentation defines host/key checks and response codes. HTTP 200 means the engine received the notification; 202 means key validation is pending. Neither proves indexing.
You can submit up to 10,000 URLs in one POST. The protocol also supports a single-URL GET request; follow its documented URL-encoding requirements.
Google Indexing API
Google's Indexing API is limited to JobPosting, or livestream VideoObject containing BroadcastEvent.
Don't use it for blog posts or general products. Google restricts this API to its supported page types. Do not treat an unsupported submission as a general indexing procedure.
The default quota is 200 publish requests per day per project, resetting at midnight Pacific. Google describes this as an initial onboarding and testing quota. Use the approval form linked from its quota documentation for eligible content; supply your Google Cloud project details.
RequestIndexing Tool
RequestIndexing distinguishes ordinary pages from eligible Indexing API content. Its current public guidance directs ordinary pages to URL Inspection or sitemap discovery.
Google's Indexing API is restricted to JobPosting pages and livestream VideoObject pages containing BroadcastEvent. No third-party tool removes that restriction or guarantees an urgent recrawl.
Choosing the Right Method
| Method | Best For | Limitations |
|---|---|---|
| IndexNow | Bing, Yandex, Naver, Seznam.cz, Yep | Doesn't reach Google |
| Google Indexing API | Job listings, livestream events | JobPosting/BroadcastEvent only |
| RequestIndexing | Check the supported submission path | Google eligibility and quotas still apply |
| XML Sitemap | Routine discovery | No urgency signal |
Use IndexNow when participating engines and URL-change notifications fit your workflow. For ordinary Google content, use crawlable links, sitemaps, or URL Inspection. Notification does not guarantee indexing.
Using Nuxt?
If you use Nuxt, follow the current Nuxt AI Ready IndexNow recipe for your installed version and configured public host. See the Nuxt IndexNow guide for the full setup.
Checklist
- Generate an IndexNow key and serve it at
/{key}.txt - Trigger notifications from a controlled publish/update workflow and inspect the response
- Submit your sitemap to Google Search Console for Google discovery
- Reserve the Google Indexing API for JobPosting/BroadcastEvent content only
- Check notification responses separately from crawling and indexing