How do you tell AI search when a page has changed? Sitemap lastmod and IndexNow explained
Keep an accurate lastmod date on every URL in your XML sitemap, and use IndexNow to ping search engines the moment a page is added, changed or deleted. The sitemap gives a complete inventory; IndexNow gives speed. Neither one guarantees a page will be indexed, ranked or cited by an AI assistant.

- Google uses
lastmodonly if it's trustworthy: its sitemap documentation says it uses the value if it's consistently and verifiably accurate, and that it ignores<priority>and<changefreq>. - Bing says the same, with a format tip: its July 2025 webmaster post calls
lastmoda key signal for recrawling, recommends ISO 8601 dates with time, says not to set it to the time the sitemap was generated, and sayschangefreqandpriorityare ignored. - IndexNow is a push, not a pull: you tell participating search engines about an added, updated or deleted URL, and they share the submission with each other. The IndexNow site lists Bing, Naver, Seznam.cz, Yandex, Yep and Amazon as endpoints.
- Google isn't on that endpoint list: for Google, the sitemap (and Search Console) is the route.
- It's a hint, not a guarantee: IndexNow's own FAQ says submitting a URL "does not guarantee immediate indexing" and that every submitted URL counts against your crawl quota.
- Use both: IndexNow's FAQ recommends sitemaps with accurate
lastmodvalues for the full inventory and for older changes, and IndexNow for recent changes.
Why this matters for AI search
AI answers are only as current as the index behind them. Bing's webmaster blog says freshness signals influence how quickly updates show up in Bing's results and AI-generated answers, and points to lastmod and IndexNow as the signals to send. If your price, policy or opening hours changed and the search engine still holds the old page, the answer it builds will be wrong, however good your new page is.
This isn't a ranking trick. It only shortens the time between "you changed the page" and "the search engine knows".
The two signals compared
Sitemap lastmod |
IndexNow | |
|---|---|---|
| What it is | A date on each URL in your XML sitemap | A request you send when a URL is added, updated or deleted |
| Direction | Pull: engines read it when they fetch the sitemap | Push: you notify them |
| Covers | Every URL you list | Only the URLs you submit |
| Who uses it | Google and Bing both read lastmod; Google only trusts it if it proves accurate |
Bing, Naver, Seznam.cz, Yandex, Yep, Amazon (per indexnow.org) |
| Setup | Usually automatic in your CMS | A key file plus a call or a plugin |
| Best for | Complete coverage, older changes | Fast notice of recent changes, deletions and redirects |
Step 1: make lastmod honest
lastmod should be the date the page's content last meaningfully changed, not the date the sitemap was generated and not "today" for every URL. Google says it uses the value only if it is consistently and verifiably accurate, so a sitemap that stamps every page with the current date teaches the crawler to ignore the field.
What to check:
- Open
/sitemap.xmland look at a few URLs. Do the dates differ from page to page? - Edit a page, wait for your CMS to regenerate the sitemap, and see whether only that page's date moved.
- Don't bump the date for cosmetic changes such as a footer tweak.
- Use ISO 8601 with the time, for example
2026-11-09T09:04:00+00:00, as Bing recommends. - Skip
<priority>and<changefreq>. Google and Bing both say they ignore them.
We checked our own sitemap on 9 November 2026: all 45 URLs carry a full date-and-time lastmod, and the values differ per page. That is what you want to see. If yours shows the same timestamp on every URL, your CMS or plugin is stamping the whole file at once.
Step 2: add IndexNow
Does your platform already do it?
Check first. IndexNow's FAQ lists WordPress, Shopify, Wix, GoDaddy, Duda, Joomla!, Drupal, PrestaShop and several others as having native support or plugins, and says Cloudflare offers a native integration. Webflow and Squarespace aren't on that list, so for those you'd use a plugin, an automation or the manual method below. Check your platform's documentation rather than assuming.
Setting it up by hand
1. Make a key. 8 to 128 characters: letters, numbers and hyphens. A UUID works.
2. Host the key file. Create a UTF-8 text file named {your-key}.txt containing only the key, and put it at the root of your site, for example https://www.example.com/{your-key}.txt. Open it in a browser to confirm it loads without a login or firewall block.
3. Submit one URL with a GET request. Replace the values and URL-encode the page address:
https://api.indexnow.org/indexnow?url=https%3A%2F%2Fwww.example.com%2Fpage1&key=your-key
4. Or submit a batch (up to 10,000 URLs) with a POST to https://api.indexnow.org/indexnow:
{
"host": "www.example.com",
"key": "your-key",
"urlList": [
"https://www.example.com/url1",
"https://www.example.com/url2"
]
}
5. Read the response code. The common ones:
| Code | Meaning |
|---|---|
| 200 | URL received |
| 202 | Received, key validation pending (often seen on the first request) |
| 400 | Bad format, for example an unencoded URL or a missing key |
| 422 | URL doesn't belong to the host, or the key doesn't match |
| 429 | Too many requests: slow down |
You only need to send your request to one endpoint, because participating engines share submissions.
Rules worth following
- Submit when something meaningful changed: content, price, availability, a deletion or a redirect. Don't submit cosmetic changes.
- Wait at least 5 minutes before resubmitting the same URL.
- Deleted and redirected URLs are fair game: submit them so engines can drop or update the old address.
- Don't dump your whole site through IndexNow every day. It's meant for recent changes; the sitemap is for the full inventory.
What neither signal does
- It doesn't make a search engine index the page. Quality, duplicate content, a
noindextag, a robots.txt block or crawl quota can all stop it. - It doesn't make an AI assistant cite you.
- It doesn't help a crawler that's blocked. If your firewall or robots.txt turns a bot away, no signal fixes that, so start with crawler access.
- IndexNow isn't a route into Google. Keep your sitemap accurate and submitted in Search Console for Google.
Run it automatically
If you'd like to see how a site scores on the basics AI tools look for, the free Web2Agents AI check scores your homepage with results on screen in real time. The €19 AI-Ready Kit runs all 36 checks on up to 25 pages and ranks the fixes.
FAQ
What is the difference between a sitemap and IndexNow?
A sitemap is a list of your URLs that search engines read when they choose to. IndexNow is a notification you send when a URL is added, changed or deleted. IndexNow's FAQ recommends using both: IndexNow for recent changes and the sitemap for complete coverage.
Does Google support IndexNow?
Google isn't listed among the IndexNow endpoints on indexnow.org. For Google, rely on an accurate sitemap and Search Console.
Will IndexNow get me into ChatGPT, Copilot or Perplexity answers?
No. It tells participating search engines a URL changed. Whether that page is indexed, and whether an AI product uses it, is decided by each engine and product.
How often should I submit the same URL?
Only when it changes in a meaningful way, and no more than once every 5 minutes. Resubmitting unchanged URLs wastes crawl quota and can trigger errors.
Is lastmod worth fixing if I already use IndexNow?
Yes. The IndexNow FAQ says IndexNow only covers changes made after you set it up, and recommends sitemaps with accurate lastmod values for everything older.
Sources
- IndexNow documentation, IndexNow.org
- IndexNow FAQ, IndexNow.org
- Build and submit a sitemap, Google Search Central
- Keeping Content Discoverable with Sitemaps in AI Powered Search, Bing Webmaster Blog, 31 July 2025
- Web2Agents sitemap, checked 9 November 2026


















