> 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/entity-architecture.md). # Entity architecture How entity architecture helps search engines and AI systems understand an organisation. Entity architecture defines the important things an organisation wants to be understood for and the relationships between them. Typical entities include the organisation, experts, services, products, programmes, locations, methodologies and subject areas. A useful entity map answers questions such as: * What is this organisation? * What does it offer? * Who is responsible for the expertise? * Which topics does it have evidence to speak about? * How do products, services and resources relate? * Which pages are canonical for each concept? Entity architecture is not a schema-markup exercise alone. It begins with information clarity, then technical signals reinforce that clarity. --- # 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/entity-architecture.md?ask=&goal= ``` `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.