Why SEO investigations are fragmented
A typical visibility review still means exporting GSC performance to one sheet, query data to another, and optionally pasting rank-tracker positions that do not share the same date range. By the time the story is assembled, the team has lost the thread of what moved first — traffic, queries or average position.
- Performance reviewed apart from query-level behaviour
- Ranking distribution checked in a separate export
- No shared timeline for deployments, annotations or Bing lag
- Hard to defend recommendations without a single operational record
ConsoleViewer keeps SEO performance investigation inside the project workspace: the same period, the same definitions, the same handoff from portfolio monitoring.
Performance, rankings and queries on one timeline
The performance card shows clicks, impressions, CTR and position. Query counting shows how queries distribute across position bands for that exact range. You are not reconciling two exports — you are reading one investigation.
- Align charts to the portfolio-selected period
- Compare Google and Bing where connected
- Overlay deployments and annotations on movement
Performance
Clicks + impressions
Query counting
Dataset coverage for the selected range
Search movement analysis from signal to explanation
Start from portfolio triage when a property card shows material delta. Open the project and read the performance shape — is the move click-led, impression-led or position-led? Move to query counting to see whether top positions grew or long-tail queries shifted.
Visibility change investigation
When clicks fall but impressions hold, the story is often CTR or SERP mix — not “rankings dropped.” When impressions rise and clicks lag, opportunity may be building in positions 4–10. The workspace is built for those reads, not for a single headline metric.
Root cause analysis examples
A deploy marker on the same week as a click lift supports release validation. An annotation records a template change. A Bing overlay shows whether Google movement is isolated. Together they form the root cause narrative you attach to SEO roadmaps when work ships.
From portfolio card to project investigation
Portfolio monitoring exists so you do not open thirty GSC properties every morning. When one card breaks pattern — click delta, impression softening or tracked-rank movement — you drill into this workspace with context already framed.
That handoff is deliberate: the portfolio tells you where to look; the investigation tells you what changed. Keyword tracking and roadmaps pick up when ongoing monitoring or tracked work is required.
Deep-dive analysis in practice
Category erosion: Impressions stable, clicks down, average position slightly worse — query counting shows growth in positions 11–20. Investigation confirms long-tail expansion without click capture; roadmap tasks target page types with highest impression share.
Post-deploy lift: Clicks and impressions rise together after a deployment marker. Performance and query bands move in sync; annotation documents the release for the next client report.
Brand vs non-brand: Traffic split (when branded terms are configured) separates brand defence from content opportunity — still on the same project timeline as performance.
How it fits into the ConsoleViewer workflow
Investigation sits between portfolio triage and tracked execution. Monitoring flags movement; this workspace explains it; keywords and roadmaps carry work forward.
- Step 1Portfolio monitoringSee which properties moved before you open a project.Learn more
- Step 2Investigation workspaceExplain performance, rankings and queries on one timeline.You are here
- Step 3Keyword trackingTrack priority terms with GSC and Bing context.Learn more
- Step 4SEO roadmapsTurn findings into prioritised, tracked work.Learn more
Supporting capabilities — custom dashboards, exports, MCP access and indexation monitoring — are documented on the capabilities hub.
How teams run investigations
Analysts open the project after portfolio triage with the same range the client expects in reporting.
Search leads validate a visibility ticket with performance and query evidence before involving engineering.
Compare investigation patterns across properties without rebuilding charts per domain.
Confirmed findings become prioritised tasks linked to the visibility period that triggered them.
Investigation workspace capabilities
Performance trends
Clicks, impressions, CTR and position on the project timeline with deployment and annotation overlays.
Ranking distribution
Query counts by position band — see whether movement is top-of-funnel or long-tail.
Query counting
Dataset coverage for the same date range as the performance chart — no range mismatch.
Operational context
Bing comparison, GA4 overlays and annotations on the axis where visibility actually moved.
Portfolio handoff
Open from portfolio monitoring when a property card flags unusual movement.
Roadmap handoff
Turn confirmed findings into prioritised tasks in SEO roadmaps.
Custom layouts, exports, blur mode and MCP access are covered on the capabilities hub.
Frequently asked questions
Monitor search movement like an operational system.
Connect your sources and review deployments, annotations, and visibility shifts in one operational workspace.