We ran SearchBlueprint on SearchBlueprint

The setup

The day our domain went live, we pointed our own audit at it. Standard scope, no special treatment. The grade came back: C, 78 out of 100. Not the number you want on the tool's own website.

What it caught

The big one was the sitemap. It still listed over 500 URLs that sit behind our login wall. Google would request each one and get redirected to the same login screen. The audit read the damage precisely: the login page counted 18 times as duplicate content, canonical tags pointing away from every crawled URL (an F in canonicalization), and four indexability failures.

It also flagged five pages shipping a 15-character title and graded the homepage D on content depth. None of this was visible from inside the product. All of it was in the report within four minutes.

What we changed

Four fixes, all shipped the same afternoon: we rebuilt the sitemap around the 47 pages that are actually public, blocked the app routes in robots.txt, set a proper title default with a template for inner pages, and added a FAQ section to the homepage.

The re-audit

Seven points in one afternoon, from fixes the report ordered by impact.

What it still flags

The content category now grades F. That's not a regression, it's visibility: the crawler finally reaches all 39 of our free tool pages, and most of them are thin. The report is telling us our next block of work, the same way it would tell you yours. When we've done that work, we'll update this page with the new numbers.

The point

The audit found an infrastructure mistake the people who built the product shipped and missed. If it catches us, it will catch something on your site too. The same audit is free, takes about four minutes, and gives you the ranked fix list first.