The page still satisfies its job
Keep it when the answer is current, the page answers distinct demand, and no material improvement is needed.
SEO maintenance · existing demand
A content refresh should preserve what is already working, improve what is missing, and change URLs only when the evidence justifies the risk.

Direct answer
Update a page when the buyer task or evidence changed, not because the calendar says it is old.
01 · Choose the least destructive action
Keep it when the answer is current, the page answers distinct demand, and no material improvement is needed.
Refresh facts, screenshots, examples, decision steps, and links while preserving the URL and intent.
Consolidate overlapping value into the strongest owner. Redirect only when a genuine replacement exists.
Low traffic alone is not a deletion rule. A page can support a narrow buyer question, earn qualified conversions, hold links, explain a necessary concept, or strengthen a larger decision path. Start with page purpose and evidence, not a traffic threshold.
02 · Refresh with a change budget
Before editing, capture the current title, H1, canonical, indexability, main answer, top queries, landing-page clicks, links, conversion role, and internal links. Mark each element as preserve, improve, or retire. This prevents a “refresh” from accidentally becoming an unmeasured rewrite.
Read the query set and current result landscape. A page about choosing should not be rewritten as a definition page.
State the useful conclusion in plain language, then add conditions, evidence, examples, and the method.
Replace stale claims and visuals; add missing decision support; retain material that still works.
Annotate the change date and compare query, click, conversion, and crawl behavior over an appropriate window.
03 · Resolve overlap with ownership
Two pages are not cannibalizing simply because they contain the same phrase. The problem exists when multiple pages compete for the same searcher job and the site sends inconsistent ownership signals. Export the queries and landing pages, compare the intent each page satisfies, and choose an owner before merging anything.
If both pages serve distinct tasks, clarify titles, headings, copy, internal links, and anchors. If one is a weaker duplicate, move its unique material into the owner and redirect it. Google recommends redirects and canonical signals for duplicate URLs, but a canonical is not a substitute for deciding what each public page is for.
Record the previous title, H1, canonical, indexability, primary query group, internal links, and conversion role beside the revised values. Save the release date and the exact reason for every material change. That record makes a later decline diagnosable and prevents a new editor from repeating the same broad rewrite.
After release, confirm a successful response, the intended canonical, and at least one crawlable internal link. Check the hero and body on mobile. Any redirect must land on a genuine replacement. Then review query and landing-page movement without confusing ordinary volatility with a structural failure.
Never combine these changes casually: new URL, new intent, new design system, new internal-link structure, and broad copy rewrite. Staggering changes preserves diagnostic clarity.
Questions this owner resolves
Q062
Name the searcher's task first: learn, compare, diagnose, choose, or act. Review the current result set, then make the title, opening answer, evidence, format, and next step complete that task. Do not copy the dominant format when it leaves the buyer's decision unresolved. One page should own one clear job even when it answers several tightly related questions.
Use this rule: If a reader still needs another search to complete the same task, the page has not matched intent well enough.
Example: A query asking 'consultant or agency' needs criteria and a decision rule, not a 2,000-word definition of each business type followed by a contact form.
Field note: Search intent is a job, not a content format. Ten listicles in the results do not prove that an eleventh listicle is the best answer.
Q063
Update a page when a fact, product behavior, buyer decision, source, example, or search result has materially changed, or when the page lacks evidence needed to complete the task. Do not change the date alone. Google specifically warns against changing dates or removing older content merely to make a site appear fresh. Preserve the page's proven purpose while improving the parts that became wrong or incomplete.
Use this rule: Require a written change reason tied to accuracy, usefulness, or a changed reader decision before changing copy or the reviewed date.
Example: For a platform guide, recheck official controls quarterly or after a named product release. For an evergreen definition, update only when the definition, evidence, or reader task changes.
Field note: Freshness is not a property of the timestamp. It is the distance between the page's claims and the current operating reality.
Q064
No, not for low traffic alone. Keep a page that serves a distinct reader or site role; improve it when the intent is sound but the answer is weak; merge it when another page owns the same task more completely; remove it when it has no separate value or accurate destination. Google says adding or removing content merely to make a site appear fresh does not help.
Use this rule: Decide from distinct value, accuracy, overlap, links, conversions, and the replacement destination, not from a traffic cutoff by itself.
Example: A page with twenty annual visits but two qualified inquiries may deserve preservation. Ten pages splitting one query with no separate value are better consolidated into one owner with redirects.
Field note: Traffic is an outcome, not the page's job description. A low-volume page can still carry a high-value decision or support the path to a sale.
Q065
Map the overlapping queries to the reader task and choose one canonical owner. Keep separate pages when they serve distinct decisions; rewrite titles, openings, and internal links to make those jobs explicit. Merge only true duplicates, redirect the weaker URL to the complete owner, and update internal links and sitemap references. Monitor both URLs and queries in Search Console before and after the change.
Use this rule: Do not merge because two pages share a keyword; merge when they compete for the same user task and neither needs an independent role.
Example: If two pages rank for 'marketing agency cost' but one handles price ranges and the other contract terms, differentiate them. If both answer the same pricing question, consolidate and redirect the weaker page.
Field note: Cannibalization is an ownership problem before it is a keyword problem. The cure is one clear job per URL, not automatic deletion.
Primary and observed sources
Official documentation supports platform and search requirements. Third-party pricing and practice pages are cited as observed market examples, not universal facts or proof of ranking causation.
Continue the decision