# Add LocalBusiness Schema From Your Google Listing

Website business details can differ from a Google listing, making structured data harder to maintain. This skill builds JSON-LD from available listing fields and proposes an exact website diff for approval.

## Install

```bash
npx skillstore add locusintelligence-dauagency/add-local-business-schema
```

## Metadata

- Status: approved
- Slug: locusintelligence-dauagency-add-local-business-schema
- Skillstore revision: r1
- Version status: missing
- Tree hash: bb8ef0540be1559b8e454aa5d62c7bfd25d06ebb6f0f1c4c0b5fa87c5f4e04cd
- Author: locusintelligence-dauagency
- GitHub username: locusintelligence-dauagency
- License: MIT
- Repository: https://github.com/locusintelligence-dauagency/reach-skills/tree/2b10a6be9b9b9a990ae0beb360a21476fad41918/skills/add-local-business-schema
- Ref: 5e1f762ecf28b75c366ed9b67053b444b2eb9ffd
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/locusintelligence-dauagency-add-local-business-schema
- Manifest: https://skillstore.pages.dev/api/skills/locusintelligence-dauagency-add-local-business-schema/manifest

## Capabilities

- Select a connected business location and read its profile through Reach MCP.
- Choose a specific schema.org business subtype from the primary category, with LocalBusiness as the fallback.
- Map available name, phone, website, address, hours, and description into JSON-LD without inventing missing fields.
- Serialize JSON-LD safely and escape less-than signs before embedding it in an HTML script tag.
- Locate website layouts, check existing JSON-LD blocks, and propose an exact diff before editing.
- Compare website hours, phone, and address with listing values and request approval for each correction.

## Use Cases

- Prepare Business Website Structured Data: Generate schema from an existing Google listing and review the proposed website change before approving it.
- Integrate Schema Into a Website Layout: Locate the shared layout, inspect existing JSON-LD, and update structured data using safe serialization.
- Compare Public Business Details: Review differences between website contact details and Google listing values before requesting specific corrections.

## Prompt Templates

### Draft LocalBusiness Schema

```
Create LocalBusiness JSON-LD from my connected Google listing. Explain the selected type and missing fields. Do not edit files yet.
```

### Prepare a Website Diff

```
Read my listing and inspect this website repository. Find existing JSON-LD and propose an exact schema diff. Wait for approval before editing.
```

### Compare Website and Listing Details

```
Compare website hours, phone, and address with my selected Google listing. Show differences in a table and ask which values are correct.
```

### Review an Existing Schema Integration

```
Inspect existing JSON-LD against my selected listing. Check subtype, missing fields, duplicates, and safe serialization. Propose an exact diff and await approval.
```

## Limitations

- Requires a connected Reach MCP server, browser OAuth sign-in, and an active Google listing connection.
- Cannot write to Google Business Profile through this skill.
- Uses returned profile data only; missing fields and unknown freshness must remain explicit.
- Does not guarantee search visibility or automatic validation; it suggests external tools for owner review.

## Best Practices

- Confirm the correct location, active connection, returned limitations, and data freshness before generating schema.
- Review the exact diff and resolve each business-detail discrepancy before approving edits.
- Use safe JSON serialization, update existing schema instead of duplicating it, and verify the resulting page.

## Anti Patterns

- Inventing ratings, images, coordinates, price ranges, or other fields absent from the listing.
- Embedding raw listing text directly into HTML or leaving script-tag termination sequences unescaped.
- Approving broad changes without reviewing the exact diff or assuming this skill updates the Google listing.

## Security Audit

- Audited at: 2026-10-10T22:35:33.367\+00:00
- Summary: All 16 static findings are false positives: Markdown formatting, documented service links, privacy guidance, or defensive JSON escaping. The workflow requires explicit approval before repository edits and feature submissions, while prohibiting Google listing writes. No evidence found of prompt injection, credential collection, unauthorized data transfer, or concealed execution in the reviewed instructions.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0