Audit website articles: decide what to refresh, consolidate or retire

Define the reader job before judging the page

Write one sentence for what a reader should accomplish. “Understand why a form email is missing” is more useful than “target a keyword.” Then check whether the existing article actually helps someone distinguish the likely cases, take appropriate steps and recognize a successful result.

Google’s people-first content guidance emphasizes usefulness, accuracy, clear sourcing and added value. It rejects a preferred word count and the idea that bulk additions or removals make a site seem fresh enough to improve rankings.

Older publication dates do not automatically make an answer wrong. A stable explanation can remain valuable, while a recent pricing guide may already contain a changed limit. Prioritize factual exposure, reader impact and unclear decisions rather than age alone.

Build an inventory that supports a decision

Record each public URL, title, primary reader job, content owner, category, original publication date, last substantive review, important claims, evidence links and current action. Add known internal links pointing to the page and any downloads or embedded tools it owns.

Gather actual search and reader evidence where available. Search Console’s Performance report distinguishes clicks, impressions and other search metrics with filters and date ranges. Record the selected property, period and filters so two exports are comparable.

Search data is one input. A new page, seasonal answer or support reference can have little recorded search traffic and still serve readers. Missing data is not zero demand, and no-click pages should not enter an automatic deletion queue. Separate unavailable evidence from a verified absence of a particular event.

Refresh claims and steps, not just the date

Open the current primary source behind each changing claim: supported feature, plan limit, process, interface path or technical standard. Note its account type, version and scope. If a claim cannot be established, remove the certainty or explain the limit rather than replacing it with another publisher’s unsupported wording.

For a fictional mail guide, the meaningful change could be replacing a removed web-fetching workflow with supported direct-client access, while preserving the distinction between receiving and sending. That requires revised instructions, warnings and examples; changing “2025” to “2026” in the title does not fix it.

Improve the opening answer, decision criteria, failure branches and explanation of success. Preserve accurate authorship and describe researched guidance honestly. A documentation review does not become hands-on testing merely because the article contains numbered steps.

Consolidate only after identifying distinct useful material

Compare overlapping pages section by section. Record the questions each answers, unique examples, caveats, evidence and incoming links. Choose a destination because it can satisfy the combined reader task, not simply because its title looks broader.

For example, two shallow guides on missing image descriptions might become one stronger accessibility workflow. However, an article about writing useful alt text and another about diagnosing failed image delivery have different reader jobs. Combining them into a long generic image post could obscure both answers.

Draft and verify the destination before retiring anything. Carry forward the valuable details without duplicating every paragraph. Keep source attribution and meaningful section anchors where possible, and check links that previously pointed to a specific old section.

Use the content structure guide to distinguish navigation and taxonomy changes from actual article consolidation. Moving a post into a category is not the same as replacing its answer.

Choose URL behaviour deliberately

When the reader job remains the same, retaining the established URL can avoid needless migration work. A revised headline does not require a new slug. If a page really moves or is replaced permanently, Google’s redirect guidance describes server-side 301 and 308 redirects as permanent-move signals.

Map the old URL to the closest useful replacement, not automatically to the homepage. Avoid loops and unnecessary chains. Test the original address and final destination; a redirect configuration saved in a plugin is not proof that the public response is correct.

Canonical guidance concerns duplicate or very similar pages and signals a preferred URL. A canonical annotation does not send a visitor to a replacement and is not a universal substitute for retiring a page. Search engines still make their own canonical selection.

For wider slug changes, use the permalink change guide rather than mixing a global URL migration into routine editing.

Retire pages without inventing a replacement

If there is no meaningful replacement, an honest not-found or gone response may be appropriate. Google’s HTTP status documentation explains that most 4xx responses, including 404 and 410, tell its processing systems the content does not exist. Neither response guarantees a timetable or improved rankings.

A friendly missing-page design can offer navigation while still returning the correct status. A page saying “not found” with a successful 200 response is a different technical result. Check the response, not only the visible text.

Retirement should also address internal links, menus, related-article widgets, feeds and owned downloads. Do not leave readers repeatedly following links to intentionally removed material. Preserve necessary historical or correction context when replacing an answer would hide an important change.

Preserve recovery before publishing the changes

Save the current text, source records, metadata and URL decision map before editing or merging. Keep a protected copy of any material to be removed and record who approved the action. Do not let a spreadsheet status be the only remaining evidence of an old answer.

WordPress revisions can help compare and restore saved post changes, subject to the site’s configuration. They are not a complete backup or a promise that a permanently deleted post, media file and redirect settings can all be recovered.

WordPress’s backup guidance separates files and database. Confirm an appropriate recoverable copy before material bulk changes. A content export also has limits; see our article export/import guide. Recovery planning should match the actual change, rather than assuming every CMS undo button covers it.

Update dates, navigation and discovery signals honestly

Show a meaningful review or update date only when it accurately describes what happened. Google’s byline-date guidance recommends clear visible labels and consistent structured date information. Providing dates does not guarantee their appearance in Search.

After consolidation, update internal links to the intended live destination, check its title and description, and remove retired URLs from navigation. Verify anchors, examples, images and mobile readability on the revised page, not just the editor preview.

Sitemap guidance calls for preferred canonical URLs and accurate significant-modification information. Keep the sitemap consistent with the chosen public pages. A sitemap helps discovery; submitting it does not guarantee crawling, indexing or a ranking improvement.