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:
2 errors · 1 warning · supporting passes and not-evaluated checks
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 linking, 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 capability 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 crawling, indexing, 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.
À propos de l’outil
Obtenez un mémo on-page priorisé sur cinq points et des contrôles avancés du HTML brut couvrant titres, liens, images, favicons et métadonnées sociales.
Fonctionnalités
- Priorisation des constats les plus importants pour la page.
- Contrôles des titres, liens, images, directives robots et éléments canonical.
- Vérification des favicons et signaux Open Graph ou Twitter.
- Preuves conservées dans le HTML analysé pour faciliter la revue.
Fonctionnement
Le moteur analyse le HTML brut, regroupe les signaux par surface et hiérarchise les cinq constats prioritaires avant d’exposer les contrôles détaillés. Chaque recommandation conserve le signal observé afin que la correction puisse être vérifiée dans une nouvelle analyse.
Limites
- Le mode URL dépend de la réponse HTML reçue et ne voit pas les changements ajoutés uniquement par JavaScript.
- Les recommandations donnent un contexte technique, pas une promesse de classement.
- Les signaux sociaux et les données structurées doivent être vérifiés dans leur contexte de publication.
Questions fréquentes
L’outil remplace-t-il un audit complet de site ?
Non. Il fournit une analyse ciblée d’une page ; utilisez un crawl séparé pour couvrir l’ensemble du site.
Les recommandations sont-elles des pénalités automatiques ?
Non. Elles indiquent des signaux à examiner et doivent être interprétées selon le contenu, le modèle et l’objectif de la page.
Pourquoi un signal injecté par JavaScript manque-t-il ?
Le contrôle analyse la réponse HTML brute. Fournissez le HTML rendu si une application ajoute le signal côté client.