On April 14, 2026, HubSpot held its Spring Spotlight event and announced two things at once.
The first was a new product called HubSpot AEO (Answer Engine Optimization), $50 per month standalone or bundled into Marketing Hub Pro and Enterprise (HubSpot, April 2026). The pitch: AI engines like ChatGPT, Gemini, and Perplexity are reshaping how buyers research, your site needs to be visible to them, and HubSpot’s new tool will help you get cited.
The second was the supporting statistic the marketing press picked up immediately. According to HubSpot’s own data, organic search traffic across its customer base is down 27% year-over-year. The framing in every recap since: AEO is no longer optional.
We spent 16 years as a HubSpot partner and completed 2,000+ projects on the platform. So when HubSpot launches a product on the back of an organic-traffic collapse, we do what most of the marketing press hasn’t done yet. We look up what happened to HubSpot’s own organic traffic.
It’s worse. Roughly 81% worse.
That isn’t “AI is eating search.” HubSpot lost that traffic because Google decided the content playbook HubSpot pioneered, pumping out high-volume, loosely related blog posts to catch top-of-funnel search, no longer deserves to rank. The old play simply stopped working. And now the company that built that play is selling its customers a tool to fix a problem the tool doesn’t actually solve.
That’s the most expensive sleight of hand in B2B software right now. Two soft numbers prop up HubSpot’s pitch; one much bigger number explains what really happened to their traffic, and to yours. Let’s take them in order.
HubSpot’s AEO launch buried the bigger number
The Spring Spotlight announcement is structured around a clean narrative: organic traffic is collapsing, AI search is the new channel, HubSpot AEO is the answer. The 27% figure (HubSpot, April 2026) anchors the urgency. The footnote claims AI referral traffic has “tripled” over 13 months. Read past the headline and both numbers soften:
The 27% is HubSpot’s proprietary data presented as a marketing announcement, not an audited industry measurement. HubSpot has not published the methodology. There’s no sample size, no definition of “organic traffic,” no breakdown by company segment or industry, no weighting disclosure. The number is asterisked in HubSpot’s own press materials because it is an internal metric, not an external one.
The “tripled” figure comes from one practitioner, Jason Tabeling, Head of Solutions at a marketing agency called Further, writing in Search Engine Land (February 2026). His data covers his agency’s clients across 13 months. Number of clients, industries, sizes: undisclosed. The figure HubSpot turned into “AI referral traffic tripled” is buried under a much larger one in Tabeling’s own analysis. LLM referrals account for less than 2% of total referral traffic across the dataset, with a per-client range of 0.15% to 1.5%. “Tripled” is a tiny number multiplied by three: roughly half a percent of traffic becoming one and a half.
Search Engine Land is owned by Semrush. The piece runs inline Semrush promotions. The category, “AEO tooling,” is commercially adjacent to the publication. None of this makes the data fabricated. All of it should change how seriously you take the urgency framing.
HubSpot stitched two soft numbers into a hard pitch. Customer organic traffic is collapsing, AI is the cause, we sell the fix. Two of those three claims don’t hold up.
Why did HubSpot’s own blog traffic collapse?
This is the question HubSpot’s announcement carefully sidesteps. Between early 2024 and early 2025, blog.hubspot.com lost roughly 76 to 81 percent of its organic traffic, depending on which SEO tool you trust.
Ahrefs measured the blog dropping from approximately 10 million monthly organic visits at the start of 2024 to under 1.9 million by January 2025, an 81% decline (Surfer SEO analysis, January 2025). Semrush put the same blog at 14.8 million in January 2024 and 2.8 million a year later, also 81%. Sistrix’s Visibility Index showed a 76% year-over-year decline. Three independent tools, the same direction, the same magnitude.
The decline wasn’t gradual. It clustered around two specific dates: Google’s March 2024 Core and Spam updates, and Google’s December 2024 Core and Spam updates. Those updates explicitly targeted sites publishing content far outside their topical authority, and a related Site Reputation Abuse policy went after the exact tactic of using high-authority domains to rank for low-relevance, high-volume keywords.
HubSpot’s blog was the canonical example. Ryan Law of Ahrefs surfaced it. Chris Long’s analysis on LinkedIn (January 2025) added the kicker: 53% of HubSpot’s blog pages were under 2,000 words, and the highest-traffic content included pages on the shrug emoji, famous quotes about life, and how to write resignation letters.
That content has nothing to do with CRM software. It existed because the inbound playbook, the methodology HubSpot literally trademarked and built a multi-billion-dollar company on, said to capture top-of-funnel attention by publishing high-volume informational content adjacent to your buyer’s interests. For fifteen years it worked. Google ranked the pages. Buyers landed on the blog. A small percentage converted into HubSpot trials. The flywheel spun.
In 2024, Google stopped rewarding the play.
HubSpot didn’t get hit by AI. HubSpot got hit by Google deciding their content didn’t earn the rankings it had been getting.
There is no AEO tool that fixes that. There is no schema you can add to a shrug-emoji article that makes it relevant to a CRM-software search query. The only fix is structural. Stop publishing the wide, shallow, persona-keyed informational content the 2024 updates targeted. That isn’t an AEO problem. It’s a content-strategy problem on every platform, AI or not.
The lost traffic didn’t evaporate into AI chatbots, either. As Ahrefs founder Tim Soulo pointed out in the Surfer SEO analysis, the keywords HubSpot lost are still ranking. They moved to other websites that filled the gap. Canva benefited heavily because many of the lost queries were image-related. Other sites picked up the rest. The traffic is still there. It just isn’t coming to HubSpot anymore.
HubSpot’s response was to rename the annual conference (see our piece on the UNBOUND rebrand) and launch an AEO product.
The 27% drop is the same story, one level down
HubSpot’s customers are losing organic traffic for the same reason HubSpot is. They were taught to run the inbound playbook. The playbook stopped working.
Walk through the typical HubSpot customer’s content engine. A mid-market B2B company on Marketing Hub Enterprise has a blog with anywhere from 200 to 2,000+ posts, the majority published between 2018 and 2023, the majority targeting informational keywords loosely related to their products. The persona-led brief. The keyword cluster. The 1,500-word how-to with a bottom-of-funnel CTA. That format wasn’t invented by HubSpot, but HubSpot Academy taught a generation of marketers to produce it at scale, and HubSpot’s content tools made the production cheap.
Google’s 2024 updates didn’t only punish HubSpot.com. They punished the entire pattern. Sites publishing high volumes of medium-depth, persona-targeted, informational content saw the same ranking compression. Sometimes 30%, sometimes 50%, sometimes 80%. The Surfer SEO analysis specifically called out that blog.hubspot.com was the canary, not the exception. Every site running the same playbook was vulnerable.
A 27% aggregate decline across HubSpot’s customer base isn’t a referendum on AI. It’s a referendum on a content strategy Google decided was no longer earning its keep. HubSpot’s customers got hit because they ran HubSpot’s playbook. The playbook is the problem, not the absence of an AEO subscription.
AI Overviews compound the damage. Google now answers a meaningful slice of informational queries directly in the search results, which compresses click-through rates on exactly the type of top-of-funnel content HubSpot customers tend to publish heavily. But AI Overviews are a Google product, not an OpenAI product. The mechanism draining traffic from HubSpot customer blogs is Google’s own answer engine, not ChatGPT’s. The fix is the same as the fix for the 2024 core updates. Write fewer, deeper, more authoritative pieces in tighter topic clusters. Stop chasing high-volume keywords adjacent to your expertise.
You can do all of that on HubSpot. You can also do all of it on a platform that doesn’t fight you at every step.
Why is AEO on HubSpot CMS so much harder than it sounds?
AEO has technical requirements any modern site can meet trivially. Product and content pages need visible FAQ sections that answer real buyer questions, and every page template should generate structured schema on its own as basic search hygiene. Pages need to load quickly, above all for the buyers who click through from an AI answer. Copy should be written as questions and answers that match the natural-language queries buyers type into AI engines. Many teams also publish an llms.txt file at the domain root, a plain-text summary of the site for AI tools. It’s cheap housekeeping rather than a lever: Google says its search ignores the file, and Ahrefs found that 97% of the llms.txt files on the 137,000 sites it studied got no requests at all in May 2026.
None of that is exotic. All of it is painful on HubSpot CMS.
Schema implementation requires a custom module or a code-injection workaround per page type. Even FAQ markup, which a modern template generates for free from the questions already on the page, has to be wired into a custom field group inside a custom module, then surfaced as a JSON-LD block in the template. Manageable for one page, slow across a content portfolio. Deploying llms.txt at the root of a HubSpot-hosted domain isn’t a setting. It requires either a code snippet that conditionally serves a text response, a hosted-file workaround, or routing the file through external infrastructure entirely. Sitemap behavior on HubSpot is opinionated and not always under your control.
Then there’s the page-load problem, and this is the one nobody at HubSpot wants to talk about.
HubSpot CMS adds its own code to every page it hosts. Every template has to include HubSpot’s standard header and footer tags, and the footer tag loads the tracking code along with whatever chat, form, and analytics scripts the account turns on. You can filter that output with template workarounds, but HubSpot doesn’t support it. HTTP Archive, which tests millions of live websites every month, shows the result. On a phone, the median HubSpot CMS site sends about 1 MB of JavaScript per page and scores 56 on Lighthouse, Google’s own speed test, which counts 90 and above as good. Sites built with Astro, a framework that sends finished HTML, come in at 399 KB of JavaScript and a score of 70 (September 2026). Neither median clears 90, so a static site isn’t fast by default. But the HubSpot gap starts with code you aren’t allowed to remove, and that part isn’t a tuning problem. It’s the platform.
Speed won’t earn you AI citations. A slow page loses the buyers those citations send you.
That gap costs you buyers far more than it costs you AI coverage. Google does crawl less when a server slows down, but its own documentation says crawl budget is mainly a concern for very large sites: roughly a million pages that change weekly, or 10,000 that change daily. A mid-market HubSpot site is nowhere near that. Speed doesn’t buy citations either. When SALT.agency, a technical SEO firm, studied 107,352 pages that appear in Google’s AI Overviews and AI Mode, better Core Web Vitals scores (Google’s page-experience measures) didn’t reliably earn more AI visibility, though the slowest pages did worse (Search Engine Land, January 2026). Speed is a floor, not a lever. Speed can cost you an AI answer directly in one case, a live fetch. When an engine fetches your page while a user waits, it won’t wait long, and a slow, script-heavy response can be dropped before it’s read. Where a slow page really hurts is with the people an AI answer sends you: Google’s own 2016 data found that 53% of mobile visits are abandoned when a site takes more than three seconds to load.
The companies winning AEO are not the ones who bought a $50-per-month dashboard. They are the ones whose pages load fast for every visitor, whose templates emit schema on every page automatically, whose teams ship a new FAQ-rich comparison article in hours rather than file a developer ticket and wait two weeks. That capability is an architectural property, not a feature.
For the full breakdown of what makes a site visible to AI engines (and what makes it invisible), see our audit-driven piece on AI website performance. It’s the same diagnosis, walked through with a specific client portrait.
”AI is eating search” is the wrong diagnosis
Be careful here, because this is where the marketing press has been the loosest with the framing.
AI referral traffic is growing. That isn’t contested. Tabeling’s data shows roughly 3x growth across his agency’s clients between January and December 2025. Other practitioner reports tell similar stories. ChatGPT, Perplexity, and Gemini collectively send real traffic to real sites, and the share is rising month over month.
The share is also small. Tabeling’s own number: LLM referrals account for less than 2% of total referral traffic, with a per-client range of 0.15% to 1.5%. SEO and direct traffic remain roughly 25 times larger. A category that small doesn’t support the framing that “AEO is no longer optional,” no matter what its year-over-year growth rate looks like.
The TechTarget coverage of the HubSpot AEO launch (Don Fluckinger, April 14, 2026) is more measured than the newsletter recaps. The article quotes HubSpot’s own executive saying “SEO is not going away.” It notes that AEO and SEO will coexist. It doesn’t repeat the urgency frame. But it does accept the premise that “marketers have seen website traffic drop since OpenAI launched ChatGPT in late 2022” as established fact. That causal link is contested. The 2024 traffic drops have been attributed to Google’s core updates, AI Overviews, zero-click search, and ChatGPT, and the relative weight of each is unsettled. Treating the AI thesis as proven is convenient for selling AEO tools. It isn’t convenient for diagnosing why the traffic actually dropped.
The honest read: AEO matters more than it did a year ago, and it will matter more again a year from now. It doesn’t matter enough today to explain a 27% decline in customer organic traffic on its own. The real cause is Google’s 2024 algorithm shifts plus the underlying content strategy those shifts targeted. HubSpot’s customers got hit because they ran the playbook HubSpot taught them. Selling them a $50/month AEO tool addresses a real but smaller problem and leaves the larger one untouched.
What actually moves the needle on AEO
If you read our piece on AI website performance, most of this will be familiar. AEO success comes down to four levers, and the platform you build on decides whether you can actually pull them:
- Page speed. Treat it as the floor. The slowest pages do worse in Google’s AI results, but a page that’s already fast won’t earn more citations by getting faster, so the biggest payoff is the buyers who stay on the page. On HubSpot CMS you tune around scripts the platform requires, while a static-rendered site starts without them.
- Answer-ready pages. AI engines quote the visible words on a page, so give them FAQ sections and question-led copy that state each answer plainly. Product, Article, and Organization schema should come from every page template as free hygiene rather than being added page by page. On a modern stack, that’s one component. On HubSpot, it’s a per-page custom module.
- Content velocity. The AI search landscape shifts monthly, and when it does you need to publish comparison content, refresh FAQ sections, and add schema in hours. Filing developer tickets against a proprietary CMS turns every adaptation into a four-week project.
- Topical authority. The one lever no tool can give you. Write deeper on the topics where you have actual expertise, and stop publishing the persona-led, keyword-clustered, 1,500-word inbound posts the 2024 Google updates punished. AI engines reward the same signals Google now does: deep, authoritative, citation-worthy content.
The HubSpot AEO product touches none of those four levers in a meaningful way. It’s a dashboard that tracks how your existing content appears in AI engines, surfaces competitor benchmarks, and offers prompt suggestions. The underlying site, the one HubSpot has been selling you for fifteen years, is unchanged. The platform that constrains your page speed, schema implementation, and content velocity is the same platform selling you the AEO bolt-on.
You’re paying for a thermometer when the patient has a structural problem. And the thermometer doesn’t have to be rented: you can track AEO today in GA4, your CRM and your server logs, with known limits and no dashboard to buy.
The architecture is the AEO strategy
Here’s the part HubSpot won’t say in a press release.
AEO is real. AI search is growing. Your content needs clear answers, fast loads, and topical depth to get cited. Every word of that is true.
It is also true that the proprietary CMS HubSpot has spent fifteen years selling is, architecturally, the worst possible foundation for that work. The platform fights you on schema, fights you on llms.txt, fights you on page speed, fights you on content velocity, and recently launched a $50-per-month AEO dashboard to make the friction feel like progress.
This is the Code Lock operating exactly as designed. The vendor benefits from the architectural problem. The customer pays to manage the symptom. The product roadmap depends on the customer never solving the underlying issue, because solving it would mean leaving.
If your organic traffic dropped 27% (or 50%, or 80%) in 2024, ask these four questions before you ask which AEO tool to buy:
What share of your blog content targets keywords adjacent to your expertise rather than core to it? That content is the highest priority to prune or rewrite. No AEO tool gives you topical authority you didn’t earn.
How fast do your pages load, honestly, on mobile? Run PageSpeed Insights. If your main content takes more than 2.5 seconds to appear (the LCP score Google grades you on), you’re below the floor, and fixing that comes before any AEO tool.
How long does it take to ship a new comparison article with an FAQ section and schema? If the answer involves a ticket queue, the platform is the strategy problem, not just an execution one.
If you left the platform tomorrow, would your work compound or evaporate? Content locked in HubSpot’s proprietary templating language (HubL) evaporates. Markdown content and standards-based components compound.
A $50/month AEO tool changes none of those answers. A different architecture changes all of them.
We’re publishing the full analysis of what companies actually pay for HubSpot. Get the report before anyone else.
The cure doesn’t match the diagnosis
HubSpot’s Spring 2026 Spotlight told a clean story. AI is changing search, organic traffic is dropping, HubSpot has the fix.
The truth is messier. Google changed search. The content strategy HubSpot pioneered stopped working. HubSpot’s own blog took the biggest hit because they ran the playbook hardest. HubSpot’s customers are running the same playbook on the same platform and getting the same result. The architecture that makes AEO hard is the same architecture that made the old inbound playbook profitable for HubSpot in the first place: proprietary templates, platform overhead, slow page loads, and a long ticket queue for any structural change.
Selling AEO as the fix is a marketing move, not a strategic one. The actual fix lives one layer down, in the question of what platform you build on and how fast that platform lets you adapt.
We left HubSpot after 16 years because the answer to that question kept getting worse (see why we left). The companies that win the next wave of search visibility will be the ones whose stack moves at the speed of search itself.
HubSpot is selling you a dashboard. The thing you actually need is a different foundation.
Want to see how your site actually performs on the four AEO levers? Get the free AI assessment for a 60-second read on your tech stack, page-load performance, and AI visibility. No sales pitch.
The research is free. So is the diagnosis. 60 seconds →