AI visibility for
SaaS.

For a query like 'best tool for customer feedback analytics', none of the four engines fetches a ranked list. Each assembles a shortlist from comparison and alternatives pages, third-party threads on Reddit and Hacker News, review-platform listings, and vendor documentation. AIRank samples all four — ChatGPT on Bing grounding, Claude on its first-party index, Perplexity on its own index, Google AI Mode on Google Search — every six hours, and the source mix stays remarkably stable inside a category.

SaaS is the one vertical with no safety guardrail in the way. Nothing filters a project-management recommendation the way medical or financial content is filtered, which means nothing protects incumbents either. What decides the shortlist is extractability and corroboration: whether your claim exists as a liftable sentence, and whether anyone other than you has repeated it.

The composition step is where most SaaS companies lose. The model allocates each named tool roughly one clause — a differentiator. If your site never states that differentiator in a single declarative sentence with your brand name in it, the model writes the clause itself from your homepage headline, which is usually a benefit statement that could describe nine competitors.

Three shapes sit at the decision point: 'best <category> for <segment>', '<competitor> alternatives', and '<competitor A> vs <competitor B>'. All three assume budget exists and a shortlist is being drawn. All three are winnable by writing, because the pages that answer them are pages your competitors have no incentive to write about you.

Pricing queries — 'how much does X cost for 50 seats' — also sit at the decision point and are decided mechanically: the model needs a number. Publish tiers and per-unit limits in HTML and you are eligible. Route everything to 'contact sales' and the answer gets built from a third-party review site's guess about your pricing, which is usually stale and rarely flattering.

Definitional queries — 'what is a customer data platform' — are research, not purchase, and they are already owned by review platforms and encyclopaedic sources with a decade of corroboration behind them. Winning one buys you a footnote in an answer where nobody is choosing a vendor. Treat them as brand hygiene at best.

Two shapes you should not chase at all. Brand-name queries always cite you and therefore measure nothing — AIRank's own methodology flags them as bad tracker inputs. And 'how do I do X in <competitor's product>' routes to that vendor's documentation by design, so pages you write about their API are accurate, expensive and never cited.

The leaders share one architectural decision: one idea per URL. Stripe's documentation splits every concept onto its own stable page with a complete example on it, so a retrieved chunk never depends on the page before it. Linear's feature pages state a specific capability in a declarative sentence rather than a benefit tagline. Both produce spans that survive being lifted out of context, which is the only property that matters at extraction time.

Notion's use-case directory works because there is a page whose H1 literally matches the query shape 'X for Y'. Vercel offers its documentation corpus pre-digested through llms.txt. PostHog outperforms its own link profile because its writing carries claims nobody else can make — extractability substituting for authority, which is exactly what the rubric predicts when 40% of the weight sits in the content pillar.

Three of those four moves cost engineering time, not budget. Split your documentation one concept per URL. Rewrite your top ten feature paragraphs into declarative sentences containing your brand name. Create one page per '<category> for <segment>' pair you actually serve. What is not reproducible is Stripe's referring-domain profile — and it does not need to be, because referring domains carry three points out of forty-seven.

Top-ten listicles on your own blog with yourself at number one. That page shape exists thousands of times over, so the claim-uniqueness check that carries four points scores near zero, and the ordering is transparently self-serving to any reader. In content marketing the format still earns links. In an answer engine it earns nothing.

Anything that lives inside the product. Interactive tours, in-app screenshots, Loom walkthroughs and gated sandboxes are invisible: the scanner uses the same Bingbot-class crawlers the answer engines use, and those cannot log in. SaaS teams routinely put their most differentiated material — the actual workflow — where no crawler will ever reach it.

Top-of-funnel definitional content, which was the standard B2B play for a decade. 'What is <category>' posts were built to catch a search that now terminates inside the model with no click and no citation attached. That budget belongs on comparison pages and documentation instead.

Link buying. Referring domains are worth three points in a forty-seven point rubric and authority as a whole is one pillar of four. A quarter of link budget moves a SaaS company less than one afternoon spent making the pricing page machine-readable.

These are the rows that separate an invisible B2B SaaS site from one the models reach for by default. Read across: find the leftmost column your site honestly sits in for each row, and the pattern tells you whether you have a content problem or a corroboration problem.

Fix the comparison-page row first. It is the only row that simultaneously adds extractable chunks, matches a query shape sitting at the decision point, and gives third parties something concrete to link to. The AI Score row is an outcome rather than an input — it moves when the other five do.