Refresh Tasks
Refresh tasks are actionable items created when PageBridge detects content decay. They bridge the gap between data analysis and editorial action.
Task lifecycle
- Detection — the DecayDetector identifies a page with declining performance
- Creation — the TaskGenerator creates a
gscRefreshTaskdocument in Sanity with context about the decay - Review — editors see the task in the Refresh Queue with severity, reason, and suggested queries
- Action — editors refresh the content, optimizing for the queries that drive traffic
- Resolution — the task is marked as done, snoozed, or dismissed
Task structure
Each refresh task contains:
- Linked document — reference to the Sanity content document
- Linked site — reference to the gscSite document
- Reason —
position_decay,low_ctr, orimpressions_drop - Severity —
low,medium, orhigh - Metrics at detection — position before/now, CTR before/now, current impressions
- Query context — top 5 search queries driving traffic to this page (with impressions, clicks, and position for each)
- Notes — editors can add notes when snoozing or dismissing
Deduplication
The TaskGenerator checks for existing open or in-progress tasks for the same page and reason before creating a new one. This prevents duplicate tasks from accumulating across sync runs.
Using query context
Each task includes the top search queries driving traffic to the page. This is the most actionable piece of information for editors:
- High impressions, low clicks — the page appears in search results but does not attract clicks. Consider improving the title tag and meta description.
- Dropping position — a specific query is losing rank. Review whether the content still answers the search intent for this query.
- New queries appearing — the page may be ranking for queries it was not designed for. Consider creating targeted content for these queries.
Manual tasks
Tasks can also be created with reason manual for cases where an editor identifies a page needing refresh through their own analysis.