How to run an on-page SEO audit that ends in a decision

An audit score compresses unlike problems into one number. A missing description, two URLs answering the same search, an unsupported claim, and content hidden by a rendering fault do not have the same cause or the same remedy. Adding them together makes an on-page SEO report look precise while avoiding the decision the site actually needs.

Work one URL at a time. Determine what the reader needs, what the business needs from the visit, the evidence that bears on both, the relationship with neighboring pages, and the action that follows. The output should be specific enough that someone with access to the site can make the change without reconstructing the rationale.

Write a page brief before opening the checklist

Begin with a short statement that can be disproved. Name who the page is for, what they should understand or do, what the business needs the visit to accomplish, and the related searches the page is meant to serve, grouped by the answer they need; an ad account's keyword match types decide which searches trigger an ad and say nothing about how many pages a site needs. Then name the closest competing URL on the same site.

If the brief cannot distinguish the page from its nearest neighbor, do not move straight to headings and word counts. First decide whether both URLs deserve to remain. Improving both pages can make the conflict more expensive rather than resolving it.

Separate observations from inferences

Record what you can see before deciding what it means. Search Console can show which queries produced impressions and clicks for a URL. The current search results show the kinds of pages Google is presenting. The page itself shows its offer, claims, structure, and links. Analytics can show what visitors did after arrival. None of those observations alone proves why a page ranks or converts as it does.

Google's guidance on using Search Console and Analytics together makes the division useful: Search Console describes search exposure and clicks, while Analytics describes behavior on the site. Keep those sources separate in the record, then state the inference they support.

Observation: two URLs receive impressions for the same cluster of queries. Inference: they may overlap. Decision: compare the questions they answer, their content, links, and performance before choosing whether to separate or consolidate them.

Inspect the page as one system

A page-level audit needs more than a content read and less than a sitewide technical crawl. Inspect the parts that can change what this URL represents, whether Google can evaluate that version, and what a qualified visitor can do with it.

• Ownership: Which query family and reader decision should this URL own? Compare the queries already producing impressions with the nearest pages on the same site.
• Eligibility: Is the intended URL indexable, served successfully, internally canonicalized, and selected as canonical by Google? If rendering, robots rules, or canonicalization block the page, route that dependency into technical implementation rather than trying to rewrite around it.
• Answer: Does the visible content supply the facts, reasoning, examples, and decision the reader came for? A heading that repeats the query cannot compensate for a partial answer.
• Presentation: Do the title element, main heading, prominent labels, and description accurately represent the same page? Compare them with the title link and snippet Google actually shows for the relevant queries.
• Relationships: Which pages link here, what do their anchors imply, and where should this page send the reader next? Internal links should clarify the boundary with neighboring owners, not distribute a phrase by quota; the internal linking guide sets which pages link where and with what anchor.
• Business path: Can the useful visit reach the intended product, service, enquiry, or other outcome without the article pretending that every reader is ready to convert?

A failure in one layer can make another look weak. A well-written page selected as a duplicate needs a canonical or consolidation decision. A correctly indexed page that answers the wrong question needs a different owner or a rewrite. Record the primary constraint before listing secondary improvements.

Worked example: two guides, one actual answer

Consider a fictional payroll software site with these URLs:

Suppose Search Console shows that both URLs receive impressions for overlapping payroll software queries, the search results favor comprehensive guides, and the first URL has the stronger links and clearer business path. The finding is not “add more keywords to the weaker page.” The two pages have no defensible separation.

The implementable decision is to keep the first URL, move any unique and useful material from the second into it, update internal links to point directly to the remaining page, and permanently redirect the retired URL. Google's documentation treats a permanent redirect as a signal that the target should become canonical, but the redirect is justified here because the target fully answers the old page's question. See the primary guidance on redirects in Google Search.

Change one assumption and the decision changes. If one guide serves payroll administrators while the other helps a first-time founder compare software, and the content and query evidence support that distinction, keep both and make the difference unmistakable. The URL nouns do not decide. The reader needs do.

Choose the action that follows from the evidence

Keep

The page has a useful, distinct purpose and already fulfils it adequately. Record why no material change is warranted.

Improve

The purpose is valid, but the answer, proof, structure, title, or contextual links obscure it. Name the specific change and expected effect.

Merge

Two pages answer the same question. Select the remaining URL by evidence, preserve useful unique material, and update links.

Redirect

A remaining page fully replaces a moved or consolidated URL. Point the old URL directly to that final destination.

Remove

The page serves no useful purpose and has no truthful replacement. Return a real not-found response instead of sending every retired URL to the homepage.

Across a whole site, the same decisions fill a content audit template, one row per page.

A title or snippet problem may be one part of an improve decision. Use the separate guide to write and diagnose title tags and snippets after the page's purpose is settled.

Write down the change before handing it off

For every accepted action, record the current state, the exact implementation, the reason, the query or business outcome it is meant to affect, the person who can make the change, and the first sensible review point. This prevents a recommendation from becoming a timeless sentence in a slide deck.

1. Current state: URL, title, primary heading, canonical, indexability, relevant copy, and important internal links.
2. Evidence: query and page data, result-set observations, conversion evidence, content facts, and neighboring URLs.
3. Decision: keep, improve, merge, redirect, or remove, with the reason that rules out the nearest alternative.
4. Implementation: the actual content, template, navigation, link, redirect, or status-code change.
5. Expected effect: the related queries, reader behavior, or commercial outcome that should change if the diagnosis is right.

Google's people-first content guidance is useful here as a boundary on the answer: the page should serve its intended audience and purpose. It is not a substitute for deciding which URL should carry that answer on this particular site.

Review the hypothesis, not just the average

After implementation, allow time for crawling and reprocessing, then compare the affected page and related queries with an appropriate prior period. Check whether impressions, clicks, position, and the relevant on-site outcome moved together. Segment by query, device, country, or search appearance when the overall average hides a material difference.

Do not claim success because one metric rose. A page can gain impressions from irrelevant queries while qualified visits fall. A title change can alter clicks without changing position. Demand can change independently of the site. Google's guide to debugging search traffic drops explicitly recommends examining pages, queries, seasonality, technical issues, and concurrent search changes before deciding what caused a movement.

If the audit produces decisions but the site still lacks the access or responsibility to publish them, that constraint belongs in the conclusion. Another document is not the remedy for missing implementation access. Our on-page SEO services start from this audit and end with the change published on the site.