Cloudflare services
Not every Cloudflare service earns its place on day one. For a local news and business site like ours, running on WordPress, the ones that actually pull their weight from the start are DNS, the CDN, SSL/TLS, DDoS protection, the WAF, bot protection, and WordPress-specific tuning through Cloudflare’s plugin and APO. The flashier tools—Workers, Stream, Access, and Pages—are things we grow into rather than launch with. They’re genuinely useful for interactive features, video, locking down admin and staging areas, and any future static or headless build, but none of them are needed to get a solid WordPress site online.
BristolTalks is a local-first publication and business platform made for one place: Bristol, Connecticut. We cover what’s actually happening here, put a spotlight on the small businesses that make the city tick, and build practical, AI-assisted tools that help residents and organizations get answers faster, spot opportunities, and stay plugged into the things that matter around town.
| Product | Why it matters | Plain-language summary | Technical note |
|---|---|---|---|
| Cloudflare DNS | Core now | It points the BristolTalks domain to the right place quickly and reliably. | Cloudflare DNS is an authoritative DNS service; in full setup, Cloudflare becomes the primary DNS provider for the domain. |
| Cloudflare CDN | Core now | It makes pages load faster by serving cached content from nearby Cloudflare locations instead of always pulling from the origin server. | Cloudflare says its CDN caches static and dynamic content across data centers in 335+ cities. |
| SSL/TLS | Core now | It keeps the connection encrypted so visitors can read the site securely. | Cloudflare issues free certificates through Universal SSL and supports an origin certificate for the Cloudflare-to-server connection. |
| DDoS protection | Core now | It helps keep the site online during traffic floods or malicious attacks. | Cloudflare DDoS protection is available on all plans and automatically detects and mitigates attacks. |
| WAF | Core now | It blocks common web attacks before they hit WordPress. | Cloudflare’s WAF is available on all plans and includes managed protection plus custom rules. |
| Bot protection | Strong next step | It reduces junk traffic, scraping, spammy automation, and abusive crawlers. | Free plans get Bot Fight Mode; Pro/Business/Enterprise get Super Bot Fight Mode; Bot Management is an Enterprise add-on. |
| WordPress plugin + APO | Core now for WordPress | It makes a WordPress site much easier to optimize on Cloudflare, with smarter caching and easier setup. | APO lets Cloudflare cache HTML and serve the whole WordPress site from the edge; it is included with Pro/Business and available as a $5 add-on on Free. |
| Workers | Strong next step | It adds custom logic without managing servers. Good for AI widgets, redirects, custom APIs, paywalls, local tools, and maintenance pages. | Workers are serverless functions that scale automatically from zero to millions of requests. |
| Access | Strong next step | It protects admin tools, dashboards, and staging pages behind login rules instead of leaving them public. | Cloudflare Access acts as an identity-aware proxy and is part of Cloudflare One, which has separate Zero Trust plans. |
| Stream | Optional growth tool | It is useful if BristolTalks starts publishing regular video interviews, local explainers, or event clips. | Stream uploads, encodes, stores, and delivers live or on-demand video with usage-based pricing. |
| Pages | Optional and usually future-facing | Good for static landing pages or a later static/headless rebuild, but not the simplest first move for a live WordPress origin. | Pages is a JAMstack platform; Cloudflare also notes that new static/full-stack projects are now generally better started on Workers Static Assets. |
We built BristolTalks to be useful before it tries to be impressive. In practice that means clear information, pages that load fast, access you can count on, and a site people can trust whether they’re on a phone, a laptop, or squeezing in a quick read between errands. For a hyper-local site, that reliability is the whole point. Someone might be checking a Bristol headline from downtown, catching up on a business story after their shift, or opening an article on a shaky mobile signal—and in every one of those moments it should just feel simple, quick, and secure.
The Cloudflare services behind our site.
Cloudflare DNS is what quietly gets people to BristolTalks in the first place—it takes a typed address and points it at our site fast, and it rarely misses.
Technical note: in a full setup, Cloudflare acts as the authoritative DNS provider for the domain, answering every DNS lookup for the site itself.
Cloudflare CDN is the reason pages feel snappy. Instead of every visitor pulling content all the way from our origin server, Cloudflare serves cached copies from a location close to them.
Technical note: Cloudflare’s network caches content across data centers in more than 335 cities, which improves speed and availability while taking load off our origin.
The setup order below isn’t something we made up—it mirrors Cloudflare’s own recommended onboarding path: add the domain, review the DNS records, switch the nameservers, finish SSL/TLS setup, turn on the WordPress plugin, and confirm APO is doing its job if you’re using it.
Practical setup steps
- Add the domain to Cloudflare and review records. Confirm the imported A, AAAA, and CNAME records match the current host, and proxy the records that serve the website. Leave MX/TXT and other non-web records as DNS-only. Change nameservers at the registrar. If DNSSEC is active, disable it first, update the registrar to the Cloudflare nameservers, verify activation, then re-enable DNSSEC if appropriate.
- Set SSL/TLS to Full (strict) after installing a valid origin certificate or Cloudflare Origin CA certificate on the server. Avoid loose SSL mode choices unless there is a temporary migration reason.
- Turn on HTTPS controls. Enable HTTPS redirection and Automatic HTTPS Rewrites to reduce mixed-content problems.
- Install the Cloudflare WordPress plugin. Create a Cloudflare API token from the WordPress template, authenticate the plugin, and use its “Apply Recommended Cloudflare Settings” option to align the site with best practices in a single step.
- Enable APO if BristolTalks stays WordPress-first. APO is the easiest win for performance on a content-heavy WordPress site because it lets Cloudflare cache HTML as well as static assets. Do not stack multiple cache systems blindly; Cloudflare recommends turning off cache plugins during the initial rollout and then testing.
- Verify it works before you call it done. Check for
cf-rayto confirm traffic is flowing through Cloudflare, then confirm APO withCF-Cache-Status,cf-apo-via, andcf-edge-cache.
The prices and plan notes below are pulled straight from Cloudflare’s published application-services pricing. We pay closest attention to APO, the Stream allowances, and whether partial (CNAME) setup is available, because those three directly shape how well a WordPress site performs, how easily we can add video later, and how much flexibility we have in deploying it.
| Plan | Published positioning | Price | What matters | Recommendation |
|---|---|---|---|---|
| Free | Personal or hobby projects that are not business-critical | $0/mo | Includes DNS, CDN, Universal SSL, unmetered DDoS protection, WAF, and baseline bot protection. APO is extra at $5/mo. | Good for testing or pre-launch |
| Pro | Professional websites that are not business-critical | $20/mo annual or $25/mo monthly | Better fit for a serious WordPress publication; APO is included; more security/performance control; Super Bot Fight Mode is included. | Best default choice |
| Business | Small businesses operating online | $200/mo annual or $250/mo monthly | Adds 100% SLA and is the minimum plan for partial CNAME setup if nameservers cannot be changed; stronger support posture. | Use only if DNS/provider constraints or support/SLA needs justify it |
| Enterprise | Mission-critical applications | Custom | Best for high-compliance, high-traffic, always-on operations, custom contracts, and Enterprise add-ons like Bot Management. | Overkill for current BristolTalks unless the site becomes mission-critical infrastructure |