Performance Tracking
Google Search Console
GSC shows what happens after publishing — the data that closes the loop:
- Queries — which keywords drove impressions
- Clicks — organic click volume
- Impressions — how often pages appeared in search results
- CTR — click-through rate
- Average Position — ranking performance
- Indexing — which pages are indexed
- Errors — technical issues affecting search visibility
GSC Performance API
The Google Search Console API is free and can pull:
| Data | Endpoint |
|---|---|
| Search analytics | searchanalytics.query |
| URL inspection | urlInspection.index.inspect |
| Sitemap list | sitemaps.list |
Recommended data structure in a separate CSV:
PID,Site,URL,Keyword,Date Start,Date End,Clicks,Impressions,CTR,Avg Position,Device,Country,Last Pulled
info
GSC data is delayed 1–3 days and retains ~16 months of history. Pull weekly or monthly and store in a separate CSV keyed by PID and URL.
Content Refresh Cycle
| Phase | Timing | Action |
|---|---|---|
| Publish | Day 0 | Content goes live |
| Monitor | 30 days | Check indexing and initial impressions |
| Assess | 90 days | Review clicks, position, and queries |
| Refresh | 6–12 months | Update data, add new FAQ, improve weak sections |
Suggested Reporting Cadence
- Weekly: Pipeline status review, new keyword opportunities
- Monthly: GSC performance report, top winners/decliners
- Quarterly: Full content audit, refresh candidates, strategy adjustment
GSC CSV Architecture
The GSC tracking file is kept separate from the production pipeline CSV:
content-pipeline.csv → Production (keyword → publish)
gsc-performance.csv → Performance (post-publish tracking)
Connect them through PID and URL for end-to-end reporting.