AEO · SaaS · B2B
How B2B tools get recommended by ChatGPT in 2026.
The short answer. B2B buyers ask ChatGPT, Perplexity, and Google AI Overviews for tool recommendations now. AI engines pick which SaaS to cite based on five signals: SoftwareApplication or Product JSON-LD with depth, an llms.txt file at the root, comparison and alternatives pages that name competitors directly, deep public-facing documentation, and third-party mentions on Reddit, Hacker News, G2, and Capterra. Most B2B SaaS marketing sites optimize for the demo CTA but ship none of the structural pieces. The gap is wide and the fix is well-defined.
If you sell B2B SaaS, your buyer journey changed in the last 18 months and your marketing site probably did not. Fifteen years ago a buyer typed a category into Google. Five years ago they searched for comparison articles. Today, increasingly, they paste a sentence into ChatGPT: "What's the best customer support tool for a 12-person startup that uses HubSpot and needs Slack integration under $300/month?" The AI returns three to five named tools with one-line summaries. Whichever tools get cited get the meeting. Whichever do not are invisible.
This is not a theoretical shift. ChatGPT alone reports more than 800 million weekly active users and a substantial fraction of those queries are commercial discovery. Perplexity, the most aggressive citation-first model, has crossed 30 million active users with a heavy B2B skew. Google AI Overviews now appear above the blue links on roughly 60 percent of B2B-flavored queries in North America. The buyer who used to read your homepage now reads an AI's summary of three sites that may or may not include yours.
The optimization for this new buyer journey is called AEO (Answer Engine Optimization). For B2B SaaS specifically, the playbook is structural and well-defined. Most companies have not done the work. This is what to do.
Map your structural strategy to the queries you want to win. The B2B SaaS prompts AI engines see most often:
Notice the shift from category-level questions to constraint-loaded questions. The AI engine's job is to filter a long list down to a recommendation. Your job is to make sure your product is in the candidate set when it does.
Schema.org's SoftwareApplication type is the canonical machine-readable container for SaaS. The deep version includes name, applicationCategory, operatingSystem, offers (with pricing tiers), aggregateRating, review, featureList, and softwareRequirements. The thin version (which most SaaS sites ship) just has name and url. The thin version gets you nothing in AI Overviews; the deep version gets you correctly summarized when an AI cites you. If you sell to procurement, the additional Offer structures with explicit pricing tiers also drive the "tool under $X" filter queries.
An llms.txt file at yourtool.com/llms.txt tells AI engines what your product does, who it is for, and which pages matter. For a B2B SaaS, the file should declare product category, ICP segment, key features (3 to 5), pricing tiers, integration list, links to docs / pricing / changelog / case studies, and a one-paragraph product description. We have a full guide on llms.txt structure. This file alone is one of the cheapest, fastest, and most-leveraged AEO fixes a SaaS company can make.
This is where most B2B SaaS marketing teams get squeamish. AI engines pull comparison answers from sites that explicitly name competitors. A fair, well-structured "Linear vs Jira" page or "alternatives to Notion" page will get cited every time buyers ask comparative questions. Refusing to name competitors keeps you out of one of the highest-converting query classes that exists. The trick is to write these pages honestly: a side-by-side feature table, an explicit "when to pick them, when to pick us" section, and a price comparison. AI engines reward this structure because it gives them clean fields to summarize.
If your docs require a login or a search box that hides URLs from crawlers, AI engines cannot read them. They cannot answer "what is the API rate limit on X" because they cannot see X's docs. Public, indexable, well-linked documentation is the strongest E-E-A-T signal a SaaS can ship: it proves the product is real, mature, and well-supported. Use real URLs per concept, link from your homepage to the docs, ship a sitemap that includes them, and resist the temptation to gate them behind a login.
AI engines weight where else your product is talked about. The relevant places for B2B SaaS:
You cannot fake these overnight. You can earn them with PR, Show HN launches, deliberate community building, and a category-specific changelog that is genuinely interesting.
Allow: rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, anthropic-ai. Sites that ambiguously block AI crawlers (especially via overly aggressive Cloudflare rules) lose every AEO signal.AEO (Answer Engine Optimization) for SaaS is the practice of structuring product, comparison, and documentation pages so AI engines like ChatGPT, Perplexity, Google AI Overviews, and Claude cite the product when buyers ask for tool recommendations. It is the equivalent of SEO for the new buyer journey, where the buyer asks an AI before opening a Google tab.
The most common are: best [category] tool 2026, X vs Y comparison, alternatives to [competitor], cheapest [category] tool with [specific feature], best [category] for startups under 10 people, what is the API limit on X, and how does X handle [edge case]. Comparison and alternative-to queries are particularly heavy because AI engines have to assemble a recommendation list, which means citing several sources.
Five signals: (1) SoftwareApplication or Product JSON-LD with depth (pricing, features, system requirements, applicationCategory), (2) llms.txt at the root with declared product category, ICP, key URLs, (3) substantive comparison and alternatives pages that name competitors directly, (4) deep public-facing documentation that AI engines can crawl (not gated behind a login wall), and (5) third-party mentions on Reddit, Hacker News, G2, Capterra, and category-specific blogs. Reviews matter but as a secondary signal.
Yes. AI engines pull comparison answers from sites that explicitly name competitors. A page titled X vs Y with a fair side-by-side feature table will get cited when buyers ask comparative questions, even ones the page does not directly answer. Refusing to name competitors keeps you out of the comparison query class entirely, which is one of the highest-converting buyer-stage queries that exists.
Local AEO weights LocalBusiness schema, address, opening hours, neighborhood mentions. SaaS AEO weights SoftwareApplication schema, pricing structure, integrations, public docs, and competitor comparison content. Local AEO is mostly about getting cited for one geography. SaaS AEO is about getting cited across category lists, alternatives lists, and feature-specific queries that have no geographic component.
No. They reinforce each other. Most SaaS-relevant Google queries now show an AI Overview at the top, and the same content depth that earns AI citations also earns Google rankings. Treat AEO as the layer on top of strong SEO, not the replacement. If your product pages already rank, optimizing schema and adding llms.txt is incremental work for outsized AI-citation upside.
Run your homepage and pricing page through the free Meridian15 AEO Audit. It grades 14 signals in 30 seconds, no email gate, and tells you exactly which structural pieces are missing. From the audit, prioritize llms.txt and SoftwareApplication JSON-LD first; these are the two highest-leverage fixes for SaaS specifically. From there, build out the Alternatives and Comparison pages over the next two sprints. The companies that ship this stack of structural work in 2026 will be the ones AI engines cite for the rest of the decade.
Get cited, not just ranked.
Same audit we run for B2B SaaS clients. 14 signals, no email gate. Find the gaps before your competitor does.
Run the Audit