7 LocalBusiness Schema Mistakes Law Firm Websites Make

Google reconciles the name, address, and phone number in a firm's LocalBusiness schema against what appears in the Google Business Profile. A mismatch as small as "Suite 400" on the site versus "Ste. 400" in the GBP introduces an entity disambiguation problem. Google treats inconsistent NAP as a signal that the website and the profile may belong to different businesses. For a PI firm running campaigns around terms like "car accident lawyer near me," that ambiguity can directly suppress 3-Pack placement. Every character in the schema's name, streetAddress, and telephone fields must be an exact copy of what appears in the GBP.

Many law firm websites set @type to "Attorney" when the correct type for a personal injury practice is "LegalService" — or a more specific subtype such as "Attorney" nested within a "LegalService" parent using the sameAs or mainEntityOfPage relationship. Schema.org defines "Attorney" as a person-level type, not an organization-level type. Applying it at the firm level causes Google's parser to interpret the entity as an individual rather than a business, which breaks the connection to an organization-level GBP. A PI firm should use @type "LegalService" at the organization level and, if the site has individual attorney pages, apply "Attorney" only to those person-specific pages.

The url property in LocalBusiness schema is supposed to identify the canonical homepage of the business — the same URL associated with the GBP's website field. Firms frequently set url to an interior page, a tracking URL, or an HTTPS variant that redirects, rather than the exact URL entered in the Business Profile. Google uses url as a primary signal for entity matching between the site and the profile. When those URLs differ, the two records are harder to reconcile as the same entity. The url value should be the bare canonical homepage with no trailing UTM parameters and must match the website field in the GBP character for character.

Google's local ranking system factors business hours into queries with implied timing, such as "emergency car accident lawyer open now." When the openingHoursSpecification block is absent from the schema, Google relies entirely on the GBP hours and has no corroborating signal from the website. More damaging is when the schema specifies hours that contradict the GBP — for example, the schema says the office closes at 5 PM but the GBP lists 24-hour availability for a firm that takes after-hours calls. Contradictory hours signals create an entity trust problem and can trigger knowledge panel inconsistencies. The openingHoursSpecification in JSON-LD should be kept synchronized with GBP hours on every update.

The geo property — containing latitude and longitude as GeoCoordinates — gives Google a precise physical anchor for the business entity. Many PI firm websites omit geo entirely, and others populate it with coordinates rounded to two decimal places, which can place the office in the wrong city block. Google's proximity calculation for 3-Pack results depends on its confidence in where the business physically sits. A firm handling premises liability cases in a specific metro area loses proximity advantage when its coordinates are ambiguous. Coordinates should be pulled from Google Maps using the exact pin location that matches the GBP address and expressed to at least six decimal places.

The sameAs property is a JSON-LD array that lists authoritative URLs Google can use to confirm a business entity's identity across the web. A common mistake is omitting the firm's Google Business Profile URL from this array, or including a short Google Maps link that redirects rather than the canonical GBP URL in the format "https://www.google.com/maps/place/?cid=XXXXXXX". Google uses sameAs references to build its Knowledge Graph confidence score for the entity. For a personal injury firm, a well-formed sameAs array that includes the GBP URL, the firm's state bar directory listing, and any authoritative legal directories strengthens the entity signal significantly. Any URL placed in sameAs must resolve correctly and consistently — a broken or redirecting sameAs link weakens rather than helps the entity record.

Plugin-heavy law firm websites frequently generate two or more LocalBusiness schema blocks on the homepage simultaneously — one from the theme, one from an SEO plugin, and occasionally one hardcoded by a developer. When Google's parser encounters duplicate or contradictory schema blocks, it must decide which values to trust, and the result is often that it discards structured data signals from the page entirely rather than risk indexing incorrect information. A PI firm with one block listing the office phone number and another listing a tracking number has introduced a direct NAP conflict at the schema level. The fix is to audit the page source and confirm exactly one LocalBusiness JSON-LD block is rendered, with all other sources disabled. Google's Rich Results Test and Schema Markup Validator both surface duplicate block problems and should be run after any site update.