Prompt

7 minute read

Content Refresh Brief Prompt: Plan Evidence-Based Updates

A reusable content refresh brief prompt that compares an article with verified updates and queries, then lists what to keep, update, add or remove, each tied to evidence.

Abstract illustration for Content Refresh Brief Prompt: Plan Evidence-Based Updates

This content refresh brief prompt compares an existing article with the evidence you collect and returns a brief for the writer. It lists outdated parts, missing parts and parts to keep, and it ties every suggested change to a source or a data point. The writer then updates the page, and an editor checks the facts.

The page explains each variable, gives the full prompt and shows one real run on an invented article. It also lists the checks that stop a refresh from becoming a cosmetic date change. Google's guidance warns against changing dates without making substantive changes, so the brief asks for real updates only.

What this content refresh brief prompt does

The prompt reads three things: the current article, a list of verified updates such as new documentation or product changes, and optional Search Console queries. It then sorts each part of the article into keep, update, add or remove, with a reason for each.

It must not write the new article or invent facts. When it thinks something may be outdated but you gave no evidence, it marks the item "verify" and names the source to check. As a result, the brief stays a list of decisions a person can approve.

When to use it

Use it when a page has lost clicks, describes a product or policy that changed, or simply has gone months without a review. It works best on one article at a time.

  • A guide refers to features, prices or steps that have changed.
  • Search Console shows queries the article does not answer well.
  • You are planning a quarterly refresh and need briefs for several writers.

However, if the page's whole purpose no longer fits what searchers want, a brief is not enough. Decide first whether to rewrite, merge or retire the page.

Inputs and variables

Replace every bracketed variable before you run the prompt. The evidence list matters most, because the model cannot browse or know what changed.

  • [ARTICLE_TEXT]: the current article, with headings, as plain text or Markdown.
  • [VERIFIED_UPDATES]: facts you have confirmed, one per line, each with its source URL and date.
  • [QUERIES]: optional top queries for the page from Search Console, with impressions and clicks. Write "none" if you skip them.
  • [READER]: who the article serves, for example "home mechanics with basic tools".

Use only public sources and your own site data. Do not paste unpublished plans or customer information into a public AI tool.

Reusable prompt — version 1.0

Copy the prompt below as it is. It forces a reason and an evidence reference for every change.

You are helping an editor plan a refresh of an existing article for [READER].

<task>
Compare <article> with <updates> and <queries>, then write a refresh brief. Do not rewrite the article.
</task>

<rules>
1. Sort each section of the article into KEEP, UPDATE, ADD or REMOVE.
2. Every UPDATE, ADD or REMOVE must cite an item from <updates> or a row from <queries>.
3. If you suspect something is outdated but no update supports it, label it VERIFY and name the kind of source that would settle it.
4. Never invent facts, statistics, dates, prices, search volumes or quotes.
5. Do not recommend changing the published or updated date unless the brief contains substantive changes.
6. Flag any query that the article's purpose does not fit, instead of adding a section for it.
</rules>

<output_format>
1. Summary: two sentences on how much needs to change.
2. Table: section | decision | what to change | evidence
3. List: VERIFY items with the source to check
4. List: queries that do not fit this page
5. Suggested new title, only if the main topic changed
</output_format>

<article>
[ARTICLE_TEXT]
</article>

<updates>
[VERIFIED_UPDATES]
</updates>

<queries>
[QUERIES]
</queries>

Rules 2 and 3 do the real work. Together they separate changes you can make today from questions someone must answer first.

How to use it

Any capable chat model can run this content refresh brief prompt. Long articles fit best in models with a large context window.

  1. Collect the changes since you wrote the article, each with a source and date.
  2. Export the page's top queries from Search Console if you have them.
  3. Fill in the variables, paste the prompt into a new chat and run it.
  4. Resolve every VERIFY item before you hand the brief to a writer.
  5. After the update, check that each change in the brief made it into the page.

Example input and output

We ran version 1.0 once on Claude Opus 5.5 on November 15, 2026. The article and updates are invented for this example; the output is trimmed, and trims are marked with "…".

READER: home mechanics with basic tools
ARTICLE_TEXT: (an invented 900-word guide, "How to adjust disc brakes",
with sections: Tools, Centre the caliper, Fix rubbing, When to see a shop)
VERIFIED_UPDATES:
- The shop now sells a pad spacer tool; product page updated
  November 2, 2026 (northwind.example/tools/pad-spacer).
QUERIES:
- disc brake rubbing: 1840 impressions, 12 clicks
- hydraulic brake bleeding: 300 impressions, 0 clicks
1. Summary: The guide is mostly current. One tool section needs an
update and the rubbing section should come earlier.

| section | decision | what to change | evidence |
| Tools | UPDATE | Mention the pad spacer as an option | Update 1 |
| Fix rubbing | UPDATE | Move it up; it matches the top query | Query: disc brake rubbing |
| Centre the caliper | KEEP | — | — |
…
3. VERIFY: torque values in "Centre the caliper"; check the brake
   manufacturer's current manual.
4. Does not fit: "hydraulic brake bleeding" is a separate task; consider
   a dedicated guide instead of a new section.

In this run, each change cited an update or a query, and the model flagged an unrelated query instead of padding the guide. That single run is an illustration, not a benchmark.

How to check the output

Review the brief before anyone starts writing.

  • Evidence: every change points to a real update or query row that you supplied.
  • No invention: there are no new facts, numbers or dates without a source.
  • VERIFY items: settle each one with a primary source before writing.
  • Scope: queries that do not fit are not forced into the page.
  • Dates: the updated date changes only if the page changes substantively.

Troubleshooting

These fixes address the bad outputs we see most often.

  • The model rewrites whole sections: repeat "Do not rewrite the article" at the end.
  • Changes have no evidence column: add "leave the row out if you have no evidence" to rule 2.
  • Too many VERIFY items: supply more confirmed updates, or ask for the five most important.
  • It adds a section for every query: set a minimum, such as 200 impressions, in rule 6.

Limitations

The prompt knows only what you paste. It cannot check whether your updates are complete or whether competitors cover the topic better. Therefore, the quality of the brief depends on the evidence you collect first.

Outputs vary by model, version and input. The brief is a draft for an editor; the writer and editor remain responsible for accuracy, in line with Google's guidance on generative AI content.

Version history

Each version carries a date, so you can tell which prompt produced an older brief.

  • 1.0: November 15, 2026. First version, tested once on Claude Opus 5.5.

Frequently asked questions

Quick answers to the questions readers ask most about this topic.

Which AI models does this content refresh brief prompt work with?

Any capable chat model that follows structured instructions, such as current models from OpenAI, Anthropic or Google. Long articles need a model with a large context window. We tested it once on Claude Opus 5.5.

Can the prompt find what changed on its own?

No. It cannot browse or know about new releases. You supply confirmed updates with sources and dates, and the prompt marks anything it suspects but cannot support as VERIFY.

Should I change the updated date after a refresh?

Only when the page changed substantively. Google's guidance treats changing dates to make pages look fresh, without real changes, as a warning sign.

Does the prompt write the new version of the article?

No. It produces a brief with decisions and evidence. A writer makes the changes and an editor checks the facts before the update goes live.

Sources

These pages support the refresh guidance and the prompting approach above.

  1. Google Search Central: Creating helpful, reliable, people-first content developers.google.com
  2. Google Search Central: Guidance on using generative AI content developers.google.com
  3. OpenAI: Prompt engineering guide developers.openai.com
  4. Anthropic: Claude prompting best practices platform.claude.com