The SEO Supercharger (w/ Cloudflare connection)

Quick Summary


The SEO Supercharger is an included feature for the quick HTML embed. It serves your blog as flat static HTML that is faster and easier for Google and AI tools to read. After the one-time setup, it runs on its own.


If you use the Shopify app, the WordPress plugin, an SDK (most AI builders), or the API, skip this step as all benefits below are already active on your account. Not sure which path you are on? Click the chat bubble in the bottom right and we will tell you.


How to Activate the SEO Supercharger

To activate the SEO Supercharger, you need to complete these two steps:


Step 1: Connect Cloudflare
Step 2: Generate your Cloudflare API token


Already connected but something is not working? Jump to Troubleshooting.


In this document:


Why Cloudflare?


The SEO Supercharger uses a free Cloudflare account so your posts can have clean URLs and show up properly in Google and AI search. As a bonus, it also helps your site load faster and keeps junk traffic off.


What are the benefits of using a Cloudflare connection?


Enable the SEO Supercharger after the quick HTML embed. It is an included feature. It gives you:


  • Cleaner URLs – Say goodbye to ?p=my-post-name, and hello to /my-post-name/.
  • Lightning-fast loading – Using a unique technology, we are able to flatten your blog posts and load them lightning fast without the use of JavaScript. You'll get fast-loading static blog pages that Google absolutely loves.
  • More AI Mentions – This same static page technology also makes your content easily readable by ChatGPT and other AI bots, increasing your chances of being cited in AI-generated answers across the web.
  • Dynamic Sitemap – You’ll get a live sitemap URL that you can submit to Google Search Console which updates every time you have a new blog post. This will help your new and updated posts index faster.
  • Social Sharing – Shared blog posts on social platforms like Facebook, X, and LinkedIn will display your post’s SEO Page Title, SEO Meta Description, and Featured Image.
  • IndexNow Support - Instantly notify Bing (and ChatGPT) when you publish or update a post, speeding up indexing and visibility in search and AI tools.


Requirements


Before you start, check these four things. Most setup problems come from one of them.


  1. You use your own domain. The SEO Supercharger works with a custom domain such as example[.]com. It cannot be used on a platform subdomain such as yourschool[.]thinkific[.]com, yourstore[.]mybigcommerce[.]com, yourschool[.]teachable[.]com, or yoursite[.]carrd[.]co. Set up your custom domain with your website platform first.
  2. Your domain's DNS is hosted with Cloudflare. In many cases it already is. If it is not, you will need to move your DNS from your current provider to Cloudflare. Our Connecting Cloudflare guide walks you through it step by step. Cloudflare's free plan is all you need.
  3. The Cloudflare proxy is turned on for the record that serves your blog. In Cloudflare, go to DNS and find the record that matches your blog URL. If your blog lives at www[.]example[.]com/blog, that is the www record. If it lives at example[.]com/blog, that is the record named example[.]com (sometimes shown as @). The cloud icon next to it must be orange and say Proxied. If it is grey (DNS only), click it to turn the proxy on.

  1. SSL mode is set to Full. If your website shows a "too many redirects" error after connecting, go to SSL/TLS > Overview in Cloudflare and set the encryption mode to Full.


Moving your DNS to Cloudflare


If your DNS is not on Cloudflare yet, this is the part that worries people the most. Here is what actually happens.


What stays the same


  • Your domain registrar. Your domain stays registered where it is today (GoDaddy, Namecheap, Squarespace, and so on). You are not transferring the domain. You are only telling it to use Cloudflare's nameservers.
  • Your website hosting. Your site keeps running on the same platform. Cloudflare sits in front of it.
  • Your email. Cloudflare scans and copies your existing DNS records, including the MX records that route your email. Your email keeps working as long as those records are in Cloudflare before you switch the nameservers.
  • Your other services. Anything else pointed at your domain (verification records, subdomains, marketing tools) comes along with the DNS records Cloudflare copies over.


What changes


  • The nameservers listed at your registrar change to the two Cloudflare gives you.
  • From then on, you manage your DNS records inside Cloudflare instead of at your old provider. Changes there take effect in minutes, not hours.


Is there downtime?


Normally, no. Your old DNS keeps answering until the nameserver change spreads, and Cloudflare answers with the same records afterward. Visitors never notice the switch.


Can I undo it?


Yes. If you ever want to go back, change the nameservers at your registrar back to your previous provider's and your DNS is served from there again. Nothing is deleted.


Two things to check before you switch the nameservers


  • Review the records Cloudflare found in the quick scan and compare them with the list at your current DNS provider. If anything is missing (email records are the important ones), add it in Cloudflare before you change the nameservers.
  • Make sure the proxy (orange cloud) is turned on for the record that serves your blog. See the requirements above.


Not sure about any of this? Click the chat bubble in the bottom right and send us your domain name. We will look at your DNS with you before you change anything.


Specific Platform Instructions


Some website platforms need a specific DNS setup in Cloudflare. If your platform is listed here, set this up before you generate your API token.


BigCommerce


If your website is built using BigCommerce, it is required that your DNS record is set up as a CNAME record. If your DNS is set up as an A record, you will need to switch it.


BigCommerce is itself hosted on Cloudflare, so this is an "Orange-to-Orange" setup. For BigCommerce's own guidance, see their Cloudflare for Performance and Security article.


  • If your domain is a naked domain, such as "example[.]com", create your CNAME record pointing "@" to "shops.mybigcommerce.com".

  • If your domain uses a subdomain, such as "www.example[.]com", create your CNAME record pointing your subdomain (i.e. "www") to "shops.mybigcommerce.com".


LearnWorlds


If your website is built using LearnWorlds, it is required that your DNS record is set up as a CNAME record. If your DNS is set up as an A record, you will need to switch it.


  • If your domain is a naked domain, such as "example[.]com", create your CNAME record pointing "@" to your LearnWorlds domain (example.learnworlds.com).

  • If your domain uses a subdomain, such as "www[.]example[.]com", create your CNAME record pointing your subdomain (i.e. "www") to LearnWorlds domain (example.learnworlds.com).


Framer


Framer has its own notes in the DropInBlog integration guide for Framer.


If you have questions about transferring your DNS to Cloudflare, turning on the Cloudflare proxy, or anything else, click the chat bubble in the bottom right.


Troubleshooting



The Cloudflare record for your blog's domain is not proxied. Go to DNS in Cloudflare and turn the proxy (orange cloud) on for the record that matches your blog URL. See Requirements above for how to find the right record.


Your site shows "too many redirects"


Go to SSL/TLS > Overview in Cloudflare and set the encryption mode to Full.


DropInBlog says it cannot find your domain, or your API token does not have permission


The API token was created in the wrong Cloudflare account, or by a user who does not have permission to manage your domain. See Who should create the token in the API token guide.


Your blog page shows a Cloudflare message, or nothing at all


To wrap your blog in your site's design, DropInBlog reads the HTML of your blog page. Cloudflare's bot protection sometimes blocks that read because it does not look like a normal visitor. When that happens, the page where your blog should be shows a Cloudflare message instead (often the "Verify you are human" checkbox), or it shows nothing at all.


Cloudflare's own security products are the cause here, not your website platform or DropInBlog.


First, make sure AI bots are not blocked.


In Cloudflare, go to Security > Settings > Bot traffic and find Configure AI bot policies.


Set Search, Agent, and Training to Allow (do not block).

Blocking these also blocks the AI tools the SEO Supercharger is designed to reach, so they should be allowed regardless. If your account still shows the older Block AI bots option instead, set it to Do not block.


If you are on Cloudflare's Free plan


Message us through the chat bubble in the bottom right and include your blog URL. We will look at what is blocking the read and sort it out with you.


If you are on Cloudflare's Pro plan or higher


You can keep bot protection on for everyone else and allow only DropInBlog through, using a private token that is unique to your blog.


  1. In DropInBlog, go to Settings, scroll to SEO Supercharger, and click Copy next to Crawler Access Token. (Don't see it? Send us a message and we will enable it on your blog.)

  1. In Cloudflare, go to Security > Security rules. Click Create rule, then select Custom rules from the dropdown.

  1. Name the rule DropInBlog crawler.
  2. Under When incoming requests match, set the field to Header, the header name to x-dib-token, the operator to equals, and the value to the token you copied from DropInBlog.

  1. Under Then take action, choose Skip.
  2. Under WAF components to skip, check All Super Bot Fight Mode Rules.
  3. Open More components to skip and check User Agent Blocking and Browser Integrity Check.

  1. Click Deploy.

  1. Back in DropInBlog, go to Settings, scroll to SEO Supercharger, and click Refresh HTML.


The expression preview in Cloudflare should look like this (with your own token):


(any(http.request.headers["x-dib-token"][*] eq "your-token-here"))


The token only tells Cloudflare that a request came from DropInBlog. It cannot be used to access your Cloudflare or DropInBlog account.


Still not working?


Some sites have extra rules from a security plugin, a hosting provider, or an older Cloudflare setup. Message us through the chat bubble and include your blog URL. We can see exactly what blocked the read and tell you which setting to change.


FAQs


Can I use Cloudflare for my blog only?
No, your domain's DNS can be hosted by only one provider at a time. If you wish to use Cloudflare for DropInBlog, you must switch your domain's DNS provider to Cloudflare.


Do I have to switch where my domain is registered?
No, there's no need to change your domain's registrar. You only need to update the domain's nameservers to those provided by Cloudflare.


What about all of my DNS records such as email (MX)? Will they transfer over to Cloudflare?
Yes, Cloudflare automatically imports all your existing DNS records, including email (MX) records, into your Cloudflare account. It is still worth comparing the imported list with your old provider before you change the nameservers.


Will my website go down while I switch?
Normally, no. See Moving your DNS to Cloudflare above.


Cloudflare is connected, but my featured images are not showing.
The Cloudflare DNS record for your blog's domain is not set to proxy mode. In Cloudflare, go to DNS, find the record that matches your blog URL, and turn the proxy (orange cloud) on so it says Proxied.


Cloudflare is connected, but I encounter a "Not Found" error when clicking on a post.
The Cloudflare DNS record for your blog's domain is not proxied. In Cloudflare, go to DNS, find the record that matches your blog URL, and turn the proxy (orange cloud) on so it says Proxied.


Cloudflare is connected, but my blog page shows a Cloudflare message or is blank.
Cloudflare's bot protection is most likely blocking DropInBlog from reading your site. See Troubleshooting above.


What should I do if my blog URL changes?
If you change your blog URL, you will need to reconnect Cloudflare to ensure it maps to your new URL. This is necessary whether you are changing your domain (e.g., from "website1.com" to "website2.com" or just the URL path (e.g., from /blog to /news).


Does the SEO Supercharger cost extra money?
No. It is included in your DropInBlog plan. We pay for the background delivery so you don't.


Do I need a paid Cloudflare account?
No. Cloudflare's free plan is enough. No credit card required for this.

Updated on: 12/09/2026