I want you to do something before you read the rest of this.
Open a new browser tab and type your site’s URL, followed by /sitemap.xml or /sitemap_index.xml. Look at what comes back. If you’re on WordPress, the sitemap is almost certainly live.
Now scroll through it. Not the XML structure — just the URLs. What you’re looking at is a list of every page on your site that you’re asking Google to care about.
Is it what you intended to ask?
What the sitemap reveals
The XML sitemap is the most honest document on your site because nobody writes it deliberately. It’s generated automatically from your publishing decisions, which means it reflects what you’ve actually been doing rather than what you planned to do or what you tell clients you do.
A site with a clear content strategy has a sitemap that reflects that strategy. The URLs cluster into recognizable topical areas. The pillar content is there. The spoke content connects to it. The site sections make sense together.
A site without a clear content strategy has a sitemap that looks like a five-year archive of whatever seemed worth publishing at the time. Every tag archive that was automatically generated. Every thin placeholder page that was meant to be temporary and never was. Every post from the period when the editorial focus was different.
The categories of sitemap problems
There are four things a sitemap audit reliably finds:
Pages that shouldn’t be indexed.
Paginated archives, tag pages, author archives, search result pages, admin pages that somehow got indexed — these pages are taking up space in your sitemap and in Google’s crawl allocation without providing any value. They signal to Google that you don’t have a clear sense of what your content is for. How your sitemap reveals where your crawl budget is being wasted is one of the most actionable things a sitemap audit produces — and most teams never look.
Thin or outdated content you forgot about.
The post from 2018 that was 300 words and exists only because someone thought “we should post something this week.” The seasonal content from three years ago that’s now wrong. The service page for a service you no longer offer. The sitemap shows you all of it.
The content technical debt audit trail.
URL patterns from previous site structures, redirected URLs that were left in the sitemap, pages that moved and were never cleaned up. The sitemap often preserves the archaeological record of everything that’s ever been on the site.
The topical spread.
If you think you’re a content strategy site, does the URL pattern reflect that? Are a significant portion of your indexed pages about content strategy, or are they scattered across subjects that don’t reinforce each other?
Why this is a content strategy document
The difference between a content plan and a content strategy is, in part, the difference between knowing what you published and knowing what you built. The sitemap is the record of what you built — or didn’t build.
A coherent sitemap is the output of deliberate content strategy: a decision about what this site is for, what topics it covers, what pages deserve to be indexed, and what pages aren’t worth Google’s attention. The content audit often starts with the sitemap because it’s the fastest way to see the scope of the problem.
The fix isn’t technical, or not mostly technical. The technical fix — removing pages from the sitemap, adding noindex tags, redirecting orphaned URLs — is straightforward. The work is the editorial decisions that precede it: what stays, what goes, what gets updated before it can stay. The sitemap is also how to use your sitemap to identify consolidation candidates — the posts competing for the same keyword become visible the moment you sort URLs by topic cluster.
What a healthy sitemap looks like
A healthy sitemap has URLs that are predominantly valuable, indexed pages. No paginated archives unless there’s a specific reason. No tag pages unless you’ve built them out into genuinely useful topic hubs. No thin content that you’re embarrassed to look at.
It has a pattern. The URLs cluster into a recognizable structure that reflects your expertise. Someone looking only at the sitemap should be able to say: this is a site about X, and it has a coherent body of content around Y and Z sub-topics.
That pattern is the architectural expression of your content strategy. If the pattern isn’t there, the strategy isn’t really there — it exists as intent, maybe as a document, but not as a built thing that Google can read.
Just stopping publication to do this audit — to actually look at what you’ve built rather than continuing to add to it — is sometimes the most strategic move available.
The sitemap is waiting. Go look.
An XML sitemap is a structured file that lists your website’s URLs and tells search engines which pages exist and should be crawled. It’s not a guarantee of indexing — Google decides whether to index each URL independently — but it’s the clearest signal you can send about what you want Google to prioritize. On WordPress with Yoast SEO, the sitemap is generated automatically at /sitemap_index.xml.
Try yoursite.com/sitemap.xml or yoursite.com/sitemap_index.xml. With Yoast on WordPress it’s at /sitemap_index.xml by default. You can also find it in Google Search Console under Sitemaps — if it’s been submitted, it will be listed there with status. If neither URL returns a valid sitemap, check your SEO plugin settings.
Remove: paginated archive pages, tag and category pages with fewer than three to five posts, pages marked noindex in Yoast, thin or outdated content you wouldn’t actively promote, and redirect URLs. What remains should be the pages you’d be proud to submit to Google as your best content. If you’d be embarrassed to share a URL with a prospective client, it probably shouldn’t be in your sitemap.
The sitemap shapes Google’s crawl priorities. A clean sitemap focused on your best content directs Googlebot to the pages worth ranking. A bloated sitemap full of thin archive pages signals that the site lacks editorial standards. Submitting your sitemap to GSC after significant publishing or architecture changes also accelerates how quickly new or updated content gets indexed — important at a 2–3 posts per week publishing cadence.
Jacob Clifton is the principal of Clifton Creative, an editorial strategy consultancy based in Austin, Texas. He spent fourteen years as a flagship staff writer at Television Without Pity and has written for Tor.com, Vulture, BuzzFeed News, and the Austin Chronicle.
For inquiries:
jacob@cliftoncreative.agency · Book a discovery call
This post is part of the Clifton Creative guide to SEO for content teams.