Help4 Net WordPress CDN, GeoDNS and WAF
| Path | Use it when | Next step |
|---|---|---|
| Free plugin | You want to install the WordPress connector and start plugin-managed onboarding | Download the plugin directly from Help4.net. |
| $8 Pro | One production domain needs Help4 DNS, GeoDNS, full proxy, WAF controls, broader POP reach, and stronger cache controls | Buy through the Help4 Network CDN catalog. |
| $20 Enterprise starting path | The full site needs managed GeoDNS proxy delivery, origin shielding, WAF policy, and advanced operational visibility | Request an Enterprise scope through Help4 Network. |
Why the layers matter
A CDN cache and a managed proxy solve different parts of delivery.
The WordPress plugin handles onboarding and sync. DNS and GeoDNS decide where traffic should go. Proxy and WAF controls inspect and protect requests before they reach the origin. The right plan depends on whether the goal is asset acceleration, production route control, or full-site protection.
Performance
Reduce unnecessary origin trips and use edge cache controls suited to the site.
GeoDNS
Steer requests using managed routing policy instead of relying on one fragile path.
WAF
Apply managed request controls and virtual-patching workflows ahead of WordPress.
Origin safety
Reduce direct exposure and keep controlled fallback behavior for full-proxy deployments.
Need the CDN path selected?
Start with the site and the problem, not a feature checklist.
Send the domain, current DNS/CDN, traffic regions, cache problem, security concern, ecommerce/login behavior, and whether nameserver changes are acceptable.
WordPress delivery checklist
Choose a CDN, GeoDNS, or managed WAF from the traffic problem you actually have.
A WordPress CDN can cache public files and pages closer to visitors. GeoDNS can steer traffic toward an appropriate regional endpoint. A managed full proxy can add request filtering, cache control, and origin protection in front of WordPress. Those jobs overlap, but they are not interchangeable, so Help4 starts with the domain, host, login and checkout behavior, traffic regions, and current failure mode.
Start with the free plugin
Use the Help4 CDN plugin to connect WordPress to the Help4 Net workflow and inspect the current site before changing authoritative DNS. This path is useful when you want guided onboarding and visibility without immediately moving the whole domain behind a proxy.
Add regional delivery when it helps
The Pro path adds Help4 Net CDN and GeoDNS capabilities for sites that need broader delivery or regional traffic steering. Before changing nameservers or records, inventory the origin, email DNS, third-party verification records, redirects, API endpoints, and authenticated routes so acceleration does not break business operations.
Use managed proxy and WAF controls for higher-risk sites
Stores, membership sites, public campaigns, and frequently attacked WordPress installs may need a managed full-proxy design. Help4 verifies public edge delivery, direct-origin restrictions, cache bypass for private requests, fallback behavior, and the exact hostnames that should remain reachable.
What Help4 checks before launch
We verify HTTPS and canonical redirects, origin reachability, WordPress login and API exclusions, cache behavior, mobile rendering, security headers, sitemap and robots access, email DNS preservation, and a rollback route. The goal is not merely a faster speed-test screenshot; it is a site that remains usable, indexable, and recoverable after traffic moves through the edge.