XML sitemaps: what Google actually uses, and what it ignores
Priority and change frequency do nothing in Google, the ping endpoint is gone, and lastmod only helps if it is honest. A short, accurate guide to sitemaps.
Sitemaps attract a surprising amount of folklore. Plugins offer sliders for priority and dropdowns for change frequency, and site owners spend time tuning values that have no effect. Here is what Google has said about sitemaps, in its own words, and what that means for a WordPress site.
What a sitemap is for
A sitemap is a list of the addresses you want search engines to know about. Google's documentation says it helps most with large sites, new sites with few external links, and sites with pages that are hard to reach through normal links. For a small site with good navigation, Google would probably find everything anyway. A sitemap is still cheap insurance.
It is a hint, not a command. Listing a page does not guarantee it will be crawled or indexed.
Fields Google ignores
In a June 2023 post on its Search Central blog, Google stated that it does not use the changefreq or priority elements at all. Every slider you have set is decoration. Other search engines may read them, but there is no evidence they matter much there either.
The field Google does use
lastmod, the date a page last changed, is used as a signal for scheduling recrawls, with one condition: it has to be consistently and verifiably accurate. A sitemap that marks every page as changed today, every day, teaches Google to ignore the field for your site.
Accurate means the date the content meaningfully changed: the text, structured data or links. A changed copyright year in the footer does not count.
The ping endpoint is gone
For years, plugins "pinged" Google with the sitemap address after each change. In that same 2023 post, Google announced the ping endpoint was being retired, because most of the pings it received were not useful. Requests to it now fail. Google finds sitemaps through Search Console and through the Sitemap: line in your robots.txt file.
Bing and some other engines support IndexNow, a protocol for telling them directly which addresses changed. Google does not participate.
What belongs in a WordPress sitemap
- Include pages, posts, products and other public content you want found.
- Leave out anything marked
noindex, thin archive pages you do not care about, internal search results, cart and checkout pages, and attachment pages. - Never list addresses that redirect or return errors. Every entry should answer 200 with the content at that address.
- Split large sites into several sitemaps under an index. A single sitemap may hold up to 50,000 addresses or 50 MB uncompressed.
A quick check
Open your sitemap and pick ten addresses at random. Each should load, should not redirect, and should be a page you would want in search results. If any fail, the sitemap is working against you.
In Ironhelm
Sitemaps lists your pages and keeps itself current, leaving out pages you asked search engines to skip. Dates come from real content changes. Crawlers and AI adds the sitemap to robots.txt and tells Bing and other IndexNow engines about changes the moment you publish.
Sources
- Google Search Central Blog, Sitemaps ping endpoint is going away (June 2023)
- Google Search Central, Learn about sitemaps
- Google Search Central, Build and submit a sitemap
- IndexNow
Ironhelm Suite is one WordPress plugin for security, speed, SEO and analytics. See plans or tour the features.