Astro Integration
Astro IndexNow
Automatically notify IndexNow-compatible search engines when Astro pages change — without resubmitting unchanged URLs.
Last Updated: 01 April 2026
Usage Snapshot
5,712
Downloads in Last 30 Days
v2.1.1
Latest npm Version
Source: npm registry
Why This Plugin Exists
Search engines typically rely on crawling to discover content changes, which can introduce delays between when content is updated and when it is discovered.
IndexNow provides an open protocol for proactively notifying search engines when URLs are created, updated, or removed.
Astro IndexNow integrates directly into Astro’s build lifecycle and submits only URLs that have actually changed, based on the final generated HTML output.
Design Principles
- Build-time only — no runtime or client-side execution
- Changed-only submissions based on real HTML output
- No analytics, telemetry, or tracking
- Deterministic and CI/CD-safe
- No dashboards, background services, or cron jobs
What This Plugin Delivers
- Detects real content changes using HTML hashing
- Submits only changed URLs to IndexNow
- Batches submissions to respect protocol limits
- Runs automatically during astro build
- Uses a small local cache for incremental behaviour
Installation
npm install astro-indexnow
Configuration is handled via the plugin options and a small local cache file used to detect changes between builds.
FAQs
What does the Astro IndexNow plugin do?
Astro IndexNow submits only new or changed URLs to IndexNow-compatible search engines during the Astro build process, avoiding unnecessary re-submission of unchanged pages.
Does Astro IndexNow affect Google Search?
No. Google does not currently use IndexNow. The plugin has no impact on Google indexing, crawling, or rankings.
Implementation FAQs
What problem does Astro IndexNow solve?
Astro IndexNow solves the problem of repeatedly submitting unchanged URLs to IndexNow. It ensures only URLs whose final HTML output has changed are submitted.
How does the plugin detect changed pages?
The plugin hashes the final generated HTML output for each page and compares it against a stored hash from the previous build.
Why hash the final HTML instead of source files?
Hashing final HTML ensures that only real, user-visible changes trigger submissions, regardless of where those changes originate.
What is the cache file used for?
The cache stores URL-to-hash mappings from the previous build so the plugin can detect which pages have changed.
Should the cache file be committed in Git?
Yes for CI/CD. CI environments are ephemeral, so committing the cache file allows correct change detection across deployments.
What is IndexNow?
IndexNow is an open protocol that allows websites to notify participating search engines when URLs are created, updated, or removed.
Project Links
Source code, package distribution, releases, and documentation.
Need Implementation Details?
Read the FAQs for usage patterns, integration caveats, and rollout guidance.