A homeowner hunting for a plumber opens a search result, sees a business name, address and opening hours in the snippet, and calls without visiting the site. That snippet came from structured data. Schema markup is a small block of JSON-LD code that labels your pages so search engines can read them accurately. The myth is that you need dozens of types. You don't. Five cover most small sites: Organization, LocalBusiness, Article or BlogPosting, Product with Offer, and BreadcrumbList. Add FAQPage when you have real questions and answers. That's it.

What does schema markup actually do under the hood?

Search engines crawl your page, parse the HTML, and extract structured data from JSON-LD scripts. That data goes into an index. When someone searches, the engine retrieves matching pages and decides how to display them. Schema doesn't boost rankings directly. It helps the engine understand what your page is about and whether it qualifies for a rich result.

Put simply, schema is a label on a box. The box still needs good contents. A page with thin text and ideal schema won't rank. A page with clear text and no schema can still rank, but it may miss visual enhancements in search results.

The JSON-LD format is specified by the W3C in the JSON-LD 1.1 Recommendation (W3C, 2020). Schema.org publishes the vocabulary. Google's own documentation on structured data lists which types trigger rich results and which are just hints. The current in-force version of any standard prevails.

Why do most small sites need only five types?

Because most small sites have five kinds of pages: a home or about page, a location page, content pages, product pages, and a navigation trail. Each maps to one schema type. Adding more types without matching content creates noise.

Google's structured data documentation warns that markup must match the visible page content. Marking up a page as a Product when it's actually a blog post can trigger a manual action for spammy structured data. The rule is simple: if the page doesn't show it, don't mark it.

The five types work together. Organization identifies the brand. LocalBusiness adds location details. Article or BlogPosting describes written content. Product with Offer describes items for sale. BreadcrumbList shows where the page sits in the site structure. FAQPage is the optional sixth when you have genuine Q&A.

Which schema type should you add first?

Start with Organization on the home page. It's the anchor. Google uses it to connect your logo, social profiles and brand name across the site. Without it, the engine may treat subdomains or regional pages as separate entities.

Next, add LocalBusiness to any page with a physical address, phone number or opening hours. This is critical for local search. If you serve customers at their location and have no storefront, use the appropriate subtype such as HomeAndConstructionBusiness or ProfessionalService and mark the service area.

Then add BreadcrumbList site-wide. It's low effort and helps users and engines understand hierarchy. After that, match the remaining types to your page types: Article for blog posts, Product for ecommerce items, FAQPage for question sections.

How do you pick the right type for each page?

Use this decision rule. If the page sells a physical item, use Product with Offer. If it's a written guide or news post, use Article or BlogPosting. If it's a location page, use LocalBusiness. If it's a list of questions, use FAQPage. If it's the home page, use Organization plus WebSite. If it's a category page, use CollectionPage with BreadcrumbList.

Don't stack types that conflict. A page can have Organization and LocalBusiness together if the business is the organization. A page should not be both Article and Product unless it genuinely is both, which is rare.

Google's documentation says multiple structured data blocks are allowed on one page. The engine merges them. Just keep each block focused on one entity.

What does each type look like in JSON-LD?

Here are copy-paste snippets. Replace the placeholder values with your own. These are examples, not a live implementation. Validate them with Google's Rich Results Test or the Schema Markup Validator before publishing.

Organization

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Business Name",
  "url": "https://www.example.com",
  "logo": "https://www.example.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/yourbusiness",
    "https://twitter.com/yourbusiness"
  ]
}

Use on the home page. The sameAs property links to official profiles. Google uses this to confirm brand identity.

LocalBusiness

{
  "@context": "https://schema.org",
  "@type": "Plumber",
  "name": "Your Plumbing Co.",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St",
    "addressLocality": "Springfield",
    "addressRegion": "IL",
    "postalCode": "62701",
    "addressCountry": "US"
  },
  "telephone": "+1-555-123-4567",
  "openingHours": "Mo-Fr 08:00-18:00",
  "url": "https://www.example.com"
}

Use on the contact or location page. The openingHours format follows the schema.org specification. Use 24-hour time.

Article / BlogPosting

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Fix a Leaky Faucet",
  "datePublished": "2026-01-15",
  "dateModified": "2026-02-01",
  "author": {
    "@type": "Person",
    "name": "Jane Doe"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Your Business Name",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.example.com/logo.png"
    }
  }
}

Use on blog posts and guides. The dateModified helps engines see freshness.

Product with Offer

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Copper Pipe 1/2 inch",
  "image": "https://www.example.com/pipe.jpg",
  "description": "Type L copper pipe, 10 ft length",
  "sku": "CP-12-10",
  "offers": {
    "@type": "Offer",
    "url": "https://www.example.com/products/copper-pipe",
    "priceCurrency": "USD",
    "price": "24.99",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition"
  }
}

Use on product pages. Price must match the visible price. Google's merchant listing guidelines require accurate availability and condition.

BreadcrumbList

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://www.example.com"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Plumbing Supplies",
      "item": "https://www.example.com/plumbing"
    }
  ]
}

Use on every page except the home page. The trail must match the visible breadcrumb navigation.

FAQPage

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you offer emergency callouts?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, we offer 24/7 emergency callouts within 20 miles."
      }
    }
  ]
}

Use only on pages with real questions and answers. Google's FAQ rich results are limited to authoritative government and health sites for some query types, so check current documentation.

How do you combine multiple types safely?

Use separate <script type="application/ld+json"> blocks or a single @graph array. Separate blocks are easier to debug. Google's documentation supports both.

The key rule: each entity must be accurate. If you mark up an Organization and a LocalBusiness on the same page, make sure the names, addresses and phone numbers match exactly. Inconsistent data confuses the engine.

Don't nest Product inside Article unless the article is genuinely about that product. Don't add FAQPage to a page where the questions are hidden or not visible. Markup must reflect what a user sees.

How do you test and validate schema markup?

Use Google's Rich Results Test for pages that may qualify for rich results. Use the Schema Markup Validator from schema.org for general vocabulary checks. Both tools are free and public.

Check the rendered HTML, not just the source. Some CMS platforms inject JSON-LD via JavaScript. Google's documentation says it can process JavaScript-generated structured data, but server-rendered markup is more reliable.

Watch Search Console's Enhancement reports. They list valid items, warnings and errors. Fix errors before adding more types. A broken Product markup can suppress rich results for that page.

Schema types by page and priority
Page type Schema type Priority Key property
Home page Organization 1 name, url, logo
Location / contact LocalBusiness 2 address, telephone, openingHours
Blog post / guide Article or BlogPosting 3 headline, datePublished, author
Product page Product with Offer 4 name, offers.price, availability
Any page with hierarchy BreadcrumbList 5 itemListElement
Q&A section FAQPage Optional mainEntity

What mistakes trigger rich result penalties?

Marking up content that isn't visible on the page is the most common. Google's structured data policies call this spammy markup. It can lead to a manual action that removes rich results from your site.

Another mistake is mismatched data. If your LocalBusiness schema says you open at 8am but the page says 9am, that's a violation. Keep schema and visible content in sync.

Using FAQPage on every page with a single question is another. Google's documentation says FAQ markup should be used for genuine FAQ content. Overuse can dilute its value.

Finally, don't add schema for types that don't apply. A blog post doesn't need Product markup. A service page doesn't need Event markup unless there's an event.

Key Takeaways

  • Five schema types cover most small sites: Organization, LocalBusiness, Article/BlogPosting, Product with Offer, and BreadcrumbList.
  • Add FAQPage only when you have real, visible questions and answers.
  • Schema doesn't directly boost rankings; it helps engines understand and qualify pages for rich results.
  • Markup must match visible content. Mismatches can trigger manual actions.
  • Validate with Google's Rich Results Test and Search Console before publishing.
Which schema type should a small business add first?

Start with Organization on the home page. It anchors your brand identity for search engines.

Can I use multiple schema types on one page?

Yes. Use separate JSON-LD blocks or an @graph array. Keep each entity accurate and consistent with visible content.

Do I need LocalBusiness schema if I have no storefront?

If you serve customers at their location, yes. Use a subtype like HomeAndConstructionBusiness and mark your service area.

How do I test if my schema markup is valid?

Use Google's Rich Results Test for rich result eligibility and the Schema Markup Validator for vocabulary checks. Both are free.

Does schema markup actually improve rankings?

Not directly. It helps engines understand your page and can qualify it for rich results, which may improve click-through rates. Rankings depend on content and other factors.

Data sources: the standards and technical parameters referenced in this article are based on the corresponding national/industry standards and the manufacturer's factory QC records; the current in-force version prevails.