Tag: entities

  • How to rank better in LLMs and AI search

    How to rank better in LLMs and AI search

    For about a decade, SEO meant one thing for most of us: getting found in a list of blue links.

    That work still matters. But here’s what changed. A lot of people now get an answer first, from Google AI Overviews or AI Mode, from ChatGPT, from Gemini, from Perplexity. Only after that do they decide which source to open, if they open one at all.

    So you can rank fine in classic search and still be missing from the answer. Frustrating, right?

    Let’s clear something up first. “Ranking” in a large language model isn’t a position you can buy. It’s closer to this question: when a system needs a source, is your page easy to find, easy to read, and specific enough to quote without twisting what you said?

    Nobody can guarantee you a citation. Anyone who says they can is selling something. What you can do is remove the reasons you’d get skipped.

    That’s what this post is about. I’ll cover entity clarity, writing that’s worth citing, honest structured data, brand mentions, crawler access for AI bots, and a format that works for people and machines.

    What “ranking” in LLMs can reasonably mean

    Google is the clearest official voice on its own AI features. Its documentation on AI features and your website says there are no extra technical requirements to show up in AI Overviews or AI Mode. No special schema either. A page just has to be indexed and eligible to show in Google Search with a snippet.

    The same document repeats the usual SEO basics:

    • Allow crawling.
    • Use internal links.
    • Put important information in text.
    • Keep structured data consistent with the visible page.
    • Keep your Business Profile or Merchant Center info current, if those apply.

    And inclusion still isn’t guaranteed.

    ChatGPT, Gemini (the app), and Perplexity are different animals. Depending on the mode and the question, they may pull live sources, lean on training data, or do both. What you can influence is more down to earth: Can the right crawler reach your page? Is the page specific and clearly about a named entity? Can your claims be quoted accurately? Is your brand referred to the same way around the web?

    If someone promises you a reliable “LLM rank,” don’t take it on faith. I wouldn’t.

    Make the entity obvious

    Systems retrieve and cite more reliably when they can tell who you are, what the page is about, and how it fits with the rest of your site. That’s traditional entity SEO. And it’s become more important, not less.

    Here’s what that looks like day to day. Use one consistent name for your organization, your authors, and the products or services you write about. Your homepage, About page, bylines, and contact info should all agree. If you work in a specific place, say so in plain words, not only in the footer. Put the subject in the title, the H1, and the first couple of sentences.

    Ambiguity costs you. If a system can’t tell whether “Mercury” is a company, a planet, or a metal, it’ll go find a less confusing source.

    Thin, interchangeable posts don’t travel well in AI search either. When I read a page that could’ve been written about any brand in the category, I always ask: what would a model even hold on to here? A page that describes an actual method or a first-hand observation gives it something real. That’s the page that gets pulled.

    Write so a system can cite you without distorting you

    Answer engines like passages they can lift without having to fix the meaning. That changes how you write. What you target is only half of it.

    • Lead with the answer. Open important sections with a direct answer, then add the conditions and detail. A heading that’s a real question, followed by a plain answer, is much easier to retrieve than a slogan.
    • Make claims concrete and bounded. “Meaningful SEO trust often takes six to eight months of persistent work” is something a reader can use. “We deliver explosive growth” isn’t.
    • Credit your sources. If a fact isn’t yours, link to the official or named source. If you can’t name a source, don’t make up a statistic. Ever.
    • Keep the text complete. Google’s AI features guidance says plainly that important content should be available as text. Don’t bury the answer in an image or a tab that never renders as HTML.
    • Date your updates. When the substance changes, update the page and say what changed.

    Bonus: the same habits help your classic snippets and title tags. Two birds.

    Structured data, used honestly

    Structured data doesn’t come with a secret AI-ranking bonus. Google says you don’t need special schema to show up in AI Overviews or AI Mode, and that any structured data you do use should match the visible text on the page.

    So use schema when it accurately describes something already on the page: an Organization, a Person, an Article, a LocalBusiness, a Product, or an FAQ people can actually see.

    Don’t mark up reviews you don’t have. Don’t credit authors who didn’t write the piece. Don’t add FAQ markup for questions that never appear on the page. Inaccurate markup isn’t a shortcut. It’s a trust problem waiting to happen.

    When your Organization name, logo, and official profiles line up in the markup and on the page, you’ve given systems a cleaner identity to attach mentions to. That’s useful. It still doesn’t replace being mentioned and linked as a real source.

    Brand mentions, and the sites that already cite you

    Classic SEO taught us to care about links. They still matter.

    But unlinked mentions and consistent naming help too. They help a model connect a claim to a brand, especially when those mentions show up on sources the system already treats as reliable.

    Can you fake this? Not usefully. A burst of identical bios on low-quality directories won’t make you the go-to source for a technical question.

    What helps, slowly, is the same work that has always built authority. Publish pages other practitioners would actually cite. Be accurate when someone quotes you. Show up in places your buyers already trust.

    If your public footprint is thin, start by making the official record consistent. Then write a few genuinely specific pages instead of a big stack of interchangeable ones.

    Give AI crawlers a clear, deliberate path

    Retrieval requires access. This is the most technical part of the whole job, and it’s the part I see sites get wrong by accident more than any other.

    OpenAI documents its crawlers separately. OAI-SearchBot is used to surface websites in ChatGPT’s search features. Sites that opt out won’t show up in ChatGPT search answers, though they can still appear as navigational links. GPTBot is the one used to crawl content that may go into training generative AI foundation models.

    Those two controls are independent. Keep that in mind.

    ChatGPT-User is a fetcher that kicks in when a user asks for something. It’s not an automatic crawler in the same sense. OpenAI also notes a robots.txt change can take about a day to be reflected, and firewalls can block crawlers even when robots.txt lets them in.

    PerplexityBot is used to surface and link websites in Perplexity results, and according to Perplexity, it isn’t used to crawl content for foundation models. Perplexity-User handles user-initiated fetches and generally ignores robots.txt, since a person asked for the page.

    Google’s Search AI features rely on ordinary Search eligibility. That means Googlebot has to be able to crawl and index the page. Google also documents other product tokens, including Google-Extended, in its crawler overview. Those tokens don’t replace being indexable in Search.

    Here’s the audit I run:

    1. Read your robots.txt. Make sure you haven’t disallowed OAI-SearchBot, PerplexityBot, or Googlebot on the URLs you want visible, unless that’s a deliberate policy.
    2. Check your CDN, WAF, and bot-challenge rules. A 403, a JavaScript challenge, or a login wall can shut out a crawler that robots.txt allows. When a provider publishes IP ranges, use those official lists, not a one-time sample from your logs.
    3. Compare what the crawler sees with what a user sees. The crawler should get the same main content, not a blank shell that only fills in after a client-side app loads.
    4. Decide training access separately from search access. And write the decision down.

    That third one catches more sites than you’d think.

    What not to do

    Don’t buy “submit your site to 50 LLMs” services. Don’t paste a hidden block of machine-only answers at the bottom of every page. There’s no evidence it helps, and it tends to create thin, duplicate content.

    Don’t confuse blocking GPTBot with blocking all visibility in ChatGPT. If you want to appear in ChatGPT search, the crawler that matters is OAI-SearchBot.

    Don’t invent statistics, fake expert quotes, or schema that doesn’t match the page.

    And don’t assume you need a special file or a “GEO score” for Google AI Overviews or AI Mode. Google has said the opposite.

    How this work shows up in a real engagement

    When I work on AI search visibility at Seopya, I start with the same foundation I’d use for classic SEO. Are the important pages indexable? Internally linked? Written with real specificity?

    Then I check crawler access, entity consistency, and whether the pages are actually citable. It all lives inside our SEO and AI search services.

    Here’s the blunt version: if the site can’t be crawled or the content is interchangeable, no amount of “LLM optimization” will make it a preferred source.

    Key takeaways

    • You can’t buy a reliable spot inside ChatGPT, Gemini, Perplexity, or Google AI Overviews. You can make your pages easier to retrieve and safer to quote.
    • For Google AI Overviews and AI Mode, the official requirement is ordinary Search eligibility. No special schema.
    • Be consistent about who you are, write bounded claims, keep structured data in line with visible text, and allow the crawlers that power search visibility.
    • Mentions and citations around the web still help, as long as they’re real.

    FAQ

    Is GEO different from SEO?

    Generative engine optimization is a handy name for the work of becoming a source in AI answers. It doesn’t replace technical SEO, on-page clarity, or earned authority. For its own AI features, Google treats SEO fundamentals as the relevant work.

    Should I block AI crawlers?

    That’s a policy decision, not a default. If you want to be eligible for ChatGPT search or Perplexity results, allow the search crawlers those companies document. Training crawlers can be a separate call. Make the decision on purpose, then check that your security tools actually honor it.

    Does structured data get me cited by ChatGPT or Perplexity?

    There’s no official structured-data requirement that guarantees a citation in those products. Accurate markup can make your entity easier to interpret, especially for Google. It won’t make up for a page a crawler can’t reach, or claims too vague to quote.

    The next step

    Pick five pages that should already be sources. Check each one: Is it indexable? Internally linked? Clear about the entity? Does it give a direct answer? Is the schema consistent (if you use any)? Can the crawlers you want to allow actually reach it?

    Fix those five before you publish ten more.

    If you’d rather have help, get in touch. I can tell you what an AI search pass on your site would involve.