how it works // crawl → judge → report
How a dotmap audit works
dotmap crawls your site, sends each page to Jev once for twelve judgments, runs eighteen technical checks in code, and turns the results into a report and a map. Fifty pages take about three seconds and cost about half a cent.
One audit, start to finish5 steps
- 01
Enter a URL
Choose a page limit and a depth. The crawler stays on the same site.
- 02
dotmap crawls the site
A bounded pool of workers fetches pages and extracts content, headings, metadata and JSON-LD.
- 03
Each page gets one Jev call
Seven scores and five probabilities come back from a single request.
- 04
Eighteen technical checks run in code
Status, indexing, titles, canonical, structured data, speed and links.
- 05
You get a report and a map
A site score, ranked issues, the pages to fix first and a link you can share.
crawl // same-site, bounded
The crawl stays on your site and shows its limits.
The crawler starts at the URL you enter and follows internal links to the depth you set. It fetches HTML pages and skips images, scripts and other assets. A signed-in deep crawl also reads your sitemaps.
When it reaches the page limit it stops, and the report lists every URL it found but did not fetch. Coverage is stated, never implied.
judge // one jev call per page
One request per page returns twelve judgments.
Each page's extracted content goes to TypeSafe's Jev model in a single call. Jev returns seven rubric scores and five yes-or-no probabilities, each with a calibrated confidence, so a borderline page reads as borderline.
Because the output is structured and free, the cost is the input tokens only: about 2,400 for a typical page.
report // grades + ranked issues
Page scores become one site report.
Each page's score is 65% semantic and 35% technical, graded A at 85 and up, B from 70, C from 55, D from 40, and F below that.
The report adds them up: a site score, how many pages got each grade, and the issues that affect the most pages, ranked.
live run // cost meter
Results arrive while the crawl is still running.
Pages are scored the moment they are fetched. One dot per page fills in with its grade colour, and the cost meter runs off real token usage.
When the last page lands, the report is ready: site score, grade distribution, the issues that affect the most pages, and the strongest and weakest URLs.
rubric // 7 scores + 5 probabilities
What a page is scored on
Seven scores describe how good the page is. Five probabilities describe what kind of page it is and whether it can be quoted.
See all eighteen technical checksSeven scoreshow good the page is
- Title quality
- Does the title say what the page is, specifically?
- Meta description
- Does it summarise the page and earn the click?
- Content depth
- Is there enough substance to answer the topic?
- Heading structure
- Do the headings outline the page?
- Search-intent match
- Does the page deliver what its title promises a searcher?
- Readability
- Can a reader follow it without effort?
- Answer-readiness
- Does it answer its own question directly and early?
Five probabilitieswhat kind of page it is
- Title matches content
- Flags titles that describe a different page
- Utility page
- Login, error and empty archive pages are judged differently
- Worth indexing
- Whether the page deserves a place in search at all
- Clear call to action
- Whether a reader knows what to do next
- Citable by an answer engine
- Whether a passage could be quoted as a source
how it works // three steps
SEO is now also AEO.
Search results are increasingly answers with citations. A page earns a citation when a model can lift a self-contained passage from it. dotmap checks the signals a search engine wants and the one an answer engine wants, page by page, and tells you which URLs are ready.
- 01
Enter a URL
Set a page limit and depth. The crawler stays on the same site and skips assets.
- 02
Each page gets one Jev call
Seven rubric scores and five yes-or-no probabilities over the page's extracted content, plus eighteen technical checks in code.
- 03
Read the report, then share it
Site score, grade distribution, top issues with fixes, the share of citable pages, best and worst pages, and a public link with a preview card.
aeo // answer engine optimization
Find out which pages an AI answer could quote.
Answer engine optimization (AEO) is writing pages so AI answer engines can cite them. dotmap reads every page on your site, estimates whether it contains a passage a model could lift as a source, and tells you which ones to rewrite.
Search ranks pages
A search engine shows a list and the reader picks a result. Your title and snippet do the work.
Answer engines quote passages
An answer engine writes a reply and attaches a few sources. It needs two or three sentences it can lift.
So the passage has to stand alone
If the answer is spread across the page, or leans on context above it, there is nothing clean to quote.
What a rewrite looks like
Welcome to our reporting features. Over the years we have built many tools for teams. As you will see below, there is a lot to explore, and it depends on your plan.
Acme reports show the SEO score of every page on your site and the issues that affect the most pages. Reports update after each weekly audit and can be shared by link.
compare // dotmap vs google vs bing
Google and Bing each grade one thing. dotmap grades the whole site.
Google's Lighthouse score tests one URL for tags and speed. Bing publishes guidelines but no score. Neither reads what your pages say or tells you whether an AI answer could quote them. dotmap does both for every page, and shows the Google and Bing numbers beside its own so you can compare.
How much of the site it checks
Judges what the page says
Ready to be quoted by AI answers
Tells you what to fix first
Page speed on a phone
A single score you can share
Use Lighthouse when
you need to know how fast one page loads on a phone, or whether its basic tags are in place.
Use Bing Webmaster Tools when
you need to see what Bing has crawled and indexed, and submit a sitemap or changed URLs.
Use dotmap when
you need to know which of your pages are weak, why, and which ones to fix first.
Read next
ready
See it on your own site.
Enter a URL and watch the pages fill in. No account needed.