Schema stack

    Contact / Location Stack

    Contact/location pages with contact page markup, org/local identity, FAQs, and breadcrumb context.

    Included schema
    Contact Page
    Local Business
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Contact/location pages with address, map, and hours
    • Branch pages where FAQs cover parking, hours, and appointments
    • Support contact hubs needing navigation clarity
    Composition

    What is included

    Data contract

    Properties across the bundle

    Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.

    Required properties

    • address.addressCountry
    • address.addressLocality
    • address.addressRegion
    • address.streetAddress
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • telephone
    • url

    Recommended properties

    • description
    • geo.latitude
    • geo.longitude
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • openingHours
    Copy-ready example

    Combined JSON-LD

    Paste this as one script tag, then replace every example value with data from the live page.

    [
      {
        "@context": "https://schema.org",
        "@type": "ContactPage",
        "@id": "https://www.example.com/contact#page",
        "name": "Contact Us",
        "url": "https://www.example.com/contact",
        "description": "Get in touch with our team or visit our office."
      },
      {
        "@context": "https://schema.org",
        "@type": "LocalBusiness",
        "@id": "https://www.example.com/contact#office",
        "name": "Northwind Analytics HQ",
        "url": "https://www.example.com/contact",
        "telephone": "+1-415-555-0000",
        "address": { "@type": "PostalAddress", "streetAddress": "200 Market St", "addressLocality": "San Francisco", "addressRegion": "CA", "postalCode": "94105", "addressCountry": "US" },
        "openingHours": "Mo-Fr 09:00-18:00",
        "geo": { "@type": "GeoCoordinates", "latitude": 37.792, "longitude": -122.395 }
      },
      {
        "@context": "https://schema.org",
        "@type": "FAQPage",
        "mainEntity": [
          { "@type": "Question", "name": "Where do I park?", "acceptedAnswer": { "@type": "Answer", "text": "Validated parking is available in the Market Street Garage next door." } },
          { "@type": "Question", "name": "Do you accept walk-ins?", "acceptedAnswer": { "@type": "Answer", "text": "Visits are by appointment only. Please schedule ahead." } }
        ]
      },
      {
        "@context": "https://schema.org",
        "@type": "BreadcrumbList",
        "itemListElement": [
          { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
          { "@type": "ListItem", "position": 2, "name": "Contact", "item": "https://www.example.com/contact" }
        ]
      }
    ]
    Workflow

    Implement and verify

    1. 01

      Start with the live page

      Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.

    2. 02

      Add one JSON-LD script

      Use the combined example as a template in the document head or before the closing body tag.

    3. 03

      Complete regional details

      Fill shipping destinations and timing for every region the page actually serves.

    4. 04

      Link the return policy

      Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.

    5. 05

      Match visible answers

      Add only FAQs that users can read on the same page, with identical answers.

    6. 06

      Validate after changes

      Run Rich Results Test after implementation and whenever price, availability, or policy data changes.

    Quality check

    Common errors and fixes

    • Missing currency or availability

      Use ISO currency codes and complete schema.org availability URLs in Offer data.

    • Incomplete shipping details

      Include shippingDestination.addressCountry and deliveryTime.transitTime with units.

    • Return policy is not connected

      Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.

    • FAQ answers differ from the page

      Keep structured FAQ answers identical to visible answers.

    Questions

    Stack FAQs

    Can I use Organization instead of LocalBusiness?

    Yes. Use the type that matches the page. For branches, LocalBusiness is better; for HQ contact, Organization works.

    Should I include map coordinates?

    Recommended if you show a map; include latitude/longitude for clarity.

    Primary sources

    References