What it does

Assesses a specific, already-published article and — if warranted — revises and republishes it in place. Handles light-to-moderate updates through the same review and approval gate as new content.

Why you should use it

Content that ranked well can decay over time. This workflow is the targeted fix, without rewriting an entire article from scratch through Full Content Pipeline.

Before you can use it

You need an existing article to refresh — this workflow updates something that already exists, it doesn’t create anything new. Find one in Content Library and note its article ID (visible on the article’s detail panel — see Understand Your Results) and its domain ID.

Where to find it

Trigger it by its ID, content-refresh.

What information you must enter

The optional fields help the assessment step decide how much revision is warranted — they’re not required to run it.

Step-by-step

1

Find the article and its ID

Content Library → click the article → note its details.
2

Trigger the workflow

3

Wait for the assessment

The first step decides whether — and how much — revision is actually needed.
4

Approve the revision

Same mandatory human checkpoint as new content — see Take Action.

What happens after you click Trigger run

An assessment step decides the refresh’s scope first. This workflow only handles light-to-moderate revisions — a full rewrite isn’t performed here (if that’s what’s actually needed, that’s a job for a fresh full-content-pipeline run instead).

How long-running work is shown

Same live execution timeline as any workflow. Budget-capped lower than the full pipeline ($2.00 max) since it’s a targeted edit, not a full article from scratch.

How to understand the output

What action to take based on the output

  • refresh_needed: false → nothing else to do; the article didn’t need changes yet.
  • Refreshed and republished → check Analytics over the following weeks to see if position/traffic recovers.

Common mistakes

  • Triggering this on an article that hasn’t actually lost ranking — it’s meant for maintenance, not routine editing.
  • Forgetting article_id must belong to an article that already exists and is published — this isn’t a way to create new content.

Troubleshooting

See Troubleshooting.