Operations · document 30

Search Intelligence

In the workspace: /search-intelligence/

Availability

Open on every plan, and it needs a Search Console property matched to the project. Connecting Google is part of the plans that include Search and Cloud integrations.

This document is open to every reader on every plan. Availability tells you what a plan includes; it does not decide what you may read.

What it is for

Finds the searches you can grow from what already ranks, using your real Search Console data rather than anything inferred from a single-page audit. It points at visible results with weak click-through and at queries sitting just below page one, which are usually the cheapest gains a site has.

How to use it

Connect Google and match the Search Console property for the project first; the masthead says "Not connected" until you do.
Open Search intelligence and choose the "Website project".
Choose the "Start date", the "End date" and the "Dimension": queries, pages, countries or devices.
Press "Load evidence" and work through the two opportunity queues before writing anything new.

Reading the result

The status reads Loaded, Ready or Not connected. The KPI row shows clicks, impressions, click-through rate and average position. "Low CTR on visible results" lists items in the top ten that are seen but rarely clicked; "Page-one quick wins" lists items ranking from 4 to 20 with enough impressions to justify the work.

What it cannot tell you

It reads one date window from Search Console, capped to a bounded result set. Cannibalisation, topic clusters and refresh priorities need a project-wide history and are deliberately not offered here. Search Console reports what Google measured, rounded and delayed, not every search.

What it keeps

Nothing. The values are read on demand for the window you choose and discarded after the page is rendered; they are not stored by the platform.