Begin with one page and one reader task

On-page SEO concerns the content and page elements you control. Before reviewing tags, write the question the page should answer. A product page should explain fit; a tutorial should enable a task; a comparison should support a decision. The title and introduction should make that purpose apparent to someone arriving directly from search.

Open the page on a phone and a desktop. Read the headline, first explanation, and primary action. Ask whether they describe the same offer. A perfectly formed title cannot compensate for a page that promises an instructional walkthrough and delivers only a product pitch. Resolve that mismatch before moving through the technical checklist.

Align the title, main heading, and description

Write a distinctive page title that accurately names the topic or decision. Keep the main visible heading clear and consistent with that promise. Google documents several possible sources for its displayed title links, including the title element and prominent page headings, so the wording you provide is an input rather than a guaranteed search-result label.

Use the meta description to summarize what a visitor can learn or do. Google may create a snippet from page text and sometimes use the description when it fits the query. Avoid treating a particular character count as a universal display guarantee. Read the wording for clarity and accuracy before compressing it to fit an arbitrary target.

Check the answer, evidence, and limitations

Confirm that the page delivers the promised explanation. Use headings that follow the reader’s sequence, examples that show the important decision or action, and source links for changeable facts. A technical instruction should identify its prerequisites. A software comparison should make the basis of the comparison visible.

Check product claims against the current version and plan. Replace unsupported superlatives with specific behavior a visitor can inspect. Label hypothetical calculations and examples as such. Google’s helpful-content questions provide a useful editorial standard: the page should contribute real value and leave the intended reader with a satisfactory answer.

Follow the links and inspect the media

Click the important internal and external links. Check the destination, the surrounding promise, and any download. Use descriptive link text so someone understands the next page before opening it. Keep related references near the point where a reader needs them, rather than filling the page with an unrelated list of destinations.

Review screenshots and diagrams for legibility and factual accuracy. Provide useful text alternatives where an image conveys information, and keep important product facts available as text. Check that the main action works with a keyboard and that tables remain usable on a narrow screen. These are part of making the explanation accessible to the people it is written for.

Verify the page’s intended public status

For a page you want in search, confirm that it returns the intended public content, has no accidental noindex instruction, and is reachable through relevant links. Check the canonical destination, especially after copying a template or moving content. Keep private account screens and unfinished sample pages outside the set you want indexed.

Use Search Console’s URL Inspection when investigating a particular page. Its indexed view and live test answer different questions; a live test helps assess current accessibility but does not guarantee indexing or ranking. Review the actual published URL instead of assuming that a successful local preview proves the public setup is correct.

Finish with a publishable acceptance check

Use this compact review before the page goes live. Keep any unresolved item with an owner so it does not disappear between writing and deployment.

  • The title, visible heading, introduction, and main action serve the same reader need.
  • Important facts have been checked, and examples are labeled accurately.
  • Links and downloads reach the promised destinations on the published site.
  • The page works on a phone and with keyboard navigation.
  • Canonical and indexing instructions match the page’s intended role.
  • A maintenance owner and the relevant source records are recorded.