SwiftSchemaGenerate
    Schema stack

    Digital Signature Request Stack

    E-signature request 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

    • Document signing portals for customers or vendors
    • E-signature request landing pages
    • Compliance or consent signature workflows
    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.

    Validate
    [
  {
    "@context": "https://schema.org",
    "@type": "WebApplication",
    "@id": "https://www.example.com/sign/requests#app",
    "name": "Document Signature Portal",
    "description": "Review and sign documents securely online.",
    "applicationCategory": "BusinessApplication",
    "operatingSystem": "Any",
    "url": "https://www.example.com/sign/requests"
  },
  {
    "@context": "https://schema.org",
    "@type": "Service",
    "@id": "https://www.example.com/sign#service",
    "name": "Digital Signature Service",
    "serviceType": "ElectronicSignature",
    "provider": { "@type": "Organization", "name": "Northwind Sign" },
    "areaServed": { "@type": "Country", "name": "United States" },
    "description": "Legally binding electronic signatures with audit trails.",
    "url": "https://www.example.com/sign/requests"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Are electronic signatures legally binding?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. E-signatures are legally binding when they meet ESIGN and UETA requirements."
        }
      },
      {
        "@type": "Question",
        "name": "How is signer identity verified?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Signers verify identity via email authentication and optional SMS codes."
        }
      },
      {
        "@type": "Question",
        "name": "Can I sign on mobile?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. The portal works on modern mobile and desktop browsers."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Sign", "item": "https://www.example.com/sign" },
      { "@type": "ListItem", "position": 3, "name": "Requests", "item": "https://www.example.com/sign/requests" }
    ]
  }
]
    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 audit trail details?

    If the page describes audit trails, mention them in the Service description and FAQ answers.

    How do I show signer roles?

    Include signer roles in the page copy and mirror them in the FAQ answers if relevant.

    Primary sources

    References