SwiftSchemaGenerate
    Schema stack

    Identity Verification Stack

    Identity verification and KYC pages with WebApplication + Service context, FAQs, and breadcrumbs.

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

    When to use this stack

    • KYC onboarding portals for fintech or marketplaces
    • ID verification pages for secure access
    • Compliance verification flows with upload instructions
    Composition

    What is included

    • Web Application

      Defines the identity verification portal experience.

    • Service

      Describes the identity verification service and provider.

    • Frequently Asked Questions

      Answers document requirements, processing time, and data security questions.

    • Breadcrumb

      Provides navigation context for the verification 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

    • 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.

    Validate
    [
  {
    "@context": "https://schema.org",
    "@type": "WebApplication",
    "@id": "https://www.example.com/verify#app",
    "name": "Identity Verification Portal",
    "description": "Verify your identity to complete account setup.",
    "applicationCategory": "SecurityApplication",
    "operatingSystem": "Any",
    "url": "https://www.example.com/verify"
  },
  {
    "@context": "https://schema.org",
    "@type": "Service",
    "@id": "https://www.example.com/verify#service",
    "name": "Identity Verification Service",
    "serviceType": "IdentityVerification",
    "provider": { "@type": "Organization", "name": "Northwind Identity" },
    "areaServed": { "@type": "Country", "name": "United States" },
    "description": "Secure identity checks with document and selfie verification."
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What documents are accepted?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We accept government-issued IDs such as passports and driver licenses."
        }
      },
      {
        "@type": "Question",
        "name": "How long does verification take?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Most verifications complete within a few minutes, but some may take up to 24 hours."
        }
      },
      {
        "@type": "Question",
        "name": "Is my data secure?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Data is encrypted in transit and stored according to compliance standards."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Verify", "item": "https://www.example.com/verify" }
    ]
  }
]
    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 selfie requirements?

    If selfie capture is required, mention it in the FAQ answers and portal instructions.

    How do I show supported countries?

    List supported countries in the Service description or FAQ answers and keep them aligned with the UI.

    Primary sources

    References