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
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.
Replace each placeholder with your own detail. The more specific you are, the less the model invents.