↑↓ to move · Enter to open · Esc to close

Website SEO Analyzer

Run a one-page SEO analyzer on our server to inspect titles, meta tags, headings, links, schema, robots rules, and response details. Nothing is stored.

This check runs on our server. The address you enter is used only for this check and is not stored.
Built by · Updated

Mode: SEO overview

Tick the box to show you are not a robot, then press Check.

How to use the Website SEO Analyzer

  1. Enter the full page URL.
  2. Start the analyzer.
  3. Review each pass, warning, or fail item and fix the page template or response headers as needed.

How it works

The analyzer fetches one HTML page, follows up to three redirects, and reads the final response without running JavaScript. It reports the final URL, HTTP status, fetch time, and redirect chain. It also reads head tags, headings, HTML text, image alt attributes, JSON-LD, and robots.txt sitemap references.

Indexing checks combine robots and Googlebot meta tags with applicable X-Robots-Tag response headers. A noindex or none rule produces a fail even when another tag says index. Canonical checks warn when the target differs from the fetched URL or HTML and HTTP canonical declarations conflict. A different canonical can be intentional; the report asks you to verify it.

Pass, warning, fail, and informational results describe these checks only. Word count is informational. The report does not assign a Google quality score or confirm that a page is indexed.

Examples

Example report

This illustrative example is for a page at https://example.com/draft with no meta description, a canonical pointing to https://example.com/another-page, and an X-Robots-Tag: noindex header. It is not a live scan of example.com.

CheckResultWhat to review
Meta descriptionFail: missingAdd a specific description if the page needs one.
Canonical URLWarning: another URLConfirm which page is the preferred version; a different target can be intentional.
Indexing directivesFail: HTTP noindexRemove the blocking rule only if this page should appear in search.
HTML text countInformationalJudge whether the page serves its purpose, rather than chasing a word-count threshold.

A redirect from HTTP to HTTPS can still return a successful final page. When redirects occur, the report lists each received status, source URL, and Location value. Malformed JSON-LD is reported separately from the other checks.

What each check looks for

CheckWhat the result means
Title tagMissing titles fail. The 20 to 65 character range is an internal readability guideline; other lengths warn.
Meta descriptionMissing descriptions fail. The 70 to 170 character range is an internal guideline; other lengths warn.
Canonical URLA matching target passes. A different target or a conflict between HTML and HTTP canonicals warns.
Indexing directivesApplicable robots, Googlebot meta, and X-Robots-Tag rules contain no noindex or none instruction.
Main headingOne H1 passes this structural check. Missing or repeated headings need review.
HTML text countInformational only; there is no word-count pass threshold.
HTML language and charsetA lang attribute and a declared charset were found.
ViewportA viewport meta tag was found.
Open Graphog:title, og:description, and og:image were found.
Image alt textSampled images have non-empty alt attributes. Decorative images can correctly use empty alt text and need manual review.
Structured dataJSON-LD parses; this does not validate eligibility for a Google rich result.

The analyzer applies its own audit rules, which are not Google indexing requirements. A pass does not guarantee ranking or indexing, and a warning does not automatically mean the page should be changed.

Writing a title tag that gets clicked

Write a concise title that describes the page in the words its readers use. Put the main topic where it is easy to see and keep branding brief. Google can rewrite title links and truncates them to fit the available device width; there is no fixed character or 600-pixel limit that applies to every result.

Give each page a title that identifies its own purpose. A meta description can help explain that purpose, but Google may generate a different snippet. Use the SERP preview tool for an estimate, and read Google's title-link guidance for the limits of that preview.

Limitations

  • The analyzer checks one page at a time. It is not a site crawler.
  • It reads the HTML the server receives and does not run JavaScript, so client-rendered tags or content can be missed.
  • The page fetch is capped at 5 MB to keep checks predictable.

The report does not measure content originality, backlinks, keyword relevance, real-user performance, or whether Google has indexed a URL. It checks noindex and none rules for Google web search; it is not a full crawler-permission emulator. A canonical warning does not prove that the declared target is wrong.

Frequently asked questions

How long should an SEO title be?

Use a concise, descriptive title. This analyzer uses 20 to 65 characters as an internal guideline, not a Google limit. Google may truncate or rewrite title links depending on the device and query.

Does the analyzer check links?

It counts the internal and external links in the page HTML. It does not follow them, so use the broken link checker to test whether each one works.

Why is there no overall SEO score?

A single score hides the actual problems. This report lists what passed, what needs work, and why.

Does the analyzer render JavaScript?

No. It checks the raw HTML response only.

Can I use this for a whole site audit?

Not directly. It is built for one page per request, which makes the result easier to understand and keeps the server-side check within its limits.

Often used together with Website SEO Analyzer.

  • Google SERP PreviewDeveloper Tools

    Previews how a title and meta description may appear in Google results.

  • Robots.txt GeneratorDeveloper Tools

    Creates robots.txt rules for search and AI crawlers and tests URLs against them.