Geolocation Troubleshooting

Overview

Geolocation in Cookie Compliance determines which consent experience a visitor sees based on their IP-resolved location. If your banner is appearing (or not appearing) incorrectly for visitors in a specific country, this guide walks through the most common causes and fixes.

Banner Showing for Wrong Region (or Not Showing at All)

Geolocation works on IP address, not browser language or Accept-Language headers. If your banner is appearing incorrectly for visitors in a specific country:

1. Verify the visitor's actual IP-resolved location

Tools like ipinfo.io or whatismyipaddress.com show the resolved location for any IP. Corporate networks, mobile carriers, and VPNs can all cause an IP to resolve to an unexpected country. If a visitor's ISP routes through another country, geolocation uses that resolved location — this is expected behavior.

2. Check your geolocation mode and zone configuration

Log in to the Admin Portal at app.hu-manity.co → Configuration → Laws (scroll to the Geolocation section). Confirm:

• Are you using Managed or Manual geolocation?
• For Manual: Verify the rule for the affected region, and that its law is selected (a rule applies only when its law is on). Other Regions applies to visitors that no enabled law rule matches. Rules also match on your organization's location: if your company is in a region whose law is selected, that rule applies to all visitors. US visitors get no rule at all unless CCPA or Other US State Laws is selected.
• For Managed: The system uses your organization's registered location combined with the visitor's location. If either side is in the EU, it defaults to stricter EU-style behavior. Those per-region rules are read-only until you switch to Manual.

3. Check that configuration changes were published

Changes saved in the Admin Portal only take effect after you publish. Look for an unpublished changes indicator. If you recently updated geolocation settings, make sure you clicked Publish Now.

Configuration Changes Not Reflecting on the Site

New visitors get the published configuration straight away; a tab that already had the site open can keep the old settings for up to an hour. Check in a new private window. If your site still shows old settings, clear your own page caches in this order.

Clear caches in this order

1. Your CDN cache (for example Cloudflare), if your site uses one — Purge everything.
2. WordPress caches (WP Rocket, W3 Total Cache, LiteSpeed, WP Super Cache, etc.) — Clear all.
3. Server-level cache (Varnish, Redis object cache) — Flush if applicable.
4. Browser — Open a new tab or private window. A hard refresh in the same tab keeps the old settings.

After clearing, verify in an incognito/private browser window to eliminate browser-side cached responses.

You can also use the Purge Cache button in the WordPress admin (Settings tab → Technical Settings) to force the plugin to fetch the latest configuration.

Geolocation Not Triggering at All

If the banner ignores geolocation entirely and shows the same experience to all visitors:

Check that your site is connected

Geolocation is a feature of the connected Cookie Compliance service. If your site is in the unconnected (Banner Only) state (no app_id), geolocation rules are not applied — the plugin uses its own local settings with no location awareness. Connect your site through the WelcomeModal or the Admin Portal to enable geolocation.

Check for script loading issues

1. Open DevTools (F12) → Network tab.
2. Search for hu-banner.min.js.
3. If it is missing, blocked, or loading with errors, geolocation cannot run.
4. Common causes: ad blockers, security plugins (Wordfence, Sucuri), or Content Security Policy (CSP) headers blocking the script domain.

Check for script deferral conflicts

Caching and optimization plugins that defer JavaScript can delay the Cookie Compliance banner script until after the page renders. This causes the banner to appear in a default state (or not appear at all) while the script catches up.

Look for "Exclude from deferral" options in your optimization plugin (WP Rocket, SiteGround Optimizer, LiteSpeed Cache, etc.) and add hu-banner.min.js to the exclusions list.

Banner Not Suppressed for Certain Countries

If you have configured a zone to hide the banner (for example, "Banner Display: Off" for US visitors) but those visitors still see it:

Confirm your Manual geolocation zone settings

In the Admin Portal at Configuration → Laws, check the United States-California (CCPA/CPRA) and Other U.S. States rules. "Banner Display: Off" suppresses the banner only. If you have Autoblocking enabled globally, scripts may still be blocked until the page fully loads — banner suppression and script autoblocking are separate controls.

Check for conflicting plugins

If you have both Cookie Compliance for WordPress and another cookie/consent plugin active, they may conflict. Disable other cookie consent plugins to test in isolation.

Test with a clean environment

• Use a VPN set to the target country.
• Open an incognito/private browser window (no cookies, no local consent state).
• Visit your site and check behavior.

Still Not Working?

Share these details in your support ticket and we can investigate directly:

1. Your site URL
2. Which geolocation mode you are using (Managed or Manual)
3. Screenshot of your geolocation configuration in the Admin Portal
4. Which caching plugins are active on your site
5. The country/region you are testing from (verified via ipinfo.io)
6. Browser DevTools Console output (any errors in red)

Related Articles

• Geolocation — How geolocation works and how to configure zones.
• Troubleshooting: Banner Not Appearing — General banner visibility troubleshooting.
• Portal vs WP Admin: What Lives Where — Geolocation is configured in the portal; the WP admin has a toggle only.