Search digestJune 2026

June added first-party views for AI-search visibility while clarifying several controls that are often overinterpreted. The useful discipline is to keep Google, Bing and Yandex measurements separate, label previews as previews, and avoid turning a file or report into a ranking promise.

Product change

Search Console introduced generative-AI performance reports

On June 3 Google announced dedicated Search Console views for impressions in generative AI features across Search and Discover, including AI Overviews and AI Mode. Google said the data remains included in the overall performance report and that the dedicated reports initially rolled out to a subset of websites. This is a reporting surface, not a separate traffic channel: compare it with the standard report carefully and record availability before drawing a trend.

Action

Google clarified llms.txt and domain-variant migration guidance

Google’s June documentation update clarified that llms.txt is not needed for Google Search and has no positive or negative effect on visibility or rankings, while allowing that other systems may use it. On June 17, Google added Change of Address guidance for all subdomain variants, including www and non-www, during a domain move. The practical distinction is clear: do not create llms.txt for Google ranking; do map every public host variant before a migration.

zoom_in

Product change

Bing expanded AI Performance reporting in preview

On June 16 Bing Webmaster Tools announced preview capabilities for AI Performance: Intents, Topics, Citation Share and Compare. Bing described Citation Share as the percentage of citations attributed to a site among citations for the same grounding query, and explicitly called it observational rather than a ranking system, traffic share or quality score. The report can guide inspection of cited pages and themes, but its preview labels and changing AI classifications must remain part of the interpretation.

Product change

Yandex Webmaster added hourly query-monitoring data

On June 25 Yandex Webmaster said Query Monitoring could show fresh data for the previous day with hourly detail, replacing the earlier two-day update pattern for that view. Yandex also warned that operational hourly values can change as processing completes and recommended the two-week report for final analysis of an individual query. This is a regional measurement update: use it for anomaly triage, not as settled reporting or proof that a technical change caused a result.

Action

What to check on your own site

• Open the dedicated Google generative-AI reports only where available, and retain the standard performance view for scope comparison.
• Keep AI citation counts, Google impressions and sessions as separate measures with their own dates and definitions.
• Do not add llms.txt for Google Search rankings; document any other system that has a separate use for it.
• Before a domain move, list every host and subdomain variant and verify redirect, canonical, sitemap and Change of Address choices.
• Use Yandex hourly data to investigate anomalies, then confirm an individual-query conclusion with the completed reporting window.