thelastapi
Get started free

Get new pages indexed faster with IndexNow

IndexNow instantly notifies search engines when pages are added or updated, and thelastapi triggers it automatically after every production deploy.

On this page 8 sections

IndexNow is an open protocol that immediately alerts participating search engines when URLs are added, updated, or deleted on your site. Instead of waiting days or weeks for crawlers to discover changes through scheduled sitemap crawls, IndexNow pushes modified URLs directly to search engines like Bing, Yandex, Naver, and Seznam within minutes. thelastapi automates this entire submission process after every production deployment, requiring zero manual pings or custom webhook scripts.

Understanding how IndexNow handles URL distribution, key verification, and sitemap tracking helps ensure your newest content gets crawled and indexed without unnecessary delays.

How IndexNow accelerates search engine discovery

Traditional search engine indexing is passive. A crawler periodically visits your site, downloads your sitemap, follows links, and allocates a crawl budget across your domain. For newer sites or rapidly updated catalogs, this discovery process can take days or weeks.

IndexNow changes this discovery dynamic from pull to push:

  • Immediate notification. When a URL is created or changed, a ping is sent directly to the IndexNow gateway.
  • Shared distribution. Notifying one IndexNow endpoint alerts all participating engines, including Bing, Yandex, Naver, and Seznam.
  • Resource efficiency. Search engines crawl only the pages that actually changed, rather than repeatedly requesting static, unmodified URLs.

Google does not participate in IndexNow. Google relies on standard sitemap processing and its own Search Console integrations. However, for Bing and other supported search engines, IndexNow provides near-instant notice of fresh content.

How automatic IndexNow submission works on deploy

Search indexing is built directly into the hosting environment on thelastapi. You do not need to configure build plugins, write serverless functions, or manage third-party webhook dispatchers.

Whenever a production deployment goes live—whether triggered by a fresh build, promoting a staging build, or rolling back a release—the platform executes an automated search routine:

  1. Reads the sitemap: The system reads your site's /sitemap.xml file, including every child sitemap listed in a sitemap index. If your site does not yet serve a sitemap, it sends your home page once.
  2. Detects modifications: It compares current URLs against previous deploy records. A page is selected if it is completely new or if its <lastmod> timestamp has changed since the previous run.
  3. Dispatches to IndexNow: Selected URLs are sent immediately to IndexNow. If a ping fails or is refused, IndexNow retries on its own after 1 hour, 6 hours, and 24 hours, as well as on the subsequent deployment.

By default, submissions run only for your project's first live custom domain. The free <slug>.vibiz.app address is excluded from submissions by default to prevent half-finished prototypes from populating search engine indexes. Once you connect a custom domain, only that domain's URLs are sent. If you want the free address indexed before your custom domain is live, you can enable it manually:

Terminal
vibiz search free-address on

You can toggle the same setting via the API:

Terminal
curl -X PATCH https://thelastapi.dev/v1/projects/prj_123/search \
  -H "Authorization: Bearer $VIBIZ_API_KEY" \
  -H 'content-type: application/json' \
  -d '{"submit_free_address": true}'

How site ownership verification works

IndexNow requires proof of domain ownership before accepting URL submissions. This proof is established using a unique key served as a text file at the root of your website: /<key>.txt.

You do not need to generate, store, or rotate this key file by hand. thelastapi injects the key file automatically into every production deployment:

  • For applications using a package.json, the verification file is added to public/ (or static/ if your project structure already uses a static directory).
  • For plain static sites, the verification file is placed directly in the web root.
  • If your application already ships its own file at /<key>.txt, your existing file is preserved.

When an IndexNow run cannot submit URLs, the note field in your search data tells you why. The two most common reasons are running without a custom domain or deploying before the key file has been served. Triggering a fresh production deploy resolves the key file placement.

Submitting new and changed pages on demand

While deploy-triggered submissions handle your routine updates, you can also dispatch URL updates on demand. This is useful when database-backed content changes without a new code release or when updating markdown files on an external backend.

From your terminal, submit modified pages immediately using the CLI:

Terminal
vibiz search submit

To submit on demand from an automated script, CI runner, or backend service, call the project's search submission endpoint:

Terminal
curl -X POST https://thelastapi.dev/v1/projects/prj_123/search/submit \
  -H "Authorization: Bearer $VIBIZ_API_KEY"

The response confirms whether URLs were submitted or explains why no pages were dispatched (for instance, if no <lastmod> timestamps changed since the last run).

Monitoring IndexNow status and search metrics

You can inspect the state of your search submissions across projects directly in the console under SEO, or programmatically through the CLI and API.

Run vibiz search to see submission details for your active project:

Terminal
vibiz search

To fetch raw JSON data for monitoring scripts:

Terminal
curl https://thelastapi.dev/v1/projects/prj_123/search \
  -H "Authorization: Bearer $VIBIZ_API_KEY"

The returned object contains an indexnow block detailing submission history:

JSON
{
  "indexnow": {
    "host": "example.com",
    "sending_free_address": false,
    "submit_free_address": false,
    "key_url": "https://example.com/8f9a2b1c4d5e.txt",
    "pages_sent": 142,
    "last_sent_at": "2025-05-10T14:32:00Z",
    "last_sent_count": 8,
    "note": null
  }
}

For complete coverage, read the Search docs to see how Google Search Console and Bing Webmaster Tools integrate alongside IndexNow.

Comparing search discovery channels

IndexNow works alongside direct search engine consoles rather than replacing them entirely. Here is how search discovery channels behave on the platform:

Discovery channelSupported search enginesTriggerVerification methodBest for
IndexNowBing, Yandex, Naver, SeznamEvery production deploy or manual submitAuto-injected /<key>.txt fileReal-time indexing of new and modified URLs
Bing WebmasterBingDaily sync via API key (vibiz search sync)Auto-injected BingSiteAuth.xml fileCrawl error monitoring, search impressions, ranking analytics
Google Search ConsoleGoogleDaily sync via connected Google account or service account keyDNS record or auto-injected /google<code>.htmlClicks, positions, inspections, and indexing status

Connecting Bing Webmaster Tools via your API key (POST /v1/search/bing) allows the platform to submit sitemap URLs directly to Bing within your site's reported daily quota, supplementing your IndexNow pings.

Auditing pages before requesting indexation

Before submitting newly published URLs to IndexNow, ensure those pages meet technical SEO baselines. Search engines that crawl pages quickly will also catalog technical flaws quickly.

You can inspect technical issues on any page using the built-in SEO audit action:

Terminal
vibiz seo audit https://example.com/blog/new-post

This audit checks for missing title tags, descriptions, empty H1 headers, broken status codes, slow page loads, and images missing alt text. You can also research search interest before publishing using keyword ideas with volume and difficulty from one call.

If you want to verify how crawlers parse your rendered content, you can scrape a website to markdown with one API call or inspect the visual layout by learning how to screenshot a web page with an API. Full parameter references for audit and crawling actions are available in the Web data actions documentation.

To submit your site to search engines right now, verify your domain and check your indexing status with vibiz search.

Frequently asked questions

Why doesn't Google index my pages through IndexNow?

Google does not participate in the IndexNow protocol. Google discovers pages through sitemap reads and Google Search Console, which you can connect directly in thelastapi using a Google service account key or OAuth sign-in.

Does IndexNow send every URL on my site after every deploy?

No, IndexNow only sends pages that are brand new or whose `<lastmod>` date in your sitemap has changed since the previous run. This prevents unnecessary crawl requests for unchanged static pages.

Where does the IndexNow verification key file live?

thelastapi automatically serves the verification key at `/<key>.txt` on every production deploy. For JavaScript projects it is placed in `public/` or `static/`, and for static sites it sits at the root.

Can I use IndexNow before buying a custom domain?

By default, IndexNow only submits pages for a project's first live custom domain. If you want to index pages under the free address first, enable it using `vibiz search free-address on` or set `submit_free_address: true` via the API.