XML Sitemap Audit: What Should and Should Not Be Included

An XML Sitemap Audit checks whether your sitemap contains the right URLs for Google to discover and index. A good sitemap should normally include live, indexable URLs that return a 200 status code and identify themselves as the preferred version. If your sitemap contains redirects, broken pages or noindex URLs, it needs reviewing. These entries can send mixed signals about which pages matter. This XML Sitemap Audit explains what to include, what to remove and how to check the results in Google Search Console.

What Should Be Included in an XML Sitemap?

A sitemap helps Google discover URLs on your website. It does not guarantee that those pages will appear in search results. For a UK service website, your sitemap may include:

homepage;
main service pages;
useful location pages;
blog posts.

URL type	Include?	Reason
Live, indexable service page	Yes	Important page with search value
Original blog post	Yes	Useful content intended for search
Valuable category page	Yes	Helps visitors explore a clear topic
Product page	Yes	Relevant page available to searchers
Canonical duplicate URL	No	Another URL is preferred
Redirected or deleted page	No	No longer a live content destination
noindex page	No	Not intended for Google Search

Only include pages intended for search. Do not add every URL WordPress generates.

Include Only Preferred Canonical URLs

A canonical URL is the version you want Google to treat as the main page. For example:

https://example.co.uk/roof-repairs/

https://example.co.uk/roof-repairs/?utm_source=email

If both show the same content, the clean URL should normally appear in the sitemap. The tracking version should not. Check that the canonical tag and sitemap both point to the same preferred URL. Our planned guide, Canonical URLs Explained for WordPress and Service Websites, covers cases where Google selects another canonical.

Include Pages That Return HTTP 200

A sitemap should generally list live pages returning 200 OK. If a service page returns 404, the URL is broken. If it returns 301, it points somewhere else. Neither should remain in the sitemap as the final content URL. Replace incorrect entries with their live, indexable destinations.

Use Accurate Last-Modified Dates

The optional <lastmod> field tells Google when a page was meaningfully updated. Use the real modification date when your website can provide it reliably. Do not set every URL to today’s date simply because the sitemap was regenerated. Google may ignore <lastmod> values that repeatedly fail to match actual page changes.

What Should Not Be Included in an XML Sitemap?

A proper XML Sitemap Audit should also identify URLs that do not belong in the file.

Redirected and Broken URLs

Remove URLs returning:

301;
302;
404;
410;
server errors.

For example, if:

/old-roof-service/

redirects to:

/roof-repairs/

include the replacement URL instead. Keep the redirect working where necessary. Removing the old URL from the sitemap does not replace the redirect.

Noindex and Blocked Pages

A page with a noindex instruction should not normally appear in a sitemap intended for Google indexing. Common examples include:

private account pages;
some thank-you pages;
deliberately excluded archives.

Also remove pages Google cannot access because of login restrictions or unsuitable crawl blocks. Do not use robots.txt as a replacement for noindex. If crawling is blocked, Google may not see the indexing instruction. Our Robots.txt vs Noindex guide explains the difference.

Duplicate URLs and Parameters

Avoid listing several URLs that display the same main content. Sorting parameters and tracking links may create extra versions of service or product pages. Review their canonical settings before removing them. Some filtered pages provide genuinely different content, so do not assume every parameter URL is a duplicate.

Low-Value Utility and Staging URLs

Login screens, internal search results and temporary staging pages normally do not belong in a public XML sitemap. However, do not remove a useful category or paginated page simply because it uses an archive template. Judge the page by its purpose and indexing settings.

How to Run an XML Sitemap Audit

Start by collecting your sitemap URLs and comparing them with what the website actually serves.

Step 1: Find Your Sitemap

Common WordPress sitemap locations include:

https://example.co.uk/wp-sitemap.xml

https://example.co.uk/sitemap_index.xml

Your website may use another address depending on the SEO plugin. Open the sitemap and confirm it loads correctly. A sitemap index may link to separate files for:

posts;
pages;
products;
categories.

A simple sitemap entry looks like this:

<?xml version=”1.0″ encoding=”UTF-8″?>

<url>

<loc>https://example.co.uk/roof-repairs/</loc>

</url>

</urlset>

The <loc> contains the page URL. The optional <lastmod> shows the last meaningful update date when known.

Step 2: Crawl the Sitemap URLs

Use Screaming Frog SEO Spider to download and crawl the sitemap URLs. In Mode > List, use the sitemap download option and enter its URL. Review:

status codes;
indexability;
canonical targets.

You can also crawl the whole website with sitemap discovery enabled. This gives a stronger comparison between sitemap URLs and internally linked pages.

Step 3: Find Incorrect Sitemap Entries

Filter the results to identify issues.

Audit finding	What it means	Recommended fix
301 redirect	Listed URL has moved	Replace with final destination
404 or 410	Listed URL is unavailable	Remove or replace if appropriate
noindex	Page is not intended for indexing	Remove from sitemap
Non-self canonical	Another URL is preferred	List preferred canonical URL
Blocked URL	Google may not access the page	Review access and indexing
Important page missing	Useful URL was not submitted	Add it if eligible

A missing sitemap entry is not always a problem. Only add the page when it is suitable for indexing.

Step 4: Find Sitemap-Only Pages

Compare your sitemap with a full website crawl. A page found in the sitemap but not through internal links may be orphaned. For example, a useful service guide may appear in the sitemap but have no links from:

homepage;
service pages;
blog.

Before calling it orphaned, check whether the crawl missed:

JavaScript links;
restricted pages;
areas outside the crawl scope.

If the page is genuinely orphaned, add relevant internal links. Our guide, How to Find and Fix Orphan Pages, covers this in more detail.

Step 5: Review Sitemap Limits and Dates

Google limits one uncompressed sitemap file to:

50 MB;
50,000 URLs.

Larger websites should split URLs across multiple sitemap files and use an index where needed. Check that sitemap files contain:

valid full URLs;
accurate modification dates.

A modest WordPress website does not need dozens of small sitemap files.

How to Audit Your Sitemap in Google Search Console

Google Search Console is an important part of an XML Sitemap Audit. Open Google Search Console. Choose your property and go to: Indexing > Sitemaps Select the submitted sitemap. The report shows whether Google could fetch and read it.

Understand Sitemap Submission Statuses

Search Console status	What it means	Next action
Success	Google read the sitemap	Review indexed versus excluded pages
Couldn’t fetch	Google could not retrieve it	Check URL, server access and blocks
Sitemap had X errors	Google found errors	Open details and fix reported issues

A Success status does not mean every listed URL is indexed. Open the Page indexing report and use the sitemap filter to review affected URLs.

Check Page Indexing Results

You may see statuses such as:

Page with redirect
Excluded by ‘noindex’ tag
Alternate page with proper canonical tag
Crawled – currently not indexed
Discovered – currently not indexed

These do not all mean the sitemap is broken. A valid submitted page may remain unindexed for reasons unrelated to the sitemap. For duplicate URLs, check which URL Google selected as canonical. Use URL Inspection for important pages before making changes.

XML Sitemap Audit Example

Imagine a London property-maintenance website with these sitemap entries. These are illustrative examples, not Wixdek client results.

Sitemap URL	Finding	Correct action
/roof-repairs/	Indexable, self-canonical, 200	Keep
/old-roofing/	301 to /roof-repairs/	Replace with destination
/thank-you/	noindex	Remove
/roof-repairs/?utm_source=email	Canonical to clean page	Remove duplicate
/services/	Indexable, 200, but absent	Add if suitable

The XML Sitemap Audit should record each problem and the final result after correction. Use the companion XML Sitemap Audit Checklist to record:

URLs;
findings;
fixes.

For real Wixdek evidence, the published guide should include an anonymised crawl export showing affected URLs, actions and verified outcomes.

How to Fix WordPress XML Sitemap Errors

WordPress may generate XML sitemaps through:

its built-in sitemap feature;
an SEO plugin.

If you use Yoast SEO, Rank Math or another sitemap tool, confirm which system currently creates the sitemap. Avoid running competing sitemap setups without a clear reason. Review plugin settings for excluded:

post types;
taxonomies;
individual pages.

After correcting entries, clear relevant caches and open the live sitemap again. Confirm that the XML reflects the new settings. If you make major changes, resubmit the sitemap in Search Console. Google also recrawls submitted sitemaps periodically, so routine changes do not always need manual resubmission. For wider WordPress indexing problems, our WordPress SEO services cover sitemap configuration and related technical settings.

XML Sitemap Audit Checklist

Use this XML Sitemap Audit Checklist before submitting or updating your sitemap.

The sitemap loads and contains valid XML.
Important indexable pages are included.
Listed URLs return successful responses.
Canonical tags match preferred sitemap URLs.
Redirects, broken pages and noindex URLs are excluded.
Staging, utility and unwanted parameter URLs are excluded.
Important orphan pages have suitable internal links.
<lastmod> values reflect genuine updates.
Sitemap limits are respected.
Search Console errors have been reviewed.

Frequently Asked Questions

What Is an XML Sitemap Audit?

An XML Sitemap Audit checks whether a sitemap contains the correct indexable URLs and excludes redirects, broken pages, duplicate URLs and noindex pages.

How Often Should You Run an XML Sitemap Audit?

Check it after major website changes and review it periodically. A six-month XML Sitemap Audit can be a useful starting point for many smaller websites.

Why Does Search Console Say My Sitemap Couldn’t Be Fetched?

The sitemap URL may be incorrect, blocked or temporarily unavailable. Open the sitemap, inspect the reported error and check server access before resubmitting.

Does an XML Sitemap Guarantee Indexing?

No. A sitemap helps Google discover URLs, but Google still decides whether each page should be indexed.

Need Help With an XML Sitemap Audit?

An incorrect sitemap can make it harder to identify which pages should appear in search. Wixdek helps UK businesses carry out an XML Sitemap Audit covering sitemap entries, canonical URLs, indexing rules and technical SEO issues. Explore our Technical SEO services to identify problems and plan the correct fixes.

Request a Technical SEO Audit

By Wixdek

Case Studies

Careers

Partners