Composway
/MCP Documentation
SupportOpen app
MCP Documentation

Investigate a traffic drop

Use this guide to find queries that lost clicks and examine the evidence for each loss. The assistant returns possible explanations, confidence limits, and the next investigation for each query.

When to use this use case

Use this use case when clicks fell and you need to decide what to check before changing pages. Search-console data does not always identify a cause.

What to ask

Replace the domain and end date before using this prompt.

Investigate the recent drop in clicks for example.com using data available through September 30, 2026. Confirm the change with a site snapshot and weekly trend. Diagnose the largest query losses over eight complete weeks. Separate ranking changes, changes in the ranking page, CTR losses, and impression losses where the data supports that distinction. Keep inconclusive findings inconclusive. Show the evidence and next investigation for each query. Do not run paid SERP checks.

How the assistant runs it

The assistant confirms the loss before examining individual queries:

  1. Call get_server_status, list_sites, and get_connection_status to confirm the site and coverage.
  2. Call get_site_snapshot to compare recent performance with the preceding period.
  3. Call get_performance_trend to locate the change. Separate a lasting decline from a partial reporting period.
  4. Call diagnose_traffic_losses with a small query limit and a defined series length. Read the returned period boundaries, confidence, and unsupportedInputs.
  5. Call get_query_pages for selected queries. Use detect_keyword_cannibalization if the result suggests competing pages or a change in the ranking page.
  6. Recommend the next investigation. Do not prescribe a page change when the evidence does not support it.

Example tool input

This input requests five query diagnoses across eight complete weeks.

json
{  "tool": "diagnose_traffic_losses",  "arguments": {    "site": "example.com",    "to": "2026-09-30",    "granularity": "weekly",    "periods": 8,    "limit": 5,    "minImpressions": 100,    "excludeBranded": true,    "checkPageSwap": true,    "searchVertical": "web"  }}

What the result includes

The assistant returns the following information for each selected query:

  • The engine, observed loss, and period when performance changed.
  • Changes in clicks, impressions, CTR, and position.
  • The tool's diagnosis and confidence, including inconclusive results.
  • The ranking page and any evidence of a page change.
  • A next investigation tied to the evidence.

How to read the result

Treat a ranking loss, a CTR loss, and a fall in impressions as different findings. A page change is a reason to inspect the pages, not an automatic instruction to consolidate them.

The tool cannot see search-result features from search-console data. It cannot prove that an AI Overview caused the loss. A demand classification applies to the measured query wording, not necessarily the whole topic.

Eight weeks do not establish annual seasonality. The seasonal test needs a longer monthly series. Report seasonality as untested if the returned data does not support the test.

Reduce the period count or query limit if the call times out. Turning off the page-swap check reduces work but leaves that explanation unchecked. Read truncation warnings before treating missing query rows as zero.

On This Page