Documenting Yoast SEO Sitemap Settings for Client Handoffs

When handing off a WordPress site, record both whether Yoast SEO generates XML sitemaps and which kinds of content Yoast includes in them. An XML sitemap is a file that lists URLs for search engines to discover. The sitemap index is the top-level file that links to the individual sitemaps, such as those for posts or pages.

These settings determine which URLs can appear in search results and in the sitemap. In the handoff, list the settings and the client’s choices, then check the live sitemap index. This helps the next maintainer compare the saved choices with the files the public site serves.

Record the master sitemap setting and content visibility

Yoast’s site-wide sitemap switch is at WordPress Dashboard → Yoast SEO → Settings → Site features → Technical SEO → XML sitemaps. Record whether XML sitemaps are enabled and the sitemap URL shown by the View the XML sitemap link. Yoast documents this path in its XML sitemap settings guidance.

The master switch controls whether Yoast generates sitemaps. Other settings control which content groups can appear in search results and, as a result, in the sitemap. Check Content types for posts, pages, and public custom post types, which let WordPress sites use content types beyond posts and pages; Categories & tags for taxonomies, which group content; and Advanced settings for archive options, such as author archives. Record each relevant toggle and the client’s reason for its choice.

The Show [type] in search results? toggle controls whether a content group can appear in search results and in Yoast’s sitemap. When it is on, the group is eligible to appear in search results, and Yoast can include its URLs in the sitemap unless another setting excludes them. When it is off, Yoast excludes the group from search results and removes it from the sitemap. Yoast explains this relationship in its sitemap customization instructions.

The master XML sitemap switch affects all Yoast sitemaps; a content-group toggle affects only that group. WordPress also generates its own sitemap. Yoast says that turning on its sitemap feature disables the WordPress sitemap, while turning off Yoast’s feature leaves the WordPress sitemap enabled. Record which generator serves the site’s sitemap endpoint. Do not assume the site has no sitemap when Yoast’s switch is off. See Yoast’s Site features documentation.

Check the live sitemap index

Open the sitemap from Yoast’s View the XML sitemap link, then confirm that the public index at the site’s /sitemap_index.xml path loads. The index should link to individual sitemaps. Compare those links with the documented visibility choices, then open a few of the individual sitemaps and check that they contain the expected kinds of URLs. Yoast’s functional specification describes the index and its child sitemaps.

A browser check confirms that the files are accessible and lets you inspect their contents. Record any error or HTML response. Also record unexpected redirects and any wrong domain or protocol; do not mark the check successful. Caching, redirects, and other sitemap issues appear in Yoast’s troubleshooting guidance.

If the client grants access to Google Search Console, check the submitted sitemap_index.xml and record the reported status or processing errors. Search Console provides Google’s report of sitemap access and processing; a browser check does not show whether Googlebot fetched or processed the file. Sitemap submission helps Google discover URLs, but it does not guarantee crawling, indexing, or rankings, as Google explains in its sitemap guidance.

The settings screen also does not explain every missing URL. An individual URL may be absent because it has a noindex directive, a manual canonical URL pointing elsewhere, or a redirect. A noindex directive tells search engines not to include that page in search results. Record representative exceptions and check for custom Yoast filters, other sitemap plugins, or cache and CDN rules that affect the output.

Handoff checklist

Use this checklist to record the settings and checks for the next maintainer. Keep the notes with the handoff so they can compare the documented choices with the live sitemap.

• [ ] Record the production domain, WordPress version, and Yoast SEO version.
• [ ] Note whether Yoast XML sitemaps are enabled and identify the active sitemap generator.
• [ ] Record the visibility toggle and rationale for each relevant content type, taxonomy, and archive.
• [ ] Note individual noindex, canonical, or redirect exceptions and any sitemap-related customizations.
• [ ] Open /sitemap_index.xml, confirm the expected child sitemaps, and inspect representative child files.
• [ ] Record the check date and any errors, unexpected redirects, or stale output.
• [ ] If available, record the Google Search Console property and its submission status, along with any reported 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