> 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/knowledge-layer-architecture.md). # Knowledge-layer architecture What a structured knowledge layer is and how it should relate to a commercial website. A knowledge layer is a structured public reference that explains an organisation's expertise, concepts, methods and decision guidance. It should complement the main website rather than duplicate it. The commercial site remains the canonical place for service offers, product pages and conversion journeys. The knowledge layer goes deeper on definitions, frameworks, comparisons, FAQs, evidence and buyer questions. A strong architecture usually includes: * a clear taxonomy, * stable canonical topics, * concise answer pages, * trust and governance pages, * deliberate links back to commercial destinations, * and measurement that distinguishes knowledge discovery from commercial conversion. --- # 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/knowledge-layer-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.