Start with what changed in your own Search Console data. A fall in clicks is an observation, not a diagnosis. This workflow ends with a supported explanation to investigate, the affected pages and a reviewed next action.
Before you start
- A connected Search Console property and permission to read it. Confirm the selected site and its latest available data.
- Comparable periods with complete days. For seasonal businesses, consider whether the comparison covers a similar season within the available history.
- The relevant publication notes and confirmed Business Brain context. GA4 is optional and remains a separate source.
- 1
Set the comparison
Open Performance. Select the site, dates, country and device. Check the data-through date and use the same filters in both periods. Incomplete recent days must not be compared as completed results.
- 2
Locate the pages that explain the loss
Review the pages with the largest absolute click decline. A large percentage on a very small page can distract from a smaller percentage on an important page. Keep the full page identity, including its host, with the comparison.
- 3
Read the queries and metrics together
Open a relevant page or query view. Compare clicks, impressions, CTR and average position, including brand and non-brand context where available. Confirm the period again if the destination changes it.
- 4
Check competing explanations
Compare the pattern with release annotations, seasonal demand and the page's purpose. When a technical issue is plausible, inspect the existing audit evidence and its timestamp. A fresh paid check needs its own deliberate action and cost review.
- 5
Ask a precise question
Ask Solvuri AI about the selected page, dates and observed loss. Read the supporting sources and check the answer against confirmed Business Brain facts. An explanation without relevant evidence remains a hypothesis.
- 6
Record the decision
Create or update a task only after reviewing the finding. Include the URL, query, source period, evidence, proposed check and why it fits the business. If the evidence is incomplete, record the follow-up needed instead of prescribing a rewrite or deletion.
Interpret the pattern without assuming its cause
| Observation | Next check |
|---|---|
| Clicks and CTR fall while average position is similar | Inspect query mix, intent and current search-result context. This alone does not prove an AI Overview caused the loss. |
| Impressions fall for a destination or seasonal page | Check comparable periods, markets and available query coverage before rewriting the page. |
| An important page loses clicks and average position | Review content changes, competing pages and dated technical evidence; several causes can coexist. |
| A report is empty or still syncing | Check connection, scope and freshness. Missing data is not observed zero traffic. |
Short practical walkthrough
- 1
Open the Performance demo. The Northwind workspace is fictional.
- 2
Read its selected period and brand/non-brand context, then inspect a page or query with a decline.
- 3
Write down the observation, one possible explanation and the evidence you would need to distinguish it. Do not treat the example as your site's result.
- 1
Confirm the property and complete comparison periods.
- 2
Select one affected page and keep its source evidence with the investigation.
- 3
Decide between a reviewed fix, a technical check or waiting for sufficient data. Record the reason and next review.
Continue with the same question.
Keep the same site, period and filters when you apply the workflow to your own data. The public examples use fictional data.