How to Get Your AI Tool Mentioned by ChatGPT, Claude and Perplexity

Why most of what shapes whether an assistant names your product happens outside your own site, and the specific, unglamorous things a maker can change this month.

How to Get Your AI Tool Mentioned by ChatGPT, Claude and Perplexity

The question comes up constantly, in roughly one form: an assistant keeps naming two competitors and never this tool, and the founder has already done the things the checklists say to do. More content. Schema markup. A comparison page. Nothing moved.

The advice was not wrong, exactly. It was aimed at the wrong mechanism. Most of what determines whether your product gets named lives outside your website entirely, and almost none of the popular checklists say so plainly.

Running a launch directory means watching what happens to a product's description once it leaves the founder's hands and lands on somebody else's page. That vantage point does not make me an expert on how any model works internally. It does mean I have seen, repeatedly, which pages survive to get quoted and which quietly do not.

Key facts

  • An assistant can only mention you two ways: it learned about you during training, or it looked you up while answering. For a small or new product, the first path is effectively closed.

  • The retrieval path runs on third-party pages, not your own site. A vendor's landing page is a claim. An outside page describing the same thing is corroboration.

  • A page has to be readable by something that is not a browser rendering JavaScript. I have seen high-authority directory pages that only display their listing text and outbound links after a client-side script runs, which means a crawler reading the raw HTML sees nothing there at all.

  • There is no submission form for a training set and no reliable way to track your rank in AI answers over time. Anyone promising guaranteed mentions is promising something nobody controls.

The two paths, and why only one is open to you

Ask an assistant about a product it has heard of a thousand times and it answers instantly, no lookup required. That answer was baked in during training, from the accumulated weight of everything written about that product before the training cutoff. This is the training-data path, and for a tool that launched this year, or last year, or that simply has not accumulated much written material yet, it is close to a locked door. You cannot submit anything to a training run. You cannot request inclusion. The set was fixed before you had a chance to be in it.

The second path is different in kind. Some assistants, when a question calls for current or specific information, search the live web or a connected index and pull text into the answer as it is being composed. This is the retrieval path, and it is the one a small product can actually influence, because it depends on what exists on the open web right now, not on what existed at some earlier cutoff date.

I want to be honest about the limits of what I know here. I do not have visibility into exactly which systems retrieve for which questions, or how heavily any one source gets weighted against another. What I can say with more confidence is the shape of the problem: if you are not already famous enough to be in the training data, retrieval is the only lever left, and retrieval runs entirely on pages other than your own.

Why the quote comes from someone else's page

Try asking any assistant "what is the best tool for X" and think about what evidence it is reaching for. That is a subjective question, and a system answering it prefers a source that is not the vendor making the claim about itself. Your own landing page telling a visitor it is the best is exactly the kind of statement that needs a second, independent voice behind it before it counts as evidence for anything.

That is where a directory listing, a roundup post, or a comparison article earns its place. It is a third party stating in plain terms what your tool is and who it is for, sitting on a domain that is not yours, discoverable independent of anything you say about yourself. It is one of the cheapest pages you can get created, because in most cases someone else is willing to host it for you at no cost beyond a form and a bit of patience.

This is genuinely useful ground, and it is worth naming honestly rather than backing into it. If you want a sense of how many of these third-party pages exist and what each one is actually worth, I keep a running catalog of launch directories with domain rating, traffic and pricing for each, because the landscape changes faster than any single blog post can track.

The name, briefly, and then the real problem

Before anything about content: if your product's name collides with a dictionary word or an existing company, bind it to a category everywhere it appears, because an unbound name gives a retrieval system nothing to disambiguate with. That is as far as naming goes here. It is a big enough topic to deserve its own treatment elsewhere.

The related problem, and the one I actually want to focus on, is consensus. If eight pages describe your tool eight different ways, none of them reinforce each other, and a system pulling from several of them at once gets a blur instead of a fact. One plain sentence describing what the tool does and who it is for, repeated close to verbatim across every page that mentions you, is worth more than eight pages of varied, clever copywriting.

A directory submission is one of the fastest ways to get that one sentence onto an indexed page you do not control, which is exactly the kind of page a retrieval system treats as evidence rather than a pitch. My own free submission page is a plain example: you write the sentence once, it gets published verbatim, and it sits there indexed on a domain that is not yours.

What actually makes a page quotable

Setting aside where the page lives, the mechanics of the page itself matter more than most founders assume.

It has to be server-rendered, or at least readable without executing JavaScript. I have looked at directory listings on domains with real authority where the product name, description and outbound link only appear after a client-side script runs. View the raw HTML and there is nothing there. A retrieval system reading that page the way a basic crawler does never sees the product at all. This is an easy thing to check and a common thing to get wrong, on both the directory's side and, sometimes, on a founder's own site.

Beyond that, plain declarative sentences beat marketing copy. "X is a tool that helps Y do Z" is more extractable than three paragraphs of positioning that never quite states what the thing is. A page that answers the obvious question in its own words, early, in a sentence that could stand alone, is doing the retrieval system's job for it. A page that makes you read four paragraphs before the point arrives is asking more of the system than it is likely to give.

Why "best X" and "alternatives to Y" pages carry extra weight

The questions people actually ask an assistant tend to follow a small number of shapes: what is the best tool for this job, what are the alternatives to the one everyone already knows, what would you recommend for this specific case. Being present on a page built around that exact phrasing matters more than being mentioned somewhere generic, because the page's own framing already matches the question being asked. A tool absent from every "alternatives to" or "best X" page for its category is starting from a real disadvantage, independent of how good the product is.

What you cannot control, said plainly

You cannot make a model cite you, and there is no dial to turn that raises the odds in a predictable way. Measurement is genuinely weak right now. Ask the same question twice and you can get two different answers, with no version history to compare against and no rank tracker that reliably reflects reality. I ran a small test of my own earlier this month, several questions across a handful of assistants, and my own directory did not appear in a single answer despite doing most of what is described here. I mention that as a check on my own credibility, not as a finding to build a case on.

The same weak measurement cuts against the advice itself. I cannot show you a before-and-after for anything in this article, because there is no clean instrument that would isolate one directory listing's effect on one AI answer months later. What I can offer is that these are the observable, checkable pieces of the mechanism, not proof any of them moved a specific answer.

None of this is fast, and none of it is guaranteed. Anyone selling a guaranteed AI mention is selling a story, not a result.

What to actually do this month

  1. Write one sentence describing what your tool does and who it is for. Reuse it, close to word for word, everywhere your product appears.

  2. Get listed on a few directories that render their listings server-side, checkable by viewing source with JavaScript off.

  3. Find or create at least one "best X" or "alternatives to Y" page in your category, and make sure your listing sits on it with the sentence from step one.

  4. Check your own product pages the same way. Confirm the description and category are in the raw HTML, not injected afterward.

Then wait, and check back in months, not days. This moves slowly, and slowly is the honest pace.

Nick Launches is a product launch directory. Running one means reading an unreasonable number of product descriptions, which is where the habit of checking whether a machine can see any of them came from.

Information

Publisher:
Shawn HacksShawn Hacks
Published date:June 21, 2025