When should an RIA update, merge or retire an old article?

An RIA should update an old article when its reader question still matters but the answer, evidence or firm facts need work. Merge it when another page already serves the same intent and can carry the useful material without losing needed context. Retire it when the page cannot provide a truthful, useful answer or no longer serves an appropriate purpose. Make those decisions from content and current evidence, not the belief that changing dates or deleting old pages will automatically improve rankings. Google expressly warns against artificial freshness and content removal aimed mainly at making a site seem fresh. [1]

Key takeaways

• Audit the reader decision and material claims before treating traffic as the verdict.
• Preserve a useful existing URL when improving its answer. A rewrite is not necessarily a new article.
• Match visible dates, metadata, links and structured information to the approved revision. Do not claim search or AI-answer inclusion from an editorial update.

This is an editorial maintenance framework for US advisory-firm websites, not legal advice or a technical instruction to delete pages. Compliance, records and website owners should review the exact changes. Google sources in this article describe Google; they do not establish how every search engine or assistant behaves.

What makes an article worth reviewing now?

Review when a material fact changes, the page's evidence no longer supports the claim, or reader questions reveal that the answer is incomplete. Age is a useful inventory field, not a verdict by itself.

A current service change can matter more than the article's publication year. A post that says the firm offers a service it has stopped providing deserves review even if it was published last month. A years-old explanation of how to prepare questions for an adviser might remain useful if its scope, links and current firm details are still accurate.

Separate factual change from cosmetic aging. An outdated annual limit, discontinued product, expired offer or changed fee can alter what the reader decides. A dated screenshot may confuse a user even when the principle remains sound. By contrast, a new background color is not evidence that the article's answer changed.

For marketing communications within the SEC rule's scope, material accuracy and substantiation matter. The SEC guide's general prohibitions include misleading material facts and implications and statements without a reasonable basis for substantiation. [2] A general disclaimer is not a maintenance plan for a materially wrong service claim.

How should you choose the first pages to audit?

Prioritize consequence and evidence gaps before volume. A page that could mislead a reader about costs, eligibility or financial rules deserves attention even if it receives little traffic.

Use three questions: what decision does the page support, what would go wrong if its answer is stale, and who can verify the important claims? Then add observable signals such as broken links, recurring reader confusion, outdated firm information and duplicated intent.

This is an editorial prioritization method, not a proven ranking formula. Search traffic can help show which pages readers use, but a low-traffic page may answer an important question for a small audience. A high-traffic page may still need urgent correction. Do not treat traffic as permission to keep a misleading claim.

Inventory the current URL, title, audience, reader question, owner, last substantive review, primary sources, firm-dependent facts and next-step destination. Store the actual evidence or approved version where the team can recover it. A spreadsheet is sufficient if the workflow is maintained.

A keep, update, merge or retire decision worksheet

Use this worksheet for one URL at a time. The result is a proposed editorial action that still requires the firm's applicable review and a technical plan.

Record the reason in plain language. "Old" and "SEO cleanup" are weak explanations; "the article names a service we no longer offer" identifies the actual problem.

When is an in-place update the right choice?

Update the existing page when the core reader question remains and the URL still makes sense. Preserve useful explanations while correcting or replacing unsupported parts.

For a related check, see our guide to reviewing the firm's About page.

Start with a claim pass: identify each material statement, its source, date checked, limits and whether it describes the firm's own current service. Then inspect the opening answer. A detailed correction halfway down the page is not enough if the headline and first paragraph still make the old promise.

Revise the examples and next step as well. A new rule or service boundary can affect a table, FAQ, diagram and form wording together. If an example is fictional, keep that label. Do not replace an invented result with another invented result just because the numbers look more realistic.

An update should add value for the reader. Google's people-first guidance asks whether content provides original information or analysis and a useful, substantial answer rather than merely rewriting sources. It says Google has no preferred word count. [1] A longer page is not automatically better, and a small accurate correction can be important even without a major expansion.

Keep a record of what changed and why. A reviewer should be able to distinguish source verification from a substantive rewrite and find the previous approved version under the firm's records policy.

When does merging help rather than hide a problem?

Merge when the pages genuinely serve the same decision and one coherent answer can preserve their useful material. Compare audience, intent and scope before choosing a destination.

A service page about what the firm provides and an educational article about a broader decision may share terms without duplicating each other. Keep them separate when they do different work, and link them where that helps. Two near-identical articles that differ only in a profession label are a different case; inspect whether either has distinct evidence or practical value.

Choose the destination from the existing useful content and the site's structure, not simply the newest slug. Prepare an exact map of sections, citations, FAQ answers, links and artifacts to carry forward. Correct bad claims rather than copying them into the surviving page.

Before any redirect or removal, the website owner should plan how readers arriving at the older URL reach a relevant answer. Check the actual destination after the change; a redirect that lands on an unrelated homepage is not an editorial substitute for the missing explanation. This is a reader-experience recommendation, not a promise about how a search engine will transfer signals.

Do not count a consolidation as several new articles. The work may be valuable, but its state is a revision or merge, not multiple new reader answers.

When should a page be retired or held?

Retire or hold when the team cannot support a useful truthful version or the page no longer belongs in the site's service and educational scope. State what is unresolved rather than calling it a completed refresh.

A page promising an unavailable program is not saved by adding a footnote that the program is being tested while the headline still describes it as delivered. A legal or tax explanation with contradictory sources may need a qualified reviewer before publication. If a reviewer is unavailable, hold the affected claim or page; other low-risk editorial work can continue.

Retirement needs a records and navigation plan. Establish whether a useful replacement exists, which internal links need correction and how previous advertisements or approved versions must be kept. Removing a public page is not the same as disposing of records. The SEC guide describes recordkeeping requirements for advertisements, with additional categories of supporting records. [2] The firm's compliance team should determine its specific obligations.

Do not remove a page merely to make the site look newer. Google says adding or removing content primarily to make a site seem fresh is not a useful ranking tactic. [1] Reader utility and truthful communication remain the basis for the decision.

What should happen to publication and update dates?

Keep dates truthful and explain what they mean. A source review with no material change is different from a substantive update, and neither should be presented as an entirely new story by default.

Google's date guidance recommends a visible date and appropriate publication or modification structured data, with consistent values and time zones. It says that significantly updated pages can show an update date and warns against artificial freshening. The same page includes specific Google News guidance, which should not be treated as a universal rule for every advisory blog. [3]

A firm can retain the original publication date and show a clearly labeled substantive update date. If it separately records a fact-check date, the label should not imply that the whole page was rewritten. Technical metadata should reflect what actually happened and agree with visible information.

Do not promise that Google will use the date exactly as supplied. Its guidance explains that dates are estimated from multiple factors and that structured information is not a guarantee. [3]

What belongs in the final revision check?

Check the full reader path and the exact live result, not only the edited paragraph. The headline, answer, tables, FAQ, images and next-step links should all agree.

For a related check, see our guide to planning a maintainable publishing rhythm.

For text, compare the approved revision with the rendered page. Look for lost sections, duplicate headings, missing citations and old claims left in excerpts. For images, inspect actual desktop and phone crops and alt text; an illustration should not still imply a financial outcome the copy removed. For FAQ markup, generate it from the same visible question-and-answer pairs, not an older file containing different advice.

Verify the canonical URL, internal links, intended indexing state and sitemap behavior with the responsible website owner. These checks do not authorize changing an intentional noindex decision. Google's AI-feature guidance says pages must meet ordinary Search eligibility, including being indexed and eligible to show a snippet, to appear as supporting links in AI Overviews or AI Mode. Eligibility does not guarantee appearance. [4]

No special AI text file or invented schema is a substitute for those conditions. Direct answers and useful worksheets improve clarity; they do not prove that an assistant will cite the article or that an inquiry will follow.

How do you measure an update without overstating it?

Record the correction and observable reader behavior separately. Publishing an accurate revision is an outcome in its own right, even if traffic has not changed.

Before changing the page, save the problem statement and relevant baseline. Afterward, verify that the false or unclear statement is gone, links work and the reader can reach the appropriate next step. Where measurement is available, distinguish search impressions, clicks, page engagement, inquiries, meetings and clients.

A small change in traffic is not proof the revision caused it. A sampled AI answer that mentions the page is one observation, not coverage across engines or prompts. If the purpose was to remove an unavailable service claim, do not reframe the result as client-growth success.

Use recurring reader questions to choose the next review. A maintenance register is more useful than a rigid refresh quota when the team acts on real evidence and assigns an owner for each correction.

The bottom line

Keep useful current answers, update stale evidence, merge only genuine overlap, and retire what cannot responsibly serve a reader. Preserve truthful dates and records, then inspect the entire live path. Start with one high-consequence page and complete the decision worksheet before changing its URL or counting it as new content.

Sources

[1] Google Search Central, Creating helpful, reliable, people-first content: https://developers.google.com/search/docs/fundamentals/creating-helpful-content

[2] SEC, Investment Adviser Marketing, Small Entity Compliance Guide (April 28, 2021): https://www.sec.gov/resources-small-businesses/small-business-compliance-guides/investment-adviser-marketing

[3] Google Search Central, Help Google Search know the best date for your web page (March 11, 2019): https://developers.google.com/search/blog/2019/03/help-google-search-know-best-date-for

[4] Google Search Central, AI features and your website: https://developers.google.com/search/docs/appearance/ai-features