Skip to content

thedaviddias/Front-End-Checklist / skills/local-business

local-business

Verified

Use when auditing a local business website's structured data. Applies to any business that serves customers at a physical location or specific geographic area.

Add LocalBusiness schema markup

LocalBusiness schema enables Google to show your business details (hours, address, phone, rating) directly in search results and Google Maps, improving local visibility without requiring a click.

Quick Reference

  • Add LocalBusiness JSON-LD schema to your homepage and contact page
  • Required properties: @type, name, address (PostalAddress), telephone
  • Include openingHours, geo coordinates, and image for richer results
  • Use a more specific sub-type when available (Restaurant, DentalClinic, etc.)

Check

Check the page source for a JSON-LD script block with @type matching 'LocalBusiness' or a sub-type (Restaurant, Store, etc.). Verify the required properties are present: name, address with PostalAddress, telephone, and url. Validate with Google's Rich Results Test.

Fix

Add a block to the homepage with LocalBusiness schema. Include: @context, @type, name, address (with streetAddress, addressLocality, addressRegion, postalCode, addressCountry), telephone, url, openingHours, and geo. Use a specific sub-type if applicable.

Explain

LocalBusiness structured data tells Google the essential details about a physical business. This data powers the Knowledge Panel in search results, the local pack ('map pack'), and integrations with Google Maps. Without it, Google has to guess business details from unstructured page content.

Code Review

Find JSON-LD script blocks with @type 'LocalBusiness' or a sub-type. Verify required fields: name, address.streetAddress, address.addressLocality, address.addressRegion, address.postalCode, address.addressCountry, telephone, url. Check that address values match the visible on-page address text. Validate with Google's Rich Results Test API.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/rules/seo/local-business

rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall