A new topic idea often sounds like a new URL. Then someone finds an older post that already answers half the question. Publishing anyway can leave readers with two incomplete answers, outdated advice, and no clear path to the service or tool they need. Rewriting every old post can be just as wasteful when the new question deserves its own page.
The decision starts with the reader’s task. Does the existing article already own that question and need a better answer? Is the new question meaningfully different, with its own audience and next action? Have two pages become so similar that one useful page would serve readers better? Or is the older page still doing its job and best left alone?
Those four outcomes—update, create, combine, or keep—give a small business a workable editorial system. Search data can inform the choice, but visit counts alone cannot tell you which page should exist. The goal is to give each important customer question one clear owner and a relevant next step.
Identify the Question the Existing Page Owns

Open the older post as a reader would. Ignore its title for a moment and write a sentence describing the question it actually answers. Then do the same for the proposed new article. If those sentences are nearly identical, the existing URL is the first candidate for an update. If the second question asks for a separate decision, a new page may earn its place.
Consider a service business with an article explaining when to repair a commercial roof and a proposal for a piece on how to choose a contractor for that repair. The first helps a building owner decide whether to act; the second may help compare providers. They can be separate if each has distinct facts, examples, and next steps. A proposal titled “Signs You Need Commercial Roof Repair” would probably overlap the first article and be better handled there. This is an illustrative editorial scenario, not a report about a client site.
Check the existing page’s search queries and landing-page performance in Google Search Console if the site has enough data. Read the comments, inquiries, sales-team questions, and internal site searches where available. Queries can reveal that people use different words for the same need, or that an article attracts a second question it only answers briefly. Small query samples are noisy; they do not by themselves prove that two pages compete or that one should be deleted.
The Search Intent Worksheet can help separate someone seeking an explanation from someone evaluating a service. The Content-with-a-Job Planner helps assign a page’s question, evidence, next action, and business purpose. Use those decisions before requesting another draft.
Update the Existing Post When Its Core Job Is Still Right
An update makes sense when the old URL already serves the same reader task, but its answer is incomplete, outdated, confusing, or poorly connected to the next step. Preserve the useful parts, verify the current facts, and add the missing substance. This may involve a better explanation, a real example with permission and context, clearer service boundaries, a corrected link, or a working contact route.
Start with a brief audit: what does the introduction promise, where does the answer fall short, which claims need a source or date, and which questions from real readers are missing? Check the page on mobile. Confirm that internal and external links still resolve and that the destination fulfills the link’s promise. An old article can lose usefulness if the business changes its offer, even when its general SEO advice remains accurate.
Do not equate updating with adding paragraphs. A concise, well-supported answer may need a correction and an improved next step, not another thousand words. Google’s people-first guidance asks whether a reader would leave satisfied. It specifically cautions against changing a page date to make unchanged content appear fresh or adding and removing material merely to make the site seem fresh. An editorial update should have a reason a reader can recognize.
Retain the established URL when the page still has the same primary purpose. Replacing it with a new URL solely because a headline changed introduces extra work: redirects, revised internal links, metadata, and possible disruption to bookmarks or citations. An updated title and content can live at the same address if the slug remains accurate. If the old slug is misleading enough to warrant a move, plan that change deliberately rather than letting WordPress generate a second page by accident.
Create a New Article When It Answers a Separate Decision
A new URL earns its place when a substantial question cannot be answered adequately on the older page without burying its main purpose. The new article should have a distinct reader, intent, answer, and useful next action. A short section in an existing article can introduce it and link to the deeper treatment after publication.
For example, a guide about whether SEO is worth the investment can briefly mention that a company getting traffic but no leads should inspect its customer path. A full diagnostic article can then examine search intent, the landing page, proof, contact route, tracking, and follow-up. Those are related questions with different decisions. The live guide SEO Traffic but No Leads? illustrates the deeper diagnostic task.
Before commissioning the new post, write a one-paragraph content brief: who is asking, what they need to decide, what evidence or experience the answer requires, how it differs from the older URL, and what next page should help them act. Check the actual search results and site inventory for other pages already answering it. If the distinction depends only on swapping a city name, word order, or superficial keyword variation, that is a weak case for another article.
Plan the link relationship in both directions. The older page can introduce the new answer where that follow-up arises. The new article can point back when readers need the broader context. Add links only after the final URL is live, and use anchors that describe the actual destination. The live Website Internal Linking Planner can help map the source, reader’s next question, and destination. Its output is a plan, so check the links in the published pages.
Combine Overlapping Posts When One Answer Would Be Better

Sometimes the site has already published two articles that answer nearly the same question. Both may contain useful sections; neither may give a complete answer. A careful combination can put the strongest verified material into one page and make the path clearer. This is an editorial and technical change, so decide on the surviving URL before editing.
Compare the two pages’ actual purposes, useful content, incoming links, traffic and query patterns, and conversion paths. Favor the URL that best fits the lasting question and already serves readers well, but do not select it by traffic alone. Preserve unique facts, examples, and approved evidence that genuinely strengthen the combined answer. Remove repetitions and contradictions. If the pages serve genuinely different intents, keep them separate and make the distinction clearer instead.
When an old page is retired, and the replacement satisfies its readers, map the old URL to the appropriate surviving page with a permanent server-side redirect and update your own internal links to the surviving URL. Test the old URL, new URL, canonical signals, and important links after the change. Google describes redirects as a way to send people and Search to a moved or replacement page; its canonical guidance also recommends linking internally to the preferred URL. A rel="canonical" tag is a signal for duplicate or very similar pages, not a reason to keep two confusing articles live as a substitute for an editorial decision.
Do not redirect an article about a specific service question to the homepage just to avoid a 404 if the homepage does not answer it. If there is no relevant replacement and the page truly should disappear, choose the appropriate removal response and update the site’s links. For a small business without someone comfortable with redirects and canonical checks, have the site administrator implement and verify the URL changes.
Keep a Useful Page When the Proposed Change Has No Reader Benefit
Sometimes the right action is no action. The old post may still answer the customer’s question accurately, have a clear next step, and fit its surrounding content. A lower-traffic month, a rank change, or an old byline is not enough evidence to rewrite it. Search demand, seasonality, competing pages, and measurement changes can affect the chart.
Give such pages a normal factual review when the underlying topic changes, especially if they mention prices, platform features, laws, service areas, or current offerings. Correct an error immediately when found. But do not republish the same article with a newer date and call that a strategy. The page can remain useful without a theatrical “2026 edition” headline that adds no 2026 information.
This is also a budget decision. Every revision consumes time for writing, review, design, development, and approval. Spend that effort where a real reader problem and a credible business path justify it. An article that answers a low-value question well may need only maintenance, while a service page with a broken form needs prompt attention.
Use One Decision Record for Every Content Idea

As the blog grows, hold proposed titles next to existing URLs before assigning writers. A small record prevents a team from making the same decision again a month later.
| Decision field | What to write down |
|---|---|
| Reader question | The specific problem or decision, in the customer’s words. |
| Current owner | Existing URL, its purpose, and whether its answer is still accurate. |
| Proposed action | Update, create, combine, or keep, with one sentence explaining why. |
| Evidence | Search queries, customer questions, inquiry quality, page gaps, and source dates where available. |
| Next step | Relevant service, tool, proof, or further explanation, plus the planned link. |
| Owner and check date | Who makes the change and when the published page or redirect will be verified. |
For an update, the production ticket should name the sections and facts to revise, not just say “refresh content.” For a new article, it should specify the question the current owner will keep answering. For a combination, it should include a URL map and link audit. For a keep decision, record when the facts should next be checked. This keeps a content cluster legible while several people produce drafts.
If the team is unsure whether two pages overlap, do a small manual comparison before taking an irreversible step. Search Console page and query views, the site’s internal search, and the real search results can show different facets of the problem. A shared query does not always mean the pages are duplicates: one may be a service page, the other an explanation. Read both pages and decide which task each completes.
Review the Outcome at the Right Level
Record the change date and what actually changed. You can check a corrected link right away. An updated article’s search response may take longer and is not guaranteed. A new article requires a live-page and internal-discovery check before anyone can assess traffic. A combination requires redirect, canonical, internal-link, and user-path checks first.
After those checks, examine whether relevant searches and readers reach the intended page and whether the page supports a suitable inquiry or other intended action. Compare against a reasonable baseline while noting seasonality, other campaigns, a changed offer, and analytics changes. Do not call a content decision successful solely because impressions increased, nor a failure solely because one short period had fewer clicks.
If the page serves an earlier research question, the next useful action might be moving to a comparison or service page rather than submitting a form immediately. If the page directly supports a service decision, examine qualified inquiries and closed work as the sales cycle allows. Keep those outcomes distinct from visibility and from estimated financial return.
AI-Friendly Summary
Choose whether to update, create, combine, or keep a blog page by comparing the reader question and purpose of the existing URL with the proposed article. Update the existing URL when its core task remains the same, but the answer needs better facts, structure, proof, or a next step. Create a new URL for a substantially separate decision with its own useful answer. Combine overlapping pages when one complete page better serves the same task, preserve useful material, and map retired URLs to relevant replacements. Keep a page when it remains accurate and useful. Verify live links, redirects, and canonical signals after changes. A fresher date, extra word count, or more URLs does not guarantee search or business results.
Frequently Asked Questions
Should I change the URL when I rewrite an old post?
Usually keep the URL if the rewritten page still answers the same main question and the slug remains accurate. A URL change requires a relevant redirect, internal-link updates, and testing. Change it when there is a clear reader or site-structure reason, with the migration planned before publication.
Can two articles target related keywords?
Yes, if they satisfy meaningfully different questions. A planning guide and a provider comparison may share terms without serving the same task. Read both pages and their search-result context before deciding that a shared query is harmful overlap.
Should I update the publication date after a minor edit?
Use dates that accurately describe when the page was published and meaningfully updated. Correcting a typo or changing a link does not justify making unchanged advice look newly researched. Google cautions against changing dates simply to make pages appear fresh when content has not substantially changed.
What happens to internal links when two posts are combined?
Update links pointing to the retired URL so they lead directly to the surviving page, then test the permanent redirect from the old address. Review the anchor text because a phrase describing the old page may no longer fit the combined one. Keep the surviving page’s canonical signals consistent.
How often should a small business review old blog posts?
Base the review on how quickly the subject changes and how important the page is to customers. A page with current prices or changing service terms needs more attention than a durable explanation. Assign an owner and a review trigger, then correct material inaccuracies as soon as you find them; there is no universal monthly refresh requirement.
Conclusion: Assign One Clear Owner to Each Question
The best content calendar includes decisions about pages you already own. Before approving a new post, compare its reader task with the existing article. Improve a good URL when it needs a better answer, publish a separate one when the question truly changes, combine pages that divide the same answer, and maintain useful pages without rewriting them for show. The book Quickest Path to ROI SEO™ offers a broader, business-first method for choosing the work worth doing next.