> For the complete documentation index, see [llms.txt](https://docs.iheartjane.com/partner-success/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iheartjane.com/partner-success/ecommerce-premium/onboarding-a-wp-engine-site-into-cloudflare.md).

# Onboarding a WP Engine Site into Cloudflare

This guide walks through connecting a WP Engine-hosted site to Cloudflare for DNS management. The key step is replacing the default A records that Cloudflare auto-imports with a single CNAME record pointing to WP Engine.

### Step 1: Get the CNAME Target from WP Engine

Before touching Cloudflare, you need to grab the correct CNAME value from WP Engine.

1. Log in to [**my.wpengine.com**](http://my.wpengine.com).
2. Click **Sites** in the left sidebar.
3. Find and click into the site you're onboarding.
4. Under **Manage**, click **Domains**.
5. On the primary domain row, click the **three-dot menu** (⋮) on the right side.
6. Click **View DNS Details**.
7. A popup will appear showing DNS details for advanced network. Copy the **CNAME** value — it will look something like `wp.wpenginepowered.com`.

<figure><img src="/files/nZP084QqPI3sQZBY5Nbn" alt=""><figcaption></figcaption></figure>

> **Hang on to this value.** You'll need it in the next step.

***

### Step 2: Set Up DNS in Cloudflare

When you add a domain to Cloudflare, it will automatically scan and import your existing DNS records. This is mostly fine, but there's one important change you need to make: the **A records for the root domain need to be replaced with a CNAME record**. Your DNS auto-import will likely look something like this:

<figure><img src="/files/BrqRtsBWRjoOLzh2CBbf" alt=""><figcaption></figcaption></figure>

#### Remove First Auto-Imported A Record

Cloudflare will typically import two A records for the root domain pointing to WP Engine IP addresses (e.g., `141.193.213.10` and `141.193.213.11`). We’ll delete one and update the other. **Make a note of the IP addresses you see, if something isn’t working correctly after swapping to the CNAME you can simply re-add the A records.**

*💡 If there is only one A record, skip to the “Change” section below. Do NOT delete both records,  traffic to your site may go down if you have no A or CNAME records at the root.*

1. In Cloudflare, go to **DNS** in the left sidebar.
2. Find any **A** records where the **Name** matches your root domain (e.g., `premiumwpcf.com`).
3. Click **Delete** on the first one.
4. Confirm the deletion.

<figure><img src="/files/QhzTv9fVelnuy0BamgIw" alt=""><figcaption></figcaption></figure>

#### Change A record CNAME Record for the Root Domain

Now update the remaining A record to a CNAME that points your root domain to WP Engine.

1. Click on the other **A record**.
2. Set **Type** to `CNAME`.
3. Set **Name** to `@` (this represents the root domain).
4. Set **Target** to the CNAME value you copied from WP Engine (e.g., `wp.wpenginepowered.com`).
5. Make sure **Proxy status** is toggled on (orange cloud icon).
6. Click **Save**.

<figure><img src="/files/pdr9wagCE1XDHEMayIJb" alt=""><figcaption></figcaption></figure>

#### Verify the www Record

Cloudflare should have auto-imported a CNAME record for `www` already. Double check that it exists and points to the same WP Engine target (`wp.wpenginepowered.com`) with the proxy toggled on.

***

### Step 3: Review All Records

Before finishing, do a quick scan of all your DNS records in Cloudflare. You should see something like this:

| Type  | Name     | Target                                                  | Proxy                  |
| ----- | -------- | ------------------------------------------------------- | ---------------------- |
| CNAME | @ (root) | [wp.wpenginepowered.com](http://wp.wpenginepowered.com) | Proxied (orange cloud) |
| CNAME | www      | [wp.wpenginepowered.com](http://wp.wpenginepowered.com) | Proxied (orange cloud) |
| MX    | @ (root) | *(your mail server)*                                    | DNS only               |
| TXT   | @ (root) | *(your SPF record, etc.)*                               | DNS only               |

<figure><img src="/files/jrHixOOgO3ugO4hPhNga" alt=""><figcaption></figcaption></figure>

> **Don't touch** your MX, TXT, or other records unless you have a specific reason to. These handle email and domain verification and should carry over correctly from the auto-import.

***

If you handled this step AFTER onboarding the domain, you’re done! Traffic should now properly be passing through this Cloudflare zone before reaching your WPEngine site. If you handled this step DURING onboarding, continue on to Step 4, “**Update your Domain Nameservers”** in our [onboarding guide!](/partner-success/ecommerce-premium/jane-premium-onboarding-guide-cloudflare.md)&#x20;

***

### Why Replace A Records with a CNAME?

Our embedded menu uses a Cloudflare Worker to reverse-proxy traffic on a specific path on your domain (e.g., `yourdomain.com/menu`). If your root domain uses A records pointing to WP Engine's IPs, an "Orange-to-Orange" conflict prevents the Worker from intercepting traffic on the root domain — so `yourdomain.com/menu` won't work even though `www.yourdomain.com/menu` does.

Switching to a proxied CNAME fixes this. See [Cloudflare's WP Engine guide](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/wpengine/) for more detail.