A practical guide

Review whether website content is helping

Use a page objective, search observations and real reader questions to choose an improvement, with a fictional data table and action log.

Start a content review with the page's intended result. For a repair service, that may be helping suitable visitors understand the inspection process. For a worksheet, it may be helping someone complete a usable brief. A rise in visits is interesting, but it does not by itself show whether the page achieved either task.

You can keep a useful review log without adding an analytics script or paid tool. Use the evidence you already have, record its limits and choose a change you can explain.

Write an objective you can inspect

“Improve SEO” does not tell you which part of the page to change. “Help visitors decide whether their wooden dining chair is within scope and understand the first step” gives you specific questions to test.

For that objective, evidence might include a reader explaining the process back to you, repeated unsuitable enquiries, a broken preparation link or search queries that suggest a different need. Record both numbers and observations; neither tells the whole story alone.

Understand the search numbers

For a site you manage, Google Search Console's Performance report provides clicks, impressions, click-through rate and average position, with dimensions such as page and query. Click-through rate is clicks divided by impressions. Average position is an aggregate, not a fixed rank that every person sees.

Keep comparisons consistent: the same search type, page, country and device filters where those filters matter. Check date ranges before drawing a conclusion. A short, incomplete recent period should not be compared casually with a complete month.

Worked example: two review periods

All figures and observations below are invented for teaching. Period A and Period B each represent a complete 28-day interval in the same fictional reporting setup. They are not Content Charlie results, forecasts or proof of an optimisation technique.

Page A: impressions / clicks A: CTR B: impressions / clicks B: CTR
Workshop homepage 720 / 28 3.89% 940 / 32 3.40%
Dining-chair repairs 400 / 20 5.00% 620 / 25 4.03%
Preparing furniture photos 90 / 3 3.33% 140 / 7 5.00%

The service page gained five clicks while its CTR fell. That is not a contradiction: impressions grew faster than clicks. The aggregate numbers cannot tell us whether the page began appearing for less relevant questions, whether the mix of devices changed or whether another change affected the results.

The photo guide's CTR rose, but seven clicks is still a small count. One more or one fewer click would move the percentage noticeably. It would be premature to declare the format a proven winner and reproduce it across the website.

Add the evidence that explains the task

In the fictional workshop's review, the following observations are recorded alongside the table:

  • A staff member reports repeated questions about home visits, although the workshop does not offer them.
  • The service page's transport limitation appears only near the bottom.
  • A test reader can describe the repair type but thinks a quotation is final before inspection.
  • Query observations include both service-finding questions and do-it-yourself repair questions.

These observations suggest a useful content change without proving why the search metrics moved. Clarify transport and approval earlier on the page. Inspect the query mix before changing the title to cover a broader subject.

Turn the review into an action record

Record Fictional completed entry
Page objective Help suitable visitors prepare for a workshop inspection.
Problem observed Readers miss the transport limitation and confuse photo review with a final quotation.
Evidence Staff question log, one reader walkthrough and inspection of the published page.
Change Add a short suitability-and-process section near the introduction; link directly to the photo guide.
What stays stable Service scope, page URL and unverified pricing claims remain unchanged.
Review point Recheck after another complete reporting period and after collecting further reader questions.
Success evidence Readers can explain the inspection and approval sequence; repeated transport misunderstandings reduce in the observation log.
Remaining uncertainty Seasonality, search-result changes and small samples may still affect the metrics.

The stable elements are recorded so a later review can understand what happened. This is a proportionate editorial comparison, not a controlled experiment.

Choose a review period that fits the evidence

A page with a handful of visits may need a longer observation period or a direct reader walkthrough before numbers are informative. A seasonal product needs its seasonal context. Compare equivalent periods where possible, and note holidays, offer changes, technical outages or other known events.

If several things change at once, record all of them. Avoid attributing a rise in clicks to a rewritten paragraph when the site also gained new pages, changed its navigation or ran a campaign.

Decide whether to improve, combine or leave alone

Improve a page when a clear question is unanswered or the information has become inaccurate. Consider combining pages when they duplicate a reader task and a careful URL review supports the move. Leave useful, accurate content alone when the only reason for an edit is the desire to show a newer date.

Use the clarity checklist for the actual revision and the redesign guide before changing URLs. Record meaningful updates honestly; the review log should explain a decision, not manufacture a success story.

The source notes

Sources and further reading

  1. Google Search Console: Performance report Checked 4 November 2026
  2. Google Search Central: useful, reliable content Checked 4 November 2026

Keep making progress