Free SEO Checker
Audit any page against 18 on-page checks and see its Domain Rating beside them. Every result is shown with its reason and the tool that fixes it, so you leave with a to-do list rather than a number.
How to use the SEO checker
- 1
Paste a URL
Homepage or any public path you want to audit. We fetch that exact page, so checking your pricing page tells you about your pricing page, not your homepage.
- 2
Read the score and DR
On-page readiness and Ahrefs Domain Rating are deliberately shown separately. One is what you control this afternoon, the other is what you earn over months.
- 3
Fix failing checks
Every failure names the problem and links to the tool that fixes it. Ship the changes, then re-run to confirm each check flipped.
Auditing like an SEO
Audit templates, not pages
If your blog posts share a layout, checking one tells you about all of them. Audit one page per template (home, product, blog, pricing) and you have covered the whole site in four runs.
Missing tags usually mean client-side rendering
We read the HTML your server returns without executing JavaScript. If a tag shows as missing but appears in your browser, it is being injected client-side, which is a real problem worth fixing rather than a false positive.
A perfect score is not the goal
The score measures unforced errors. Once you are above 85, further points come from checks that barely matter, and your time is better spent on content and links.
Re-run after every deploy to a template
Metadata regressions are silent. A refactor that drops a canonical tag will not break the build or the page, and nothing will tell you until rankings slip.
Compare before you panic
A score in isolation lacks context. Run the same audit on two competitors: if all three of you fail the same check, it is rarely what is holding you back.
Frequently asked questions
What does this SEO checker actually test?
Eighteen weighted checks on the exact page you enter: title and meta description presence and length, a single H1, canonical tag, indexability, HTML lang, content length, Open Graph and Twitter card, structured data, HTTPS, mobile viewport, server response time, robots.txt reachability and sitemap declaration, and image alt text. Each one is listed with its result, so the score is explainable rather than a black box.
How is the score calculated?
Each check carries a weight reflecting how much it matters, from 4 points for HTML lang up to 10 for things like HTTPS, a title tag, and indexability. Your score is the percentage of available weight you earned. Nothing is hidden, so you can disagree with our weighting and still use the individual results.
What is a good score?
Above 85 means the fundamentals are handled and further gains will come from content and backlinks rather than tags. Between 70 and 85 usually means a few quick wins are available. Below 70 normally points at something structural, like metadata missing across a whole template.
Why does a check fail when it looks fine in my browser?
We read the HTML your server returns, without running JavaScript, which is roughly what a crawler sees on its first pass. Tags injected client-side will show as missing here. That is a genuine finding, not a bug: third-party crawlers frequently never see client-rendered tags at all.
Is this the same as Lighthouse or PageSpeed Insights?
No. Those measure rendering performance in a real browser and are the right tools for speed work. This checks the SEO fundamentals in the served HTML plus a single server response time. Use both; they answer different questions.
Why is Domain Rating shown separately from the score?
Because they are different kinds of problem. The on-page score is entirely within your control and fixable today. Domain Rating reflects your backlink profile, which takes months to move. Blending them into one number would hide which lever to pull.
Does a high score mean I will rank?
No. On-page correctness is necessary but not sufficient. Rankings depend mostly on content relevance and backlink authority. Think of this as removing unforced errors so that your content and links can do their work.
Can I audit a page behind a login?
No. We fetch the page anonymously, exactly as a search engine would. If a page requires authentication, crawlers cannot see it either, which is itself worth knowing if you expected it to rank.
Are my results stored?
No. Audits run on request and nothing about your page is saved or published. Domain Rating values are cached for 24 hours to avoid repeat lookups, and that is a public metric about a domain rather than anything about you.
How often should I run this?
After any deploy that touches templates or metadata, and once a month as a routine check. Metadata regressions are silent, so a scheduled audit catches them long before ranking data would.