← ClaudeAtlas

content-refresh-performance-tracker-and-dashboardlisted

Builds a content-refresh performance tracker and dashboard and updates it weekly. It measures each refreshed page's Google search impact against that page's own go-live date (since-refresh delta against an equal-length pre-refresh window, +7/+14/+28/+90 day milestones, net of a sitewide control), gives every page a verdict (Winner, Holding, Rank slipped, Decliner, Demand-drop, Maturing, No data), and ships a tidy append-only Excel workbook plus an optional Looker Studio dashboard kept current by a weekly scheduled task. The first step is always to ask where the go-live dates live (tracking sheet, CMS, sitemap or a manual list). Use when someone asks "did our content refreshes work", wants a refresh-performance dashboard, post-update SEO impact per page, refresh tracking, rollback candidates after a content update, or a weekly refresh report. Portable through a per-site config.json.
savenjudesajen/seo-aeo-agent-skills-tools · ★ 0 · Data & Documents · score 73
Install: claude install-skill savenjudesajen/seo-aeo-agent-skills-tools
# Content Refresh Performance Tracker & Dashboard Home page: [unilytics.ai/skills/content-refresh-performance-tracker-and-dashboard](https://unilytics.ai/skills/content-refresh-performance-tracker-and-dashboard/), the canonical source of this skill. Answer one question rigorously: **are the content refreshes working: which pages went up, which went down, and is the refresh program lifting search performance over time?** For every refreshed page, measure the impact **anchored to that page's own go-live (refresh) date**, net of a sitewide control, and roll it into a tidy Excel workbook plus an optional Looker Studio dashboard that a weekly task keeps current. Related public skills: this is the refresh-impact sibling of `gmb-multi-location-looker-studio-dashboard` (same build, verify and scheduled-refresh discipline), and it reuses `gsc-url-queries` for fast per-URL Search Console pulls. Use those rather than rebuilding them. ## Before you start (every run) 1. **Load the config.** Read `data/config.example.json` for the shape, then get or confirm this site's `config.json`: Search Console property, go-live-date source, milestones, output paths, the Google account that owns Search Console and Looker Studio, and the dashboard source type. Nothing is hard-coded; every value is a runtime input. 2. **Check tools.** Confirm you can read Search Console data for the property (see Tools). If the site already has a tracker workbook, open it: this run appends to it, it neve