WRITING & TEXT FLAGSHIP
AI SEO Score Checker
Page to check
PageSpeed Insights usually takes 10–60 seconds. The page must be public — login-walled or local pages cannot be checked.
At a glance
AI SEO Score Checker — Paste any public page URL and get its real SEO score from Google PageSpeed Insights — a 0–100 score plus a pass/fail list of the actual SEO audits, never a guessed number.
Free for the core workflow, no account required. Parsing and transformation are performed locally in the browser from the data you enter.
About AI SEO Score Checker
Paste any public page URL and get its real SEO score from Google PageSpeed Insights — a 0–100 score plus a pass/fail list of the actual SEO audits, never a guessed number.
Most "SEO score" tools on the internet are guessing: they fetch your page, count a few things, and invent a number that looks authoritative. This one does not guess. It sends your URL to Google's own PageSpeed Insights API, which runs the same SEO audits Google uses in Lighthouse, and reports the real result — a score from 0 to 100 and a pass/fail list covering the page title, meta description, image alt text, link text, crawlable links, robots.txt and structured data. The check takes 10–60 seconds because Google is doing real work, and if the page cannot be reached or the API fails, you get a plain error message instead of a fake score. One search task usually leads to the next. The Hashtag Generator builds a relevant hashtag set for Instagram and the OCR Text Cleaner cleans common formatting artifacts in OCR text without changing the words themselves. Finally, the URL Slug Generator turns article titles and text into clean, SEO-friendly URL slugs. A single number that claims to grade your SEO is suspicious by nature, and most of the tools that produce one deserve the suspicion. They fetch your page from their own server, run a handful of shallow checks, and dress the result up as a score — and because the number is invented, it cannot be reproduced, it cannot be explained, and it changes when the tool's author changes the formula. The honest alternative is to ask Google itself, and that is what this tool does. PageSpeed Insights is Google's public service for running Lighthouse audits, including the SEO category, on any public URL. The score it returns is the same score Lighthouse would give the page in Chrome DevTools, computed from the same audits, with the same weights — and the audit list it returns names the exact checks that passed and failed, so the score can be explained line by line. That explainability is the whole point. A score of 88 with one failure on image alt text is a page with a clear next step: add alt text to the images. A score of 88 from a guessing tool is a page with a number and no next step at all. The seven audits this tool surfaces are the ones that matter most for a typical page. The document title check asks whether the page has a title at all — a page without one shows its URL in search results, which costs clicks. The meta description check asks whether a description exists; Google may rewrite it, but a missing one is a missed chance to shape the search snippet. The image alt check catches images with no alt text, which matters for accessibility and for image search. The link text and crawlable anchors checks catch links that say "click here" or are built in ways a crawler cannot follow — both are invisible problems until someone looks. The robots.txt check confirms the file exists and parses, because a broken robots.txt can accidentally block the whole site. And the structured data check validates any schema markup on the page, which is what earns rich results like review stars and recipe cards. None of these audits measures whether your content is good, whether anyone links to you, or whether you rank — and a tool that pretended otherwise would be lying. Worked example — here is how to read a result. Say you run https://www.exptool.com/ through the checker and it comes back 88 out of 100, with six passes and one fail, on image alt text. The reading is: the page is in good shape, and the single most valuable fix is adding alt text to the images that lack it. You would open the page, find the images without alt attributes, write a short description of each image, publish, and re-run the check to confirm the audit now passes and the score has moved. If instead the result came back 62 with failures on the title, the meta description and link text, the reading would be different: the page is missing the three basics, and those three fixes — a real title, a real description, descriptive link text — would move the score more than any other work. Table — the audits at a glance: document title, missing it costs clicks in search; meta description, missing it wastes the snippet; image alt text, missing it hurts accessibility and image search; link text, vague text like "click here" helps nobody; crawlable anchors, links a crawler cannot follow may as well not exist; robots.txt, a broken file can block the whole site; structured data, valid markup is what earns rich results. Each audit is pass or fail — there is no partial credit — which is why the list is more useful than the score alone. Before / after — before: a redesigned homepage ships, and nobody checks it. The new template forgot the meta description, three images lost their alt text in the migration, and the navigation links say "click here". The page looks fine and scores nothing, because nobody measured it. After: the same page is run through this checker, the failures are listed by name, the three fixes take an afternoon, and a re-check shows them passing. The page looks identical. What changed is that search engines can now read its title, its description, its images and its links — the four things a redesign most often breaks silently. Sources: Google PageSpeed Insights API documentation and Lighthouse SEO audit reference (developers.google.com/speed/docs/insights/v5/get-started and web.dev) — accessed November 2026. Content last reviewed: November 2026.
Primary objective: Runs a page through Google PageSpeed Insights and reports the real SEO score and audits.
Privacy assurance: Parsing and transformation are performed locally in the browser from the data you enter.
How to Use AI SEO Score Checker
- Paste the full URL of a public page, starting with http:// or https://.
- Press Check SEO score and wait — PageSpeed Insights usually takes 10–60 seconds.
- Read the 0–100 score, then read the audit list underneath it.
- Fix the failed audits first, starting with the title and meta description.
- Re-run the check after fixing to confirm the failures are gone.
- Use the live URL, not a staging or preview link — PageSpeed Insights can only audit what the public internet can reach.
- Run the check on desktop strategy first, since that is what this tool uses; mobile scores can differ.
- Work through failures in this order: title, meta description, crawlable links, image alt text, then structured data.
- After each fix, re-run the check — do not assume a fix worked until the audit passes.
- Keep the audit list, not just the score: the score moves for many reasons, but a named failure is always actionable.
Key Use Cases & Applications
- Checking a newly published page to confirm its title and meta description are in place.
- Auditing a homepage after a redesign to catch missing alt text and broken links.
- Comparing a page before and after an SEO fix to prove the fix worked.
- Proving an SEO fix worked by comparing the audit list before and after.
- Auditing a competitor's public page to see which technical basics they have covered.
- Adding a real, reproducible SEO check to a launch checklist for every new page.
Frequently Asked Questions
Why does the check take so long?
PageSpeed Insights loads your page on Google's servers and runs the full Lighthouse SEO audit suite against it. That genuinely takes 10–60 seconds. Any tool that returns a score instantly is not running the real audit.
What does the score actually measure?
Technical on-page SEO checks: whether the page has a title and meta description, whether images have alt text, whether links have descriptive text and are crawlable, whether robots.txt is valid, and whether structured data is valid. It does not measure rankings, backlinks or content quality.
Why did I get an error instead of a score?
Either the URL was not a full http(s) address, the page is not publicly reachable — login walls and local addresses cannot be checked — or the PageSpeed Insights API failed. The error message says which, and no fake score is shown.
Is a score of 100 necessary?
No. A score of 90 or above is generally good, and the last few points are often the hardest to earn — usually structured data edge cases on pages that do not need it. Fix the failures that affect real visitors first: title, description, alt text and links.
By Shehzad Hussain — owner and editor of ExpTool, based in Multan, Pakistan. He builds and tests every tool on this site himself.
Last updated: 2026-11-11