Found in Sitemap
Found in Sitemap
What We Do
Examples of How Found in Sitemap Data Can Be Used
- Example 1: Identify pages that are missing from a sitemap
- Example 2: identify resources that should be removed from a sitemap
Benefits of Sitemap Data
If the URL is listed in any XML sitemap.
Raptor’s web crawler collects encoding data for every accessible resource on a site.
Within the column for ‘Found in Sitemap’, there three values that can be returned for this which are as follows:
URL is found in an XML sitemap
URL is not found in an XML sitemap
If the URL is inaccessible
A basic but highly useful check, we look to see if this URL is listed in an XML sitemap. Returning a classic ‘True’ or ‘False’ response for each field in the column. This checks for nothing except that stated previously, regardless of whether the page is any of the following:
- Accessible / Status Code
- Based on file type
If there are no sitemaps, or non-that we could find, we state “No Sitemaps”.
The examples below show how Found in Sitemap data can be used for SEO.
You can simply filter this column for ‘false’ to find any page that is not listed in a sitemap, when combined with things like status 200, HTML/Text pages, Page is Canonical; you can quickly see what pages, if any, are missing.
Using similar filters to those above such as listed in site and any of the below:
- Non-canonical page
- Non-indexable page
- Has a status other than 200
- Is the wrong file type
The list of guides below might be useful if you are analysing sitemap data and want to know more about it:
Related column headers in Raptor website crawler reports for this topic are as follows:
There are several main benefits to analysing sitemap data, some of the more popular ones we’ve listed below:
- Identify what pages are listed in xml sitemaps
- Analyse xml sitemaps
- Identify xml sitemaps
- Identify pages that should be removed from a sitemap
- Identify pages missing from a sitemap
No Credit Card Required - Free 30-Day Trial. Identify Sitemap Issues Quickly & Easily