Current state
Search data beta is available to Growth and higher teams. Connect Google Search Console from Integrations → Search data, choose the property for the current brand, then use Sync now to cache the latest page and query demand for Tasks.
Connection and sync are always explicit actions. Opening Integrations does not contact Google or start a refresh, and PromptScout does not schedule background Search Console refreshes.
Connection and refresh
Each Search Console connection belongs to one team and one brand. After Google OAuth, select the exact Search Console property that represents that brand. You can change the property or disconnect and reconnect when the brand context changes.
Use Sync now to request a Search Analytics refresh. PromptScout enforces a 24-hour cooldown after a successful sync and displays the next available UTC time in the card. If a sync fails, the last successful cached reporting window remains visible; use Retry sync after checking the selected property's access.
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 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 "Google Search Console Search data beta" or "Growth+ Search data beta". It is a compact cached summary for weekly prioritization, not a complete Search Analytics dashboard.
Avoid language like:
- "proves AI traffic impact"
- "attributes AI visibility movement to search demand"
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.