> 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/apps/reputation.md). # Reviews Monitor your online reputation, solicit feedback from patients, and publish to your website with a click of a button. **Why do reviews matter for your practice and your website?** 1. Fresh Content: Reviews are a form of fresh content that can help your website stay relevant and attract more visitors. Search engines like to see fresh content, so regularly publishing reviews can help boost your website's rankings. 2. Keywords: Review pages often include specific keywords that people might use when searching for products or services related to your business. By including these keywords in your reviews, you can help your website rank higher for those specific keywords and phrases. 3. User engagement: Reviews can also help improve user engagement on your website. When users find the reviews helpful and informative, they are more likely to spend more time on your website, which can help lower your bounce rate and signal to search engines that your website is valuable to users. 4. Social proof: reviews can act as a kind of social proof, showing potential customers that other people have tried and liked your products or services. This can help boost your credibility and authority, which can in turn help boost your search engine rankings. Want some help getting reviews from patients? Log in to your DoctorLogic Dashboard and use the Review Request tool! --- # 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/apps/reputation.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.