Build geolocation rules around a deliberate delivery plan. Local lookup can avoid a per-visitor API request, while public caching and search visibility need their own checks.
Start with the rule, then test the source
Use WPLocation Free from WordPress.org for posts, pages, categories and selected content sections. Keep Free active when adding Pro. Check an allowed country, a denied country and an unknown result before testing the real page.
IP country detection is approximate. A VPN, proxy or missing country record can change the result. Use authentication and authorization for private content.
Keep local lookup lightweight
A configured local GeoLite2 Country database keeps visitor-IP lookup on the server and avoids an HTTP lookup for each visitor. Database downloads are separate, explicit operations; automatic update checks are opt in.
Measure the page’s total response time on your own host. The rule lookup is only one part of a request; the theme, other plugins, database and external services also affect performance.
Make caching correct before making it fast
A shared cached page can contain the wrong country’s content. The currently published Free plugin requests uncached frontend HTML because targeted content can appear in secondary queries and content sections. It also scopes its REST cache headers to country-aware post, page and search reads.
Keep static assets cached. Use an object cache where appropriate. Before enabling shared HTML caching, use a tested country-aware cache configuration and repeat allowed/denied requests after warming the cache. Checkout, accounts and license responses need private delivery. Follow the full cache and CDN checklist.
Give search engines discoverable URLs
Google explains that it may not discover every variation of a page that changes by perceived country. For important regional landing pages, use separate crawlable URLs, visible region links and the appropriate canonical and hreflang configuration in your SEO or multilingual system.
WPLocation’s country visibility rules do not create translations, regional URL structures, canonicals or hreflang annotations. Those remain separate configuration responsibilities. Do not assume a country rule improves rankings or automatically makes a site SEO safe.
Google’s guidance on locale-adaptive pages ↗
Keep crawler and visitor rules consistent
Do not exempt a request merely because its user agent says Googlebot. Apply the same country behavior to a crawler and a visitor from that country. Keep important public content reachable through your chosen URLs, and check the resulting HTTP status, canonical, robots directives and sitemap entry.
Geo Redirects in Pro can offer a regional page with a visitor choice. Test direct links, loop prevention and non-targeted fallback before activating a redirect. See the Geo Redirects guide.
Verify the full journey
- Record a response-time baseline and the country-source status.
- Test the saved rule with allowed, denied and unknown countries.
- Test the public URL with cold and warm caches.
- For Pro, test the catalog, direct product, add-to-cart, existing cart and checkout.
- Inspect search access through Search Console and your SEO tool’s actual public output.
- Repeat these checks after changing the theme, cache, CDN, rules or plugin versions.
Need help? Send a safe reproduction report with versions, source, expected result and actual behavior.
Contact WPLocation with your software versions and the result you expected. Keep keys and customer data private.