Five public sources reviewed
Four boundary tests
Two possible route decisions
Key Takeaways
- A refresh preserves the page's job; a new article earns a distinct reader decision.
- Keyword overlap is not enough to prove that two routes compete.
- The safest decision follows question, audience, evidence, and conclusion.
Published August 21, 2026
The boundary question
When should a daily SEO routine improve an existing article, and when should it create a new one? The answer cannot be “whenever a related keyword appears.” A refresh changes a page's ability to serve its existing job. A new article creates a separate route with a separate promise. Confusing the two can produce cannibalization, duplicated research, or a page whose opening no longer matches its body. This study asks how a delegated team can make the boundary explicit.
Research method
I compared Google Search Central's guidance on helpful content and canonicalization, the Search Console performance documentation, Nielsen Norman Group's work on information scent, the U.S. Digital.gov content strategy guidance, and the UK Government Digital Service content principles. The analysis is a document review, not a crawl of DelegationAssistant's pages and not a ranking experiment. It offers decision tests rather than a claim that any specific route should be changed.
The page's job comes first
Start with the current page's declared question. If the evidence is still appropriate and the reader's decision is unchanged, a refresh may be the right action. The change might improve clarity, correct a date, strengthen a source, or repair an internal link. The route remains responsible for the same job even if its wording improves.
Create a new article when the reader's decision is materially different. “How can an assistant document an SEO change?” and “Should a site refresh an old article or create a new one?” may share vocabulary while requiring different evidence and conclusions. One teaches measurement records; the other sets an editorial boundary. Similar words do not make identical intent.
Four tests
The question test asks whether both routes answer the same explicit question. If yes, consolidate or refresh is more plausible. The audience test asks whether the intended reader has the same context and decision authority. A founder choosing an editorial process is not necessarily the same reader as an assistant executing a review.
The evidence test asks whether the same sources and method can support both pages without a strained outline. If the second page needs a different evidence set, that is a strong sign it has earned a separate brief. The conclusion test asks whether both pages would end with the same recommendation. If their evidence-led conclusions differ, keeping them distinct may be clearer even when they link to each other.
These tests are editorial reasoning, not search-engine rules. Google's canonicalization documentation explains how duplicate or near-duplicate URLs can create selection issues, but it does not decide whether two useful pages are duplicates. That decision depends on content purpose and audience. The GDS and Digital.gov principles likewise point toward user need and clear content purpose, not keyword count alone.
What an assistant can inspect
The assistant can build a comparison sheet from the existing page and the proposed brief: title, opening question, audience, primary evidence, promised decision, conclusion, and internal links. It can mark shared terms and shared sources, but it should not infer competition from overlap alone. It can also note whether the new idea fills a missing question or merely restates the old one with different nouns.
The editor owns the route decision. A refresh changes an existing public asset and needs a reason tied to its current job. A new article needs a distinct title, slug, thesis, source set, and conclusion. This boundary protects the sibling Blog and Research families too: a research page should not become a checklist just because the existing blog already answers the practical version.
Limitations
Search intent is not directly observable from a keyword string, and public guidance cannot supply a universal overlap threshold. A page can have multiple legitimate audiences, and a well-linked cluster may contain related questions by design. The framework also cannot estimate traffic or business outcomes. It is a disciplined starting point for review, not a substitute for reading the actual pages.
Conclusion
Refresh when the page's job remains intact and its evidence or presentation needs improvement. Create a new article when the reader, decision, evidence, or conclusion is materially different. The strongest signal is not keyword distance; it is whether a careful reader would expect two different answers. For daily DelegationAssistant work, that question-first boundary makes new routes genuinely additive and keeps existing pages useful.
The cost of a false merge
When two questions are merged, the page often grows in a way that looks comprehensive but becomes harder to navigate. The opening names one reader problem, a middle section answers another, and the conclusion retreats to a general statement that satisfies neither. Internal links then point to pages with nearly identical promises, leaving both routes difficult to maintain. A false split has a different cost: duplicated research and competing updates. The four tests help expose both errors before a writer commits to a route.
The decision should be reversible only at the planning stage. Once a public page is rewritten or a new route is introduced, its history and links become part of the site's information architecture. A short comparison note is therefore cheap insurance. It lets the editor explain why the route exists and gives the next reviewer a reason to preserve, merge, or retire it later.
Sources
Sources
External sources cited in this article. Follow each link to review the original publisher and context.
