# How to refresh a page that lost its traffic

Your page slid and the rest of the site held. Do not rewrite from scratch. Decide if demand fell or your page did, then refresh in a set order and measure after 28 days.

Updated 2026-09-14 · Source: https://porteur.ai/guides/content-refresh

## Decide first: did demand fall or did the page fall

You fix the right thing when you know which moved. Use Search Console data, not a hunch.

1. **Open Performance, Pages** Compare the last three months to the previous three months. For seasonal sites, compare to the same period a year before.
2. **Sort by click difference** Pick the pages with the biggest drops in clicks. Open each page’s Queries tab.
3. **Read impressions and position per query** If impressions for the core queries fell, demand fell. If impressions held but average position worsened, the page fell.
4. **Check the results page** Search the core query in a logged-out browser. Note new features, fresh dates on rivals and the questions on the page.

> Rule: act on the page only when impressions for its main queries held but position worsened. If demand fell, consider a new angle, not a refresh.

## What a refresh is, and what it is not

- Same URL kept live
- Facts updated: prices, limits, support, features, screenshots, schema
- Sections rewritten to match the current results page questions
- Missing questions added and dead sections trimmed
- Broken links fixed and new references added
- Title revised to reflect the moved results page
- dateModified updated, visible on the page and in structured data

- Not a rewrite from scratch that loses what ranked
- Not a new URL
- Not a date change without a significant update

> Warning: changing the date without changing the content is discouraged. The date should reflect a significant update.

## Prioritise with a simple content audit

Do not pick pages one by one. Run a light audit and choose the work that can pay back this quarter.

- Make a table of every indexable page
- Add clicks and impressions for 12 months from Search Console
- Add inbound links, last updated date and the page’s purpose
- Decide one action per row: keep, refresh, merge, redirect or remove
- Repeat each quarter, judge decisions on the next quarter’s figures

Merge when two pages rank on the same queries and neither does well, or they answer one intent. Keep the URL with more links and clicks, fold in what the other had that was better, 301 the other.

Delete when a page has no clicks, no impressions, no links and no purpose for a year. Return 410 or 404 unless a close equivalent exists, then 301.

## Refresh in this order

1. **Update the facts** Fix dates, numbers, product names, UI terms and screenshots. Retake images so the interface matches.
2. **Rewrite sections against current queries** Open the results page. Note the questions, People Also Ask and featured answers. Rewrite or add sections to answer them, in your product’s frame.
3. **Fix links** Remove dead links. Add new sources you cite. Link to your recent pages that cover related sub-questions.
4. **Revise the title** Match the results page wording if it moved, keep the core keyword, stay under about 60 characters. Avoid clickbait.
5. **Update the date** Show a visible ‘Updated’ date on the page. Set dateModified in structured data. Keep datePublished unchanged if the original date still stands.

A fixed page reads tight, answers the new questions high on the page, and shows a recent updated date that reflects real edits.

## Rewrite to the results page’s questions

Your section plan should mirror the live questions. If the results page shows ‘how’, add steps. If it shows comparisons, add a short table.

- Search your primary query in quotes, note the top headings
- Expand each People Also Ask that sits near your target query
- Scan featured snippets for the exact phrasing of the answer
- Cover the same ground in your own words with your product’s proof
- Add a short FAQ at the end to catch long-tail variations

Do not copy rivals. Keep what already earns impressions. Replace only the parts that no longer match intent or are stale. Remove fluff that never ranked.

## Dates and structured data that match

Google can read a visible date and the same date in datePublished and dateModified. It prefers a page that says when it was last updated.

- Keep the URL when you republish a page
- Show one clear Updated date near the title or byline
- Set datePublished to the original publish date
- Set dateModified to the date of the significant update
- Use Article or BlogPosting schema, not a custom type, if it is an article

> Rule: only change the visible date and dateModified when the refresh is significant, not for a typo or a new image alt text.

## Tidy the on-page elements that drift

- Title: match the moved query, about 60 characters, no year unless needed
- Meta description: one clear sentence that reflects the new sections
- H1: stable, do not change it every quarter to chase trends
- Intro: one or two lines that say what changed and who this helps
- Internal links: add links from newer pages, remove overlaps that cannibalise
- Screenshots: current UI, readable on mobile, compressed
- Alt text: describe the image, not the keyword stuffed
- Anchor text: plain words that match the destination’s promise

If Core Web Vitals slipped, fix images, fonts and scripts while you are here. A fast, stable page keeps the gains you win back from the refresh.

## Worked example: refreshing a fictional guide

Page: yourproduct.com/guides/getting-started. It lost clicks while the site held. Queries: “getting started yourproduct”, “yourproduct setup”, “yourproduct tutorial”.

- Before: title “Getting Started With YourProduct”. No date. Screenshots from an old UI. No section on “migrate from Trello”.
- Results page now shows fresher dates, a featured snippet with a 5-step setup, and People Also Ask shows “How do I import from Trello?” and “Is there a free plan?”
- Refresh plan: keep the URL. Add a 5-step setup section high on the page with clear headings. Add a short import guide and link to /guides/trello-import. Add a pricing note that states the current free plan limits. Retake screenshots.
- After: title “YourProduct setup: a 5‑step getting started guide”. Intro says it was updated this month. Visible Updated date near the h1. dateModified set. Dead links removed. New links to the import and pricing pages.

1. **Ship and request indexing** Update the page. Submit the URL in Search Console’s URL Inspection to request a recrawl.
2. **Measure after 28 days** Compare the last 28 days to the previous 28. Check clicks, impressions and average position for the three core queries.
3. **Decide next action** If impressions rose and position improved, keep and move on. If impressions held but position still lags, expand the sections that rivals still beat.

## When not to refresh: merge or remove instead

A refresh cannot rescue pages that overlap or that have no purpose. Merge or prune and move on.

- Two thin pages on “/pricing-faq” and “/pricing-questions” that rank for the same queries: merge into “/pricing”, 301 the weaker URL
- An old “/features/calendar-2019” with no clicks, impressions or links for a year and no product feature now: return 410 or 404
- A near-duplicate “/blog/what-is-kanban” and “/guides/kanban” with neither doing well: keep the one with more links and clicks, fold in the other, 301 it

> Warning: low-quality pages can affect how the site as a whole is assessed. Prune on data, not on a hunch.

## Guardrails: scale, AI writing and site reputation

Google’s spam policies target scaled content abuse, site reputation abuse and expired domain abuse. They do not penalise AI-assisted writing as such.

Avoid spinning out many low-value pages. A page family earns when each page holds data or an answer of its own that a reader wants. Refresh to improve value, not to pad volume.

## Questions

### What is a content refresh?

It is an update to an existing URL that fixes facts, rewrites sections to match the current results page, retakes screenshots, revises links and title, and updates the modified date. It is not a new URL and not a rewrite that throws away what ranked.

### How often should I refresh pages?

Audit quarterly and choose refreshes that can pay back in the next quarter. High intent pages with steady impressions but falling positions come first. Do not change dates monthly without real edits.

### Do I need to change the URL when I republish a page?

No. Keep the URL. A republished page keeps its address. Set dateModified and show a visible Updated date when the edit is significant. Change the URL only when merging and redirecting.

### How do I get Google to pick up my refresh?

Update the page, then request indexing in Search Console’s URL Inspection. Ensure internal links point to it. Google can take time, so measure on 28-day windows, not days.

### What if a feature or AI Overview takes the click now?

Adapt the page to answer the questions shown and win the click you can. Add a clear, short answer high on the page, then the detail. If demand has moved to a different query, cover that angle on its own page.

### Should I rewrite from scratch if a guide decayed?

Usually no. Keep what still earns impressions and links. Rewrite only the parts that no longer match the query. If two thin pages overlap, merge them and redirect the weaker URL.

## Read next

- [Content decay: pages that earned more before, and the refresh](https://porteur.ai/guides/content-decay): See how to spot content decay in Search Console, why it happens, and a clear refresh method. When to merge instead, and how to measure recovery.
- [The Search Console performance report, column by column](https://porteur.ai/guides/search-console-performance-report): Every column in the Google Search Console performance report explained with the traps that trip small sites, and how to act on each.
- [How to find declining pages in Search Console before the traffic is gone](https://porteur.ai/guides/find-declining-pages-in-search-console): Use Search Console to compare periods, sort by click loss, read queries, and act before a page’s traffic is gone. Works for SaaS and small shops.
- [Republishing content and changing dates: what Google reads, what is honest](https://porteur.ai/guides/republishing-and-dates): When to change dates, how to mark updates, and when to keep or replace a URL. A clear process that avoids penalties and wins back traffic.
- [People also ask: turning Google’s questions into sections](https://porteur.ai/guides/people-also-ask): See what People also ask is, where questions come from, how to collect them, write two-sentence answers, add FAQ markup, and track results.
- [Title tag length: what fits, what Google rewrites, and how to write one](https://porteur.ai/guides/title-tag-length): About 60 characters is a safe line. Learn pixels versus characters, why Google rewrites titles, and how to write titles that earn clicks.
- [Updating old blog posts: which ones, what to change, what to leave](https://porteur.ai/guides/update-old-blog-posts): Pick the posts worth your hour, make changes that pay, keep the URL, set dates correctly, and know when to merge or retire instead.

Paste your URL to get a free 30‑second check that reads your site, the searches around it and the rivals on them, and shows three findings you can ship. Free check: https://porteur.ai/