How to Earn Brand Mentions in ChatGPT: The Entity Signals That Matter
How do you get your business mentioned in ChatGPT and other AI search results? Make your organisation easy to describe. Say plainly on your own site who you are, what you do, where and for whom, then make sure trusted sites elsewhere say the same thing in the same words. Clear, corroborated facts make a business easier for an assistant to name with confidence, and a good blog on its own doesn't do that job.
That's the short version. The longer one covers what an entity is, which signals feed it, the order to tackle the work in, and how to tell whether anything's moving, since nobody can promise you a mention.
Key Takeaways
- An assistant can only recommend what it can describe. If your name, location and services shift from page to page and profile to profile, you're likely to be harder to name than a competitor who's dull but consistent.
- Your About page and Organization schema are where you state the facts about yourself. Directories, industry bodies and coverage are where other people back them up.
- A listing in an official vendor or partner directory can do more for "which agencies..." questions than a dozen extra blog posts.
- Crawlability and answer-first writing are the floor, not the strategy. Block the crawlers and none of the rest matters.
- Track ten real questions across several assistants for months. Expect noise, and don't read anything into a single run.
What an Entity Is, and Why Assistants Care
In this context an entity is a specific, named thing with attributes that hold steady wherever it's mentioned. For an organisation, those attributes are the boring ones: legal or trading name, location, founding year, what it does, who it serves, who runs it, which platforms or bodies vouch for it. (The AI glossary covers the surrounding terms if any of them are new.)
Ask an assistant "who builds Umbraco websites in Sydney?" and it has to settle on names it can stand behind. A business described identically in ten independent places is a safe answer. One described three different ways, or only on its own site, is a gamble, and a gamble is easier to leave out.
Think of asking for a tradie recommendation at a barbecue. People name whoever they can vouch for, not whoever has the flashiest ute. So the job isn't to persuade the model. It's to remove doubt.
The Sequence: Eight Things to Do, in Order
Order matters. Chasing directory listings while your own site describes you vaguely leaves the listing nothing solid to match against.
- Write down your entity facts. One short document: exact brand name, location, founding year, services in plain words, the sectors you serve, key people and their titles, certifications and partner tiers. This becomes the source everything else copies from.
- Rewrite the About page to match. State what you do, where, since when and for whom, in the first two or three sentences. No mission poetry up top. Save that for further down.
- Add Organization schema with sameAs links. Mark up the same facts in structured data, and use the sameAs property to point at your official profiles: LinkedIn, partner directory listings, your B Corp profile if you have one.
- Fix naming drift. Same brand name, same service names, same people's titles, everywhere.
- Give bylined content real author pages. A named person, their role, what they're qualified to talk about, linked from every article they've written.
- Make service pages answer "who does X in Y". The first paragraph should say what the service is, who delivers it and where.
- Claim and correct your off-site listings. Partner directories, industry bodies, certification directories. Copy from the entity document word for word.
- Start measuring before you change much. A baseline taken now is worth more than one you reconstruct later.
On-Site Signals: Saying It Plainly
The About page is a fact sheet first
Plenty of About pages open with values and a team photo. Lovely, and useless to a machine working out what you are. Put the plain statement first and let the personality follow it.
As an illustration of what "plain" looks like, here's how Webcoda's own facts read: a digital agency based in Surry Hills, Sydney, founded in 2005, a Certified B Corporation, a Microsoft Partner, an Umbraco Gold Partner and Gold Contributing Partner for 2025, a Gold partner for Xperience by Kentico, and a HubSpot Solutions Partner at Gold tier with 18 certifications, also working with Kontent.ai and Agility CMS. Not exciting, and that's the point. Most of these can be checked against an outside source, and an About page, a directory listing and a schema block should all state them identically.
Organization schema and sameAs
Schema doesn't make you famous. What it does is hand a crawler your facts in a structured, unambiguous format, and the sameAs links say "these profiles elsewhere are also me". That second part is underrated. It ties your site to the third-party pages that corroborate it, which makes it easier for any system reading it to tell whether the "Acme Digital" in a directory is the same Acme as yours.
Keep it honest. Mark up only what's visible on the page and true. Google's structured data guidelines say markup must be a true representation of the page content, and a mismatch undermines the consistency you're trying to build.
Consistent naming is unglamorous and it matters
If one page says "AI search optimisation", another says "generative engine optimisation" and a third says "LLM SEO", you've made it harder to tell that the three are one service. Pick a name per service and stick to it. Same for people: a Managing Director shouldn't be a CEO on LinkedIn and a Founder in the footer. (Brand names with and without "Pty Ltd" are a classic. Pick the trading name and use it wherever the law doesn't say otherwise.)
Author pages and service pages
Bylined content needs a person behind it, with a page that says who they are and why they're qualified. Webcoda's blog uses a consistent byline and FAQ sections on its articles, which is the kind of structural habit worth copying. It guarantees nothing, but gives each article a clear owner and extractable answers.
Service pages should answer the buyer's actual question in the first paragraph. A line like "We design and build websites for not-for-profits in Brisbane" can be lifted straight into an answer. "Digital experiences that move people" can't.
Off-Site Corroboration: Other People Saying It
Most teams skip this part. I think it matters most for recommendation-style questions, and if I'm wrong, the cost is a few afternoons spent tidying listings you should have tidied anyway.
When someone asks "which agencies are certified for X?", the assistant needs a source that can answer that question. Official vendor directories are an obvious candidate. HubSpot's Solutions Directory, the partner listings that Umbraco and Kentico publish, the B Corp directory run by B Lab: each is maintained by the organisation that granted the credential, so a listing there is hard to fake and a reasonable thing for a model to rely on. One accurate listing on an authoritative vendor site can matter more than a dozen posts on your own blog, because your blog is you talking about yourself and the directory is the vendor vouching for you.
- Check every directory you're entitled to appear in. Certified but unlisted is a common gap.
- Make the description match your entity document. Same name, same location, same services.
- Industry bodies, association member lists and genuine third-party coverage such as trade press count too.
- Link back from your site to those listings, and include them in sameAs.
None of this is fast. Directories and assistants both update on their own schedules.
The Technical Foundation, Briefly
All of this assumes the assistant can read your site. It's worth checking first:
- Crawlable pages. Key content in the HTML, not behind scripts or logins.
- Don't block the crawlers you want citing you. OpenAI's documentation separates them: OAI-SearchBot surfaces sites in ChatGPT search, while GPTBot gathers content that may be used for training, and each can be allowed or blocked independently in robots.txt. Blocking OAI-SearchBot keeps your pages out of ChatGPT search answers, although OpenAI says they can still appear as navigational links. A third agent, ChatGPT-User, fetches pages when a person asks ChatGPT to, and OpenAI notes that robots.txt rules may not apply to it.
- Answer-first paragraphs and FAQs, so a passage can be quoted without the rest of the page.
- Stable URLs. A dead link is a broken citation.
The deeper version of this lives with technical SEO. Here it's just the floor you build on.
How to Measure Something You Don't Control
Nobody controls what an assistant says. Not you, not an agency, and arguably not the companies building them. Answers differ between ChatGPT, Perplexity, Gemini and Copilot, and the same assistant can name you on Monday and leave you out on Tuesday. Anyone promising guaranteed mentions is selling something.
What you can do is watch the trend:
- Write down the ten questions you'd most like to be named for, phrased the way a buyer would phrase them, not your marketing team.
- Ask several assistants each question on a regular schedule, monthly is enough, and run each more than once.
- Record whether you're named, who is named instead, and which sources get cited.
- Look at those cited sources. They tell you which directories and publications the assistants lean on for your category, and that's your off-site to-do list.
Treat it as a slow signal measured over months. A single good run means very little. A shift across many runs and several assistants, sustained over a quarter, is worth paying attention to.
I'd rather a team track ten honest questions in a spreadsheet than buy a dashboard that turns noise into a confident-looking line. A few years ago "where do we rank?" had one answer per search engine. Now it's a distribution, and we're all still learning to read it. Webcoda included.
Where Webcoda Fits
Webcoda's AI Search Optimisation service covers this ground: making a site easier for ChatGPT, Perplexity, Google AI Overviews and Copilot to read and cite, including entity and schema work and extractable content, alongside the technical SEO it shares foundations with. If you're weighing AI work more broadly, the AI services page explains the readiness assessment as a starting point. We can't promise an assistant will name you, and we won't. What can be done is making sure that when it looks, the facts are clear, consistent and backed up.
Frequently Asked Questions
Make your organisation easy to describe and easy to corroborate. State plainly on your site what you do, where, since when and for whom, back it with Organization schema, and make sure official directories, industry bodies and third-party coverage describe you the same way. Let the AI crawlers you want citing you reach your pages. Then measure over months, because no one can guarantee a mention.
They're the consistent facts that let an assistant recognise your organisation as one specific, describable thing: name, location, founding year, services, people and credentials. Signals come from your own site, including the About page and structured data, and from independent sources that repeat the same facts.
It can, especially for "which agencies..." or "who is certified for..." questions. A vendor's own directory is an authoritative source for that kind of question, and the listing is the vendor vouching for you rather than you describing yourself. It's no guarantee, but it's one of the better-value actions on the list.
Block OAI-SearchBot only if you don't want to appear in ChatGPT search answers. Blocking GPTBot is a separate decision about whether your content is used for training. OpenAI documents separate crawlers for search and for training, so you can block GPTBot from training while still allowing OAI-SearchBot to surface your pages in ChatGPT search. Check what your robots.txt and CDN settings actually do before deciding.
There's no reliable timeline. Directories, crawlers and assistants all update on their own schedules, and answers vary between runs. Track a fixed set of questions monthly and judge progress over several months rather than weeks.
Talk to Webcoda
Webcoda is a Sydney-based, B Corp certified digital agency that has been building websites and enterprise web applications since 2005, for organisations including Sony, BridgeClimb, the Australian Federal Government and NSW Health. We are an Umbraco Gold Partner, a Gold partner for Xperience by Kentico and a HubSpot Solutions Partner, so platform advice comes without a single-vendor agenda.
Get in touch to talk through your project, or browse our full range of services and platforms.