Troubleshooting a Missing Yoast SEO Sitemap Index

On a WordPress site, Yoast SEO creates a sitemap index, an XML file that lists smaller sitemaps for content such as posts and pages. Search engines use these files to find URLs. If the index seems to be missing, check whether Yoast’s XML sitemap feature is off, a request is blocked or redirected, or a visibility setting has removed content from the sitemap.

Find the setting at WordPress Dashboard → Yoast SEO → Settings → Site features → Technical SEO. Turn XML sitemaps on, then open yourdomain.com/sitemap_index.xml. Check the page response and the address bar. They show whether the feature is off, the request is blocked, or the sitemap loads but leaves out expected content.

Check the sitemap setting and requested URL

Open the sitemap index in a browser and check the final URL and page response. Yoast’s sitemap index normally uses /sitemap_index.xml. Yoast does not generate URLs ending in /sitemap.xml. WordPress core or another plugin may serve that URL instead, according to Yoast’s XML sitemap documentation.

If /sitemap_index.xml does not show the expected index, check that the XML sitemaps toggle is on in the settings above. Another sitemap plugin or a physical sitemap.xml file on the server can cause your browser to display a different sitemap. Turn off the other plugin’s sitemap generation and remove any conflicting physical file before testing Yoast’s URL.

Yoast has documented that visitors to a Yoast sitemap page are redirected to WordPress core sitemaps when the site is not fully indexed. Check the browser’s final address. If it changes to a core sitemap URL, the request was redirected. See the relevant Yoast issue.

Tell a disabled sitemap from a blocked request

If Yoast has disabled the sitemap, first check the XML sitemaps toggle. If search engines cannot access it, check the site’s access rules. For example, robots.txt can stop search engines from crawling the sitemap. Google Search Console reports this as “URL blocked / restricted by robots.txt.” Before changing Yoast settings, check the site’s robots.txt rules and the URL named in Search Console. Yoast’s sitemap troubleshooting steps cover this and other common sitemap errors.

Yoast’s XML sitemap includes the noindex, follow HTTP header, an instruction sent with the response. It tells search engines not to index the sitemap file itself, but to follow the URLs listed in it. The header does not mean the sitemap is inaccessible.

A 404 response means the requested URL was not found. The response alone does not identify the cause. First, open Settings → Permalinks and click Save Changes without changing the settings. WordPress then refreshes the rewrite rules, which direct sitemap requests to the right place. If the 404 remains, check that the web server has the rewrite rules it needs. Yoast notes that missing rules can stop sitemap requests from working on Apache or NGINX servers.

Check whether visibility settings removed content

If the index loads but leaves out a post type or taxonomy, check Yoast’s search-visibility settings. A taxonomy is a way to group content, such as with categories or tags. You can change the sitemap index in Content types settings. You can also change it in Categories & tags settings. Advanced settings can change it as well. When you set a post type to stay out of search results, Yoast also removes it from the sitemap. Compare the missing entry with those settings using Yoast’s sitemap customization instructions.

A missing or blank date beside an individual sitemap entry points to a different issue: that sitemap is usually unavailable. Open it directly. If it returns a 404, troubleshoot that sitemap, which is listed under the index, rather than treating the index itself as missing. Yoast describes this pattern in its guidance on missing or invalid sitemap dates.

Refresh caches and investigate display errors

A cache stores a copy of a page and can serve an old sitemap after you change settings or content. Clear the caches that serve the site, including any server-level cache, then reload the index. If the sitemap still does not update, Yoast recommends turning the XML sitemap feature off, clearing the cache, and turning the feature back on. Follow Yoast’s sitemap update instructions.

A blank page, a page that shows only a header, or an HTML page instead of XML points to a display or configuration problem. Yoast lists an unavailable XSLT file, which formats XML for display, invalid XML, and the W3 Total Cache setting “Do not process 404 errors for static objects with WordPress” as possible causes. If the W3 Total Cache plugin is active, check that setting. Also compare the sitemap response and server configuration with Yoast’s common XML sitemap errors.

What I'm building

Delegate tasks. Get software.

Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.

Take a look at vroni.com