Knowledge Module

A 200 Is Not a Verdict: Finding Broken Links and Soft 404s in a Sitemap

Find broken links, soft 404s, and bad redirects in an XML sitemap. Sitemap Link Checker is a free, open source Chrome extension that checks every URL from inside your browser, so it works on staging sites and behind bot protection.

Updated
Nov 19, 2026
Version
v0.1.0
Read
5 min
By
Summit ML

An XML sitemap promises that every page it lists exists. The tools that could check it are locked out of the sites where it matters, and fooled by the pages that are most broken.

Audience
Frontend Engineers · QA Engineers · SEO and Content Teams · Teams launching or migrating a site

The status code is what the server says. The page is what the visitor gets.

Why broken links in a sitemap go unnoticed

Before a launch or a site migration, someone should confirm that every URL in the sitemap lands on a real page. That job goes to a crawler or a broken link checker, and both get two things wrong.

It is not you. Staging sits behind a password, production behind bot protection, the account area behind a sign-in. A crawler is stopped at the door. Your browser is already through it.

It trusts the status code. Many sites answer 200 OK for a page that only says "we can't find that." Search engines call these soft 404s, and a tool that looks only for 404 errors never sees them. Here are four links from one run. A check that reads only the status would pass three of them.

LinkStatusWhat the page showsVerdict
/luggage/spinner-2019404The not-found pageNot found
/backpacks/rolling200"We cannot find the product"Not found
/sale/clearance200A category with "products (0)"No results
/collections/summer200The home page, after a redirectRedirect to home

Sitemap Link Checker is a Chrome extension that runs the check inside your browser, on the site you are testing, and reads each page the way a visitor would. It is free, open source, and MIT licensed.

The results panel: every link in the sitemap with its result, status code, response time, page title and the reason

Check a sitemap for broken links

Add it from the Chrome Web Store. It also installs in Edge. Then:

  1. Open the site you want to test and click the Sitemap Link Checker button.
  2. Click Load sitemap. The checker finds sitemap.xml from the page or the site's robots.txt.
  3. If it is a sitemap index, tick the sitemap files to check and click Check links.
  4. Filter the results to the problems and click Download CSV.

You can also paste a list of URLs instead of loading a sitemap.

Every link gets a verdict, with its status code, response time, page title, and the reason.

ResultMeaning
OKThe link opened a normal page.
RedirectThe link redirects to a different URL, which is shown.
Redirect to homeThe link redirects to the home page. The page is usually gone.
Not foundA 404 or 410, or the site's not-found page under another status.
No resultsA search or category page that lists nothing.
ErrorThe site returned an error, or the page shows one.
Blocked, Sign-in neededThe site refused the link. It is not counted as broken.
WarningThe page loaded but should not be in the sitemap: it is marked noindex, or its canonical URL points elsewhere.

Filter by result, by status code, or by search. After a fix, Recheck problems checks only the links that were not OK.

The status code menu open, with 404 and 410 ticked and the results narrowed to three links

How it finds soft 404s

The first rule that matches wins.

  1. The status code. 404 and 410 are Not found. 500 and above are Errors.
  2. The words on the page. Phrases such as "we cannot find the product" or "products (0)" mark a page that answered 200 OK and is not really there. The list is under Options, and you can add your own site's wording.
  3. The site's own not-found page. Before a run, the checker asks for an address that cannot exist and remembers what comes back. Any link that returns the same page is Not found.
  4. The title and heading. "404", "not found", or "something went wrong" in either one.

Sign-ins, passwords, and bot protection

The checker uses your browser's session. It never asks for a password and never stores one.

If the site starts refusing links partway through, they are reported as Blocked, not as broken. After three in a row the run pauses. Open a blocked link, pass the sign-in or bot check, and click Recheck. The run carries on from where it stopped.

A run paused after three blocked links, with the steps to carry on

Check a production sitemap on a staging site

A staging site often serves a sitemap whose links point at the live site. The checker offers to check them on the site you are on, at the same paths:

- Link in the sitemap:  https://www.example.com/luggage/carry-on
+ Link that is checked: https://staging.example.com/luggage/carry-on

This is the case it was built for: confirming, before a launch, that every page production promises exists on the build about to replace it.

Privacy and limits

Nothing is sent anywhere. There is no server and no analytics, and the extension can only see the tab you click its button on.

  • One site at a time. It checks the site it is opened on.
  • Pages are read as served. Content that only appears after scripts run is not seen.
  • It is slower than a crawler. Three links at a time, which is also why the site keeps answering.

If the site is public, unprotected, and honest about its status codes, a command-line crawler is faster and can run in CI. Use that.

Key takeaways

  • A sitemap collects broken links quietly, because the ordinary ways a page disappears do not produce a 404 error.
  • A soft 404 answers 200 OK. The verdict has to come from the page, not the status code.
  • The sites that most need checking are behind passwords and bot protection. A check in your browser is already through.
  • A blocked link is not a broken link.

Links

Changelog

  • 0.1.0 (2026-11-19) — First draft.

Let's Build

Want this thinking applied to your systems?

Talk to the architects who wrote it.

Let's Chat