WPForms Geolocation Addon Not Tracking Address Entry? Here’s How to Fix It Fast
- No API key set: Go to WPForms → Settings → Geolocation → paste your Google Places API key
- Address field type wrong: Must use the dedicated “Address” field, not a plain “Text” field
- Google Places API not enabled: Enable both “Places API” and “Maps JavaScript API” in Google Cloud Console
- Plugin cache/conflict: Deactivate other plugins one by one and clear cache after each test
- Plan limitation: Geolocation Addon requires WPForms Pro or Elite — not available on Basic/Plus
So you installed the WPForms Geolocation Addon, set everything up, and… nothing. The address field shows up on your form just fine, but autocomplete isn’t triggering, location data isn’t saving to entries, or the whole addon seems completely silent. Been there. It’s one of those issues that feels maddening because the addon appears to be active — yet it behaves as if it doesn’t exist.
I’ve walked through this across several client WordPress sites. The good news: this is almost always fixable in under 15 minutes once you know where to look. Let’s go through every possible cause, from the most common to the edge cases, so you can get your geolocation tracking working today.
Understanding What the WPForms Geolocation Addon Actually Does
Before jumping into fixes, it helps to understand what the addon is supposed to do — and what it doesn’t do. The Geolocation Addon extends WPForms in two distinct ways:
| Feature | What It Does | Requires |
|---|---|---|
| Address Autocomplete | Shows dropdown suggestions as user types an address | Google Places API key |
| Current Location Button | Populates address from device GPS/IP location | Browser geolocation permission |
| Geolocation Data in Entries | Saves submitter’s approximate location to form entries | No API key needed (IP-based) |
| Smart Address Parsing | Auto-fills city, state, zip from selected autocomplete result | Google Places API key |
Most people reporting “geolocation not working” are actually experiencing one of two separate issues: either the autocomplete isn’t showing on their address field, or the location data isn’t being captured in entries. These have different root causes, so knowing which one affects you narrows things down fast.
Step-by-Step Troubleshooting Guide
The Geolocation Addon is available on WPForms Pro and Elite plans only. If you’re on Basic or Plus, the addon will install but won’t fully function. Go to WPForms → Settings → General and look at your license type. Upgrading is the only resolution here.
Head to WPForms → Addons and scroll to Geolocation. The button should say “Deactivate” (meaning it’s on). If it says “Activate,” click it. If it says “Install,” click that first, then activate. A common mistake is installing without activating — they’re two separate steps.
Navigate to WPForms → Settings → Geolocation. You’ll see a field for your Google Places API key. If this is empty, autocomplete will never work — the addon has no way to call Google’s address database. If there’s a key but it’s not working, the issue is likely on the Google Cloud Console side (see Step 4).
This is the #1 most missed step. Your Google Cloud project must have both of these APIs enabled: Places API and Maps JavaScript API. Log into console.cloud.google.com, go to APIs & Services → Library, search for each, and enable them. Also make sure billing is enabled on your Google Cloud project — even free-tier API calls require a billing account to be set up.
API key restrictions are a frequent silent killer. If your key is restricted by HTTP referrer, the referrer you added must exactly match your domain — including protocol (https://) and wildcard patterns. Try removing all restrictions temporarily to test. If autocomplete suddenly works, you know the restriction is blocking the API call. Then add your domain back correctly: https://yourdomain.com/*
The autocomplete feature only works with WPForms’ built-in Address field type. If you’ve used a single-line Text field and labeled it “Address,” the geolocation addon won’t attach to it. Edit your form, delete the text field, and add a proper Address field from the field panel. Then check the field settings — there should be a “Geolocation” toggle within the field options when the addon is active.
Even with everything configured globally, you need to enable geolocation per-form. Open your form in the WPForms editor → click Settings → General → look for a “Store Location Data” or similar toggle and make sure it’s on. Some users miss this because the global settings look complete, but form-level settings are separate.
Caching plugins like WP Rocket, LiteSpeed Cache, W3 Total Cache, and even Cloudflare can serve a cached version of your page that doesn’t include the fresh geolocation scripts. After any settings change: clear your caching plugin’s cache, purge Cloudflare if you use it, and test in an incognito window to bypass browser cache. You’d be surprised how often “nothing changed” turns out to be a cache issue.
Open your browser’s Developer Tools (F12 → Console tab) and reload the page with your form. Any red error messages pointing to WPForms scripts, Google Maps, or conflicting plugins are your culprit. Common offenders include Jetpack, Elementor, certain security plugins, and old jQuery versions. Try switching to a default WordPress theme (Twenty Twenty-Four) temporarily and disabling plugins one by one to isolate the conflict.
The Google Maps/Places API returns specific error codes that tell you exactly what’s wrong. Here are the ones you’re most likely to see:
| Console Error | Cause | Fix |
|---|---|---|
REQUEST_DENIED |
API key invalid or not authorized | Check key in Google Cloud Console, enable billing |
OVER_QUERY_LIMIT |
Exceeded free tier quota | Enable billing or wait for quota reset |
ApiNotActivatedMapError |
Maps JavaScript API not enabled | Enable Maps JavaScript API in Cloud Console |
RefererNotAllowedMapError |
Domain not in API key allowed list | Add your domain to key restrictions |
| No error, autocomplete still broken | Plugin conflict or cache | Test in incognito + disable plugins |
Still Stuck? WPForms Support Has You Covered
WPForms Pro and Elite plans include priority support from their technical team. If you’ve tried everything above and still can’t get geolocation working, their team can pull your site’s specific error logs and pinpoint the issue directly.
🚀 Upgrade to WPForms Pro — Fix This TodayMost Common Root Causes by Frequency
Based on WPForms support threads, community forums, and my own testing across client sites, here’s how frequently each cause appears. If you’re in a hurry, start with the top three and you’ll resolve about 80% of cases.
Setting Up the Google Places API Key Correctly (Full Walkthrough)
Since an API key issue is the culprit in a huge percentage of cases, let me walk through the correct setup from scratch so there’s no ambiguity.
Step 1: Create or Access a Google Cloud Project
Go to console.cloud.google.com. Create a new project (or select an existing one). Give it a recognizable name like “My WordPress Forms.”
Step 2: Enable Billing
Even if you’ll stay well within Google’s free tier ($200/month credit), billing must be enabled. Go to Billing → Link a billing account. Google won’t charge you unless you exceed the free tier — which for most WordPress sites, you won’t.
Step 3: Enable the Required APIs
Go to APIs & Services → Library. Search for and enable:
- Places API
- Maps JavaScript API
- Geocoding API (optional but recommended for full address parsing)
Step 4: Create an API Key
Go to APIs & Services → Credentials → Create Credentials → API Key. Copy the key immediately. Then click “Edit API Key” and under Application Restrictions, set it to “HTTP referrers (web sites)” and add your domain:
Step 5: Add the Key to WPForms
In WordPress, go to WPForms → Settings → Geolocation. Paste your API key in the “Google Places API Key” field and save. Then clear your cache and test your form.
WPForms Geolocation vs. Other WordPress Form Location Solutions
If you’re weighing whether WPForms with the Geolocation Addon is the right tool for your needs, here’s how it stacks up against alternatives:
| Solution | Address Autocomplete | Location in Entries | Cost | Ease of Setup |
|---|---|---|---|---|
| WPForms + Geolocation Addon | ✅ Yes | ✅ Yes | Pro: ~$199/yr | Easy |
| Gravity Forms + GF Geolocation | ✅ Yes | ✅ Yes | Elite: ~$259/yr | Moderate |
| Formidable Forms | ⚠️ Limited | ✅ Yes | Business: ~$149/yr | Moderate |
| Ninja Forms + Address Autocomplete | ✅ Yes | ❌ No | Agency: ~$249/yr | Easy |
| Contact Form 7 (manual) | ❌ No | ❌ No | Free | Requires Dev Work |
WPForms hits the sweet spot for most WordPress site owners — the UI is genuinely beginner-friendly, the addon installation is a single click (once you’re on the right plan), and the documentation is solid. The main frustration comes from the API key setup on Google’s side, not from WPForms itself.
Pros and Cons of the WPForms Geolocation Addon
✅ What Works Well
- One-click install from within WPForms dashboard
- Address autocomplete dramatically reduces user input errors
- Location data visible directly in form entries without extra tools
- Works with WPForms’ conditional logic and notifications
- No coding required for basic setup
- Works on both front-end forms and admin preview
❌ Known Limitations
- Requires Google Cloud account + billing setup (even for free tier)
- Only available on Pro/Elite plans — locked behind paywall
- Autocomplete only works on the dedicated “Address” field type
- Location accuracy depends on IP for entry data (not GPS-precise)
- IP-based geolocation may misidentify VPN users’ location
- Cache conflicts can be confusing to diagnose
Why Geolocation Data Saves to Entries But Autocomplete Doesn’t Work (Or Vice Versa)
This trips people up because they see some geolocation data working and assume the rest should work too. Here’s why they can operate independently:
IP-based location logging (the data that appears in your entries showing approximate country/city of the submitter) runs entirely server-side and doesn’t need a Google API key. It uses free IP geolocation databases baked into WPForms. This is why you might see location data in entries even when your Google key isn’t configured.
Address autocomplete is a completely separate client-side feature powered by the Google Places API. No Google key = no autocomplete dropdown. Period. The two features share the same addon but use entirely different mechanisms under the hood.
So if you see location in entries but no autocomplete: your addon is partially working — you just need to sort out the Google API configuration. If you have autocomplete but no location in entries: check your form-level settings and make sure “Store geolocation data” is enabled.
Advanced: Testing Your Google Places API Key Independently
If you’re not sure whether the issue is with WPForms or with your API key itself, test the key directly. Open your browser and visit this URL, replacing YOUR_API_KEY with your actual key:
You should see a JSON response with address predictions. If you get "status": "OK", your key is working and the issue is in WPForms’ integration. If you get "status": "REQUEST_DENIED", the problem is definitely the API key — go back to Google Cloud Console and verify billing and enabled APIs.
Using Browser Dev Tools to Inspect API Calls
Open DevTools (F12) → Network tab → filter by “maps.googleapis.com” → type something in your address field. You should see a Places API request firing. Check its status code and response. A 200 with results confirms the API connection is good. A 403 means the API key is being rejected.
Common Plugin Conflicts with WPForms Geolocation
Based on patterns across the WPForms community, these plugins and setups tend to interfere with the geolocation addon most often:
| Plugin/Setup | Conflict Type | Resolution |
|---|---|---|
| WP Rocket | Deferred JS loading delays Maps script | Exclude Maps JS from deferral in WP Rocket settings |
| Cloudflare Rocket Loader | Alters how async scripts load | Disable Rocket Loader or add data-cfasync="false" to scripts |
| Jetpack | Can register its own Maps script that conflicts | Disable Jetpack’s map block module if unused |
| Custom jQuery version | Old jQuery breaks WPForms scripts | Update to WordPress default jQuery |
| Another form plugin also loading Maps | Duplicate script registration | Only one plugin should enqueue Maps API |
| Content Security Policy headers | Blocks Google domains at server level | Allow maps.googleapis.com in your CSP header |
What to Do If You’re Using Elementor or a Page Builder
Running WPForms inside an Elementor widget, Divi module, or Beaver Builder element adds another layer to troubleshoot. Page builders sometimes enqueue their own scripts in ways that interfere with WPForms’ script loading.
First, test your form on a plain WordPress page (not built with your page builder) to rule out builder-specific conflicts. Create a new page, add a Gutenberg block with your shortcode , and see if geolocation works there. If it does, the conflict is in your page builder — not WPForms.
For Elementor specifically: go to Elementor → Settings → Advanced → Script Optimization and disable “Improved Asset Loading” temporarily. This resolves script-dequeuing conflicts in many cases.
WPForms Geolocation Setup Checklist
Before calling something broken, run through this entire checklist. Print it or bookmark it — it covers every configuration point:
- WPForms Pro or Elite license confirmed and active
- Geolocation Addon installed AND activated (two separate steps)
- Google Cloud project exists with billing enabled
- Places API enabled in Google Cloud Console
- Maps JavaScript API enabled in Google Cloud Console
- API key created and not expired/revoked
- API key domain restrictions include your site’s exact URL pattern
- API key pasted correctly into WPForms → Settings → Geolocation
- Form uses the WPForms “Address” field type (not plain Text)
- Geolocation enabled within individual form settings
- Caching plugin cache cleared after settings changes
- Cloudflare or CDN cache purged
- Tested in an incognito/private browsing window
- Browser console checked for JavaScript errors
- No conflicting plugins loading their own Maps script
- Content Security Policy headers allow Google Maps domains
Ready to Get WPForms Running Properly?
WPForms is one of the most reliable WordPress form plugins out there — once the Geolocation Addon is configured correctly, it works smoothly with minimal maintenance. Start with the right plan and save yourself the headache.
🔗 View WPForms Pro Pricing & PlansHow WordPress Hosting Affects WPForms Geolocation Performance
Something that rarely gets mentioned in troubleshooting guides: your hosting environment can quietly affect geolocation reliability. Here’s why it matters.
Some managed WordPress hosts apply server-level caching that can’t be cleared from the WordPress dashboard. If you’re on a host like WP Engine, Kinsta, or Flywheel, you’ll need to clear the server cache from within your host’s dashboard — not just from your caching plugin. Additionally, hosts with aggressive output buffering or GZIP compression settings can occasionally break how asynchronous scripts (like the Google Maps API) load.
If you’re on a budget shared host and experiencing repeated issues, it may be worth looking at more WordPress-optimized infrastructure. We’ve covered several good options — the Hostinger review covers one of the most beginner-friendly options with strong WordPress-specific performance, and our best Linux hosting guide compares top-tier options with real performance data if you’re evaluating a switch.
Also relevant: the Distribb SEO content tool integrates with WordPress sites directly, which is another reminder that your hosting’s CMS integration quality affects every plugin you run — not just WPForms.
Geolocation Addon Won’t Install or Throws a Fatal Error
If you click “Install” on the Geolocation Addon and get a fatal error, a white screen, or a failed install message, here’s what to check:
PHP Version Compatibility
WPForms requires PHP 7.4 minimum, with PHP 8.0+ recommended. Go to your WordPress dashboard → Tools → Site Health → Info → Server section to see your PHP version. If it’s below 7.4, contact your host and ask them to upgrade.
Memory Limit Issues
Add this line to your wp-config.php file to increase WordPress memory:
File Permissions
The WordPress /wp-content/plugins/ directory needs to be writable for addon installation to succeed. If you see a “Could not create directory” error, your server file permissions are too restrictive — a message to your host’s support team will usually sort this quickly.
When to Contact WPForms Support Directly
If you’ve gone through this entire guide and the issue persists, it’s time to open a support ticket with WPForms. When you do, include:
Your WPForms version number, the exact error shown in your browser console (screenshot is best), your PHP version and WordPress version, a list of active plugins, and whether the issue happens on the default WordPress theme. The more specific you are upfront, the faster they can diagnose it — their support team is generally responsive and technically sharp.
WPForms Pro and Elite users get priority support with faster response times. If you’re on a lower plan and hitting these addon-level issues, that alone is a reason to consider upgrading — the combination of feature access and better support is genuinely worth the difference for sites where forms are doing important work (lead capture, bookings, order intake).
Related WordPress Tools Worth Knowing
If you’re working through WordPress configuration issues like this one, these resources from our site might save you time on adjacent problems:
- ClonewebX Review — Clone and move WordPress page builder layouts without coding
- Hostinger Review 2026 — WordPress-optimized hosting with built-in staging and AI tools
- Best Linux Hosting Providers 2026 — Compared and ranked with real WordPress performance data
- Soro AI SEO Review — Automate WordPress content publishing with proper internal linking
- Distribb Review — WordPress-native SEO automation that publishes and builds backlinks
Frequently Asked Questions
WPForms Geolocation: Get It Working the Right Way
WPForms is one of the most capable form builders in the WordPress ecosystem. With the right plan and a properly configured Google API key, the Geolocation Addon works reliably and adds real value to your forms — whether you’re collecting delivery addresses, running local service bookings, or gathering market research data by region.
✅ Get WPForms Pro — Includes Geolocation Addon