> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/add-ons/website-translation.md). # Website Translation Incorporating a website translator is crucial for expanding the reach and accessibility of digital content on a global scale. A website translator allows users from diverse linguistic backgrounds to navigate and comprehend information in their preferred language, breaking down language barriers and fostering inclusivity. Practices can engage with a broader and more diverse audience by offering content in multiple languages, increasing user engagement, satisfaction, and potential customer acquisition. In the interconnected world of the internet, a website translator becomes a powerful tool for enhancing international communication, facilitating cross-cultural understanding, and promoting the dissemination of information across borders. It broadens the user base and demonstrates a commitment to a diverse audience, making the website more user-friendly and aligning with inclusivity and cultural sensitivity principles in the digital landscape. Ready to make sure your website is available to visitors in other languages? **Contact your CSM today to ask about adding this important service.** {% content-ref url="/pages/Hkecq1Ax8z1BewLgMH0U" %} [The Customer Success Manager](/docs/contact-support/the-customer-success-manager.md) {% endcontent-ref %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.doctorlogic.com/docs/add-ons/website-translation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.