We ran our crawler against a real WebSite Auditor export and wrote down every disagreement, including the categories where we have nothing to offer. Here is the honest version of the comparison.
500 / 500
pages fetched, 0 failed
531
page WebSite Auditor export, 2026-05-18
1,376
issues in that export
33 / 33
categories, parser exact
A native crawl of gplcoffee.dev, 500 / 500 pages fetched, against a WebSite Auditor export of 2026-05-18, under the compatibility preset: 33 / 33 categories parser-exact on a 1,376-finding export. Fourteen categories matched outright, including robots, sitemap, www, http/https and custom 404 handling, and every remaining delta got one line explaining it. The full delta table is on the case study.
Three of these came out of the calibration itself: they are categories in the export our catalog has no answer for.
Each one is a property of where the audit lives, not a feature bolted onto a document.
Of every category in that export, these are the ones with no equivalent in our issue catalog. Our importer knows it: they sit on the parser's known-unmappable list, so a reconciliation reports them as absent rather than as a match.
Import your own WebSite Auditor Site Audit (details) export - the detailed report, not the summary - and we reconcile it against a live crawl. That is the same reconciliation we published on our own site: your export on one side, a live crawl on the other, every category lined up and every delta explained in one line.
A free scan reads 25 pages with the same catalog and hands back 3 fixes with the prompt to act on them. No account, no card. What the free scan does