LINK-V
LINK-V · Article

What content should you keep, rewrite or remove before a rebuild?

November 21, 2026

Before moving old pages into a new website, decide which information readers still need and which facts need correcting. Give each decision an owner so the team knows what to keep, rewrite, combine or retire.


What content should you keep, rewrite or remove before a rebuild?

Before rebuilding a website, read the content you already have and decide what still helps people. Keep accurate information that serves a continuing need, rewrite useful pages with outdated facts, combine overlapping explanations where that makes the answer clearer, and retire content that is no longer needed. Record the reason, owner and intended destination for each decision before the team starts moving it.

Imagine a small equipment supplier with product-care guides, service pages and old campaign material. A care guide may still help customers even if its design looks dated. A popular service page may need correcting. The rebuild gives the owner a chance to make those choices deliberately.

What should go into a content inventory?

Make a list of the pages and files that need review while the old website is still available. A CMS export or sitemap can help you start. Check the actual site too, including useful downloads, images and relevant language versions. A page list may leave out material published somewhere else or linked from an older guide.

For each item, record enough to explain the decision:

  • The current address, title and type of content, such as a service page, guide or downloadable document.
  • Who needs it and what they should be able to find out or do.
  • Which facts need checking, who can confirm them, and any evidence about how the content is used.
  • The important information, files and related links that must survive if it is kept.
  • The decision, reason, owner and destination where relevant, with unresolved questions clearly assigned.

Save the relevant old content as well as the list. A title alone will not show whether an important instruction disappeared during the rebuild. Keep the evidence you will need for the later comparison.

Grace WebCompare compares old and replacement websites, including titles, meta descriptions, H1 headings and URL responses. Use those findings alongside your content decisions to check intended changes. A person still needs to read the information, confirm its accuracy and inspect the files.

Compare pages with Grace WebCompare

What does someone need this page for?

Describe the reader’s purpose in ordinary words. “A customer needs the cleaning instructions for a product we still support” gives the reviewer something to check. “We have always had this page” explains its history, but leaves its current purpose unanswered.

Look at the information people ask for through support or sales, available research and the way they use related content. GDS guidance on identifying user needs gives a practical publishing example of starting from the person and task, then using evidence to understand what they need. Its government publishing rules are specific to GOV.UK; the useful question for your site is what the reader needs to accomplish.

Read the page and check whether it actually answers that question. Ask the person responsible for the subject to confirm current facts. A guide can be well written and still describe a product you no longer sell, an old process or an offer whose terms have changed.

Does low traffic mean a page should go?

Traffic helps explain use, but first check what the figures cover. Use a sensible date range, consider seasonal demand, and ask whether tracking misses some visits or routes. Search visits, downloads and enquiries answer different questions. Combine the available figures with what the content does and what people ask your team.

Low traffic is a reason to investigate a page’s purpose, not an automatic instruction to delete it. A rarely needed answer can still matter to the people who need it.

The reverse matters too: a heavily visited page can contain an important error. Its popularity does not make the advice accurate. Google’s helpful-content guidance asks publishers to consider usefulness and reliability. It also says that removing lots of older content merely to make a site appear fresh will not improve rankings overall. Age alone is a poor basis for a content decision.

Some material may need to remain as a record rather than current advice. Before removing content kept for a business, legal or historical reason, ask the responsible person what must remain and where. Follow the actual policy and obtain relevant advice where needed. An internal retained copy, a clearly dated public archive and a maintained current guide serve different purposes; a rebuild does not decide between them for you.

Should you keep, rewrite, merge or remove it?

Choose from the content’s continuing purpose and the facts you have checked. These hypothetical outcomes show how that can work on the equipment supplier’s website.

Keep the useful answer

An accurate guide explains how customers can care for a product you still support. Keep the information, including the instructions and download it refers to. Wording and presentation can still improve.

Rewrite what needs correcting

A service page answers a current question but gives an old price or describes a service you have changed. Name the person who can confirm the replacement facts before rewriting it.

Merge overlapping explanations

Two guides cover the same maintenance task. Combine them only after checking the useful details in each. Decide where the combined answer belongs and what happens to both old pages.

Remove what is no longer needed

An expired campaign page has no continuing reader purpose or requirement to remain available. Record why it can be retired, whether any useful information belongs elsewhere, and who approves the decision.

For a rewrite, say what needs correcting and what the reader must still be able to do. For a merger, read each source page and check that unique useful details remain easy to find in the combined version. Sharing a subject is not enough. Keep a question assigned if nobody can yet confirm the facts or approve the removal.

Once the content decision is clear, agree what happens to changed or retired addresses. Our guide to redirects, canonical references and removing old pages explains those technical choices. Record the intended destination here so the implementation can follow the editorial decision.

What should the team carry into the rebuild?

Give the team the approved content and its decision record. Identify the specific instructions, descriptions, images, captions, documents and language versions that belong to it. For a product-care guide, that might include a diagram, the current downloadable manual and a link from the relevant product page. Decide which version should be used before transferring the files.

Titles, descriptions and main headings can change deliberately. Record approved changes so a later difference can be explained. A comparison of page fields helps find omissions; it does not establish that the whole explanation or a linked document survived.

If the project replaces WordPress, our guide to moving from WordPress to a custom website covers the wider transfer and publishing-system questions. If important search landing pages or addresses will change, use the separate guide to preserving useful search traffic during a redesign for that preparation. The content list tells those pieces of work what should remain and why.

How do you check that the chosen content survived?

Open the intended pages on the replacement website and compare them with the approved record. Read the information, open the downloads and inspect relevant images and links. Check whether the answer is still complete and easy to find. Review differences against the decision rather than trying to restore every old sentence.

Give a missing manual or incorrect fact a named owner and check the correction again. Record what was accepted, what was changed and what still needs a decision. Our guide to deciding whether a replacement website is ready to launch extends that review to complete customer tasks and wider launch approval.

The useful result is an approved set of information, with reasons for the changes and people responsible for keeping it accurate. A clean scan or successful transfer cannot make those editorial decisions on its own.

Questions about choosing content for a rebuild

Should we remove every page with little traffic?

No. Check what the page helps someone do, whether that need still exists and what the traffic record actually covers. A rarely used support guide may still be important. Combine usage with content review and other evidence.

When does it make sense to merge pages?

When one clear version can meet the relevant needs without losing useful details. Compare the source pages, approve the combined explanation and record the destination. Similar titles alone do not justify a merger.

What should happen to old documents and images?

Include the files that belong to the retained information in the decision record. Check the correct version, links and relevant captions or descriptions on the replacement website. Do not assume that transferring a page also transfers everything it refers to.

Who should approve a content decision?

Name someone who can confirm the page’s continuing purpose and facts. Assign any rewrite or transfer to an owner, record unresolved questions, and have the selected information checked after the move.

LINK-V LINK-V