RedHub AIRedHub AI
Tool Gate · How it works

How the gate works

How the Content Refresh gate works

This tool grades an old page to decide whether it's worth refreshing. It scores 6 weighted controls into a 0–100 number — then a gate that can only make the verdict worse.

The 6 weighted controls

01Traffic decaywt 22
02Search opportunitywt 20
03Update valuewt 18
04Business valuewt 16
05Fix feasibilitywt 12
06Accuracy & safetygate · at 0wt 12
REFRESH NOW
score 78+
WORTH A REFRESH
score 55+
LOW PRIORITY
below floor
REWRITE OR RETIRE
a publish-blocker at 0–1
Publish-blocker · worsen-only

A publish-blocker at 0 or 1 — no business value, no fix feasibility, or an accuracy/safety problem — forces REWRITE OR RETIRE regardless of the refresh score. A high-traffic page you can't make accurate or safe isn't a refresh candidate; it's a liability.

80/100
REWRITE OR RETIRE

Why: Traffic decay, search opportunity, and update value are all maxed — the refresh score is 80, which reads REFRESH NOW. But accuracy & safety is at 0 (a publish-blocker): the page is built on stale, wrong claims. The gate forces REWRITE OR RETIRE — you can't refresh outdated statistics into accuracy, you rebuild or retire.

Fix firstAccuracy & safety is at 0 — the page has stale or unsafe claims a refresh can't salvage. Rewrite it from scratch or retire it; don't re-publish outdated statistics as current.

A high score didn’t save it. The score is context; the gate is the answer — and it names the one thing to fix first. Your own inputs, scored offline. Grades the page, not the author.