Test and troubleshoot country detection

If a rule is not behaving as expected, separate three questions: Can the local database return a country? Does the saved rule allow it? Does the public page reach WordPress rather than a stale cache? WPLocation provides an administrator-only Diagnostics screen for the first question and saved-result checks in rule editors for the second.

Check the data source

1. Open WPLocation → Diagnostics.
2. Look for a readable GeoLite2-Country source and review its build date. The screen flags missing, unreadable, wrong-type or old data.
3. Use Test an IP address with an IPv4 or IPv6 address you are permitted to test. The local lookup result is shown privately; the test address is not stored or sent to a lookup provider.
4. If the source needs attention, open WPLocation → Settings and fix the licensed MMDB path or MaxMind setup. Then test again.

Check the saved rule

Open the affected Page, Post or Category rule editor, save changes, and use Check the saved result for one expected allowed country and one denied country. For posts, review assigned categories too: all applicable rules must allow the visitor. For Pro products, review their categories and ancestors. An unknown country is hidden by an active restriction.

Check the public delivery path

Purge page and CDN caches, then test the public URL twice from each location. Try a clean browser session so old cookies and browser caches do not affect the comparison. A VPN changes the apparent IP for some requests, but it does not prove what a reverse proxy forwards to WordPress. If the admin test works while public requests fail, review your cache and trusted-proxy configuration.

What to send support

Include the Free and Pro versions, WordPress and PHP versions, database type and build date, the type of rule, expected and actual result for two countries, and the cache/CDN products in use. Do not send license keys, MaxMind keys, full visitor IP logs, or a database backup in an initial support message. Contact support.