local-schema

Generate LocalBusiness JSON-LD matching GBP data for single and multi-location sites.

71|14|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/garrettjsmith/localseoskills --skill local-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-schema
Source: https://github.com/garrettjsmith/localseoskills/tree/main/skills/local-schema
Command: npx skills add https://github.com/garrettjsmith/localseoskills --skill local-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Local businesses often have GBP-listed data that doesn't perfectly align with on-site structured data, leading to inconsistent local visibility. This skill ensures that a site's LocalBusiness JSON-LD mirrors GBP data exactly.

Core Features & Use Cases

  • Exact GBP alignment: Generates and validates LocalBusiness schema that matches GBP attributes (name, address, phone, hours, and area served) across pages and locations.
  • Per-location schemas: Creates location-specific schemas for multi-location businesses with unique @id references.
  • Validation readiness: Provides guidance for Google Rich Results Test and Schema Markup Validator.

Quick Start

Update your site’s LocalBusiness JSON-LD to mirror your GBP profile for each location.

Frequently Asked Questions about local-schema

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I match my website LocalBusiness JSON-LD to my Google Business Profile data?

To align LocalBusiness JSON-LD with GBP data, you mirror exact attributes like name, address, phone, hours, and area served across your site. This ensures consistent local visibility by enforcing correct @type usage and per-location @id references.

What is the best way to generate structured data for multi-location businesses?

Generating structured data for multi-location businesses requires creating location-specific schemas with unique @id references. This approach handles address, phone, hours, and areaServed mappings while complying with Schema.org and GBP requirements across every page.

Why does my LocalBusiness schema fail Google Rich Results Test validation?

LocalBusiness schema fails Google Rich Results Test validation when address, geo, openingHours, or per-location @id references are incorrectly placed. Correcting these elements ensures your JSON-LD complies with both Schema.org and GBP requirements.

Do I need separate JSON-LD for each location on my multi-location site?

Yes, multi-location sites need separate JSON-LD for each location. Applying per-location schemas with unique @id references ensures each location's address, phone, and hours are accurately mapped and individually validated.

When do I need to update LocalBusiness structured data to match GBP?

You need to update LocalBusiness structured data whenever your GBP attributes change. Keeping name, address, phone, hours, and area served exactly mirrored prevents inconsistent local visibility and ensures ongoing compliance with Schema.org.