Refresh an old post or write a new one?

Refresh when the question is still the same

Keep the existing URL when the reader’s core question has not changed and the page already has impressions, clicks, links, or a clear place in the site. Update obsolete facts, weak examples, missing sections, and the search title in place.

Record what changed. A refresh should be more than changing the displayed year or adding a new opening paragraph.

Write new when the decision is genuinely different

Create a separate page when the searcher needs a distinct answer. “What is DSCR?” and “How a higher refinance rate changes DSCR” overlap, but the second can support a complete scenario and decision that the definition page cannot.

State the difference before drafting. If the team cannot explain why both URLs deserve to exist, one stronger page is usually safer than two competing versions.

Use the query report to test overlap

Compare the queries and pages in Search Console. If two pages already appear for the same query set, inspect whether they serve different intents or simply repeat one another.

Do not decide from average position alone. Look at impressions, clicks, trend, and the actual content. Search Console values are evidence about appearances, not a complete editorial diagnosis.

Choose one of four actions

Protect an accurate winner. Refresh an established page whose facts or presentation weakened. Expand with a new page for a distinct question. Consolidate overlapping pages when neither has a defensible separate job.

After the change, update internal links and the sitemap, keep the canonical destination clear, and compare complete periods. The decision is finished only when the site points readers to the chosen answer.

• Protect: accurate answer, relevant traffic, no material gap.
• Refresh: same question, weaker facts or declining response.
• Expand: distinct decision with enough material for a complete page.
• Consolidate: overlapping URLs competing to answer the same thing.