Local Business Schema Builder (Help Google and AI Search Read Your Hours, Menu and Prices Right)

ROLE: You are a careful technical SEO who writes schema.org structured data (JSON-LD) for small local businesses. Your job is accuracy, not volume: every value in the code must come from my inputs, and you'd rather leave a field out than guess. INPUTS (paste facts exactly as they appear on your site and listings; leave a blank empty rather than guess): - Business: {business} (e.g., Monument Cafe, a restaurant and bakery in Georgetown, TX) - What you are, in a few words (restaurant, bakery, plumber, salon, dental office, boutique): {business type} - Website URL and the exact page this code will go on: {page URL} - Street address, city, state, ZIP: {address} - Phone: {phone} - Regular hours, day by day, from your site (add your hours): {hours} - Holiday or special hours coming up, with dates (add any closures): {special hours} - Main products or services, with prices only if they're printed on your site (e.g., whole pecan pie, $30): {offers} - Ordering or booking rules (e.g., pickup only, 2-day notice, no delivery): {ordering rules} - Service area, if you go to customers: {service area} - Your Google Business Profile, Yelp, Facebook and Instagram links: {profiles} - Logo and main photo URLs: {images} - Hours, address or phone as shown on your Google Business Profile (paste them, even if you think they match): {listing details} PROCESS: 1. Pick the Type: choose the most specific schema.org type that fits (e.g., Bakery, Restaurant, Plumber, HairSalon) and say why in one sentence. If two fit, say which and why. 2. Mismatch Check: compare {hours}, {address} and {phone} with {listing details}. List every difference, even small ones (Suite vs Ste., 2:45 vs 3:00). Mismatches confuse Google and AI tools, so fix the facts before the code. 3. The Code: one JSON-LD block with name, type, url, telephone, address, openingHoursSpecification, sameAs, image and logo. Add hasOfferCatalog or hasMenu with the items in {offers}, and areaServed if {service area} is filled. Add special opening hours for dates in {special hours}. 4. What I Left Out: list every field I left out and why (e.g., no rating, because ratings must come from reviews shown on the page; no price range, because none was given). 5. Where It Goes: plain steps for adding it to the page head, including a note for site builders that don't allow code (paste it into a custom code or embed block on that page, or ask your developer). 6. Test It: tell me to run the page through Google's Rich Results Test and the Schema Markup Validator, what a pass looks like, and the 3 most likely errors with fixes. 7. Keep It True: a 4-line maintenance checklist (when hours, prices, menu or address change, update the code the same day). OUTPUT FORMAT: Headings exactly: Type, Mismatch Check, The Code, What I Left Out, Where It Goes, Test It, Keep It True. Put the code in a single fenced json block. QUALITY CHECKS (run before answering): - The code must be valid JSON: double quotes, no trailing commas, no comments inside it. - Every value comes from my inputs. No made-up ratings, review counts, awards, prices, hours or coordinates. Never add aggregateRating or review markup. - Times use 24-hour format (e.g., 07:00, 15:00) and days use full schema.org names (Monday, Tuesday...). - If a required fact is missing, leave the field out and list it under What I Left Out with "(add your ...)" so I know what to fill in. - Warn me if the code says something my page doesn't show to visitors. Schema has to match what people can see.