Paste a URL, wait a few seconds, get a score out of 100 and a list of exactly what's wrong. That's the whole job of an on-page SEO checker. It reads a page the way a basic crawler does and reports the signals that decide whether search engines — and now AI answer engines — can understand and rank it.

Here's what a good free checker actually looks at, how to read the result, and where these tools stop. (Full disclosure: we built a free SEO checker, so the examples come from ours — but every check below is standard.)

What "on-page SEO" means

On-page SEO is everything a search engine reads from the page itself, before it ever looks at your backlinks. Three buckets matter most:

  • The basics that show in search: the <title> and meta description. These become your blue link and the grey text under it.
  • Structure: one clear <h1>, sensible <h2> subheadings, a canonical tag, and a lang attribute.
  • Machine signals: Open Graph tags (for social previews), JSON-LD structured data (for rich results), and a viewport tag (so Google treats the page as mobile-friendly).

A checker pulls all of these in one request, so you're not viewing source and counting tags by hand.

Reading the report

A typical result is a score plus a pass / improve / fail list. Don't obsess over the number — read the reds first. The ones that move rankings fastest:

  • Missing or too-long title — aim for roughly 30–60 characters, with your main phrase near the front.
  • Missing meta description — around 70–160 characters. It won't rank you, but it lifts click-through.
  • No H1, or several H1s — one per page.
  • noindex in the robots meta — this quietly tells Google not to index the page. It's the single most common "why isn't my page showing up" cause.
  • No viewport tag — the page is treated as not mobile-friendly, which hurts on mobile-first indexing.

Yellow items (few Open Graph tags, thin word count, a slow server response) are worth fixing but rarely urgent.

The checks people forget

The interesting part of a modern audit isn't the title tag — it's the technical and forward-looking signals.

  • robots.txt and sitemap. Does the site have a valid robots.txt? A valid XML sitemap? Is the sitemap declared inside robots.txt so crawlers find it? If you don't have one yet, a sitemap generator builds it in your browser, and our guide covers how to submit a sitemap to Google.
  • Security headers. HSTS, a content-security-policy, X-Content-Type-Options, and a referrer policy. These are quiet trust signals and easy wins.
  • AI-search access (AEO). This one is new. Your robots.txt can allow or block AI crawlers like GPTBot, ClaudeBot and PerplexityBot. If it blocks them, your content simply won't appear in ChatGPT, Claude or Perplexity answers. A good checker tells you whether you're visible to answer engines — most tools still don't look at this.

What a free checker can't do

Be honest with yourself about the ceiling. On-page tools read the page. They do not have a backlink index or keyword search volumes, because those require crawling a large slice of the web — an infrastructure that costs tens of millions of dollars a year. So:

  • A free checker can tell you your page is technically sound. It cannot tell you your domain is too weak to rank yet.
  • For a rough, free authority number, some tools add Open PageRank (built on Common Crawl data) — useful as a directional signal, not a substitute for a paid backlink tool.
  • For your own site's real ranking and click data, nothing beats Google Search Console — it's free and uses Google's own numbers.

When you outgrow the free ceiling and need actual search volumes and a backlink index, the budget-friendly paid route we use is Mangools: <a href="https://mangools.com/kwfinder#a6a5d5ec16aee08a669ebbee9" rel="sponsored noopener" target="_blank">KWFinder</a> for keyword volume and difficulty, and <a href="https://mangools.com/linkminer#a6a5d5ec16aee08a669ebbee9" rel="sponsored noopener" target="_blank">LinkMiner</a> for checking any site's backlinks. It's a fraction of the price of the enterprise suites, and there's a free tier to test with. (Disclosure: those two are affiliate links — they cost you nothing and support the free tools on this site.)

A checker also reads the raw HTML, so heavily JavaScript-rendered pages (single-page apps) can look emptier than they are. Googlebot renders JS; a lightweight fetcher doesn't. If your title shows as empty on a React/Vue app, that's usually why.

A 60-second routine

Run this on any page you care about:

  1. Paste the URL into an on-page SEO checker and read the reds.
  2. Fix the title and meta description first — they're fast and they show in search. A meta tag generator helps you write them with a live preview.
  3. Confirm one H1, a canonical tag, and no accidental noindex.
  4. Check that robots.txt and the sitemap exist and agree with each other.
  5. Run the built-in Lighthouse test for real speed scores, and fix anything red there.

Repeat after every meaningful edit. Most on-page problems are five-minute fixes — the hard part is just seeing them.

Bottom line

An on-page SEO checker won't build your authority or write your content. It removes the guesswork about whether search engines can read the page you already have. Start with a free SEO checker, fix the reds, and re-run it — that loop alone puts you ahead of most sites, which never check at all.