
Google AI Overviews now sit above organic results for many health queries. ChatGPT and Claude are also where people start when they look for a doctor, a fitness app or a telehealth option. Ranking on Google still matters. Getting named in an AI answer matters too.
We wanted to know whether the tech stack mattered. Specifically: do Next.js sites show up more often than WordPress sites in Generative Engine Optimization (GEO) answers?
So we ran a study. 99 health industry websites. 49 built on Next.js, 50 on WordPress. 25 real health queries. Three AI platforms. Here's what the data says.
The Headline Numbers
Next.js sites captured 70% of all AI citations across ChatGPT, Claude, and Google AI Overviews. Out of 163 total study site mentions, 114 went to Next.js sites and 49 went to WordPress.
But the gap goes deeper than raw counts:
81.6% of Next.js sites were cited by at least one AI platform. 48.0% of WordPress sites were cited by at least one AI platform. Next.js sites averaged 2.29 citations per site vs WordPress at 1.02.
That's not a marginal difference. Next.js sites were cited at nearly double the rate.
What the AI Platforms Actually Recommended
We asked all three platforms questions that real people ask every day , things like "what are the best telehealth platforms," "what apps help with anxiety and meditation," and "what are the best health wearables."
ChatGPT was the most selective, and the hardest for WordPress sites in this set. When someone asks ChatGPT for a recommendation, it usually names 5 to 7 brands and moves on. In our runs those names were mostly Next.js properties such as Peloton, Strava, Calm, Headspace, GoodRx, Equinox and Dexcom. WordPress sites in the study set rarely appeared. The companies ChatGPT named tend to invest in modern site architecture and strong off-site recognition.
Claude was the most generous with citations overall, mentioning 103 study sites across 25 queries , but even with a wider net, Next.js sites still dominated with 72% of mentions. WordPress sites that did get cited tended to be large publishers with massive content libraries. Smaller WordPress sites were almost entirely shut out.
Google AI Overviews showed the strongest skew of all. When the AI Overview panel appeared (we tested 10 queries), 78% of study site citations went to Next.js properties. WordPress sites struggled to break through even when they ranked well in traditional organic results. Google's AI clearly favors the kind of fast, well-structured sites that Next.js produces out of the box.
Why Next.js Sites Win in AI
We dug into the data to understand why this gap exists. It comes down to four things.
1. Next.js Powers the Brands AI Trusts
The companies building on Next.js in the health space tend to be the ones investing heavily in product, content, and brand. Think Healthline, GoodRx, Calm, Whoop, Peloton, Dexcom. These aren't small operations , they're category leaders with deep content libraries, millions of users, and strong brand signals across the web.
AI models learn from the internet's collective knowledge. When Healthline shows up in thousands of medical articles, Reddit threads, and "best of" lists, AI systems internalize that authority. When a local med spa has a WordPress site with good Yoast SEO scores but limited off-site presence, AI has far less signal to work with.
The takeaway: Next.js has become the default choice for ambitious, tech-forward health companies. That selection bias means the Next.js ecosystem is stacked with exactly the kind of brands AI engines prefer to cite.
2. WordPress's SEO Plugins Don't Help with AI
Here's the uncomfortable truth for WordPress loyalists. WordPress sites in our study actually had better traditional SEO scores than Next.js sites. WordPress averaged a 5.64 SEO score (out of 9) compared to 4.73 for Next.js. WordPress sites had more schema markup (1.42 average schema types vs 0.65), more Open Graph tags, and more Twitter cards , largely thanks to Yoast SEO doing the heavy lifting.
None of that translated into more AI citations. Not even close.
This exposes a fundamental problem with the WordPress approach to discoverability. Plugins like Yoast optimize for a search paradigm that's being replaced. Schema markup, meta descriptions, and structured data are table stakes for Google's organic results, but AI citation engines don't care about your Yoast score. They care about brand authority, content depth, and real-world recognition , signals that no plugin can fake.
If your GEO plan starts and ends with "install Yoast and add more schema," you are only covering classic search basics. Schema still helps Google. It did not close the AI citation gap in this study.
3. WordPress sites were slower in this set
Page speed is a user experience issue and it also shows up in how easy a site is to crawl. The average WordPress health site in our study loaded in 4 to 6 seconds on mobile. Next.js sites averaged under 2 seconds. That gap is large enough to matter for both visitors and crawlers.
Google has explicitly tied Core Web Vitals to ranking signals, and there's growing evidence that AI systems inherit those same biases. A slow site signals low investment, poor maintenance, and a worse user experience. WordPress's reliance on heavy themes, render-blocking plugins, and unoptimized PHP makes speed an uphill battle. Next.js ships fast by default , server-side rendering, automatic code splitting, image optimization, and edge caching are built into the framework, not bolted on as afterthoughts.
When AI engines evaluate which sites to cite, they're drawing from the same crawl data that penalizes slow pages in traditional search. WordPress sites carry that weight whether they know it or not.
4. Next.js Is Built for How AI Evaluates Sites
Next.js gives development teams capabilities that directly produce the kind of web presence AI engines favor: server-side rendering for fast, crawlable pages; API-driven content architectures that scale across channels; superior Core Web Vitals that improve user engagement; and the flexibility to build rich, interactive content experiences that keep visitors on-site longer.
WordPress, by contrast, fights against its own architecture to achieve these things. Plugin bloat tanks performance. PHP-rendered pages are slower to crawl. Theme constraints limit content flexibility. Every optimization requires another plugin, another workaround, another layer of technical debt.
Next.js sites in this set were faster and easier to keep structured. That does not replace brand authority or useful content, but it removes a common technical drag while you build those things.
What This Means for Your GEO Strategy
If you're a health industry brand thinking about AI visibility, here's what our data suggests:
If you are on WordPress: a migration will not create citations by itself. You still need clear content and real recognition. What the data suggests is that WordPress sites in this set started from a slower, harder-to-crawl place. If AI visibility is a priority, put a rebuild conversation on the calendar and weigh it against content and authority work you still need either way.
If you are building something new: Next.js is the stack we would start on for a health or therapy site that cares about speed and AI visibility. In this study, the companies that got named most often were overwhelmingly on Next.js. Stack choice is not the whole strategy, but starting on a fast, structured foundation saves you from fighting the platform later.
About This Study
This analysis is based on original research by Driftlss, testing 99 health industry websites across 25 standardized queries on ChatGPT, Claude and Google AI Overviews. Sites were classified by CMS platform, brand authority tier and SEO/schema markup level. Complete data and methodology are available in the companion analysis spreadsheets.
Want to see how your practice shows up in AI answers? Contact Driftlss and we will scope a GEO review around your site. Pricing is a custom quote after scoping.


