How it works
Three checks before a country decision.
A browser-supplied country header alone is never enough. The source only trusts a request that passes the configured origin token and viewer-address checks.
Cache-aware setup
Configure CloudFront before enabling.
Forward CloudFront-Viewer-Country and CloudFront-Viewer-Address to WordPress, and set the custom origin token. Keep personalized HTML uncached or include country in the CloudFront cache key. Account and checkout pages should never be publicly cached.
A CDN hit can bypass WordPress entirely, so verify the real distribution with at least two countries and the direct origin. The isolated release tests did not include a customer AWS distribution.
Common questions
Know the boundaries.
Does it need MaxMind or paid WPLocation credits?
No, not when CloudFront provides the verified country. A local licensed MMDB is optional fallback. Your AWS distribution and transfer charges are separate.
Can I use it without CloudFront?
No. Do not enable this source for a direct-origin site. Free can continue using a locally licensed GeoLite2 Country database.
Does a verified country make content private?
No. IP location is approximate, and a CDN can serve cached content before WordPress runs. Use authentication and access controls for confidential information.
How are downloads and licensing handled?
The add-on will be delivered through your WPLocation account under the parent Pro license. Every Pro, Agency and lifetime plan includes it for its covered sites when the compatible release becomes available. No separate CloudFront license key or purchase is required. AWS infrastructure charges are separate.
Ready to connect your distribution?
Start with the verified source.
Get Pro for your current workflows. CloudFront Country Source 1.0.2 will appear in your licensed account when its paid package is released; then follow the source and cache setup guide before enabling it.
