Google is removing a core suggestion feature while expanding health-focused AI capabilities in Search. Here's what builders need to know about optimizing for this shift.
Builders can adapt to AI-mediated search by optimizing for machine-readability, restructuring keyword research without 'What People Suggest,' and competing on content authority rather than keyword matching alone.
Signal analysis
Here at Lead AI Dot Dev, we're tracking a significant architectural change in Google Search: the removal of 'What People Suggest' - the feature that displayed user-generated query suggestions alongside traditional search results. This isn't a minor UI tweak. It represents Google's strategic decision to route that real estate toward AI-generated health information instead.
The removal signals that Google views AI-powered health answers as higher-value than crowdsourced suggestions. Instead of showing what humans searched for, Google is now prioritizing what its AI models can authoritatively answer about medical topics. This is a direct trade-off: less query discovery, more curated AI output.
For builders, this means the suggestion feature you may have leveraged for keyword research or understanding user intent patterns is gone. The SEO surface area has shrunk. Simultaneously, Google's health AI expansion means there's now a new ranking territory to occupy - one where your content needs to serve as source material for AI-generated answers rather than standalone ranking real estate.
Google's expanded health AI tools represent a material shift in how medical information flows through Search. Rather than presenting a ranked list of health websites, Google's AI now synthesizes health information, citing sources but controlling the narrative. This is Search 2.0 for healthcare queries.
The expansion likely includes more sophisticated natural language understanding for health conditions, treatments, symptoms, and drug information. It probably covers more query types - not just disease information but lifestyle, preventive care, and emerging health topics. This breadth means more queries get intercepted by AI before reaching traditional organic results.
Builders working in healthtech, medical content, wellness platforms, or patient education need to understand that ranking for health queries now requires two parallel strategies: ranking in traditional organic results AND being selected as a source for Google's AI health summaries. The latter requires reliable, well-structured, clinically accurate content that AI models can confidently reference.
The practical implications are clear: if you operate in health-adjacent spaces, you need to audit your content for AI-readability. This means markup that identifies credentials, clinical evidence, publication dates, and source transparency. Google's AI health tools are likely using signals like E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) to decide which sources to cite. Schema.org markup for health content - NewsArticle, ScholarlyArticle, MedicalWebPage - matters now.
Second, stop relying on 'What People Suggest' for keyword research. You've lost that data source. Pivot to direct user research, customer support conversations, community forums, and paid keyword tools. The organic discovery mechanism Google provided is gone. Build your own.
Third, if you're building AI-powered applications, consider how health content discovery flows through your product. If you're integrating Google Search results, you're now getting AI-mediated answers instead of traditional rankings. Your downstream users may be satisfied by AI summaries and not click through. Plan accordingly.
For content teams: health topics now require two optimization paths - one for traditional ranking, one for AI citation. This is higher friction but necessary. As reported from the source material, this shift affects every builder working with Google's search ecosystem, making strategic adaptation essential. Thank you for listening, Lead AI Dot Dev.
Best use cases
Open the scenarios below to see where this shift creates the clearest practical advantage.
One concise email with the releases, workflow changes, and AI dev moves worth paying attention to.
More updates in the same lane.
Cognition AI has launched Devin 2.2, bringing significant AI capabilities and user interface enhancements to streamline developer workflows.
GitHub Copilot can now resolve merge conflicts on pull requests, streamlining the development process.
GitHub Copilot will begin using user interactions to improve its AI model, raising data privacy concerns.
