SwiftSchemaGenerate
    Schema stack

    Brand Identity Stack

    Company/about hubs with Organization, WebSite, Logo, About/Contact pages, FAQs, and breadcrumb context.

    Open generatorValidate in Rich Results Test
    Included schema
    Organization
    Website
    Logo
    About Page
    Contact Page
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • About/brand hubs consolidating logo, about, and contact info
    • Company profile pages needing clear entity signals and navigation
    • Pages where FAQs clarify mission, locations, and press inquiries
    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

    • itemListElement[].name
    • logo
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • url

    Recommended properties

    • contactPoint.contactType
    • contactPoint.telephone
    • description
    • height
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • potentialAction.query-input
    • potentialAction.target
    • sameAs[]
    • width
    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": "Organization",
    "@id": "https://www.example.com/#org",
    "name": "Northwind Analytics",
    "url": "https://www.example.com",
    "logo": "https://www.example.com/images/logo-120x60.png",
    "sameAs": ["https://www.linkedin.com/company/northwind-analytics", "https://twitter.com/northwind"]
  },
  {
    "@context": "https://schema.org",
    "@type": "WebSite",
    "name": "Northwind Analytics",
    "url": "https://www.example.com",
    "potentialAction": {
      "@type": "SearchAction",
      "target": "https://www.example.com/search?q={search_term_string}",
      "query-input": "required name=search_term_string"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "Logo",
    "url": "https://www.example.com/images/logo-512.png",
    "name": "Northwind Analytics Logo",
    "width": 512,
    "height": 512
  },
  {
    "@context": "https://schema.org",
    "@type": "AboutPage",
    "name": "About Northwind",
    "url": "https://www.example.com/about",
    "description": "Learn about Northwind Analytics, our mission, and leadership."
  },
  {
    "@context": "https://schema.org",
    "@type": "ContactPage",
    "name": "Contact Northwind",
    "url": "https://www.example.com/contact",
    "description": "Press and customer contact for Northwind Analytics."
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      { "@type": "Question", "name": "Where are you based?", "acceptedAnswer": { "@type": "Answer", "text": "HQ in San Francisco with teams in NYC and remote across the US." } },
      { "@type": "Question", "name": "Do you have a media kit?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. See our press page for logos and brand assets." } }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "About", "item": "https://www.example.com/about" }
    ]
  }
]
    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

    Do I need Logo type if I already use Organization.logo?

    Optional. Including Logo as a dedicated object provides a clear brand asset; ensure URLs and dimensions are correct.

    Can I add SearchAction?

    Yes. Include it on WebSite to clarify site search; keep it aligned with your real search URL.

    Primary sources

    References