Our dotmap self-audit: 67 to 80, with work left
case study // , 5 min read, by Darthwares
We used dotmap on dotmap.ai itself. A baseline crawl on September 27, 2026 scored six reachable pages at 67/100. After improving the audit page, legal metadata, internal navigation and publishing research articles, the same audit endpoint returned 80/100 across ten pages. That is progress, not a claim of perfect SEO or an observed increase in Google traffic.
On this page // 4 sections
The baseline showed a split site
The homepage already scored well at 91/100, but the site-wide average was 67. The audit page scored 71. The terms page scored 54, and two noindex login URLs scored 56 each. The report identified short content, missing canonicals or structured data, short titles and descriptions on supporting pages, and utility pages that were not useful search landing pages.
This distinction matters: a strong homepage cannot compensate for every weak or duplicated route in a site-level average. It also does not mean all those pages should rank. Login pages are intentionally marked noindex; we should interpret them as utility pages even though the current crawler still includes them in its audit denominator.
What we changed, and what we did not
We published three focused, source-linked articles on continuous SEO monitoring, revenue exposure and a small sponsored-news experiment. We gave the audit page a useful explanation of the report, its coverage limits and what its score does not measure. We clarified legal and privacy copy, added canonical metadata and relevant structured data, improved internal navigation, and included the new pages in the sitemap. The research covers decisions a reader can make, rather than repeating keywords to inflate word counts.
We did not set a score in code, alter Jev's scoring weights, or claim that our content was cited by an AI answer engine. The score reflects a fresh crawl and the current rubric. A different crawl limit, a new page, or a later model judgment could change the number.
The measured result
The new run scored the monitoring guide 93, the revenue-risk guide 90 and the sponsored-news guide 95. The audit page moved from 71 to 87. Privacy moved from 76 to 88. The terms page rose to 61 but remains a utility page under this rubric. The homepage returned 90, close to its earlier 91. Together, the ten analyzed URLs averaged 80/100.
After we published this case study with links to both reports, a fresh crawl reached thirteen pages—including the two linked reports—and still returned 80/100. The URL set changed, which is why every before-and-after should state its coverage. These are dotmap grader results, not Search Console metrics. We have not measured a change in organic clicks, signups or revenue from this work. The reports below let readers inspect page-level findings rather than accept a single headline number.
Why we are not calling this 100
The two login URLs remain intentionally noindex and score 56 as utility pages; the terms page scores 61. More prose on a login screen would not make it a useful search landing page. A good next product decision is to improve how dotmap reports utility and intentionally excluded pages, while keeping the raw coverage and score transparent. We will not silently remove weak pages from a report to present a perfect average.
The practical loop continues: audit, fix the right pages, recrawl with the same settings, and compare real search and conversion data separately. If a future run earns 100 without hiding pages or changing the rules to flatter ourselves, we can say so then. Until that point, 80 is the verified result.
Primary sources and further reading
Prepared with AI-assisted drafting and checked against the primary sources below. These sources support the platform and measurement claims; the examples and recommendations are dotmap analysis, not results reported by the sources.