Free tool
Free SEO page checker: read any page the way a crawler does
Most on-page problems are visible in the HTML long before anyone opens a crawler. This reads one page for them, then reads the pages competing with it for the same answer.
The report
What the SEO page checker reports
Six things, read straight from the HTML the server sent. No estimates, no scores out of a hundred.
01
Metadata
Title tag and meta description, each with its character count against the limit it will be truncated at.
02
Indexability
The robots directive, the canonical, and whether that canonical points at this page or hands it to another one.
03
Heading structure
The H1, then every heading below it in document order with a count per level, so a broken outline is obvious.
04
Keyword signals
The terms the page actually leans on, weighted by how often they appear and whether they reach the title, description or headings.
05
Targeting
The market, language and audience the page reads as being written for — useful when a page is aimed at one country and reads like another.
06
Crawl basics
robots.txt and the sitemap at the domain root, fetched and confirmed rather than assumed to exist.
The comparison
Competitors found from the page content
Most tools pick competitors by domain similarity, which returns the brands you already know and none of the pages you are actually losing to. This reads what the page is about first, then names three to five pages answering the same question.
Each one is then fetched and put through the same six checks, so you are comparing like with like rather than reading someone’s summary of them. The drafted title and description come last, written against what those pages are already doing.
Read this before you act on it
Competitor suggestions are AI-assisted. A suggested URL can redirect somewhere more generic, and some sites refuse server-side requests outright — those come back marked could not crawl rather than quietly guessed at.
Check the final URL on each card. If it is not the page that was suggested, the comparison is against whatever it landed on.
The method
How the SEO page checker works
01
The page is fetched
Server-side, the way a crawler would, following redirects and reporting the URL it finally landed on.
02
The HTML is parsed
Metadata, directives, headings, keyword weighting and targeting signals, all read from what the server actually sent.
03
Competitors are checked
Suggested from the content, then fetched and run through the same checks. Anything unreachable is reported as unreachable.
04
A title is drafted
A title tag and meta description for your page, written against the competitor set rather than in isolation.
The limits
What the SEO page checker will not tell you
Three limits worth knowing before you read the report.
One page, not a site
Crawl waste, internal linking, index bloat, log files and rankings all sit outside it. No free tool that runs in a few seconds is going to tell you about those honestly.
HTML, not the rendered page
It reads what the server sends, before JavaScript runs. A site that builds its content in the browser looks almost empty here — which is close to what a crawler sees on its first pass, so it is worth knowing.
Gaps stay gaps
When it cannot reach a page or cannot answer something, it says so instead of filling the gap. If the missing part is the part you need, a proper engagement is the honest answer — and I will tell you if the work is not worth doing.
Questions
SEO page checker questions people ask
Yes. It is free to use and there is no account to create. You give an email address so the run can be attributed and rate-limited, and because it is how I follow up if you want a real audit. There is a daily cap per email, per connection and across the site, so it cannot be used as a bulk crawler.
Because that site refused the request. Large sites often block server-side fetchers outright, returning a 403, or fail the TLS handshake for anything that is not a browser. The checker reports the refusal instead of guessing at the page, so a blank competitor card means the data was not available — not that the page is empty.
Because its content is built in the browser rather than sent in the HTML. The checker reads what the server returns, which is what a crawler gets before it decides whether to spend the budget on rendering. A near-empty result is a finding, not a failure — it is worth checking how that page is indexed.
One page. Enter the exact URL you care about, not the domain, or you will get a report on the homepage. For anything site-wide — crawl waste, internal linking, index bloat, migrations — you need a real audit rather than a single-page check.
Read them first. They are written from the page content and the competitor set, and they are a strong starting point, but they do not know your brand rules, your product names or what legal will accept. Treat them as a draft to edit, which is how I would use them myself.
This one reads your HTML. The AI visibility audit asks answer engines the questions your buyers would ask and reports whether your brand comes up, where in the answer, and who gets cited instead. Different halves of the same problem — classical search first, answer engines second.
Check how AI engines answer about you
This page checker reads the HTML. The AI visibility audit does the other half — it asks the answer engines the questions your buyers would ask, and reports whether your brand comes up, where, and who gets cited instead.