Skip to main content
All CollectionsApp Settings
Using an apex / root domain
Using an apex / root domain
Updated over a month ago

To proceed with this setup, you'll need an account with Cloudflare (the Free tier contains all the functionality you’ll need to get this working). You have two options: either purchase a domain directly through Cloudflare, or, if you already own a domain purchased through a different registrar, update your domain's nameservers at your current registrar to point to Cloudflare.

Connect the apex / root domain (or www version) to Movement

Once you have a domain either purchased through, or connected to Cloudflare, you can link your domain to Movement using the same steps outlined in the ‘Add Your Domain to Movement” section above, but omitting the subdomain. You can either use www or non-www version of your domain e.g. www.yourmovement.co or yourmovement.co. In this example, we will use the root domain (yourmovement.co).

  1. Add your root domain to Movement:

2.After adding your root domain, a modal will appear containing instructions on how to set up the CNAME in your DNS records.

3. Login to your Cloudflare account, navigate to “DNS” then hit [+Add Record] on your domain.

4.Under ‘Type’ choose ‘CNAME Record’ from the dropdown. Under ‘Name’ type or paste in the ‘@’ character. Under ‘Target’ type or paste in ‘domains.mvt.so’. Leave the proxy status toggled on to ‘Proxied’ and the TTL field with whatever default value is there. Once everything is correct, hit ‘Save’.

5. Navigate back to the “Custom Domain” section in your Global App Settings in the Movement admin, and you’ll notice your custom domain has a Pending status. DNS can take up to 48 hours to propagate. You can use the refresh button to check the status periodically.

6. Once the changes have propagated, you will see the status change to ‘Active’, and your custom domain will now link to your Movement app.

7. Now, when users click on this link, type or paste it into their browser, they will be taken directly to your app.



Configure www / non-www redirect page rule in Cloudflare

To prevent access errors and avoid SEO penalties from search engines perceiving 'www' and non-'www' versions of your site as duplicates, it's essential to set up a www redirect and an additional CNAME record.

In the example below we will be redirecting our "www" domain to our "non-www" domain (www.yourmovement.so -> yourmovement.so).

  1. Login to your Cloudflare account and click on your domain.

2. Navigate to Rules > Page Rules in the lefthand sidebar.

3. Hit the ‘Create Page Rule’ button.

4. In the URL section, paste or type in your root domain with ‘www.’ in front of it and ‘/*’ after it. E.g. ‘www.yourmovement.co/*’.

5. In the ‘Pick a Setting’ dropdown , choose ‘Forwarding URL’.

6. Select ‘301 - Permanent Redirect’ from the ‘Status Code’ dropdown.

7. In the ‘Enter Destination URL’ section, type or paste in your root domain with ‘https://’ in front of it and ‘/$1’ after it e.g. ‘https://yourmovement.co/$1’.

8. Once everything looks correct, hit the ‘Save and Deploy Page Rule’ button.

9. You will now need to add one more CNAME record for www in your DNS settings.

10. Navigate to “DNS” then hit [+Add Record] on your domain.

11. Under ‘Type’ choose ‘CNAME Record’ from the dropdown. Under ‘Name’ enter ‘www’. Under ‘Target’ type or paste in ‘domains.mvt.so’. Leave the proxy status toggled on to ‘Proxied’ and the TTL field with whatever default value is there. Once everything is correct, hit ‘Save’.

12. Your DNS records should now look similar to the following.

13. You can now share both www and non-www versions of your domain for your community to access your app with 🎉.

Did this answer your question?