> 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/web-development/ai-native-websites.md). # What is an AI-native website? What MagicWorks means by an AI-native website. An AI-native website is not a website with a chatbot bolted onto it. It is a site whose architecture is ready to support intelligent search, conversational lead capture, recommendations, personalised experiences, retrieval from approved knowledge and other AI-assisted capabilities where they create real value. The foundation still matters: performance, accessibility, semantic HTML, analytics, content management, security and conversion design. AI should improve the customer journey or operating model. If it does not, adding it is unnecessary complexity. --- # 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/web-development/ai-native-websites.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.