Schema stack

    Contractor License Lookup Stack

    License lookup tools with WebApplication + Service context, FAQs, and breadcrumbs.

    Included schema
    Web Application
    Service
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Contractor license verification search tools
    • State license lookup portals
    • Service pages explaining license compliance checks
    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
    • areaServed.name
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • operatingSystem
    • provider.name
    • serviceType
    • url

    Recommended properties

    • description
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • offers.url
    • softwareVersion
    • url
    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": "WebApplication",
        "@id": "https://www.example.com/licenses/contractor-lookup#app",
        "name": "Contractor License Lookup",
        "description": "Search contractor licenses by name, license number, or company.",
        "applicationCategory": "BusinessApplication",
        "operatingSystem": "Any",
        "url": "https://www.example.com/licenses/contractor-lookup"
      },
      {
        "@context": "https://schema.org",
        "@type": "Service",
        "@id": "https://www.example.com/licenses/contractor-lookup#service",
        "name": "License Verification Service",
        "serviceType": "LicenseVerification",
        "provider": { "@type": "Organization", "name": "Northwind Licensing" },
        "areaServed": { "@type": "AdministrativeArea", "name": "Texas" },
        "url": "https://www.example.com/licenses"
      },
      {
        "@context": "https://schema.org",
        "@type": "FAQPage",
        "mainEntity": [
          {
            "@type": "Question",
            "name": "How often is the data updated?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "License data is refreshed nightly from the state registry."
            }
          },
          {
            "@type": "Question",
            "name": "What if I can't find a contractor?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Check spelling, try the license number, or contact support for assistance."
            }
          },
          {
            "@type": "Question",
            "name": "Does a result confirm good standing?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Results show active status; verify disciplinary actions in the detailed record."
            }
          }
        ]
      },
      {
        "@context": "https://schema.org",
        "@type": "BreadcrumbList",
        "itemListElement": [
          { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
          { "@type": "ListItem", "position": 2, "name": "Licenses", "item": "https://www.example.com/licenses" },
          { "@type": "ListItem", "position": 3, "name": "Contractor Lookup", "item": "https://www.example.com/licenses/contractor-lookup" }
        ]
      }
    ]
    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 jurisdictions?

    If the tool supports multiple states, clarify coverage in page copy and FAQs.

    How do I show verification disclaimers?

    Include disclaimers on the page and summarize them in FAQ answers when needed.

    Primary sources

    References