SwiftSchemaGenerate
    Schema stack

    Childcare / Daycare Stack

    Daycare/childcare center pages with ChildCare + LocalBusiness context, FAQs, and breadcrumb navigation.

    Open generatorValidate in Rich Results Test
    Included schema
    Child Care
    Local Business
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Daycare center landing pages with hours and enrollment
    • Childcare program pages with pricing and schedules
    • Pages where FAQs clarify age ranges and policies
    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.addressLocality
    • address.addressRegion
    • address.streetAddress
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • telephone
    • url

    Recommended properties

    • address.addressCountry
    • geo.latitude
    • geo.longitude
    • image
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • openingHoursSpecification
    • priceRange
    • sameAs[]
    Copy-ready example

    Combined JSON-LD

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

    Validate
    [
  {
    "@context": "https://schema.org",
    "@type": "ChildCare",
    "@id": "https://www.example.com/childcare/greenwood#center",
    "name": "Greenwood Daycare",
    "url": "https://www.example.com/childcare/greenwood",
    "telephone": "+1-206-555-0174",
    "image": "https://www.example.com/images/greenwood-daycare.webp",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "450 Pine St",
      "addressLocality": "Seattle",
      "addressRegion": "WA",
      "postalCode": "98101",
      "addressCountry": "US"
    },
    "openingHoursSpecification": [
      {
        "@type": "OpeningHoursSpecification",
        "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
        "opens": "07:30",
        "closes": "18:00"
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "LocalBusiness",
    "@id": "https://www.example.com/childcare/greenwood#business",
    "name": "Greenwood Daycare",
    "url": "https://www.example.com/childcare/greenwood",
    "telephone": "+1-206-555-0174",
    "address": {
      "@type": "PostalAddress",
      "addressCountry": "US"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What ages do you accept?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We accept children from 6 months to 5 years old."
        }
      },
      {
        "@type": "Question",
        "name": "Do you provide meals?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Breakfast, lunch, and snacks are included."
        }
      },
      {
        "@type": "Question",
        "name": "How do I schedule a tour?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Tours can be scheduled online or by calling the center."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Childcare", "item": "https://www.example.com/childcare" },
      { "@type": "ListItem", "position": 3, "name": "Greenwood", "item": "https://www.example.com/childcare/greenwood" }
    ]
  }
]
    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 list multiple locations?

    Yes. Use one ChildCare entity per location with unique @id values.

    Do I need both ChildCare and LocalBusiness?

    Yes. ChildCare captures the facility details, while LocalBusiness strengthens local entity signals.

    Primary sources

    References