Sitemap Cannibalization Checker

Sitemap Cannibalization Checker produces groups of near-duplicate slugs. The last path segment is split into words. A trailing plural s is folded, and the words are sorted, so seo-courses and course-seo land in one group. The same path with a different query string is marked as query variants. 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 Cannibalization Checker, guide 1.)

Use https://example.com/seo-course as the file you are checking and https://example.com/seo-course?ref=1 as a page address you expect to see or not see, depending on the job. A group of one is not shown. Titles appear only when you paste them, or when you ask for up to 20 title tags. The tool does not fetch a title for every URL. If the file is a sitemap index, child documents such as https://example.com/seo-courses 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 Cannibalization Checker, guide 2.)

Sitemap Cannibalization Checker 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 Cannibalization Checker, 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 Cannibalization Checker, 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 Cannibalization Checker, guide 5.)

Reading a slug group as proof that two pages compete. The same words are a hint. The titles and the page intent still have to be checked by hand. 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 Cannibalization Checker, guide 6.)

A concrete pass through Sitemap Cannibalization Checker starts with https://example.com/seo-course. If that address is an index whose first child is https://example.com/seo-courses, the file list and the page list answer different questions. The page address https://example.com/seo-course?ref=1 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 Cannibalization Checker, 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 Cannibalization Checker does not add a second title to the page, and it does not restyle the tools around it. (Sitemap Cannibalization Checker, guide 8.)

Take Sitemap Cannibalization Checker as one step. The next page in this set is Sitemap Topical Map, which answers a different question about the same sitemap. Sitemap Compare is the other close check. Finish the reading on this page before you switch, so you do not mix groups of near-duplicate slugs with a different report. (Sitemap Cannibalization Checker, guide 9.)