Get a prioritized page memo
Turn a public URL into a focused top-five list of observed raw-HTML issues before opening the full audit.
On-Page SEO Checker
Free, no signup. A concise five-item on-page memo first, with the full raw-HTML detector output available in Advanced.
General preserves the base report. A named profile adds its required-signal checks; unavailable schema guidance and pack weights stay visibly not evaluated.
Checks run from our server; we fetch the URL you enter and don't keep the results. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
Sample report
Illustrative example — deterministic raw-HTML findings, not a live site claim
For a 200 page with no title, one H1, a self-canonical, a missing meta description, and an image without alt text, the report would summarize:
Top 5 prioritized findings
2 errors · 1 warning · supporting passes and not-evaluated checks
Page title · No title element was found.
Meta description · No meta description was found.
Image alt text · One image needs review.
Primary heading · One H1 was observed.
Rendered-only checks · Not evaluated in raw-HTML mode.
How to use it
- Enter a public, crawlable page URL and choose Run report.
- Start on Simple: top 5 for the highest-priority memo.
- Open Advanced: all checks to see every supported detector, including passes and not-evaluated states.
- Verify important fixes in the rendered page and Search Console where appropriate.
+ saves the current site or page. Use ☆ beside any saved site, page, or list to favorite it. Recent check history appears below.
Create a named list
Target filled from your local choices.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Changed page? Compare a selected Wayback capture with the current page.
Rate this tool
What the results mean
- Errors (red) are clear implementation defects or strong blockers supported by the response.
- Warnings (orange) are likely issues that need context before changing the page.
- Needs review (yellow) marks evidence that cannot support a pass or error verdict yet.
- Information (blue) records useful evidence without calling it a defect.
- Pass means that specific observable rule passed, not that the whole page is optimized.
- Not evaluated means no verdict was possible and never counts as a pass.
How it works
The server retrieves the public response because browser cross-origin rules prevent direct inspection. The page context normalizes the final URL, status, headers, and raw HTML, then a deterministic detector registry runs supported technical and on-page checks. The Simple memo prioritizes the same results; it does not use a separate opaque score.
Features
- Five-item prioritized memo plus complete detector output.
- Checks across metadata, headings, canonicals, directives, links, images, and supported markup.
- Hreflang cluster validation follows up to 500 declared URLs with at most six concurrent fetches.
- Evidence-based pass, warning, error, information, and not-evaluated states.
- Escaped output and no fabricated verdicts when evidence is unavailable.
Limitations
This checker does not render JavaScript, run Lighthouse, measure Core Web Vitals, assess accessibility, score writing quality, inspect backlinks, or predict rankings. Hreflang detail shown on the page and in coverage samples is bounded even when validation reaches the 500-URL ceiling. A fetch can also differ from Googlebot because it originates from this site's server infrastructure. Confirm rendered and index-level behavior with purpose-built tools.
Frequently asked questions
What does an on-page SEO checker analyze?
This checker analyzes signals available in the server-returned HTML and response metadata, including titles, descriptions, headings, canonicals, robots directives, links, images, and supported structured-data patterns.
Is a passing report a guarantee that the page will rank?
No. The report identifies observable implementation issues. Rankings also depend on relevance, content quality, competition, authority, internal linkingAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them., and signals this raw-HTML tool cannot measure.
Why does the report say not evaluated?
Not evaluated means the checker lacks the evidence or rendering capabilityTurning HTML, CSS, and JavaScript into the final visual page and DOM. needed for a responsible verdict. It is different from a pass and keeps unavailable checks from inflating the result.
Does the checker render JavaScript?
No. It analyzes the raw HTML response. Use a rendered-page tool when a JavaScript application changes metadata, headings, content, or links after load.
Which findings should I fix first?
Start with errors that can prevent crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., or a useful search result, then address warnings that affect page meaning. The Simple tab prioritizes five findings using the same detector results shown in Advanced.
Feature requests for On Page Seo Checker
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Where this tool helps
Common use cases
Review a page before launch
Check headings, links, images, favicons, social metadata, and related on-page signals on a staging-accessible or public page.
Investigate a ranking or snippet change
Use the advanced evidence groups to find metadata, indexability, or content-structure changes worth validating.
Verify a targeted repair
Rerun the same URL after deployment and compare the observed findings rather than relying on the score alone.
Watch the full workflow
On-Page SEO Checker walkthrough
Read the transcript
On-Page SEO Checker
A useful on-page report should surface blockers first while preserving the evidence and the checks it could not perform. I’ll show you how to run the report, choose a page profile, use the Simple top-five memo, inspect every Advanced detector, read the search preview, hreflang and tag evidence, export a bundle, understand raw-H-T-M-L limits, and verify fixes.
Step 1
Use this checker for launches, migrations, template changes, and page-level diagnostics. It analyzes observable response headers and raw H-T-M-L, then prioritizes five findings from the same transparent detector results available in the complete report.
Step 2
Enter a public crawlable page U-R-L and select General or a named page profile. Profiles add required-signal checks from a dated pack. Unavailable schema guidance or weights remain visibly not evaluated instead of silently changing an opaque score.
Step 3
Begin with errors that can prevent crawling, indexing, or a useful search result. Then review warnings affecting meaning or consistency. Passes support one specific rule; they never mean the entire page is optimized or likely to rank.
Step 4
This walkthrough uses fictional example dot com evidence and does not imply a live fetch. A real run retrieves the response, normalizes its final U-R-L, status, headers, and raw H-T-M-L, then runs the deterministic detector registry.
Step 5
The Simple tab summarizes counts and the five highest-priority results with rationale. Errors are supported implementation defects, warnings need context, information records useful evidence, and not evaluated means the tool could not responsibly reach a verdict.
Step 6
The local search preview helps review observed title and description text, likely truncation, and obvious fallback. It is not a live Google result and cannot reproduce query-dependent rewrites, device differences, or result-page experiments.
Step 7
Open Advanced to see every check grouped by category, including passes and unavailable states. Use the evidence to trace a finding to headers, metadata, headings, links, images, directives, or supported structured markup. The memo and Advanced view use the same results.
Step 8
When hreflang is declared, the tool follows a bounded cluster with capped concurrency and visible coverage. Missing evidence remains not evaluated. No declarations can be not applicable, and x-default is optional; absence alone is not an error.
Step 10
Export the audit bundle to preserve the target, detector results, acquisition state, profile, bounded hreflang evidence, and tag observations. After a change, import the saved bundle to count structured differences without relying on screenshots alone.
Step 11
The checker does not render JavaScript, run Lighthouse, measure Core Web Vitals, assess writing quality or accessibility, inspect backlinks, or predict rankings. Its server fetch can differ from Googlebot, and hreflang detail is bounded. Confirm important behavior with purpose-built tools.
Step 12
Fix blockers and inconsistencies in the shared template or content source, then rerun the report. Verify rendered metadata and links, validate schema and hreflang, test performance separately, and confirm indexing in Search Console. Compare the new bundle to document what actually changed.
Prioritize blockers—verify every important fix.
Fix supported crawl, indexing, canonical, metadata, and markup issues at their shared source. Re-fetch the page, inspect the rendered D-O-M, validate structured data and hreflang, and confirm index-level behavior in Search Console. Compare an exported bundle after deployment without treating a passing raw-H-T-M-L rule as a ranking guarantee.
Common issues & how to fix them
- Warning Primary H1 is missing Fix: Add one descriptive H1 that clearly states the page’s primary topic.
- Warning Heading hierarchy skips levels Fix: Restructure headings into a sequential hierarchy that reflects section nesting.
- Information Low visible text volume Fix: Review whether the observed text is complete for the page’s purpose. Add useful information only when something material is missing; do not pad the word count.
- Warning Title is near-duplicate of another signal Fix: Differentiate the title from competing page signals so it uniquely identifies this page’s intent.
- Warning Images lack alt attributes Fix: Add concise alt text to meaningful images and empty alt attributes to decorative images.
- Warning Links are non-navigational Fix: Give each navigational link a valid href and descriptive accessible text, or use a button for non-navigation actions.
- Error Title element is missing Fix: Add one non-empty, page-specific title element in the initial HTML.
- Warning Meta description is missing Fix: Add a concise page-specific meta description in the initial HTML.
- Error Noindex directive is present Fix: Remove noindex from pages meant to be indexed, or keep it only when exclusion is intentional.
- Warning Canonical is missing Fix: Add one absolute rel=canonical URL for the preferred indexable version.
- Information Structured data is absent Fix: Add supported structured data only when it accurately describes visible page content.
- Error Title elements contain conflicting values Fix: Keep one non-empty title element in the document head and remove every competing title value.
- Warning Robots directive is outside the HTML head Fix: Move the intended robots meta directive into the document head and remove ineffective body declarations.
- Warning Robots directive combination is ineffective Fix: Add the prerequisite robots directive or remove the ineffective token, then verify the effective Googlebot policy.
- Warning Canonical element is outside the HTML head Fix: Move the intended canonical link into the document head and remove body-level canonical declarations.
- Warning Noindex and canonical are combined Fix: Confirm whether exclusion or consolidation is intended, then remove the signal that conflicts with that outcome.
- Warning Robots.txt prevents Googlebot from seeing noindex Fix: Allow Googlebot to crawl the page while noindex removal is required, then verify that the directive can be processed.