How Do I Find And Refresh Decaying Content?

Decaying pages often keep the URL, but they stop matching what searchers want. EngineSEO helps you find content that needs attention and create a reviewed replacement so you can decide what goes live.

Run a content refresh tool workflow in two phases to spot decay and create an updated draft

Phase 1: Identify pages that are getting stale

  1. List your target content types and pick a cutoff window for “decay,” such as pages published 12+ months ago or pages that have dropped in performance for the last 28 days.
  2. Pull the candidate URLs from your Google Search Console property so you can use real query and click behavior rather than guesswork.
  3. Run a content decay search from your Search Console data using EngineSEO’s decay recovery strategy so the tool can suggest which existing articles to refresh based on patterns it detects.
  4. Score candidates using three checks: whether the page still answers the main query intent, whether key facts look old (pricing, process, screenshots, dates), and whether the page has lost CTR (signals show people click less when the snippet is weak).
  5. Pick the top 10 candidates for the first batch and document why each one is on the list (for example: “The steps were last updated in 2022,” or “The product screenshots changed.”).

Phase 2: Generate a refreshed version and review it before publishing

  1. Create a refresh request for one candidate at a time so you can compare the old URL versus the new draft text during review.
  2. Request a regenerated draft from EngineSEO’s content refresh capability and review the new draft for accuracy, structure, and alignment with the original page goal.
  3. Verify on-page details that commonly go stale: dates, feature names, screenshots, step order, and any claims that depend on policy or platform behavior.
  4. Validate keyword coverage and subtopics: check headings against the search intent and ensure you handle adjacent questions that show up in your SERP.
  5. Approve the refreshed draft in the Review Queue if it’s ready, or reject it with specific fixes you want so the next iteration matches your editorial standards.
  6. Plan the URL change: publish the new article on Shopify, then redirect the old URL to the new one (or unpublish the old article), and measure performance for the new URL after the switch.

Worked example: Refresh 8 decaying guides using specific inputs and decision thresholds

Your inputs

  1. Start with 240 published guides and set a decay cutoff of “published more than 365 days ago.”
  2. Open your connected Google Search Console property and export click and query data for the last 28 days.
  3. Filter to pages that lost clicks in the last 28 days AND have a top 10 keyword footprint (many queries, but lower clicks than before).
  4. Choose the first batch target: 8 URLs with the weakest CTR change, such as pages where CTR dropped by at least 20% compared to the prior 28 days.

Your process (run once end to end)

  1. Send those 8 URLs into EngineSEO’s content workflow and use its Search Console-based suggestions that include decay recovery so the tool can focus on candidates that show stale behavior.
  2. Select one guide, “How to choose an SEO content plan,” and generate a refreshed draft using EngineSEO’s content refresh so you get a new draft to review.
  3. During review, compare the old and new drafts and check a simple scorecard: update coverage (0 to 5), fact accuracy (0 to 5), and readability (0 to 5). Aim for at least 13 out of 15 before you approve.
  4. Update the page’s “steps” section with current screenshots and the correct current process, then rewrite the intro so it matches the actual query framing from your Search Console queries.
  5. After approval in the Review Queue, publish on Shopify (through your content schedule or your publish action), then set a redirect from the old URL to the new one.
  6. Repeat the same steps for the remaining 7 URLs so the batch uses consistent standards and timelines.

Your measurement rule after publishing

  1. Measure the new URL, not the old one, using a 14-day and 30-day check after redirect so you can see whether impressions and CTR stabilize before clicks.
  2. Set a stop rule: if CTR stays more than 10% below the pre-refresh baseline after 30 days, revise the snippet title and first paragraph alignment with the original query intent.
  3. Set a quality rule: if rankings move but conversions don’t, keep the content refresh limited to intent and readability issues rather than changing the page’s purpose midstream.

Variations for different site types and when this workflow is a bad fit

Use the workflow when pages are “almost right,” but show age

  1. Choose guides, how-tos, and reference pages with stable intent where the core topic still matters, but the details drift (examples: processes, screenshots, and recommended steps).
  2. Use decay recovery when you want suggestions grounded in Search Console signals across the last 28 days rather than relying on a manual guess list.
  3. Run one small batch first if you have dozens of guides, because review time is the real bottleneck.
  4. Keep the editorial voice consistent with your existing site style so the refreshed draft reads like it belongs to the same library.

Skip it when the underlying page goal changed or the content is fundamentally off-target

  1. Skip “refresh” when the page no longer matches the business goal (for example: the intent is different now, or the product angle is outdated in a way that needs a new page concept).
  2. Skip it when the page competes on a topic you no longer cover, because you’ll spend effort updating something that should be replaced with a different content structure.
  3. Skip it when you cannot reliably update factual sections during review, since the refreshed draft still needs human checks for accuracy.
  4. If your site is new or has only a handful of pages, run a broader discovery step first (for example, keyword research or domain scan) before you chase decay signals.

Frequently Asked Questions

How do I pick which pages to refresh first?

Start with pages older than 12 months and then filter by Search Console performance over the last 28 days. Use a simple threshold like “CTR dropped by 20%” to narrow candidates, then score the top pages by whether they still match intent.

What should I check during the review of a refreshed draft?

Check facts that go stale, including screenshots, step order, dates, and any references to policies or platform behavior. Also confirm the headings and first section match the query framing you see in Search Console so the page answers what people actually type.

Does the refreshed version replace the existing page at the same URL?

No. Content refresh creates a new draft article for you to review, and once you publish the new article you should redirect the old URL to it or unpublish the old article. Measure performance for the new URL after the change.

How long should I wait before judging results?

Check after 14 days for stabilization and use a 30-day window for a clearer read on impressions, CTR, and clicks. If CTR remains more than 10% below your baseline after 30 days, revise snippet alignment and the first paragraph’s intent match.

Can I refresh content without Search Console data?

You can still do manual reviews, but you lose the strongest decay signals based on real query and click behavior. EngineSEO’s decay recovery suggestions use your connected Google Search Console property, so connecting it gives better prioritization.

Make the refresh decision with a clear threshold, then route the old URL to the new one

Use this rule: if a candidate page still matches the main intent and you can update key stale elements during review, proceed with a refresh; if not, replace it with a new page plan instead of forcing updates. When you run the workflow in EngineSEO, publish the reviewed draft on Shopify and then redirect the old URL so measurement reflects the new page. Start your next batch by selecting 8 URLs that match your criteria and run the same process in EngineSEO so your workflow stays consistent.

Back to all articles