← Home

Organization and FAQ structured data: help machines name you correctly

Structured data (usually JSON-LD) is a machine-readable copy of facts that already appear on your pages. For a small business, the useful pieces are usually Organization (who you are) and, when you have real Q&A, FAQPage (common questions in a fixed shape).

Checked against schema.org and Google Search Central on 13 October 2026. Markup does not guarantee AI citations or Search features.

Organization: what Google says it is for

Google’s Organization documentation says homepage (or About) markup can help Google understand administrative details and disambiguate your organization in Search. Some properties work behind the scenes; others can influence visuals such as which logo appears. There are no required properties — add what applies.

Google recommends placing this on the home page or a single About page, not on every URL, and using the most specific subtype when it fits (for example LocalBusiness or OnlineStore).

Source: Organization structured data (Google) · type definition: schema.org/Organization

Minimal Organization example (must match the visible page)

Replace placeholders. Google’s AI-features guidance says structured data should match the visible text on the page.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Bakery Ltd",
  "legalName": "Example Bakery ApS",
  "url": "https://www.example.com/",
  "logo": "https://www.example.com/logo.png",
  "email": "hello@example.com",
  "telephone": "+45-12-34-56-78",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Hovedgaden 1",
    "addressLocality": "Copenhagen",
    "postalCode": "2100",
    "addressCountry": "DK"
  },
  "sameAs": [
    "https://www.linkedin.com/company/example"
  ]
}
</script>

Useful fields for disambiguation (when true for you): legalName, vatID / tax IDs, sameAs profile URLs, physical address. Inventing identifiers is worse than omitting them.

FAQPage: still useful as structure — not as a Google FAQ rich result

schema.org/FAQPage marks a page whose main content is a list of questions and answers.

Important Google change (2026): Google deprecated the FAQ rich result feature (announced May 2026; documentation removed June 2026). So do not add FAQ markup expecting a special FAQ box in Google Search results. We still use FAQPage because:

Sources: Google Search documentation updates (May–June 2026 FAQ rich result entries) · schema.org/FAQPage

Minimal FAQPage example

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you offer catering?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. We cater for 10–80 people in the Copenhagen area. Email hello@example.com with the date and headcount."
      }
    },
    {
      "@type": "Question",
      "name": "Where are you located?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Hovedgaden 1, 2100 Copenhagen, Denmark."
      }
    }
  ]
}
</script>

Put the same questions and answers in ordinary HTML headings and paragraphs so the markup is not the only place the facts exist.

What structured data will not fix

Source: Google AI optimization guide · AI features and your website

Check your own pages

Our free check looks for Organization or WebSite JSON-LD, visible business facts, and FAQPage or Q&A headings. It does not score Search rankings or citations.

Run the free AI-readiness check