June 2026 brought two relevant changes for website management: better visibility into traffic from AI experiences and an additional safeguard for WordPress extension releases.
Search Console begins reporting AI-experience performance
On 3 June, Google announced dedicated reporting for a subset of its generative experiences. Rollout is gradual, so properties may not receive the same data immediately. Reports can cover clicks and impressions, pages, countries, devices and dates. Read the official Google Search Central announcement.
A business should not read these numbers in isolation. An impression is not a conversion and a click does not explain intent. Connect the report with GA4, forms, phone and WhatsApp, then review the pages contributing to real enquiries.
- watch 28- and 90-day trends;
- compare informational and commercial pages;
- document content changes before interpreting results;
- keep consistent lead and conversion definitions.
WordPress adds a release safety window
On 5 June, WordPress introduced “Protect The Shire”, including a 24-hour window for certain plugin and theme releases. It aims to reduce the risk of a compromised maintainer account immediately publishing malicious code. Read the official WordPress explanation.
Platform protection helps but does not replace local maintenance. Sites still need individual accounts, strong authentication, least privilege, off-server backups and tested updates.
Practical actions
- Check whether the new report is available and document its start date.
- Configure meaningful GA4 events without unnecessary personal data.
- Audit administrators and remove unused accounts.
- Test backup restoration.
- Update in staging and verify commercial flows.
The common direction is observability and control. A healthy site does not depend on one report or one safeguard, but on a system where data, security and decisions can be verified.