WordPress and site builders

The setup is the same everywhere: forward the site’s /work address to SimplifyLocal. Some hosts let you add that rule; some don’t.

Check where the DNS lives first

The rule can go at the DNS layer instead of the host. If the domain’s DNS is at Cloudflare, with Cloudflare’s proxy on, use the Cloudflare page regardless of where the pages are built. A site built on GoDaddy Builder, Squarespace or Wix but served through Cloudflare connects this way.

In the wizard, pick Cloudflare on the Hosting step even if the app detected something else.

WordPress

WordPress itself has no setting for this. The rule goes on the web server underneath it:

• Managed or shared hosting on Apache (cPanel, Bluehost, A2 and similar): Apache, in the site’s .htaccess.
• A VPS running Nginx: Nginx.
• DNS at Cloudflare: Cloudflare.

If you are not sure which applies, the Hosting step’s detection is a reasonable first guess. If it reports a host, start with that page.

Wix, Squarespace, GoDaddy Builder, Shopify

These builders don’t let you add a forwarding rule, so there is no snippet for them. Unless the domain’s DNS is at Cloudflare (see above), the connection can’t be made yet.

In the wizard, choose Wix, Squarespace, GoDaddy Builder, or other on the Hosting step, or Other (my host isn’t listed) on the Setup step. The app offers:

• A ready-to-paste prompt for the host’s built-in AI helper, for hosts that do allow a redirect or proxy rule.
• An email link to help@simplifylocal.app with the rule attached.
• A waitlist form (Add me to the waitlist). The app emails you when the host is supported, and the rest of setup continues in the meantime.

If you later move the site to a supported host, open Setup, follow See details on the host notice, and press Check again. I switched hosts. to re-run detection.