Document Search Console AI report navigation

[harrisboatworks]

Summary

• distinguish Search Console's AI-powered filter configurator from the Generative AI performance report
• document stable report routes and subset-rollout unavailable states
• note that Search Analytics searchAppearance rows are only corroboration

Verification

• confirmed with an authenticated Search Console property
• verified final routes, visible labels, and unavailable-report screenshot state

---

Summary by cubic

Added a new docs page on Google Search Console performance reports. It lists stable routes for the standard and Generative AI reports, shows how to distinguish the AI filter configurator, gives quick verification steps and subset-rollout "not found" behaviors, and clarifies that searchAppearance API rows are only corroboration.

^{Written for commit 2d26f18. Summary will update on new commits.}

[browser-harness-review]

✅ Skill review passed

Reviewed 1 file(s) — no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2d26f1817a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

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]

2 issues found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="domain-skills/google-search-console/performance-reports.md">

<violation number="1" location="domain-skills/google-search-console/performance-reports.md:1">
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.</violation>

<violation number="2" location="domain-skills/google-search-console/performance-reports.md:31">
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.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

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>

[cubic-dev-ai]

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>