Edge and performance
Cloudflare for ecommerce stores
Cloudflare is where we put the parts of an ecommerce estate that sit outside the store platform: DNS for the whole domain, redirect maps, hosting for content sites and headless storefronts, image and asset delivery, and protection for the forms people abuse. What it is not is a layer to force in front of a hosted commerce platform that already serves its own storefront from its own network. Getting that boundary right is most of the value.
Cloudflare
Edge and performance · by Cloudflare. A text wordmark, not a logo: we are not affiliated with the vendor and make no claim to its trademarks.
What we do with it
The work inside Cloudflare
DNS as the control point for the whole domain
A brand's domain usually points at several systems: the store, a content site, email, a help centre and a status page. Holding DNS in one account with change control means adding a market site or moving a subdomain is a planned edit with a record of who changed what, rather than an afternoon of guessing.
Hosting the layers the platform does not serve
Content sites, campaign microsites, tools and headless storefronts are deployed to run close to visitors, with server rendering where a page needs it. That gives fast first responses in both countries a North American brand sells to, without operating servers or paying for capacity that sits idle overnight.
Redirects and routing at scale
A replatform or a URL restructure produces thousands of redirects, and putting them in a theme or an app usually means a slow chain of hops. Handling them at the network edge keeps them fast and centrally auditable, which matters when a crawler is working through the old structure for weeks.
Caching decided by page type
Static pages, images and assets can be cached aggressively. Anything showing price, stock, a cart or a logged-in state cannot. We write cache rules per route with explicit bypasses rather than a blanket setting, because a cached price is a customer service problem rather than a performance win.
Forms, abuse and crawler policy
Lead forms and newsletter signups attract automated submissions, and a challenge on those keeps the list clean without asking real customers to solve puzzles. Rules for automated traffic are written deliberately, with search and AI crawlers allowed on purpose rather than caught by a broad block.
When it fits
Cloudflare is the right tool when
Brands running more than one system on one domain
A store on a hosted platform plus a content site elsewhere needs routing that keeps everything on one hostname. That decision lives at the network layer.
Stores replatforming or restructuring URLs
Large redirect maps need somewhere fast, testable and reversible to live. Doing it at the edge also makes it easy to see which old URLs are still being requested months later.
Custom and headless builds
A storefront or tool that has to be hosted somewhere benefits from running close to shoppers, with deployment previews and quick rollbacks as part of the workflow.
Merchants dealing with form spam or scraping
Where junk signups pollute the email list or a competitor scrapes pricing all day, rules and challenges applied at the edge are cheaper than filtering the mess afterwards.
What to watch
Where accounts drift
Facts about defaults and costs, not criticism. These are the settings we check on every account.
Hosted platforms manage their own delivery
Shopify and similar platforms serve the storefront and checkout through their own infrastructure and specify how the domain must be configured. Follow the platform's documented setup rather than trying to insert another layer in front of it.
DNS deserves the same care as a deployment
A single incorrect record can take a store offline for as long as it takes to notice. Access should be limited, changes reviewed by a second person, and the existing configuration exported before any migration begins.
Cache rules can outlive their purpose
A rule added for a campaign in March is still serving something in November. Every rule needs a note explaining why it exists, and the set needs a periodic read-through against what the site now looks like.
Blocking rules can catch useful visitors
Aggressive automated traffic rules can affect the crawlers, monitoring services and platform integrations a store depends on. Test changes against what is genuinely required, and check server responses for search crawlers after any tightening.
Can we put a proxy in front of our hosted store to make it faster?
Generally no, and it is not needed. Hosted commerce platforms deliver the storefront and checkout over their own global network and document how the domain should point at them. Speed gains on those stores come from the theme, apps and images, not from adding another network layer.
What does the edge layer actually do for an ecommerce brand?
It handles everything around the store: DNS for the estate, redirects, hosting for content and custom builds, asset delivery, form protection and crawler rules. On a store using a hosted platform that is a supporting role, and it is still the part most likely to be misconfigured.
How should a large redirect map be handled during a migration?
Build it from the old site's crawl and its search data, apply it in one place so each old URL reaches its destination in a single hop, then monitor which sources are still being requested. Keep the map for at least a year, because crawlers return to old URLs long after launch.
Will bot rules stop search engines or AI crawlers reaching the site?
They can if written broadly. Decide which automated visitors you want, allow those explicitly, and verify afterwards by checking the responses returned to known crawlers. Blocking an AI crawler is a legitimate business decision, but it should be deliberate rather than a side effect.
Delivered through
Works alongside
Find the leak.
A free Growth Analysis ranks what your store should fix first, by revenue at stake.