> 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/buyer-guides/choosing-knowledge-layer-partner.md). # Choosing a knowledge-layer partner A buyer guide for evaluating a partner to build an AEO and AI-search knowledge layer. A knowledge-layer partner should understand information architecture, SEO/AEO, web implementation, editorial governance and measurement. Ask whether the proposed solution: * keeps content portable, * distinguishes the knowledge layer from the main commercial site, * has a canonical and internal-linking strategy, * includes trust and evidence standards, * measures indexing, search visibility, referrals and conversions, * avoids guarantees of AI citations, * and can be maintained after the initial build. The platform matters less than the operating model. A good partner should be able to explain how the content remains useful even if the underlying documentation technology 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/buyer-guides/choosing-knowledge-layer-partner.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.