LOCAL

LocalBusiness schema plan

Use when you need structured data for a location page and want the properties to match what is actually on the page.

local-business-schema-plan.md

Download .md

Plan LocalBusiness structured data for one location page.

Business name: {{BUSINESS_NAME}}
Most specific business type that applies: {{BUSINESS_TYPE}}
Address: {{ADDRESS}}
Phone: {{PHONE}}
Page URL: {{PAGE_URL}}
Opening hours: {{HOURS}}
Other facts available (price range, payment methods, areas served, social profiles, geo coordinates, booking URL, department or branch relationships): {{OTHER_FACTS}}
What is visibly on the page: {{PAGE_CONTENT_SUMMARY}}

Produce:

1. A property table with columns: Property, Value to use, Source (given by me, or on the page), Required or recommended, Note.

2. The JSON-LD, ready to paste, using only values I supplied. Where a property would be valuable but I have not given the value, include it commented out in a list beneath the JSON rather than filling it with a guess.

3. A validation checklist of things to confirm before publishing, including whether each marked-up fact is visible on the page.

Rules:
- Choose the most specific type that genuinely fits and say why. Do not use a specific type as a guess.
- Do not include aggregateRating or review markup unless I supplied real review data, and say plainly that self-serving review markup on a business page is not eligible for rich results.
- Do not mark up anything not present on the page.
- Do not invent geo coordinates, opening hours or a price range.
- Keep the output ASCII.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{BUSINESS_NAME}}
{{BUSINESS_TYPE}}
{{ADDRESS}}
{{PHONE}}
{{PAGE_URL}}
{{HOURS}}
{{OTHER_FACTS}}
{{PAGE_CONTENT_SUMMARY}}

Getting a better result

Match the phone number and address in the schema character for character to your Google Business Profile.
The visible-on-page check is the one people skip and the one that causes manual actions.
One correct LocalBusiness block per location page beats a sitewide block repeated everywhere.

Questions about this prompt

When should I use this rather than a general schema generator?

When the page already exists and you want markup that matches it. This takes {{PAGE_CONTENT_SUMMARY}} and checks each property against what is visibly on the page, which is the constraint that causes trouble months later if it is skipped. A generic generator will happily mark up facts no visitor can see.

What do I need before running it?

The address and phone exactly as they appear on your Google Business Profile, the page URL, hours, and the most specific {{BUSINESS_TYPE}} you believe applies. Character for character matching with the profile matters. Collect {{OTHER_FACTS}} such as areas served and booking URL, but do not guess coordinates or a price range.

What comes back?

A property table showing the source of each value, pasteable JSON-LD built only from what you supplied, missing properties listed underneath rather than filled in, and a validation checklist. The visible on page check in that checklist is the item that prevents the problem the markup would otherwise create.

What is the mistake?

Adding aggregateRating because the block looks bare without it. The prompt states plainly that self serving review markup on a business page is not eligible for rich results. The other one is repeating a single sitewide block on every location page instead of one correct block per page.