Most technical audits start with a 4,000-row crawl export. You need something faster: is this one URL even allowed to rank?
Paste it into the SEO Readiness Score Checker. You get a 0–100 score, a letter grade, and a fix list ordered by what actually blocks search and AI extraction. It is a pulse check, not a ranking forecast.
Then fix the red items. Re-run the same URL after deploy.
What this score is (and what it is not)
An SEO readiness score is a single-URL diagnostic of signals you control: on-page tags, indexability, structured data, content and links, security headers, and AI readiness. The checker returns a weighted 0–100 total, a letter grade, category scores, and a prioritized fix list.
It is not a Google ranking prediction. Rankings still need links, content quality, competition, and whatever Google’s systems do with the rest of the web. A high readiness score means the page is set up so crawlers and extractors can use it. It does not mean position one next Tuesday.
It is also not a full site crawl. One URL is one URL. Templates, faceted junk, sitemap lies, and orphan pages live in a different job — the technical SEO audit checklist.
The live checker does not drag in retired Google features. No retired mobile-friendly test. No Google Cache check. It fetches the URL and scores what is on the page and in the response today.
When to run it
Use it when you care about a specific public URL:
- Before you publish a landing page or a money template
- After a CMS or theme change that rewrote titles, canonicals, or robots
- After migration cutover, as a pulse on the new money URLs (the full cutover workflow is the site migration SEO checklist)
- When a client asks “is this page OK?” and you need an answer in one minute, not one week
Spot-check the URLs that pay the bills. Do not pretend one homepage score covers the catalog.
Skip passworded staging. If the checker cannot fetch what Googlebot will see on production, the number is noise.
How to use the tool
- Open the SEO Readiness Score Checker.
- Paste the full public URL — production, HTTPS, the address you actually want indexed.
- Click Check SEO score.
- Read the score, the letter grade, the category breakdown, and the What to fix list.
No account. No login. No usage limits or paywalls on the tool page. Paste and run.
How to read the score and the fix list
The headline number is 0–100. The letter grade rides with it. From live runs on real URLs, treat the bands as triage, not vanity:
- A (about 90+) — fundamentals look solid; leftover items are usually polish
- B (80s) — usable, but the fix list still has work
- C (70s) — weak spots that will bite if this is a money URL
- D (60s) — foundational gaps; do not ship and celebrate
- F (below 60) — something basic is wrong (indexability, tags, schema, or worse)
Do not invent a “Google wants 80+” rule. Google did not publish that. Use the grade to decide how urgent the ticket is.
Under the score you get a Score breakdown across six categories. Each has its own points, a pass / warn / fail status, and line-item findings (also pass / warn / fail). Live weights today:
- On-page SEO — 30 points (title, meta description, H1, HTTPS)
- Indexability — 20 points (HTTP status, noindex, canonical, Googlebot access)
- Structured data & social — 15 points (JSON-LD, rich types, Open Graph / Twitter)
- Content & links — 15 points (word count, image alt, internal links)
- Security headers — 10 points (including HSTS and
X-Content-Type-Options) - AI readiness — 10 points (FAQ / question structure, AI crawler access, answer-first H2s)
Those weights match what the live tool returns today.
The What to fix list at the bottom is ordered with high, medium, and low priority. Start at high.
Triage order: anything that blocks crawling or indexing first, then on-page and schema on money pages, then headers and AI polish. A pretty title on a noindex URL is still a draft.
Worked example. Score was fine last week. After a deploy it falls into the D/F range and Indexability flips to fail. Open the findings: leftover noindex from staging, or a canonical pointing at the old host. That is the whole story. Diff the fix list against the deploy. Remove the staging rule. Re-run the same URL. Do not rewrite the meta description first.
Indexability
This category is the kill switch. Live checks include HTTP status, whether a noindex directive is present, whether the canonical is self-referencing, and whether Googlebot is blocked for that path.
If the page returns a soft failure here, the rest of the score is academic. Confirm with the Canonical Checker when the canonical looks wrong, and with the Google Index Checker when you need to know if Google already kept or dropped the URL. For the longer “why isn’t it indexed” write-up, see how to verify index status.
On-page tags
On-page SEO is the largest slice of the score (30 of 100). The checker looks at title length, meta description, H1, and HTTPS.
It is a hygiene pass, not a copy workshop. If the title is missing, duplicated across a template, or wildly truncated, fix the template. For a deeper length and SERP read on a single field, use the Title Tag Checker and Meta Description Checker — then stop. Do not turn a readiness pulse into a brand-voice debate.
Schema
Structured data & social covers JSON-LD presence and validity, whether useful types showed up (FAQPage, Organization, and friends), and Open Graph / Twitter tags.
Rich results are a bonus when the markup matches the visible page. Mismatched Product or FAQ markup is a liability. If this category fails or warns, open the Schema Checker on the same URL and read the errors against what you can see in the HTML.
Security headers
Security headers are trust and hygiene, not a ranking fetish. The readiness checker scores things like Strict-Transport-Security and X-Content-Type-Options. Missing HSTS will not “kill SEO” by itself. It is still worth fixing on a live HTTPS site.
For the raw response and a fuller header pass, use the Security Headers Checker.
AI signals / extractability
AI readiness is its own category (10 points), separate from a dedicated GEO score. On a live run the checker looks for FAQ / question-style structure, whether major AI crawlers are allowed in robots.txt, and whether H2 sections lead with a direct answer. You also get an AI readiness signal list under the breakdown.
That is extractability and crawler access on this URL — not a promise that ChatGPT will cite you. For citation-oriented scoring, use the GEO Score Checker. For who is allowed through robots.txt, use the AI Crawler Accessibility Checker.
A sensible fix order
P0 — cannot be crawled or indexed as intended. noindex on a money URL. Robots blocking the path. Canonical to a 404 or the wrong host. Non-200 on the live address. Fix this week. Re-check.
P1 — in the index, still weak. Missing title. Broken or empty JSON-LD on a money template. Thin body on a page that should carry the query. This sprint.
P2 — headers and AI polish. HSTS, CSP notes, answer-first headings, FAQ schema if it fits the page. Backlog unless you are already selling “AI search ready” in a deck.
Ship the P0 fixes. Re-run the same URL. Audits that never re-hit production are how the staging noindex survives three sprints.
Pair it with these checks (don't stop at one score)
The readiness checker answers “does this URL have a pulse?” Pair it when the question changes:
- Index status unclear → Google Index Checker
- Whole site feels sick → technical SEO audit checklist
- URLs moved → site migration SEO checklist
- Citation / answer-engine readiness → GEO Score Checker and AI Crawler Accessibility Checker
- Whether Google shows an AI Overview for a keyword → AI Overview Checker
- Schema errors need a microscope → Schema Checker
One score is a starting line, not the whole audit.
Mistakes that waste the report
Treating 70 as “fine.” A C-range score on a checkout or pricing URL is not fine. Read the fix list.
Fixing meta while robots still blocks. Title polish on a Disallow or noindex URL is busywork. Indexability first.
Running staging. Basic auth, staging noindex, and staging hostnames produce a score that does not match production. Use the live URL.
Confusing this with rankings. The score summarizes what the tool measured on the page. It does not include backlinks, competitors, or Search Console impressions.
Confusing this with a full crawl. Screaming Frog (or any desktop crawler) still owns sitewide discovery. This tool owns the one-URL pulse. Use both when the job needs both.
Closing
Run the checker on the money URL. Ship the P0 fixes. Re-check the same address after deploy. That is the whole loop.
SEO Readiness Score Checker — free, no login.