> For AI agents: a documentation index is available at [llms.txt](https://1alexander.ai/llms.txt).

# A technical AEO checklist

A technical AEO checklist for llms.txt, schema and site access, so assistants can fetch and understand your pages before you do deeper work.

[All guides](https://1alexander.ai/articles)

By [Jake Parks](https://1alexander.ai/about)  Updated 16 Nov 2026  6 min read

Start with pages assistants can fetch and understand. An llms.txt file can point agents to important URLs, but Google Search ignores it, including for AI features, so it is not a ranking switch. Schema should describe visible facts; it is not a pass into answers. [\[1\]](https://1alexander.ai/articles/aeo-checklist#source-1) [\[2\]](https://1alexander.ai/articles/aeo-checklist#source-2) [\[3\]](https://1alexander.ai/articles/aeo-checklist#source-3)

In this guide  

## Check the foundations

Use this checklist to find access problems and make your pages more useful to buyers. It is editorial guidance, not a certified standard or a ranking guarantee. If AEO is new to you, start with [what answer engine optimization means](https://1alexander.ai/articles/what-is-answer-engine-optimization).

Scroll sideways to see the full checklist.

| Check | What to inspect |
| --- | --- |
| Crawler access | Check robots.txt and hosting or WAF blocks. Review OAI-SearchBot for ChatGPT search and PerplexityBot for Perplexity search; distinguish training and user-initiated fetches. For Grok, check the vendor’s current published docs. \[5\] \[6\] |
| Google eligibility | Confirm that the page is indexed and eligible for a Search snippet before investigating Google AI Overviews. Eligibility does not guarantee appearance. \[1\] |
| Clear offer and facts | Explain what \[product\] does, who it suits and which facts support \[company\]’s claims. Publish accurate product, comparison and integration information where useful. |
| Useful headings | Give each section a clear heading that helps buyers find its answer. Write for the reader’s question. |
| Internal links | Connect important pages with descriptive links so readers and crawlers can find the supporting detail. |
| Matching schema | Use FAQPage and Article or BlogPosting only where the page really contains those answers or an article. Keep structured data consistent with visible facts. \[3\] |
| Optional llms.txt | Maintain a brief index of important public URLs if you want to help agents that look for it. Google Search does not use the file. \[2\] \[4\] |
| Dated retest | Repeat the same buyer questions in ChatGPT, Google AI Overviews, Perplexity and Grok. Keep mentions, citations, referral visits and sales in separate records. |

## Use llms.txt as an index

The [llms.txt community proposal](https://llmstxt.org/) describes a Markdown file at /llms.txt that gives agents brief background and links to important URLs. It is a proposal for helping agents use a website, not a Google ranking signal. [\[4\]](https://1alexander.ai/articles/aeo-checklist#source-4)

Does your site need one? It can be useful if you want agents that look for this file to find key URLs in one place. Google says it is fine to maintain one for other services, but it neither helps nor harms Google Search visibility or rankings because Search ignores it. No special file is required for Google’s AI features. [\[2\]](https://1alexander.ai/articles/aeo-checklist#source-2)

The live [1Alexander llms.txt](https://1alexander.ai/llms.txt) is a worked example of an index of public pages. Its existence is not evidence that the file causes citations or recommendations. Keep any index accurate as pages change.

## Mark up visible facts

Structured data gives search systems a defined description of page content. It can help a page qualify for ordinary Search rich results. Google does not require structured data for its generative AI search features, and there is no special schema.org markup to add for them. [\[1\]](https://1alexander.ai/articles/aeo-checklist#source-1) [\[3\]](https://1alexander.ai/articles/aeo-checklist#source-3)

Mark up only information readers can see. Article or BlogPosting should describe the article on the page; FAQPage belongs where the page actually contains those questions and answers. Eligibility never guarantees a rich result, citation or AI-overview link. [\[3\]](https://1alexander.ai/articles/aeo-checklist#source-3)

## Separate access from appearance

For Google AI Overviews and AI Mode, a supporting page must be indexed and eligible for a Search snippet. There are no additional technical requirements, and neither indexing nor serving is guaranteed. No special Google AI bot is required. [\[1\]](https://1alexander.ai/articles/aeo-checklist#source-1) [\[2\]](https://1alexander.ai/articles/aeo-checklist#source-2)

Check robots.txt, hosting restrictions, a web application firewall (WAF), login walls and other access problems. A missing mention alone does not tell you that a crawler was blocked. Use the official bot documentation to distinguish the following roles.

### ChatGPT search and fetches

OpenAI recommends allowing OAI-SearchBot in robots.txt for ChatGPT search appearance. Opted-out sites do not appear in search answers, though navigational links remain possible. Allow about 24 hours after a robots.txt change. [\[5\]](https://1alexander.ai/articles/aeo-checklist#source-5)

GPTBot collects content that may train foundation models. Blocking it opts out of training, not ChatGPT search. ChatGPT-User handles some user-initiated fetches, including Custom GPTs; it is not an automatic crawler, robots.txt may not apply, and it does not determine Search appearance. Use OAI-SearchBot for search opt-out. [\[5\]](https://1alexander.ai/articles/aeo-checklist#source-5)

### Perplexity search and fetches

Perplexity recommends allowing PerplexityBot in robots.txt to support search results that surface and link sites. It does not crawl for AI foundation models. Allow up to 24 hours for changes. Perplexity-User supports user-initiated fetches and generally ignores robots.txt. Check the documented IP ranges when reviewing WAF rules. [\[6\]](https://1alexander.ai/articles/aeo-checklist#source-6)

### Check Grok’s current guidance

No official crawler user-agent documentation was found on x.ai or docs.x.ai when checked on 16 November 2026. The x.ai/robots.txt file governs that site; it is not a guide to crawler tokens. Check the vendor’s current published documentation rather than guessing a bot name. Include Grok in the dated answer checks even when crawler guidance is unavailable.

## Pick a capable platform

There is no proven best CMS for AEO. Choose a platform that lets you publish crawlable, indexable pages with clean URLs, editable templates and structured data that matches visible facts. Check those capabilities on your actual site rather than assuming a platform name settles them.

For \[product\], a useful page might explain supported integrations, who the product suits and the limits buyers should know. Give \[company\]’s factual pages clear headings and links to supporting detail. Avoid unsupported comparisons or claims that an assistant will recommend you.

## Repeat the buyer questions

After access or page changes, repeat the same buyer questions in ChatGPT, Google AI Overviews, Perplexity and Grok. Save the date, question, assistant, raw answer and cited URLs. Keep the question set and conditions consistent enough to inspect changes, and record any differences.

Keep mentions, citations, referral visits and sales in separate records. An appearance in an answer is not a visit or a sale, and a changed answer does not establish what caused it. Use the [AI visibility audit guide](https://1alexander.ai/articles/ai-visibility-audit) to organize the evidence and [measuring AI search](https://1alexander.ai/research/measuring-ai-search) to define outcomes. The [ChatGPT guide](https://1alexander.ai/articles/get-business-on-chatgpt) explains the broader discovery checks.

## Short FAQ

### Do I need an llms.txt file?

It is a proposed Markdown file at /llms.txt with brief background and important URLs for agents. It is optional: useful for agents that look for it, but ignored by Google Search, including its AI features.

### Does schema markup help with AI search visibility?

Schema can help a page qualify for ordinary Search rich results when it matches visible facts. Google requires no special schema for its AI features. Markup does not guarantee a rich result, citation or AI-overview link.

### What should an AEO checklist include?

Check crawler access, Google indexation and snippet eligibility, clear factual pages, useful headings, internal links and schema that matches visible content. Treat llms.txt as optional, then repeat the same buyer questions and record outcomes separately.

### Which website platforms or CMSs are best for AEO?

There is no proven best CMS for AEO. Choose one that supports crawlable, indexable pages, clean URLs, editable templates and structured data that matches visible facts. Verify those capabilities on your actual site.

### How do I optimize my website for AI search engines?

Start with pages assistants can fetch and understand. Resolve access issues, explain your offer with accurate facts, connect useful pages and retest the same buyer questions in ChatGPT, Google AI Overviews, Perplexity and Grok. Track mentions, citations, referral visits and sales separately.

## Sources

Official pages and the original community proposal checked on 16 November 2026 (Asia/Manila). The checklist and platform advice are editorial guidance, not a certified standard or evidence of guaranteed visibility. The Grok documentation search on x.ai and docs.x.ai found no official crawler-token guide on that date.

\[1\] [Google Search Central, AI features and your website](https://developers.google.com/search/docs/appearance/ai-features)

\[2\] [Google Search Central, Optimizing your website for generative AI features on Google Search](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide)

\[3\] [Google Search Central, General structured data guidelines](https://developers.google.com/search/docs/appearance/structured-data/sd-policies)

\[4\] [The /llms.txt file proposal](https://llmstxt.org/)

\[5\] [OpenAI, Overview of OpenAI Crawlers](https://developers.openai.com/api/docs/bots)

\[6\] [Perplexity, Perplexity Crawlers](https://docs.perplexity.ai/docs/resources/perplexity-crawlers)

## Related reading

[How to claim your business on ChatGPT](https://1alexander.ai/articles/get-business-on-chatgpt)

## Put the guide into practice

[Read the methodology](https://1alexander.ai/methodology)
