Impressions Up, Clicks Down? Diagnose the Query Before You Rewrite (2026)

Before changing a page that still earns impressions but lost clicks, split the loss into four checks in Search Console: query, position, intent, and the search-result layout. That is the useful response to this week's August 5-6 volatility. It tells you whether the page needs an SEO edit at all.

What changed this week

Search Engine Roundtable reported a sharp increase in SEO chatter on August 5 and 6. Practitioners described large swings and reversals, including cases where keyword rankings improved while traffic fell by 14%, and cases where clicks dropped even though reported rankings barely moved. The report calls the event a possible update, but Google had not confirmed one. 1

Google's Search Status Dashboard still lists the June 2026 spam update as its latest ranking incident in the ranking history; it does not list an August ranking incident in the page retrieved for this issue. Treat the August reports as observed volatility, not as proof that Google targeted a specific page type. 2

The most useful fresh discussion in r/SEO was narrower than the update theories: how to handle a page with many impressions but almost no clicks. Several replies converged on the same order: inspect the individual query, then its position, search intent, and the result-page layout before touching the title, snippet, or content. 3

The one action: diagnose one URL at query level

Use this on one page whose clicks or CTR fell while impressions continued. It is especially useful when the page sits in the positions 8-20 range, appears for a wider set of queries than you intended, or competes with AI features, videos, shopping results, or other prominent blocks.

Open Search Console > Performance > Search results. Set the date range to two equal, complete periods: one before the drop and one after it. Select Web as the search type, enable Clicks, Impressions, CTR, and Average position, then use the Pages dimension to filter to the affected URL. Search Console provides these metrics and dimensions, but its newest data can be preliminary, so do not treat an incomplete current day as the final comparison. 4
Switch to the Queries tab while keeping the page filter. Start with the five queries that have the most impressions in the affected period. For each one, write down the clicks, CTR, and average position for both periods. Do not use the page's overall CTR as the diagnosis: one URL can collect impressions from very different queries.
For each query, label the result with one of these three findings:
- The position fell: this is a ranking problem first. A title rewrite will not explain why the page moved down, so leave the title alone until you know what changed in the result set.
- The position is stable and the query fits: search the query on the same device and in the same general location as your audience. Look for the page's actual title and snippet beside ads, AI Overviews or AI Mode, video, image, shopping, or other result blocks. This is a presentation problem only if the page still ranks for the right query but is being outcompeted for attention.
- The position is stable but the query does not fit: the page is earning irrelevant impressions. Changing its title to attract more of those searches would increase the mismatch. Fix the page's targeting or content only when several high-impression queries show the same intent gap.
Keep a copy of the query rows and your labels. Make at most one change after the classification: either a page-level ranking diagnosis, a result-presentation edit, or a content-intent fix. Record the date of that change next to the Search Console export.

Search Console's average position is not a fixed rank for one keyword. It averages the topmost position of your property or page across the searches that generated impressions, and the value can differ from what you see in one manual search because of location, device, history, and timing. Use it to classify the pattern, not to claim that the URL is always in position 6 or 12. 5

The August-specific trap: new AI queries

Do not automatically treat strange conversational queries as evidence that your old keyword lost relevance. Google says a follow-up question inside AI Mode is counted as a new query in the general Search Console Performance data, with its own impressions, position, and clicks. The generative AI report does not provide query data, so the main Performance report is where these rows can appear. 6

Search Engine Roundtable reported the same practitioner observation on August 6, including follow-up-style rows such as "yes" and "yes, pricing." These rows are clues, not a clean Google-provided AI Mode filter. Use them to explain an odd query mix, then compare the ordinary queries that actually match your page. 7

What your result tells you

Clicks fell, impressions fell, and position fell for the same query group: stop treating this as a CTR problem. Keep the query export and investigate the ranking change separately; do not start by rewriting the snippet.
Impressions stayed similar, position stayed similar, but CTR fell for matching queries: inspect the live result layout and then change one title or visible heading if it clearly misstates the page. Google generates title links automatically from several sources, including the <title>, visible titles, headings, og:title, page text, and anchor text, so a new <title> is not guaranteed to be the text users see. 8
Impressions grew mainly from weakly related or AI follow-up queries: do not broaden the page to chase the extra impressions. Tighten the page around the intent it can genuinely satisfy, and keep the query export as the before-state.

The verification is complete when every high-impression query for that URL has one label and one recorded next step. If the labels disagree, do not force a page-wide rewrite. The August signal is still unconfirmed, and a mixed query pattern is evidence that the page needs a narrower diagnosis, not a guessed algorithm fix.