SS

SEO Republish Prioritizer

RPM-weighted recovery potential × probability of success. Four views mirror Raptive's SEO Workbook; per-signal breakdown and dollar-denominated scoring are ours. All numbers are mocked.

All
Sessions
233,325
Pages
246
7% vs YoY
Every post on the site
Updated
Sessions
76,493
Pages
66
0% vs YoY
Modified in last 4mo
New
Sessions
979
Pages
25
0% vs YoY
Published in last 12mo
All other
Sessions
156,505
Pages
168
10% vs YoY
Mature + untouched
Est. monthly revenue opportunity (actionable)
$391
Across 168 prioritized posts. Real (non-seasonal) component: $390 (100% of total).
40 posts flagged as seasonal — recovery comparison falls back to YoY same-window, not absolute peak. Refreshing won't recover the peak; wait for the seasonal cycle.
Updates landing
0
posts marked as actioned
Committed opportunity: $0
Outcome tracking placeholder. v1 will show 7/14/30/60d session + revenue delta vs the baseline captured at mark-as-actioned time.
Content by segment
Core46$122/mo opportunity
Evergreen140$268/mo opportunity
Seasonal15$1/mo opportunity
New25$1/mo opportunity
Low15$2/mo opportunity
Unknown5$1/mo opportunity
Recommendation mix
Consolidate16
Content update46
Title / meta refresh40
Expand30
Republish36
Leave alone78
Content age distribution
< 6 months14 (6%)
6–12 months11 (4%)
12–24 months66 (27%)
24–36 months135 (55%)
36+ months20 (8%)
Posts under 12 months are routed to New Pages, not the republish queue.
How this compares to Raptive's SEO Workbook
Parity
  • 4-view workflow (Scorecard / Pages to Update / New Pages / All Pages)
  • All / Updated / New / All other KPI strip with YoY framing
  • Cross-cutting segments taxonomy (Core / Evergreen / Seasonal / Low / New / Unknown)
  • Recommended Update Size (Small / Medium / Large / Overhaul)
  • Seasonal Period as concrete months on each row
  • Best Keyword as a first-class column
  • Outcome tracking stub via mark-as-actioned
Where we exceed
  • RPM-weighted recovery in $ — Raptive ranks by pageviews; we rank by monthly revenue
  • Per-signal "Why?" breakdown — every score decomposes into named signals; theirs is a colored bar
  • 6-way recommendation classifier paired with their Update Size — "title refresh + Small effort" beats either alone
  • Tunable weights surface in lib/weights.ts for iteration