LocalBusiness values need a format review
In the reportLocalBusiness values fail format requirements
structured_data_localbusiness_format_errors · Review item
Inspect the original property and its measured format, then correct the declared business value using accurate source information.
Severity: Low. Review item: deterministic value formatting, not a judgment of business eligibility or map-pin accuracy.
Why it matters
Readable, consistently formatted business values help structured-data consumers understand the declared business details.
What to do
- Read the original property, expected format and measurement in the report.
- Use accurate coordinates with at least five decimal places, opening times in hh:mm or hh:mm:ss, supported full day names or their schema.org IRIs, and a priceRange under 100 characters. Do not invent location precision.
- Run another full audit of the same page after changing the value.
When to leave it as it is: Do not add optional values solely to satisfy this check. Numeric JSON coordinates, telephone country codes and uncertain entity types require separate review.
What we read
The current audit’s complete typed JSON-LD, Microdata or RDFa and original node/property byte ranges.
An existing original JSON-LD root inventory prevents invisible untyped business fields from appearing to be a correction. It supplies coverage evidence, never a finding by itself.
This subset checks nodes typed exactly LocalBusiness. Subtype hierarchy, telephone calling-code membership and numeric coordinate lexical precision are not established.
Example & evidence
Illustrative correction of the time format; the actual opening time stays unchanged.
{"@type":"LocalBusiness","openingHoursSpecification":{"@type":"OpeningHoursSpecification","dayOfWeek":"Monday","opens":"9:00"}}{"@type":"LocalBusiness","openingHoursSpecification":{"@type":"OpeningHoursSpecification","dayOfWeek":"Monday","opens":"09:00"}}Confirm & check again
Check for yourself: Confirm that the correction describes the real business and that the same page’s complete source was checked.
Check again: Full audit — A subsequent full audit uses the shared evaluator and lifecycle for the same page. Missing or incomplete coverage, changed entity type and hidden untyped nodes cannot prove a fix.
Limits & sources
Only string coordinate lexemes are measured; normalized JSON numbers have lost their original decimal precision.
Every present telephone remains unverified without governed calling-code authority; a plus sign alone is not proof.
Other/lost types carrying business fields, unresolved references and multi-valued fields remain unknown. Known formatting errors may still be shown alongside incomplete coverage.
Missing or incomplete JSON-LD root inventory, inline/array/scoped contexts and unsafe numeric inventory remain unknown in this conservative subset. Oversized original source is not checked removal.
This check does not prove business ownership, eligibility, map-pin accuracy or a valid telephone number. A failed or missing page response is not a correction.
Confidence: High High for deterministic original string formatting on an explicitly typed LocalBusiness; uncertain coverage blocks reconciliation.
Sources
- Google Search Central, Local business structured data — Existing catalog authority for business value format conventions; this implementation documents its narrower supported evidence and unknown cases. Checked 12 July 2026.
Editorial review: 2 November 2026