Site index for AI agents: /llms.txt. Documentation pages under /docs are also served as markdown at the same URL plus .md (e.g. /docs/geo-audit.md) or via an Accept: text/markdown request.
GuideFor the question how to get the work cited, not only the brand name

How to get the work cited, not just the brand name

A brand prompt retrieves your domain. A job prompt retrieves whoever already answered the job. If you only publish About us and comparison pages, the model can name you when asked and still recommend someone else for the work. Write the job page first.

Harsh Songra

Two kinds of prompt, two retrieval paths

"What is [your brand]" and "identity security consultancy for a mid-size bank" look like neighbours. To a retrieval system they are different queries with different candidate sets. The first contains the brand name, so your domain is retrieved almost by definition. The second contains the job, so the retrieved set is whoever has a page that answers it. If that is not you, the model has your name and somebody else's work.

A marketing lead at an identity-security firm described it exactly during discovery in August 2026: "Ask about the brand and we get cited. Ask about the work we do and we don't." That is not an entity problem. The model knows the entity. It is a missing-page problem.

The diagnostic, in two rows

Prompt typeExampleYou are cited?What it means
Brandwhat is [brand]; [brand] pricing; [brand] vs [competitor]Usually yesThe entity is known and the domain is retrievable
Jobtool to see why ChatGPT recommends a competitor; how to measure brand mentionsOften noNo page of yours answers the job in its H1 and first paragraph

If the first row is yes and the second is no, every dollar spent on brand-building is going to a problem you do not have. The work is a page.

Why comparison and About pages do not fix it

A comparison page answers "X vs Y". A features page answers "what does X do". An About page answers "who is X". All three are brand-adjacent: they are retrieved when the model already has the brand in its query. None of them is retrieved for "how do I solve this problem", because none of them has that question as its title. Amplitude's product-analytics content is a useful model here: its explore pages are titled by the job (a retention-rate definition, how to choose an event-tracking approach) and the product appears after the answer, not in the H1.

What a job page is

  1. The H1 is the job, in the buyer's words. No product name, no year, no "best".
  2. The first paragraph answers it. The mechanism, in plain text, inside the first 200 visible characters. ChatGPT's fast path indexes roughly that much of the body.
  3. One liftable block. A table or a numbered list a model can quote without the prose around it.
  4. The product appears once, as the method, in a boxed aside near the end. Not in the title, not in the lead.
  5. A URL that says the job. /guides/how-to-measure-brand-mentions-in-chatgpt, not /blog/post-4812.

Every page in this guides section is built that way, which is deliberate. The section exists to be retrieved for job prompts the brand pages could never win.

The order of work

  • List the job prompts. Sales calls are the source. Eight to twelve to begin.
  • Run them, record who is cited, and open the cited pages. You are looking at the job pages you do not have.
  • Write one. Ship it under a job-shaped URL, link to it from the related brand pages, and leave the brand pages alone.
  • Re-run the same prompts weekly. The pass condition is your URL in the cited column on the job prompt, on repeated runs. Then write the next one.

Questions people ask next

No. A blog post titled "10 AI visibility trends" is not a job page; nobody types that question. A job page has one buyer's question as its title and the answer as its first paragraph. Ten of those beat a hundred posts.

Check its H1. If the title is "The [Brand] Playbook", it is a brand page with a job inside it. The engine retrieves on the title and first paragraph. Rename the H1 to the job and move the brand to the aside, or write a separate job page and link the playbook from it.

One per job that matters commercially, shipped one at a time so you can see which one moved the prompt. A dozen is a real program. Hundreds in a month is a content farm, and engines have learned to discount those.

Not if the H1s are different jobs. "What is [brand]" and "how to measure brand mentions in ChatGPT" do not compete. Cannibalisation happens when two pages answer the same question, which is exactly what this guide tells you to avoid.

Run the same prompts every day, not just once.

Sign up, add the eight to sixteen questions your buyers type, and get named, cited and competitor named per prompt, per engine, with the history kept for the week-apart comparison. Free to start, no card.