Best AI Tools

Sitemap and internal-link discovery checker

Compare URLs listed in an XML sitemap with destination URLs in an internal-link crawl export. The local checker highlights sitemap URLs with no matching link in the supplied crawl data and linked destinations absent from the sitemap. These are coverage differences to review; they do not show what Google has discovered or guarantee crawling or indexing.

Compare your URL lists

Paste one XML sitemap (a <urlset>, not a sitemap index) and a CSV crawl export with source-page and destination-page columns. Common crawler headers such as Source/Destination or From/To are recognized. Processing stays in this browser tab.

How do I compare sitemap and internal-link coverage?

  1. Export the current XML sitemap as a <urlset>. For a sitemap index, use each child URL set separately; this checker does not fetch or expand sitemap indexes.
  2. Run a crawl that records source and destination URLs for internal links. Export those link edges as CSV and confirm the export covers the pages and links you intend to review.
  3. Paste the XML and CSV, then compare. A sitemap URL with zero incoming links in the supplied export is a candidate to inspect for navigation and crawl-path coverage. A linked destination absent from the sitemap may be intentionally excluded, canonicalized elsewhere, or missing by mistake.
  4. Open the source page for a link candidate and confirm it is a normal HTML anchor with an href, points to the intended canonical URL, and has useful surrounding context. Check redirects, noindex rules, robots access, and crawl depth using your own crawler and site data.
  5. Prioritize important pages that are neither linked in the crawl export nor present in the sitemap, and verify intended inclusion with your site owner. Record intentional exclusions rather than adding every discovered URL automatically.

What does the comparison tell me?

The checker normalizes URLs by resolving them as HTTP or HTTPS URLs, lowercasing the host, removing fragments and default ports, and preserving path, trailing slash, and query string. It reports sitemap duplicates after that normalization. If the same canonical page appears under different paths, query strings, or host aliases, those remain separate until you review the site’s redirects and canonical declarations.

“No incoming links” means only that the URL did not appear as a destination in the crawl export you pasted. A partial crawl, blocked page, JavaScript-only navigation, export setting, or different URL form can hide links. The result is not a Google discovery report, Page indexing status, indexability test, or proof that a page is orphaned.

Google documents both known-page links and sitemaps as ways URLs can be found. Its link guidance recommends crawlable anchor elements with an href and says important pages should have at least one internal link. Neither a sitemap entry nor an internal link guarantees that Google will crawl or index a URL.

Frequently asked questions

Does a sitemap-only URL mean Google has not found the page?

No. This tool compares two lists supplied by you; Google may know the URL through a sitemap, links outside the export, or other sources. Use Search Console URL Inspection and Page indexing reports for Google’s observations.

Should every linked URL be added to the sitemap?

No. A linked destination may be a redirect, duplicate, utility page, or another URL you do not intend to have indexed. Review canonical and indexing intent before changing the sitemap.

Does a linked sitemap URL mean Google will index it?

No. Google says links help it find pages and sitemaps help it discover URLs, but discovery does not guarantee crawling or indexing.

Does the tool upload or save my data?

No. The comparison runs in this page, does not fetch your site or contact Google, and only creates a CSV download when you request it. Your pasted data is lost when you leave or reload.

Sources · checked November 3, 2026

Related: record dated URL Inspection observations, understand discovered versus crawled statuses, and diagnose a sitemap fetch report.

Methodology and limitations

This browser-only helper parses one XML sitemap urlset and a CSV export containing source and destination URLs. It normalizes HTTP(S) URLs by lowercasing hosts, removing fragments and default ports, and preserving paths, trailing slashes, and query strings. It reports URL-set differences only in the supplied files; it does not crawl a site, contact Google, verify crawlability, infer orphan status, or predict indexing. Google Search Central documentation and the cited Community question were checked November 3, 2026; the community post is qualitative evidence of one question, not prevalence or search-volume data.

Affiliate placeholder {{AFF_TOOLNAME}} — referral link not configured.