> For the complete documentation index, see [llms.txt](https://docs.3techagency.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3techagency.com/help-center/setup-and-account/setup-checklist.md).

# Setup checklist

Get from installation to a safe first workflow.

1. Confirm **WordPress 7.0 or newer** and **PHP 8.1 or newer**.
2. Upload the WP AI Manager ZIP under **Plugins > Add New > Upload Plugin** and activate it.
3. Enter your license on the Freemius activation screen.
4. Install a WordPress AI Connector and add its key under **WordPress Settings > Connectors**. Approve it if your site uses Connector Approval.
5. Open **WP AI Manager > AI Chat**. A green status dot means the provider works. **No AI provider connected** means step 4 is not finished.
6. Optional: pick models under **Settings > AI Models**. If you skip it, recommended models are used.
7. Fill in **Site Knowledge > Brand Kit** (use **Auto-fill from this site**) and a short **Context**.
8. Check **Integrations** for the builder, SEO, form, WooCommerce or backup plugin you plan to use.
9. Run **Site health check** from Playbooks. It is read-only. Then try **Write a blog post**, which saves a private draft.

Home's **Needs you** area and **Settings > Onboarding** track these steps. See [Install and activate](https://docs.3techagency.com/documentation/start-here/install-and-activate).


---

# 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://docs.3techagency.com/help-center/setup-and-account/setup-checklist.md?ask=<question>&goal=<user_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.