SEO Content Refresh Brief (Traffic Decay to Update Plan)

This prompt creates a page-specific SEO refresh brief that focuses on content quality, missing intent coverage, weak sections, internal linking gaps, and opportunities to make a page more differentiated. It is built for updating existing content, not churning out disposable rewrites.

GPT / Claude / Gemini5 variables
Prompt
Create an SEO refresh brief for this page.

PAGE URL: {URL}
PRIMARY QUERY: {KEYWORD}
SEARCH CONSOLE SIGNS: {SEARCH_CONSOLE_DATA}
CURRENT PAGE COPY:
{PAGE_CONTENT}

OPTIONAL COMPETITOR NOTES:
{COMPETITOR_NOTES}

Rules:
- Diagnose likely quality or indexing weaknesses first
- Focus on usefulness, differentiation, and intent coverage
- Do not recommend keyword stuffing
- Prioritize highest-impact changes

Output format:
1) Page diagnosis
2) Likely blockers
3) Refresh strategy
4) New sections to add
5) Sections to rewrite or compress
6) Internal links to add
7) Metadata + schema ideas
8) 7-day implementation plan
Quick brief
Purpose

Turn aging pages into clear refresh plans that improve usefulness, depth, and ranking potential.

Expected output

A refresh brief containing: page diagnosis, likely indexing or ranking blockers, sections to rewrite, sections to add, internal links to create, FAQ ideas, metadata improvements, schema suggestions, and a prioritized execution plan.

Customize before copying

Replace these placeholders with your own context before you run the prompt.

{URL}{KEYWORD}{SEARCH_CONSOLE_DATA}{PAGE_CONTENT}{COMPETITOR_NOTES}
Works well with
GPT
Claude
Gemini
Variations
Make the brief specific for a tool review page.
Make the brief specific for a prompt page.
Add a section for pages marked Crawled - currently not indexed.
Create a version optimized for affiliate or money pages.
How to get better results

Fill in the placeholders with specifics instead of generic labels.

Tell the model what a strong answer looks like before you ask for the output.

After the first run, paste the response back in and ask for one focused revision.

What this prompt helps you do
This prompt creates a page-specific SEO refresh brief that focuses on content quality, missing intent coverage, weak sections, internal linking gaps, and opportunities to make a page more differentiated. It is built for updating existing content, not churning out disposable rewrites.
When to use it
Use this when a page has impressions but weak clicks, traffic has declined over time, Search Console shows pages as crawled but not indexed, or your content feels thin compared with stronger competitors. Most valuable for existing pages with some search demand already.
Decision context
Refreshing content works best when the page already has a viable topic and some evidence of demand. If the topic is irrelevant or the page has no unique angle, a refresh may not be enough. This prompt helps you decide what to deepen, remove, restructure, or add so the page becomes more useful and more index-worthy.
How it works
The prompt audits the current page against search intent, user value, structure, and evidence of originality. It then turns those findings into a prioritized refresh brief covering title/H1 opportunities, section upgrades, missing FAQs, internal links, schema opportunities, and specific editorial additions that make the page stronger instead of simply longer.
Best practices
Include the current page copy, target keyword, Search Console patterns, and at least a short note on competing pages. Ask the model to prioritize recommendations by impact so you avoid spending time polishing low-value sections first. Use the output as an editor's brief, not a blind rewrite command.
Common mistakes
Refreshing pages by just adding words. Stuffing keywords into headings. Rewriting sections that were already fine while ignoring missing intent coverage. Updating title tags without improving the actual content. Treating refreshes as technical SEO only when the main problem is page value.
What you should expect back
A refresh brief containing: page diagnosis, likely indexing or ranking blockers, sections to rewrite, sections to add, internal links to create, FAQ ideas, metadata improvements, schema suggestions, and a prioritized execution plan.
Limitations
A refresh cannot rescue a page targeting a weak topic, duplicated topic, or query that has no realistic demand. It also cannot replace genuine expertise or examples if the page has nothing original to say. Search performance still depends on competition and site-wide trust.
Model notes
Works with GPT, Claude, and Gemini. Claude is strong at editorial diagnosis, GPT is strong at structure and action plans, and Gemini can be useful for broader SERP-pattern brainstorming. Provide page content and keyword context for best results.
Real-world applications
SEO teams use this for updating decayed blog posts. Niche site owners use it to improve thin affiliate or tool pages. Editorial teams use it before quarterly refresh sprints. Agencies use it to turn vague improve-this-page tasks into execution-ready briefs.
How to tell if it worked
A successful refresh increases click-through rate, improves coverage of user questions, reduces thin sections, and creates more internal routes into the page. In Search Console, you should expect stronger impression-to-click performance over time and fewer obviously weak indexed pages.
Specific recommendations
Ask for a before-and-after outline so the new structure is obvious. Request three truly new sections instead of generic filler. If the page is already indexed, ask for changes that improve differentiation rather than total reinvention.
Where to go next
Use Search Console Triage to decide which pages deserve refresh priority. Pair with Comparison Page Outline for decision-heavy topics. Follow with Content Repurposing to turn the upgraded page into supporting assets.
When to skip this prompt
Skip a refresh when the page should really be merged, redirected, or deleted instead of improved.