Stores comparing Google vs Loqate for WooCommerce address validation are usually asking the same question: which API should check the shipping address before payment? Both can confirm a street against postal data, return a standardized version, and let you warn, correct, or block at checkout. They are not the same product, and the right pick is usually the network you already pay for, plus the autocomplete behaviour you need.
Google Address Validation is a Maps Platform API. Loqate Address Verify is a GBG postal-grade check. Address Guard Pro treats them as interchangeable validation providers, so you can choose either, or mix one vendor’s suggestions with the other’s verify step.
This article compares Google vs Loqate WooCommerce address validation in practical terms: what each validates, how Places differs from Capture, how billing works, and when to pick one over the other. For the checkout flow itself, see How to Validate Addresses Before WooCommerce Checkout. Dedicated setup lives in Google Address Validation for WooCommerce and Loqate Address Validation for WooCommerce.
The short answer
Choose Google Address Validation when you already have a Google Maps Platform project, want Places suggestions and validation on one API key, or ship to many countries and want Maps coverage from a vendor you already bill.
Choose Loqate Address Verify when you already have a Loqate or GBG account, need Capture’s nested building-then-unit results, or want postal-grade Verify from that network rather than Maps.
Mix them when search quality and postal verification do not need to come from the same vendor. Google Places plus Loqate Verify, or Loqate Capture plus Google Address Validation, is a normal production setup.
Neither replaces WooCommerce shipping zones, tax, or carrier rates. Those still run on country, state, and postcode. Validation answers a different question: can we ship to what they entered?
What both providers do at WooCommerce checkout
WooCommerce only checks that required fields are filled in. A missing house number, a postcode from another country, or a street a carrier cannot find will still pass. Google and Loqate both close that gap at place-order.
Address Guard Pro sends street, city, state, postcode, and country to the validation provider. Typical outcomes are the same four statuses, regardless of vendor:
- Verified. Street, city, postcode, and country match a known location.
- Corrected. The address is close, but formatting, city, or postcode should change. The customer can accept the suggestion.
- Unverified. The provider cannot confirm the building. Rural properties, new builds, and some apartment formats land here even when a carrier can deliver.
- Invalid. There is no usable match. A fake street, an incomplete route, or a combination that does not exist usually lands here.
Your store then decides the policy: warn, offer a corrected address, allow checkout, or block it. Provider errors can be marked for review so an API outage does not freeze payment.
That shared checkout behaviour is why Google vs Loqate is a provider decision, not a plugin decision. The customer-facing flow is the same. The data network, autocomplete pair, and billing account are what change.
Google vs Loqate WooCommerce address validation: side by side
| Google Address Validation | Loqate Address Verify | |
|---|---|---|
| Company | Google Maps Platform | Loqate (GBG) |
| Validation product | Address Validation API | Address Verify |
| Autocomplete pair | Google Places | Loqate Address Capture |
| What it proves | The address holds together against Google’s postal data | The address holds together against Loqate’s postal records |
| Match signal | Completeness, match granularity (building, street, city), inferred or replaced components | Address Verification Code (AVC), match score, partial vs full verify |
| Nested units | Places returns a selected place; unit data depends on the result | Capture can drill from building to apartment, then fill sub-building |
| Billing | Google Cloud project, Maps quotas and SKUs | Loqate credits, Capture and Verify enabled per key |
| Credentials | Merchant-owned Google API key | Merchant-owned Loqate API key |
| Best fit | Stores already on Maps, or that want Places plus validation on one key | Stores already on GBG, or that need nested Capture for apartments |
| Works without its autocomplete? | Yes. More typed addresses will fail or warn. | Yes. More typed addresses will fail or warn. |
| Can mix with another vendor? | Yes. Mapbox or Loqate Capture plus Google validation is valid. | Yes. Places or Mapbox plus Loqate Verify is valid. |
The validation vs autocomplete comparison is worth reading if you are still deciding which layer to enable first. Google vs Loqate is the next decision: which network powers the verify step.
Places vs Capture: the autocomplete difference that matters
Stores often treat “Google at checkout” or “Loqate at checkout” as a single feature. Each vendor is two products.
| Product | Role at checkout | What the customer sees |
|---|---|---|
| Google Places | Autocomplete | A suggestion dropdown on address line 1. Selecting one fetches place details and fills street, city, state, postcode, and country. |
| Google Address Validation | Validation | A check before the order is placed. |
| Loqate Address Capture | Autocomplete | A suggestion dropdown on address line 1. Nested results can expand a building into units. |
| Loqate Address Verify | Validation | A check before the order is placed. |
If you only turn on autocomplete, a customer can ignore the dropdown and type a fake street. If you only turn on validation, more addresses fail because they were typed poorly in the first place. Most stores that print shipping labels need both layers.
The practical difference between Places and Capture is apartments.
Loqate Capture is built for structured postal search. For a building with many units, the customer can pick the building, then the apartment. Address Guard Pro maps Loqate’s sub-building into address line 2. That matters if you ship a lot of flats, condos, or office suites.
Google Places is search against place data. It is excellent at filling a complete street quickly. It is not the same nested building-then-unit drill-down. If your failed labels are mostly missing unit numbers in dense housing, Loqate Capture is usually the stronger autocomplete pair. If your customers already live in Maps-quality search, Places is usually enough.
You do not have to pair autocomplete and validation from the same vendor. Address Guard Pro keeps them as separate choices.
How each provider scores an address
Google does not return a simple yes or no. It returns signals Address Guard Pro maps into checkout statuses.
| Google signal | What it usually means | Mapped result |
|---|---|---|
| Address complete, matched to building or unit | The location holds together | Verified |
| Google inferred or replaced a component | City, postcode, or street was standardized | Corrected |
| Complete but not confirmed to the building | Rural, new-build, or unusual unit format | Unverified |
| Incomplete, unconfirmed, or only matched to street or city | Fake, truncated, or internally inconsistent | Invalid |
Loqate Verify uses an Address Verification Code (AVC) and a match score. Address Guard Pro maps those into the same four statuses.
| Loqate signal | What it usually means | Mapped result |
|---|---|---|
| Verified at a useful match level, high score | The location holds together | Verified |
| Verified with a lower match score, or a partial verify that still looks close | Formatting or a component should change | Corrected |
| Ambiguous or only partially confirmed | Rural, new-build, or several possible matches | Unverified |
| Rejected, unmatched, or verified only at a useless level | Fake, truncated, or internally inconsistent | Invalid |
Treat unverified and invalid as different problems on both networks. Invalid is usually a typing failure you can ask the customer to fix. Unverified is often a data-coverage gap. Blocking every unverified result will stop orders a carrier can still deliver.
When either provider returns a standardized address that differs from what the customer typed, offer it. “Did you mean …?” converts better than a generic validation error. How to write that message is covered in How to Warn Customers About Invalid WooCommerce Addresses.
Coverage, data, and shipping countries
Neither vendor is “international” in the abstract. Coverage is about the countries you actually ship to, and how those countries write addresses.
Pick Google when:
- You already trust Maps results in your shipping countries
- Customers search the way they search in Google (street, business-like place names, mixed formatting)
- You want one Maps project to cover many destinations without a second postal contract
Pick Loqate when:
- You already buy GBG data for those markets
- You need postal-grade formatting (especially UK, EU, and other postcode-heavy countries)
- Apartments, sub-buildings, and organisation names need to land in the right WooCommerce fields
For a mostly US catalogue, also consider Smarty. Address Guard Pro supports it as a validation provider. Google vs Loqate is still the usual international comparison.
Do not choose a validator because a demo address in one city looked perfect. Test the destinations in your shipping zones: a capital-city street, a rural property, a new-build, and an apartment with a unit number. The provider that verifies your actual order mix is the one that will save fulfilment time.
Billing, keys, and who owns the usage
Address Guard Pro does not bundle provider usage. You connect your own credentials and keep control of API billing.
Google bills through a Google Cloud project. You enable Address Validation API (and Places API (New) if you want autocomplete), create an API key, and restrict that key to those APIs. Address Guard Pro calls Google from your WordPress server, so IP address restrictions on the site’s outbound IP are appropriate. An HTTP referrer restriction that only allows your domain will block server-side validation even when Places appears to work in the browser on other plugins.
Loqate bills through your Loqate account. Capture and Verify are separate products on the key. A key that is only enabled for Capture will fail the validation test. A key that is only enabled for Verify will fail the autocomplete test. Watch IP or URL restrictions, exhausted credits, and rate limits. Those surface as provider errors, not as a generic WooCommerce checkout failure.
Cost is usage, not a plugin fee. Keep it predictable on both vendors:
- Validate the shipping address. Leave billing off unless invoices or tax IDs depend on a precise street.
- Pair autocomplete with validation so fewer messy typed addresses hit the verify API.
- Limit autocomplete countries to the destinations you ship to.
- Set provider errors to Mark for review so a quota, credit, or network failure does not stop paid orders.
A Google-only stack is one Maps key. A Loqate-only stack is one Loqate key with both products enabled. A mixed stack is two bills. That is fine when search quality and postal verification are worth splitting.
You can mix Google and Loqate
Autocomplete and validation do not have to come from the same vendor.
| Autocomplete | Validation | When it makes sense |
|---|---|---|
| Google Places | Google Address Validation | Simplest Google-only setup. One Maps key. |
| Loqate Address Capture | Loqate Address Verify | Simplest Loqate-only setup. Nested Capture plus postal Verify. |
| Google Places | Loqate Address Verify | Maps-quality search, GBG verification. |
| Loqate Address Capture | Google Address Validation | Nested unit capture, Maps verification. |
| Mapbox Address Autofill | Google or Loqate | Search-quality suggestions without putting Places or Capture on checkout. See Mapbox address autocomplete for WooCommerce. |
The usual reason to mix is an existing contract. You already pay for Places, or you already pay for Loqate Verify. Address Guard Pro does not force you to buy the matching autocomplete product from the same vendor.
Limit autocomplete countries to your shipping zones. If the customer has already chosen a checkout country, that country should win. Otherwise a suggestion from another market fills the form, and shipping methods and tax look wrong.
What WooCommerce still will not do
Native checkout can:
- Require country, street, city, state, and postcode
- Offer shipping methods from those fields
- Copy billing into shipping
Native checkout cannot:
- Suggest real addresses as the customer types
- Confirm that the building exists
- Standardize formatting for label purchase
- Show a corrected address and let the customer accept it
- Keep original versus provider-normalized data on the order
Browser autofill is not Google or Loqate. Autofill replays an address the customer saved earlier. It will fill a stale or incomplete address just as readily as a good one. A Places or Capture suggestion is structured search data. Address Validation and Address Verify are the separate check against postal records.
Warn, block, allow, or mark for review
Google and Loqate return data. Your store decides the policy. The actions are the same for both.
| Action | What the customer sees | Use it when |
|---|---|---|
| Warn | A checkout message. They can continue. | Unverified addresses, first-week validation, or provider uncertainty |
| Block | A checkout error. They must change the address. | Invalid matches, missing house numbers, unusable PO boxes |
| Allow | Nothing extra, or a quiet pass | Verified addresses, or cases you have chosen not to interrupt |
| Mark for review | The order can be placed. Fulfilment gets a flag. | API errors, heavy normalization, or destinations a human should check before buying a label |
Do not launch on Block checkout as the store-wide default. Rural properties and new buildings are often unverified in postal data even when a carrier can deliver there. A customer who cannot place the order does not wait around to argue with the validator.
A practical split for either provider:
- Warn on unverified results.
- Offer the suggested address when the provider returns a standardized version that differs from what they typed.
- Block missing house numbers and invalid postcode/country combinations once those rules are tested.
- Review when the API is unreachable, so a billing, quota, credit, or network failure does not stop paid orders.
Local rules still matter. Google and Loqate tell you whether the address matched postal data. Rules encode what your warehouse will not ship: PO boxes, parcel lockers, missing house numbers. That policy work is independent of which validator you chose.
How to connect either provider in Address Guard Pro
The admin path is the same. Only the credentials change.
- Go to WooCommerce → Address Guard → Providers.
- Choose Google Places or Loqate Address Capture (or Mapbox) as autocomplete, if you want suggestions.
- Choose Google Address Validation or Loqate Address Verify as the validation provider.
- Enter the matching API key.
- Click Test autocomplete provider and Test validation provider.
- Enable validation on the shipping address under Checkout, start with Warn customer, and allow unverified addresses until you have reviewed a week of orders.
Do not enable checkout validation until the tests you intend to use succeed. A failed Google test is usually a missing Address Validation API, a key restricted to HTTP referrers, or a billing problem. A failed Loqate test is usually a product that is not enabled on the key, a restriction, or exhausted credits.
Full steps, including rules, messages, and Checkout Blocks vs classic checkout, are in the Google setup guide and the Loqate setup guide.
Keep this on the shipping address. That is the address on the label. Billing can stay quieter. A customer may bill to a registered office and ship to a street. Those forms should stay independent.
After the customer continues
Validation only helps fulfilment if someone can see it on the order.
Address Guard Pro stores the original address, the provider-normalized address, the validation status, matched rules, and the checkout action. Open the order and check the Address Guard panel before you buy a label when:
- The status is unverified or invalid
- The customer was warned and continued
- A suggested address was shown and declined
- A Google or Loqate API error occurred
If the same warning keeps leading to return-to-sender parcels, change that rule from warn to block. If it never predicts a failed label, soften or remove it. That loop is how you learn whether Google or Loqate is actually predicting carrier failures in your countries, rather than arguing about vendor marketing.
A decision guide
| Your situation | Start with |
|---|---|
| You already pay for Google Maps Platform | Google Places plus Google Address Validation |
| You already have a Loqate or GBG account | Loqate Capture plus Loqate Verify |
| You ship many apartments and need building-then-unit capture | Loqate Capture, with Loqate Verify or Google Address Validation |
| You want Maps-quality search without GBG | Google Places, then Google or Loqate for the check |
| You want search without putting Google or Loqate on the dropdown | Mapbox Address Autofill plus Google or Loqate validation |
| Your catalogue is mostly US and you already pay for Smarty | Smarty validation (optionally with any autocomplete provider) |
| You only need PO box or house-number rules | Local rules first. Add a provider when labels still fail. |
| You are unsure and ship internationally | Connect the vendor you already bill. Warn on shipping. Review a week of orders before you switch. |
If you are choosing from a blank sheet, pick the simpler stack: one vendor, shipping only, warn first. Switching later is a Providers screen change, not a checkout rebuild.
Common questions
Is Google Address Validation the same as Loqate Address Verify?
No. Both verify a WooCommerce shipping address against postal data, and Address Guard Pro maps both into verified, corrected, unverified, or invalid. The data network, match signals, autocomplete pair, and billing account are different.
Is Google Places the same as Loqate Address Capture?
No. Both are autocomplete. Places fills the form from Google place data. Capture fills the form from Loqate search and can nest a building into units. Neither is the validation step.
Does picking a Places or Capture suggestion mean the address is validated?
No. A suggestion is structured capture from search data. Google Address Validation and Loqate Address Verify are separate checks against postal records. Run both layers if you need deliverability, not only a filled form.
Can I use Google validation with Loqate Capture, or Loqate Verify with Google Places?
Yes. Autocomplete and validation are separate choices in Address Guard Pro. Mixing vendors is a normal production setup.
Which is more accurate?
It depends on the country, the address format, and whether the failure is a typo, a missing unit, or a coverage gap. Test your shipping destinations. Do not pick a validator from a single demo city.
Should I block checkout when either provider returns unverified?
Not on day one. Unverified often means rural, new-build, or an unusual unit format. Warn first. Block invalid matches and local rules you have tested, such as missing house numbers.
Does this work with Checkout Blocks?
Yes. Address Guard Pro supports Checkout Blocks and classic [woocommerce_checkout]. Test the type your store actually runs, including a phone-width viewport so suggestions and notices are not clipped.
Will Google or Loqate replace shipping zones?
No. Shipping zones decide which methods to offer. The validator decides whether the address itself is complete and verifiable.
What if the API is down or over quota?
Set provider errors to Mark for review so checkout can continue and fulfilment gets a flag. Do not let a Maps billing problem or Loqate credit failure become a payment failure.
Do I need both autocomplete and validation?
If you print shipping labels, yes for most stores. Autocomplete makes the correct address easy to enter. Validation confirms it before payment. See WooCommerce address validation vs autocomplete.
Pick the network, then check the address before payment
Google vs Loqate for WooCommerce address validation is not a choice between two plugins that do different jobs. Both check the shipping address while the customer is still on checkout. Google is the Maps Platform path: Places to enter the address, Address Validation to confirm it. Loqate is the GBG path: Capture to enter it (including nested units), Verify to confirm it.
Choose the vendor you already pay for, or the one that covers your shipping countries and apartment formats best. Mix them if search and verification should come from different networks. Keep the check on shipping, start with warnings, and store the result on the order so fulfilment is not guessing.
Learn more about Address Guard Pro, or start with the setup guide: Get Started.