Resources

Where these materials are easiest to misuse

Common misuses include treating one answer as a percentage, pooling country and language, treating a paper’s gain as a promise, and treating markup or llms.txt as a citation requirement.

Published 2026-10-14

Treating one answer as a percentage

One question and one answer are one observation. The NIST handbook discusses intervals for a proportion, which need a sample size. Without a sample size and an interval, do not write that visibility is 0% or 100%.

Pooling country and language

Saudi Arabia and the UAE are not one question condition, and Arabic and English are not either. The API documents checked earlier keep country, result language, and response language in different fields. A single score that adds them together does not say which question it belongs to.

Treating the paper’s gain as a promise

The abstract of the GEO paper says visibility rose by up to 40% in the authors’ experiments. The introduction says the Perplexity.ai check reached up to 37%. The engine, model, and sampling are described in the paper. Those sentences are not a promise about your brand, your page, or current ChatGPT. In Table 1, keyword stuffing’s position-adjusted overall score is below the unoptimized baseline. Calling “add more keywords” a method the paper recommends goes against that table.

Mixing up crawler switches and citations

The OpenAI crawler overview separates OAI-SearchBot, GPTBot, and ChatGPT-User. Opting out of the search crawler is what the page ties to absence from ChatGPT search answers. Opting out of the training crawler is not the same switch. For user-triggered ChatGPT-User fetches, the page says robots.txt may not apply.

The Perplexity crawler page says Perplexity-User generally ignores robots.txt. Blocking PerplexityBot is not a statement that a user-triggered fetch was blocked. Allowing a crawler is also not a statement that an answer will include your link.

Using markup or llms.txt in place of the page

Google’s spam policies define keyword stuffing as filling a page with keywords or numbers in an attempt to manipulate rankings in Google Search. The subject is Google Search. The structured data guidelines require markup to match visible content and say display is not guaranteed. The 2023 FAQ note limited regular FAQ rich results to government and health sites.

The llms.txt proposal calls the file a proposal. The OpenAI and Perplexity documents checked for these notes do not list it as an input to search citation. Publishing the file, or publishing JSON-LD that does not match the page, is not a citation requirement established in those documents.

Using an English page in place of an Arabic page

Google’s hreflang document says Google does not use hreflang to detect the language of a page. The tag does not turn an English body into Arabic, and that document does not make it a citation rule for generated answers. The W3C Arabic layout note describes right-to-left layout, and it labels itself a draft. Correct layout is not a citation.

Keeping a conclusion after the snapshot expires

If the page, the question, the country parameter, or the model and tool changed, the old answer describes only that earlier run. A new conclusion needs a new snapshot. These notes do not publish brand results. There is no customer measurement here that a reader could check, and someone else’s percentage is not relabeled as ours.

Sources

These links were opened and checked on 2026-10-14. The pages may change later.

  1. NIST/SEMATECH e-Handbook, section 7.2.4.1

    https://www.itl.nist.gov/div898/handbook/prc/section2/prc241.htm

    One observation is not a confidence interval for a proportion.

  2. GEO: Generative Engine Optimization

    https://arxiv.org/abs/2311.09735

    The 40% and 37% figures are the paper’s experimental statements. Keyword stuffing scored below the baseline in that experiment.

  3. Overview of OpenAI crawlers

    https://platform.openai.com/docs/bots

    Search, training, and user-triggered fetches are different controls.

  4. Perplexity crawlers

    https://docs.perplexity.ai/docs/resources/perplexity-crawlers

    Perplexity-User generally ignores robots.txt.

  5. Google spam policies

    https://developers.google.com/search/docs/essentials/spam-policies

    The keyword-stuffing definition is about ranking in Google Search.

  6. General structured data guidelines

    https://developers.google.com/search/docs/appearance/structured-data/sd-policies

    Markup must match visible content, and display is not guaranteed.

  7. Changes to HowTo and FAQ rich results

    https://developers.google.com/search/blog/2023/08/howto-faq-changes

    Regular FAQ rich results were narrowed in 2023.

  8. llms.txt proposal

    https://llmstxt.org/

    The proposal is not a confirmed citation factor.

  9. Localized versions of your pages

    https://developers.google.com/search/docs/specialty/international/localized-versions

    hreflang does not detect page language and does not replace the body.

  10. Arabic & Persian Layout Requirements

    https://www.w3.org/TR/alreq/

    Arabic script is right to left. That is a layout fact, not citation evidence.