Schema stack

    Flight Status Stack

    Flight status pages with WebPage + Flight context, FAQs, and breadcrumbs.

    Included schema
    Web Page
    Flight
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Flight status lookup pages
    • Airline flight tracking pages with delays
    • Airport flight status dashboards
    Composition

    What is included

    • Declares the flight status page and summary.

    • Provides the flight details and current status.

    • Answers delay, gate change, and notification questions.

    • Provides navigation context for the flight status page.

    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

    • arrivalAirport.name
    • arrivalTime
    • departureAirport.name
    • departureTime
    • description
    • flightNumber
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • url

    Recommended properties

    • dateModified
    • estimatedArrivalTime
    • flightStatus
    • inLanguage
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • provider.name
    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": "WebPage",
        "@id": "https://www.example.com/flights/aa-452#page",
        "name": "Flight AA 452 Status",
        "description": "Live status for American Airlines flight AA 452 from Austin to Denver.",
        "url": "https://www.example.com/flights/aa-452",
        "inLanguage": "en",
        "dateModified": "2025-05-10"
      },
      {
        "@context": "https://schema.org",
        "@type": "Flight",
        "@id": "https://www.example.com/flights/aa-452#flight",
        "flightNumber": "AA 452",
        "provider": { "@type": "Airline", "name": "American Airlines" },
        "departureAirport": { "@type": "Airport", "name": "Austin-Bergstrom International Airport" },
        "arrivalAirport": { "@type": "Airport", "name": "Denver International Airport" },
        "departureTime": "2025-05-10T13:05:00-05:00",
        "arrivalTime": "2025-05-10T14:45:00-06:00",
        "flightStatus": "https://schema.org/FlightScheduled",
        "estimatedArrivalTime": "2025-05-10T14:55:00-06:00"
      },
      {
        "@context": "https://schema.org",
        "@type": "FAQPage",
        "mainEntity": [
          {
            "@type": "Question",
            "name": "Where can I find gate information?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Gate details appear on the status page and are updated as the airline publishes changes."
            }
          },
          {
            "@type": "Question",
            "name": "How often is the status updated?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Status updates refresh every 5 minutes or when new data is available."
            }
          },
          {
            "@type": "Question",
            "name": "Can I sign up for alerts?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Yes. Use the alerts button to receive SMS or email updates."
            }
          }
        ]
      },
      {
        "@context": "https://schema.org",
        "@type": "BreadcrumbList",
        "itemListElement": [
          { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
          { "@type": "ListItem", "position": 2, "name": "Flights", "item": "https://www.example.com/flights" },
          { "@type": "ListItem", "position": 3, "name": "AA 452", "item": "https://www.example.com/flights/aa-452" }
        ]
      }
    ]
    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

    Should I include multiple legs?

    If the page shows multi-leg info, include separate Flight entries for each leg.

    How do I show cancellations?

    Use a FlightStatus of FlightCancelled and align the page copy with the status.

    Primary sources

    References