Your XML sitemap should communicate the preferred URLs you want search engines to discover. For a normal business website, focus on canonical, indexable pages that return the intended content. Redirects, broken URLs and deliberately excluded pages should not form the core of that list.

Which URLs belong in an XML sitemap?
Start with useful service pages, genuine location pages, important company information and published articles. Then verify each URL’s status, canonical target and indexing directive. The fact that WordPress generated a URL does not mean it deserves search visibility.
Our technical SEO service reviews sitemap discovery alongside canonicals and indexing directives, so the submitted URLs support the intended website structure.
Google’s sitemap guidance recommends using the URLs you prefer as canonical versions. A sitemap is a discovery signal, not a promise that every listed page will be crawled or indexed.
A practical sitemap review
- Open the sitemap index and identify its child sitemaps.
- Sample URLs from each content type.
- Check that they use the correct HTTPS domain.
- Look for redirects, missing pages and staging addresses.
- Compare sitemap inclusion with intentional noindex settings.
- Confirm that recent published content appears as expected.
For an illustrative WordPress site, a theme migration might leave old service URLs redirecting to new paths. The new canonical URLs belong in the current sitemap. Internal links should also point directly to them rather than relying on redirects.
What about categories, tags and attachments?
Decide whether each archive provides a useful search destination. An empty tag archive or media attachment page may not need indexing. Configure the responsible WordPress component consistently instead of editing a generated XML file by hand and losing the change later.
Keep future scheduled posts out of the public sitemap until publication. A public sitemap should not reveal draft content or link readers to unavailable articles.
After submitting the sitemap
Review processing status in Search Console and investigate meaningful errors. Compare important intended pages with the Page Indexing report. If a URL is excluded, diagnose its reason; repeatedly submitting the same file is not a substitute for fixing access, content or canonical conflicts.
Common questions
Does every page need a sitemap entry?
No. A sitemap should reflect useful preferred URLs, and search engines can discover pages through links too.
Can I fake recent modification dates?
Use accurate dates that reflect meaningful content changes. A misleading update timestamp does not improve the page.
Should the sitemap replace internal linking?
No. Visitors and crawlers still need a clear, browsable structure.
Put the next step into practice
Need help applying this to your website? Explore technical SEO services, or request a focused website review. Tell us what you want to improve and which page or process is involved. We will discuss the scope before recommending work.
Continue with the related planning guide for broader context.
Reference: Google: Build and submit a sitemap. Practical examples in this article are illustrative, not client results. Platform features and guidance can change.

