Free · 2 minutes · 8 pillars
Enter your site. Get its standing.
Your public pages, read the way a crawler reads them: one score out of 100, the evidence behind every number, and what to fix first. No login, no code installed.
Examples of what the assessment reads
- ResponseHTTP 200 in 312 ms
- TransportHTTPS with HSTS
- Structured data3 JSON-LD blocks
- Security headers3 of 5 present
- AI crawlersGPTBot allowed
- Archive64 months captured
- Headings2 H1 elements
- Images18 of 24 lazy-loaded
- IndexingIndexable
- 100-pointscore with published weights
- 8 pillarsthe evidence behind each
- 0 codeinstalled, no login
- Archiveread even when your site is down
What the assessment reads
Eight pillars, one score.
Your homepage and up to eight other public pages, read like a search engine or an AI crawler reads them. That evidence alone scores the eight pillars, and the weights add up to one number out of 100.
- 15%
Architecture
How your pages are rendered and routed, and what that costs you.
- 15%
Performance
What your pages ship: script weight, image loading and the render pattern.
- 12%
Security
The headers your server sends, and what they leave open.
- 12%
Search
Titles, canonicals, robots rules and the signals a crawler reads first.
- 10%
Schema
The structured data that tells machines what each page is.
- 10%
AI readiness
Whether AI crawlers can reach your pages and quote them.
- 10%
Editorial experience
Your headings, structure and how cleanly the content reads.
- 16%
Operational health
Caching, errors and the upkeep your site shows from outside.
How your read happens
Two minutes, four steps.
Read your live site
The assessment fetches your homepage and up to eight public pages the way a crawler does, and logs every reading as it goes: response, headers, metadata, structured data.
Evidence logSample · Live- ResponseHTTP 200 in 312 ms
- TransportHTTPS with HSTS
- Platform signalNot disclosed
- Core metadata5 of 5 tags present
- Headings2 H1 elements
- Structured data3 JSON-LD blocks
- Security headers3 of 5 present
- Page mapped/pricing/
- Page mapped/blog/release-notes/
Check what the archive holds
At the same time it reads the Wayback Machine's public index for your domain, so you see how much of your site survives there. If your site is down, this is the part that still answers.
What the archive holdsSample- Months captured
- 64
- Archived URLs
- 1,240
- Pages
- 812
- Images
- 371
- PDFs
- 18
Last good capture: August 2026. An archived copy holds pages, images and files, not your database.
Score eight pillars
Each pillar gets a score from 0 to 100 from the evidence alone, then the weights add up to one number. Two weak pillars usually explain most of a low total.
Website Standing ScoreSample52/100At risk- Architecture42
- Performance88
- Security71
- Search91
- Schema37
- AI readiness63
- Editorial58
- Operational72
- 80 to 100
- Good standing
- 60 to 79
- Constrained
- 40 to 59
- At risk
- 0 to 39
- Legacy condition
Get what to fix first
Your report closes with the changes that raise your score most, each tied to the evidence behind it. Share the unlisted link with whoever does the work.
Priority actionsSample- 01
Send a Content-Security-Policy and HSTS on every response; security is the pillar holding your score down most.
- 02
Render the product pages on the server, so crawlers and AI assistants see the copy without running scripts.
- 03
Add Organization and Product structured data to the templates that have none.
- 01
- ResponseHTTP 200 in 312 ms
- TransportHTTPS with HSTS
- Platform signalNot disclosed
- Core metadata5 of 5 tags present
- Headings2 H1 elements
- Structured data3 JSON-LD blocks
- Security headers3 of 5 present
- Page mapped/pricing/
- Page mapped/blog/release-notes/
Start where you are
Start from the question you have.
Each page runs the same assessment and explains one thing you might be asking about your site.
Site down or hacked?
Down, hacked or broken: what survives, what to rebuild.
Website repairRedesigning soon?
Baseline before, reconcile after.
Website redesign SEOIs AI reading you?
Crawl access, extractable passages, schema, llms.txt.
AI SEO audit
- Website health checkThe general read, all eight pillars.
- Core Web Vitals testLCP, INP and CLS from what the page ships.
- Website audit checklistThe eight pillars as a list you can run yourself.
- Enterprise SEO auditWhat a free scan can establish, and where it stops.
- Next.js SEO auditRendering mode, metadata, hydration cost.
- Astro SEO checkIslands, content collections, schema, vitals.
- Headless CMS SEO auditRendering, canonicals, previews, schema from the template.
- Website consultantWhat a consultant checks first, and what it costs.
- AI consultantWhat they do, every AI role, and what to check first.
- Legacy CMS consultantWhat a consultant checks first on an ageing platform.
- Domain name consultantHow to choose, vet and buy the right domain.
- Sitecore alternativesSupport dates, licensing and the paths off XP.
- Drupal alternativesUpgrade, decouple or move, judged by your pages.
- AEM alternativesWhat to run when you use a fraction of the suite.
- WordPress alternativesStay, go headless or move: judged by your pages.
- Wix alternativesWhat exports, what does not, and where to go.
- Squarespace alternativesWhat exports, what you lose, where to go next.
- Webflow alternativesWhere the limits bite and what replaces it.
- Shopify alternativesBy store size, with the keep-the-checkout option.
- Joomla alternativesUpgrade, move to a builder, or a modern stack.
- TYPO3 alternativesEnterprise CMS or modern stack, without the agency tie.
- Drupal to Next.jsDecouple or replace, with the content model intact.
- WordPress to AstroPre-built pages, content in Markdown or a headless CMS.
- WordPress to Next.jsHeadless WordPress first, or content into Sanity.
- Sitecore to Next.jsItems, templates and renderings into a headless model.
- Magento to ShopifyCatalog, customers, orders, extensions and URL rewrites.
- Drupal to WordPressWhen simpler is right, and what the content model loses.
- Webflow to WordPressCode and CMS exports, and when Astro fits better.
Questions, answered.
01Is the assessment free?
Yes. It costs nothing and takes about two minutes. To send you the report link once, and only once, it asks for a work email. The report sits at an unlisted address (so nobody stumbles on it), and you can share that link with anyone you choose.
02Does it work on a site behind a login or a staging password?
No. It reads public pages only, the way a search engine does, so protected pages return nothing, and your report says so instead of guessing. So run it on the public site you want measured.
03How often should you run it?
Quarterly. Run it again after any release that touches templates, redirects, plugins or hosting. Keep the report links, because two readings three months apart tell you more than either alone. A single score is a snapshot. A pair is a trend you can act on.
04Who built it?
Gautam Khorana built the assessment and runs it from London. He has spent 12+ years on thousands of websites of every shape and size, from one-page brochures to directories. The about page has the detail, and the detail is where he'd rather you looked.
Free, two minutes, no login