Every page on your site,
read end to end, twice a month.

The crawl under Site Health, Issues and Page Tracker. It reads every page you have, grades them against 75 checks, re-scans your compliance pack's banned claims, and costs nothing for the pages that didn't change.

While it runs

Every stage
shows its work.

Discover, fetch, check, embed, score, persist. Each stage streams a line as it lands, with a real percentage behind it, so a long crawl never reads as stalled. Willowdale's 269 pages take about nine minutes.

Runningstreaming live…
Crawling https://willowdaleequity.com✓
Discovering pages on https://willowdaleequity.com✓
Found 285 pages in the sitemap✓
Measuring Core Web Vitals on 6 representative pages✓
Crawled 269 pages · 269 content pages to grade so far✓
Checking 250 external links + images✓
Embedding 269 pages for cannibalization analysis✓
Scoring and saving your pages✓
Internal linking: 34 pages with link opportunities✓
On every page

75 checks,
page by page.

Run over the HTML your site actually serves: titles, meta, canonicals, noindex, headings, images, internal links, JSON-LD. Your compliance pack's banned claims are re-scanned on every published page, and the E-E-A-T dial is scored from the same pass.

Technical
94
Good
Flag
306
Titles & meta
Pass
✓
Crawl & index
Flag
601
Media & schema
Compliance
Blocked
Flag
51
Hard blocks
Flag
70
Review flags
Info
3
Rules active
E-E-A-T
94
Good
Pass
✓
Author
Flag
27
Experience
Flag
1
Trust
What a re-run costs

The model re-reads
only what changed.

Every page is hashed on the text a model would read. If the hash matches what's stored, the page keeps its verdict and no model call is made. On Willowdale's second crawl that was 257 pages reused and 12 judged. The deterministic checks still run on all 269.

Completed
Crawled 269 pages · 269 content pages to grade so far✓
Grading content quality✓
LLM-judged 12 pages, reused 257 unchanged✓
Scoring and saving your pages✓

269 pages scored of 285 found · 1,289 issues · health 95/100

View in Site Health →
Where it lands

One crawl feeds
three screens.

The scorecard, the issue worklist and the per-page table are all views over the same run. Nothing here changes your site: the crawl reads, scores and files, and a person decides what to act on.

Last updated Sep 3, 2026, 4:00 PM UTC
Overall
95
Excellent0 vs last
Health · last 30 days
0255075100Aug 6Aug 10Aug 14Aug 18Aug 22Aug 26Aug 30Sep 3Sep 4
269 pages · 225 worth fixingLast full crawl Aug 27Scan look wrong? Email support

How it works

One run, start to filed.

Thirty-odd steps, batched so nothing in the middle can kill the whole thing.

Start for free
Found 285 pages in the sitemap✓
01

It finds every URL

robots.txt and the sitemap first; no sitemap and it crawls out from your homepage.

Crawled 269 pages · 269 content pages to grade so far✓
02

It fetches and checks each one

25 pages a step at concurrency eight, so a slow site can't time the run out.

Joined Search Console data for 214 pages✓
03

It joins Search Console and Analytics

28 days of queries, clicks, position and sessions, matched per page.

75 checks · 43 clean · 30 flagged · 2 n/a

04

It scores, files and stops

Every check's outcome is recorded, including the ones that didn't apply.

Questions

What people ask about the crawl.

How often, how deep, what it costs you, and what it will never do.

How often does it run?

Twice a month, on the 1st and the 15th at 09:00, on every plan including Starter. You can also start one yourself from Scheduled Tasks at any time; the tab shows the last result and the next scheduled run.

Does it read every page, or a sample?

Every page it can reach, up to a ceiling of 2,000 URLs, and it tells you in the run stream if it hits that ceiling. There is no per-plan page cap and no freemium wall: Starter gets the same crawl Agency gets.

What happens on a page that hasn't changed?

It is still fetched, still checked, still scored and still re-linked. The one thing skipped is the model read: each page is hashed on the text a model would see, and an unchanged hash reuses the stored verdict. That is why running this fortnightly costs about the same as running it monthly.

Is Core Web Vitals measured on every page?

No, and we will not claim it is. Each crawl measures a deterministic sample of up to six pages through PageSpeed Insights: your homepage, up to three distinct top-level sections and up to two blog posts. Speed is template-determined, so that covers the templates. Any single page can be measured on demand.

Is anything different during the trial?

The deterministic checks run on every page from the first crawl, always. Only the model-read pass is capped at 100 pages while you are trialing, taken shallowest-URL-first so it is your most important pages and the same 100 on a re-run. When the trial converts, a full re-audit is queued automatically and reads the rest.

Is this the same as the 46-check validation engine?

No. The validation engine grades a draft in the editor before it can publish. The crawl runs its own inventory of 75 checks over HTML your site already serves, and it writes to a worklist rather than a gate. Nothing the crawl finds is changed on your site by Verand.

Deep crawl

Point it at your domain.

The first crawl runs during onboarding and reads every page you have. You see the scorecard before you decide anything.

Verand

Content built to rank in Google and get cited by ChatGPTPerplexityGeminiClaude, with every claim checked before it goes live.

support@verand.ai

© 2026 Verand. All rights reserved. TermsPrivacyAI policyAccessibilitySecurity
Not legal advice. Compliance packs are AI researched and operator reviewed.