FIELD GUIDE · REVIEWED OCTOBER 15, 2026

Investigate low CTR and overlapping pages

Low click-through rate and multiple pages returned for one query are useful review signals. Neither alone proves that a title is wrong or that pages are harming one another.

Treat the report as a lead

A low click-through rate can reflect a mismatch between a result and search intent, but it can also reflect position, device, result features, or the query mix. Separately, Search Console can return more than one landing page for a query. That observation is sometimes called overlap or suspected cannibalization, but multiple URLs do not establish harmful competition. Search Console performance rows do not reveal the pages’ full content, canonical declarations, or what searchers intended. Use the report to decide what to inspect, not to automatically combine, redirect, or rewrite pages.

Worked overlap example

Imagine one query has two returned pages: page A has 60 clicks and 1,500 impressions; page B has 40 clicks and 1,000 impressions. Together, the returned rows show 100 clicks and 2,500 impressions. Their shares of those returned totals are 60% and 40% for clicks, and 60% and 40% for impressions. These shares describe only the rows in this report. They do not show how many unique people searched, whether the pages reached distinct audiences, or whether one page displaced the other. A report that lists only the top five pages also may omit additional returned pages while showing an omitted count.

Check intent before changing pages

Open each listed page and compare its purpose, subject, and intended audience. Then inspect the query wording and live search results for the relevant market and device. Ask whether the pages answer different needs, whether one should be the clear destination, and whether internal links and page titles make that choice understandable. Review canonical and indexing signals in the appropriate tools; they are not inferred from the overlap rows. For low CTR, compare the result title and snippet with the page and the result features present for that query. If you change a page, make one deliberate change and evaluate it over a comparable date range, while accounting for incomplete or omitted data.

Try the workflow

Explore the interactive sample first. For an approved connected account, ask your authorized MCP client:

For example.com, review low-CTR candidates and queries with multiple returned pages for August 1–14, 2026. For each overlap, show page-level clicks, impressions, and shares of the returned totals; include omitted-page counts when present. Separate measured facts from hypotheses, suggest specific intent and canonical checks, and do not label overlap as harmful cannibalization without independent evidence.

Relevant tool: detect_query_page_overlap. See product documentation and connection settings.

What the evidence cannot tell you

Returned query and page rows may be incomplete because Google can omit anonymized or low-volume data, and report row limits can constrain evidence. Shares are calculated from returned rows and do not represent unique searchers or total market reach. CTR is affected by position, device, intent, and search-result layout. Multiple returned pages and heuristic intent or URL-shape hints are not proof of conflict, cause, or a recommended redirect.

Sources and build scope

Original editorial examples, reviewed October 15, 2026. Google defines clicks, impressions and average position; its Search Analytics API reference documents grouping, inclusive Pacific Time dates, fractional CTR and bounded results.

Product behavior checked against Searchlight source 4f160c3, calculation version searchlight-insights-v2 (repository access required). This is implementation provenance, not proof of production availability or live-provider acceptance. Roadmap features are not described as shipped.

← All guides