How to Check Your Website SEO Score for Free

How to Check Your Website SEO Score: The Short Answer

Quick answer: A website SEO score is one number from 0 to 100 that a checker gives a page. In our report it is the share of checks passed. Paste the page address into the free checker, select Generate Report and read the circle labeled Your score. Use the number as a to-do list for that page, not as a prediction of where it will rank.

1. Open the checker. Go to the free Website SEO Score Checker. The box on the home page works the same way.
2. Enter the address. The box asks you to "Enter a Website URL" and shows https://www.example.com as the example, and a bare domain such as example.com works. Select Generate Report. A card reads "Analyzing your website... Please wait...", and example.com took 9.2 seconds in our test. A heavy page takes longer, and the audit stops itself at 85 seconds.
3. Read the circle. It is labeled "Your score" and sits beside four counts: Total, Passed, Warning and Failed.
4. Write it down. Note the number and the date before you change anything, because a re-run replaces the report and there is no history view.

The rest of this post explains how to check SEO score results with care, and what the number can and cannot tell you.

What Is a Website SEO Score?

The SEO score of a website is a number that a tool calculates from its own list of checks on a page. It is a tool-maker's term and not a Google metric, and no standard formula exists, so the figure can differ from one tool to the next.

Three different things share the name:

• Check-based scores, such as an on-page SEO score, are built from the checks a page passes, which is what our report gives you. This post is about that kind.
• Authority scores such as Domain Authority estimate ranking strength from link data. Our page authority versus domain authority guide covers them, and our report has no backlink check.
• Traffic or search visibility estimates are usually modeled from keyword rankings, not from the page itself.

Google's Search documentation describes no overall SEO score. On October 31, 2026 we read its page experience guidance, the SEO Starter Guide, Search Essentials and the helpful content guidance, and none of them uses the term. Lighthouse, Google's open-source audit tool, does print an SEO category score for a page, and its documentation describes equal weighting for the audits that count, the same idea ours uses.

What is a free SEO score check for? It flags things that can keep a page from being found or understood, and it gives you a before-and-after check. It is not a grade from Google and not a measure of traffic.

How Our Website SEO Score Is Calculated

The formula

The scoring formula is passed checks divided by counted checks, times 100, kept to two decimals. The circle shows the rounded score as a whole number, so 67.65 appears as 68, and the title of that report's browser tab includes "Score 68%".

What counts and what does not

Five rules decide what goes into that fraction.

• Equal weighting. Every scored check counts once, with no weights and no section scores.
• Warnings earn nothing. Each check ends as Passed, Warning or Failed, and only a pass raises the score.
• Not measured. A check the browser could not measure is labeled Not measured and does not enter the fraction on either side.
• Four rows that pass on every page. Nofollow Attribute and the three keyword tables (most common keywords, keyword usage and long-tail keyword usage) are informational: counted, but unable to fail. One check is worth 100 divided by 68, about 1.47 points on a 68-check report, so those four rows hand every page about 5.9 points. Dropping them from the count would lower example.com by about 2 points, because 42 of 64 is 65.6.
• The count varies. Our latest re-run counted 67 to 69 checks per report, so one check is worth about 1.5 points.

A worked example from a real report

Divide 46 by 68, multiply by 100 and you get 67.65, which the circle shows as 68. Those numbers belong to that date, and a later section shows how one unchanged page can change score.

Under the overview sits a separate block, AI Search Readiness. It is a second weighted score from 0 to 100, built from ten checks where a warning earns half the weight, and example.com got 44 there on that date. It never changes the main score, because it is attached after that score is counted. It reflects what a crawler can read, not whether an AI product will cite the page, and our guide on how to show up in AI search explains what those checks are for.

What the Score Checks and What It Leaves Out

The report runs more than 60 scored checks on the one page you enter. It groups them under Seo, Speed optimizations, Server and Security and Advance, and the AI Search Readiness block sits apart. Our guide to every check in the report explains each row.

What it leaves out

• Backlinks and link authority.
• Keyword rankings and traffic.
• The quality of the writing.
• Field data and Interaction to Next Paint (INP). The report has lab data only, and Total Blocking Time is the lab stand-in, so it covers Core Web Vitals only partly.
• Anything beyond the page you entered, so duplicate titles across pages stay invisible.
• Whether Google has indexed the page or whether robots.txt blocks it. The report reads the live page, not Google Search Console, and its robots.txt rows only look for the file and its Disallow lines.
• A malware scan, because the Safe Browsing row only checks that the page answers normally.

The speed timings come from one lab run in headless Chromium on our server.

Which Page to Check and What You Will See

The score belongs to one page, so a page SEO score only describes the address you entered. Check your home page and the two or three pages that carry your traffic or revenue.

These are the address rules we tested, and each refusal came back in under half a second:

• A bare domain such as example.com works, https:// and www are optional, and a path or query string is audited as typed.
• Text that is not an address, such as "hello world" or "javascript:alert(1)", answers "Check the address".
• "localhost" and "http://127.0.0.1/" answer "Address not allowed".
• A name that does not exist answers "Website not found".

As a guest you see the score, the Overview and what each check found and why. The detail lists inside many checks ask you to register or log in, and a free account also unlocks Save Report and Download PDF.

If a firewall or bot challenge answers instead of your page, the report shows a banner saying the score does not describe the real page, so fix the access and not the number. Clear your page cache before a re-run, because the audit sees whatever your server sends. For steps three and four in detail, follow the free walkthrough with a real report.

What Is a Good Website SEO Score? What Real Reports Show

What is a good SEO score? There is no universal answer, and scores from different tools are not comparable. Many guides name 80 or above as good without showing data behind it, and on this checker that bar is rare.

What the sites we audited scored

On October 31, 2026 we audited 347 addresses that had been checked on this tool, once each under today's rules. Of those, 274 produced a score. We left out 63 that gave no result (42 domains that no longer resolve, 4 server errors, 8 certificate errors and 9 other failures) and 10 bot-challenge pages, because their scores would describe the challenge and not the site.

This is not a random sample of the web. People check pages they are working on, and some of the checks were ours. It describes this checker only, so it is neither an industry average nor an SEO benchmark. This post lists no addresses and no per-site scores.

Reaching 80 or above took 6.2 percent of the scored sites (17 of 274), 85 or above took 0.7 percent (2 sites) and none reached 90, while 0.7 percent (2 sites) scored under 50. Stored reports from before this run mix versions of our rules, so we did not use them. The same sites had a median of 66.2 there. You can open real reports of other sites on the published SEO reports page.

Our reading: a 71 sits in the middle of what we audited, and an 80 is among the highest 6 percent. Neither number says anything about how a page ranks.

How to judge your own score

1. Compare it with your last run of the same page. A score trend means more than one level, and a re-run overwrites the old report, so keep your own record.
2. Compare it with the pages that rank for your query. Any public address works, so run the same SEO checker on them and compare check by check, not number to number.
3. Read the checks that did not pass. Every check is worth the same, about 1.5 points, so a noindex tag costs a page exactly as much as one stray inline style does, though it is far more serious. That is why we say to read the rows and not only the number.

Does Your Website SEO Score Affect Google Rankings?

Not as a number. Google's Search documentation describes no overall SEO score, and a score calculated inside a third-party tool is computed outside Google, so it is not a signal Google reads. Google's page experience guidance answers whether a single page experience signal exists with "There is no single signal", and says Google ranking systems look at "a variety of signals". The same page says "Core Web Vitals are used by our ranking systems", yet good results in Search Console's Core Web Vitals report or in third-party tools do not mean a page will rank at the top.

Our speed timings come from one lab run, in which the report reads Total Blocking Time (TBT), First Contentful Paint (FCP), Cumulative Layout Shift (CLS) and Largest Contentful Paint (LCP). It has no Interaction to Next Paint and no field data, while the Core Web Vitals thresholds are judged on real page loads at the 75th percentile. So passing our rows does not mean a page passes Core Web Vitals. When a vital does fail, our Core Web Vitals guide shows how to diagnose it.

The score is good for something narrower. It catches things that keep a page from being found or understood, such as a noindex tag or a missing title or H1, and it confirms that a fix landed. We have not tested whether our score predicts rankings, and two pages with the same score can rank very differently.

Why the Same Page Gets Different SEO Scores

Different tools run different checks with different pass marks and weights. Lighthouse, the engine PageSpeed Insights runs, reports its Performance score as a weighted average, and the Lighthouse scoring documentation says the weightings have changed over time. Ours has no weights, and neither method is the right one.

When the page itself has not changed, a score can still move for two reasons. The first is lab noise: the Lighthouse documentation lists ads being served, routing changes, different devices, browser extensions and antivirus software as common causes of Performance score swings. Our audit is one headless Chromium load, so speed rows can move, though every run of example.com on October 31 under today's rules gave the same counts.

The second is the checker's own rules. Run through the audit script as it stood before October 30, example.com comes out at 65 (44 passed, 4 warnings, 20 failed, or 64.71). Today's script gives 68 (46 passed, 4 warnings, 18 failed, or 67.65). On October 30 we revised two rows: Nofollow Attribute now always passes, and Noopener and Noreferrer now looks only at external links that open in a new tab. Example.com has one external link, a Learn more link to iana.org that its own script adds, so two checks flipped from Failed to Passed, and two of 68 is about 3 points.

A score belongs to a date and a version of the rules, and one flipped check is about 1.5 points. So compare only within one tool and one page, rerun the same tool after a fix, date every score you record, and treat a move of one or two points as small unless you can name the check that changed state.

What to Do After You Get Your Score

Pick the route that matches your next question.

• To understand what each section and row means, read the guide to reading an SEO audit report.
• To work through fixes in order, use the score improvement plan.
• If the real problem is traffic and not a number, start with the Search Console routine for organic traffic.

Our ordering advice, since the report marks status and not severity: fix Failed rows before Warnings. Start with the priority fixes, meaning anything that can keep the page out of search results or hide its topic, such as a noindex tag or a missing title or H1. Then run the same page again and compare it with the number you wrote down.