Google Search Console
Google Search Console is Google's web service reporting how a property performs in Google Search and whether pages are indexed correctly.
Also known as: gsc · search-console
Why it matters
GSC is the ground truth for organic search visibility on Google, without it, opportunity scoring, decay detection, and CTR analysis are guesswork. It is the highest-ROI integration for Learn Domains activation.
How it works
Verify site ownership, submit sitemaps, and pull search analytics and coverage APIs. Data lags a few days but includes query-page dimensions competitors cannot infer from GA4 alone. OAuth connects with `webmasters.readonly` scope.
Common mistakes
- Verifying the wrong property, http vs https, domain vs URL-prefix.
- Ignoring coverage errors after template deploys.
- Judging performance on three-day windows only.
- Disconnecting OAuth without noticing stale brief data.
Best practices
- Use domain property when possible for full coverage.
- Sync after major migrations and monitor exclusions weekly.
- Segment branded vs non-branded performance.
- Pair GSC landing data with GA4 engagement metrics.
Learn Domains perspective
Connect Search Console and your Mission Brief stops guessing, it ranks opportunities from queries and pages you already rank for, like pushing a position-8 URL to page one, instead of keyword ideas with no data behind them.
FAQ
- Is GSC required for Learn Domains?
- Not on day one, but strongly recommended, most opportunity scoring needs query and page data.
- What OAuth scope is used?
- `webmasters.readonly`, read-only search analytics and coverage.
- How often does Learn Domains sync GSC?
- On a regular schedule plus manual Sync now from your vault integrations panel.
Next steps
- 1Connect GSC to your primary vault property.
- 2Run Sync now and confirm healthy status.
- 3Regenerate Mission Brief with fresh query data.
Knowledge graph
Parent terms
Child terms
Related concepts
google-analytics-ga4 · opportunity-engine · digital-asset-intelligence