Google Launches Core Update Amid I/O AI Search Overhaul – SEO Pulse: the Strategic Visibility Angle

There are weeks in SEO where we deal with a single variable—a new algorithm tweak or a change in a documentation page. Then there are weeks like this one. When a core update rolls out at the exact same time as a major product keynote like Google I/O, the noise level becomes deafening. It is difficult to tell where the ranking shifts end and the interface changes begin.

This isn't just a matter of tracking a few keywords in a spreadsheet. We are seeing a simultaneous shift in how Google ranks content, how users interact with the search box, and how AI agents are being positioned to navigate the web. For anyone managing a digital presence, the challenge now is separating the signal from the noise to decide where to actually allocate resources.

The Arrival of the May 2026 Core Update

On May 21, Google officially began the rollout of the May core update, as confirmed via the Google Search Status Dashboard. To put this in perspective, this is the second core update of 2026 and the fourth time this year that Google has implemented a confirmed ranking update. The rollout is expected to take up to two weeks to fully propagate across the index.

Notably, Google has remained quiet on the specifics. There is no companion blog post detailing the goals of this update or the specific quality signals being prioritized. We are essentially flying blind on the "why," relying instead on the "what" as the data trickles in.

Why This Timing is Problematic

The overlap between a core update and I/O week creates a significant attribution problem. If you see a dip or a spike in your Search Console data over the next fortnight, it is nearly impossible to isolate whether that change is due to the core update's ranking shifts or the new AI-driven interface changes announced at I/O.

The tradeoff here is between speed and accuracy. Many will be tempted to make immediate "fixes" to their content to stop a slide in rankings. However, reacting to volatile data during a dual-event window is a recipe for over-correction.

The Decision: Your baseline should be the performance data from the weeks immediately preceding May 21. Compare this against your performance only after the rollout is officially complete. I recommend waiting at least one full week after the update finishes before making any strategic pivots based on the data.

Industry Perspectives on the Update

The community is already attempting to connect the dots. Marie Haynes, founder of Marie Haynes Consulting Inc., noted that the timing aligns with the integration of Gemini 3.5 Flash into Search's AI features, suggesting the update may be preparing the index for these new capabilities.

Other experts are more skeptical of recent optimization trends. Harpreet Singh Chatha, an SEO and AI Search Consultant, suggested that this update might be a correction for sites that have spent too much effort "gaming" AI citations. If you've used aggressive or unnatural tactics specifically to appear in AI-generated answers, this update may be the reckoning.

The Redesign of the Search Experience and AI Agents

At I/O, Google unveiled what they describe as the most significant upgrade to the Search box in over 25 years. This isn't just a visual refresh; it is a functional overhaul. The Search box now expands dynamically and supports multimodal inputs, meaning users can upload images and files directly into the query process. Furthermore, the system now provides AI-powered suggestions that go far beyond traditional autocomplete.

Beyond the box, Google introduced Gemini 3.5 Flash as the default model for AI Mode and previewed "information agents" slated for release this summer. These agents are designed to proactively monitor the web and deliver updates to the user. This is paired with new capabilities like agentic booking, generative UI, and the expansion of Personal Intelligence to nearly 200 countries.

The Shift from Retrieval to Synthesis

The redesign encourages users to move away from fragmented keywords and toward longer, conversational queries. When a user describes a complex need in a natural sentence, and Gemini 3.5 Flash processes it, the result is often a synthesized AI response rather than a list of blue links.

The introduction of information agents adds another layer of complexity. If an agent is continuously searching and synthesizing updates on a topic, the traditional "click-through" model is further eroded. The risk is that your content becomes the "fuel" for the AI's answer without the user ever needing to visit your site.

The Decision: You must inspect your current content to see if it is "synthesizable." If your value proposition is locked behind a click-heavy journey, you are at risk. The goal is no longer just to rank, but to be the authoritative source that the agent chooses to cite in its synthesis.

The "Visibility vs. Clicks" Debate

Jake Ward, an SEO and content entrepreneur, points out that while many are claiming "SEO is dead," the reality is that the nature of the reward has changed. He notes that click-through rates (CTR) have been declining for several years. We are moving into an era where visibility is the primary metric, rather than the click.

This is a hard pill to swallow for those who rely on traditional traffic metrics, but it is the logical conclusion of an AI-first interface. The value is shifting toward brand presence within the AI's response—being the "recommended" entity even if the user doesn't leave the search page.

Analyzing the First Year of AI Mode Usage

For the first time, Google has released internal data on how users are actually utilizing AI Mode in the U.S. The numbers are staggering: AI Mode has surpassed 1 billion monthly users, with query volume doubling every quarter.

More importantly, the behavior is fundamentally different from traditional search. Queries in AI Mode are three times longer than standard searches. Follow-up queries are increasing by 40% monthly, and over 16% of searches are multimodal (voice, image, or video). Perhaps most critical for businesses is that "planning queries"—those involving research and comparison—are growing 80% faster than overall usage.

The Death of the Keyword

The most vital takeaway here isn't the billion-user milestone, but the behavioral shift. When users write longer queries and engage in multi-turn conversations, the traditional "keyword" strategy becomes obsolete. A page optimized for a short-tail keyword will likely fail to match the conversational patterns of an AI Mode user.

The growth in planning queries suggests that AI is becoming a research partner. Users are using AI to evaluate services and compare products long before they reach the point of purchase. This means the "consideration phase" of the marketing funnel is moving entirely into the AI interface.

The Decision: Review your high-value commercial pages. Instead of asking "What keyword does this target?", ask "What complex research question does this answer?" If your content doesn't provide the depth required for a "planning" query, it will be overlooked by AI Mode.

Expert Interpretation: The "Brief" vs. The "Keyword"

Jeffrey Cohen of Skai captures this perfectly. He argues that shoppers are no longer typing "running shoes"; they are providing a detailed brief, such as "what are the best running shoes for a wide foot that I can wear for a half marathon training on pavement under $150."

This shift means that the brand that provides the most comprehensive, specific answer during this research phase owns the consideration. The transition from keyword to conversation isn't a future prediction—the data shows it is already the current reality.

The Conflict Over llms.txt Guidance

In a confusing turn of events, Google's own teams are sending mixed signals regarding llms.txt—a proposed standard for providing machine-readable summaries for LLMs. The Google Search team has stated that llms.txt is not necessary for AI Search visibility. However, the Lighthouse team has integrated a check for llms.txt into version 13.3, flagging sites that lack the file as having errors.

Adding to the noise, Gary Illyes (via Mueller) clarified that while markdown pages can be useful for technical documentation, they aren't necessary for most general websites. He emphasized that sites should focus on discovery (being found) rather than optimizing for on-page agent tasks.

Navigating Internal Misalignment

This conflict highlights a gap between Google's Search team (focused on ranking and retrieval) and the Chrome/Lighthouse team (focused on agentic browsing and technical standards). The tradeoff here is between following "official" SEO advice and preparing for a future where AI agents browse the web like humans do.

If your site is primarily a content hub or a blog, the Search team's advice is likely the priority. However, if you maintain extensive documentation or a complex product catalog, the agentic browsing audits in Lighthouse suggest that machine-readable summaries will eventually be a standard for accessibility.

The Decision: Follow the advice to "prioritize needs before dreams." If you are currently struggling with visibility, ignore llms.txt and focus on content quality. If your visibility is stable and you have the resources, consider implementing a machine-readable summary to future-proof your site for agentic browsing.

The Agentic Browsing Perspective

Chris Long of Nectiv noted that the new Agentic Browsing audits in Chrome specifically check for a machine-readable summary at the domain root. This contradicts the narrative that SEOs don't need to worry about additional markup. It suggests that while llms.txt might not help you *rank* today, it may help an agent *understand* your site tomorrow.

The Theme of the Week: The Quiet Rebuild

If you look at the individual pieces, Google is telling us that the fundamentals of SEO still apply. They've published guides saying that AEO (AI Engine Optimization) and GEO (Generative Engine Optimization) are simply "still SEO." They tell us to focus on current needs and ignore the noise.

But if you look at the totality of the week, a different story emerges. Google is quietly rebuilding Search from the ground up. They've launched the biggest search box upgrade in 25 years, scaled AI Mode to a billion users, and introduced agents that proactively monitor the web. They are moving from a system of "indexing and retrieving" to a system of "monitoring and synthesizing."

Why This Matters

The key issue here is The timing puts this update in the middle of Google I/O week. Ranking movement over the next two weeks will overlap with other changes Google announced, which could make it harder to isolate what caused any shifts you see in Search Console. Your baseline... My read is to treat it as a decision point: what signal needs to become clearer, what part of the system is currently weak, and what evidence would show that the work is improving visibility rather than only adding activity.

That is the difference between reacting to a trend and building a useful search system. Connect this point back to the page template, internal linking, entity signals, content depth, crawl accessibility, and the way the brand is represented across the wider web before deciding what to change first.

Why This Matters

The key issue here is The Search box redesign prompts users to describe needs in longer, conversational queries. Paired with Gemini 3.5 Flash in AI Mode, responses mostly come from AI rather than traditional pages. Information agents continuously search and synthesize updates,... My read is to treat it as a decision point: what signal needs to become clearer, what part of the system is currently weak, and what evidence would show that the work is improving visibility rather than only adding activity.

That is the difference between reacting to a trend and building a useful search system. Connect this point back to the page template, internal linking, entity signals, content depth, crawl accessibility, and the way the brand is represented across the wider web before deciding what to change first.

Practical next steps

The useful part is not only the idea itself, but the operating habit behind it. Use it as a checklist for decisions: what deserves attention now, what should be monitored, what needs a stronger evidence base, and what can wait until the system has more scale.