Evidence-Grounded SEO Content Refresh Plan for Existing Blog Posts

Public field comparison

SEO Content Refresh Strategy and Recommendations for Old Blog Posts

Evidence-Grounded SEO Content Refresh Plan for Existing Blog Posts

Generate a detailed SEO content refresh plan by analyzing search intent, keywords, competitors, content gaps, internal links, and outdated sections to optimize old blog posts effectively.

Use ChatGPT to produce a prioritized, evidence-traceable SEO refresh brief for an existing article, covering intent alignment, content gaps, metadata, links, citations, schema eligibility, verification, and post-refresh measurement without claiming unperformed changes.

—

Useful for turning article copy, search performance exports, SERP observations, competitor notes, and internal-link inventories into a review-ready SEO content refresh brief with clear evidence, priorities, approval points, and acceptance checks.

Search Intent Review
SEO Content Refresh
Content Briefing
SERP Competitor Review
Internal Linking Review
Citation Readiness

Evidence-based refresh briefs for underperforming blog posts
Search-intent and article-structure gap analysis
SERP-supported content differentiation reviews
Internal-link and citation readiness planning
Pre-publication SEO acceptance and monitoring plans

Target keyword
Secondary keywords
Existing content URL
Current article text or outline
Current title
Current meta description
Audience
Target country or market
Search intent
Current ranking or performance data
Google Search Console data
Competitor URLs or summaries
Existing internal links
Internal links to add
Brand voice or style requirements
Content constraints
Definition of done

Target keyword
Current article text
Current title
Audience and market
Definition of done
Approval scope
Secondary keywords
Existing content URL
Current meta description
Search intent hypothesis
Performance evidence
SERP and competitor evidence
Internal link inventory
Business goal and conversion
Brand and editorial requirements
Content constraints

Replace every bracketed placeholder with your specific project information before running the prompt. Provide detailed and accurate inputs to ensure actionable and precise SEO refresh recommendations.

Open ChatGPT and replace every bracketed variable with project-specific information, using “Not provided” for unavailable optional inputs. Supply the exact article text, current metadata, target query, audience and market, definition of done, approval scope, dated Google Search Console or analytics exports, documented SERP or competitor observations, and an approved internal-link inventory where available. Redact confidential or personal data, then run the prompt. Review and authorize the resulting brief before making any CMS, metadata, linking, schema, or publication changes.

An SEO operator wants to improve an underperforming blog post about sustainable gardening. They input the target keyword 'sustainable gardening tips', the URL of the current post, audience details, search intent focused on beginners, current ranking data, competitor URLs, existing internal links, and a clear definition of done. The prompt produces a prioritized refresh plan with rewrite suggestions, meta updates, FAQ additions, and a verification checklist.

An SEO team is reviewing an underperforming article about sustainable gardening for beginners. It supplies the full article, target query, market, current metadata, a 16-month Google Search Console export with query and device filters, dated SERP notes, approved internal destinations, editorial constraints, and an approval scope limited to recommendations. ChatGPT returns a traceable refresh brief that separates observed intent gaps from hypotheses, preserves useful sections, proposes supported title and outline changes, identifies citation needs, ranks actions by impact and confidence, and assigns implementation-dependent checks to human owners without claiming that anything was published or verified.

Advanced

Advanced

ChatGPT

ChatGPT

analysis

analysis

seo
search-intent
content-refresh
internal-links
content-optimization
meta-description
ranking
old-blog-posts
google-search-console
blog-seo

seo
search-intent
content-refresh
internal-links
content-optimization
meta-description
ranking
old-blog-posts
google-search-console
blog-seo

SEO Content Refresh Prompt for Optimizing Old Blog Posts | Advanced Strategy

Evidence-Grounded SEO Content Refresh Plan Prompt

Create a detailed SEO content refresh plan for old blog posts using search intent, competitor gaps, internal links, metadata, and performance data.

Build a traceable SEO refresh brief with intent analysis, content gaps, citations, link planning, approvals, and concrete verification checks.

Prompt-body line comparison

Removed Added Unchanged context

−You are an expert SEO strategist and content refresh specialist.
−
−Your task is to create a detailed SEO content refresh strategy for an existing blog post. The goal is to improve search intent alignment, content quality, topical coverage, internal linking, metadata, freshness, and ranking potential without changing the brand voice unnecessarily.
−
−Context:
−Target keyword: [Target keyword]
−Secondary keywords: [Secondary keywords]
−Existing content URL: [Existing content URL]
−Current article text or outline: [Current article text or outline]
−Current title: [Current title]
−Current meta description: [Current meta description]
−Audience: [Audience]
−Target country or market: [Target country or market]
−Search intent: [Search intent]
−Current ranking or performance data: [Current ranking or performance data]
−Google Search Console data: [Google Search Console data]
−Competitor URLs or summaries: [Competitor URLs or summaries]
−Existing internal links: [Existing internal links]
−Internal links to add: [Internal links to add]
−Brand voice or style requirements: [Brand voice or style requirements]
−Content constraints: [Content constraints]
−Definition of done: [Definition of done]
−
−Important note:
−If you cannot access the existing URL or competitor URLs directly, use the pasted article text, summaries, keywords, and performance data provided in the context. Do not pretend to have reviewed URLs you cannot access.
−
−Task:
−
−1. Analyze the current content.
−   Identify:
−
−* Outdated information
−* Thin sections
−* Missing subtopics
−* Weak headings
−* Search intent mismatch
−* Poorly answered user questions
−* Weak examples
−* Missing statistics or sources
−* Sections that should be rewritten, expanded, merged, or removed
−
−2. Analyze search intent.
−   Explain:
−
−* The likely intent behind the target keyword
−* What the reader expects to find
−* Whether the current article satisfies that intent
−* What should be added to better match the intent
−
−3. Compare against competitors.
−   Based on the competitor URLs, summaries, or provided details, identify:
−
−* Common competitor headings
−* Topics competitors cover that the article misses
−* Content depth gaps
−* Formatting or UX gaps
−* Unique angles the article can use to stand out
−
−4. Create a content gap analysis.
−   Use a table with these columns:
−   Gap | Why it matters | Recommended fix | SEO impact | Priority
−
−5. Recommend title and meta description improvements.
−   Provide:
−
−* 3 SEO title options
−* 3 meta description options
−* Recommended final title
−* Recommended final meta description
+Produce an evidence-grounded SEO content refresh brief for the existing article described below. The deliverable is a recommendation and handoff document—not an executed edit, CMS update, publication, schema deployment, or guarantee of ranking improvement.
 
−6. Recommend heading structure improvements.
−   Provide a refreshed H2/H3 outline that improves readability and search intent alignment.
+INPUTS
 
−7. Recommend specific rewrite actions.
−   For each major section, state:
+Blocking inputs required for a reliable brief:
+- Target keyword: [Target keyword]
+- Current article text: [Current article text]
+- Current title: [Current title]
+- Audience and market: [Audience and market]
+- Definition of done: [Definition of done]
+- Approval scope: [Approval scope]
 
−* Keep, update, expand, merge, remove, or rewrite
−* What exactly should change
−* Why the change matters
−* Suggested replacement angle or content
+Useful optional context; enter “Not provided” when unavailable:
+- Secondary keywords: [Secondary keywords]
+- Existing content URL: [Existing content URL]
+- Current meta description: [Current meta description]
+- Search intent hypothesis: [Search intent hypothesis]
+- Performance evidence: [Performance evidence]
+- SERP and competitor evidence: [SERP and competitor evidence]
+- Internal link inventory: [Internal link inventory]
+- Business goal and conversion: [Business goal and conversion]
+- Brand and editorial requirements: [Brand and editorial requirements]
+- Content constraints: [Content constraints]
 
−8. Recommend internal linking improvements.
−   Suggest:
+INPUT AND ACCESS RULES
 
−* Existing internal links to keep
−* Internal links to add
−* Anchor text suggestions
−* Where each link should appear
−* Pages that should link back to this refreshed article
+1. Treat pasted article copy, exported Google Search Console or analytics data, dated rank-tracking records, supplied crawl reports, internal-link inventories, and documented SERP observations as the available evidence.
+2. ChatGPT may analyze materials present in the conversation. If browsing is available and explicitly used, identify each successfully opened page and its access date. Do not imply that a URL was opened, crawled, rendered, or audited when it was not.
+3. A URL alone is not evidence of its page content. If browsing is unavailable or access fails, rely on supplied text or summaries and mark the page “not inspected.”
+4. Never invent rankings, traffic, conversions, search volume, keyword difficulty, dates, competitor coverage, citations, source conclusions, link destinations, page status, schema eligibility, or implementation results.
+5. Separate:
+   - Supplied fact: directly present in the inputs.
+   - Observation: directly visible in supplied or successfully accessed material.
+   - Assumption: a declared premise used to continue.
+   - Hypothesis: an interpretation requiring validation, such as inferred intent.
+   - Unknown: information not available.
+   - Conflict: sources or inputs that disagree.
+   - Recommendation: proposed work that has not been implemented.
+6. Cite the relevant input, URL, report, query, metric, and date beside material findings where available. Use “source not provided” when evidence is absent. Do not convert correlations into causal claims.
+7. If any blocking input is missing, ambiguous, or internally inconsistent, begin with concise clarification questions and mark the brief “Blocked—clarification required.” You may still provide a clearly labeled preliminary assessment where safe, but preserve unknowns and do not present it as final.
+8. For missing optional inputs, continue with bounded analysis, state the limitation, reduce confidence, and specify the evidence needed to validate the recommendation.
+9. If performance datasets use different date ranges, query filters, countries, devices, search types, attribution rules, or URL variants, do not combine them until reconciled. Record the mismatch.
 
−9. Recommend external sources or citation needs.
−   Identify where the article needs updated statistics, expert sources, official documentation, or credible references.
+AUTHORITY, SAFETY, AND EDITORIAL BOUNDARIES
 
−10. Recommend FAQ additions.
−    Provide FAQ questions and short answer directions that support search intent and long-tail visibility.
+- Work only within [Approval scope]. Do not edit a CMS, publish content, change metadata, add links, deploy schema, alter canonicals, redirect URLs, modify robots directives, request indexing, contact third parties, or approve claims.
+- Label all proposed copy and technical changes “Draft—human review required.” Obtain authorized human approval before implementation or publication.
+- Do not recommend keyword stuffing, hidden text, misleading metadata, fabricated expertise, copied competitor language, manipulative link schemes, unsupported superlatives, or schema that is not supported by visible page content.
+- Paraphrase competitor observations; do not reproduce substantial protected text.
+- Redact personal data, credentials, private customer information, confidential analytics identifiers, and unnecessary query-level data before analysis.
+- Flag medical, legal, financial, safety, regulated, or other high-stakes claims for qualified subject-matter and compliance review. Do not draft unsupported claims or imply that editorial review replaces professional approval.
+- Preserve original source attribution and useful content unless evidence supports changing it. Flag licensing uncertainty for images, quotations, datasets, or third-party assets.
+- Stop and escalate rather than prescribing implementation if the evidence suggests a migration, manual action, security incident, legal dispute, widespread indexation failure, conflicting canonical or redirect rules, or a change outside the approval scope.
+- Require a CMS revision, export, staging copy, or equivalent rollback point before authorized implementation. Recommend changing one controlled version at a time and recording the publication date and exact edits.
 
−11. Recommend schema opportunities.
−    Suggest relevant schema types, such as:
+WORKFLOW
 
−* Article
−* BlogPosting
−* FAQPage
−* HowTo
−* BreadcrumbList
+A. Establish the evidence baseline
+- Inventory every supplied or successfully accessed source with source name, type, coverage date, relevant URL or query, access status, and limitations.
+- Normalize known URL variants and note unresolved canonical, redirect, indexability, or duplication questions without claiming they were technically tested.
+- Summarize available performance by matching date range and dimension where possible: clicks, impressions, CTR, average position, landing-page engagement, and conversions tied to [Business goal and conversion]. Preserve “not provided” values.
+- Record data conflicts, freshness concerns, and any evidence too weak to support a decision.
 
−Only recommend schema that fits the content naturally.
+B. Determine probable search intent
+- Classify the likely primary and secondary intent behind [Target keyword] using supplied query data and SERP evidence where available.
+- Describe the audience’s likely questions, desired format, depth, trust requirements, and next action.
+- Compare those expectations with the current article. Distinguish observed mismatch from an unvalidated intent hypothesis.
+- Note intent ambiguity, mixed SERPs, seasonality, localization, or query drift that could change the recommendation.
 
−12. Prioritize the refresh plan.
−    Create a priority table with:
−    Task | Impact | Effort | Priority | Reason
+C. Audit the current article
+Assess the supplied article text for:
+- satisfaction of the primary question and information hierarchy;
+- accuracy, freshness, source support, first-hand experience, and trust signals;
+- thin, repetitive, obsolete, unsupported, or off-intent passages;
+- missing definitions, steps, examples, caveats, comparisons, visuals, or decision support;
+- heading clarity, scannability, accessibility, mobile readability, and conversion continuity;
+- natural use of the target and secondary terms without prescribing fixed keyword density;
+- title and meta alignment, avoiding unsupported claims or truncation-sensitive wording;
+- link usefulness, anchor clarity, destination relevance, and likely orphan-page opportunities based only on the supplied inventory.
 
−13. Create a post-refresh verification checklist.
−    Include:
+For each material finding, provide location, evidence class, supporting source, consequence, confidence as High/Medium/Low, and proposed treatment: keep, update, expand, merge, move, remove, or rewrite.
 
−* Keyword placement checked
−* Search intent checked
−* Title/meta updated
−* Headings improved
−* Outdated content removed
−* New sections added
−* Internal links added
−* External sources added
−* FAQ added where useful
−* Schema reviewed
−* Formatting improved
−* Mobile readability checked
−* Indexing/crawlability checked
+D. Compare SERP and competitor evidence
+- Use only the supplied or successfully accessed [SERP and competitor evidence].
+- Identify recurring result formats, content patterns, questions, subtopics, depth, freshness, trust signals, and differentiators.
+- Separate broad SERP patterns from observations about an individual competitor.
+- Do not infer traffic, authority, structured data, or ranking causes from appearance alone.
+- Identify worthwhile coverage gaps, but reject irrelevant competitor topics and imitation that would weaken audience fit or brand differentiation.
 
−14. Recommend performance monitoring.
−    Suggest how to track results using:
+E. Design the refresh
+- Create a refreshed H1/H2/H3 outline mapped to intent and audience questions.
+- Give a section-level disposition and precise change instruction. Preserve strong material and explain removals.
+- Provide three title options and three meta-description options, followed by one recommended pair. Explain intent fit, differentiation, claim support, and likely display-length risk; do not promise that a search engine will display the supplied metadata.
+- Suggest useful FAQ content only where it answers genuine reader questions. Provide answer direction, required evidence, and the recommended on-page location.
+- Recommend internal links only to destinations supported by [Internal link inventory]. For each, provide source location, destination, suggested natural anchor, reader value, and whether a reciprocal link is worth editorial review. Mark unverified destinations as candidates, not approved links.
+- Identify external citation needs by claim location, evidence type required, preferred primary-source class, freshness requirement, and validation owner. Do not fabricate citations.
+- Evaluate Article or BlogPosting, BreadcrumbList, FAQPage, and HowTo schema only when visible content and current search-engine eligibility guidance support them. Distinguish valid markup from eligibility for enhanced search presentation, and require technical validation after implementation.
 
−* Google Search Console
−* Google Analytics
−* Rank tracking
−* Click-through rate
−* Impressions
−* Average position
−* Engagement metrics
−* Conversions or business goals
+F. Prioritize and define the handoff
+Score each action using stated qualitative criteria for expected impact, confidence, effort, dependency, and risk. Rank high-confidence intent, accuracy, and usability fixes ahead of speculative additions. Identify the owner, approver, prerequisite, rollback consideration, and status for each action.
 
−Output format:
+G. Define verification and measurement
+- Convert [Definition of done] into measurable acceptance checks.
+- For every check, report the expected observation, current or actual observation, evidence, and state: Pass, Fail, Blocked, Not tested, or Not applicable.
+- Never mark a check Pass without evidence. Because this is a planning run, implementation-dependent checks should normally be Not tested unless post-change evidence was actually supplied.
+- Include pre-publication checks for factual support, intent coverage, title/H1 consistency, link destinations, anchor relevance, accessibility, mobile presentation, brand compliance, plagiarism or licensing concerns, and required specialist approval.
+- Include post-implementation checks for rendered title and meta directives, canonical target, indexability, HTTP status, crawlability, links, structured-data validation, sitemap inclusion where applicable, and analytics or conversion tracking. Assign these to an authorized implementer; do not claim ChatGPT performed them.
+- Reconcile every recommended action with the final outline and priority table. List omissions, duplicates, unresolved conflicts, and blocked decisions.
+- Define a monitoring plan with a documented pre-change baseline, publication annotation, comparison windows appropriate to traffic and seasonality, query/page/country/device segmentation, and measures from [Performance evidence]. Avoid ranking guarantees and avoid attributing movement to the refresh without sufficient evidence.
 
−Executive Summary
+REQUIRED OUTPUT
 
−Search Intent Analysis
+1. Decision Header
+- Brief status: Ready for review, Preliminary, or Blocked—clarification required
+- Article, target query, audience/market, business goal, approval scope, definition of done
+- Top recommendation, top risk, and next human decision
 
−Current Content Issues
+2. Clarifications, Assumptions, Unknowns, and Conflicts
+Use a table: Item | Classification | Why it matters | Safe interim treatment | Owner or evidence needed
 
−Competitor and SERP Gap Analysis
+3. Evidence Register
+Use a table: Evidence ID | Source or URL | Evidence type | Coverage/access date | Access status | Relevant observation | Limitation
 
−Content Gap Table
+4. Baseline and Search Intent Assessment
+Include available performance metrics with date ranges and filters, inferred primary/secondary intent, audience expectations, current satisfaction assessment, confidence, and validation needs.
 
−Recommended New Outline
+5. Current Content Findings
+Use a table: Article location | Finding | Evidence class and ID | Consequence | Disposition | Recommended change | Confidence
 
−Section-by-Section Refresh Plan
+6. SERP and Competitor Gap Assessment
+Use a table: Pattern or gap | Evidence ID | Recurrence or scope | Relevance to audience | Opportunity | Caveat | Confidence
 
−Title and Meta Description Recommendations
+7. Recommended Information Architecture
+Provide the proposed H1/H2/H3 outline. Map each section to intent, audience question, evidence requirement, and disposition of existing copy.
 
−Internal Linking Recommendations
+8. Section-by-Section Refresh Brief
+Use a table: Current section | Action | Exact editorial instruction | Material to preserve | Evidence/citation needed | Acceptance criterion | Priority
 
−External Source and Citation Recommendations
+9. Title and Meta Options
+Provide three title and three meta-description options, one recommended pair, rationale, supported-claim check, and display-length caveat.
 
−FAQ Recommendations
+10. Link Plan
+Use a table: Type | Source location | Destination | Suggested anchor | Reader value | Destination verified? | Approval or follow-up
 
−Schema Recommendations
+11. Citation and Claim-Support Register
+Use a table: Claim or section | Evidence required | Preferred source class | Freshness requirement | Supplied source | Validation status | Reviewer
 
−Priority Action Plan
+12. FAQ and Schema Eligibility
+For each FAQ, give question, answer direction, evidence need, and placement. For each schema candidate, give visible-content prerequisite, recommendation, reason, implementation owner, and validation requirement.
 
−Post-Refresh Verification Checklist
+13. Prioritized Action Register
+Use a table: Action | Expected impact | Confidence | Effort | Risk | Dependency | Priority | Owner | Approver | Status
 
−Performance Monitoring Plan
+14. Verification and Acceptance Matrix
+Use a table: Check | Expected observation | Actual/current observation | Evidence | State | Owner | Resolution needed
 
−Final Recommendations
+15. Monitoring Plan
+Include baseline period, publication annotation, review windows, segments, metrics, business outcome, interpretation cautions, and decision thresholds. If numeric thresholds were not supplied, propose them for approval rather than inventing accepted targets.
 
−Verification:
−Before finalizing, check that:
+16. Human Handoff
+List decisions requiring approval, specialist reviews, blocked items, implementation sequence, rollback preparation, and the evidence that must be collected before anyone may claim the refresh was implemented, validated, or successful.
 
−* Recommendations are specific and actionable.
−* The refresh plan matches the target search intent.
−* The article’s existing authority and useful content are preserved where appropriate.
−* Internal linking recommendations are practical.
−* High-impact tasks are prioritized first.
−* You do not claim to have reviewed URLs unless the content or summaries were provided.
+FINAL INTEGRITY CHECK
 
−Begin the SEO content refresh strategy now.
+Before returning the brief:
+- Ensure every material conclusion has evidence, a declared assumption, or an explicit unknown.
+- Ensure no inaccessible page is described as inspected.
+- Ensure recommendations remain inside [Approval scope].
+- Ensure factual, regulated, legal, privacy, licensing, and brand risks are routed to appropriate human review.
+- Ensure proposed, approved, implemented, tested, indexed, and measured states remain distinct.
+- Ensure no ranking, traffic, display, indexing, or rich-result outcome is guaranteed.
+- Ensure the acceptance matrix contains expected and actual observations, evidence, states, owners, and unresolved work.
+- Ensure the final recommendation preserves useful existing authority and content where the evidence supports doing so.