The old sitemap ping endpoint — the URL you would call to notify Google or Bing that your sitemap had changed — is gone. Google removed support for its ping endpoint, and Bing had already retired its own. If your publishing workflow still fires a request to that endpoint after every update, it now does nothing. In 2026, sitemap discovery relies on three things instead: a reference in your robots.txt, submission through Search Console, and the accurate lastmod dates inside the sitemap itself.
What changed and why
For years, the standard trick after updating content was to send an automated ping so search engines would re-fetch your sitemap sooner. That endpoint was widely abused and largely ignored — pinging did not meaningfully speed up crawling, and it generated noise. So the major engines deprecated it. The unsolicited ping is no longer a signal anyone acts on, which means any script or plugin still calling it is spending effort for zero effect. It is worth auditing your deploy pipeline to remove those dead calls.
Importantly, this changes discovery notification, not sitemaps themselves. Your XML sitemap is as valuable as ever — it is still how engines learn the full set of URLs you want crawled. Only the "poke us to look now" mechanism went away.
How sitemaps get discovered now
Three reliable methods remain, and you should use all three:
- Reference it in robots.txt. A Sitemap line in your robots.txt file points every crawler that reads it straight to your sitemap. This is the most universal method because it is not tied to any one engine's dashboard. If you are unsure of the syntax, see the complete robots.txt guide.
- Submit through Search Console and Bing Webmaster Tools. Adding your sitemap in each engine's console registers it permanently. The engine then re-checks it on its own schedule — you do not need to re-submit after every change.
- Keep lastmod accurate. When a crawler re-reads your registered sitemap, the lastmod date on each URL tells it what has actually changed. Honest lastmod values are the closest thing to a freshness signal you have left.
The lastmod discipline that now matters more
With the ping gone, your lastmod field carries more weight. It should reflect the real date a page's meaningful content changed — not the date your CMS last rebuilt the site, and not today's date stamped on every URL. Engines learn quickly to distrust sitemaps where every entry claims to have changed on the same day, and once they distrust your lastmod, they ignore it. Update the value only when the content genuinely changes, and it becomes a trustworthy hint that helps crawlers prioritize your updated pages. For very large sites split across many files, the same honesty applies to each child sitemap, as covered in managing XML sitemaps for large sites.
When you genuinely need fast indexing
If losing the ping worries you because you publish time-sensitive content, there is a better-supported path for instant notification: the IndexNow protocol. Rather than pinging a sitemap endpoint, IndexNow lets you notify participating engines — including Bing and Microsoft Copilot's index — the moment a specific URL is published or changed, and they can fetch it right away. It is the modern replacement for the "look at this now" use case the sitemap ping used to serve, and it operates per-URL rather than per-sitemap. The full mechanics are in the IndexNow guide to instant indexing.
Your 2026 sitemap checklist
- Remove any automated calls to the old sitemap ping endpoints — they are dead.
- Reference your sitemap in robots.txt so every crawler can find it.
- Submit it once in Search Console and Bing Webmaster Tools; no need to resubmit per change.
- Maintain honest lastmod values that reflect real content changes.
- Use IndexNow for genuinely time-sensitive URLs that need fast pickup.
The end of the ping endpoint is a small cleanup, not a crisis — but only if your discovery setup rests on the methods that still work. To confirm your sitemap is discoverable, your robots.txt points to it correctly, and crawlers can reach everything you want indexed, run the CheckMy.site scanner.