Published: Last updated:
TL;DR
An older article can still answer a customer’s question well. Its age alone does not tell you whether to rewrite it. Review existing content when the advice becomes inaccurate, the service changes, readers struggle to find an answer, or search performance suggests a problem worth investigating.
For a small business with limited time, that review can be more useful than adding another article about a topic already covered. The aim is a better page for the right visitor, with a clear connection to the services you actually provide.
Choose a page with a reason to change
Start with your own information. Which questions keep arriving by email? Which services have changed? Which pages attract visitors who rarely enquire? In Search Console, compare the page’s queries and clicks across sensible periods. Seasonal demand and changes in search results can affect those figures, so a decline does not automatically mean the article is poor.
Suppose a Barnsley electrician has an older guide to arranging an inspection. The page may still explain the process accurately but omit what customers should prepare before calling. Adding that practical answer could make it more useful without replacing the entire article.
Prioritise pages relevant to the business. A popular article about an unrelated subject may bring visits without helping potential customers. A quieter guide that answers an important buying question may deserve attention first.
Check the answer before changing the wording
Read the article as someone unfamiliar with your business. Can you identify the answer near the beginning? Are qualifications, exceptions and limitations explained? Do the examples still reflect your service? Check factual claims against reliable sources and remove unsupported statistics rather than replacing them with equally weak ones.
Separate genuine errors from stylistic preferences. If a section is already clear, leave it alone. Add detail when it resolves a missing question; shorten passages that repeat the same point. Google’s people-first content guidance explicitly rejects the idea of a preferred word count. A longer article is not automatically a better answer.
Decide whether to update, combine or retire
Keep the existing URL when the article still serves the same purpose. This avoids making existing links unnecessarily take a different route. If two pages answer essentially the same question, review them together. One complete page may serve readers better than two overlapping versions.
If a page no longer describes a service you offer, decide whether it should explain that change, redirect to a genuinely equivalent resource, or be removed. Do not send every retired article to the homepage. A developer can help choose the appropriate response and check internal links.
Make the useful changes visible
Check links, images, headings and the contact route alongside the text. Link to the service page that helps someone act on the advice. Replace broken references and explain images that carry meaningful information. Test the page on a phone and send a test enquiry if the article leads to a form.
Use an updated date when there has been a substantive change, and retain the original publication date where useful. Google’s date guidance explains how visible dates and structured data can describe publication and modification. Re-dating unchanged advice gives readers a misleading impression of review.
Record what changed and watch the outcome
Keep a short note of the edits and the date. Monitor the questions bringing people to the page, relevant enquiries and any technical problems. Allow time for search engines to revisit it; do not treat a few days of movement as proof that one edit caused a ranking change.
If you need help choosing what to improve, get in touch with the page and the business problem it should solve. A useful review starts with that problem, not a publishing quota.
