Table of Contents

  1. What the New Store Address Attribute Is
  2. Format Requirements at a Glance
  3. Minimum Requirements That Cause Disapprovals
  4. Multiple Stores: One Address Per Store Context
  5. Address Consistency Across Your Whole Presence
  6. A Safe Rollout Plan
  7. If You Are Online-Only
  8. Troubleshooting Common Errors
  9. Store Address Checklist
  10. Keeping Location Data Clean Over Time
  11. Why Address Accuracy Matters to Shoppers
  12. Frequently Asked Questions

What the New Store Address Attribute Is

On October 14, 2026, Search Engine Land reported that Google Merchant Center introduced a new store address [store_address] attribute for local inventory. Google's help documentation for the attribute says it specifies the postal address of your store, and lists it as required for each product where it applies.

If you run local inventory ads or free local listings, which means you tell Google which of your physical stores have a product in stock, this attribute is now part of your data model. If you only sell online and never submit local inventory, this change does not touch you, though it is a useful reminder of how Google ties products to real-world locations.

Read the live spec

Details here reflect Google's Merchant Center help page for the attribute at the time of writing. Local inventory data specifications are updated often, so verify the current rules before changing your feed.

Format Requirements at a Glance

Google's documentation gives these technical details for the attribute:

Notice that the example is a single plain string with street, city, state and postal code separated by commas. Do not split the address across multiple fields unless the feed method you use specifically requires it.

Minimum Requirements That Cause Disapprovals

Google states that if you do not follow the minimum requirements, the product will be disapproved and you will be notified in Merchant Center. The listed requirements:

  1. Submit a valid postal address. A made-up, partial, or PO-box-style placeholder is the first thing to fail.
  2. Use Unicode characters. Google recommends ASCII only where possible.
  3. Avoid invalid Unicode characters. Examples Google names include control characters such as U+200D, function characters, private-area characters, surrogate pairs and unassigned code points. These typically sneak in during file encoding, so export in UTF-8.
  4. Prevent encoding issues. Google suggests submitting files in a compressed format.
  5. Double-check for typos. Verify the address submitted is correct.
  6. Verify the account. Confirm the correct address is updated in your Merchant Center account.
The invisible-character trap

A zero-width joiner (U+200D) or a stray private-use character is invisible in a spreadsheet but fatal to validation. If a seemingly perfect address is rejected, paste it into a plain-text editor with visible whitespace or re-type it by hand, then export as UTF-8.

Multiple Stores: One Address Per Store Context

Local inventory data already uses a store code and a product ID to say which store has which item. Google's local inventory specification says the store code must match the store codes you submitted in your Business Profiles and is case-sensitive. The new attribute adds the postal address to the data you provide per product submission.

For a merchant with several locations, that means each row should carry the address that matches its store code. The simplest safeguard is to generate the address column from the same source of truth as the store code, such as your Business Profile export or POS location table, rather than typing it into the feed by hand.

If you sell the same item in multiple stores, the specification reminds you that the same ID appears for multiple store codes, with one ID entry per store and the other attributes changed accordingly. Our omnichannel retail guide and BOPIS guide walk through the wider setup.

Address Consistency Across Your Whole Presence

Google cross-checks business identity signals. Your Merchant Center business information, Business Profile, website contact page and the new feed attribute should all tell the same story. Differences such as Suite versus Ste are harmless, but a different street or city is a trust problem.

This links directly to the contact requirements for approval. Our contact page requirements guide explains what Google expects to see, and the misrepresentation guide explains why inconsistent business details raise flags.

A free scan at gmcunbanned.com checks your store for the policy and landing page issues that most often trigger suspensions.

A Safe Rollout Plan

  1. Export your store list. Pull store code and full postal address from the system you trust most.
  2. Normalize. Apply a consistent format: street, city, state or province, postal code, country where relevant.
  3. Clean the characters. Strip control and private characters, save as UTF-8.
  4. Test with one store. Submit a single store's inventory, then review Diagnostics.
  5. Expand to all stores. Add the rest once the test is clean.
  6. Monitor weekly. Set a recurring review of Needs Attention for local inventory warnings.

Feed monitoring is easier with alerts. See our Diagnostics guide for what to watch.

If You Are Online-Only

Many of our readers run purely online stores. For you, the practical takeaway is to avoid submitting local inventory data that does not reflect real stores. Do not add a fake storefront address to qualify for local listings: that is a textbook misrepresentation trigger. A warehouse that does not serve customers is not a store. If you do run a showroom or pickup point open to the public, then local inventory can be legitimate, but verify your Business Profile first.

Troubleshooting Common Errors

Most failures trace back to a data-pipeline step, not to Google. Fix the pipeline and the errors stop recurring.

Store Address Checklist

✅ Local Inventory Address Checklist

store_address column present for every local inventory row

Each address is a valid postal address matching the store code

File exported as UTF-8 with no control or private-use characters

Store codes match Business Profile codes exactly (case-sensitive)

Addresses consistent with contact page, Business Profile and Merchant Center account

Single-store test passed before full rollout

Keeping Location Data Clean Over Time

Store data decays. Locations move, close, rename and get new suites. Assign an owner for the location master list and review it each quarter. Whenever a store opens or closes, update the Business Profile, your website's store locator, your feed's local inventory file and the address attribute in the same working day. The merchants who run into recurring local inventory errors are almost always the ones where each of those lives in a different spreadsheet.

Build a lightweight validation step into your export. A short script that checks every address for a postal code, rejects control characters and verifies that each store code exists in your Business Profile list will catch most problems before Google does. Run it automatically each time the feed is generated, and send the failure report to whoever owns the feed.

Finally, document your process. When an agency, developer or new employee takes over the feed, a one-page description of where addresses originate and how they flow to Google saves days of detective work, and it makes any later appeal or support conversation much easier because you can show exactly how the data is produced.

Why Address Accuracy Matters to Shoppers

Local inventory listings promise a shopper that an item is available at a specific place. If the address is wrong, the shopper drives to the wrong location or finds a closed shop, and the experience reflects on both your brand and Google's results. That is the real reason Google insists on a valid postal address. Treat the field as a customer promise rather than a technical formality, and you will naturally keep it accurate.

Frequently Asked Questions

Is store_address required? Google's documentation says it is required for each product where it applies, namely local inventory submissions.

What format should the address use? A single string such as 1600 Amphitheatre Pkwy, Mountain View, CA 94043 for text and XML feeds.

Why was my valid address rejected? Invisible Unicode characters and encoding problems are common culprits. Re-export as UTF-8.

Do online-only stores need it? No, it concerns local inventory. Do not invent a store to qualify.

Does it affect my account health? Disapproved products reduce what you can show, and repeated data errors make account reviews harder. Fix them promptly.

How can I check my store quickly? Run the free scan at gmcunbanned.com to review contact details and policy pages that Google cross-checks with your feed.

Local Inventory Errors Often Start With Business Details.

Run the free scan at gmcunbanned.com to check that your contact and address information is consistent across your site.

Run Free GMC Scan →