Kept AI
Back

Content Creation

Build a page refresh review queue

Use saved history and current citations to identify pages worth inspecting.

Connect your Kept MCP
Kept AIAI assistantYour workspace
Open Kept AI

Command

Use my supplied host, owned URL inventory, saved citation export, and days of 7, 30, or 90. Confirm the host through list_projects. Read list_sources({host,kind:"urls",days,limit:100}), get_gap_analysis({host,days}), and get_agent_analytics({host,section:"crawlability",days}). Match owned pages to current records and compare only compatible historical measures from my export. Build a refresh queue with evidence of decline where available, competitor context, crawlability questions, and suggested review scope. Without history, label entries current inspection candidates rather than losing pages. Propose editorial briefs for approval; these read-only tools cannot fetch arbitrary page bodies, edit content, or publish refreshes.

What you need

  • Supply an owned URL inventory, a visible host, and a supported window.
  • Provide a historical citation export to identify decline; publishing requires separate access.
Read the setup guide

Find pages with a reason to investigate

Match your owned inventory against current citations and historical evidence where available. The queue separates observed declines from pages that simply lack a current match, preserving coverage limitations and making each candidate’s reason for review easy for an editor to inspect.

Scope refresh work before drafting changes

Attach an editorial investigation brief, competitor context, and relevant crawlability questions to each candidate. Reviewers can decide whether the next step is content research, technical inspection, or no change, rather than treating every missing citation as a reason to rewrite a page.