> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hypergsc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Find out why your Google search traffic changed

> Use HyperGSC to compare Search Console performance, find pages and queries behind a traffic change, and prioritize your next SEO actions.

Start with what changed, then investigate where it happened. HyperGSC can help you compare Search Console periods and turn the largest observed movements into an SEO action list.

Advanced comparisons require Starter or higher. On Free, begin with a basic top-query report and describe the available reporting range.

## Ask your AI assistant

```text theme={null}
Use HyperGSC to review my Google search performance.
Ask which property to use if more than one is enabled.
Compare the last complete seven-day period ending at least three
days ago in Pacific time with the preceding seven days.

Show clicks, impressions, CTR, and average position.
Identify the pages and queries with the largest observed click changes.
Include dates, coverage warnings, and three prioritized follow-up actions.
Separate observed changes from possible explanations.
```

## What to look for

**Clicks and impressions both fell.** Investigate demand, ranking changes, the affected pages, and possible indexing problems. A traffic decline alone does not establish its cause.

**Impressions stayed similar but clicks fell.** Check CTR, query mix, devices, and average position. A different mix of searches can change overall CTR even when individual pages are stable.

**A few pages account for most of the change.** Review those pages and their queries before changing the whole site. Compare related pages to see whether traffic shifted within the property.

## How HyperGSC builds the review

The assistant starts with `get_capabilities` and the exact enabled property. It can use `get_performance_overview` for totals and trends, `compare_search_periods` for equal-length comparisons, and query or page reports for detail.

Ask it to preserve the same search type and filters across periods. Missing rows should stay unknown rather than become zero.

## Turn the review into a decision

Request a short table with the affected URL, observed change, supporting queries, confidence, and next action. Useful actions include checking indexing, reviewing a changed page, or investigating low CTR.

Keep seasonal demand, competitors, and concurrent site edits in the explanation when evidence supports them. The result is a set of testable explanations, not proof that a particular edit or algorithm update caused the change.

Continue with [CTR opportunities](https://docs.hypergsc.com/workflows/improve-ctr.md), [indexing checks](https://docs.hypergsc.com/workflows/check-indexing.md), or [measuring an applied change](https://docs.hypergsc.com/workflows/measure-seo-changes.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.