How Yoast Sitemap Settings Relate to Noindex Tags
On a WordPress site, Yoast controls which URLs appear in its XML sitemap and whether pages should appear in search results. An…
Categories
Verifying Yoast Sitemaps After Theme or Plugin Updates
After a WordPress theme or related plugin update, maintainers should check whether Yoast SEO still publishes the intended sitemap index and whether its child sitemaps contain the expected public URLs. A sitemap index is an XML file that points search engines to separate sitemap files for content such as posts, pages, and taxonomies. Yoast’s main index is usually at /sitemap_index.xml.
An index change may reflect changes to content eligibility or configuration, so it does not by itself show a problem. Yoast includes content only when it is public and eligible for indexing, and a theme or plugin change can affect whether a custom content type exists or whether Yoast is configured to include it. Compare the index and representative child sitemaps with the site’s intended content, then check the settings and WordPress registrations behind any unexpected change.
Check the index and its child sitemaps
Open /sitemap_index.xml directly and inspect the XML source. The Yoast sitemap specification shows an index with one <sitemap> entry for each child sitemap. Each entry includes a <loc> value, which identifies the child sitemap’s absolute URL; a <lastmod> value is optional. Yoast also provides a dashboard link labeled View the XML sitemap. See the Yoast sitemap specification for the documented structure.
Compare the index entries with the content types and taxonomies the site should include. Posts, pages, custom post types, authors, and taxonomies can have separate sitemaps, but Yoast does not create an entry for every possible type. A type must be public and have eligible content. For example, an author sitemap depends on authors having qualifying published content.
Open representative child sitemaps and check that their <loc> values point to the expected canonical URLs: the preferred URLs for the listed content. Confirm that the URLs use the site’s intended host and protocol, such as HTTPS. If the site has many items of one type, check the full index for additional child sitemap files. Yoast’s specification documents a default limit of 1,000 items per sitemap and describes numbered files such as post-sitemap2.xml for overflow. Treat that limit as a documented default, since the installed Yoast version or custom code may change the behavior.
A sitemap response can include X-Robots-Tag: noindex, follow. That header tells search engines not to list the sitemap file as a search result; it does not by itself mean they cannot read the sitemap. Use /sitemap_index.xml as the primary Yoast endpoint. If /sitemap.xml returns a sitemap or redirects elsewhere, inspect the response and redirect chain to identify which component generated it. Yoast’s help documentation and developer specification describe that endpoint differently, so the endpoint name alone does not establish an error.
Re-check Yoast settings and content registration
Confirm that XML sitemaps remain enabled under Yoast SEO → Settings → Site features → Technical SEO, then review Settings → Content types and check the search visibility setting for each type the site expects in the index. Yoast removes a content type from the sitemap when that type is disabled for search results. Check the Categories & tags settings for expected taxonomies as well. Yoast describes these controls in its guidance on customizing the sitemap index.
Check the individual URLs that disappeared. A page-level or type-level noindex setting can explain why a particular URL is absent. A manually changed canonical URL or a Yoast Premium redirect can also explain its absence. Also review relevant archive settings and any custom code that excludes content from the sitemap.
A theme update deserves a separate check when the theme registers custom post types or taxonomies. WordPress defines a custom post type as a content type beyond built-in Posts and Pages. If the active theme supplied that registration and the update removed or changed it, WordPress may no longer expose the expected type to Yoast. Before concluding that Yoast failed to generate the sitemap, confirm that the type still exists, is public, and has eligible content. WordPress documents the role of register_post_type(), while Yoast documents developer filters that can exclude content types.
Also check the WordPress Address and Site Address under Settings → General if the site recently changed its preferred host or protocol. If the site is configured to discourage search indexing, an empty index or one without URLs can be expected. Sites using Yoast Video SEO or News SEO should separately confirm that the add-on and its sitemap entries remain expected; those sitemaps depend on the corresponding extension.
Match symptoms to the likely cause
| What you see | What to check |
|---|---|
| A child sitemap disappeared from the index | Confirm that its content type or taxonomy still exists, is public, has eligible members, and is enabled for search results. Check theme, plugin, and custom-code exclusions. |
| One URL is missing | Review that item’s noindex and canonical settings, its type-level visibility, and any Yoast Premium redirect. |
| The index or a child sitemap returns a 404 or an unexpected page | Check permalink rules and server rewrites. Yoast recommends saving the Permalinks settings without changing them when the sitemap endpoint fails. |
| The XML source is stale after a change | Check plugin, theme, host, and server caches. Yoast notes that caching can prevent the displayed sitemap from reflecting current content. |
| The source is empty, malformed, or has unexpected output before the XML | Look for a static sitemap file, conflicting sitemap generator, or unexpected output from a theme or plugin. |
| The browser display is blank or unstyled, but the source contains XML data | Check whether the referenced XSL stylesheet, which controls browser presentation, loads correctly. A display problem is different from missing sitemap data. |
| URLs use the wrong host or protocol | Verify the WordPress Address and Site Address, then check whether stored site URLs need updating. |
Yoast discusses these failure patterns in its guidance on common XML sitemap errors and blank sitemap output. A valid XML document with no eligible entries can reflect visibility or content rules. Blank or malformed output calls for investigating the response itself. Check rewrites and conflicts, and look for files that take precedence.
Compare before and after the update
Before a planned update, save the sitemap index and representative child sitemap URLs, and record the relevant Yoast settings. After the update, open the same URLs and compare their entries. This baseline makes it easier to separate an intended content change from a configuration change.
When an entry differs, start with Yoast’s sitemap toggle and visibility settings. Confirm that the expected post types and taxonomies still exist in WordPress. Review individual URL settings and inspect custom exclusions. If the XML is correct but the browser display is not, focus on the stylesheet. If the XML is stale, check caching; if the endpoint fails or returns a different page, check rewrites and competing sitemap files.
If those checks do not identify the cause, test for a conflict. Yoast recommends using WordPress Health Check & Troubleshooting mode to test with plugins disabled and a default theme. Then re-enable Yoast, the preferred theme, add-ons, and other plugins one at a time. The mode lets maintainers test without changing what normal visitors see.
What I'm buildingDelegate 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