On-Page SEO: Complet Guide
A practical map of lune page-level signals vous contrôler, ce que chaque un peut influence, and où to trouver le site's detailed implementation guides.
Langues
1 indice probant sur cette page
- Outil en ligne associéOn-Page SEO Checker
On-page SEO is lune page-level fonctionner vous contrôler: the réponse and evidence in the principal content, HTML structure, headings, lien internes, titles and snippets, images, and données structurées. Ne faites pas collapse ceux elements into un liste of ranking factors. Some aider a search system match and rank une page; some faire lune page eligible to be indexé or affiché in a particulier fonctionnalité; some influence how le résultat is presented; and some primarily aider personnes utiliser and comprendre lune page. Commencer by making lune page's objectif and réponse clair, alors vérifier que the rendered HTML exposes the intended content and signals. Utiliser ce guide to choisir the correct subguide, and utiliser the separate on-page checklist quand vous are ready to execute an audit.
TL;DR — On-page SEO is the fonctionner vous do on an individual page to faire its objectif, réponse, structure, and search presentation clair. Le contenu and its usefulness come premier. Titles, headings, liens, images, metadata, and structured données chaque have différent jobs; none is a magic score. Ce page maps ceux jobs and sends vous to the correct detailed guide. Quand vous besoin a step-by-step audit, utiliser the on-page SEO checklist.
Ce que on-page SEO is
On-page SEO is the définir of page-level choices vous contrôler que aider personnes and search systems comprendre, evaluate, navigate, and présent une page.
Que inclut:
- the question or task lune page sert;
- the principal réponse, supporting evidence, and utile detail;
- the HTML que exposes le contenu and relationships;
- the title, headings, lien internes, images, and metadata;
- données structurées que accurately describes eligible visible content;
- accessibility choices que faire lune page usable by plus personnes.
It fait pas mean every element fait the même job. Que shortcut creates bad priorities. A meta description is a snippet candidate que Google may utiliser quand it meilleur describes lune page pour a requête. Données structurées peut créer eligibility pour pris en charge résultats enrichis sans guaranteeing un. Texte alternatif helps accessibility and image understanding. A clair réponse peut aider relevance, but relevance ne fait pas guarantee a top ranking.
Evidence for this claim Google primarily creates snippets from page content and may use the meta description when it better describes the page for a query. Scope: production Confidence: high · Verified: Control your snippets in search resultsThe four jobs mental model
Put every proposed on-page modifier into un or plus of ces jobs:
| Job | Question | Exemples | Ce que success semble comme |
|---|---|---|---|
| Relevance and quality | Fait lune page satisfy the searcher’s task with clair, reliable information? | principal content, entities, evidence, descriptive headings, internal context | the correct audience trouve and uses the réponse |
| Eligibility and accès | Peut the system récupérer, parse, index, and considérer the intended material or fonctionnalité? | indexable HTML, crawlable liens, valid pris en charge données structurées | lune page or fonctionnalité peut enter the candidate définir |
| Presentation | How may le résultat be represented avant a click? | title element, headings utilisé as title sources, meta description, image preview contrôle | the affiché result accurately sets expectations |
| Accessibility and usability | Peut personnes perceive, navigate, and comprendre lune page? | heading hierarchy, meaningful liens, alt decisions, readable structure | personnes peut complet the task with fewer barriers |
Ces jobs overlap, but ils ne sont pas interchangeable. Passing a structured-data validator ne fait pas faire weak content utile. Writing a strong meta description fait pas faire a blocked page indexable. Ajout keywords to every heading ne fait pas repair a misleading réponse.
Commencer with lune page’s job
Avant editing tags, écrire un sentence:
Ce page helps [audience] complet [task] by providing [réponse or outcome].
Alors tester lune page contre it:
- Is the réponse visible sans forcing the reader via a long preamble?
- Fait lune page cover the decisions and evidence the task genuinely exige?
- Is the scope différent from nearby pages, or are several URLs competing to do the même job?
- Do the title and principal heading accurately décrire lune page personnes reach?
- Peut someone navigate the sections, liens, and images sans guessing?
Google’s current SEO Starter Guide puts utile, well-organized, people-first content ahead of mechanical tricks and dit là are aucun secrets que automatically rank a site premier.
Utiliser the library by problem
Ce site déjà has detailed subguides. Utiliser ce hub to choisir un plutôt que trying to appliquer every tactic to every page.
Le contenu is hard to scan or its hierarchy is unclear
Commencer with header tags. It explique H1–H6, heading nesting, multiple H1s, and the difference entre semantic structure and visual styling.
Important content or signals are manquant from the HTML
Utiliser HTML SEO pour parsing, rendered output, semantic elements, crawlable liens, language markup, and malformed-head échecs.
Images are heavy, inaccessible, or hard to découvrir
Utiliser image SEO pour discovery, page context, filenames, responsive images, alt decisions, formats, and performances. Recherche d’images and page-speed fonctionner overlap, but ils ne sont pas the même objective.
Le résultat title, snippet, or robots contrôle besoin fonctionner
Utiliser meta tags pour title tags, meta descriptions, robots directives, snippet contrôle, favicons, and social preview metadata. A tag’s job doit be evaluated separately; là is aucun utile universal “meta tag score.”
Vous besoin explicit machine-readable meaning or rich-result eligibility
Utiliser données structurées pour schema.org, JSON-LD, pris en charge Google fonctionnalités, validation, and type-specific guides. The markup doit match visible content, and valid markup n’est pas a afficher or ranking guarantee.
Evidence for this claim Accurate supported structured data can make content eligible for supported search features, but valid markup does not guarantee that a feature will be displayed or improve rankings. Scope: production Confidence: high · Verified: Understand how structured data worksVous are ready to inspect a réel page
Utiliser the on-page SEO checklist. It owns the prioritized execution sequence. Ce hub explique the system and routes the fonctionner; the checklist indique vous ce que to inspect and in ce que order.
Ce que on-page SEO ne peut pas fix
On-page fonctionner ne peut pas compensate pour every upstream problem. Déplacer to the appropriate technical guide quand:
- l’URL ne peut pas be découvert or crawled;
- rendering hides the principal content;
- canonicalization points elsewhere;
- a
noindexrule empêche indexation; - the incorrect page owns the search intent;
- the architecture du site leaves lune page orphaned;
- external reputation, competition, or demand is the réel constraint.
On-page SEO is un couche in a search system, pas the whole system.
TL;DR — Treat une page as a contract entre intent, evidence, rendered HTML, retrieval signals, presentation contrôle, and human usability. Diagnose the failed couche avant modification copy. Separate candidate eligibility from relevance, ranking, result assembly, and accessibility. Maintain un owning URL per task, route specialized implementation to the existing subcluster guides, and validate les deux source/rendered output and observed search behavior.
Model lune page as a layered contract
A utile on-page examiner follows lune page via several layers:
- Task ownership: qui audience, question, and outcome ce URL owns.
- Réponse: the direct réponse, traiter, evidence, exemples, and limitations.
- Information structure: sections, headings, listes, tables, and relationships.
- HTML exposure: ce que apparaît in the initial réponse and rendered DOM.
- Search contrôle: title sources, snippet contrôle, index directives, canonicals, and pris en charge données structurées.
- Connections: lien internes into and out of lune page, with utile anchor text.
- Media: discoverable images and video, accessible alternatives, and performances.
- Observed outcome: indexation, requête fit, result presentation, usage, and business behavior.
A échec décrit as “on-page” peut begin in quelconque couche. A manquant réponse may be an editorial gap. A manquant réponse in rendered HTML may be a rendering defect. A correct title element que n’est pas affiché may be a result-assembly choice plutôt que a broken tag.
Separate the gates
The la plupart important avancé distinction is entre entering a candidate définir and winning dans it.
| Couche | Typical question | Evidence | Ne faites pas conclude |
|---|---|---|---|
| Discovery/accès | Peut the system reach l’URL and resources? | liens, réponse, robots, render | que accès signifie indexation |
| Index/eligibility | Peut lune page or fonctionnalité be considéré? | canonical/index state, pris en charge markup, policies | que eligibility guarantees afficher |
| Relevance | Fait le contenu réponse ce requête or subtask? | query-page comparison, passage coverage | que relevance alone determines rank |
| Ranking/reranking | Qui eligible candidates are preferred? | observed results and controlled tests | a fixed public weight pour un element |
| Presentation | Qui title, snippet, image, or fonctionnalité is affiché? | live result and Search Console context | que supplied metadata is toujours utilisé |
| Accessibility | Peut personnes operate and comprendre lune page? | manual and assistive-technology testing | que an SEO robot d’exploration proves conformance |
The practical benefit is meilleur prioritization. Si lune page is non indexée, rewriting the meta description is downstream of the réel problem. Si a rich result is absent, premier establish eligibility, alors remember que Google ne fait pas guarantee afficher.
Design a content contract
Pour every important page class, define:
- the owning intent and excluded intents;
- l’URL canonique and attendu index state;
- the requis réponse blocks and evidence owners;
- acceptable freshness and examiner triggers;
- title and heading generation rules;
- requis internal-link relationships;
- media and alternative-text rules;
- structured-data eligibility and visible-content dependencies;
- validation checks and accountable team.
Ce is plus durable que a one-time score. It aussi rend template regressions testable avant publication.
Route the implementation to its owner
Header system
The header-tags hub owns heading levels, H1 questions, hierarchy, and navigation implications. Utiliser headings to expose a logical outline and utile section étiquettes; ne faites pas invent a ranking-weight ladder pour H1–H6.
HTML system
The HTML SEO hub owns source-versus-rendered HTML, semantic HTML, crawlable anchors, language attributes, and parsing échecs. Google’s lien guidance is explicit à propos de crawlable anchor markup and utile anchor text.
Image system
The image SEO hub owns image discovery, responsive delivery, page context, filenames, texte alternatif, and image performances. Google’s current image guidance distinguishes discoverable HTML image elements from CSS background images and connects texte alternatif with les deux image understanding and accessibility.
Metadata system
The meta-tags hub owns title and snippet inputs, robots metadata, snippet limites, and social metadata. Google may assemble title liens from several page signals and usually builds snippets from page content, parfois en utilisant the meta description. Supplied text is an input, pas an instruction que doit be affiché.
Evidence for this claim Google primarily creates snippets from page content and may use the meta description when it better describes the page for a query. Scope: production Confidence: high · Verified: Control your snippets in search resultsStructured-data system
The structured-data hub owns schema.org vocabulary, formats, feature-specific requirements, and validation. The Schema.org documentation defines the shared vocabulary, pendant que Google’s structured-data introduction frames markup as standardized clues pour understanding and pris en charge search fonctionnalités; it ne fait pas turn markup into a general ranking guarantee.
Manage overlap and cannibalization
Two pages peut mention the même entity sans competing. The problem is ambiguous ownership of the même reader task.
Utiliser a simple ownership record:
| Field | Exemple |
|---|---|
| Owning task | Expliquer the on-page system and route to detailed guides |
| Principal audience | Someone deciding ce que kind of on-page fonctionner is nécessaire |
| Requis réponse | scope, mental model, library map, diagnostic routing |
| Explicit exclusion | step-by-step audit execution |
| Handoff | on-page SEO checklist |
Quand two URLs apparaître to propre the même task, choisir an owner, narrow the autre page, strengthen the linking relationship, and confirmer the titles and introductions reflect the distinction. Ne faites pas merge pages solely parce que a outil reports overlapping words.
Tester changements as hypotheses
An on-page edit devrait state:
- Problem: ce que observed behavior is incorrect?
- Couche: task, content, HTML, eligibility, presentation, or accessibility?
- Modifier: ce que unique material variable va be altered?
- Attendu observation: ce que devrait modifier, où, and pour whom?
- Window: quand va exploration, processing, and trafic cycles faire evaluation fair?
- Guardrail: ce que utilisateur or business outcome doit pas obtenir worse?
Pas every page supports a causal SEO tester. Pour a low-traffic page, the honest result may be “implementation verified; performance effect not determined.”
The executive view
On-page SEO is a portfolio of page-level product contrôle, pas a copywriting cleanup. It determines si chaque page has a clair job, exposes a reliable réponse, presents itself accurately, and connects to the rest of le site.
Fund fonctionner in ce order:
- pages tied to material utilisateur and business tasks;
- template defects affecting nombreux valuable URLs;
- accès, index, or eligibility échecs;
- misleading or weak réponses and result presentation;
- reusable accessibility and content-quality contrôle;
- cosmetic cleanup with aucun demonstrated consequence.
Demander teams to report affected cohorts and outcomes, pas counts of “SEO errors.” A title problème on a major product template and a manquant meta description on an archived page ne doit pas recevoir equal priority.
The durable deliverable is une page-class contract with an owner, tests, and a examiner cadence. The on-page SEO checklist peut alors be utilisé as the operational inspection couche.
On-page SEO in un compact model
- On-page SEO covers lune page-level réponse, structure, HTML, liens, metadata, media, and données structurées vous contrôler.
- Classify fonctionner by relevance/quality, eligibility/accès, presentation, and accessibility/usability.
- The jobs overlap but ne sont pas substitutes: eligibility ne fait pas guarantee afficher, supplied metadata may be rewritten, and accessibility exige plus que an SEO robot d’exploration.
- Faire lune page’s owning task and direct réponse clair avant optimizing tags.
- Utiliser the dedicated hubs pour header tags, HTML SEO, image SEO, meta tags, and données structurées.
- Utiliser the on-page SEO checklist pour execution; ce hub owns the conceptual map and routing.
Principal documentation
- Google SEO Starter Guide — utile content, organization, liens, titles, snippets, and images in un bounded introduction.
- How Recherche Google fonctionne — separates exploration, indexation, and serving, qui empêche downstream on-page fonctionner from being blamed pour upstream échecs.
- Influencing title liens — the title element is un source Google may utiliser; clair, concise, accurate titles are the goal.
- Contrôler snippets — snippets are usually drawn from page content and may utiliser the meta description.
- Google image SEO meilleur practices — image discovery, HTML elements, context, filenames, texte alternatif, and performances.
- Structured-data introduction and general guidelines — eligibility, accuracy, visible-content, and feature-specific requirements.
- Google lien meilleur practices — crawlable anchors and descriptive lien text.
- W3C WAI heading tutorial — en utilisant headings to communicate organization and prise en charge navigation.
- W3C WAI accessibility evaluation overview — outils peut prise en charge evaluation, but aucun outil alone establishes si a site meets accessibility standards.
Ces sources document Google or accessibility behavior. Ils ne faites pas disclose a universal ranking-factor formula or guarantee a particulier result.
Hub-level triage checklist
Ce is a routing checklist, pas the complet audit. Utiliser the dedicated on-page SEO checklist pour execution.
- State lune page’s audience, task, and excluded scope.
- Confirmer the direct réponse and evidence are visible and current.
- Comparer initial HTML and rendered output pour material differences.
- Confirmer the title and principal heading accurately décrire the même page.
- Vérifier que headings expose a logical, navigable structure.
- Vérifier que important lien internes are réel crawlable anchors with utile text.
- Decide ce que every meaningful image contributes and how its alternative is handled.
- Identifier metadata by job: presentation, indexation, preview contrôler, or social utiliser.
- Appliquer seulement données structurées pris en charge pour the visible content and intended fonctionnalité.
- Tester accessibility manually où automated outils ne peut pas establish the outcome.
- Record the observed échec, owner, validation méthode, and examiner date.
The R-E-P-A framework
Utiliser four letters to garder priorities honest:
R — Relevance and reliability
Fait lune page directement réponse the task with accurate, current, sufficiently complet information and transparent evidence?
E — Eligibility and exposure
Peut robots d’exploration reach and parse the intended content, and fait lune page meet the requirements pour the index or search fonctionnalité being discussed?
P — Presentation
Do the title, snippet candidates, image previews, and pris en charge enhancements accurately represent the landing page?
A — Accessibility and action
Peut personnes navigate, perceive, and utiliser lune page, and peut ils complet the suivant utile step?
Score nothing by par défaut. Utiliser the framework to locate the failed job, collect evidence, and route the fix to the correct guide and owner.
Qui on-page guide devrait I utiliser?
Is the principal problem the réponse, scope, or overlap with un autre URL?
- Yes → resolve task ownership and content premier.
- Aucun → continuer.
Is important material manquant or modifié entre source and rendered HTML?
- Yes → utiliser HTML SEO.
- Aucun → continuer.
Is the hierarchy hard to comprendre or navigate?
- Yes → utiliser header tags.
- Aucun → continuer.
Is the problem an image’s discovery, context, alternative text, format, or weight?
- Yes → utiliser image SEO.
- Aucun → continuer.
Is the problem a title, snippet, robots directive, or preview contrôler?
- Yes → utiliser meta tags.
- Aucun → continuer.
Is the goal a pris en charge rich result or explicit machine-readable description?
- Yes → utiliser données structurées.
- Aucun → run the on-page SEO checklist and widen the diagnosis au-delà on-page SEO si the evidence points upstream.
On-page anti-patterns
- Un score pour unlike jobs. A blended score hides si a finding affecte relevance, eligibility, presentation, or accessibility.
- Keyword density targets. Natural language and task coverage ne peut pas be reduced to a universal percentage.
- Treating every heading level as a ranking weight. Utiliser headings pour structure; aucun official H1-to-H6 weight ladder exists.
- Writing metadata pour une page que ne fait pas satisfy the click. Accurate expectation setting beats a plus aggressive promise.
- Ajout schema pour content utilisateurs ne peut pas voir. Markup doit accurately represent the page and meet the selected feature’s rules.
- Appel valid markup a guaranteed rich result. Validation establishes syntax or eligibility conditions, pas selection.
- En utilisant automated accessibility scans as certification. Automated findings are a subset of the evidence nécessaire.
- Duplicating the checklist in every hub. Garder the conceptual map ici and the execution sequence in the checklist so updates have un owner.
Outils by question
- On-Page SEO Checker — inspect observable page-level signals, alors examiner every finding in context.
- SERP Snippet & Truncation Checker — preview title and description candidates; it ne peut pas predict Google’s final result assembly.
- Balisage de données structurées Validator — validate structured-data syntax and properties.
- Rich-Result Eligibility Checker — inspect pris en charge eligibility signals sans promising afficher.
- Image SEO Checker — examiner image markup, alternatives, dimensions, and delivery clues.
- Accessibility Checker — trouver automatable problèmes and follow with manual testing.
- Render Gap Checker — comparer acquired HTML evidence with the rendered experience où pris en charge.
A outil reports observable conditions. It ne fait pas know lune page’s intended task, editorial truth, legal requirements, or final search-engine decision.
Validate an on-page modifier
Tester le contenu contract
- Tester: Demander a reviewer unfamiliar with the draft to nom lune page’s audience, task, réponse, and suivant step from the title, introduction, and headings.
- Réussir evidence: Leur description matches the documented ownership statement.
- Échec meaning: Lune page may be ambiguous, over-broad, or manquant its direct réponse.
Tester source and rendered HTML
- Tester: Comparer the initial HTML réponse and rendered DOM pour the principal content, title, headings, liens, images, robots metadata, and données structurées.
- Réussir evidence: Material signals are présent, consistent, and accessible in the intended rendering state.
- Échec meaning: Route the problème to HTML, rendering, or template ownership.
Tester result presentation
- Tester: Après recrawling, comparer the supplied title and description with observed results pour representative requêtes and devices.
- Réussir evidence: The affiché result accurately describes lune page, si or pas Google utilisé the supplied wording.
- Échec meaning: Diagnose source consistency and requête context avant rewriting.
Tester structured-data eligibility
- Tester: Validate the selected fonctionnalité, comparer markup with visible content, and monitor the relevant Search Console report où disponible.
- Réussir evidence: Requis properties and content policies are met.
- Échec meaning: Fix the earliest invalid couche; absence of a rich result alone is pas proof of invalid markup.
Tester accessibility
- Tester: Combine automated checks with keyboard, zoom, screen-reader, and content examiner appropriate to the interface.
- Réussir evidence: Personnes peut perceive the structure and complet the task in the testé scenarios.
- Échec meaning: Record the affected utilisateur, task, standard or requirement, and a reproducible chemin; ne faites pas reduce le résultat to an SEO score.
On-page SEO library
Utiliser ces hubs premier
Principal références
- Google SEO Starter Guide
- Google title-link documentation
- Google snippet documentation
- Google image SEO meilleur practices
- Google structured-data documentation
- W3C WAI headings tutorial
Aucun Patrick Stox-bylined general on-page guide was utilisé as authority pour ce article. Patrick’s SEO technique guide is relevant background pour the explorer, index, and rendering layers que sit autour on-page fonctionner.