Welcome to the week’s Pulse: Google’s explanation for lost clicks was tested; a case study showed why Core Web Vitals fixes target the wrong element; a report measured how agents handle pricing pages; John Mueller weighed in on agent access; and a longtime Bing leader announced his retirement.
Here’s what matters for you and your work.
AI Overviews Don’t Just Absorb Low-Value Clicks
Researchers shared new data from a randomized field experiment on Google’s AI Overviews. They found no measurable difference in bounce rates, return to search, or time on site between clicks that occurred with summaries and those that occurred without them.
Key facts: The study measured a 39.8% drop in organic clicks when AI Overviews appear. Losses focused on informational queries, while navigational and transactional queries showed no measurable change on smaller samples. Google VP of Search Liz Reid has said AI Overviews cut “bounce clicks,” the low-value visits users abandon quickly, but hasn’t released data to support that.
Why This Matters
If AI Overviews were mainly absorbing low-value visits, the extra clicks websites get when the summaries are removed should look worse, but they didn’t. The added clicks carried the same bounce rates, dwell time, and return-to-search behavior as the rest.
That leaves Google’s click-quality defense unsupported by the experiment’s data. A drop in clicks on AI Overview queries can’t be waved off as just losing visitors who wouldn’t have converted. We covered the original experiment in April, when it first measured the click loss. Reid has repeated the bounce-clicks explanation in several public settings, and Sundar Pichai addressed the same traffic question in May, but Google still hasn’t released the segmented click data that would settle it.
Read our full coverage: Google AI Overviews Study Finds Lost Clicks Weren’t Lower Quality
LCP Fixes Often Target The Wrong Element
Google’s John Mueller pointed to a case study explaining why so many Largest Contentful Paint (LCP) fixes fail to improve the score. In store layouts that vary by merchant, the browser can lock onto the wrong element, so every optimization after that targets something that was never the LCP.
Key facts: The case study, published on web.dev, traces a year of Core Web Vitals work. The team traced the store’s weak LCP scores to the browser locking onto the wrong on-page element, a side effect of how its templates loaded, then adjusted the pages so the browser measured the real main content. The retailer reports that a higher share of its online storefronts passed LCP afterward.
Why This Matters
The useful part here is the order of operations, more than the specific fixes. Before compressing another hero image, confirm which element the browser actually counts as the LCP, because in template-driven or carousel-heavy layouts it may not be the one you think it is.
Our own look at Core Web Vitals across CMS platforms found the same…
Source link
Disclaimer
We strive to uphold the highest ethical standards in all of our reporting and coverage. We blogs.grocliq.com want to be transparent with our readers about any potential conflicts of interest that may arise in our work. It’s possible that some of the investors we feature may have connections to other businesses, including competitors or companies we write about. However, we want to assure our readers that this will not have any impact on the integrity or impartiality of our reporting. We are committed to delivering accurate, unbiased news and information to our audience, and we will continue to uphold our ethics and principles in all of our work. Thank you for your trust and support.
Website Upgradation is going on for any glitch kindly connect at [email protected]
