Skip to content

Document Search Console AI report navigation #524

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
harrisboatworks wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Document Search Console AI report navigation #524

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions domain-skills/google-search-console/performance-reports.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
# Google Search Console performance reports

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Move the skill under the loaded domain-skills tree

This new skill is added under repo-root domain-skills/, but the harness only discovers skills from AGENT_WORKSPACE / "domain-skills" / <host-key> when BH_DOMAIN_SKILLS=1 (src/browser_harness/helpers.py:132-135), and the README points contributors to agent-workspace/domain-skills/. As committed, navigating to Search Console will never surface this guidance via goto_url; place it in the agent workspace domain-skills tree, using the key the loader derives for the target host, or update the loader/docs together.

Useful? React with 👍 / 👎.

@cubic-dev-ai cubic-dev-ai Bot Jul 14, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1: With domain skills enabled, agents will never discover this report because it is outside the agent workspace searched by goto_url(). Move it to agent-workspace/domain-skills/google-search-console/ so search.google.com navigation can return it.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At domain-skills/google-search-console/performance-reports.md, line 1:

<comment>With domain skills enabled, agents will never discover this report because it is outside the agent workspace searched by `goto_url()`. Move it to `agent-workspace/domain-skills/google-search-console/` so `search.google.com` navigation can return it.</comment>

<file context>
@@ -0,0 +1,31 @@
+# Google Search Console performance reports
+
+Use the user's already-authenticated Chrome session. Stop at the Google sign-in page; never enter credentials from screenshots or local files.
</file context>
Fix with cubic


Use the user's already-authenticated Chrome session. Stop at the Google sign-in page; never enter credentials from screenshots or local files.

## Stable routes

- Standard Search performance report:
`https://search.google.com/search-console/performance/search-analytics?resource_id=<URL-encoded property>`
- Generative AI performance report:
`https://search.google.com/search-console/performance/search-analytics/ai`

For a domain property, encode the complete value such as `sc-domain:example.com` when passing `resource_id`.

## Distinguish the two AI controls

The standard Performance report may show `Customize your Performance report using AI`. This is only an experimental filter/comparison configurator. It is not the separate Generative AI performance report for AI Overviews and AI Mode impressions.

Verify generative-report access independently:

1. Open the normal Performance report and screenshot the left navigation.
2. Check for a Generative AI, AI Overviews, or AI Mode report item.
3. Open the direct `/performance/search-analytics/ai` route.
4. Screenshot the result.

During subset rollout, an unavailable report can redirect to `/search-console/not-found` and visibly render `Page couldn't be found` even while the property is selected and normal Search Console access works. Opening the route without a selected property may instead show `Please select a property`; that is not proof of report access.

## API cross-check limitation

The Search Analytics API `searchAppearance` dimension is useful corroboration, but it is not a substitute for the UI-only Generative AI performance report. Ordinary rows such as `PRODUCT_SNIPPETS` or `TRANSLATED_RESULT` do not indicate AI Overviews or AI Mode report access.

After any navigation, use `page_info()` and a screenshot to verify the selected property, final route, visible report title, and error state.

@cubic-dev-ai cubic-dev-ai Bot Jul 14, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3: A screenshot can capture an intermediate route or loading view, producing a false access result after the direct AI navigation. Wait for the navigation to settle before inspecting the final route and UI.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At domain-skills/google-search-console/performance-reports.md, line 31:

<comment>A screenshot can capture an intermediate route or loading view, producing a false access result after the direct AI navigation. Wait for the navigation to settle before inspecting the final route and UI.</comment>

<file context>
@@ -0,0 +1,31 @@
+
+The Search Analytics API `searchAppearance` dimension is useful corroboration, but it is not a substitute for the UI-only Generative AI performance report. Ordinary rows such as `PRODUCT_SNIPPETS` or `TRANSLATED_RESULT` do not indicate AI Overviews or AI Mode report access.
+
+After any navigation, use `page_info()` and a screenshot to verify the selected property, final route, visible report title, and error state.
</file context>
Fix with cubic