Category: AI search

Answer engines and generative engines: how ChatGPT, Perplexity and Google AI Overviews pick what they cite.

  • How Google AI Overviews choose which pages to use

    How Google AI Overviews choose which pages to use

    Google AI Overviews and AI Mode do not pick pages the way the ten blue links did. They fan a question out into sub-questions, fetch candidates for each, and assemble an answer from the pages that cover the most ground credibly. The implication for a writer is simple and uncomfortable: a thin page cannot win, however well it is optimised.

    What “depth” means in practice

    Take the question your page answers and write down the five questions a careful reader would ask next. If your page answers three of them in passing and ignores two, you have found your edit. This is the “query fan-out” idea, and it is the single most useful lens for GEO work.

    Signals that read as trust

    • Outbound citations to primary sources, with real links.
    • Original numbers: your own measurements, survey, or worked example.
    • A table where a comparison is being made.
    • Semantic HTML: the article in an <article>, navigation in <nav>, so the model can discard the chrome.
    • A clear “Updated on” date that matches dateModified.

    What the GEO score checks

    Rankavia’s generative-engine score looks for exactly these things on the rendered page: sub-topic coverage against the heading structure, the presence of citations, tables and original data, semantic wrappers, and freshness. It then lists the specific gaps for the page in front of you. It will not write the missing section for you unless you ask it to draft one with your own AI key, and even then you approve every word.

  • How to write pages that answer engines cite

    How to write pages that answer engines cite

    When an answer engine cites a page, it is usually quoting one or two sentences. Pages get cited because those sentences exist and can be found. That is a writing problem more than a markup problem, and it is fixable in an afternoon.

    State the answer first

    Under every question-shaped heading, the first sentence should be the answer in plain words. Context, caveats and examples come after. Models and people both read top-down, and both leave early.

    Use headings that are questions

    “How long does a WordPress migration take?” is a heading an engine can match to a query. “Timeline” is not. You do not need every heading to be a question, but the ones that carry the main answers should be.

    Show who wrote it and when

    A visible author with a short bio, a visible date, and matching Person and dateModified fields in the page’s structured data. Engines weigh this more than they used to, and the plugin outputs it automatically from the author profile.

    Give them something to quote

    A number, a definition, a short list of steps, a comparison table. Original material is what gets cited; a paraphrase of someone else’s page is what gets skipped. Rankavia’s answer blocks (Key takeaways, Definition, Steps, Pros and cons) exist to make this structure easy to add without touching the theme.

    What about FAQ schema and llms.txt?

    Add them if they are cheap, and do not expect them to rank you. FAQ rich results are gone for most sites, and llms.txt is a courtesy index that some crawlers read and none are obliged to. Rankavia labels both honestly in the interface for that reason.

  • Are you blocking AI crawlers without meaning to?

    Are you blocking AI crawlers without meaning to?

    Every answer engine has a crawler, and every crawler reads robots.txt. Blocking them all is a decision some publishers make deliberately. Blocking them by accident, because a plugin or a host added a rule years ago, is far more common.

    Which bots are we talking about?

    OpenAI runs GPTBot for training and OAI-SearchBot for ChatGPT search results. Anthropic runs ClaudeBot. Perplexity runs PerplexityBot. Google-Extended controls whether your content feeds Gemini, separately from ordinary Google search. Bingbot feeds both Bing and Copilot. Then there are CCBot, Applebot-Extended, Bytespider and Meta-ExternalAgent, each with their own purpose.

    Search yes, training no

    The most defensible policy for a business site is to allow the bots that send visitors and to decide separately about the ones that only train models. That means allowing OAI-SearchBot, PerplexityBot and Bingbot, and making a conscious choice about GPTBot, ClaudeBot, Google-Extended and CCBot. Rankavia ships this as a one-click preset, writes the rules into robots.txt, and shows you what each bot actually fetched in the AI bot log.

    How to check what you have today

    Open /robots.txt on your own domain and look for any User-agent block that names one of the bots above, or a blanket Disallow: /. Then check the response headers of a page for X-Robots-Tag. The free AI crawler check on rankavia.com does both and tells you, bot by bot, whether you are allowing, blocking or saying nothing.

    Saying nothing is allowing. If that is not what you intend, write it down.