How to use the website SEO score checker
- 1Enter the page address and press Audit page.
- 2Read the Checklist score and the counts of passes, warnings and problems.
- 3Work through Fix first: problems come before warnings, heaviest checks first.
- 4Open Full checklist with evidence to see what was found for every check, such as the exact title text and its width.
Example: the sample page (illustrative URL)
https://www.example.com/baking/sourdough-starter/ (the tool's sample HTML, served with Brotli, 310 ms TTFB)
Checklist score 82/100 (71 of 87 points) · 15 passed · 5 warnings · 1 problem · 5 notes Fix first: Problem og:image: relative URL “/images/starter.jpg” Warning Title tag: ~724 px, likely truncated Warning Meta description: 46 characters, short Warning Visible text: 27 words Warning Heading structure: jumps from H1 to H3; empty H2 Warning Image alt attributes: 1 of 1 image has no alt
Computed by the tool's checklist on the sample HTML with the response details shown. A real URL's result depends on what its server returns.
What the audit checks
Our server requests the page as a crawler would, then checks what it received:
- Indexability: HTTP status, redirects, robots meta, X-Robots-Tag, canonical.
- Title and description: present, unique in the page, estimated pixel width.
- Content and headings: H1, heading order, amount of visible text.
- Links and images: internal links, empty links, alt attributes, image dimensions.
- Structured data: JSON-LD present and parseable.
- Mobile and document: viewport,
lang, charset, favicon. - Speed basics: server response time, compression, HTTPS.
- Social sharing: Open Graph and X card tags.
Each check shows its evidence, so you can verify it yourself.
How the score is calculated
Every scored check has a weight. A pass earns the full weight, a warning half, a problem nothing; notes aren't scored. Score = points earned ÷ points available × 100.
| Weight | Checks |
|---|---|
| 10 | HTTP status, robots meta tag, X-Robots-Tag (when it blocks), title tag |
| 6 | Meta description, viewport |
| 5 | H1 |
| 4 | Canonical, visible text, HTTPS |
| 3 | Heading structure, links, image alt, structured data, server response time, og:image, redirect chains of 2+ hops |
| 2 | Single title, page language, HTML compression, empty links, og:title, og:description |
| 1 | Single description, charset, favicon, twitter:card |
The score summarises this checklist. It isn't a Google metric and doesn't predict rankings.
Indexability: robots, canonical, status
These checks carry the most weight because any one of them can keep a page out of search entirely: a non-200 status, a noindex in the HTML or in an X-Robots-Tag header, or a canonical pointing somewhere else. If the address redirects, the audit runs on the final URL and lists the hops; two or more redirects in a row cost points. If the page can't be fetched at all, the tool shows the error and no score, rather than a misleading number.
Content and headings
The audit counts the words in the HTML body and flags pages under 150 words, a point where the HTML may be a JavaScript shell or a thin page. That isn't a Google rule; there's no minimum word count. It also checks for one descriptive H1 and headings that go down one level at a time. For the full outline use the heading checker, and for titles and social tags in more detail, the meta tags analyzer.
Prioritising fixes
Fix first lists problems before warnings, heaviest first. A reasonable order of work:
- Anything that blocks indexing (status, noindex, canonical).
- Title and description, which shape how the result looks.
- Headings, content and internal links.
- Structured data, images and social tags.
- Speed: the audit only measures the HTML response; run the website speed test for Core Web Vitals.
Then validate structured data with the schema markup validator.
What happens to the address I enter?
To check a URL, our server requests the address you enter and returns the result to you. We don't store the pages we fetch or keep a list of the addresses you check. Like any website, our hosting provider keeps short-lived technical request logs for security. See the privacy policy.