Sign in Start free

Decide Build New or Refresh Existing

Publishing a new page against a query you already cover splits internal links and history across two URLs and usually leaves both weaker. But refreshing is not automatically right either - an existing page built for a different intent will not become the right page by adding sections. The judgment turns on whether the existing URL has equity worth keeping and whether its intent matches.

CATEGORY
Content strategy
FORMAT
build-or-refresh-decision.md
STEPS
6
PRICE
Free - no account
WHEN TO REACH FOR THIS

Use when a target query is one you already have a page for and you are unsure whether to rewrite that page or publish a second one.

The skill file

build-or-refresh-decision.md
---
name: build-or-refresh-decision
description: Use when a target query is one you already have a page for and you are unsure whether to rewrite that page or publish a second one.
---

# Decide Build New or Refresh Existing

Publishing a new page against a query you already cover splits internal links and history across two URLs and usually leaves both weaker. But refreshing is not automatically right either - an existing page built for a different intent will not become the right page by adding sections. The judgment turns on whether the existing URL has equity worth keeping and whether its intent matches.

## What you need first

- Search Console query and page data for the candidate URL over 12 months
- the current top 5 results for the target query
- the existing page's internal inbound link count

## Method

1. Check whether the existing URL has ever had impressions for the target query. If it has none in 12 months despite being indexed, Google does not consider it a candidate and rewriting rarely changes that.
2. Compare page types in the top 5. If they are all comparison tables and your page is a narrative guide, that is a format mismatch and a refresh means rebuilding it entirely, which costs the same as building new.
3. Count internal links and referring domains to the existing URL. Above roughly 10 internal links or any external links, refresh and keep the URL - that equity is expensive to rebuild.
4. If the existing page ranks for a different cluster that is also valuable, do not refresh it. Build new, and link from the old page down to the new one with the target phrasing in the anchor.
5. When refreshing, change the page substantively - restructure the H2s to match the questions in the SERP, replace stale figures, cut sections nothing ranks for. Editing the intro and updating the date does nothing.
6. Record the refresh date and the before-state positions, then leave it alone for at least 6 weeks before judging.

## What this produces

A per-URL decision of refresh, build new, or consolidate, with the reason recorded against each.

## Where this goes wrong

- refreshing by adding a paragraph and changing the published date, then concluding refreshes do not work
- building a second page on a query the existing URL already gets impressions for, so the two cannibalise
- keeping a page alive because it once ranked, when it now has neither impressions nor internal links

---

From the QuQi skill library - https://www.quqi.io/skills/build-or-refresh-decision
Free to download · no account, no email

What you need first

  • Search Console query and page data for the candidate URL over 12 months
  • the current top 5 results for the target query
  • the existing page's internal inbound link count

Method

  1. 01 Check whether the existing URL has ever had impressions for the target query. If it has none in 12 months despite being indexed, Google does not consider it a candidate and rewriting rarely changes that.
  2. 02 Compare page types in the top 5. If they are all comparison tables and your page is a narrative guide, that is a format mismatch and a refresh means rebuilding it entirely, which costs the same as building new.
  3. 03 Count internal links and referring domains to the existing URL. Above roughly 10 internal links or any external links, refresh and keep the URL - that equity is expensive to rebuild.
  4. 04 If the existing page ranks for a different cluster that is also valuable, do not refresh it. Build new, and link from the old page down to the new one with the target phrasing in the anchor.
  5. 05 When refreshing, change the page substantively - restructure the H2s to match the questions in the SERP, replace stale figures, cut sections nothing ranks for. Editing the intro and updating the date does nothing.
  6. 06 Record the refresh date and the before-state positions, then leave it alone for at least 6 weeks before judging.

What this produces

A per-URL decision of refresh, build new, or consolidate, with the reason recorded against each.

Where this goes wrong

  • refreshing by adding a paragraph and changing the published date, then concluding refreshes do not work
  • building a second page on a query the existing URL already gets impressions for, so the two cannibalise
  • keeping a page alive because it once ranked, when it now has neither impressions nor internal links

Use this skill in your own AI

The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.

Claude Code Save it as ~/.claude/skills/build-or-refresh-decision/SKILL.md and Claude loads it on its own when what you are doing matches the trigger line. Put it in .claude/skills inside a project instead if the whole team should have it.
Claude Upload the file in the skills section of your settings. Once it is there it applies itself in any conversation where the trigger fits, so you do not have to remember it exists.
ChatGPT There is no skills format to install into, so paste the file contents into a Project instruction or a Custom GPT instead. It then applies to every chat in that project rather than only the one you paste it into.
Anything else Paste the markdown into the chat before your question. It works in any assistant, it just has to be pasted again each time.

Questions about this skill

When do I run this rather than just publishing the new page?

When you already have a page on the query. A second URL splits internal links and history across two pages and usually leaves both weaker. Refreshing is not the automatic answer either, because a page built for a different intent does not become the right page by adding sections. Run the decision when the existing URL has equity at stake.

What do I need in hand before starting?

Twelve months of Search Console query and page data for the candidate URL, the live top five for the target query, and the internal inbound link count. Without the impression history you cannot tell whether Google ever treated that URL as a candidate, which is the first branch of the decision. Without the link count you risk replacing equity that is expensive to rebuild.

What do I end up with, and which part of it gets used?

A per URL decision of refresh, build new or consolidate, with the reason recorded against each. The recorded reason is the part that gets used, since the question resurfaces every time that query comes back round and the argument otherwise restarts from nothing. Record the refresh date and the before-state positions too, or you cannot judge the result at six weeks.

What ruins this most often?

Refreshing by editing the intro and changing the published date. That is a timestamp, not a refresh, and when nothing moves the team concludes refreshes do not work and stops doing the one thing that would have helped. A real refresh restructures the H2s against the questions in the SERP, replaces stale figures and cuts sections that rank for nothing.

More in Content strategy