Update old website content with a practical review log

Separate age from inaccuracy

A three-year-old preparation guide can still be useful. A service page updated yesterday can still contain the wrong phone number. Our content review starts with accuracy and customer decisions rather than the age displayed beside the title.

Create a review list with URL, page purpose, factual owner, last checked date, problem, and next action. Give the highest priority to errors that cause missed appointments, unsuitable inquiries, wasted travel, or incorrect expectations. A spelling improvement should not displace a wrong booking link.

Use three passes instead of rewriting everything

First, check operational facts: services offered, business hours, coverage, contact options, staff identities, and any stated prices or availability. Confirm them with the person responsible for the operation, not by copying another page on the same site.

Second, check usefulness: can a customer tell what is included, what they need to prepare, and what happens after contacting you? Third, check connections: open links, downloads, embedded forms, and project examples. Record each issue so a missing image does not distract you from a broken inquiry form.

Work through a realistic example

Imagine a home organizer who originally offered full-day visits but now starts with a planning consultation. The old service page may still promise a booking process that no longer exists. Update the opening description, package explanation, FAQ, button label, confirmation message, and any guide that sends visitors to the old offer.

Retain relevant before-and-after examples if their context remains clear and you have permission to use them. Label historical projects accurately rather than implying that every former package is still available. If a customer follows an old link, they should understand the current offer without discovering the change only after submitting a form.

Keep dates honest

Google advises against changing dates to make unchanged content appear fresh.

Record meaningful changes for people and systems

Google says a sitemap's lastmod should reflect a significant update, such as a change to main content, rather than a routine copyright-date change. Ask your developer whether the website generates that value accurately.

Decide whether to improve, merge, or retire

Improve a page when its purpose remains useful. Merge it when another page now answers the same need more completely. Retire it when the service or information is no longer relevant and there is no suitable replacement. For pages that move, plan the destination before removing the old address.

Google's site-move guidance calls for mapping old URLs to appropriate new destinations and treating genuinely removed content appropriately. A developer should implement the resulting redirects or removal responses; sending every old page to the homepage is not a thoughtful content decision.

Make the next review easier

At the end of the edit, record what changed, who confirmed the facts, and what event should trigger the next review. For example: consultation offer confirmed by owner; review when pricing or booking process changes. Give one person responsibility for the page. That small record prevents the same uncertainty from returning every time someone updates the website.