Compare performance across site sections

Use this guide to compare search performance across URL directories. The assistant returns section changes and a page-level shortlist for investigation.

When to use this use case

Use this guide to review sections such as a blog, product directory, or tools directory. The tool groups pages by their leading URL path segments, not by content type or saved custom segments.

What to ask

Replace the domain, dates, and sections before using this prompt.

Compare example.com's main URL directories during the 28 days ending September 30, 2026 with the previous 28 days. Show clicks and impressions by Google and Bing. Focus on /blog/ and /tools/, and identify pages worth investigating within each. Explain the grouping and data coverage. Do not treat directory totals as complete shares of property traffic or compare sections by an unweighted average of page CTRs.

How the assistant runs it

The assistant reviews directory changes before drilling into pages:

Call get_server_status, list_sites, and get_connection_status to confirm the site and engines.
Call analyze_site_sections with the required directory depth. One path segment groups pages under sections such as /blog.
Read the current window and changes from the previous equal-length window. Check engine coverage before reporting section results.
Call get_advanced_search_analytics for pages within a selected section. Group by page and searchEngine and filter the page text.
Repeat the page query for the comparison window if you need engine-specific changes or page movers. The directory response does not include a full per-engine comparison table.
Use a site snapshot for property context. Explain that section totals cover the rows available to the tool.

Example tool inputs

These inputs read first-level directories and list pages in the blog section.

json

{  "tool": "analyze_site_sections",  "arguments": {    "site": "example.com",    "to": "2026-09-30",    "windowDays": 28,    "sectionDepth": 1,    "limit": 50,    "searchVertical": "web"  }}

json

{  "tool": "get_advanced_search_analytics",  "arguments": {    "site": "example.com",    "to": "2026-09-30",    "windowDays": 28,    "dimensions": ["page", "searchEngine"],    "filters": [      {"field": "page", "operator": "contains", "value": "/blog/"}    ],    "limit": 50  }}

What the result includes

The section review contains the following information:

Directory grouping, dates, and returned page counts.
Clicks and impressions by engine for the current period.
Section changes and selected page changes for the comparison period.
Pages to investigate and the reasons for selecting them.
Source limits and any truncated results.

How to read the result

Page-row limits can reduce section totals. Do not present them as a complete allocation of property traffic. Recalculate CTR from compatible click and impression totals instead of averaging page CTRs.

The advanced tool supports text filters, not wildcard or regular-expression matching. It combines filters with AND and does not support nested OR conditions. Use separate calls for separate groups.

A path filter such as /blog/ does not include a canonical section root ending in /blog. Add a separate root lookup if it belongs in the group. Also check subdomains because a blog on a separate hostname is not necessarily a /blog/ directory.