How to Ping Google With Your Sitemap
Pinging Google after updating your sitemap is a fast, free way to notify Googlebot that your sitemap has new content to process. Rather than waiting for Google to discover your updated sitemap during its next scheduled crawl, a ping sends an immediate signal. It's particularly useful for news sites, e-commerce stores, and any site publishing time-sensitive content where discovery speed matters.
The Google Sitemap Ping Endpoint
Google provides a simple HTTP endpoint for sitemap pings. Send a GET request to:
https://www.google.com/ping?sitemap=https://example.com/sitemap.xml
Replace the sitemap URL with your own, URL-encoded if necessary. A successful ping returns an HTTP 200 response with a simple confirmation message. You can test this in a browser or via curl: curl "https://www.google.com/ping?sitemap=https://example.com/sitemap.xml". No API key or authentication is required.
What Happens When You Ping Google?
When Google receives a sitemap ping, it queues the sitemap URL for re-fetching during Googlebot's next available crawl session. This does not guarantee immediate crawling — it adds the URL to a priority queue, which Googlebot processes based on its own scheduling. For active, well-established sites that Googlebot already crawls frequently, a ping can meaningfully shorten the time between content publication and discovery. For new or low-authority sites, the effect may be less pronounced since crawl frequency is already low.
When Should You Ping Google?
Ping Google after publishing a significant batch of new content, after completing a site migration where URLs have changed, after recovering from a sitemap error and resubmitting, or when launching a time-sensitive campaign where fast indexing matters. Avoid pinging after minor updates like fixing a typo or updating metadata on a single page — the overhead isn't worth it. A good rule of thumb: ping when at least 10+ new or significantly changed URLs have been added to the sitemap.
Ping Frequency Limits
Google recommends pinging no more than once per day per sitemap. Excessive pings are rate-limited and provide no additional benefit — they do not cause Googlebot to crawl faster or index more pages. Some CMS plugins (like older versions of WordPress SEO plugins) were notorious for pinging on every single post save, which is unnecessary and potentially counterproductive. Configure your tools to ping only on publish events, not on drafts or autosaves.
Automating Sitemap Pings
For automated pinging, integrate the ping endpoint into your publishing workflow. In WordPress, Yoast SEO and Rank Math handle this automatically. For custom applications, add a post-publish webhook or deployment hook that fires a GET request to the ping endpoint. Here is a simple Node.js example:
const sitemapUrl = encodeURIComponent('https://example.com/sitemap.xml');
await fetch(`https://www.google.com/ping?sitemap=${sitemapUrl}`);Add error handling and logging so you can confirm pings are reaching Google successfully and not silently failing due to network issues.
Ping vs. GSC Sitemap Resubmission
Pinging is faster and requires no authentication. GSC resubmission (deleting and re-adding the sitemap) is more thorough and resets any error state, but it's slower and requires manual action or API integration. For routine content updates, pinging is the right approach. Reserve GSC resubmission for cases where you've fixed a fundamental sitemap error — like an XML parse problem or a wrong sitemap URL — and need to clear the error status in the Sitemaps report.
Does Pinging Help With Indexing Speed?
Pinging helps with sitemap discovery speed, not indexing speed directly. Once Googlebot crawls your updated sitemap and discovers new URLs, those URLs enter the crawl queue. How quickly Google then indexes those pages depends on crawl budget, page quality, server speed, and other factors outside the sitemap ping's control. For a well-established site with good crawl budget, the full cycle from ping to indexed can be as fast as a few hours for high-priority content.
Bing Sitemap Ping
Bing also provides a sitemap ping endpoint at https://www.bing.com/ping?sitemap=YOUR_SITEMAP_URL. If Bing search traffic is relevant to your site, it's worth pinging Bing alongside Google. Some CMS plugins do this automatically. The same frequency guidelines apply — once per day per sitemap is sufficient, and only when content has actually changed significantly.