analytics-console-review

Analytics console review

Use this method when the required evidence exists in a provider console but the toolkit has no configured API client for it. The browser belongs to the agent host, not SEOHEAD Tools: this skill does not bundle a browser, open a remote service, or make a provider integration appear to exist.

Preflight

Before navigation, establish a scope ticket with:

• provider and already-authorized account;
• exact property, counter, container, or project;
• report and comparison periods;
• dimensions, metrics, filters, and search type;
• an ignored local output directory, for example _sandbox/analytics-console-review/2026-08-30/.

If the request says only “search traffic,” ask which evidence source is intended: GSC, Bing Webmaster, Yandex Webmaster, or a web-analytics platform. Do not assume that GSC access exists.

Ask the user to handle sign-in and account selection. Never type credentials, inspect cookies or tokens, open developer storage, or switch to another property to bypass missing access.

Report one explicit readiness state before collecting data:

• browser unavailable;
• sign-in required;
• property selection required;
• access denied;
• read view available;
• export available;
• export unavailable.

When sign-in, property, or access is missing, stop console work with a concise handoff:

Readiness: sign-in required | property selection required | access denied
Provider: <provider or unresolved>
Needed from the user: sign in, select <property>, approve read-only review
Proposed scope: <report>, <period A> vs <period B>, <dimensions/metrics>
First export: <smallest aggregate table>
No settings, users, tags, sitemaps, or saved reports will be changed.

Read and export boundary

The user may authorize navigation, temporary report filters, aggregate table review, and named file downloads for the scoped task. A local download is not permission to share, commit, upload, or keep the data indefinitely.

Do not collect raw session recordings, ClientID or user identifiers, cookies, authentication material, unrestricted event logs, or browser network archives. Prefer aggregate CSV/XLSX exports and record when the UI exposes only a truncated or sampled view.