Guides
Console surfaces: one page, four questions
Search, Traffic, Audit and Monitoring as four jobs on one page, with the page dossier, opportunities and the fix-verification loop.
Guide · console surfaces
The console is one site, one shell, four surfaces — not four tools that happen to share a login. Search, Traffic, Audit and Monitoring answer different questions about the same URLs, so a page you spot in one surface can be opened, diagnosed and re-checked in the next without re-entering the site. The site selector at the top sets the scope for all of them.
Search, Traffic, Audit, Monitoring
- Search — What Google sends, which queries sit just out of reach, and which terms you track. Performance, Opportunities and Keywords read Search Console through the same property binding. Console → Search → Performance / Opportunities / Keywords
- Traffic — What happens after the click: sessions, engaged sessions, conversions and AI referrals. GA4 supplies the numbers when it is bound; the page beacon fills the block when GA4 has no rows. Console → Search → Traffic
- Audit — What is wrong on the page: rule-level findings with severity and fixes, internal-link structure, index status and run history. Console → Audit → Fixes / Structure / Index status / History
- Monitoring — What changed since the last look: domain and uptime, key-page checks, daily Web Vitals and the change feed. Console → Monitoring → Domain / Key pages / Web Vitals
Overview is the cockpit above them: setup state, top findings, what changed, and the way into each surface. It does not hold a fifth data model — it links into the four and reuses their numbers.
The page dossier
Open any page from a search row, a traffic row or an audit finding and the dossier keeps one URL in view with every source beside it: Search clicks, impressions, CTR, average position and top queries; Traffic sessions, engaged sessions, conversions and average time; Crawler fetches, 404s, blocked paths and last seen; AI referral sessions; Index verdict, coverage state, last crawl and canonical drift; audit findings; and LCP, INP and CLS at p75 with the sample count.
Each block names its source and window. A block with no data reads na with a reason — no-source, no-probe, gsc-unbound, no-data or not-indexed-yet — never 0. Zero is a measurement; na means the source was not connected or had no row for that page. The dossier also repeats the GA4 note when visitor numbers come from the shorter snapshot.
Use it when a number in the page row surprises you. Search Console setup is covered in the Search Console guide; the crawler and AI blocks need the first-party telemetry probe, and stay na without it.
Page opportunities
Opportunities is a per-page row, not a per-query grid. One row per URL joins Search clicks and average position, sessions, engaged sessions, conversions, AI fetches, AI visits, LCP and open findings. The join key is the page: a URL with twenty queries still has one session count, because sessions are never split per query.
Windows differ by source and the header says which are in play. Search Console numbers follow the selected window with their 1–3 day lag. GA4 sessions and engagement come from a 7-day snapshot of the top 20 organic landing pages, so they stay 7-day even when the report is set to 28 or 30 days; conversions always use GA4's last 7 days. The page beacon covers the whole selected window. A page outside GA4's top 20 reads na, not zero.
Filters from other search tabs do not apply here — opportunities are calculated site-wide. Treat the row as a triage list: pick the page, open the dossier, decide what to change.
Fix, re-audit, verify
- Fix. Every finding carries the rule, severity and fix. Nothing is applied for you; the console points at the change, you ship it.
- Re-audit. A single-page re-check runs the current rules without spending an audit run, and closes the finding as fix-applied when it passes. The next full run compares added, fixed and regressed issues.
- Effect-verify. Title, meta, H1 and JSON-LD changes are fingerprinted. After a 14-day window plus about 3 days of Search Console settling, clicks and CTR are compared with the prior 28 days, netted against up to five same-site control pages.
Body-only changes are recorded but not effect-verified. Without a control page the result is directional and labelled as such. Verification can also end as pending, insufficient (the baseline or verification window had fewer than 100 impressions), blocked or dropped instead of a verdict — a no-conclusion is a result, not a failure. The full loop is described on the page decisions page.
The SEO reporting dashboard guide turns this loop into one report; how to verify an SEO fix walks the re-audit and effect check after the change ships.
Limits and non-goals
- Search Console reports with a 1–3 day lag; average position is averaged across the queries and dates you selected, not a daily rank.
- GA4 page detail is a 7-day top-20 snapshot and conversions are always last 7 days; pages outside the top 20 read na.
- The crawler block needs the server probe. Without it the block is na, not zero; fetches prove access, not a visit.
- No AI advice: findings carry the rule and the fix, but the console does not write copy or choose the strategy for you.
- No rank grid: there is no stored daily position per keyword. Tracked-term SERP checks are on-demand snapshots, not history.
- No estimated traffic and no third-party rank database: every number is observed or read from a connected source.
Open the console to use these surfaces; tracked terms have their own guide. Plans are on pricing; the traffic side has its own GA4 guide.
Was this page helpful?