Free SEO Page Checker

Paste any page and get every on-page SEO basic checked in one report: whether Google can index it, how it looks in search results, its headings, sharing tags and structured data, phone basics and links. Each finding says what to fix, and the page gets a score you can improve.

Free · No sign-up · Nothing stored

Checking the page from every angle. This takes about 10 seconds…

At a glance

  • One page, about 22 checks, six groups, with a link to the deeper free tool for each group.
  • The score is transparent: pass = 1 point, check = ½, fail = 0, out of the checks that apply.
  • Fix in order: indexing first, then the search result, then structure, then sharing and structured data.
  • On-page only. It doesn't measure rankings, backlinks or content quality, and it doesn't run a speed test.

What the SEO checker looks at

Most of what decides whether a page can do well in search is on the page itself, and most of it is quick to fix once you can see it. The checker groups everything into six questions:

What the SEO page checker covers
GroupWhat's checkedGo deeper with
Can Google index it?Status, robots.txt, noindex (tag and header), canonical, sitemap listing, httpsIndexability Checker
How it looks in GoogleTitle and description by pixel width, duplicate tags, Google previewMeta Tag Checker
Page structure and contentOne H1, heading order, page language, image alt text, amount of textMeta Tag Checker
Sharing and structured dataog:title, og:description, og:image, twitter:card, JSON-LD that parsesSchema Markup Checker
Phones and speed basicsViewport and zoom, HTML size, compression, response timeMobile-Friendly Checker
LinksLinks to your own pages, links out, links with no textBroken Link Checker

Each check comes back as Pass, Check (worth improving) or Fail (fix this), with the reason in plain words. Where it can, the checker uses exactly the same logic as our single-purpose tools, so a result here matches what you'd see there.

How the SEO score works

Every check that passes is worth one point, every Check is worth half a point and every Fail is worth nothing. The score is your points divided by the number of checks that apply, out of 100. A page with 20 passes, 1 check and 1 fail scores 93.

We show a score because it makes progress visible: fix two warnings and watch it move. But we don't hide what's behind it, and we don't weight things in secret. A page can score 100 and still not rank if the content doesn't answer the search better than the pages already there.

Real example: our sitemap guide, scored

We ran the checker on our guide What Is a Sitemap?. It scored 98/100, passing 21 of 22 checks: the page loads, robots.txt and noindex allow it, the canonical points to itself, it's in the sitemap, the title fits at about 588px, there's one H1 with 33 headings in order, Open Graph and structured data are set, the HTML is 92 KB and Brotli-compressed, and it links to 60 of our own pages.

The one warning was useful: the 153-character meta description measures about 1,003 pixels, wider than the roughly 920 Google shows on desktop, so the end would likely be cut. A character count alone would have passed it.

What to fix first

  1. Anything in "Can Google index it?" A noindex tag, a robots.txt block or an error status makes every other fix pointless. Our guide to why a page isn't indexed covers each cause.
  2. The title and description. They're what people read in the results. See how to write meta titles and descriptions.
  3. The H1 and heading order, so readers and search engines can follow the page.
  4. Sharing tags and structured data, so the page looks right when shared and is easy for search engines and AI assistants to understand. Our guides to Open Graph tags and schema markup explain both.
  5. Phone basics and links: a missing viewport tag, uncompressed HTML or a page with no internal links.

On-page SEO checklist

On-page SEO checklist
CheckGood looks likeIf not
Status code200 at the address you link toFix the page or 301-redirect it
robots.txt and noindexNeither blocks the pageRemove the rule or tag if the page should rank
CanonicalPoints to the page itselfSet a self-referencing canonical
TitleFits about 600px; key words firstRewrite to 50–60 characters
Meta descriptionFits about 920px; answers the searchRewrite to 120–155 characters
H1Exactly one, naming the topicTurn extra H1s into H2s
Open GraphTitle, description and image setAdd them in your SEO plugin or page settings
Structured dataPresent and valid JSONFix the broken block or add the right type
Viewportwidth=device-width, zoom allowedAdd the standard viewport tag
Internal linksAt least a few, with descriptive textLink to related pages

What the SEO checker doesn't do

  • It checks one page. For a whole site, start with your most important pages, then follow our SEO audit guide.
  • No rankings, keywords or backlinks. Those need search data, which you'll find in Google Search Console.
  • No speed test. The response time is one measurement from our server. For real-visitor speed, see Core Web Vitals and the Mobile-Friendly Checker.
  • It reads the HTML your server sends and doesn't run JavaScript, so content added later by scripts isn't counted.
  • It can't judge content quality. Whether the page answers the searcher's question well is still the biggest factor.

An on-page SEO check on one map

Mind map: what an on-page SEO check coversSEO page check. Indexing: Loads (200), robots.txt + noindex, Canonical + https; Search result: Title by pixel width, Meta description, Google preview; Structure: One H1, Heading order, Alt text + language; Sharing + data: Open Graph, twitter:card, Structured data; Phones + links: Viewport, Size + compression, Internal links.IndexingLoads (200)robots.txt + noindexCanonical + httpsStructureOne H1Heading orderAlt text + languagePhones + linksViewportSize + compressionInternal linksSearch resultTitle by pixel widthMeta descriptionGoogle previewSharing + dataOpen Graphtwitter:cardStructured dataSEO page check
One page, every on-page basic: whether Google can index it, how it looks in results, its structure, sharing tags, phone basics and links.

Checking a page before you share it? Preview its link card with the Open Graph Checker. Planning the next page to write? Our guide to SEO competitor analysis shows how to find the searches worth targeting.

Check every page, not just this one

Owl-gorithm Hacker audits crawling, indexing and on-page basics across your whole site, and ranks what to fix first.

See Owl-gorithm Hacker

Frequently asked questions

Is the SEO page checker free?

Yes. It's free with no sign-up, within a fair-use limit, and we don't store the pages you check.

What does the SEO score mean?

Each check that passes earns one point, each one marked Check earns half, and a fail earns none; the score is the share of points out of the checks that apply to the page. It measures how many on-page basics are in place, not how well the page ranks.

Is a score of 100 enough to rank?

No. On-page basics make a page eligible and easy to understand. Rankings also depend on how well the content answers the search, links from other sites and the competition for that search.

How do I check the SEO of a whole website?

This tool checks one page at a time. For a whole site, check your most important pages here, then use a crawler: our guide to doing an SEO audit walks through the process, and Owl-gorithm Hacker audits the whole site layer by layer.

Why is my description flagged as cut off when it's under 160 characters?

Google cuts descriptions by width, not characters, at roughly 920 pixels on desktop. Wide letters and capitals use more space, so a 150-character description can still be cut. Put the key point first.

Does the checker run JavaScript?

No. It reads the HTML your server sends, like many crawlers do first. If your content or tags are added by JavaScript after the page loads, some checks will show them as missing, which is worth knowing in itself.

Why isn't there a speed score?

Real speed scores come from Google's PageSpeed Insights, which we don't call from this tool. You get the HTML size, compression and our server's response time here; for Core Web Vitals use the Mobile-Friendly Checker or PageSpeed Insights.

What should I fix first?

Anything in the indexing group first, because nothing else matters if Google can't index the page. Then the title and description, then the H1 and structure, then sharing tags and structured data.

How often should I run it?

Whenever you publish or change an important page, and after a redesign or platform move. For pages that change often, a site crawler that re-checks automatically saves time.