> For the complete documentation index, see [llms.txt](https://knowledge.magicworksitsolutions.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.magicworksitsolutions.com/knowledge/seo-aeo-geo-and-ai-search/seo-vs-aeo-vs-geo.md).

# SEO vs AEO vs GEO

The difference between SEO, Answer Engine Optimisation and Generative Engine Optimisation.

SEO, AEO and GEO overlap, but they are not identical.

## SEO

SEO focuses on crawlability, indexing, relevance, authority, user experience and search performance.

## AEO

Answer Engine Optimisation focuses on making important questions and answers explicit. Definitions, FAQs, comparisons, structured headings and semantic clarity all help.

## GEO

Generative Engine Optimisation focuses on whether high-quality sources are understandable and useful to generative systems. It depends heavily on expertise, evidence, entity clarity, distinctiveness and consistent publication.

No agency controls whether a specific AI system will cite a particular page. The responsible promise is to improve the conditions for discovery and retrieval, then measure what changes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.magicworksitsolutions.com/knowledge/seo-aeo-geo-and-ai-search/seo-vs-aeo-vs-geo.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.