Google Clarifies LocalBusiness Type Markup
Google updated Search Central guidance to specify that multiple LocalBusiness types must be declared in an array, not through additionalType.
The News
Google Search Central’s latest documentation updates list an August 29, 2026 clarification for Local Business structured data. The affected surface is Google Search’s interpretation of LocalBusiness markup on location pages. Google says sites specifying multiple types should put them in an array, and that additionalType is not supported for this use case, tightening how local entity classification should be encoded.
The OPTYX Analysis
This is a local discovery signal because local entity data increasingly depends on consistency between profile systems, location pages, and machine-readable markup. The mechanism is type-array validation, where Google is making the supported modeling pattern explicit and rejecting a common schema.org-style workaround for multiple business classifications. Strategically, this pushes multi-service and multi-category local brands toward cleaner entity declarations rather than broad or improvised type expansion. The change matters because category ambiguity can weaken eligibility, diagnostics, and confidence around local rich-result interpretation.
Enterprise Impact
The exposed operator is the multi-location SEO team, franchise platform, healthcare directory, home-services brand, or CMS owner generating LocalBusiness schema at scale. The opportunity is cleaner local entity classification across templates that serve many categories, departments, or service lines. The vulnerability is legacy markup that relies on additionalType, plugin defaults, or stitched schema graphs that appear valid generally but are unsupported for Google’s LocalBusiness handling. Required move is a schema-template audit across location pages, validator rules, deployment pipelines, and category mapping logic before stale markup becomes a silent local-discovery quality issue.