How to Decide Which Old Content Needs Refreshing

Refreshing an old article can be a worthwhile editorial investment, but changing its publication date or adding several new sentences does not automatically make it more useful. An established guide may contain accurate explanations, valuable links and years of earned visibility. Another article may be obsolete, overlap with stronger material or describe a service the business no longer offers. The correct decision starts with the reader's task and the existing page's evidence, not a content calendar demanding that every old URL be republished. For small UK agencies, a structured review can distinguish articles that need an update, those better merged into a complete resource, and those that should be retired with care.

Begin with the reason somebody still needs the page

Read the original article before opening its traffic chart. What question was it designed to answer? Is that question still relevant, and does the page answer it correctly? A guide explaining a technical concept may remain helpful for years, while a list of current platform settings can become inaccurate after one major release. A service article may be obsolete because the company stopped delivering the service. Record the intended audience, present usefulness and genuine maintenance requirement before deciding what to do. Search impressions can help identify exposure, but low traffic does not make a narrow answer unnecessary.

Ask support and operations colleagues whether customers still refer to the resource. A page with modest search visits may serve existing customers or reduce repeated enquiries. Another with a large historic audience may no longer support the company's present offering. The decision should balance real value, accuracy, risk and maintenance effort.

Check factual currency rather than superficial age

Not every paragraph becomes outdated on its anniversary. A definition can remain correct whilst screenshots, product names and procedures around it change. Read factual claims line by line and identify the authoritative source for each significant statement. Check linked documentation, product version, applicable geography and whether the cited evidence still supports the wording. If information cannot be verified, narrow or remove the claim. A cosmetic date change should never imply that research was repeated when it was not.

Google's people-first content guidance cautions against changing dates or adding and removing material simply to make content appear fresh. An update should resolve an actual reader problem. Explain what changed where that context helps, particularly when older screenshots or instructions could otherwise confuse users.

Compare the old article with neighbouring resources

Review the content inventory around the subject. A website might have several posts explaining similar aspects of structured data or page-speed testing. Some serve different levels of expertise and should remain separate. Others repeat the same definitions and examples. The main question is whether each URL provides independent value. A better guide may absorb useful passages from weaker overlapping posts, but do not automatically remove a specialist article because it shares terminology with an overview.

Record the unique reader task, useful sections, existing links and intended successor for each candidate. Decide whether to update one article, merge several or keep them separate with clearer navigation. A content merge should preserve verified information and routes to distinct answers rather than create one enormous document that is difficult to use.

Investigate performance without turning trends into verdicts

Google Search Console can identify query and landing-page groups with changes in impressions or clicks, subject to reporting definitions. Compare suitable periods, allowing for seasonality, changes in search demand and major site releases. A declining query may reflect reduced interest rather than deteriorating content. A guide may receive fewer clicks because result presentation changes while still serving visitors who reach it. A large percentage change from a small baseline can exaggerate importance.

Separate factual problems from search performance observations. A broken link or obsolete technical instruction deserves repair even if impressions are stable. Conversely, a decline in clicks does not prove the article must be rewritten. Google's traffic-drop guidance provides categories of possible causes, not an automatic decision to republish.

Choose an update when the page remains the right answer

If the original URL still serves a clear purpose, keep it and improve the substance. Correct outdated procedures, replace obsolete resources, refine unclear examples and add missing decisions. Preserve useful explanations rather than discarding them to make the article look new. Update the headline and description only when they no longer match the actual content. A small factual correction may be enough; a complex technical procedure may need a more substantial rewrite.

Check the supporting images as part of the update. A historical screenshot can remain useful if labelled accurately and linked to its source. A licensed diagram can be replaced when it no longer represents the procedure. Keep author, licence and modification information appropriate to the asset rather than copying unattributed imagery from search results. An updated article is not finished if the public version contains a broken diagram or misleading caption.

Choose consolidation when several URLs serve one task

When two or more articles substantially duplicate one answer, a consolidated resource can simplify navigation and editorial maintenance. Identify the strongest current destination based on purpose, content, relevant links and suitability. Move valuable verified explanations from other pages without copying repetitive filler. Decide which old addresses require appropriate redirects to the genuinely relevant successor, then update key internal links and canonical references.

Do not route every removed article to the homepage. A visitor following a detailed troubleshooting link needs relevant content. Google's site-move guidance explains URL mapping and verification. The technical success condition is a working public route to the intended resource, not an exact guaranteed search position after migration.

Retire content that no longer has a legitimate role

Some pages describe discontinued products, obsolete policies or activities the business no longer performs. Retention can mislead customers, especially when the old article continues to attract search visits. Determine whether the information still has archival or explanatory value. It may be appropriate to maintain a dated historical explanation, redirect to a relevant successor or return an honest not-found/gone response when the resource has been withdrawn without replacement.

Coordinate with stakeholders before removing service, policy or customer-support material. An article can have contractual or operational relevance that a marketing review does not reveal. Preserve records where legally or operationally necessary, without exposing private documents publicly. Removal should be a deliberate content-lifecycle decision rather than an attempt to make a site audit show fewer pages.

Be truthful about publication and modification dates

Dates communicate context to readers, particularly for time-sensitive technical guidance. If an article receives significant substantive changes, a clearly labelled last-reviewed or updated date can help explain its state. Minor formatting adjustments should not automatically make it appear newly researched. If software or policy changed, identify the relevant version and date where useful. Never invent a new author biography or unsupported firsthand testing to give an update greater apparent authority.

If Article structured data includes published or modified dates, keep those consistent with actual editorial records and visible information. A valid JSON-LD value cannot establish that someone verified the facts. Build the review process around real approvals and changed source material, not automatic timestamp manipulation.

Recheck titles, headings and internal navigation

After editing, compare the HTML title, H1 and the actual answer. They can differ naturally but should describe the same subject. Old headings may promise sections that have been removed; new content may require a more logical outline. Check links from related guides, service pages and topic hubs. A previously useful anchor can become misleading after a consolidation, even when its destination still returns a successful response.

Use descriptive links and avoid adding unrelated destinations merely to increase counts. Google's link best practices support clear navigation. Preserve contextual relationships through appropriate redirects and ensure the surviving article answers the reader's next question.

Include accessibility and mobile checks in the editorial review

A refreshed comparison table can be difficult to read on a phone if its container has a fixed desktop width. Long headings can overlap with sticky navigation or become clipped. Check representative narrow viewports and user zoom. Ensure tables have meaningful headers, images have relevant alternative text and form or link interactions remain available through keyboard navigation. A technically valid article can still be unusable after an otherwise successful content update.

Check public rendering rather than assuming the CMS preview reflects production. A stylesheet change may break a table while leaving all database fields intact. An old cache may show the previous article, or an internal editorial note may be accidentally displayed by a faulty frontend renderer. These require independent engineering or public acceptance tests.

Measure the right outcome after publishing

Record the decision, reason, original URL, affected links, source changes and date of public verification. Then observe later query and page performance over suitable periods. Search rankings and clicks can change for many reasons, including demand, competitors and result features. Do not attribute every movement to the refresh or promise that an updated timestamp creates a ranking reward.

A factual correction may be worthwhile because it prevents readers acting on obsolete instructions, regardless of whether clicks increase. A consolidation may succeed because customers reach one complete answer instead of fragmented resources. Define those direct quality outcomes alongside later search observations. Where a business conversion is relevant, verify it through appropriate authorised data rather than inventing leads from traffic statistics.

Run a repeatable review with clear owners

Maintain a content inventory with last substantive review, known source dependencies, owner and next trigger. Critical guides may need review after platform releases; evergreen explanations may only require periodic checks. When a source changes, find every article repeating the affected fact. This can prevent inconsistent guidance across an archive. Avoid rigidly rewriting everything on a monthly calendar when no material change has occurred.

For each candidate, make one documented decision: update, consolidate, retain or retire. Ensure the decision considers reader purpose, evidence and technical consequences. A good refresh programme is not measured by the number of dates changed or URLs deleted. It is measured by whether the published knowledge base remains accurate, navigable and useful, with public changes verified and uncertainty recorded.