Stack

Digital Signature Request Stack

E-signature request pages with WebApplication + Service context, FAQs, and breadcrumbs.

Open generator Validate in Rich Results Test

When to use this stack

Document signing portals for customers or vendors
E-signature request landing pages
Compliance or consent signature workflows

What's included

Web Application
Open generator
Defines the signing portal experience.
Service
Open generator
Describes the digital signature service and provider.
Frequently Asked Questions
Open generator
Answers legal validity, identity verification, and device support questions.
Breadcrumb
Open generator
Provides navigation context for the signature page.

Required properties (stack union)

Ensure every applicable required property is present in your implementation. Nested props reference their parent objects (for example, `offers.priceCurrency`).

applicationCategory

areaServed.name

itemListElement[].name

mainEntity[].@type=Question

mainEntity[].acceptedAnswer.text

name

operatingSystem

provider.name

serviceType

url

Recommended properties (stack union)

description

itemListElement[].item

mainEntity[].acceptedAnswer.text

mainEntity[].author.name

mainEntity[].name

offers.url

softwareVersion

url

Combined JSON-LD

Paste as a single script tag. Keep product details, offer data, shipping/returns, and FAQ answers in sync with the 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" }
    ]
  }
]

Implementation steps

Start from your live product detail page content; ensure titles, prices, and availability match the page.
Embed one JSON-LD script in the head or just before the closing body tag using the combined example as a template.
Fill shipping details for each region you serve and keep them aligned with on-page shipping tables.
Attach your canonical MerchantReturnPolicy URL and keep the policy text in sync with Merchant Center.
Add 3–6 FAQs that address purchase blockers (shipping, returns, compatibility) and keep answers consistent with visible content.
Validate in the Rich Results Test and revalidate after price/availability/policy changes.

Common errors and fixes

Missing currency or availability: ensure `offers.priceCurrency` and `offers.availability` use ISO currency codes and schema URLs.
ShippingDetails missing destination or transit time: include `shippingDestination.addressCountry` and `deliveryTime.transitTime` with units.
MerchantReturnPolicy not linked: reference it from the Offer via `hasMerchantReturnPolicy` and provide a stable policy URL.
FAQ answers don't match the page: keep FAQ content identical to visible answers to avoid review or manual actions.

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.

SwiftSchema

Intuitive Schema Generation at Your Fingertips