LocalBusiness schema includes required fields
Why it matters
A LocalBusiness JSON-LD block without name, address, and telephone is structurally incomplete per schema-org LocalBusiness and schema-org PostalAddress specifications. Google requires these three fields to associate your structured data with a real physical entity. A schema missing telephone or a properly nested PostalAddress with at least streetAddress and addressLocality will not generate a Knowledge Panel entry or local pack listing, and Google may ignore the entire block.
Severity rationale
High because incomplete required fields cause Google to discard the LocalBusiness schema entity, negating the visibility benefit of having structured data at all.
Remediation
Add the missing required fields directly to your LocalBusiness JSON-LD in app/layout.tsx or a dedicated src/components/structured-data.tsx.
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Springfield Plumbing",
"telephone": "+15555555555",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main St",
"addressLocality": "Springfield",
"addressRegion": "OH",
"postalCode": "45501",
"addressCountry": "US"
}
}
All three fields — name, telephone, and address — must be non-empty. An address object missing addressLocality is treated as absent.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Local SEO Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- schema-org · LocalBusiness — LocalBusiness required properties
- schema-org · PostalAddress — PostalAddress type for address field
Taxons
History
- 2026-04-18·v1.0.0·Initial import from marketing-local-seo·automated