On this page
Rule out a reporting mismatch
Compare complete periods with the same search type and filters. Check data freshness and whether both engines returned the requested dates. For a seasonal site, also compare with the previous year where the source has that history.
Compare periods and filter search performanceRead the pattern, page by page
Sort pages by lost clicks, then inspect their queries. Keep Google and Bing separate: Google web search and Bing’s reported surfaces have different scopes.
| Pattern | Next check |
|---|---|
| Impressions fall, position is similar | Check demand, seasonality and changes in the query mix. |
| Impressions are similar, CTR falls | Review titles, snippets, intent and the current search results. |
| Position worsens across affected queries | Review affected pages, site changes and Google’s Search status information. |
| A page disappears from the report | Inspect the URL and check redirects, canonicals and crawl access. |
Validate the explanation before changing the site
Compare affected pages with pages that stayed stable. Check your release history, technical changes and source reporting issues. An algorithm update near the same date is a lead to investigate, not proof. Review the live SERP before rewriting a page that still performs well.
Try it with your own site
Replace example.com with a site you can access. Connect your data and assistant first.
Investigate the click decline for example.com over the last complete 28 days versus the previous 28 days. Check date coverage and source scope first. For each engine, rank pages by absolute click loss, then inspect their query, impression, CTR and available position changes. Separate facts from possible causes. Recommend the next three checks and explain what evidence would confirm each hypothesis.Keep in mind
Search Console does not return every query, and Bing query and page records are weekly and non-exhaustive. Average position can change with the query mix. Empty or incomplete data is not proof of lost traffic.