Prompt Library

Content Refresh Prompts for Controlled Updates

Compare existing content with verified new evidence, identify decay, preserve useful sections, and produce a reviewable update plan.

This reviewed prompt collection is for content teams, SEOs, and publishers updating an existing asset. It separates current facts supplied by the editor from model suggestions and preserves material that still serves the reader.

When to use these prompts#

Use this page when you need prompts that compare supplied old content with verified new facts, preserve useful sections, identify decay, and produce a human-review change plan. Replace every bracketed variable with verified, non-sensitive information before using a template in your own AI product.

Inputs to prepare#

  • current page text and original purpose
  • current audience and target queries
  • dated performance or feedback data supplied by the team
  • verified new facts, sources, product changes, or regulations
  • sections known to be stale or inaccurate
  • sections that perform well or must remain
  • new business and reader goals
  • required approvals and publication deadline

Draft prompt templates#

1. Refresh gap and change plan#

Purpose: Diagnose what should change before rewriting.

Prompt template
Compare [CURRENT CONTENT] with [VERIFIED NEW FACTS AND SOURCES], [CURRENT AUDIENCE], and [PERFORMANCE NOTES]. Create a change plan with keep, update, remove, merge, and investigate categories. For each item cite the source section, reason, evidence, risk, and reviewer needed. Do not invent current statistics, rankings, regulations, or product details.

Before use, remove irrelevant fields, replace every placeholder, and verify that the requested judgment can be supported by the material you supplied.

2. Fact and freshness audit#

Purpose: Find claims that need confirmation or timestamps.

Prompt template
Audit [CONTENT] for dates, numbers, product behavior, named roles, external links, regulatory statements, and time-sensitive recommendations. Cross-check only against [SUPPLIED CURRENT SOURCES]. Mark each item current, outdated, unsupported, or needs expert review. Do not rewrite unsupported claims as if they were confirmed.

Before use, remove irrelevant fields, replace every placeholder, and verify that the requested judgment can be supported by the material you supplied.

3. Controlled section rewrite#

Purpose: Update selected material while preserving approved sections.

Prompt template
Rewrite only these sections of [CONTENT]: [SECTIONS]. Use [VERIFIED FACTS], preserve [APPROVED MATERIAL], and target [AUDIENCE AND INTENT]. Show the revised sections, a change log, removed claims, and open questions. Do not alter unaffected sections or add facts beyond the supplied sources.

Before use, remove irrelevant fields, replace every placeholder, and verify that the requested judgment can be supported by the material you supplied.

Why the structure matters#

Refreshing content is an evidence-management task, not simply a request to “make it better.” These prompts require a dated source set, preserve useful material, and produce a change log that editors can verify.

Weak prompt and what it misses#

Prompt template
Update this old article for SEO and add the latest information.

The model is not given current sources, a date, performance evidence, or a definition of what is stale. It may invent “latest” facts, replace useful sections, or optimize for generic keywords.

Human review checklist#

  • Verify every changed fact against a current authoritative source.
  • Keep a record of removed claims and why they were removed.
  • Check redirects and internal links after structural edits.
  • Preserve sections that still answer the reader’s task.
  • Update visible dates only when the page received a substantive reviewed change.

Testing and maintenance#

  1. Use original, non-sensitive sample values when testing a prompt.
  2. Retest examples after material changes to the prompt, page, or AI product.
  3. Check factual preservation, requested format, missing-data behavior, and task-specific risks.
  4. Update the visible test date when a material retest is completed.
  5. Keep the site operator responsible for the final human review.

A dated operator attestation is sufficient for the site's internal publication check; full chat transcripts are not retained or published.