The short answer
Update an existing page when the audience and main question remain the same, but the answer is incomplete, inaccurate, or difficult to use. Create a new page for a distinct customer need; if only the format needs to change, consider adapting the existing page. Merge pages only when they serve substantially the same purpose. Leave useful, accurate pages alone unless you can identify a specific improvement.
A relevant page is losing search visits.
Check: Compare its queries, demand patterns, search results, and technical availability.
Next: Refresh only if the evidence points to a content problem; resolve other causes separately.
Customers repeatedly ask something your site does not answer.
Check: Does an existing page serve that same need, or would the question change its purpose?
Next: Add a useful section for the same need; create a separate page for a distinct one.
Two articles seem to cover the same subject.
Check: Compare their audience, query groups, unique information, and business role.
Next: Merge genuine duplicates; retain pages that help readers make different decisions.
An old page remains accurate and useful.
Check: Look for factual defects or customer obstacles rather than an old publication date.
Next: Keep it and direct the available budget toward a better-supported opportunity.
Choose the page changes that help your customers
The useful budgeting question is: which change will best help a relevant visitor make a decision? A refresh can be a small correction or a substantial rewrite. A new article adds another page to maintain. Neither option deserves priority simply because it is cheaper to commission or easier to count.
My recommendation is to prioritize work with a clear business connection, a documented reader problem, and evidence you can provide. Include research, expert review, images, publishing, and checking in the effort estimate—not just writing. A short comparison requiring supplier verification may take more work than a long explanation. A content strategy built around customer decisions helps compare those demands before assigning work.
Establish what the existing page should do
Write a one-sentence purpose for each candidate: “Help office managers choose desk dimensions before ordering.” Then open that page’s Performance data in Google Search Console and inspect the available queries. Search intent means the task behind a search: learning, comparing, buying, or solving a problem. Group queries by task, not merely shared words. Use query-to-page mapping when several pages appear to serve the same task.
Google’s traffic-drop guidance recommends investigating technical issues, demand changes, and other potential causes rather than assuming content is responsible. Compare equivalent periods and examine whether the change affects one page, a topic group, or the whole site.
For your own diagnosis, record the comparison dates, country, device, and search type. Inspect relevant current results too: a results page dominated by products may indicate that an informational article is the wrong format. A decline alone does not establish that the answer needs rewriting.
Google Search Central: Debugging drops in Google Search traffic
Compare the options before commissioning work
Illustrative example: a hypothetical office-furniture retailer has an established advice section and a limited editing budget. The observations below are assumed for this exercise, not real client findings. The aim is to decide what evidence and work each option requires, rather than label every underperforming URL a refresh opportunity.
I would address incorrect product-fit information first, because it can mislead a buyer. Next, I would resolve duplicated advice and verify the installation offering before commissioning its page. The accurate care guide can wait. A useful content audit deliverable should include these reasons, dependencies, and acceptance checks—not just a list of URLs.
| Candidate | Evidence to verify | Decision | Acceptance check |
|---|---|---|---|
| Existing desk-size guide | Relevant searches and customer questions; obsolete dimensions in one diagram | Refresh the current URL | Check measurements against current products and replace the diagram |
| Two home-office measuring articles | Same reader task; each contains a useful detail absent from the other | Merge after reviewing both pages | Retain unique advice and send the retired URL directly to the combined page |
| Office installation service | A real available service; buyers need coverage, exclusions, and quote requirements | Create a dedicated service page | Confirm the operational details and a working inquiry route |
| Desk-cleaning guide | Instructions remain correct; no identified usability problem | Keep and monitor | Verify care instructions against current surface materials |
Identify content gaps worth filling
A competitor covering a subject you omit is a research lead, not proof that you need another section. Ask whether the information changes a customer’s choice, whether you can support it, and whether it belongs on this page. For the desk guide, legroom measurements could help selection; a long history of office design would not.
Google’s people-first guidance emphasizes usefulness and original value rather than writing to a preferred word count. It also cautions against changing dates to make content appear fresh without substantially updating it.
My editorial test is simple: can you state what the reader will do differently after reading the addition? Use support emails, sales questions, product documentation, and relevant search results to build the brief. If the addition needs a different promise, evidence set, and next step, consider a separate page. Related wording alone is not enough reason to combine two tasks.
Google Search Central: Creating helpful, reliable, people-first content
Specify what to change and what to keep
Before editing, save the current page and prepare a short change brief. Name the problem, supporting evidence, proposed fix, and approval requirement. Preserve accurate explanations, useful images, and existing links unless there is a reason to replace them. Otherwise, a broad rewrite can remove the very details that made the page useful.
On my own WordPress projects, Zovovo and Supplement Explained, I use Google Search Console (GSC), GA4, and DataForSEO alongside content research, search intent analysis, and gap analysis to plan updates and new content. I also use AI-assisted writing with manual review before publication.
- For each changed claim, identify the source and who can verify it.
- For each new image or table, specify the decision it should help the reader make.
- For each proposed deletion, check whether it removes an answer still needed by relevant visitors.
Check URLs and page functionality when publishing
Keep the existing URL when the page still answers the same main question. A cleaner-looking address alone is rarely worth introducing a move. If you merge pages, choose the destination based on purpose, relevant links, and existing usefulness—not age alone. A permanent redirect sends visitors and crawlers from the retired address to its replacement; update internal links to point directly there.
After publication, check the mobile layout, tables, images, inquiry forms, and search-indexing settings. Confirm that the canonical—the declared preferred URL—still identifies the intended page. Any structured data should match the visible content. My WordPress SEO work covers this publishing context; specialist development is coordinated with the client’s developers when needed.
Compare results across the affected pages
Record the publication date, changed sections, and expected effect before reviewing results. Compare the same query themes and page group over equivalent periods, allowing for seasonality and meaningful data volume. After a merge, compare the combined destination with both former pages together; otherwise, a transfer between URLs can look like growth.
Pair search data with relevant business evidence: qualified inquiries, product exploration, or recurring support questions. GA4 can record measured visits and configured actions, but not every customer interaction. If visits increase without better inquiries, examine why traffic is not producing leads before adding more articles. Simultaneous technical changes, promotions, and demand shifts limit what you can attribute to the refresh.
Common questions
Should I update every article each year?
No. Schedule reviews around how quickly the underlying information changes. Product specifications and service conditions may need closer attention than stable explanations. Correct consequential inaccuracies promptly; an annual rewrite of every page is not a useful default.
Is a content refresh always cheaper than a new page?
No. Checking unsupported claims, rebuilding diagrams, or untangling duplicate pages can require substantial work. Compare complete scopes, including verification and publishing. A clearly defined new page may be simpler than repairing an unfocused article.
Should I delete pages with no search visits?
Not automatically. Check whether they support customers, receive other relevant visits, or have an indexing problem. If a page is obsolete and has no useful replacement, removal may be appropriate. Do not redirect unrelated material to the homepage merely to avoid a missing page.
How soon can I judge a refresh?
Check accuracy and functionality immediately. Assess search and business effects once there is enough comparable data for a useful judgment. Search engines need to revisit changes, and demand varies. There is no fixed evaluation window or guaranteed improvement.