> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/onboarding/lead-gen/wordpress-+-sfmc/wordpress-installation-no-code.md).

# Wordpress Installation \[ No Code ]

How to add your wordpress site to Edgetag

**Here ere is a step by step guide;**

1. Go to app.edgetag.io  and create your account
2. Ensure you log in \[ magic link in your inbox ];  Note: we use magic links to login; check SPAM in case email is not in your INBOX
3. If you are HIPAA compliant, please email us at <support@blotout.io>
   1. stop here
4. If not, say No to HIPAA Compliant option
5. Choose WordPress as your option to get started by following these [instructions](/installation/wordpress/installation.md)
6. Since you are a Lead Gen Site, we recommend you skip the Consent Banner step
   1. If you use Consent, you can say Yes and do the needful \[ self explanatory ]
7. You are now ready to add your Ad Platforms that drive leads; Note:  we recommend we started testing your setup
   1. If you use Meta Lead forms, we anticipate you are sending this to your CRM directly
   2. If you need help to collect Meta Lead forms, email <smblead@blotout.io>&#x20;

Audio/Visual Guide:  < loom video >


---

# 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.edgetag.io/onboarding/lead-gen/wordpress-+-sfmc/wordpress-installation-no-code.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.