SwiftSchemaGenerate
    Schema stack

    Shipment / Order Tracking Stack

    Order tracking pages with WebApplication + ParcelDelivery, FAQs, and breadcrumb navigation.

    Open generatorValidate in Rich Results Test
    Included schema
    Web Application
    Parcel Delivery
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Shipment tracking portals with status updates
    • Order tracking pages tied to a tracking number
    • Pages where FAQs clarify delivery windows and exceptions
    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

    • applicationCategory
    • deliveryStatus
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • operatingSystem
    • provider.name
    • trackingNumber
    • trackingUrl
    • url

    Recommended properties

    • deliveryAddress.streetAddress
    • description
    • expectedArrivalUntil
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • offers.url
    • provider.url
    • softwareVersion
    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": "WebApplication",
    "@id": "https://www.example.com/track#app",
    "name": "Shipment Tracking Portal",
    "description": "Track your shipment status and delivery updates in real time.",
    "applicationCategory": "BusinessApplication",
    "operatingSystem": "Any",
    "url": "https://www.example.com/track",
    "offers": {
      "@type": "Offer",
      "url": "https://www.example.com/track"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "ParcelDelivery",
    "@id": "https://www.example.com/track/ABC123#parcel",
    "trackingNumber": "ABC123",
    "trackingUrl": "https://www.example.com/track/ABC123",
    "deliveryStatus": "https://schema.org/InTransit",
    "provider": {
      "@type": "Organization",
      "name": "Example Logistics",
      "url": "https://www.example.com"
    },
    "deliveryAddress": {
      "@type": "PostalAddress",
      "streetAddress": "1200 Market St"
    },
    "expectedArrivalUntil": "2025-10-02"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Why is my tracking not updating?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Updates can take up to 24 hours after pickup. Contact support if no scans appear after 48 hours."
        }
      },
      {
        "@type": "Question",
        "name": "What happens if delivery is delayed?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Delays are shown on the tracking page and we send a notification with a revised ETA."
        }
      },
      {
        "@type": "Question",
        "name": "Can I change the delivery address?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Address changes are available before the package is out for delivery via the tracking portal."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Track Order", "item": "https://www.example.com/track" }
    ]
  }
]
    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 packages?

    If the page lists multiple packages, add a ParcelDelivery entry for each tracking number.

    Do I need delivery address details?

    Include deliveryAddress only if the page shows the destination address.

    Primary sources

    References