How to decide what to create, refresh or merge on a website
Learn how to decide what to create, refresh or merge by comparing pages by reader task and writing a content plan your team can put into action.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What it means to decide what to create, refresh or merge
To decide what to create, refresh or merge, list the site's pages and group them by reader task, the thing someone comes to a page to do. A shop owner checking whether a provider supports gift cards has a different task from a cashier looking for instructions to redeem one. A task with a sound page may be settled already. An outdated answer may need a refresh, several answers to the same question may belong on one page, and a task with no page may justify a new one.
The result is a list of proposed changes an editor or developer can carry out. For a merge, it identifies the page to keep, the material to move and the addresses to redirect. For a refresh, it gives the current passage and a sourced replacement. For a new page, it sets out what the reader needs to learn or do and which existing pages should lead to it. Content pruning is often used as a broad label for this work. The decision here starts with the usefulness of each answer and the evidence you have for changing it.
What it does for the business
- Fix errors buyers act onAn outdated claim on a page that sells can create confusion at the point of purchase. A refresh brief that quotes an incorrect return instruction and names its replacement lets the owner fix the page and check whether support materials give the same advice.
- Spend writing time where an answer is missingA content inventory shows when an existing page can handle a proposed topic with a small addition. You can use the time saved on a separate draft to brief a page that covers a real gap, such as a buying question the sales team keeps fielding.
- Give readers one complete route through a taskWhen the steps to complete a task are spread across overlapping pages, a content consolidation plan brings the necessary instructions and examples together. The support team can then use the surviving address in its replies and update saved links that pointed to the old pages.
- Turn an audit into work you can assignAn ordered list gives editors the passages to change and developers the addresses and links to update. The team can size the work, schedule dependencies and hand over a useful first batch while larger changes are still being scoped.
How to decide what to create, refresh or merge, step by step
List the site and group possible overlaps
Cover the titles broadly so you can spend reading time where it changes a decision.
What to do
- Define the site, market and language you are reviewing. List page addresses and titles from the sitemap, then look through the blog index and its older pages, category and tag lists, menus and footer for addresses the sitemap missed.
- Group likely versions of the same answer. Check annual editions, singular and plural variations, similar addresses ending in a number, and formats such as a guide and a checklist on the same task. Treat these groups as leads to investigate.
- Set a reading budget. Spend it on complete look-alike groups first, then on pages with dated claims, short pages, pages with few obvious paths from elsewhere on the site and the main pages that sell.
- For each page you open, record the main heading, dates shown and the canonical address if the page declares one. A canonical address is the preferred version the site signals to search engines. Record earlier interventions and how you chose the pages you read.
Why
Reading a complete group gives you a fair comparison for a merge. Recording the sample helps a client see which recommendations came from full pages and which groups still need a closer look.
Decide what each reader task needs
The reader's task determines whether two similar pages belong together.
What to do
- Propose a merge when the pages answer the same question for the same reader. Look for a complete page with a clear address and useful internal links pointing to it. If you have visit or link data, consult it before choosing the survivor. Record the passages worth moving and where each old address would redirect.
- Refresh a page when it owns the task and has an outdated or incorrect claim, a broken example or a gap in the answer promised by its title. Quote the exact sentence and draft its replacement, or specify where a missing answer should go. Give the source for each new fact.
- Propose a new page when the offer or the site's existing articles point to a real task with no owner. Check the full inventory and inspect plausible candidates. Give the new page a working title, address, outline and a list of existing pages that can link to it.
- Keep pages that serve distinct tasks. Write a short reason for leaving them separate, such as one page explaining what to buy and another explaining how to maintain it. Flag groups you have yet to read as candidates for further review.
- Check that a merge of legal or reference pages preserves the information readers use, including relevant conditions, definitions and exceptions. Have a qualified reviewer assess proposed changes to legal text.
Why
A title gives you a subject. The page and its intended reader tell you which work it does. A setup guide might contain a list of troubleshooting tips that a second page lacks, even when both cover the same setup task. Identifying that detail before writing the merge brief keeps the useful answer in the combined page.
Write and order the actions
A decision is ready to assign when the team can see what to change and where.
What to do
- Use one row for each proposed action. Include the addresses, the decision, the reason, the priority and your confidence in the evidence. Put the source beside each new fact so an editor can verify it.
- For every merge, write a redirect map listing each old address and its destination. Add the affected internal links and the passages the surviving page needs before anyone changes those links or applies redirects.
- Address inaccurate facts on commercial pages first. Compare the remaining work by its importance to readers and the size of the affected group. Put decisions to keep distinct pages after the work someone needs to do.
- Give the lead a short list to start with and show the limits of the review alongside it. Indicate which choices depend on the reading sample, and which survivor choices would benefit from checking visit or link data.
Why
A merge can involve writing, link updates and redirects. Putting those dependencies in the same row shows the project lead what needs to be ready before publishing.
Verify the evidence and hand over the plan
Every proposed change should survive someone reopening the pages it names.
What to do
- Have a second reader reopen every page in an action when possible. Check that refresh quotes appear verbatim and that each source supports the replacement wording, including who or what it applies to.
- Confirm that the survivor exists, covers the shared task and can retain the relevant passages from the other pages. Read each pairing in the redirect map as a visitor following an old link.
- Check every new brief against the full inventory once more. Look for another page that could own the task and reopen it if the title alone leaves the answer unclear. Remove actions whose evidence you cannot confirm.
- Recount the actions and hand off the plan with the first changes, their owners and open decisions. Mark any redirect destination that still needs confirmation from visit data.
Why
A review can catch a missing qualification in a replacement sentence or a surviving page that answers only part of a shared question. Checking coverage and destinations before any edits gives the team time to preserve missing material and correct a mistaken redirect before an old address changes.
Common mistakes
- Merging from titles aloneSimilar wording can hide different tasks, so read each page before assigning it to a survivor.
- Choosing a survivor by traffic aloneA heavily visited page can still need material from another page to answer the shared task in full.
- Recommending a vague refreshAn instruction to update a page leaves the editor to find the error again and check the new facts from scratch.
- Briefing a page before checking older listingsA useful answer may already exist in an archive or category that the main menu omits.
- Redirecting before moving useful materialReaders following the old link should be able to find the relevant instructions, examples and conditions at the destination.
What a good result looks like
- Your inventory identifies the scope and shows which pages you read in full.
- Each merge names a survivor, the material to carry over and the destination for every old address.
- Each refresh identifies the affected wording or missing answer and gives the editor a sourced replacement.
- Each creation covers a reader task you checked against the inventory and names existing pages that can link to it.
- The ordered plan explains the evidence and marks decisions that still depend on additional data.
And then what? Using the result
- Assign inaccurate commercial claims to the page owners and give them the sources for the replacements.
- Review the survivor choices against visits and links where available. Approve the destination for each old address before scheduling the redirects.
- Move the useful passages into each survivor and check that it answers the shared task. Then update internal links, apply redirects and try the old addresses yourself.
- Give each new page a brief with the reader's task and the proposed outline. Add its links from the relevant existing pages when the answer is ready.
When to run it
- Before commissioning a batch of articlesCheck where the site already answers the questions you want to cover. You can brief writers on missing answers and assign small changes to existing owners.
- After years of guides on the same subjectsAnnual guides and separate checklists can repeat the same answer. Read the groups and see which pages can be combined while retaining distinct examples and instructions.
- When taking over a client siteStart with the public pages while you gather access to visit and link data. The first plan can show the evidence for each action and which address choices to confirm later.
Questions people ask
How do you decide what to create, refresh or merge?
Start with the reader's task and check which existing pages answer it. Create a page for a task the site should cover, refresh the page that owns a task when its answer needs work, and merge pages that serve the same reader with overlapping answers.
Can you make a content consolidation plan without traffic data?
Yes, you can propose a merge by reading the pages and showing where they answer the same task. If you have a Pages export from Google Search Console, compare clicks by address before choosing where to redirect.
How do you choose which URL to keep when merging pages?
Choose an address that can carry the complete answer and is already a sensible destination for the site's links to that task. Check existing visits and inbound links when available. Move relevant material from the other pages before applying their redirects.
When do similar pages deserve to stay separate?
Keep them separate when the people reading them need different answers or need to take different actions. A product compatibility page helps someone choose what to buy, while a troubleshooting page helps someone diagnose a product they already use.
What should a content refresh brief include?
Include the page address, the exact text to replace, the proposed wording and a source for any changed fact. If a section is missing, describe the answer the reader needs and indicate where the editor should add it.
How do you handle pages you did not have time to read?
Record them in the inventory and label suspected overlaps as candidates. If you plan to merge a group later, first read each member so you can identify distinct tasks, choose a destination and preserve useful material.
More jobs in SEO agencies
Decide what to create, refresh or merge, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac