Idiomas

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.

Built by Patrick Stox

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.

Feedback
Report a bug

Found something broken in On Page Seo Checker? Let us know what happened — this goes straight to a private triage queue, not a public list.

What will be sent 
 No tool inputs, uploads, pasted source, complete results, query parameters, or URL fragments are attached automatically. You can edit or remove the selected passage above. Browser and anti-abuse metadata is processed for spam prevention. 
  
 
  
 
 
  
 
 
  
 
 
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
  1. Enter a public, crawlable page URL and choose Run report.
  2. Start on Simple: top 5 for the highest-priority memo.
  3. Open Advanced: all checks to see every supported detector, including passes and not-evaluated states.
  4. Verify important fixes in the rendered page and Search Console where appropriate.
 
 
 
       
     
     
 
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.
 
 
Next stepContent Gap Analyzer — look up the exact spec and expected values.

People also explore
ToolHeading Structure CheckerToolLink AnalyzerToolImage SEO CheckerArticleAlt TextArticleThe HTML lang AttributeArticleRanking in Google Images
 
 
 
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.

   
Loading…
  
  ➕ Request a feature   
New requests are reviewed before they appear here.
 
     
  
  
 
 
 
 
   
 
       
Sobre a ferramenta
Grátis, sem cadastro. Um concise five-item on-page memo primeiro, com o completo raw-HTML detector saída disponível em Advanced.
Um prioritized on-page SEO relatório de raw HTML e observable resposta cabeçalhos.
Recursos
  • Features Five-item prioritized memo plus Concluído detector saída. Verificações across metadados, headings, canonicals, directives, links, images, e compatível marcação. Hreflang cluster validação follows up para 500 declared URLs com em most six concurrent busca. Evidence-based pass, aviso, Erro, information, e não avaliado states. Escaped saída e Não fabricated verdicts quando evidência é indisponível.
  • Este verificador analyzes signals disponível em o server-returned HTML e resposta metadados, including titles, descriptions, headings, canonicals, robots directives, links, images, e compatível structured-data patterns.
  • Como usar Enter um público, crawlable página URL e escolha Run relatório . Start em Simple: top 5 para o highest-priority memo. Abrir Advanced: todas verificações para see cada compatível detector, including passes e não avaliado states. Verifique importante correções em o rendered página e Search Console onde appropriate.
  • O que os resultados significam: Erros (vermelho) são defeitos claros de implementação ou bloqueios fortes respaldados pela resposta. Avisos (laranja) são problemas prováveis que precisam de contexto antes de alterar a página. Precisa de revisão (amarelo) marca evidências que ainda não sustentam um veredito de aprovação ou erro. Informação (azul) registra evidência útil sem chamar isso de defeito. A aprovação significa que aquela regra observável passou, não que a página inteira esteja otimizada. Não avaliado significa que nenhum veredito foi possível e nunca conta como aprovação.
Como funciona
Como funciona O servidor retrieves o público resposta porque navegador cross-origin rules prevent direto inspeção. O página contexto normalizes o final URL, status, cabeçalhos, e raw HTML, então um determinístico detector registry runs compatível técnico e on-page verificações. O Simple memo prioritizes o mesmo resultados; isso faz não usar um separate opaque pontuação.
Limitações
  • Limitations Este verificador faz não render JavaScript, run Lighthouse, measure Core Web Vitals, assess accessibility, pontuação escrita quality, inspecionar backlinks, ou predict rankings. Hreflang detail mostrado em o página e em coverage amostras é limitado even quando validação reaches o 500-URL ceiling. Um buscar pode also differ de Googlebot porque isso originates de este site's servidor infrastructure. Confirm rendered e index-level comportamento com purpose-built ferramentas.
  • Não. Isso analyzes o raw HTML resposta. Usar um rendered-page ferramenta quando um JavaScript application alterações metadados, headings, conteúdo, ou links depois load.
Perguntas frequentes
Que constatações deve I corrigir primeiro?
Start com erros que pode prevent rastreamento, indexação, ou um useful pesquisa resultado, então address avisos que affect página meaning. O Simple tab prioritizes cinco constatações using o mesmo detector resultados mostrado em Advanced.
Faz o verificador render JavaScript?
Não. Isso analyzes o raw HTML resposta. Usar um rendered-page ferramenta quando um JavaScript application alterações metadados, headings, conteúdo, ou links depois load.
É um passing relatório um garantia que o página will classificação?
Não. O relatório identifies observable implementation problemas. Rankings also depende em relevance, conteúdo quality, competition, authority, internal linking, e signals este raw-HTML ferramenta cannot measure.
Por que faz o relatório say não avaliado?
Não avaliado means o verificador lacks o evidência ou rendering capability needed para um responsible verdict. Isso é different de um pass e keeps indisponível verificações de inflating o resultado.
O que faz um on-page SEO verificador analisar?
Este verificador analyzes signals disponível em o server-returned HTML e resposta metadados, including titles, descriptions, headings, canonicals, robots directives, links, images, e compatível structured-data patterns.