Brands with strong traditional SEO rankings are getting skipped by ChatGPT, Perplexity, and Google’s AI Overviews. Not because their content is bad, but because it’s structured for a retrieval system that AI pipelines don’t use. Four days at SEO Week NYC 2026 laid out exactly what’s broken and what fixes it.

You’ve likely watched this play out already: rankings hold, but traffic from AI-generated answers goes to competitors. Or a prospect mentions they “looked it up” before calling, more recently meaning they asked an AI. The problem isn’t your SEO. It’s that the signals AI systems use to decide what to cite are often different than the signals that determine traditional rankings, and most brand sites haven’t been built for them yet.

AI Systems Filter Out Most Content Before They Ever Read It

AI retrieval pipelines evaluate content through a series of eligibility checks before a model ever sees it. Content that fails those checks can’t be cited, regardless of its quality or ranking. Krishna Madhavan, Principal Product Manager at Microsoft AI, opened the conference by describing what he called the “invisible, converged web”: a layer of grounding confidence scores, safety filters, publisher controls, and attribution signals that sits between your content and the AI systems your audience is using. If your content doesn’t carry the right signals, it gets filtered out at that layer. It never reaches the model.

This is the structural gap most brands don’t know they have. A page can rank on the first page of Google and be completely absent from AI-generated answers on the same topic, because ranking signals and retrieval eligibility signals are different. Google evaluates pages. AI pipelines evaluate whether individual content blocks are structured, sourced, and verified enough to ground a response. Madhavan’s framing was precise: modern SEO and GEO now feel less like ranking tactics and more like a distributed systems challenge, where the goal is coordinating the signals that let AI pipelines trust and reuse your content.

In every GEO audit we run at Oomph, most brand sites are missing at least two of those signals. The most common gaps are invisible in standard SEO tooling, which is exactly why brands with strong traditional performance are still surprised when their AI citation share is near zero.

Traffic Metrics Will Lie to You About Your AI Search Performance

AI Overviews, ChatGPT, and Perplexity are answering questions in your category and not sending traffic to your site, but your analytics won’t show you that as a problem, because there’s no traffic to track. Jori Ford, Chief Marketing and Product Officer at FoodBoss, introduced the HEO (Hybrid Engine Optimization) framework at SEO Week specifically to address this measurement gap. Her Hybrid Engine Score is a weekly composite that tracks both traditional ranking performance and AI citation performance in a single number. Measuring them separately, or measuring only one, gives you an incomplete and often misleading picture of your actual search visibility.

Dale Bertrand of Fire&Spark extended this into the CFO conversation that most marketing leaders are currently losing. If your traffic is down but AI-influenced conversions are up, you’re actually winning. GA4 misses most AI-driven attribution, so you look like you’re failing. Bertrand’s work with global brands showed that revenue-focused GEO consistently produces stronger business outcomes than traffic-focused SEO when you measure far enough downstream. The brands building that measurement and implementation frameworks now are the ones who’ll be able to defend AI search investment in 12 months, when leadership starts asking why organic traffic hasn’t recovered.

“Revenue-focused GEO consistently produces stronger business outcomes than traffic-focused SEO.”

A Weak Paragraph Loses to a Strong One Every Time

AI systems retrieve at the paragraph level, not the page level, which means every paragraph on your site now competes independently to be cited. Mike King’s session was the most direct of the conference on this point. His framing: Google has been operating semantically for over a decade, most SEO tooling still does keyword math, and the gap between what tools measure and what AI systems actually evaluate has become the opportunity for brands willing to close it. A well-structured, well-evidenced paragraph on a thinner site gets cited ahead of a buried, unfocused paragraph on a high-authority domain.

The practical consequence for your content team is specific. Paragraphs need to open with their conclusion, not build toward it. Each paragraph should address one provable idea with enough context that it can be extracted and stand alone. Sourcing needs to be explicit and named. An unnamed statistic is an assertion an AI system can’t ground.

The brands we work with who’ve rebuilt their content architecture around these requirements are seeing measurable improvement in AI citation rates within 60–90 days. That improvement shows up in AI Overview appearances and third-party platform citations before it shows up in traffic numbers.

Four Technical Requirements Now Sit Between Your Content and AI Citation

Structured, sourced, crawlable, and machine-readable content gets cited by AI systems. Content missing any one of those properties gets filtered before retrieval. Andrea Volpini, CEO of WordLift, described the staged retrieval process AI systems use: models don’t consume your site whole, they pull from a pre-filtered subset of content that met a minimum bar for structure and verifiability. Content that isn’t structured, connected, and verifiable gets excluded from that subset, regardless of how good it is as writing.

The four technical requirements that determine whether your content clears that bar are: AI crawler access confirmed in your robots.txt; schema markup that is complete, accurate, and present on key pages; an llms.txt file that correctly tells AI agents what they can use from your site; and content blocks written so individual paragraphs can stand alone as cited answers. In every GEO audit we run at Oomph, most brand sites are missing at least two. None of these are advanced configurations. They’re the new baseline for being retrievable. Platforms like Scrunch can show you exactly where you stand across ChatGPT, Perplexity, Gemini, and Google AI Overviews: which prompts surface your brand, which source pages are driving citations, and where competitors are getting cited in your place.

The Brands That Close This Gap First Will Be Significantly Harder to Displace

AI citation compounds the same way that traditional search authority compounds. Brands that establish consistent citation history build a signal advantage that takes competitors real time to close. The difference from traditional SEO is that the window to build that advantage early is shorter, because the field is moving fast and the gap between brands actively building for AI retrieval and brands waiting to see how it develops is widening every month.

The sequencing for closing that gap is straightforward. Technical access for AI crawlers comes first, because you can’t be cited if you can’t be read. Schema markup and structured data come next, because they’re the verification signals AI systems use to trust your content.

Passage-level content architecture follows. Reformatting existing strong content for standalone paragraph retrieval is often faster than creating new content. Third-party brand presence on the platforms AI models train on comes last, because it’s the authority signal that determines whether an AI system treats your content as a credible source or skips it in favor of one it recognizes.

At Oomph, we run GEO audits that score your site across all four of these dimensions and return a prioritized 30-day action plan. If you’re not sure where your brand stands on AI visibility, the audit tells you exactly which gaps are costing you citations right now. Talk to us about a GEO audit.

Summary

Health systems grown through acquisition are investing heavily in unified digital front doors – the patient-facing layer of scheduling, intake, navigation, and engagement. But most of these initiatives stall because the front door is a design problem, while the real barrier is an architecture and governance problem: dozens of disconnected content management systems, conflicting editorial workflows, and duplicate content libraries that sit behind it. We call this the Front Door / Back Office Gap. With healthcare M&A accelerating – 231 health services deals in the first half of 2025 alone – and the digital front door market projected to reach $82 billion by 2031, closing this gap is the difference between a unified patient experience and an expensive redesign layered on top of operational chaos.

Through May 2025, more than 445 health service deals totaling $64 billion were announced. That pace is not slowing. In 2025, approximately 44% of announced M&A transactions involved a distressed party, and healthcare services M&A volume rose 14.4% in the first half of 2025, with total deal value surging 549.8% to $20.8 billion.

Every one of those transactions creates the same digital problem: two or more organizations, each with its own website (or websites), its own CMS, its own editorial team, its own brand standards, and its own content governance structure. Add in the EHR systems that power scheduling, provider directories, appointment booking, and patient portals, and the fragmentation runs deeper than the marketing layer. All of this is now expected to present a unified experience to patients.

The executive mandate is always some version of “build a digital front door.” The assumption is that the front door is the hard part. It is not. The digital front door market is projected to grow from $31.66 billion in 2026 to $82.25 billion by 2031, and platform vendors are delivering increasingly capable scheduling, intake, and engagement tools. The technology for the front door exists. What does not exist in most post-acquisition health systems is the content infrastructure to support it.

Why Do “Unified Digital Front Door” Initiatives Stall After the Design Phase?

Because they treat the patient-facing experience as a design challenge when it is actually a content operations challenge.

A digital front door needs content – provider directories, service line descriptions, location information, patient education materials, insurance and billing guidance, procedural instructions. In a health system that has grown through acquisition, that content exists across multiple platforms, maintained by multiple teams, governed by multiple (and often contradictory) editorial standards.

The Front Door / Back Office Gap refers to the structural disconnect between the unified patient experience a health system promises and the fragmented content operations that must produce it.

You cannot build a coherent front door on an incoherent back office.

Yet this is precisely what most digital front door initiatives attempt: a new presentation layer on top of unreformed content infrastructure.

Only 14% of healthcare M&A deals reach successful integration, with 83% of practitioners citing integration hurdles as the leading cause for failure. The digital properties are rarely the first integration priority – EHR consolidation, revenue cycle management, and clinical systems take precedence. By the time leadership turns attention to the website, the content fragmentation has compounded for months or years.

What Does Post-M&A Digital Fragmentation Actually Look Like?

It looks like a health system operating 8 to 15 separate websites on 3 to 5 different CMS platforms, each with its own content model, its own editorial workflow, and its own version of “how we describe cardiac services.”

Here is the pattern we see in practice. A regional health system acquires two community hospitals and a physician group. The parent system runs Drupal. One hospital runs WordPress. The other runs a legacy proprietary CMS. The physician group has a Squarespace site that a practice manager updates. Each site describes overlapping services in different language, with different levels of clinical detail, different calls to action, and different information architectures. Provider directories are maintained in at least two places and contradict each other on accepted insurances.

This is not a hypothetical. As KPMG noted in its 2025 healthcare M&A outlook, “postclose integration must prioritize digital enablement, especially in RCM, patient engagement, and data interoperability.” But digital enablement for patient engagement requires content consistency – and content consistency requires infrastructure that most post-acquisition systems simply do not have.

For patients, the fragmentation is not abstract. A patient searching for a cardiologist in the newly merged system finds one provider directory on the parent system’s website and a different, partially overlapping directory on the acquired hospital’s site. The scheduling pathways are different. The insurance information may conflict. Deloitte estimates healthcare organizations stand to lose $54.4 billion if they cannot deliver on consumer expectations, and the expectation is increasingly a coherent, consumer-grade digital experience across the entire care network.

Why Is Multi-Brand CMS Consolidation Different in Healthcare?

Because healthcare content carries compliance obligations that make “just merge the sites” genuinely dangerous, and because local brand equity often has clinical implications that other industries do not face.

Three factors make healthcare CMS consolidation distinct:

Regulatory content requirements. Service descriptions, patient education materials, consent language, and pricing transparency content all carry compliance obligations – HIPAA, ADA, CMS price transparency rules, and state-specific regulations. When you consolidate content from multiple sources into a unified platform, every piece of clinical and billing content must be reviewed for regulatory accuracy in its new context. A service description that was compliant on Hospital A’s website may not be compliant when published under the parent system’s brand with different insurance contracts.

Local brand trust. In many acquisition scenarios, the acquired facility’s brand carries decades of community trust that the acquiring system does not yet have in that market. Rushing to rebrand or subsume the local site under a parent domain can alienate patients who chose their provider based on the local name. The digital architecture needs to accommodate a multi-brand reality – shared infrastructure, shared governance, but distinct brand presentation where it matters clinically and commercially.

Editorial team distribution. Unlike a SaaS company where a central marketing team owns the website, health system content is produced by marketing, clinical departments, physician liaisons, compliance, and sometimes individual practices. When multiple teams across 6 to 10 departments collaborate on content, governance overhead increases by 27%. In a post-acquisition health system, those teams have never worked together and may not even know each other’s content exists.

What Does a Realistic Content Architecture Look Like for Multi-Brand Health Systems?

It looks like a shared content infrastructure with federated editorial control – not a single website, and not a collection of disconnected ones.

The architecture that works for post-acquisition health systems is what we describe as a multi-brand content platform: a single CMS instance (or a tightly integrated set of instances) with a unified content model, shared governance, and brand-specific presentation layers. Content is structured once – a provider profile, a service line description, a location record – and published to whichever brand surface needs it, styled appropriately for each. Our work with Bradley Hospital illustrates this in a healthcare context: Bradley’s site runs on Drupal using the Domain Access module suite, sharing infrastructure with the Brown University Health system while presenting as a fully independent domain with its own brand, content, and editorial control.

This is the approach we took when consolidating 8,500+ pieces of content across disconnected systems for Workhuman, building a unified Contentful-based content system with structured models, governance documentation, and team training. The same architectural principles apply to healthcare, with the addition of compliance review workflows and HIPAA-aware access controls. We have written separately about how to evaluate CMS platforms specifically for healthcare organizations – the selection criteria are meaningfully different from what a SaaS or media company would prioritize.

West Virginia University Health System, which grew to 21 hospitals through M&A, offers an instructive parallel. By standardizing its integration infrastructure, WVUHS cut interface development time by more than 50% and accelerated onboarding of new facilities. The same principle applies to content: standardize the model, federate the editorial control, and new acquisitions plug into the existing architecture rather than creating another silo.

What Should Health System Digital Leaders Do First?

Accept that the digital front door initiative is actually a content infrastructure initiative, and sequence the work accordingly.

1. Inventory what you actually have. Before any platform decision, catalogue every digital property across the system – websites, microsites, provider directories, patient portals, landing pages. For each, document the CMS, the editorial team, the update frequency, and the content overlap with other properties. In our research and strategy engagements, this audit consistently reveals 30 to 50% more digital properties than leadership realized existed.

2. Define shared content types before selecting a platform. Provider profiles, locations, service lines, conditions, insurance information – these are the content objects that must be consistent across every brand surface. Design the content model for these shared types first, with input from clinical, compliance, and marketing stakeholders across all entities. The platform decision follows from the model, not the other way around.

3. Plan for multi-brand governance from day one. Establish who owns the shared content model, who can publish under which brand, and how compliance review works when content appears across multiple sites. This governance structure is the single most important determinant of whether your digital front door initiative produces a unified patient experience or a redesigned facade over the same fragmentation.

The digital front door is a compelling vision. But for health systems shaped by acquisition, the path to that vision runs through the back office first – through the content models, editorial workflows, and governance structures that determine whether “unified” is a patient experience or just a press release.

Health systems that invest in content infrastructure before investing in the front-end design will build something durable. Those that do not will build something that looks unified and operates in fragments.

Oomph is a digital experience consultancy serving regulated industries and mission-driven organizations, including healthcare, higher education, government, and associations, where compliance, accessibility, and trust are non-negotiable.

This week Salesforce signed a deal to acquire Contentful, and most of the coverage is filing it under CMS M&A. I think that misses what’s actually being bought. The interesting part is what an AI agent does with a content platform.

An agent doesn’t take your content and show it to someone. It reads structured, governed source material – your context – and writes the content itself: the answer, the reply, the assembled page, generated on the fly, per customer, per channel. So the most valuable thing you can hand an agent is context it can trust.

That distinction matters more than it sounds. Agents are moving into production quickly, and they will answer your customers and your own staff straight from that material. Point one at clean, governed context and it’s useful. Point it at stale, contradictory, ungoverned content and it will hand back a fluent, confident, wrong answer. Garbage in, confident-sounding garbage out. Either way, it’s speaking for you.

I’ve argued before that content won the web, but context wins the agents, that the CMS was quietly becoming the layer agents reason over. This deal is the biggest CRM on the planet putting real money behind exactly that. Oomph is a gold-certified Contentful partner. We build on the platform daily, and we’ve integrated it with Salesforce and the systems around it. So I’ve been watching this one closely.

So look at what Salesforce already owned. Customer data, and plenty of it – they paid $8 billion for Informatica last year to pull it all together. CRM, marketing, commerce, service. Agentforce on top, ready to act. The one thing they couldn’t pull out of a customer record was the context an agent needs to say something trustworthy: approved product facts, current pricing, the disclosure that has to run in a regulated market, the brand voice, and the right localized version for each audience. Contentful holds all of that. It fits a pattern, too – Informatica, then Momentum, Qualified, Cimulate, and now Contentful. That’s a company building an agent stack on purpose, one acquisition at a time. They decided the context layer was worth buying rather than building.

A customer record can’t tell an agent what it’s allowed to say

Your CRM knows who the customer is. It has no idea what you’re allowed to say to them.

That gap is the whole game. Ask an agent “what’s the current return policy in Germany for this product line” and it will answer either way. Whether the answer is right comes down to three things. Your data tells the agent who is asking. Your context, the structured, governed, current truth behind everything, is what it reasons from. And the content is what the agent generates out of that context in the moment. Data and content are the parts most companies already plan for. Context is the part that gets treated as an afterthought, and it’s the part an agent leans on most.

Jujhar Singh, who runs the applications group at Salesforce, framed the deal around three things working together: the data, the AI-driven content, and the experience. Context is the thread running through all of it. The agent generates the content live, the experience is only as good as what it generates, and both stand on whether the context underneath is trustworthy. That’s what Salesforce bought: the governed context everything else gets built from.

The old acronym survives. The job is changing.

For twenty-five years a CMS has been a Content Management System: somewhere to keep content and push it onto a page for a person to read. An agent uses the same system for a different job. It reasons over that governed context and generates whatever needs to be said from there. Same three letters, new system. The CMS is turning into a Context Management System, and Salesforce just paid to own one.

The headless platforms saw this coming. They had already solved the hard parts an agent needs – structured models, versioning, permissions, and audit trails – and were adding the connective tissue to talk to agents directly. When the biggest player in the category backs that direction with a checkbook, the rest of the market should take the hint.

The old job doesn’t go anywhere, to be clear. Plenty of organizations are running Contentful today purely to manage website content, several of them clients of ours, and that work is the foundation the rest of this gets built on. The structured models, the editorial workflows, the governance, the API-first delivery you set up to run a modern website are the exact things an agent reasons over. You built it to publish pages. You were also building the context layer, whether you planned to or not.

And context reaches well beyond the public website. A lot of it lives in intranets and internal systems: the policies, the procedures, the product knowledge, and the operational detail that actually run the business. That changes who owns the platform. For most of its life a CMS was a marketing purchase, a tool for the brand and the website. Once agents need that governed internal context too, it outgrows marketing, and ownership moves to IT, data, and the enterprise. That shift is already underway, and if you sit in one of those teams, it’s landing on your desk whether you asked for it or not.

The part most of the coverage will skip

The blast radius isn’t the same for everyone. For a retailer, a wrong answer is a bad refund. For a hospital, a bank, a university, or a regulator, it’s a misinformed patient, an exposed internal document, or a benefit you never actually offered. Same technology, very different exposure, which is why governed context is a bigger deal for the organizations we work with most – in healthcare, higher education, government, and associations – than the headlines suggest.

There’s a sovereignty question here too, and it lands hardest on the public sector. Contentful is a German company, and bringing it under a US owner pulls it under US law, including the CLOUD Act. With the EU moving to restrict sensitive public-sector data on US clouds, a government or higher-ed buyer should put that on the question list, not in a footnote.

Where this leaves you

The instinct in most organizations is to make more content. The work that matters now is getting your context in order – structured, current, owned, and governed – because your agents will generate from it whether it’s clean or not. The content platform becomes a system of record: where brand, policy, product knowledge, and compliance live, and where your agents go to find the truth.

If you already run Contentful, the practical news is reassuring. Salesforce has said it keeps operating on the same platform, APIs, and support model, with tighter Agentforce integration as the roadmap rather than a forced migration. Nothing about your current build breaks. The move now is to point the foundation you’ve built at what’s coming next, and that’s a conversation we’re already having with clients.

The organizations that get their context right now are the ones whose agents will be worth trusting later. The big platforms have started spending real money to get there. The window to do the unglamorous work before your agents go live is open right now, and I don’t think it stays open long.

Oomph is a digital experience consultancy serving regulated industries and mission-driven organizations, including healthcare, higher education, government, and associations, where compliance, accessibility, and trust are non-negotiable.

The DOJ just handed organizations an extra year on their WCAG compliance deadline, but that doesn’t mean the work stops. If anything, it’s a signal to accelerate.

On April 20, 2026, the Department of Justice issued an Interim Final Rule extending the ADA Title II web accessibility deadline by one year. State and local government entities serving populations of 50,000 or more now have until April 26, 2027, to achieve full WCAG 2.1 Level AA conformance. Smaller jurisdictions have until April 26, 2028. For organizations that have already been tracking Oomph’s earlier breakdown of the WCAG compliance landscape, this is the latest update, and the stakes are higher than the extension might suggest.

The Extension Doesn’t Change the Underlying Obligation

The DOJ’s rule revision pushes a deadline. It doesn’t remove one. WCAG 2.1 Level AA remains the legal standard under the ADA, and the obligation to make digital content accessible to people with disabilities has been codified since the original Title II rule was finalized in April 2024. The extension was issued in response to documented capacity constraints; some organizations were struggling with the scope of remediating thousands of PDFs and auditing vendor platforms. But organizations that have paused work in anticipation of a rollback shouldn’t interpret this as a signal to wait longer.

Private litigation hasn’t paused. ADA Title III lawsuits, which apply to private businesses, saw a 102% increase in recent years and aren’t tied to the DOJ’s enforcement calendar.

What the New Deadlines Mean for Your Organization

The updated compliance schedule breaks down by entity type:

• State and local governments (50,000+ population): April 26, 2027
• State and local governments (under 50,000 population) and special districts: April 26, 2028
• Private organizations that contract with or provide digital services to public entities: bound by the deadlines of their government partners, with contractual accessibility provisions becoming standard in procurement

If you work with public sector clients, including healthcare systems, universities, or municipalities, your contracts will increasingly reflect these requirements. Vendors are legally responsible for the accessibility of the tools and platforms they provide to covered entities. An extended deadline for your client doesn’t reduce your exposure.

Why an Extra Year Is Actually an Opportunity

Organizations that treat this extension as breathing room will spend it the same way they spent the last two years: waiting. The ones that use it intentionally will close the gap permanently.

True WCAG compliance requires more than fixing what’s broken today. It means building accessibility into your content production process, your procurement checklist, and your development workflow so that new content is compliant from the moment it’s published. There’s no grandfathering for content published after the compliance date; anything that goes live after your deadline has to meet the standard on day one.

The extension also offers something the original deadline didn’t: time to do the audit properly. A comprehensive audit, one that combines automated scanning with manual testing and includes real users with disabilities, takes time to execute and even more time to act on. Organizations that use this year to conduct a thorough audit, triage findings by risk, and implement remediation systematically will be in a fundamentally stronger position than those who rush a surface-level fix in the final weeks before a hard deadline.

What to Prioritize Now

The compliance work that matters most isn’t complicated, but it does require deliberate sequencing. Start with an honest inventory of what you have: web pages, PDFs, forms, video content, mobile applications. Identify which assets carry the highest user traffic and the highest legal exposure. That’s where remediation starts.

From there, the priorities are consistent regardless of organization type:

1. Audit your highest-traffic pages and mission-critical digital services first.
2. Address the underlying code. Overlay widgets don’t satisfy the standard and have been explicitly called out by the DOJ as insufficient.
3. Review vendor contracts and confirm that third-party platforms in your digital ecosystem meet WCAG 2.1 Level AA.
4. Build an accessibility policy that defines ownership, sets standards for new content, and creates a process for users to report issues.
5. Train staff who create and publish digital content, not just developers.

The organizations that will find April 2027 manageable are already working through this list. The ones who don’t have 12 months to close a gap that was supposed to be closed already.

The Bigger Picture Hasn’t Changed

The DOJ’s extension is administrative. The underlying direction of travel toward universal, codified digital accessibility standards has been consistent for years and isn’t reversing. WCAG 3.0, expected no earlier than 2028, will shift from a pass/fail model to a tiered scoring system with Bronze, Silver, and Gold levels. Organizations that achieve full WCAG 2.1 Level AA conformance now will enter that transition from a position of strength.

Healthcare organizations that don’t structure their content for AI retrieval are already losing patients before the first visit. Tools like ChatGPT, Perplexity, and Google’s AI Overviews have become a first stop for health questions. They pull answers directly from web content without sending users to a website. If your organization’s content isn’t structured to show up in those answers, you’re invisible at the moment patients and caregivers are most actively searching.

Answer Engine Optimization (AEO) is the practice of structuring content so AI systems can find it, understand it, and cite it. It’s distinct from traditional SEO, though the two aren’t in conflict. Understanding the difference matters for every healthcare communicator making content decisions right now.

AI Search Engines Retrieve and Synthesize, They Don’t Rank and Link

Traditional SEO optimized full pages for rankings. A page with strong domain authority, good keyword coverage, and solid backlinks would surface near the top of a results page. Users would click through to read it. That model still works for many queries, but it’s no longer the whole picture.

If you’re weighing how SEO and generative engine optimization fit together, the distinction is worth understanding clearly.

AI answer engines don’t rank pages. They retrieve specific passages from across the web, synthesize an answer, and present it directly to the user. The user often never clicks through to the source. According to SparkToro’s 2024 zero-click search study, nearly 60% of Google searches end without a click. For healthcare communicators, that means a significant portion of your potential audience is forming opinions about their health, their options, and their providers without ever landing on your site. AI-generated answers accelerate that trend.

Content strategy decisions right now should account for whether your content is structured so AI systems can extract a clear, direct answer from it, not just whether it ranks.

Healthcare Authority Helps, But Structure Is What Gets You Cited

Health information is a high-stakes category for AI systems. Google classifies health, finance, and legal content as YMYL (Your Money or Your Life) because inaccurate answers carry real consequences. AI systems tend to be more selective about which sources they retrieve and cite in these categories.

That selectivity works in favor of established healthcare organizations. Hospitals, health systems, and credentialed clinics carry demonstrated authority, and that matters more in YMYL retrieval than in general content. But authority alone isn’t enough. Content still has to be structured correctly to be extracted. A well-credentialed source with poorly structured content will lose to a less-credentialed source that’s written in a way AI systems can parse.

Most healthcare organizations already have the credibility AI systems favor. That means the path to better retrieval runs through content structure, not authority-building.

What AI Systems Actually Look For in Content

AI retrieval systems evaluate each paragraph independently, treating it as a standalone candidate for citation. A page with a strong introduction and weak middle sections will have the strong introduction cited and the rest ignored. This changes how content needs to be written.

Passages that get retrieved share a common structure. They open with a direct, declarative answer to a specific question. They use plain language rather than jargon. And they don’t require surrounding context to make sense.

A paragraph that opens with “There are many factors to consider when evaluating treatment options” is hard for an AI system to use. A paragraph that opens with “Most patients with early-stage [condition] have three primary treatment options” gives the system something it can extract and cite directly. That’s the foundation of citation-ready content architecture, and it’s the standard healthcare organizations should be building toward.

Schema markup also plays a meaningful role. Structured data signals to AI systems how to categorize and use your content. Three schema types matter most for healthcare organizations: FAQ schema for patient question pages, MedicalCondition schema for clinical content, and HowTo schema for procedural or instructional pages. Organizations that have implemented structured data on their clinical and service pages have a measurable advantage in AI retrieval over those that haven’t.

The Patient Journey Now Runs Through AI Before It Reaches You

Patients and caregivers typically begin with a question typed into an AI tool or search engine, well before they consider visiting a specific organization’s website. By the time they reach your site, they’ve already formed an understanding of their condition, their options, and what they’re looking for based on whatever content those tools surfaced.

Whether your organization is part of that pre-visit understanding depends entirely on whether your content was present in the AI’s answer. If it wasn’t, a competitor’s content filled that space instead.

For healthcare marketers, showing up in AI answers is about whether your organization is part of the conversation patients are having before they ever contact you. That matters well beyond traffic metrics.

Where to Start: Four Practical Priorities

Most healthcare organizations don’t need to rebuild their content from scratch. They need to identify where their existing content is close to being retrievable and close the gap. Four areas consistently make the biggest difference.

Audit your highest-traffic clinical and service pages for passage structure. Read the first sentence of every paragraph on each page. If those sentences don’t directly state the main point of that paragraph, the content isn’t structured for AI retrieval. Rewriting opening sentences to lead with the conclusion is often the fastest improvement available.

Build out FAQ content with direct, complete answers. FAQ pages are one of the most reliably retrieved content formats in AI search because they’re structured around specific questions with discrete answers. Healthcare organizations that publish clear FAQs on common patient questions, symptoms, procedures, recovery, cost expectations, give AI systems exactly the format they’re looking for.

Implement structured data on clinical pages. If your web team hasn’t added schema markup to your clinical and service pages, that’s a near-term technical priority. The implementation isn’t complex, but it requires coordination between your content team and whoever manages your CMS.

Prioritize topical depth over topical breadth. AI systems favor sources that demonstrate consistent depth on a topic over sources that cover many topics superficially. For healthcare communicators, this means investing in comprehensive content on your core service lines rather than spreading thin across every health topic your organization touches.

The same characteristics that make content useful for AI retrieval, clear structure, direct answers, demonstrated depth, make content better for human readers too. Raising the standard in one area raises it across the board.

Oomph will be at NESHCo May 27–29 in Burlington. If you’re headed there too, we hope to see you.

Let me be upfront about something. When I started digging into how universities handle student data, I genuinely expected to find a mixed bag. Some good, some bad, nothing too shocking. What I actually found was a picture far messier than most institutions would like to admit publicly.

The Data Challenge Universities Actually Face

Higher education has a data complexity problem that’s genuinely different in scale from most other sectors. On a single campus, you’ve got admissions offices, finance departments, health centers, libraries, research labs, and dozens of other units, all touching personal data in ways that rarely get coordinated. Then the General Data Protection Regulation arrived in 2018 and essentially said: sort it out, or pay for it.

Some universities sorted it out. Others are still finding their footing, six-plus years on.

That’s not a criticism. It’s a structural reality. A retailer knows roughly what data it holds and why. A university processes the personal information of students, staff, alumni, research participants, visiting scholars, applicants who never enrolled, donors, and contractors, often simultaneously, often under completely different legal bases. The scope is genuinely daunting.

Student records alone are an iceberg. Grades, health accommodations, financial aid history, disciplinary notes, mental health referrals. Each category carries its own sensitivity tier under the regulation, and special category data (health information, for instance) requires explicit protections that can’t be bolted on as an afterthought.

Research is where things get particularly complicated. Academic research can receive a degree of flexibility under GDPR, but that flexibility comes with strings attached: ethics board approval, data minimization obligations, retention schedules that actually get followed. A number of research departments are still operating on informal data management practices, and the gaps show.

What GDPR Actually Requires (Without the Legal Fog)

When people talk about GDPR compliance, they tend to either catastrophize it into a terrifying bureaucratic maze or wave it away as box-ticking. Neither framing is accurate.

At its core, the regulation asks institutions to answer some fairly practical questions. Do you know what personal data you hold? Where it lives? Who can access it? Under what legal basis are you processing it? And how long are you keeping it before you delete it?

That last one trips universities up constantly. Retention schedules exist on paper at most institutions. Whether the systems actually enforce deletion is a different conversation entirely.

Then there’s the rights side of things. Individuals, including students and staff, have the right to access their data, correct inaccuracies, request deletion under certain circumstances, and object to specific types of processing. Universities need workable processes for handling these requests, not a generic email address that someone checks when they get around to it.

Lawful basis matters too. There’s a tendency in higher education to lean on legitimate interests as a catch-all justification for data processing, but that’s not how it works. Processing needs a clearly identified basis, documented before the processing starts, not reverse-engineered after a complaint arrives.

The Consent Problem on Campus

Consent under GDPR must be freely given, specific, informed, and unambiguous. That last word does a lot of work.

The challenge with universities and consent is structural. When a student applies for a place, registers for courses, or uses campus health services, there’s an inherent power imbalance at play. Can a student genuinely refuse to consent to data processing when saying no might affect their access to university services? GDPR is fairly clear that where a meaningful power imbalance exists, consent isn’t a reliable legal basis. Yet plenty of institutions still rely on it for processing activities where a stronger basis would be more appropriate.

Alumni engagement sits in particularly awkward territory. Sending a fundraising appeal to a graduate decades later requires a legitimate legal basis.

“We’ve always done it” isn’t one. Neither is a pre-ticked opt-in buried in a registration form from years ago.

Third-Party Vendors and the Supply Chain Nobody Talks About

Universities run sprawling technology ecosystems. Student information systems, virtual learning environments, library databases, HR platforms, research repositories, catering apps. Behind each of those sits a vendor processing personal data on the institution’s behalf.

Under GDPR, data processors must have written agreements in place with controllers. Those agreements need to specify what data is being processed, for what purpose, under what security standards, and what happens to the data when the contract ends.

In practice, many universities have signed vendor contracts where the data processing terms weren’t exactly scrutinized closely. US-based edtech vendors in particular sometimes arrive with terms drafted for a pre-GDPR world, or for US legal frameworks that don’t map neatly onto European requirements. Negotiating those terms retroactively is tedious and uncomfortable. But it’s necessary.

The Schrems II decision added another layer of complexity. Transferring personal data outside the UK or EU requires additional safeguards: standard contractual clauses, transfer impact assessments, the full apparatus. International research collaborations and cloud services with US data centers both fall squarely into this territory.

Breach Notification: The 72-Hour Clock Nobody Loves

A personal data breach must be reported to the relevant supervisory authority within 72 hours of the institution becoming aware of it. Not three working days. Seventy-two hours, including weekends.

Universities experience breaches. Phishing attacks that compromise staff email accounts. Misconfigured databases. Laptops stolen from cars. The breach itself isn’t always the compliance failure. The failure is not having the detection and reporting processes in place so that when something goes wrong, the right people know quickly and the clock starts accurately.

Data protection officers at universities often describe the internal challenge as a political one. When a breach happens, the instinct from senior leadership is frequently to investigate quietly before involving regulators. That instinct is understandable. It’s also legally risky. The 72-hour requirement isn’t aspirational.

Where Universities Actually Stand

The honest answer is: it depends enormously on the institution.

Some large research universities have invested significantly in data protection infrastructure. Dedicated DPOs with real authority, properly resourced information governance teams, institution-wide data audits, staff training that goes beyond an annual click-through module. These institutions are in a reasonably strong position.

Smaller institutions, often with less resource and less specialist expertise, sometimes find GDPR compliance still sitting largely with whoever got handed the responsibility without the budget or headcount to match it. That’s a resourcing problem as much as a knowledge one.

The UK’s Information Commissioner’s Office has taken enforcement action in higher education. Fines have been issued. Reprimands published. The sector isn’t flying under the radar.

What Good Actually Looks Like

The institutions handling this well tend to share a few common traits. Data protection is genuinely embedded in how decisions get made, not consulted at the end of projects as a compliance sign-off. Their Records of Processing Activities document is actively maintained and regularly reviewed. Staff who handle sensitive data receive meaningful training rather than performative e-learning. And the DPO has a direct line to senior leadership, not a reporting line buried three layers down in legal or IT.

Perhaps most importantly, these institutions treat GDPR compliance as an ongoing discipline rather than a project with a finish line.

The data landscape keeps changing, the technology keeps changing, and the regulation, while stable in text, continues to be interpreted in new ways through enforcement decisions and case law.

Building systems robust enough to adapt to that reality is, ultimately, the whole game.

Structured content distribution is the decoupling of content from presentation through a headless CMS and Content as a Service (CaaS) architecture. It is a sound strategy for organizations managing complex content distribution networks across multiple channels. 

To be the most successful, this digital transformation requires organizations to change both their publishing workflows and their content ownership structures. Governance complexity affects 41% of CaaS adopters (PDF), workflow mismatches impact a third, and training requirements average 14 to 18 weeks. 

We have implemented these systems for clients in healthcare, financial services, and higher education, and the pattern is consistent: the three failures that kill structured content initiatives are the preview gap, the ownership vacuum, and the training deficit. Here is what we have learned about each one — and what actually works.

The Promise 

The pitch for structured content distribution is compelling: create content once, store it as modular data in a headless CMS, deliver it via API to any channel (web, mobile, kiosks, AI agents) without reformatting. The CaaS market is projected to reach $2.8 billion by 2035, and over 65% of enterprises have adopted headless CMS architectures.

What they do not tell you is that integration challenges affect 46% of adopters using legacy CMS platforms, and that 31% of enterprises encounter deployment delays exceeding six months. The technology works, but the governance requires just as much attention and is often overlooked. We have seen this avoidable pattern repeat across many structured content implementations.

Why Do Structured Content Migrations Stall?

In short, because organizations implement the technology without redesigning how their teams create, review, approve, and own content. That’s the governance problem.

A headless CMS decouples content from presentation. But most editorial teams have spent years, sometimes decades, working in systems where creating content and seeing how it looks are the same activity. WordPress, Drupal, and even SharePoint have a visual editing experience: build a page, see the page, publish the page.

Structured content does not work this way. Authors fill in fields like title, body, metadata, and related entries to publish content objects, not pages. As one analysis of Contentful’s editorial interface notes, “content editors work in structured content entry forms without seeing how content will render in production.” The front-end determines how those objects appear to users.

That architectural distinction is the correct one for consistent omnichannel delivery. It is also the one most likely to break editorial workflow expectations when teams do not deliberately plan for this big shift. In our experience, three governance failures account for the vast majority of structured content stalls.

What Is the Preview Gap, and Why Does It Derail Teams?

The preview gap is the loss of visual context that editorial teams experience when moving from a WYSIWYG (what you see is what you get) environment to a structured content interface, and it is the most immediate friction point in any headless CMS migration.

Authors who previously built pages visually are now filling in form fields and trusting that a front-end will render them correctly. The shift from “building a page” to “managing a content object” takes adjustment, and “once teams adapt, the structured approach tends to produce more consistent, reusable content.” The problem is what happens before they adapt.

What happens is that authors create workarounds. They paste formatted content into rich text fields, breaking the structured model. They submit tickets to developers asking “what will this look like?” multiple times per week. They maintain shadow documents in Google Docs so they can see their work in context. Every workaround is a governance failure — content that exists outside the system, formatting that undermines the content model, and developer time consumed by preview requests instead of feature development.

The planning that pays off includes building live preview environments for as many content sources as possible. This development work typically gets deprioritized because it is not user-facing, but it determines the success of the new system. As one migration guide puts it, headless platforms deliver excellent editorial experiences “when configured correctly — visual editing, live preview, flexible page-building, role-based permissions. But that configuration is work, it doesn’t happen by default.” Budget for it, build it first, and do not launch editorial access without it.

What Is the Ownership Vacuum?

The ownership vacuum is what happens when structured content crosses departmental boundaries without clear governance over who maintains the content model, who approves changes to shared components, and who is accountable when content is reused in a context the original author never intended.

In a traditional CMS, the marketing team owns the marketing pages, the product team owns product pages, etc. Structured content breaks this model deliberately — a product description created once might appear on the website, in a mobile app, in an email campaign, and through a chatbot simultaneously. But governance complexity affects 41% of CaaS adopters, and multi-team collaboration across 6 to 10 departments increases governance overhead by 27%.

Questions seldom asked include: 

• When the compliance team changes a regulatory disclaimer, who is responsible for verifying that the change renders correctly across every channel consuming that content object?
• When marketing adds a field to the product content type, who assesses the downstream impact on the mobile app and the support knowledge base?

We have seen organizations discover these questions six months post-launch, usually during a content audit that reveals inconsistencies no one can trace. In regulated industries — healthcare, financial services, higher education — those inconsistencies are compliance risks.

Knowing these pitfalls ahead of time can lead to the establishment of a content model governance board before migration begins. A small, cross-functional group (typically 3 to 5 people spanning content strategy, development, and compliance) owns the content model as a shared organizational asset. They approve changes to content types, evaluate reuse implications, and maintain a living inventory of where shared content objects appear. This role does not exist in traditional CMS organizations because it’s not needed. But in structured content environments, it is absolutely necessary.

Why Does the Training Deficit Compound Everything?

Because organizations allocate 90% of their transformation budgets to technology and implementation, and only 10% to change management — the part that determines whether anyone actually uses the system they built.

Training requirements for CaaS implementations average 14 to 18 weeks, the elapsed time from initial exposure to genuine editorial fluency. This training creates the confidence for authors to create, structure, and publish content without reverting to old habits or filing developer tickets. Most implementation budgets account for a one-day training session and a knowledge base article. The gap between that and actual fluency is where adoption dies.

The compounding effect of the training deficit makes this particularly damaging. Undertrained authors hit the preview gap and panic. Without clear governance ownership, there is no one to answer their questions authoritatively. They build workarounds. Those workarounds corrupt the content model. The corrupted content model undermines the case for structured content. Stakeholders lose confidence. The transformation stalls.

BCG’s study of 850+ companies found that only 35% of digital transformations meet their value targets globally. The failure rate is a change management problem that looks like a core problem with the technology itself.

To avoid this failure spiral, structure editorial onboarding as a phased engagement, not a one-and-done event. In our implementations, we start with a pilot group of 3 to 5 authors working with the system while the front-end is still being built. They surface friction points the development addresses in real-time. When the broader editorial team is onboarded, the common pain points have been resolved, and the pilot group serves as advocates who can answer questions and support their peers. This approach adds little cost and dramatically improves adoption velocity.

What Should Organizations Do Before Starting a Structured Content Migration?

Treat governance design as a foundation to build a successful digital transformation:

1. Audit your editorial workflows as they actually operate. Map who creates content, who reviews it, who approves it, and where informal workarounds exist. As one migration planning guide advises, most publishing workflows “are often based on legacy systems, informal approvals, or staff availability. The result? Delays, missed steps, and content that never quite gets finished.” Your structured content governance must account for the real workflow, not the theoretical one.
2. Define content model ownership before selecting a platform. Determine who will own the content model as an organizational asset, who can request changes, and what the approval process looks like. This governance structure should be platform-agnostic — it is an organizational decision, not a technical one. We have helped clients build this through our roadmapping and strategy engagements, and it consistently reduces mid-project governance confusion.
3. Budget for editorial experience parity. If your authors currently have WYSIWYG editing, live preview, and visual page building, do not assume they will accept a simpler and more limiting form-based interface. Calculate the development effort required to provide contextual preview in your new architecture and include it in the implementation scope, not as a phase-two enhancement. Phase two rarely arrives before editorial frustration does.

Wrap Up

The CaaS pitch is not wrong. Structured content distribution is the right architecture for organizations publishing across multiple channels, and it is increasingly the right architecture for AI readiness — structured data is what AI systems consume most effectively. But the promise underestimates the organizational effort to make it successful.

Technology is the easy part. Governance, training, and editorial adoption are harder, and that is where implementations succeed or fail.

We have built these systems on Contentful, Drupal, and composable architectures for organizations in regulated industries where getting content wrong has real consequences. The lesson we keep relearning is the same one: start with the team, not the platform.

Summary

On April 20, 2026, the Department of Justice extended ADA Title II web accessibility compliance deadlines by one to two years for state and local government entities. The extension does not pause underlying accessibility obligations, and it does not extend the separate HHS Section 504 deadline that may apply to hospitals and nonprofits receiving federal funding. Organizations tracking a single calendar are exposed to what we call the two-deadline trap. The right response is to use the extension to systematize accessibility, not to defer it.

This article is not legal advice. Confirm which rules apply to your organization with qualified counsel.

Four days before the original compliance date, the DOJ reset the clock.

Per a summary from Jackson Lewis, state and local governments with populations over 50,000 now have until April 26, 2027 to comply with WCAG 2.1 Level AA under Title II. Smaller entities and special districts have until April 26, 2028.

If you run digital for a public entity, exhale. If the extension made you slow down, recalibrate. The deadlines moved, but the risk did not.

What actually changed, and what did not?

The DOJ pushed back the date that specific technical requirements become enforceable. 

What did not change: the underlying ADA obligation to provide accessible programs and services. Title III public-accommodation risk for hospitals, providers, and nonprofits is unaffected. Demand letters and accessibility-related litigation continued straight through the extension announcement; they did not pause for it.

The compliance date is a deadline, not a start date. Organizations that wait will spend the extension period accumulating debt in templates, content, and vendor contracts, then attempt to remediate it in a sprint. That sprint is where the avoidable risk lives.

Why doesn’t the extension help hospitals and nonprofits?

The DOJ rule covers state and local government entities. It does not cover hospitals and nonprofits whose accessibility obligations come from a different source: federal financial assistance under Section 504 of the Rehabilitation Act.

Jackson Lewis notes that HHS has a separate Section 504 web accessibility compliance date, and as of this writing it has not been extended. Until HHS acts, plan as if it holds.

If your organization receives HHS funding, operates patient portals, runs scheduling or billing flows, accepts donations online, or hosts learning and event platforms, your timeline is likely shorter than the DOJ headline suggests. Title III public-accommodation exposure runs alongside it.

What is the two-deadline trap?

The two-deadline trap is the assumption that a single, well-publicized accessibility deadline is the only one that applies to your organization.

It happens when leadership tracks the DOJ Title II extension and treats it as the program’s primary clock, while a separate Section 504 or Title III obligation governs the actual exposure. The result is a roadmap pegged to the wrong date and a remediation budget that arrives late.

Avoiding it requires confirming, in writing and with counsel, which rules apply, which deadlines govern, and which user-facing services fall inside each scope.

What does day-one compliance actually look like?

Day-one compliance is the day your organization can demonstrate that new content is published accessibly, high-impact user flows work with assistive technology, vendors are managed as part of your posture, and governance is in place.

In our experience working with regulated organizations, the failure mode is rarely the homepage. It is the publishing system that keeps creating new accessibility debt — new pages, new PDFs, new embedded forms, new third-party widgets — faster than remediation can clear it. A defensible program stops the inflow before it works down the backlog.

That means accessibility moves upstream into design system components, CMS templates, content briefs, QA gates, and vendor intake. “Archived content” stops being a folder name and becomes a governance decision with rules. Procurement language changes so the next contract renewal does not lock in another year of vendor risk.

Will an accessibility overlay protect you?

No. Overlays can adjust some visual and interaction settings for some users, but they do not remediate the underlying barriers in your templates, components, content, or third-party tools. The Overlay Fact Sheet, signed by hundreds of accessibility practitioners and organizations, documents the consensus position.

If a widget is your strategy, assume you still need code-level fixes in templates, manual testing with assistive technology, content authoring training, and a third-party tool plan. The widget is not a substitute for any of those, and a number of overlay vendors have themselves been named in accessibility lawsuits.

What should accessibility leaders do this week?

Five actions, in order.

1. Confirm which rules apply, and which deadline governs. Title II, Section 504, Title III, or more than one. If there is uncertainty, this is a counsel question, not an internal one.
2. Name a single accessibility owner. Not a committee, but one person responsible for coordinating across IT, content, legal, and procurement. Accountability is the program.
3. Test your top five user-critical flows manually. Forms, authentication, scheduling, payments, donations, patient portal — whatever blocks access to your primary services. Manual keyboard-only and screen reader software spot checks find what automated scanners miss.
4. Inventory third-party tools and audit their contracts. Where contracts are silent on accessibility, flag them as priority renewals. Your compliance posture runs through every embedded vendor whether the contract says so or not.
5. Write a 90-day plan and share it with leadership. Specific, resourced, and tracked beats comprehensive and aspirational every time.

The extension is not a year off. It is a year to put a defensible program in place before the rules apply more explicitly than they already do. Use it wisely.

Bill Gates wrote “Content is King” back in 1996. He was right for about thirty years. On the open web, the winners were the ones who could produce, distribute, and monetize content at scale. That era shaped how we built digital products, how we organized marketing teams, and how we thought about content platforms.

That era is getting a new chapter.

When content becomes context

In the age of agents, content is context. It’s the raw material an AI uses to answer a customer’s question, draft a proposal, summarize a policy, or make a decision on behalf of your business.

If your context is a mess, your agent is a mess. Garbage in, confident-sounding garbage out.

For organizations in healthcare, higher education, and associations (industries where we work every day) that governance layer isn’t a nice-to-have. A health system deploying an agent to answer patient questions needs to know which clinical protocol is current, who approved it, and what the agent is and isn’t allowed to cite. An association managing member benefits can’t afford an agent that surfaces a two-year-old policy document as current guidance. And it’s not just the regulated organizations themselves. The enterprise technology companies that serve these industries, the SaaS platforms, the data providers, the system integrators, face the same challenge: if the content powering their products isn’t structured and governed, the agents built on top of it will inherit every gap. The stakes in regulated industries make the content-as-context problem concrete and urgent, but the same dynamics show up everywhere brand, voice, and accuracy matter: retail pricing, financial disclosures, B2B product specifications, public sector policy. Different risk profiles, same fundamental problem.

This isn’t theoretical. Gartner predicts that 40% of enterprise applications will include task-specific AI agents by the end of 2026, up from less than 5% in 2025. The shift is already moving from prediction to product.

The platforms we work with every day show the movement clearly. The Drupal AI Initiative launched last June and hit $1 million in funding within five months, with the Drupal AI and AI Agents modules reaching production-ready status in October 2025. Acquia built on that foundation with Acquia Source, shipping three AI agents for its Drupal-powered SaaS CMS in December. Contentful open-sourced its MCP server and has been publishing active guidance on agentic content operations. These aren’t experiments. They’re shipping.

Across the category, the pattern is broad. Contentstack launched Agent OS in September 2025 and introduced what it calls the “Context Economy” as its positioning. Kontent.ai shipped what it calls an Agentic CMS the following month. The Model Context Protocol that Anthropic introduced in late 2024 has become the connective tissue, adopted by OpenAI, Google DeepMind, and most of the CMS world.

The platforms are ready. The question is whether your content is.

What agents actually need

An agent doesn’t want a rendered web page. It wants structured, canonical, permissioned, versioned truth. That means:

• Structure so the agent can reason over content rather than scrape through marketing copy
• Versioning so it knows which policy, price, or product spec is current
• Permissions so the agent answering a customer question can’t pull from an internal-only HR doc
• Freshness signals so stale content doesn’t get treated as authoritative
• Governance so legal, brand, and compliance can trust what the agent says on their behalf

That’s the same job a mature content platform has been doing for years, just pointed at a new kind of consumer.

We’ve seen this movie before

Every channel shift exposes whether your content was ever really structured to begin with. CD-ROM, then the web, then mobile, now agents. Each one forces organizations to untangle content from presentation. Headless CMS platforms like Drupal, Contentful, Sanity, and Strapi won that argument. Content as structured data, delivered via API, rendered wherever you need it.

Agents are the most demanding channel yet. They don’t just display your content. They consume it, reason over it, and then take action. If your content is trapped inside HTML blobs or buried in PDFs that no one’s touched since 2021, it’s not ready to be context. Structure is the whole game now.

Where context lives today

Right now, company context is scattered across:

• Websites and headless CMS platforms
• GitHub repos full of markdown
• Confluence, Notion, SharePoint, Google Drive
• Salesforce, HubSpot, and a dozen other systems of record
• PDFs, Slack threads, and somebody’s laptop

Some of these are built for governance. Most aren’t. GitHub is hands-down great for technical content and version control, but marketing and legal teams aren’t opening pull requests to update a pricing page. Notion is excellent for collaboration, weak on structured content models and role-based delivery. Every organization I talk to has some version of this scatter, and it’s about to become a much bigger problem.

The rise of the Context Management System

The old acronym still works. CMS. New job.

Headless CMS platforms have quietly solved about 70% of what agents need. Structured content models. API-first delivery. Editorial workflows. Roles and permissions. Versioning. Audit trails. What they’re adding now is the connective tissue. Acquia is embedding AI agents directly into Drupal-powered workflows through Acquia Source, and Contentful has open-sourced its MCP server to let agents take action on content operations. Across the rest of the category, Sanity launched its Content Agent in January 2026, and Storyblok, Brightspot, and dotCMS have released MCP servers of their own. MCP servers, vector indexing, semantic metadata, agent-optimized delivery endpoints. That’s a much smaller leap than building the whole governance layer from scratch.

The “just throw it all in a vector database” approach has real merit as a retrieval layer. Retrieval is one job. Governance is a different one: who owns canonical truth, who approved the content, when it expires, and who’s allowed to see it. That’s always been the CMS job. It matters more now, not less.

For teams working on Drupal, Contentful, or Acquia Source, this is encouraging. The architectural decisions those platforms made years ago (structured data, granular revisioning, API-first design) turn out to be exactly what AI agents need. Your investment in content architecture is paying off in ways you didn’t plan for. Call it a head start.

What to do about it

If you’re building agentic products, or planning to, the content question is the quiet one that will bite you later. This is the work we’re spending most of our time on with clients right now. A few forward moves:

1. Audit where your content actually lives and who owns it. You will be surprised.
2. Pick a source of truth for each category of content. Don’t let five systems claim the same ground.
3. Get your structured content models right. If your content is trapped inside HTML, it isn’t ready to be context.
4. Build the governance layer before you need it. Versioning, permissions, approval workflows. Your legal team will thank you. So will your agent.
5. Connect your CMS to your agents via MCP or equivalent. This is how context flows. Do it early.

Content was king when the battle was for attention. Context is king now that the battle is for correctness. Agents are only as good as the material you feed them, and that material has to be managed with the same rigor we’ve applied to code, to data, and yes, to content itself.

The organizations that treat content governance as infrastructure, not a cleanup project, will be the ones whose agents are trustworthy from day one. That window is shorter than it looks.

Summary

Most organizations are treating SEO and Generative Engine Optimization as two separate disciplines – and wasting resources in the process. The real strategic question is not which channel to optimize for but whether your content is built to be reused: extracted, synthesized, and cited by both search algorithms and AI answer engines. We call this Citation-Ready Content Architecture – a unified approach where structure, authority, and specificity make content perform across every discovery surface simultaneously. Organizations in regulated industries face compressed timelines: healthcare queries already trigger AI Overviews on nearly half of all searches.

Sixty percent of Google searches now end without a click. That number is not a forecast – it is a 2025 finding from Bain & Company. Meanwhile, Gartner predicts traditional search volume will drop 25% by the end of 2026 as users migrate to AI-powered answer engines. And here is the statistic that should change how you think about your content strategy: according to Ahrefs, 80% of URLs cited by ChatGPT, Perplexity, and Copilot do not rank in Google’s top 100 results for the original query.

That last data point is the one most SEO-vs.-GEO articles ignore. If the overlap between traditional rankings and AI citations were nearly complete, you could optimize for one and trust the other to follow. It is not. The two discovery channels draw from overlapping but meaningfully different content signals. Treating them as a single problem or two separate problems are both the wrong framing.

Why Is the “SEO vs. GEO” Framing Wrong?

Because it implies a choice between two competing strategies, when what actually matters is a single architectural principle applied across both.

SEO optimizes content for ranking position – getting your page onto a results list a human scans and clicks. GEO – Generative Engine Optimization, a term formalized by researchers at Princeton, Georgia Tech, and IIT Delhi in 2024 – optimizes content so AI systems can retrieve, synthesize, and cite it when generating answers. The Princeton study demonstrated that GEO techniques can boost content visibility in AI-generated responses by up to 40%, and that the most effective strategies vary by domain.

The difference is real. But the industry conversation has overcorrected, treating GEO as something exotic that requires a fundamentally new playbook. As Entrepreneur reported in April 2026, teams are making preventable mistakes by treating GEO “like an exotic new discipline” and shifting budget away from technical SEO into untested “AI visibility hacks.” Research from AirOps found that pages ranking number one in Google were cited by ChatGPT 3.5 times more often than pages outside the top 20.

Strong SEO remains the foundation. GEO is the structural extension that makes your existing authority legible to AI systems. They are not two strategies. They are one architecture.

What Makes Content “Citation-Ready” for Both Search and AI?

Citation-Ready Content Architecture is the practice of structuring content so it simultaneously ranks in traditional search results and gets extracted and cited by AI answer engines. It is not a new technology stack or a separate editorial workflow. It is a design principle: every piece of content your organization publishes should be built for reuse from the start.

Three characteristics define citation-ready content:

Modular structure. AI systems do not read your article top to bottom and decide whether to cite the whole thing. They extract passages – a definition, a statistic, a direct answer to a question. Content with clear headings, self-contained sections, and answer-first paragraphs gives both search engines and AI systems clean material to work with. The Princeton GEO study found that adding statistics to content improved AI visibility by 41%, and citing credible sources improved it by 115% for lower-ranked pages.

Demonstrated authority. Seer Interactive’s September 2025 study of 3,119 queries across 42 organizations found that brands cited in AI Overviews earned 35% more organic clicks and 91% more paid clicks than those not cited. Authority is no longer just a ranking signal – it is the qualification for being included in AI-generated answers at all. Author credentials, original research, linked sources, and topical depth are now dual-purpose investments.

Specificity over generality. AI systems select content that provides extractable facts – numbers, definitions, named frameworks, concrete comparisons. Content that gestures vaguely at a topic (“there are many factors to consider”) gets skipped in favor of content that states something specific and citable. We have written previously about how LLMs index and use content – the same accessibility and structural principles that help AI crawlers parse your pages also make your content more citation-worthy.

Why Are Healthcare and Higher Education Hit Hardest?

Because AI Overviews appear at disproportionately high rates for the query types these industries depend on – and the consequences of being absent or misrepresented are far more serious than lost traffic.

Conductor’s Q1 2026 analysis of 21.9 million searches found that healthcare queries trigger AI Overviews at a rate of 48.75% – nearly double the overall average of 25%. Technology queries trigger at roughly 30%. For healthcare organizations and universities, AI is already mediating nearly half the informational queries that drive patient acquisition and enrollment.

The real-world impact is already measurable. U.S. News reported in March 2026 that nearly 80% of people searching for degree information read Google’s AI Overviews, and many never click through to an institution’s website. The University of Maryland Global Campus responded by using AEO and GEO techniques to revise its degree pages and A/B test FAQ-style content. Johnson County Community College found that while AI-driven traffic represents less than 1% of its website visitors, engagement from that group is 59% above its site-wide average – suggesting AI-referred visitors arrive further along in their decision-making process.

For healthcare, the stakes go beyond enrollment. When AI engines synthesize clinical information, the accuracy of that synthesis depends on the quality and structure of the sources available. Organizations that have not optimized their content for AI citation are not just losing visibility – they are ceding authority over how their expertise gets represented to patients who increasingly trust AI-generated answers.

What Does the HubSpot Collapse Tell Us About This Shift?

That traffic built on loosely related content is structurally fragile in an AI-mediated search environment.

Multiple industry analyses documented an approximately 80% traffic drop across HubSpot’s blog properties as AI Overviews began answering the high-funnel informational queries that had driven HubSpot’s organic growth for over a decade. Pages about “famous sales quotes” and “cover letter examples” had driven enormous traffic but had minimal connection to HubSpot’s core CRM platform. When Google’s algorithm update prioritized content closely tied to a website’s core expertise, and AI Overviews began answering those generic queries directly, the traffic evaporated.

The lesson is not that content marketing failed. It is that content disconnected from your organization’s core authority is exactly the kind of content AI systems will summarize without ever sending a visitor your way. In our GEO optimization Q&A, we outline why organizations should start with their highest-authority content when optimizing for AI visibility rather than trying to cover every possible keyword.

For organizations in regulated industries – where your content is tightly tied to your institutional expertise by design – this is actually an advantage. A hospital publishing evidence-based patient education content is inherently closer to citation-ready than a SaaS company publishing tangentially related blog posts for traffic volume. The structural alignment is already there. What is often missing is the formatting and schema work that makes it extractable.

What Should Content Teams Do First?

Start with what you already have. The gap between SEO-optimized content and citation-ready content is usually structural, not substantive.

1. Audit your top 20 pages for extractability. Read the first paragraph of each section in isolation. Does it directly answer a question someone would ask an AI tool? If not, restructure it. AI systems and Google’s AI Overviews pull from the opening sentences of well-structured sections – bury your answer three paragraphs deep and it will not get cited.

2. Add the schema AI systems actually use. Implement FAQPage, Organization, Article, and author schema across your priority content. BrightEdge found that sites implementing structured data and FAQ blocks saw a 44% increase in AI search citations. Author schema is especially high-impact: websites with author schema are 3x more likely to appear in AI answers.

3. Track AI visibility alongside traditional rankings. Oomph’s GEO Analytics and Reporting service configures tracking in GA4 and Google Search Console to monitor AI bot traffic and AI-generated search impressions that standard analytics miss. At minimum, create referral segments for chat.openai.com, perplexity.ai, and other AI platforms, and watch for the signature pattern of rising impressions with declining clicks – the clearest signal that AI is summarizing your content without sending traffic.

The organizations that will maintain visibility over the next two years are not the ones choosing between SEO and GEO. They are the ones building content that works across both discovery surfaces from the start – structured for extraction, grounded in genuine expertise, and specific enough that AI systems treat it as source material rather than background noise.

That is not a new content strategy. It is the old one, built to the standard the new environment actually requires.

Summary

Most content strategies optimize for one outcome: ranking. Ranking is only half the visibility equation now. Citation-Ready Content Architecture, developed at Oomph, helps organizations build content that performs across traditional search results and AI-generated answers simultaneously. It rests on three principles – modular structure, demonstrated authority, and extractable specificity – and we apply it with clients in healthcare, higher education, and government where being cited accurately is as important as being found.

This crystallized during a client conversation earlier this year. We were looking at their analytics – a major healthcare organization – and the pattern was striking. Impressions were climbing. Rankings were stable. But clicks were dropping steadily, month over month. The content was being surfaced by Google, but patients were getting their answers from AI Overviews without ever visiting the site.

That’s a visibility problem most of us weren’t trained to solve – and it requires a different content architecture.

Gartner predicts traditional search volume will drop 25% by the end of 2026 as users migrate to AI-powered answer engines. Ahrefs found that 80% of URLs cited by ChatGPT, Perplexity, and Copilot don’t rank in Google’s top 100 for the original query. And the Pew Research Center’s study of 68,879 actual Google searches found that only 8% of users clicked a traditional result when an AI Overview appeared, compared to 15% without one – roughly half the click-through rate.

Content that ranks and content that gets cited aren’t always the same – but they can be, if you build for both from the start. That’s Citation-Ready Content Architecture.

What Is Citation-Ready Content Architecture?

Citation-Ready Content Architecture is the practice of structuring digital content so it simultaneously ranks in traditional search engine results and gets extracted, synthesized, and cited by AI answer engines like ChatGPT, Google AI Overviews, and Perplexity. Developed by Oomph as a framework for regulated industries, it combines modular content structure, demonstrated authority signals, and extractable specificity into a unified content design principle – replacing the need to maintain separate SEO and GEO strategies.

The key word in that definition is “simultaneously.” That means content architecturally designed to work across every discovery surface – ranked results, AI summaries, voice assistants, whatever comes next – because the underlying structure supports all of them.

In our work with clients across healthcare, higher education, and government, we’ve found this transition isn’t a massive lift for organizations with strong content fundamentals. The gap between SEO-optimized and citation-ready content is structural, not substantive – it’s about how content is organized, not whether it’s good.

Why Do Organizations Need a New Content Architecture Now?

Information discovery has forked. Content built for only one path leaves visibility on the table.

Two parallel discovery systems now exist. Traditional search ranks your content in a list users scan. AI-powered answer engines synthesize information from multiple sources into a single response – often without the user ever clicking through to your site.

The research is unambiguous. The foundational Princeton GEO study demonstrated that content optimized for generative engines can boost visibility by up to 40% in AI responses. But it also showed that the most effective strategies vary by domain – what works for a law firm doesn’t necessarily work for a children’s hospital. A March 2026 study from researchers at the University of Tokyo found that structural optimization alone – independent of content changes – improved citation rates by 17.3% across six major generative engines.

The most striking finding: research from AirOps found that pages ranking number one in Google were cited by ChatGPT 3.5 times more often than pages outside the top 20. Strong SEO remains the foundation. Citation-ready architecture is what makes that foundation legible to AI systems too.

What Are the Three Principles of Citation-Ready Content?

The framework rests on three principles. Each serves both search engines and AI systems simultaneously – that dual purpose is the point.

Modular structure

AI systems don’t read your article start to finish and decide whether to cite the whole thing. They extract passages – a definition, a data point, a direct answer to a specific question. Content with clear headings, self-contained sections, and answer-first paragraphs gives both search algorithms and AI systems clean material to work with.

We’ve written about how LLMs index and use content – and the takeaway is that the same accessibility principles that help AI crawlers parse your pages also make your content more citation-worthy. Semantic HTML, logical heading hierarchies, and sections that can stand on their own aren’t new concepts. They’re just worth more now than they’ve ever been.

Demonstrated authority

Being cited by AI systems has become a meaningful competitive advantage. BrightEdge found that sites earning citations inside AI Overviews see CTR increases of up to 35% compared to traditional organic rankings alone. Websites with author schema are 3x more likely to appear in AI answers, and sites implementing structured data and FAQ blocks saw a 44% increase in AI search citations.

In practice, demonstrated authority means: Author credentials on every piece. Original data and research when you have it. Linked sources for every claim. Topical depth across related content – not one-off articles, but interconnected clusters that demonstrate sustained expertise.

Authority isn’t just a ranking signal – it’s the entry qualification for AI inclusion.

Extractable specificity

This is the one that separates citation-ready content from content that’s merely well-written. AI systems select content that provides extractable facts – numbers, definitions, named frameworks, concrete comparisons. Content that gestures at a topic (“there are many factors to consider”) gets skipped in favor of content that states something specific and citable.

The Princeton study found that adding statistics to content improved AI visibility by 41%, and citing credible sources improved visibility by 115% for lower-ranked pages. That 115% figure is significant: it means content that isn’t winning the traditional ranking game can still earn AI citations by being specific and well-sourced.

How Does This Apply Differently in Regulated Industries?

For regulated industries, the stakes are higher and the timeline compressed – but the structural fit is actually better.

Conductor’s Q1 2026 analysis of 21.9 million searches found that healthcare queries trigger AI Overviews at a rate of 48.75% – nearly double the overall average. For healthcare organizations and universities, AI is already mediating close to half the informational queries that drive patient acquisition and enrollment.

The structural advantage for regulated industries is real. Organizations in regulated industries – healthcare systems, universities, government agencies – produce content that’s inherently tied to their institutional expertise. A hospital publishing evidence-based patient education content is structurally closer to citation-ready than a SaaS company publishing tangentially related blog posts for keyword volume. The authority is real. The specificity is built in by the nature of the content. What’s typically missing is the formatting and schema work that makes it extractable.

When we optimize content for GEO, the biggest wins often come from restructuring content that already exists – not creating new content from scratch.

What Should You Do First to Make Your Content Citation-Ready?

Start with what you have. The gap is almost always structural, not substantive.

1. Audit your top 20 pages for extractability. Read the first paragraph of each section in isolation. Does it directly answer a question someone would ask an AI tool? If it doesn’t, restructure it. AI systems pull from the opening sentences of well-structured sections. Bury your answer three paragraphs in and it won’t get cited.
2. Implement the schema that AI systems actually use. FAQPage, Organization, Article, and author schema across your priority content. Author schema is especially high-impact – BrightEdge’s research shows it triples your likelihood of appearing in AI answers.
3. Track AI visibility alongside traditional rankings. Oomph’s GEO Analytics and Reporting service configures tracking in GA4 and Google Search Console to monitor AI bot traffic and AI-generated search impressions. At minimum, watch for the pattern of rising impressions with declining clicks – that’s the clearest signal that AI is summarizing your content without sending visitors.
4. Build for reuse from the start. Every new piece of content should include at least one standalone definition, one specific data point, and one direct answer to a question your audience would ask an AI tool. Make it easy for AI systems to cite you. That’s the architecture.

In 20 years of building digital experiences, I’ve watched a handful of shifts fundamentally change how content needs to be structured. Mobile was one. Accessibility-first was another. The shift to AI-mediated discovery is the next.

Citation-Ready Content Architecture isn’t a bolt-on to your existing strategy – it’s the design principle that makes your existing strategy work across today’s fragmented discovery environment. Organizations that build for it now will compound that advantage as AI-mediated search grows. Those that wait will be optimizing for a world that has already moved on.

We’re helping clients across healthcare, higher education, and government make this shift. If your analytics show that pattern – impressions climbing, clicks dropping – start here.

As direct website traffic decreases and LLMs slurp up text from multiple sources to mix together and redistribute to users, it has never been more important to maintain high-quality online content. A ROT analysis — which stands for Redundant, Obsolete, Trivial — is a framework through which we can evaluate site content to improve it for usability, SEO, retrieval, and GEO. 

This is a flexible exercise that can apply to a variety of digital properties: web pages, PDFs, intranets, social media pages, call center databases, support knowledgebases… Anywhere that you, as an organization, are speaking to your audience, you have an opportunity to share knowledge, build trust, and solidify your brand image.

Similarly, ROTten content can mislead users, seed doubt, and damage your reputation.

When you use a ROT analysis to kickstart a content clean-up project, you’re ensuring that users and bots alike find only your latest, clearest, most accurate and relevant information. When done properly, it can even set up your team for better content production and management in the future.

How Oomph Approaches Content ROT Analyses

Every ROT analysis looks a little different depending on the industry, content, and what a particular audience needs. 

Make a Plan

Before jumping into dashboards and spreadsheets, we start with a conversation. With any project, we need to understand what problems your organization needs to solve: What’s important to you and your users? Where are you struggling? This is our chance to understand the why behind your content.

As we learn more about what you need, we’ll define what ROT is for your organization. What existing policies do you have in place around archiving old or outdated content? If you don’t have policies, what makes sense for you? What key user journeys should the analysis focus on? We’ll answer these questions and more to make sure we’re going into the analysis with a clear vision of what your content should look like so we can see where it’s missing the mark.

Find the ROT

Let’s get into what ROT looks like specifically and where we look for it.

Redundant means the content communicates information in more than one place. This can result in an inefficient information architecture and messy user paths. There are times duplicate content can be helpful, like when separate task flows require some of the same information. That’s why it’s important to know upfront what journeys are most important to prioritize. In these cases, when the same content shows up in multiple places across a website or app, it’s important to have a method for keeping all content in sync. If it’s possible to edit this content in a single place while distributing it across multiple pages, that can be a great method for maintaining a single source of truth.

Redundant might also refer to several articles written over time that deal with the same topics in similar ways. This can result in the newest content on the topic having its SEO/GEO cannibalized by older content on the same topic. Users might more easily find older content when you want them to find the latest. 

Obsolete content includes outdated information, language, and (probably broken) links. This type of ROT is especially damaging when it’s related to products, services, or something users are trying to take action on. It’s important to keep in mind your entire digital landscape; Maybe you’ve updated the content on your main service page, but did you remember to update automated emails, support articles, and meta descriptions? What pages aren’t built directly into a user flow but can still be found by Google? 

Consider whether it makes sense to archive or unpublish old content, like past news and events. And consider your audience: Is there a reason users would be looking for a historical record, and is that need strong enough to justify keeping it available? If you do choose to keep outdated information published, make sure that it’s clear to users that the content is old and consider providing a link to the latest version.

Trivial content can be harder to define and is highly subjective based on the organization. This might look like “fluff” pieces shared for the sake of SEO or maintaining a publishing schedule, or excessive marketing language that ultimately doesn’t serve you or your users. It might be low-traffic fine print details that apply to a specific audience who typically finds it another way. Maybe it’s content that is related to but outside of your core business function. You’ll need to make some decisions about what is important to you. 

To find ROT, we’ll use a variety of collection and measurement tools. SortSite, Screaming Frog, and Siteimprove can locate broken links, orphaned pages, and other SEO issues. Google Analytics, Hotjar, Contentsquare, and MS Clarity can show common user flows and help identify trivial content. Data from these tools can also prioritize the analysis by surfacing what content is most important to users. If a page gets a lot of traffic, we know that it needs to be clear, up-to-date, and accurate. If a page isn’t visited much, we need to ask whether it should be more highly trafficked, consolidated with higher performing content, or removed.

Deliverables and Next Steps

After all this sorting and evaluating, you might be wondering what you’ll tangibly get out of the process. We know content teams are busy, and going through a review can feel like adding more work to the pile. How can we help prioritize meaningful progress here?

The big outcome is one of my personal favorites: a clean, annotated, actionable spreadsheet. Specifically, we’ll put together an audit of your content with links, page titles, notes on whether the content falls into any of the three ROT categories, and what to do about it: keep, modify, combine, or delete. Depending on the tools your content team uses or what you are willing to subscribe to, we might prepare dashboards and reports directly within an app that your team can use as an ongoing progress tracker. Wherever this list of to-do’s lives, we’ll help you prioritize it so you can start ticking off the most crucial items. Depending on what we decided in early scoping agreements, we can even help work through some high-impact issues, like bulk deleting content, suggesting rewrites, and fixing broken links.

We can also set up an ongoing content hygiene plan. While a dedicated content ROT analysis is a great way to identify and work through issues, an effective content plan should prevent ROT as much as possible and reduce the need for a large effort in the future. This might involve setting up policies, practices, and tools to guide future content management. We’ll help you find ways to see the bigger picture when updating or developing new content to make sure all pieces are accounted for. And when ROT falls through the cracks, you’ll have a plan to regularly review site content, setting ahead of time the when, what, and who.

One Piece in the Puzzle of Strong Content

As we continue to inspect the quality of your website and other digital properties, we can use this ROT analysis as a jumping off point. The initial audit may lead directly into a deeper content audit to evaluate URL paths, heading usage, performance metrics, reading level, and more. As we consider reworking, combining, and cutting entire pages, we may find the need to restructure your information architecture and taxonomy structures, in part or in whole, informed by research exercises like card sorts and tree tests. Depending on what we’ve found in the existing content and how it needs to change, we might suggest changes to your content model, adding, modifying, or removing content types and the relationships between them.

A content ROT analysis is a flexible and fruitful way to take a fresh look at your content ecosystem. If you need help getting started, let us know. We’d love to dig in with you!