> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/onboarding/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/onboarding/content-overview.md).

# Content Overview

The content portion of your site build includes the following:

#### Site Review

Our team, including your PM and Content Writer will do an in-depth review of your current site. This includes checking for any unique pages, duplicated content, and high-performing keywords. We take a look at any pages currently performing well for you and determine what can and can't be pulled over to your new DoctorLogic site.

#### New Content Creation

Each project gets assigned a writer. The writer will work closely with the PM to ensure that the content for you site is unique and performs well in terms of SEO.

#### New Content QA

We have a dedicated in-house editor who reviews all sites before they are delivered. Our editor reviews for grammar and spelling accuracy as well as compared against client notes to make sure that specifications have been met.


---

# 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://help.doctorlogic.com/onboarding/content-overview.md?ask=<question>&goal=<endgoal>
```

`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.