Key takeaways
- A quarter of UK GPs already use generative AI in clinical practice. In a 2025 survey of 1,005 GPs, 25% reported using it, up from 20% a year earlier, and 24% of those users turned to it for treatment options. The first answer an HCP reads may no longer be on your website.
- AEO and GEO are still SEO, according to Google. Its generative AI features need no special markup, no AI text files such as llms.txt and no “chunking”. They need indexable pages with helpful, reliable, non-commodity content.
- The answer engines don’t agree on tactics. Google stopped showing FAQ rich results in May 2026. Microsoft still recommends question-and-answer formats for Copilot, because assistants can lift them “word for word”.
- For pharma, “word for word” is the point. Keep the qualifier in the same sentence as the claim, don’t hide safety information in collapsed sections, and don’t leave core information only in a PDF.
- Approval doesn’t travel automatically. MLR approval for a gated HCP asset or for one market does not authorise a public page. Public resources need their own planning, review and maintenance.
- You can now measure AI visibility directly. Google Search Console and Bing Webmaster Tools both report how your pages appear in AI-generated answers.
Answer Engine Optimisation (AEO) and Generative Engine Optimisation (GEO) describe efforts to make useful content discoverable and understandable in search experiences that generate answers. For pharma teams, the opportunity is to publish clear, current information whose claims, context and sources can be checked. Approved content and modular workflows offer a strong starting point, but no format or approval process guarantees an AI citation.
Someone researching a therapy area, an omnichannel content process or a technology partner may now encounter a generated answer before visiting a website. That changes the questions content teams need to ask: Is our information accessible? Does it answer the reader’s actual question? Can its evidence and intended context survive a summary?
What do AEO and GEO mean for pharma content?
Traditional SEO helps people find a page in search results. AEO focuses on providing a useful, direct answer to a question. GEO is commonly used for work aimed at visibility in generated answers, where a system may combine information from multiple sources. The labels overlap, and neither is a separate, guaranteed route into AI search results.
In May 2026, Google published a guide to optimising for its generative AI features, including a section on AEO and GEO. Its position is short: “From Google Search’s perspective, optimizing for generative AI search is optimizing for the search experience, and thus still SEO.” Pages must be indexed and eligible to appear in Search with a snippet, and important information should be available as text. Google says site owners can ignore tactics such as “chunking” content or creating AI text files like llms.txt, and that no special schema.org markup is required. What it does ask for is “non-commodity” content: expert-led material that offers more than common knowledge.
Microsoft, whose Bing index grounds the web answers in Copilot, is more prescriptive. Its guidance on inclusion in AI search answers recommends question-and-answer formats, descriptive headings and “sentences that make sense even when pulled out of context”, and warns against hiding important answers in tabs or relying on PDFs for core information.
Other AI products use their own retrieval and citation methods, so a tactic that helps one system cannot be assumed to work everywhere. Where the two guides agree is the foundation: accessible text, clear structure, visible evidence and current information. For a life sciences organisation, that makes AEO and GEO an extension of content quality and governance: the right information, available to the right audience, with its meaning and evidence intact.
Why should pharma content teams pay attention now?
A quarter of UK GPs already use generative AI in clinical practice, and the share is growing.
In a January 2025 survey of 1,005 UK general practitioners, 25% reported using generative AI tools in clinical practice, up from 20% in the same researchers’ survey a year earlier (Blease et al., BMJ Health & Care Informatics, 2024). Among those users, 24% reported using them for treatment options, and 95% of all respondents said they had no professional training in using these tools (Blease et al., Digital Health, 2025). This is self-reported use in UK primary care, not evidence that an AI answer changed a prescription. But it does mean the answer an HCP reads is only as good as the sources behind it.
In a nationwide survey of resident physicians in Japan, 39.4% of 2,850 respondents reported using generative AI as a search engine in clinical work, but only 13% of those users relied on it as a primary reference for differential diagnoses (Miwa et al., JMIR AI, 2026). These were early-career doctors in one country, so the rate should not be generalised to all HCPs.
For a pharma content lead, the question is therefore practical: when an HCP looks for information in your therapy area, is there an appropriate, current and accessible resource that answers the question accurately? These studies do not establish that being cited makes a medicine the preferred choice. Clinical decisions also depend on evidence, guidelines, patient characteristics, safety, availability and local practice.
How do content operations support AEO and GEO?
An AI-generated answer can condense a complex subject into a few sentences. For regulated content, a statement may lose an essential qualifier, safety point, reference, audience restriction or geographic context along the way. Content teams cannot control an external system’s summary, but they can control the quality and clarity of what they publish.
That work begins before a page goes live. Global teams define claims and their substantiation; local teams adapt them for their market; medical, legal and regulatory reviewers assess the final communication in context. A modular content system can keep the links between a claim, its source, its approved wording and its permitted use intact as teams create assets across channels, especially when the modules draw on a maintained claims library.
That is a useful foundation for consistent, verifiable information. It does not mean an MLR-approved asset will be cited by an answer engine. Nor does approval for a gated HCP asset or for one market authorise publication on an open website. The public resource must be planned, reviewed and maintained for its specific audience and location.
The strategic connection is that content architecture makes approved information easier to reuse responsibly, while publishing and SEO practices make the appropriate public version easier to discover. Both parts need to work together.
What makes a pharma page more useful in an AI-shaped search journey?
Start with the audience questions your teams hear repeatedly. A global content lead might ask how to give local markets reusable, source-linked material that answers HCP questions consistently. A local brand manager might ask which approved information can be adapted for a market-specific page, and what requires a new review. Those operational questions shape whether a useful resource can be published and kept current.
In most markets, the pages an answer engine can read about a therapy area are public and non-promotional: disease awareness, patient education and public medical information. For an HCP-facing resource, map the information needs in the therapy area (patient population, evidence, efficacy endpoints, safety, administration and place in care) and select only claims and material appropriate for the audience and market. A public disease-awareness page and a restricted promotional resource may need different answers, access controls and approval paths.
Then make the page easy to navigate, check and quote:
- Answer the main question early. Give a concise, reviewed explanation before adding detail, and keep the necessary qualifications with the answer.
- Write sentences that survive being quoted. Microsoft notes that assistants can lift question-and-answer pairs “word for word” into AI-generated responses. For pharma, that means keeping an essential qualifier in the same sentence as the claim it qualifies. A footnote or the next paragraph may not travel with it.
- Use descriptive headings and distinct sections. Readers, and the systems that summarise for them, should be able to find definitions, requirements, examples and limitations without decoding marketing language.
- Show the evidence behind substantive claims. Provide the appropriate source and context for the intended audience, and distinguish an observed result from its interpretation.
- Keep essential information visible, in HTML. Microsoft warns that AI systems may not render content hidden in tabs or expandable menus, and that PDFs lack the structure HTML provides. Consider that before collapsing safety information into an accordion or leaving core information in a downloadable PDF. Publish meaningful text on crawlable pages and connect related resources through clear internal links.
- Preserve context when content is reused. Keep the approved wording, references, safety information, permitted audience and market together when a claim moves into another format or channel.
- Maintain the page, and retire it deliberately. Give content owners a process for checking review dates, links, approved claims and supporting references as information changes. A displayed update date should reflect a real review. When approval ends, don’t just take the page offline: an expired page can linger in search indexes and AI answers until it is next crawled. Redirect it to the current version, or signal clearly that it is gone, and notify search engines of the change. Bing supports the IndexNow protocol for this, and says it helps AI answers reference the current version of a page.
These are editorial and operational practices, not a recipe for guaranteed citations. They also make the page better for the people who read it directly.
Should pharma teams add FAQs and structured data?
Add FAQs when they answer genuine follow-up questions and help a reader make sense of the subject. Here the two search engines point in different directions. Google stopped showing FAQ rich results in Search altogether on 7 May 2026 (Google Search Central documentation updates) and says no special schema is needed for its AI features. Microsoft recommends question-and-answer formats, and Bing lists “clear headings, tables, and FAQ sections” among the things that help AI systems reference content accurately.
A genuine FAQ serves readers and suits both. For pharma, the same rule applies as elsewhere on the page: write each answer so it is accurate on its own, with its qualifiers, because it may be quoted on its own. Structured data can describe visible page content, but it does not guarantee a citation or replace useful copy.
How can teams tell whether their content is working?
Both major search engines now report AI visibility directly. Google Search Console’s generative AI performance report, available to all sites since August 2026, shows how often your URLs appeared in AI Overviews, AI Mode and Discover’s AI features, by page, country and device. Bing Webmaster Tools’ AI Performance report shows which pages were cited across Microsoft Copilot, Bing’s AI summaries and partner experiences, and the grounding queries the AI used to find them.
Those reports show where you appear, not whether the answer was right. For that, run a small, repeatable audit. Ask medical, brand and field teams which questions HCPs raise across the treatment journey. For suitable questions, record what search and AI experiences say, which sources they cite, whether your appropriate public resources appear, and whether the answers preserve essential context. Repeat across relevant markets and languages.
Pair those observations with measures your team can act on: relevant search visibility, qualified visits, engagement with published resources and feedback on content gaps from field and medical teams. AI-generated answers vary by product, prompt, location and time. A single screenshot cannot establish brand preference or prove that a content change caused a citation or a prescription.
The audit is especially useful for finding operational gaps. If a system repeatedly misstates an evidence point or safety limitation, investigate the cited sources and your own public information. If local teams cannot publish a timely answer to a common question, examine the content system and approval path as well as the page itself.
Where should a pharma content team start?
Pick one therapy area and a few high-value, market-appropriate resources: a public educational page, an HCP resource where access is permitted, and an answer to a frequent question. Map each published statement back to its approved source and owner. Check whether the answer is easy to find, whether the evidence and limitations are visible in the same place as the claim, and whether the information can be kept current across markets. Look at both AI reports for those pages. Address gaps through your normal medical, legal and regulatory workflow, then monitor what changes.
The opportunity is larger than a new acronym. AEO and GEO give content leaders another reason to connect what happens inside the content supply chain with what their audiences can find outside it. Clear writing and sound evidence matter; so do reusable approved content, local adaptation, review and ongoing ownership. Together, they make trustworthy information easier to publish and maintain as discovery changes.
Build public pages from approved content
Shaman automates the production of approved content across channels and markets, and lets local teams adapt it themselves. Web pages are built from the same approved modules as emails and detail aids: localised per market, version-controlled, and updated at source instead of page by page.
Frequently asked questions
What is the difference between SEO, AEO and GEO?
SEO helps people find a page in search results. AEO (answer engine optimisation) focuses on giving a direct, useful answer to a question. GEO (generative engine optimisation) is used for work aimed at visibility in AI-generated answers that combine several sources. The labels overlap, and Google treats both AEO and GEO as SEO.
Do pharma websites need special markup or an llms.txt file to appear in AI answers?
Not for Google. Google says no special schema.org markup or AI text files such as llms.txt are needed for its generative AI features, and that tactics like chunking content can be ignored. Pages must be indexed and eligible to be shown in Google Search with a snippet. Other AI products may work differently.
Are FAQ sections still worth adding to pharma pages?
Yes, when they answer genuine follow-up questions. Google stopped showing FAQ rich results in May 2026, but Microsoft recommends question-and-answer formats because assistants can lift the pairs word for word into AI-generated answers. Write each answer so it is accurate on its own, with its qualifiers.
Can MLR-approved content be published on an open website?
Not automatically. Approval for a gated HCP asset or for one market does not authorise publication on a public website. A public resource must be planned, reviewed and maintained for its specific audience and location, through the normal medical, legal and regulatory workflow.
How can we see whether AI answers use our pages?
Google Search Console’s generative AI performance report shows impressions in AI Overviews, AI Mode and Discover by page, country and device. Bing Webmaster Tools’ AI Performance report shows which pages were cited in Microsoft Copilot, Bing’s AI summaries and partner experiences, and the grounding queries behind those citations. Combine both with a manual audit of the questions HCPs actually ask.
Can a pharma company keep its website out of Google’s AI answers?
Yes. Search Console has a Search generative AI control, available worldwide since 31 August 2026. Inclusion is the default. Excluding a property removes its content from AI Overviews, AI Mode and Discover’s AI features, including links, without affecting regular search ranking. The control does not apply to AI products from other companies.
Sources: Google Search Central, “Optimizing your website for generative AI features on Google Search” (May 2026), “AI features and your website”, documentation updates (FAQ rich result deprecation, May 2026) and Search Generative AI performance reports (June 2026); Search Console Help, “Search generative AI control”; Microsoft Advertising, “Optimizing your content for inclusion in AI search answers” (October 2025); Bing Webmaster Blog, “Introducing AI Performance in Bing Webmaster Tools” (February 2026); IndexNow documentation; Blease C et al., “General practitioners’ adoption of generative artificial intelligence in clinical practice in the UK: an updated online survey”, Digital Health 2025; Blease CR et al., “Generative artificial intelligence in primary care: an online survey of UK general practitioners”, BMJ Health & Care Informatics 2024; Miwa T et al., “Current landscape of generative AI use as a search engine among resident physicians: cross-sectional study”, JMIR AI 2026.
About the author
Janaina Ferreira · Marketing Manager, Shaman
Janaina is Marketing Manager at Shaman, with more than 16 years of experience in marketing and communications. She writes about content operations in life sciences, from modular content foundations to AI-assisted MLR review, connecting customer, industry and market perspectives on the challenges teams face in content production, compliance and innovation.