An XML sitemap is most useful when it reflects the URLs you actually want search engines to discover and consider for indexing. Treating it as a dump of every public WordPress URL weakens that signal and makes troubleshooting harder.
Quick Answer
Include canonical, indexable URLs that matter to the site. Exclude redirects, 404s, noindex pages, duplicates, test content, and archives you intentionally do not want indexed. A sitemap does not guarantee indexing; it is a discovery aid.
Make the Sitemap Match Your Indexing Intent
Posts and pages that are public, canonical and useful normally belong. If an archive is intentionally noindexed, it should not simultaneously appear in the sitemap as though it were a preferred indexable URL.
Consistency makes Search Console reports easier to interpret.
Do Not Use the Sitemap as a Fix for Weak Internal Linking
A sitemap can help discovery, but important pages should also be reachable through the site’s navigation or contextual links. An orphan page in a sitemap is still an orphan in the user experience.
Use the sitemap as a supplement to architecture, not a substitute for it.
Recheck After Plugin or Taxonomy Changes
SEO plugins can regenerate sitemap indexes automatically when you add post types or change taxonomy settings. Review the actual XML output after configuration changes rather than assuming the old exclusions still apply.
Sitemap Audit
- Open the sitemap index and each child sitemap.
- Spot-check URLs for 200 responses and self-consistent canonicals.
- Remove noindex and redirected URLs.
- Confirm important content types are included.
- Submit the sitemap in Search Console and monitor processing errors.
Example: A Sitemap That Looks Clean but Is Not
Imagine a WordPress sitemap lists 180 URLs. Thirty are redirects from an old structure, twenty are tag archives you intentionally noindex, and a handful are staging or test pages that should never have become public. The file may still be valid XML, but it no longer represents your preferred indexable content set.
A better sitemap would contain the canonical destination URLs, important posts and pages, and only the archive types you actually want search engines to consider. That makes Search Console coverage easier to interpret because the sitemap is closer to a declaration of indexing intent.
How to Audit a Sitemap Efficiently
You do not need to inspect hundreds of URLs by hand. Sample each content type first: a few posts, pages, categories, tags, author archives, and custom post types. Then compare the sitemap against a crawl or CMS export to find redirects, noindex pages and missing important URLs at scale.
After changing sitemap settings, open the generated XML directly and verify the result before resubmitting. The plugin dashboard is configuration; the XML file is the output that search engines actually receive.
Common Mistakes
Common sitemap mistakes include listing redirected URLs, assuming submission guarantees indexing, including private or thin archives, and ignoring stale URLs after large migrations.
Watch the Topic in Context
How Google Search Crawls Pages
Google’s crawling overview explains where sitemaps fit into URL discovery and why they do not replace crawlable site links.
Watch on YouTube ↗ · Google Search Central