New

Sitemap Audit

Review a sitemap and see combined findings ranked by severity, from blocked responses and broken XML down to duplicates and old dates.

Sitemap input

Findings are ordered from errors, to warnings, to notes.

In practice

What fails a Sitemap Audit pass

MistakeWhat happens
Sitemap Audit: Mixing this result with another sitemap toolFixing notes before errors. An ancient lastmod can wait. An HTML challenge page cannot. (Sitemap Audit, mistake 1.)
Sitemap Audit: Ignoring a truncated listSitemap Audit stops at the published caps. A truncated note means you do not have the full file. (Sitemap Audit, mistake 2.)
Sitemap Audit: Sending a private URLLocalhost, link-local, private ranges, and the metadata address are blocked before a socket is opened. (Sitemap Audit, mistake 3.)
Sitemap Audit: Treating HTML as XMLAn HTML page or a challenge interstitial is reported as not a sitemap. Fix the URL or the firewall rule, then run the check again. (Sitemap Audit, mistake 4.)

On this tool

Before you trust Sitemap Audit

  • The input for Sitemap Audit was XML or a public sitemap URL. (Sitemap Audit, check 1.)
  • A truncated note was read before the list was treated as complete. (Sitemap Audit, check 2.)
  • HTML or a challenge page was not accepted as a sitemap. (Sitemap Audit, check 3.)
  • The copied result matches findings ranked by severity, not a different sitemap report. (Sitemap Audit, check 4.)
  • Generated files were published by you, not by this page. (Sitemap Audit, check 5.)

Read this

A result Sitemap Audit should show

Input

Paste a urlset that contains https://example.com/docs/start once and the same address a second time. Sitemap Audit keeps one stored page and records the duplicate. Fetching https://example.com/sitemap.xml instead of pasting uses the same parser after the download. (Sitemap Audit, example 1.)

What you should see

If https://example.com/sitemap.xml is a sitemap index and https://example.com/sitemaps/posts.xml is the first child, a URL fetch can read that child until the depth and child caps. A paste of the index lists https://example.com/sitemaps/posts.xml and does not download it until you fetch the index URL. (Sitemap Audit, example 2.)

Detail

How to read a Sitemap Audit report

Sitemap Audit produces findings ranked by severity. The audit combines the structural errors, fetch problems, duplicate locs, and date warnings into one list. Errors sit above warnings, and warnings sit above notes. You can paste XML into the box, or you can enter a public sitemap URL and let the server fetch it. A pasted urlset is parsed on the server without a second copy of the parser in the browser. The form stays near the top of the page, under the single title. (Sitemap Audit, guide 1.)

Use https://example.com/sitemap.xml as the file you are checking and https://example.com/docs/start as a page address you expect to see or not see, depending on the job. Start with the first error. A blocked host, a non-sitemap body, or broken nesting stops the file from being useful. A duplicate loc is a warning and does not erase the first copy. If the file is a sitemap index, child documents such as https://example.com/sitemaps/posts.xml are fetched only when you supplied the index URL, only while the depth is within 2, and only until 20 child sitemap requests have been made. (Sitemap Audit, guide 2.)

Sitemap Audit shares one fetcher with the other sitemap tools. The fetcher allows http and https only. It rejects file, gopher, and data URLs, then blocks localhost, loopback, link-local, private ranges, CGNAT space, and the cloud metadata address before it opens a socket. DNS answers are checked before the connection, and a redirect is checked again. A redirect loop is reported instead of being followed forever. Three hops is the maximum. (Sitemap Audit, guide 3.)

Large files are cut at 5 MB, and the stored page list stops at 5,000 URLs. Gzip responses and addresses that end in .gz are decompressed before parsing. A DOCTYPE or an entity declaration is rejected so the parser cannot expand an external entity. An HTML document or a Cloudflare challenge body is reported as not a sitemap. The raw response body is not written to the log. (Sitemap Audit, guide 4.)

When a URL must be fetched, the page sends the job to the server and shows a short progress line while it polls. Small pastes return immediately with the same result shape: source URL, index or urlset, child sitemaps, page rows, errors, duplicates, redirect hops, status, truncated flag, and counts. Repeat fetches of the same normalized URL can reuse a finished parse for 10 minutes. Jobs sit in a file folder so more than one server process can see them, and they expire after 30 minutes. (Sitemap Audit, guide 5.)

Fixing notes before errors. An ancient lastmod can wait. An HTML challenge page cannot. After you read that distinction, look at the severity of any finding. An error means the document or the fetch failed the check this page is responsible for. A warning, such as a duplicate loc or a truncated file, means the rest of the result is still usable. A note explains a cap, a paste that did not download child files, or a sample crawl. (Sitemap Audit, guide 6.)

A concrete pass through Sitemap Audit starts with https://example.com/sitemap.xml. If that address is an index whose first child is https://example.com/sitemaps/posts.xml, the file list and the page list answer different questions. The page address https://example.com/docs/start belongs in the page list only when a urlset contains it. Keep the two lists apart when you copy them into a spreadsheet or a ticket. (Sitemap Audit, guide 7.)

The result panel uses the same dark block as the other tools on this site. Copy is there when a text result is useful. A download button appears only for a file this page actually builds, such as CSV, XLSX, XML, or llms.txt. Sitemap Audit does not add a second title to the page, and it does not restyle the tools around it. (Sitemap Audit, guide 8.)

Take Sitemap Audit as one step. The next page in this set is Sitemap Validator, which answers a different question about the same sitemap. Sitemap Lastmod Checker is the other close check. Finish the reading on this page before you switch, so you do not mix findings ranked by severity with a different report. (Sitemap Audit, guide 9.)

Where Sitemap Audit fits

Sitemap Audit is the iSkills page for findings ranked by severity. The audit combines the structural errors, fetch problems, duplicate locs, and date warnings into one list. Errors sit above warnings, and warnings sit above notes. Paste XML when you already have the file, or enter a public http or https sitemap URL when you want the server to fetch it within the published caps.

The caps are part of the result, not a hidden failure. Sitemap Audit stores at most 5,000 page URLs, fetches at most 20 child sitemaps, and stops nested indexes at depth 2. A truncated flag and a note tell you when the list is incomplete.

Sitemap Audit in order

Paste sitemap XML or enter the sitemap URL. For Sitemap Audit, the address to try first is https://example.com/sitemap.xml. (Sitemap Audit, step 1.)

Run the check. A short progress line stays on screen while a fetch is in a server job. (Sitemap Audit, step 2.)

Read findings ranked by severity. Confirm whether the result says the list was truncated. (Sitemap Audit, step 3.)

Copy the text you need, or download the file when this page offers one. Publish any generated XML yourself. (Sitemap Audit, step 4.)

What Sitemap Audit returns

  • Sitemap Audit shows findings ranked by severity from one shared parse, so the XML rules match the other sitemap tools. (Sitemap Audit, result 1.)
  • A paste and a fetched URL return the same kind of result, including errors, duplicates, and counts. (Sitemap Audit, result 2.)
  • Private hosts, entity declarations, and oversized responses are refused before they can be used as a proxy. (Sitemap Audit, result 3.)

Terms used by Sitemap Audit

urlset
The sitemap root that lists page URLs. Sitemap Audit reads it with the shared parser. (Sitemap Audit, urlset.)
sitemap index
A sitemap that lists other sitemap files. Nested indexes are fetched only to depth 2. (Sitemap Audit, sitemap index.)
loc
The address element. Page locs and sitemap locs are kept in different lists. (Sitemap Audit, loc.)
truncated
The flag that says a byte, URL, child, depth, or time cap stopped the result early. (Sitemap Audit, truncated.)
findings ranked by severity
The specific report Sitemap Audit is built to show from the shared parse. (Sitemap Audit, findings ranked by severity.)

Detail

The check after Sitemap Audit

If Sitemap Audit is clean, Sitemap Validator is the sensible next check on that input.

On this tool

Sitemap Audit questions

What does Sitemap Audit return?

Sitemap Audit returns findings ranked by severity. Start with the first error. A blocked host, a non-sitemap body, or broken nesting stops the file from being useful. A duplicate loc is a warning and does not erase the first copy. (Sitemap Audit, What does Sitemap Audit return?.)

Does Sitemap Audit fetch a pasted file?

A paste is parsed without a download. A sitemap URL is fetched on the server. Child files inside a pasted index are listed and are not downloaded until you fetch the index URL. (Sitemap Audit, Does Sitemap Audit fetch a pasted file?.)

What will Sitemap Audit refuse?

It refuses non-http schemes, private and metadata addresses, DOCTYPE and entity declarations, responses over 5 MB, and HTML that is not a sitemap. (Sitemap Audit, What will Sitemap Audit refuse?.)

How large a file can Sitemap Audit store?

The stored page list stops at 5,000 URLs. Child sitemap fetches stop at 20, nested indexes stop at depth 2, and redirects stop at 3. The screen says when the result is truncated. (Sitemap Audit, How large a file can Sitemap Audit store?.)

WhatsApp Advisor
Enroll Now