Your SEO dashboard can look worse even when your site has not lost meaningful Google visibility. If total ranking keywords or SERP features suddenly collapse while clicks and leads remain steady, do not declare a ranking loss until you determine whether the site changed or the measurement system did.
Google has changed how third-party tools can collect search results, altered an important result-depth parameter, and added first-party reporting for multimodal searches. The practical challenge is no longer choosing one perfect metric. It is knowing which question each metric can still answer.
Three breakpoints changed the meaning of your trend lines
A rank tracker can lose the ability to observe a result without your page losing its position. That distinction became more important after three Google changes:
- In January 2025, Google required JavaScript for Search and caused a data blackout for several SEO platforms. Some providers were affected while others continued collecting results, so discrepancies between tools became more likely.
- In September 2025, Google stopped supporting the num=100 parameter, which had allowed 100 results to be returned on one page. As many as 77% of sites lost some reported keyword visibility after the change, and several volatility sensors and rank trackers were disrupted.
- In August 2026, Google confirmed the rollout of google.com/goto passthrough links. For affected results, a tool may need to resolve a Google-owned intermediary URL before it can identify the destination page.
Each change makes large-scale collection more difficult or expensive. Losing num=100 means a provider can no longer request the first 100 results in one operation. Resolving passthrough links adds work for each affected result. A provider may respond by collecting fewer positions, sampling more aggressively, refreshing less frequently, or charging more for equivalent coverage.
The distortion is most likely to appear deep in the results because positions below the first page are expensive to collect and usually less valuable to customers. This turns a platform’s total keyword count into two measurements at once: your site’s search footprint and the platform’s ability to observe that footprint. Treating it as a pure performance metric is now a category error.
Recognize the signature of a collection failure

A genuine visibility loss and a collection failure can both produce a falling graph. The distribution of the decline tells you which explanation is more plausible.
For Reddit, Semrush data from May to June 2026 showed more than 60 million fewer ranking keywords and more than 13 million fewer SERP features. Those represented month-over-month declines of 25% and 21%, respectively, while estimated traffic remained steady. The loss also became progressively larger at deeper positions:
| Position band | Change from May to June 2026 | What the pattern indicates |
|---|---|---|
| Position 1 | +16% | The most visible rankings remained observable |
| Top 3 | +11% | High-value coverage did not collapse |
| Positions 4-10 | -8% | Loss began within the remaining first-page results |
| Positions 11-20 | -28% | Missing coverage accelerated beyond page one |
| Positions 21-50 | -34% | Deep-result visibility deteriorated sharply |
| Positions 51+ | -35% | The deepest rankings were the least observable |
This is not a universal benchmark. It is a diagnostic pattern. A real sitewide ranking collapse of that scale would not normally erase progressively more deep positions while expanding Position 1 and Top 3 counts and leaving estimated traffic unchanged. A depth-weighted decline points more strongly to reduced collection coverage.
It can also make the surviving data look deceptively healthy. If a tool stops observing positions 40 through 80 but retains positions 1 through 10, the reported keyword total falls while the average position may improve. That apparent improvement is survivor bias, not necessarily better SEO.
Use this sequence whenever a visibility graph breaks:
- Start with business outcomes. Check whether organic leads, sales, sign-ups, or other meaningful actions declined during the same period. Stable outcomes do not prove that rankings were stable, but they reduce the likelihood of a commercially significant collapse.
- Check Google Search Console clicks and landing pages. If third-party keyword totals plunge while clicks and the pages receiving those clicks remain broadly stable, investigate collection coverage before changing content.
- Split rankings into Position 1, Top 3, positions 4-10, 11-20, 21-50, and 51+. A drop concentrated in the deepest bands is more consistent with an observation problem than an across-the-board ranking loss.
- Compare branded and non-branded priority queries separately from the provider’s entire discovered keyword universe. A controlled set of commercially important queries is more useful for tactical decisions than a volatile inventory of every term the tool happened to find.
- Look for provider-specific discontinuities. If one platform changes abruptly while first-party clicks, outcomes, and another independent ranking view do not, label the event as a probable measurement break.
- Allow for mixed diagnoses. A collection change and a real traffic decline can happen together. If clicks, conversions, important landing pages, and high-ranking priority queries all deteriorate, continue the SEO investigation even if deep-result coverage also changed.
Rebuild reporting around questions, not one visibility score
No single visibility number can now support every decision. Give each reporting layer a defined job and state its limitation beside it.
| Reporting layer | Use it to answer | Main limitation |
|---|---|---|
| Business outcomes | Is organic search contributing qualified leads, sales, or other valuable actions? | Demand, attribution, and conversion behavior can change independently of rankings |
| Google Search Console clicks and pages | Did Google Search send traffic, and which landing pages received it? | Reporting definitions and automated search activity can affect historical comparability |
| Priority rank set | Did a controlled set of branded, commercial, and strategically important queries move? | Results vary by location, device, and the provider’s collection method |
| Total keywords and SERP features | Where might new topics, competitors, or result features be emerging? | These inventory metrics are highly exposed to collection-depth changes |
| Multimodal performance | Are visual search experiences discovering the site’s content? | It is a distinct search surface and does not replace conventional ranking or generative AI query data |
Your report also needs a measurement change log. Record the date, affected tool, affected metric, likely mechanism, position bands involved, and whether the provider changed its collection method. Put the annotation on the chart itself. A note hidden in a separate methodology document will not stop someone from treating the break as a performance event.
Keep the original series, but do not draw an unqualified continuous trend across an incompatible baseline. Compare periods collected under the same method where possible. If that is not possible, present pre-change and post-change periods as separate regimes and label the comparison as measurement-affected. Do not invent a correction factor unless you have enough overlapping data to defend it.
September 2026 year-over-year reports require particular care. Search Console impressions fell after num=100 disappeared in September 2025 because automated requests had previously generated impressions for deep results. That creates a suppressed comparison baseline, so double-digit year-over-year impression growth can appear without an equivalent improvement in actual performance.
Do not present that percentage alone. Put absolute clicks, business outcomes, priority-query movements, and landing-page performance beside it. If only impressions rebound against the lower baseline, describe the result as affected by measurement history rather than evidence of equivalent SEO growth.
Measure multimodal discovery as a separate search surface

While third-party result coverage is becoming less complete, Search Console is adding a first-party view of visual discovery. Its multimodal search filter covers Google Lens, Circle to Search on Android, image uploads to Google Search, and Chrome’s Search this image action. The data is rolling out globally and appears when a site receives traffic from those experiences.
Multimodal visibility should not be folded silently into a general visibility score. A person searching with an image is expressing intent differently from someone typing a conventional query, and the optimization work is often different. Track the surface separately so you can see whether visual discovery is growing, which pages participate, and whether that exposure leads to useful behavior.
- Record when multimodal data first becomes available for your property. Do not interpret the first visible reporting period as the date your site first appeared in visual search.
- Review the landing pages associated with multimodal activity. Check that their images are useful to the page’s purpose, accessible to crawlers, supported by clear nearby text, and described with accurate text alternatives.
- Keep structured data faithful to the visible page. Schema can clarify products, organizations, articles, and other entities, but it should not describe an image, offer, or claim that users cannot find on the page.
- Connect multimodal reporting to page-level outcomes. More visual discovery is interesting; it becomes valuable when the discovered pages attract relevant engagement or conversions.
- Do not manufacture query-level precision where Google does not supply it. The generative AI search performance report still lacks click and query data, so a generative visibility narrative should acknowledge that blind spot.
The new filter is an additional lens, not compensation for missing third-party keyword coverage. It answers a new question: whether people are finding your content through visual and multimodal behavior. It does not tell you that a disappearing position-50 keyword remained stable, and it does not provide the prompt-level attribution many teams want from generative search.
Key takeaways for your next SEO report
- A falling third-party keyword count is not, by itself, evidence of lost Google traffic.
- A decline concentrated below positions 10 or 20 is more suspicious as a collection problem than a uniform loss across top rankings.
- Clicks, landing pages, and business outcomes should determine the severity of the response; discovered keyword totals should support exploration, not act as the verdict.
- January 2025, September 2025, and August 2026 belong in your reporting change log because each altered how search visibility could be observed.
- September 2026 year-over-year impression growth may be inflated by the lower post-num=100 baseline from September 2025.
- Multimodal reporting deserves its own baseline, goals, and page-level analysis. Do not merge it into conventional web or generative AI visibility without a label.
Before your next report goes out, annotate the three collection breakpoints, split ranking data by depth, and place first-party clicks and business outcomes ahead of total keyword counts. Then establish a separate baseline for multimodal discovery. That small reporting redesign can keep a measurement change from triggering the wrong content rewrite, budget decision, or performance diagnosis.
References
- Search Engine Land – Google’s /goto change: The latest challenge for third-party SEO data
- Search Engine Land – Google Search Console performance reports gets multimodal filter


Leave a Reply