SwiftSchemaGenerate
    Schema stack

    Rental Application Stack

    Rental application/tenant screening pages with WebPage + Offer context, FAQs, and breadcrumb navigation.

    Open generatorValidate in Rich Results Test
    Included schema
    Web Page
    Offer
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Rental application portals for properties or property managers
    • Tenant screening pages that need clear offer/terms alignment
    • Pages where FAQs clarify fees, timelines, and required documents
    Composition

    What is included

    • Web Page

      Declares the page as the rental application portal.

    • Offer

      Expresses the application offer/fee and destination URL.

    • Frequently Asked Questions

      Answers eligibility, fee, and turnaround questions.

    • Breadcrumb

      Provides navigation context to the application 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

    • availability
    • description
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • price
    • priceCurrency
    • url

    Recommended properties

    • category
    • dateModified
    • inLanguage
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • name
    • priceValidUntil
    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": "WebPage",
    "@id": "https://www.example.com/rentals/apply#page",
    "name": "Rental Application — Oakwood Apartments",
    "description": "Apply online for Oakwood Apartments. Submit screening details and pay the application fee.",
    "url": "https://www.example.com/rentals/apply",
    "inLanguage": "en",
    "dateModified": "2025-02-20"
  },
  {
    "@context": "https://schema.org",
    "@type": "Offer",
    "@id": "https://www.example.com/rentals/apply#offer",
    "name": "Rental Application Fee",
    "price": "45.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/rentals/apply#start",
    "category": "RentalApplication",
    "priceValidUntil": "2025-12-31"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What documents are required?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Government ID, proof of income, rental history, and references."
        }
      },
      {
        "@type": "Question",
        "name": "How long does screening take?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Most applications are processed within 2-3 business days."
        }
      },
      {
        "@type": "Question",
        "name": "Is the fee refundable?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Application fees are non-refundable once submitted. Contact support if you applied in error."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Rentals", "item": "https://www.example.com/rentals" },
      { "@type": "ListItem", "position": 3, "name": "Apply", "item": "https://www.example.com/rentals/apply" }
    ]
  }
]
    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 show multiple offers?

    If you present multiple application types (e.g., individual vs. joint), include one Offer per visible option with distinct URLs.

    Can I omit price?

    If the fee is waived or not shown, keep price at 0.00 and align availability and URL with the visible state.

    Primary sources

    References