How to Rank in ChatGPT: Getting Your Software Named in the Answer

You rank in ChatGPT when a property manager asks it which software to use and your product is in the answer. ChatGPT runs several searches, reads far more pages than it links, and writes a shortlist with a few links attached. This guide covers how it picks those sources, what it quotes from a vendor page, and what a property-operations vendor can do about it.

The evidence comes from the AI Shortlist Index, which captures ChatGPT’s answers to buyer prompts every month. The commercial side, for one vendor’s row, is on getting your software recommended by ChatGPT.

What does it mean to rank in ChatGPT?

It means your name appears in the answer. There is no results page and no position one. A buyer asks for the best maintenance coordination software for 300 doors and gets three or four names, a sentence on each, and sometimes a table.

The useful measure is how often you appear across many answers to the same prompt. In the September 2026 edition of the Index, ChatGPT named Property Meld in 91% of maintenance-software runs, Lula in 65% and Latchel in 64%. Those are mention rates.

The AI visibility guide defines mention rate, position score and consistency so you can run the same measurement on your own prompts. A link is a bonus, not the goal. A vendor can appear in every run and be linked in none, and that vendor is still on the shortlist.

How does ChatGPT pick sources for a software recommendation?

It searches, opens pages, pulls out facts, and writes. OpenAI’s documentation for its web search tool describes the model issuing searches, opening result pages, and returning an answer with citations to the pages it used. One buyer question becomes several searches: listicles, forum threads about maintenance coordination, and the pricing and integration pages of the products those threads mention.

The pages it links are a small part of what it read. The Index could see the full list once, when ChatGPT was captured through the API in September 2026. In that run, ChatGPT consulted 124 distinct URLs for a maintenance prompt and attached six inline citations.

All six citations pointed at vendor-owned pages: two on propertymeld.com, one each on appfolio.com, buildium.com, latchel.com and rentvine.com. The consulted list looked nothing like the links. Of the 124 URLs, 38 were on reddit.com, 16 on appfolio.com, 12 on buildium.com, five on AppFolio’s investor relations site, and four each on propertymeld.com and latchel.com.

A vendor reading the six links would conclude that ChatGPT reads product sites. The 124 say it reads Reddit and the two big PMS vendors’ blogs first, then goes to product sites for facts to quote. The second reading is the useful one.

The consumer app no longer shows that list. ChatGPT at chatgpt.com, where buyers ask, discloses only the links in the answer. The split is still documented on the API side, and the app simply shows less of it.

Which pages does ChatGPT read before it answers?

Four kinds, in roughly this order of influence, judging by the one run where the whole list was visible.

1. Forum threads. Reddit threads in r/PropertyManagement and the maintenance subreddits, where managers name the products they use and complain about the ones they left.
2. The PMS vendors’ own content. AppFolio and Buildium content made up 28 of the 124 consulted URLs, including their “best maintenance software” posts and marketplace pages. A vendor listed in those marketplaces is therefore read even when the prompt never mentions the PMS.
3. Listicles and trade coverage. The “best X software” pages that rank in ordinary search, and the trade publications that cover the category.
4. Vendor pages with facts on them. Pricing, integrations, FAQ. These are the pages that get quoted, and therefore linked.

The live version of this list, per category and per month, is the Index source map. The maintenance category’s is at its source map page.

In the September app captures, reddit.com accounted for 6 of 184 citations in the maintenance category, and the links went mostly to vendor sites. Citations and consulted pages are different lists. A source map built from citations alone undercounts the forums.

What does ChatGPT want from your vendor page?

Five facts, stated as text a crawler can read without running a script. Read across the captured run, these did all the work.

• Price per unit per month, or at least a starting price with its conditions.
• The minimum or ideal portfolio size.
• Which PMS platforms the product integrates with, by name, in text rather than logos.
• What the product does that the built-in work-order screen in AppFolio or Buildium does not.
• Whether you offer a service layer, such as after-hours triage and dispatch, or software only.

Look at what the answer quoted. For Property Meld it cited the published per-unit price for two tiers and computed a monthly cost for 300 doors. It listed six PMS integrations by name and quoted the vendor’s own statement that it suits portfolios over 100 units.

For Latchel it noted that pricing is not published and that prospects are sent to a demo call. One vendor gave the model numbers and the other gave it a form, and the answer said so.

From that run we infer that a vendor stating the five facts in plain text is more likely to be quoted than one saving them for a sales call. The model cited exactly the pages where the facts were stated. The cited Property Meld pages were an integration partners page and an FAQ.

What breaks extraction, with a before-and-after rewrite of one paragraph, is in how AI engines read a vendor page.

How do you get into the pages ChatGPT reads?

In order of where the mechanism gives you a say.

Your own pages first

State the five facts. Put the integration list on a page with the PMS names in text, and put pricing on a page, even as a starting point with conditions.

Give each product one clear name and use it identically on your site, your PMS marketplace listing and your review-site profiles. The entity consistency guide covers why one name matters to a model connecting mentions.

PMS marketplaces

A listing in the AppFolio, Buildium, Yardi or Rent Manager marketplace puts you on pages the model reads at the retrieval step. In the captured run those marketplace pages were among the 28 PMS-vendor URLs consulted. This is the cheapest source placement in the category.

Forums and threads

You cannot post your way into Reddit, and a vendor account that tries gets flagged. What you can do is make sure the name a manager uses in a thread matches the one on your site. The thread’s question should also be answered on a page of yours the model can find afterward.

Comparison and alternatives pages

Pages with vendors down a column and attributes across give the model the shape it produces. Third-party comparison pages get pulled into answers because they have already done the extraction. The Index’s own comparison pages exist for that reason, and vendor-supplied facts on them are labeled.

Do schema, llms.txt and robots.txt matter?

Text first, then markup. The quoted pages in the captured run were plain HTML. Structured data confirms what the text says and helps a model attach your name to a category and a set of integrations; the structured data guide has the templates.

Let the crawlers in. OpenAI documents separate user agents: OAI-SearchBot for the search results that feed ChatGPT answers, ChatGPT-User for pages a user’s question fetches live, and GPTBot for training data. Blocking GPTBot to keep your pages out of training still leaves a live fetch working, as long as OAI-SearchBot and ChatGPT-User are allowed.

The AI crawlers and robots.txt guide has the exact lines, and llms.txt covers the curated index file some engines read. None of this replaces a fact on a page. A perfect robots.txt in front of a pricing page that says “contact us” produces a well-crawled page with nothing to quote.

How do you measure your share of ChatGPT answers?

Ask the same prompts every month and count. A prompt set that reads like real buyers, run several times per prompt on separate days, gives you mention rate, average position and consistency per vendor. The share of answer guide sets out the framework, and the Index’s public prompt library is a prompt set you can copy.

Say the result as a fraction. “Named in 21 of 23 runs”, Property Meld’s September figure, is a claim a buyer can check. “Recommended by ChatGPT” is a screenshot.

The same prompt on the same model can produce a different shortlist on a different day. That is why the Index publishes a consistency metric per vendor instead of hiding the variance.

The Index does this for 20 property-ops categories and publishes the rows. The AI Visibility Audit applies the same prompts to one vendor’s row and names the cause behind it. How the captures are collected, run counts and metric definitions are on the Index methodology page.

What changes month to month?

The model. OpenAI changes the consumer default without a schedule, and a row can move because the model changed while nothing on the web did. The Index records the model slug per answer where the app discloses it and logs capture changes in the Index changelog.

The search behaviour. Whether ChatGPT searches at all, and how, changes without announcement, and that changes which pages get linked.

We expect the domains ChatGPT links to stay a narrow, vendor-heavy set that moves with whichever vendors publish the most quotable pricing and integration pages. The October 2026 edition is the first test of that on app captures.

Limits of this data

ChatGPT and Claude are measured today. Perplexity, Gemini and Google AI Overviews are explained from their documentation in the Perplexity, Gemini and AI Overviews guides. The Index does not yet publish runs for them.

One run is one run. The full consulted list on this page comes from a single API capture of one maintenance prompt on 3 September 2026. That capture was retired from the edition and kept in the archive because pages like this one cite it.

The September edition’s mention rates come from 25 app captures per category, one per prompt. The Index protocol calls for three runs per prompt before a rank is published. The app shows the links in an answer, not the pages behind it.

Related guides

The other engines pick sources differently. The Perplexity guide covers a model that returns dated search results and numbered citations, and the Gemini guide covers Google Search grounding. The AI Overviews guide covers an engine the Index can only observe through a captured results page.

The general mechanism shared by all four is on the AI search optimization pillar. This site’s own scorecard against every guide it publishes is the reference implementation.

Changelog

2026-10-28: Rewritten as a how-to-rank guide for vendors, with the capture settings and the seeded-mention rule moved to the Index methodology page. Added the short answer, question headings, the four source types, the crawler section and the FAQ. The September 2026 figures are unchanged and re-verified against the edition export.

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 consumer app at chatgpt.com. The consulted-sources section was rewritten to say that the consulted list is no longer visible for ChatGPT and that the split is still documented on the API. The 2026-09 figures are kept and labeled as the API capture of 3 September 2026.

2026-09-03: Rebuilt for the AI Shortlist Index scope around the Responses API capture the Index used at the time. Added the annotations-versus-consulted-sources section and the facts from the 2026-09 run of prompt mvn-best-01. Removed the off-topic retail and agent sections.

2026-06-10: First published as a general ChatGPT SEO guide.