Note: We do not recommend using Cloudflare as a solution for HTTPS. However, if you prefer to use your root domain (yourdomain.com) instead of the www domain (www.yourdomain.com) as the main domain for your Strikingly site, you can achieve this by adding a CNAME record for the root domain.
Requirement:
- A Premium Account from Strikingly
- A custom domain (if you don't have a domain yet, you can purchase one from us)
- A Cloudflare account
Do you want to use your root domain (yourdomain.com) as your main domain for your Strikingly site instead of the www domain (www.yourdomain.com)? You can do that by adding a CNAME record for the root domain. If your domain registrar does not allow this setup, you can use Cloudflare DNS settings. This guide will walk you through it.
- Step 1: Connect to Your Custom Domain on Strikingly
- Step 2: Add Your Domain to Cloudflare
- Step 3: Add a CNAME record on Cloudflare
- Step 4: Change Your Domain's Nameserver on your Registrar
- Step 5: Set up a URL forwarding with Cloudflare Page Rules
- Step 6: Wait for the records to take effect
Step 1: Connect to Your Custom Domain on Strikingly
1. Go to your Strikingly site editor, and click SETTINGS > Domains.
2. Enter your custom domain in the "Connect a Domain You Already Own" box, such as "yourdomain.com". (without https:// or http:// or /).
3. Click "UPDATE".
Note:
- Type your domain in lowercase to avoid the "Page not found" error when accessing your site
Step 2: Add Your Domain to Cloudflare
1. Sign in to your Cloudflare account or sign up if you don't have one (it's free).
2. Click "+Add site" (if you just sign up, you can skip this).
3. Enter your site:
4. Select the free plan and Click "Continue".
5. Wait for Cloudflare to finish scanning for existing DNS records.
Step 3: Add a CNAME record on Cloudflare
1. Look for existing CNAME and A records for www.
2. Delete the existing CNAME and A records (only for www).
3. Click "+Add record".
4. In the "Type" field, select CNAME
5. In the "Name" field, enter @
6. In the "Target" field, enter cf-dns.strikingly.com
7. Make sure the cloud under "Proxy status" is in orange.
8. Click "Save".
9. Click "Continue".
Step 4: Change Your Domain's Nameserver on your Registrar
1. You will be redirected to a guide on how to change your nameservers.
2. Sign in to your domain registrar.
3. Change the nameserver to Cloudflare's.
4. Wait for the nameserver update. It can take a few hours to 24 hours.
5. Once it's done, you can click "Done, check nameservers".
Step 5: Add an A record for www and Set up a URL forwarding with Cloudflare Page Rules
1. Go back to your Cloudflare account.
2. Click on "Website" then click on "DNS".
3. Create a DNS record for the www subdomain.
- It can be an A record with the
192.0.2.1value OR - An AAA record with the
100::value.
The new DNS record must also have Cloudflare’s proxy enabled (the cloud icon must be orange) to enact the Page Rule behavior you will create.
4. Next, click on "Rules"
5. Then go to "Redirect Rules ".
6. Bulk Redirects > Create bulk redirect list.
7. Name your redirect list and click "Next".
8. Select "Or, manually add URL redirects"
9. Add your redirect Source URL (for example: https://www.domain.com, http://www.domain.com...) and Target URL. Your target URL must include https:// before the root/naked domain. (for example: https://domain.com)
10. Select Edit parameters > Preserve query string, Subpath matching, and Preserve path suffix.
11. Select Next > Next > Continue to Redirect Rules.
12. Select your list > Save and Deploy.
Step 6: Wait for the records to take effect
Now that you've set up the domain records. Please allow a few up to 48 hours for the changes in the domain records to take effect globally. Be sure to clear your browser cache before you check to see if the domain is working.
Note:
We do not recommend using Cloudflare as a solution to HTTPS anymore. However, if you still want to use your root domain (yourdomain.com) as your main domain for your Strikingly site instead of the www domain (www.yourdomain.com), you can do that by adding a CNAME record for the root domain. Do this at your own risk, as this solution may prevent your other DNS records such as MX records from working properly.
If your site doesn't go online after 48 hours, contact us at support@strikingly.com or chat with us and include a screenshot of your domain settings, so we can help!