Guides

GSC + crawl correlation

Find pages that drive traffic but score poorly in your latest crawl — fix those first.

Workflow

1. Link Search Console to the property in the dashboard (one-time).
2. Optional: POST /properties/:id/gsc/sync (gsc:write) to refresh GSC data before analysis.
3. Queue a crawl: POST /properties/:id/scans.
4. Poll GET /jobs/:id until status: completed.
5. Fetch GET /properties/:id/gsc and read snapshot.crawlCorrelation.

Reading crawlCorrelation

Each row typically includes:

• pageUrl — URL present in both GSC and crawl data
• clicks / impressions — 28-day GSC traffic
• score — latest crawl score for that URL

Sort by clicks descending, filter where score < 70 (or your threshold), and export to your task tracker.

Cross-check with issues API

After the crawl completes, list open issues: GET /properties/:id/issues?status=open. Match pageUrl on critical issues against high-click URLs from GSC.

Example requests

# Refresh GSC (optional)
curl -X POST -H "Authorization: Bearer xf_live_..." \
  https://api.xenonflare.com/api/v1/properties/PROPERTY_ID/gsc/sync

# Queue crawl
curl -X POST -H "Authorization: Bearer xf_live_..." \
  https://api.xenonflare.com/api/v1/properties/PROPERTY_ID/scans

# After job completes — full GSC payload with correlation
curl -H "Authorization: Bearer xf_live_..." \
  https://api.xenonflare.com/api/v1/properties/PROPERTY_ID/gsc

Field reference: GSC snapshot fields.

Related

• Nightly crawl automation
• Search Console setup
• GSC snapshot fields
• Developer API reference
• Idempotency guide
• Site audit API
• SEO automation API