AI Search Optimization for B2B Software: How Answer Engines Choose Who to Recommend

A property manager with 300 doors types one question into ChatGPT and gets two product names back, in order, with a table explaining when to pick each. No analyst ranked those vendors and no listicle was quoted whole. The engine ran a handful of searches, read a pile of pages, and wrote a shortlist.

AI search optimization, as we use the term here, is the work of understanding that process well enough to change where your software lands in it. This page is the pillar for the methodology guides, covering the engines the AI Shortlist Index is built to measure and the mechanism they share. It also covers why a buying question becomes a shortlist, and what the first runs show.

The commercial version of this material, for vendors who want the work done, lives at our services for property management software vendors.

What does the term mean here?

SEO is the query people type, so it stays in the title, but the work is different. Classic search optimization aims at a ranked list of links a person clicks. The target here is a sentence inside a generated answer, and the unit of success is being named.

That changes what you measure and what you build. You cannot see a position number for “maintenance coordination software for 300 doors” in ChatGPT. You can only ask the question, record who was named, and ask again on another day.

The scope on this site is narrow on purpose. Every example is B2B property-operations software: resident benefits platforms, access control, maintenance and vendor network software, and the other categories in the Index. The buyers are property managers and operators, and the questions name door counts, property types and the PMS already in place.

We do not cover consumer queries, local trades or anything where the buyer is a homeowner. The mechanism is the same across categories, but the sources differ by category. Generic advice about being visible to AI falls apart when the category is 30 vendors selling into 1,000-door portfolios.

Which engines does the Index measure?

The protocol covers five engines. ChatGPT is captured from its consumer app and Claude through the Anthropic API. The other three are queried through a documented API or a licensed data provider once their keys exist.

Only ChatGPT and Claude have runs today, and every stored run records which path it came from. The Index methodology carries the full capture record.

Engine	How the protocol captures it	What comes back	Status
ChatGPT	The app at chatgpt.com, one temporary chat per prompt set to Unpersonalized, default model, browser automation	Answer text, every link in the answer, the untouched capture, the capture time; the model that answered from October 2026	Measured
Claude	Anthropic API with web search, Claude Haiku 5.5	Answer text, the links shown in the answer, the search results it read, the model id	Measured from October 2026
Perplexity	Perplexity API, sonar model	Answer text, a citations list, search results with title, URL and date	Protocol, no runs
Gemini	Gemini API with Google Search grounding	Answer text, grounding chunks resolved to final URLs, the search queries it issued	Protocol, no runs
Google AI Overviews	Third-party capture of a US desktop results page	AI Overview text and its links, plus a flag for whether an Overview appeared	Protocol, no runs

Five engines, five capture paths. ChatGPT is read from the product buyers use; the other four return an answer and its sources through their own interfaces when they run.

Each engine has its own guide: Ranking in ChatGPT, Perplexity and its citation ordering, Google AI Overviews and AI Mode, and Gemini and search grounding. Claude joined the Index in October 2026 and has a guide of its own.

Two machine-layer guides sit under this page: which AI crawlers to allow in robots.txt and why your site, LinkedIn, G2 and Crunchbase must agree about your company.

How do answer engines choose sources?

Every engine in the table works the same way at the top level, and each vendor’s own documentation describes it. The model decides whether to search and runs one or more web queries. It picks a subset of the results to read, pulls facts out of those pages, and writes an answer with citations attached.

The four steps matter because a vendor can only influence some of them.

Retrieve

OpenAI’s web_search documentation says the model decides whether to search at all based on the prompt, and can issue several queries for one request. Google’s Search Central documentation describes the same behaviour in AI Overviews and AI Mode as “query fan-out”, issuing multiple related searches across subtopics.

A PM’s question about maintenance software for 300 doors becomes several searches: the category, the door count, the PMS integrations, pricing. You do not control the searches. You control whether your pages are indexed and readable when they run.

Select

Source selection is the step that decides who gets named. In a ChatGPT run captured through the OpenAI API on 3 September 2026, ChatGPT consulted 124 distinct URLs to answer a single maintenance prompt and cited six of them inline. That run was retired from the edition when capture moved to the app and is kept in the archive.

The gap between consulted and cited is where a vendor’s position gets decided. On ChatGPT that gap is now unobservable, because the app shows the links and not the pages behind them. A page can be read and shape the answer without ever appearing as a link.

We think the consulted list is the better leading indicator of who will be named next month, because inline citations lag the sources the model has already been reading. We will test that against later editions.

Extract

Extraction is where the engine turns pages into facts: a vendor’s stated integrations, a per-unit price, a minimum portfolio size. In the real run, ChatGPT pulled Property Meld’s published per-unit pricing and its list of PMS integrations from propertymeld.com pages and quoted them in the answer.

Pages that state those facts plainly get extracted. Pages that hide them behind a demo form give the model nothing to quote, and in a buying answer that is a disadvantage.

Synthesize

Synthesis is the final write-up: an ordered list, a comparison table, a recommendation with conditions. Position within that answer is a metric the Index records; a position score of 1.0 means always named first. Vendors tend to fixate on synthesis because it is the part they can see, and almost all of the influence a vendor has sits two steps earlier.

Why does a buyer’s question produce a shortlist?

The prompts in the Index library are written the way a property manager asks: first person, one question, a real portfolio detail. “What’s the best maintenance coordination software for a property management company with around 300 doors?” is prompt mvn-best-01 in the public prompt library. It has no vendor names in it.

It is a buying question, and buying questions resolve to product names because that is what a helpful answer to a buying question looks like.

What one prompt returned

Asked that prompt on 3 September 2026, ChatGPT named Property Meld first, framed as the default pick. Latchel came second, framed as the option for operators who want after-hours calls and triage handled as a service.

Asked again from the app in September 2026, the capture the edition now uses, it named Property Meld first and Latchel second once more, then Lula, MaintainX and UpKeep.

The same answer pointed at AppFolio, Buildium and Rentvine as the route for a company willing to replace its whole property management system. The Index does not score those, because they are core PMS platforms, not maintenance-category vendors. The answer was a shortlist with conditions, which is what a good salesperson would give too.

What shapes the answer

Two things drive the shape of that answer. The door count is a filter. A vendor whose own site says it suits portfolios over 100 units matches a 300-door question, and a vendor with no stated fit does not.

The PMS is a filter too; a PM on Buildium wants a tool that integrates with Buildium, and the engine will read integration pages to check.

The prompt library varies both across its 25 prompts per category, so the Index can see whether the shortlist changes when the portfolio changes. The Index category page for maintenance and vendor network software has the current table.

What do the runs say about sources?

The 2026-09 edition holds 25 ChatGPT app captures per category, one per prompt. The archive holds one retired API run of the 300-door prompt, which is the only run whose consulted list is visible. Neither is a full dataset, and the API run is a worked example of the mechanism whose source map is its most useful part.

Of the 124 URLs consulted, reddit.com accounted for 38, appfolio.com for 16 and buildium.com for 12. The two vendors named, Property Meld and Latchel, contributed four consulted URLs each from their own domains. The six inline citations all went to vendor-owned pages: propertymeld.com twice, appfolio.com, buildium.com, latchel.com and rentvine.com.

Read those two sentences together. Our reading of the run file is that the engine did its category research on a forum and on the two largest PMS vendors’ content. It then cited the product sites when it needed a fact to quote.

What the app captures show

In the maintenance category’s 25 app captures, the links in the answers went mostly to vendor sites. The top three domains were latchel.com, propertymeld.com and lula.life, with reddit.com at 6 of 184 citations. The app shows only the second half of that process, which is why its source maps are vendor-heavy.

From that pattern we infer that a maintenance vendor’s route into a ChatGPT answer runs through r/PropertyManagement threads and the PMS marketplaces as much as through its own site. We would want three runs on separate days and the other three engines before calling it a rule. The protocol’s three runs per prompt per engine exist to stop us over-reading one answer.

What should a vendor do about it?

The order below follows the mechanism, not the marketing calendar.

Be present on the pages the engines consult

Given the consulted list, a maintenance vendor absent from the PMS marketplaces and never mentioned in forum threads is invisible at the retrieval step, before its own site is read.

Marketplace listings are usually free. Forum presence cannot be manufactured, but a vendor can make sure its name, category and integrations are stated the same way everywhere a PM might repeat them.

Make your own pages extractable

In the real run the answer quoted price per unit, minimum portfolio size, integrations by PMS name, and what the product does that the PMS’s built-in work orders do not. State each on a crawlable page in plain text.

The structured data guide covers the schema that helps machines confirm those facts. The llms.txt guide covers the site map file and what it did and did not change on this site.

Keep the entity consistent

A vendor called one thing on LinkedIn, another on G2 and a third on its own pricing page is harder to extract and easier to skip. The Index’s own extractor matches canonical names and listed aliases, and engines have the same problem at larger scale.

Then measure, monthly, with the same prompts

The AI visibility guide defines the metrics the Index publishes: mention rate, position score, consistency across runs, engine spread, and source dependency. A vendor that tracks only its own site’s traffic will not see any of this move.

Limits, and what changes month to month

ChatGPT is captured from the app itself, with memory off and the chat set to Unpersonalized, so it measures an unpersonalized baseline rather than any one buyer’s account. The protocol reads the other engines through an API or a licensed provider, which is the closest repeatable proxy for their consumer apps and not the same thing.

What changes month to month

Engines change models without notice. Where a capture records a model identifier it is stored per run, because month-to-month movement in who gets named can reflect a model change rather than anything a vendor did. The retired September API run returned gpt-5.5-2026-04-23; September app captures carry no model id, and captures from October 2026 on record it from the conversation data.

Engines are non-deterministic. The same prompt on the same day can produce a different shortlist. Three runs and a published consistency metric make the variance visible without removing it, and any single answer, including the one quoted on this page, is one draw.

Coverage is US-only and unpersonalized. An engine without runs in an edition is excluded from the denominators rather than filled with zeros, and the September edition’s numbers come from ChatGPT. The protocol records a results page with no AI Overview as “no AI Overview”, not as a zero.

The source map is what we expect to change first. Our hypothesis is that forum and marketplace domains will stay near the top of the wider source lists Perplexity and Gemini return. The domains engines link will shift toward whichever vendors publish the most quotable pricing and integration pages.

The first edition with those engines is the test. Adapter changes are logged in the Index changelog.

Where to go next

Start with the engine your buyers use most. Ranking in ChatGPT covers what the links in an answer leave out and the September run in detail.

The Perplexity citation guide covers the sonar model, dated search results and citation order. The AI Overviews guide covers the results-page capture and query fan-out, and the Gemini grounding guide covers Google Search grounding.

The measurement framework is at AI visibility, the Index’s own method at how we measure AI recommendations, and the site’s own scorecard against these guides at the reference implementation. Everything on this page traces back to the WebPossible home page and the Index it publishes.

Changelog

• 2026-10-28: Reformatted with a short answer, question headings, one subsection per mechanism step and an FAQ. The engine table now carries a status column: only ChatGPT is measured, and the other three are protocol. Removed a stale note about Perplexity’s API deprecation date.
• 2026-09-26: The September figures now cite the 25 ChatGPT app captures per category; the API run of 3 September 2026 is described as retired from the edition and archived.
• 2026-09-19: ChatGPT capture moved from the OpenAI Responses API to the app at chatgpt.com. The engine table, the model-identifier paragraph and the source-map hypothesis were rewritten to match. The 2026-09 ChatGPT figures are kept and labeled as the API capture of 3 September 2026.
• 2026-09-03: Rebuilt for the AI Shortlist Index scope. Rescoped to B2B property-operations software, added the four-engine capture table, the retrieve-select-extract-synthesize mechanism, and the source facts from the 2026-09 ChatGPT run.
• 2026-06-10: First published as a general AI search optimization guide.