A homeowner searching for a plumber sees two results. One shows stars and a price range. The other is plain text. The difference is usually structured data — and most small sites need only five types of it. Schema markup is code that tells search engines and AI answer engines what a page is about, in a format they can read without guessing.

Start with Organization, LocalBusiness, Article, Product and FAQPage. That covers most small business sites. Everything else can wait until you have a specific reason to add it.

Why does schema matter for a small site?

Search engines and AI answer engines read your page in stages: crawl, index, retrieve, cite. Schema helps at the index and retrieve stages. It labels your content so the system can match it to a query without parsing every sentence.

Google's own documentation says structured data helps it understand page content and can make pages eligible for rich results. It does not ensure a ranking boost. The benefit is eligibility and clarity, not a magic score.

For AI answer engines, the effect is similar. When a system retrieves a page to answer a question, clean entity labels make it easier to pull the right fact, price or location. Schema.org, the shared vocabulary behind all of this, defines the types and properties. Google, Bing and other search engines read that vocabulary.

Put simply: schema does not make a bad page good. It makes a good page easier to read.

What are the 5 schema types most small sites need?

The five are Organization, LocalBusiness, Article, Product and FAQPage. Each one answers a different question a search engine or AI system asks about your site.

  • Organization — who runs the site? Use it on the homepage or about page.
  • LocalBusiness — where do you operate and when are you open? Use it on the contact or location page.
  • Article — what is this piece of content? Use it on blog posts and guides.
  • Product — what do you sell, at what price, and is it in stock? Use it on product pages.
  • FAQPage — what questions does this page answer? Use it on pages with a real Q&A block.

That is the whole list for most small sites. A restaurant might swap Product for Menu. A consultant might skip Product entirely. The principle holds: pick the type that matches what the page actually is.

Schema typeWhere to put itWhat it tells the engineEffort
OrganizationHomepage or about pageBrand name, logo, contact, social profilesLow
LocalBusinessContact or location pageAddress, opening hours, phone, service areaLow
ArticleBlog posts and guidesHeadline, author, publish date, publisherLow
ProductProduct pagesName, price, availability, reviewsMedium
FAQPagePages with a Q&A blockQuestions and short answersLow

Which one should you add first?

Start with the type that matches your main money page. If you sell products, Product comes first. If you run a local service, LocalBusiness comes first. If you publish content, Article comes first.

Organization is the anchor. Add it once on the homepage and reference it from other types. That way every other block points back to the same entity.

FAQPage comes last. Add it only when the page already has a visible question-and-answer section. Google's documentation is clear that FAQ rich results are limited to well-known, authoritative government and health sites. The markup still helps machines parse the content, but do not expect a rich result for a small commercial site.

If you are unsure, add Organization and LocalBusiness this week. They take under an hour and cover the basics.

What does each JSON-LD block look like?

JSON-LD is a script tag that holds structured data in JSON format. You paste it into the page HTML, usually in the head or before the closing body tag. Google recommends JSON-LD over other formats.

Here are five copy-paste templates. Replace the placeholder values with your own. Do not leave empty fields.

1. Organization

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company Name",
  "url": "https://www.example.com",
  "logo": "https://www.example.com/logo.png",
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-555-0100",
    "contactType": "customer service"
  },
  "sameAs": [
    "https://www.linkedin.com/company/yourcompany"
  ]
}
</script>

2. LocalBusiness

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Your Company Name",
  "image": "https://www.example.com/store.jpg",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main Street",
    "addressLocality": "Springfield",
    "addressRegion": "IL",
    "postalCode": "62701",
    "addressCountry": "US"
  },
  "telephone": "+1-555-0100",
  "openingHoursSpecification": {
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
    "opens": "09:00",
    "closes": "17:00"
  },
  "url": "https://www.example.com"
}
</script>

3. Article

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Choose a Plumber",
  "datePublished": "2026-01-15",
  "dateModified": "2026-02-01",
  "author": {
    "@type": "Person",
    "name": "Jane Doe"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Your Company Name",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.example.com/logo.png"
    }
  },
  "mainEntityOfPage": "https://www.example.com/blog/choose-plumber"
}
</script>

4. Product

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Copper Pipe 15mm",
  "image": "https://www.example.com/pipe.jpg",
  "description": "15mm copper pipe, 3m length.",
  "sku": "CP-15-3M",
  "offers": {
    "@type": "Offer",
    "url": "https://www.example.com/products/copper-pipe",
    "priceCurrency": "USD",
    "price": "24.99",
    "availability": "https://schema.org/InStock"
  }
}
</script>

5. FAQPage

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you offer emergency callouts?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, we offer emergency callouts within 30 miles."
      }
    }
  ]
}
</script>

These are typical examples. Your values will differ. Keep every field truthful and visible on the page.

Can you combine several types on one page?

Yes. You can put more than one JSON-LD block on a page, or nest types inside a single block using @graph. Google's documentation supports multiple blocks.

A common mistake is marking up content that is not visible. If the page does not show a price, do not put a price in the Product block. If the FAQ section is hidden behind a script, the markup still needs to match what a user sees.

Another mistake is mixing types that describe different things. A blog post is an Article, not a Product. A contact page is a LocalBusiness, not an Article. Pick the type that matches the page's main purpose.

If you sell services rather than goods, use Service instead of Product. It is not in the five because most small sites either sell products or run a local business. Add it when your main offer is a service with a defined scope.

When does schema not help?

Schema will not fix thin content, slow pages or bad internal linking. It will not force a rich result. Google decides which rich results to show, and many types have eligibility rules.

FAQPage is the clearest example. Google's FAQ rich results are limited to authoritative government and health sites. A small commercial site can add the markup, but it should not expect stars or an expanded box.

Product markup without real reviews will not show stars. Review markup must come from real, visible reviews. Fake review markup can lead to a manual action, which is a penalty applied by a human reviewer at Google.

So the honest answer is: schema improves clarity, not rankings by itself. Add it because it makes your site easier to parse, not because it promises a boost.

How do you check that the markup works?

Use Google's Rich Results Test and the Schema Markup Validator. Both are free. The Rich Results Test shows which rich results a page is eligible for. The Schema Markup Validator checks the markup against the schema.org vocabulary.

A typical check takes five minutes per page. Paste the URL or the code, run the test, fix any errors, and re-test. Warnings are usually fine; errors are not.

Common errors include missing required fields, wrong date formats, and values that do not match the visible page. Dates must follow ISO 8601, for example 2026-01-15. Prices must be numbers, not text with currency symbols.

After you deploy, check again. A theme update or a plugin change can strip the script tag. Add a monthly check to your routine.

Key Facts at a Glance

  • Most small sites need five schema types: Organization, LocalBusiness, Article, Product and FAQPage.
  • Add the type that matches your main money page first, then Organization as the anchor.
  • JSON-LD is the recommended format; paste it into the page HTML and validate it.
  • Schema improves clarity and eligibility, not rankings by itself.
  • FAQ rich results are limited to authoritative government and health sites, per Google's documentation.
  • Use the Rich Results Test and Schema Markup Validator to catch errors before and after deployment.
What schema markup should a small business start with?

Start with Organization on the homepage, then add the type that matches your main page: LocalBusiness for a local service, Product for an online shop, Article for a blog. These three cover most small sites.

Do I need schema markup if I have a small website?

You do not need it to rank, but it helps search engines and AI systems understand your pages. The five types above take a few hours to add and cover the basics.

Can I use multiple schema types on one page?

Yes. You can use separate JSON-LD blocks or a single block with @graph. Keep each type matched to the page's main purpose and make sure the marked-up content is visible.

How do I test if my schema markup is valid?

Use Google's Rich Results Test and the Schema Markup Validator. Both are free. Fix errors, re-test, and check again after any theme or plugin update.

Does schema markup actually improve rankings?

Google says structured data helps it understand content and can make pages eligible for rich results. It does not ensure a ranking boost. The main benefit is clarity for search and AI systems.