Current state
Search data is the Google Search Console foundation for Growth and higher teams. It is meant to help PromptScout use first-party search demand as context when prioritizing pages, queries, and weekly Tasks.
Do not treat this as fully shipped Search Analytics until the full sync, read models, and dashboard UI are available in-product. In the current Integrations surface, Google Search Console is still framed as a Search data card with beta/foundation language rather than a complete analytics report.
What Search data is for
Search data helps answer context questions around AI visibility work:
- Which pages already have Google Search demand?
- Which queries might map to monitored prompts?
- Which content or comparison Task should be prioritized first?
- Which page has enough search context to make a Content brief more useful?
Search data should stay separate from Traffic. Search Console reports Google Search performance. Traffic records website-layer request observations from the installed collector.
What it should not claim
Search data should not claim:
- that PromptScout has fully shipped Search Analytics if the UI still shows the integration as disabled or coming soon.
- that Google Search Console explains why an AI answer changed.
- that Search impressions, clicks, or query movement caused AI visibility movement.
- that a Search Console connection is required for PromptScout monitoring, citations, Traffic, or Content briefs to work.
Use Search data as prioritization context beside prompt, citation, source, website, Traffic, and Task evidence.
How it fits the weekly workflow
When Search data is available, use it during the weekly review after reading Today, Morning brief, AI Visibility Changes, and Tasks.
Good uses:
- Prioritize a comparison Content brief when the target page or query already has search demand.
- Compare a Task's prompt group with related Search Console query context.
- Add Search context to the completion receipt so the next review knows why the work was prioritized.
- Review Search movement beside observed AI visibility movement without calling it causal proof.
Availability language
Use this language when describing the current state:
- "Search data beta"
- "Google Search Console foundation"
- "Growth+ Search data context"
- "Search Analytics foundation until sync, read models, and UI are fully shipped"
Avoid language like:
- "complete Search Analytics dashboard"
- "proves AI traffic impact"
- "attributes AI visibility movement to search demand"
- "fully launched GSC reporting" when the visible UI still says coming soon or disabled.
Next steps
- Use Weekly workflow to see where Search context belongs.
- Use Traffic for website-layer AI referral visits, AI user fetches, and crawlers.
- Use Content when Search context and evidence support a page brief.