Update, Merge or Keep Old Blog Posts? Start With the Page’s Job
Tuohai editorial guide · Reviewed and published October 5, 2026. The worksheets are blank working templates, not client results.
Should an old post disappear because it has no clicks? Should two posts merge because their titles share a product term? Start earlier: what does each page help readers do, is its evidence still current, and who will serve that task after a change?
Age does not establish that information is obsolete. A new publication date does not establish a distinct purpose. Separate the reader's job from the state of the source material before choosing an action.
Give Each Existing Page One Specific Job
Write a plain sentence describing its purpose: compare two structures, prepare the documents needed for a sample or prototype, or explain a model's specifications. These are task examples, not findings from an actual client audit.
“Target this keyword” is not a reader task. One term can connect selection, troubleshooting and purchasing processes. Similar titles may deserve separate pages; different keywords may still cover the same question.
Record the intended reader, what they should learn, the next step and checkable source material. If the purpose is unclear to the editor, clarify it before adding more paragraphs.
Tuohai's public industry pages distinguish tasks such as battery customisation, engineering selection and packaging samples. That approach can inform old-content review. It is neither a reason to duplicate a blog set for every industry nor evidence of client results.
Keep, Update and Merge Address Different Problems
Keep content with a clear purpose, valid information and meaningful differences from other pages. A useful explanation may serve few buyers or answer questions salespeople encounter without attracting many searches. Its age alone does not justify rewriting.
Update outdated facts, missing documents or broken next steps. Replace obsolete sources, narrow model scope, add confirmed conditions or repair relevant product and download links. Record substantive changes rather than simply replacing a year.
Merge when pages serve the same task and are incomplete or substantially repetitive. List useful, distinct information before choosing the main destination. Concatenating posts into a longer repetitive article is not a meaningful merge.
Google's people-first content guidance warns against changing dates without substantive changes or adding and removing large amounts of content to make a site seem fresh. Ask which real reader problem the edit solves.
Review historical information separately. Older-version material may still help readers maintaining those products. Keep its historical context clear rather than presenting it as current capability. Correct or pause misleading information before debating traffic.
Record the Decision and Its Reason
This is an original blank template, not a client result or an audited website inventory. Actual URLs and decisions remain blank.
| Check | Record |
|---|---|
| Existing URL, title and language | ____ |
| Intended reader and one specific page task | ____ |
| Current sources, versions and applicable scope | ____ |
| Distinct information that remains useful | ____ |
| Tasks and content overlapping other pages | ____ |
| Next step and identified problems | ____ |
| Recommendation: keep, update, merge or investigate | ____ |
| Reason, gaps and confirming role | ____ |
| If merging: main page and old-URL mapping | ____ |
| Acceptance checks, change log and later review | ____ |
Record facts before assigning actions. Missing evidence is not a universal reason to delete. Identify the missing document, whether it can be recovered and whether it changes the page's central purpose.
Analytics may inform priorities but need not appear in public worksheets. Private search data, commercial leads and customer information remain in authorised environments. Do not publish private evidence or present estimates as actual performance.
Preserve a Useful Route From Old URLs
Readers may arrive through bookmarks, old emails or existing links. Choose a destination that serves the original task rather than redirecting every post to the homepage.
Google's redirect guidance recommends permanent server-side redirects where possible for a permanent location change; 301 and 308 indicate permanent moves. Site maintainers must implement and check the change. An editorial note saying “merged” is not implementation evidence.
Google's canonical URL documentation describes redirects and canonical annotations as canonicalisation signals. A canonical expresses a preferred page; it does not merge the text or automatically send visitors to the destination.
Record each old URL's destination, preserved information and updated internal links. Check sitemap and canonical consistency. A working redirect does not prove completed search processing or guarantee transfer of every ranking signal.
Verify the Edit Separately From Search Outcomes
First check the content: corrected claims, readable sources, scope and clear worksheets. Then check the page: accessible destination, matching title and body, working next steps and redirects.
Tuohai's public industry-page release checks examined HTTP responses, titles, descriptions, H1s, canonical links and body content. Those checks establish page observations at a particular time, not Google indexing or AI recommendations. No private search analytics are published here.
Review later search and business outcomes separately. Page delivery, search exposure, qualified enquiries and sales are different stages. A publication screenshot must not carry an unverified growth claim.
Agree on template, linking and migration work through site-wide Google SEO (Chinese). Dates, author boxes and the number of merged posts do not guarantee indexing or AI recommendations.
Frequently Asked Questions
Can a zero-click post be deleted immediately?
Check its task, facts and entry points, then investigate authorised search and technical evidence. Zero clicks alone do not establish useless content. Avoid blanket deletion thresholds.
Must posts sharing a keyword be merged?
No. Compare readers, questions and next steps. Retain distinct tasks with sufficient evidence. For genuine overlap, identify the main page and preserve useful unique information.
Does changing the date count as an update?
Record changes to facts, structure or next steps. A date change alone should not imply a substantive review.
Conclusion: Correct Outdated Facts Before Resolving Overlap
Correct misleading facts first, repair important next steps, address overlapping tasks, then check migration and page state. Useful older pages with distinct tasks can remain.
Request a free complete manual audit (Chinese). A complete manual audit is free; scope and scheduling are agreed separately. It does not promise indexing, rankings, enquiries or AI recommendations.