Back to Blog

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.

What B2B Buyers Actually Ask AI Engines

Map your structural strategy to the queries you want to win. The B2B SaaS prompts AI engines see most often:

• Category lookups. "Best [project management / CRM / customer support / observability / analytics] tool 2026," "best [category] for [ICP segment]."
• Alternatives. "Alternatives to Notion," "what is like Linear but for product managers," "open-source alternatives to Datadog."
• Direct comparisons. "X vs Y," "Notion vs Coda for engineering teams," "Stripe vs Adyen pricing 2026."
• Stack-aware. "Customer support tool that integrates with HubSpot and Slack under $300 a month."
• Edge cases and limits. "What is the API rate limit on Linear," "does X support SSO on the basic tier," "how many users does Y allow on the team plan."
• Implementation. "How long does it take to onboard onto X," "best practices for setting up Y for a 50-person team."

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.

Five Parts of a Strong SaaS Foundation

1. SoftwareApplication or Product JSON-LD with depth

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.

2. Optional llms.txt summary

An llms.txt file at yourtool.com/llms.txt is an optional Markdown summary. Compatible tools may use it to discover selected public pages, but support is incomplete and Google does not use it. Read the llms.txt reference before deciding whether to publish one.

3. Comparison and alternatives pages that name competitors directly

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.

4. Deep public-facing documentation

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.

5. Third-party mentions where AI engines look

AI engines weight where else your product is talked about. The relevant places for B2B SaaS:

• Reddit (r/SaaS, r/startups, category-specific subs)
• Hacker News (Show HN posts, comments, Ask HN threads)
• G2 and Capterra (with detailed reviews, not just star ratings)
• Category-specific newsletters and blogs (Lenny's, Reforge, Indie Hackers, Startup Pirate, etc.)
• Public changelogs that get linked from third-party round-ups
• Open-source repos that mention or wrap your product

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.

The 8-Step AEO Checklist for B2B SaaS

1. Add SoftwareApplication JSON-LD with all 8 core fields on the homepage and pricing page. Validate with the Rich Results test.
2. Consider an optional llms.txt file. Publish one only if a short, maintained summary of key public pages is useful. It does not guarantee citations.
3. Check retrieval access in robots.txt. Confirm that OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, and PerplexityBot are not blocked. Decide training crawler access separately.
4. Build a real "Alternatives to [Competitor]" page for your top 2 to 4 competitors. Use a feature comparison table, explicit pricing, and a "when to pick them, when to pick us" section.
5. Build a real "X vs Y" comparison page for your two most common comparative queries. Same structure, but framed as direct comparison rather than alternatives list.
6. Make documentation public, sitemap-included, and linkable per concept. If it's gated, AI engines treat it as nonexistent.
7. Add a public changelog with dated entries. Changelog entries are a strong signal of an actively-maintained product. AI engines pull from them.
8. Add FAQ schema to a real visible FAQ section on the homepage and pricing page. Cover the questions buyers actually ask: free trial, refunds, security / SOC 2, SSO availability per tier, API limits, integrations.

Frequently Asked Questions

What is AEO for SaaS?

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.

What buyer queries do AI engines see for SaaS?

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.

What signals do AI engines weight most for SaaS?

The practical foundation includes accurate SoftwareApplication or Product JSON-LD, crawlable product and pricing pages, substantive comparison content, public documentation, and credible third-party coverage. llms.txt is an optional summary for compatible tools, not a ranking factor or citation guarantee.

Should our SaaS site name competitors directly?

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.

How does AEO for SaaS differ from AEO for local businesses?

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.

Will AEO replace SEO for our SaaS?

Start with crawlable product and pricing content plus accurate SoftwareApplication schema. Publish llms.txt only if a maintained summary of key public pages is useful. Support is incomplete, Google does not use it, and the file does not guarantee AI citations.

Where to Start

Run the homepage and pricing page through the free Meridian15 AEO audit. It runs 13 technical checks with no email gate. Start with crawlable product content and accurate SoftwareApplication JSON-LD, then build useful Alternatives and Comparison pages. Publish llms.txt only as an optional summary. Track citations separately because none of these changes guarantees inclusion in an answer. If the pipeline side needs work too, see our Calgary B2B SaaS marketing page.