How do you find content that is really declining?
Start with Search Console's Performance report. Compare clicks, impressions, click-through rate and average position for a page over two comparable periods. Then inspect the queries behind the change. A page may gain impressions from a broader set of lower-intent terms while clicks remain stable. A seasonal topic may decline every year at the same time. A page that lost its main commercial query is a different problem from one that lost only a tangential definition query.
Cross-check the page's on-site actions and CRM outcomes. If qualified enquiries are stable, a click decline on broad queries may not be the highest priority. If a core service page loses relevant visits and accepted leads, inspect it promptly. Use a prioritisation list that includes business value, magnitude of change, confidence in the diagnosis and effort to fix. That stops the team spending a week on a once-popular post that never influenced a buyer decision.
What is the right comparison period?
Use dates long enough to smooth weekly noise and compare similar seasons where relevant. Note product launches, migrations, paid campaigns and tracking changes that happened between periods. Do not assign every decline to a search engine update. Record the baseline page, main query group and conversion path before editing so a later review can tell whether the refresh helped. A screenshot without the date range and filters is hard to interpret.
The B2B SEO glossary defines impressions, click-through rate and query intent if the report uses those terms loosely.
Why did the page lose useful traffic?
Check four causes in order. First, technical access: the page may be noindexed, redirected, canonicalised elsewhere or absent from internal links. Second, demand: buyers may use different terms or no longer need the answer. Third, result intent: competing pages may now answer a more specific question or offer a product comparison where your page remains a broad guide. Fourth, page quality: facts, examples, screenshots and links may be stale or thin.
Inspect the current search result for the page's main query and a few close variants. Compare the type of result, not merely word count. If buyers now see product pages, adding paragraphs to an old explainer may not fit. If the query still returns guides, identify what question the top pages answer that yours leaves open. The keyword research guide helps separate a shift in search intent from a loss of ranking on the same intent.
What should a refresh change?
Change the part of the page that caused the gap. Verify the offer and facts with the product or service owner. Put the direct answer near the top, update the evidence and remove claims the business can no longer support. Add a decision table or worked example if it helps a buyer act. Improve navigation to the next relevant service, comparison or proof page. If a page still answers the right question, do not rewrite it wholesale for a freshness signal.
| Diagnosis | Appropriate action | Evidence to record |
|---|---|---|
| Important page blocked or miscanonicalised | Fix access and indexing | Crawl result and canonical check |
| Buyer question changed | Rescope the page or create a new one | Current query and result intent |
| Facts or examples stale | Expert-review and replace them | Current primary source and approval |
| Two pages compete for one intent | Consolidate or sharpen each role | Query overlap and link plan |
| Traffic is broad but unqualified | Clarify audience and next step | Lead quality and sales feedback |
This matrix makes a refresh a documented decision rather than a cosmetic edit. Record the changes in a brief changelog. If the page needs a new URL, prepare redirects and internal-link updates before publication. If it keeps the same URL, update the visible date only when the revision is substantial and the date accurately describes the work.
When should you merge or retire a page?
Merge pages that answer the same buyer question and split evidence across two weak URLs. Keep the stronger structure, move useful unique material into it and plan the redirect from the retired URL. A different buyer stage may justify two separate pages, but each needs a distinct question and next action. Do not merge a high-intent service page into a general blog guide merely because their keywords overlap.
Retire a page when the topic is obsolete, the offer has ended or the information cannot be kept accurate. Decide whether a relevant replacement exists; redirect only when it genuinely answers the old need. Otherwise provide an honest unavailable response. Avoid using Google's Refresh Outdated Content tool as an editing workflow: it serves a different purpose for certain removed or changed content in search results.
How do you check whether the refresh worked?
After publishing, verify the live page, links, canonical and index status. Record when search systems recrawl it, then compare the same query group and page outcomes against the baseline. Search visibility can change before the B2B sales cycle closes, so report early and late indicators separately. Our ROI guide explains how to track accepted enquiries without making a single page responsible for an entire deal.
If the expected query does not return, revisit the diagnosis. If it returns but visitors do not act, inspect whether the offer and next step are clear. If sales rejects the leads, the page may be attracting the wrong buyer. The next action should follow the evidence rather than a fixed instruction to “refresh again.” B2B content marketing includes this maintenance work alongside new writing; a free audit can help identify which existing pages merit it first.
Keep a refresh ledger with the URL, original intent, baseline period, reason for the edit, approved source, reviewer, publication date and next review date. Add the search query group and qualified action you expect the page to support. This record turns maintenance into a repeatable process and makes a later attribution discussion more honest. Without it, the team may remember that a page was “improved” but not whether it changed the answer, fixed a technical issue or merely updated a date. The ledger also helps the next editor avoid undoing a deliberate choice.
For a large site, review page families before individual URLs. A common template error can depress every service page, and a shared navigation change can alter discovery across a cluster. Fixing that shared issue may be more valuable than rewriting one declining article. Conversely, one outdated comparison page may need a focused expert review even when the rest of the cluster is healthy. The unit of work should follow the diagnosed cause.
Check the canonical URL after any merge or redirect, and verify it on the live site rather than only in a staging environment. Record whether the refresh changed qualified enquiry volume or only search visibility. That distinction helps the team choose the next page. If visibility recovers but buyer actions do not, the content may still fail to explain the offer or the next step clearly.
A refresh can become a case study only when its before-and-after evidence meets the case-study measurement standard.