Short answer: Site SEO AI Audit reads your XML sitemap and compares it with the pages it reaches by links. It warns when there is no sitemap, when the sitemap lists pages that do not work, such as redirected, broken or noindex addresses, and when listed pages are not linked from anywhere. Create a sitemap if it is missing, keep only live, indexable addresses in it, link orphan pages from your site and run a new check to confirm that the warnings have gone.
A sitemap is a list of the pages you want search engines to know about. It sounds like a minor technical file, yet it is one of the few places where you speak directly to crawlers. A good sitemap helps new and deep pages get discovered. A bad one wastes crawling on addresses that lead nowhere and teaches search engines that your list is not reliable. The audit treats the sitemap as a source of truth to compare against the site itself, which is why it can find problems that neither the sitemap nor the site shows alone. This article explains each check and the repairs.
How the audit uses your sitemap
The crawler starts from your home page and from the sitemap. It reads robots.txt to find the sitemap address, and it also reads sitemap index files that point to several sitemaps. Then it does two things. It crawls the addresses in the sitemap together with the ones it finds through links. And it compares the two sets: addresses in the sitemap that no page links to are orphans, and addresses in the sitemap that fail or are hidden from search are sitemap problems.
The page list in the report has a column that shows whether each address is in the sitemap, and the key figures at the top show how many URLs the sitemap lists. Use both: the figure tells you the size of the list, and the column helps you find pages that should be in it but are not.
The checks that involve the sitemap
| Check | Severity | What it says |
|---|---|---|
| No XML sitemap found | Aviso | A sitemap helps search engines find every page, especially new and deep ones |
| Sitemap lists pages that do not work | Aviso | The sitemap should list only live, indexable pages |
| Orphan pages (no internal links) | Aviso | Pages in the sitemap that nothing links to get little authority |
| No robots.txt | Notice | Robots.txt is where you point search engines to the sitemap |
All four sit in the Crawl and index area, which carries the biggest share of the score, twenty-five percent. They are also among the most straightforward items to fix, because the sitemap is usually produced by one plugin or one setting.
No sitemap found
If the crawler cannot find a sitemap, the report says so. The card advises creating a file at /sitemap.xml and adding it to robots.txt and to Search Console. On WordPress, your SEO plugin creates one: open its settings and enable the XML sitemaps option. On other platforms, look for a sitemap setting or an extension. After enabling it, open the address in a browser and make sure you see a list of addresses.
Then tell the crawlers where it is. Add a line to robots.txt that gives the sitemap address, and submit it in Search Console. That is also the moment to check the sibling notice “No robots.txt”: a robots.txt file is not an error to be without, but it is the natural place to point to the sitemap. The guide to XML sitemap best practices lists what to include and how to structure it.
A sitemap that lists broken pages
This check fires when the sitemap contains addresses that redirect, return errors or carry a noindex instruction. The card’s reasoning is simple: the sitemap should list only live, indexable pages, and broken ones waste crawl budget and trust. A sitemap is a promise: these are the pages I want you to index. Listing a page that is hidden from search or leads to an error breaks that promise.
Typical causes:
- Deleted pages. The page is gone, but the sitemap generator still has it, often because of a cached copy of the sitemap.
- Redirected pages. Old addresses stay in the file after a move. The sitemap should list the new address instead.
- Noindex pages. Thank-you pages, internal search results or tag archives set to noindex but still included by a plugin.
- Wrong protocol or host. The sitemap lists http or www addresses that redirect to the real version.
- Staging leftovers. Addresses from a development copy that were never replaced.
The fix is to remove these addresses. In most plugins, that means excluding the content type, the taxonomy or the single page from the sitemap, and clearing the sitemap cache. When a page is redirected, make sure the target is in the sitemap rather than the old address. The article on sitemap errors in Search Console explains how search engines report the same problems.
Orphans and missing pages
The sitemap also exposes the opposite problem. Pages that are in the sitemap but not linked from any page of the site are orphans, and the report lists them as a warning. Add contextual links, category links or menu items, or remove the page from the sitemap if it should not be there. Our guide to orphan and deep pages in your report shows how to decide for each page.
Similarly, look for important pages that are missing from the sitemap. Open the page list, use the search box to see a section and read the sitemap column. If key pages show that they are not listed, find out why: a plugin setting, a noindex, a canonical to another address or a filter that excludes a content type.
Keep the file accurate
Three details make a sitemap more useful. Use accurate last-modified dates, which tell crawlers when a page really changed; the guide to lastmod accuracy explains why wrong dates reduce trust. Use the canonical form of each address, with the right protocol, host and trailing slash. And split large sets into several sitemaps with an index file, as described in the article on sitemap index files, which becomes important when a site has thousands of pages.
For multilingual sites, sitemaps can also carry hreflang annotations. If you use that method, the Languages area of the report checks that the annotations are complete and that the targets work. The article on multilingual XML sitemaps shows the structure.
A worked example
A local news site has about 1,200 pages and a sitemap with 1,540 addresses. The report says that the sitemap lists pages that do not work, and the affected list shows 340 entries. A quick look reveals the pattern. About 200 are tag archive pages set to noindex, 90 are old articles that were merged and now redirect, and 50 are author pages that were removed. The owner excludes tags from the sitemap in the plugin settings, regenerates the file and lets the plugin skip redirected posts. The sitemap drops to 1,200 addresses, each live and indexable, and the warning disappears at the next check. Search Console shows fewer excluded pages a few weeks later, which confirms the cleaner picture.
Mistakes to avoid
- Listing everything the CMS has. The sitemap is not a database dump; it is a selection of pages you want found.
- Forgetting to clear the cache. Many plugins and CDNs keep the old file for hours.
- Using several sitemaps from several plugins. Two generators can produce overlapping or conflicting lists. Keep one.
- Setting every last-modified date to today. If every page always looks new, crawlers stop trusting the dates.
- Blocking the sitemap in robots.txt. The file must be readable by crawlers.
Step by step
- Open the report and check the figure for URLs in the sitemap. Does it match what you expect?
- Open the affected lists for “Sitemap lists pages that do not work” and read the status of each address.
- Exclude redirects, errors and noindex pages in your sitemap plugin, and clear the cache.
- Add or fix links for orphan pages, or remove them from the sitemap.
- Check that the sitemap is named in robots.txt and submitted in Search Console.
- Run a new check. Starter, Pro and Agency include re-checks. The sitemap warnings should be gone.
If you want to see what your own sitemap looks like to a crawler, create a free account and run your check, then choose a plan on the pricing page to unlock the lists.
Related reading
- XML Sitemap Best Practices: What to Include and Leave Out
- Sitemap Errors in Search Console: What They Mean and Fixes
- Sitemap lastmod: How to Keep Last-Modified Dates Accurate
The bottom line
A sitemap should be a short, honest list of live, indexable pages. Create one if it is missing, remove redirected, broken and noindex addresses, link or drop orphans and confirm with a new check.
FAQ
Do I need an XML sitemap?
The report treats a missing sitemap as a warning, because a sitemap helps search engines find every page, especially new and deep ones.
What should a sitemap contain?
Only live, indexable pages. Redirected, broken and noindex addresses should be removed.
Where do I tell search engines about my sitemap?
In robots.txt, with a sitemap line, and in Search Console.
Why does the report list orphan pages?
Because it compares the sitemap with the pages reached through links. A page listed but not linked gets little authority.
How do I see which pages are in the sitemap?
The page list in the report has a sitemap column, and the key figures show the number of URLs listed.


