Common Schema Types Every Website Should Use

Schema markup might sound like something only developers care about, but it’s actually one of the most straightforward ways to help search engines understand your content. I’ve been implementing structured data for years, and honestly? Most websites are missing out on some pretty significant opportunities.

The thing is, Google and other search engines are constantly trying to figure out what your pages are actually about. Schema gives them a helping hand by providing clear, structured information about your business, products, articles, and more. It’s like giving search engines a roadmap to your content.

But here’s where it gets interesting. Not all schema types are created equal.

Some will make a noticeable difference to how your site appears in search results, whilst others might feel like you’re just ticking boxes. I think it’s worth focusing on the ones that actually move the needle for most websites.

LocalBusiness Schema Makes You Visible

If you run any kind of local business, this schema type should be your absolute priority. I’ve seen businesses go from invisible in local searches to appearing prominently in map results just by implementing LocalBusiness schema properly.

What it does is pretty straightforward. It tells search engines exactly where you’re located, when you’re open, what services you provide & how people can contact you. Google uses this information to show your business in local search results and Google Business Profile listings.

The beauty of LocalBusiness schema lies in its simplicity. You don’t need to overthink it – just provide the basic information that customers actually need. Opening hours, address, phone number, and maybe your service area if you travel to customers.

Here’s a copy-paste example that you can adapt for your own business:

{
  “@context”: “https://schema.org”,
  “@type”: “LocalBusiness”,
  “name”: “Smith’s Plumbing Services”,
  “description”: “Professional plumbing services in Manchester”,
  “address”: {
    “@type”: “PostalAddress”,
    “streetAddress”: “123 High Street”,
    “addressLocality”: “Manchester”,
    “postalCode”: “M1 1AA”,
    “addressCountry”: “GB”
  },
  “telephone”: “+44 161 123 4567”,
  “openingHours”: [
    “Mo-Fr 08:00-17:00”,
    “Sa 09:00-15:00”
  ],
  “url”: “https://www.smithsplumbing.co.uk”
}

Article Schema Boosts Content Recognition

Every blog post, news article, or substantial piece of content on your website should have Article schema. It’s one of those things that seems obvious once you start using it, but so many sites skip it entirely.

Article schema helps search engines understand what type of content you’ve created, who wrote it, when it was published & what it’s about. This can lead to rich snippets in search results – you know, those enhanced listings that show author names, publication dates, and sometimes even star ratings.

I’ve noticed that articles with proper schema markup tend to perform better in search results. Not dramatically, but consistently. It’s like the difference between wearing a name tag at a networking event and not – people just understand who you are more quickly.

The key is being accurate with your information. Don’t inflate your word counts or claim authorship if someone else wrote the content. Search engines are getting smarter at detecting these inconsistencies.

{
  “@context”: “https://schema.org”,
  “@type”: “Article”,
  “headline”: “How to Choose the Right Boiler for Your Home”,
  “description”: “A comprehensive guide to selecting the perfect boiler”,
  “author”: {
    “@type”: “Person”,
    “name”: “John Smith”
  },
  “datePublished”: “2024-01-15”,
  “dateModified”: “2024-01-20”,
  “publisher”: {
    “@type”: “Organization”,
    “name”: “Smith’s Plumbing Services”,
    “logo”: {
      “@type”: “ImageObject”,
      “url”: “https://www.smithsplumbing.co.uk/logo.png”
    }
  },
  “mainEntityOfPage”: {
    “@type”: “WebPage”,
    “@id”: “https://www.smithsplumbing.co.uk/boiler-guide”
  }
}

Product Schema Drives Sales

If you sell anything online, Product schema is absolutely essential. I mean, why wouldn’t you want your products to show up with prices, availability, and star ratings directly in search results?

Product schema creates those rich product snippets that catch people’s attention when they’re searching. Price, stock status, reviews – all visible before someone even clicks through to your site.

The tricky part isn’t implementing it though. It’s keeping it accurate. Nothing annoys potential customers more than seeing one price in search results and finding a different price on your actual website. I’ve seen this mistake cost businesses serious money.

You’ll want to make sure your schema reflects real stock levels too. If something’s out of stock, mark it as such. Search engines appreciate honesty, and customers definitely do.

Here’s a product schema example that covers the essentials:

{
  “@context”: “https://schema.org”,
  “@type”: “Product”,
  “name”: “Combi Boiler Installation Service”,
  “description”: “Professional combi boiler installation with 2-year warranty”,
  “brand”: {
    “@type”: “Brand”,
    “name”: “Worcester Bosch”
  },
  “offers”: {
    “@type”: “Offer”,
    “price”: “2499.00”,
    “priceCurrency”: “GBP”,
    “availability”: “https://schema.org/InStock”,
    “seller”: {
      “@type”: “Organization”,
      “name”: “Smith’s Plumbing Services”
    }
  },
  “aggregateRating”: {
    “@type”: “AggregateRating”,
    “ratingValue”: “4.8”,
    “reviewCount”: “127”
  }
}

FAQ Schema Answers Questions Directly

FAQ schema might be the most underutilised schema type I come across. It’s brilliant for capturing those “People also ask” spots in Google search results, but barely anyone uses it properly.

When implemented correctly, your FAQ content can appear as an expandable section right in the search results. People can get their questions answered without even visiting your site – which might sound counterproductive, but actually builds trust and increases click-through rates.

I think the secret is choosing questions that naturally lead to wanting more information. Answer the basic query, but make it clear there’s more detail available on your site. Don’t give away everything in the FAQ schema – just enough to be helpful.

The format is pretty straightforward, but you need to make sure your questions are genuinely frequently asked. Don’t just make up questions that sound good – use real customer queries.

{
  “@context”: “https://schema.org”,
  “@type”: “FAQPage”,
  “mainEntity”: [{
    “@type”: “Question”,
    “name”: “How long does a boiler installation take?”,
    “acceptedAnswer”: {
      “@type”: “Answer”,
      “text”: “Most boiler installations take between 6-8 hours, depending on the complexity of the job and whether any additional pipework is needed.”
    }
  }, {
    “@type”: “Question”,
    “name”: “Do you provide a warranty on installations?”,
    “acceptedAnswer”: {
      “@type”: “Answer”,
      “text”: “Yes, we provide a comprehensive 2-year warranty on all installations, covering both parts and labour.”
    }
  }]
}

Breadcrumb Schema Improves Navigation

Breadcrumb schema is one of those subtle improvements that makes a bigger difference than you’d expect. It shows the navigation path in search results, helping people understand where a page sits within your site structure.

You’ve probably seen breadcrumbs in search results – they look like “Home > Services > Boiler Repair” underneath the page title. They might seem minor, but they actually help with click-through rates because people can see exactly what section of your site they’re about to visit.

The navigation clarity is particularly valuable for larger websites with complex structures. If someone’s searching for a specific service, breadcrumbs show them immediately that they’ve found the right section.

Implementation is refreshingly simple compared to some other schema types. You just need to map out the page hierarchy and present it in a structured format.

{
  “@context”: “https://schema.org”,
  “@type”: “BreadcrumbList”,
  “itemListElement”: [{
    “@type”: “ListItem”,
    “position”: 1,
    “name”: “Home”,
    “item”: “https://www.smithsplumbing.co.uk/”
  }, {
    “@type”: “ListItem”,
    “position”: 2,
    “name”: “Services”,
    “item”: “https://www.smithsplumbing.co.uk/services/”
  }, {
    “@type”: “ListItem”,
    “position”: 3,
    “name”: “Boiler Repair”,
    “item”: “https://www.smithsplumbing.co.uk/services/boiler-repair/”
  }]
}

Getting The Implementation Right

The technical side of adding schema markup isn’t particularly complicated, but there are a few things that can trip you up. First, decide whether you want to use JSON-LD (which I recommend), Microdata, or RDFa. JSON-LD is cleaner and easier to maintain.

You can add the JSON-LD code directly to your HTML head section, or if you’re using WordPress, there are plugins that handle it for you. I prefer doing it manually because you have more control, but plugins work fine for basic implementations.

Always test your schema markup using Google’s Rich Results Test tool. It’ll catch errors and show you how your content might appear in search results. Don’t skip this step – broken schema markup is sometimes worse than no schema at all.

One mistake I see repeatedly is inconsistent information between the schema markup and the visible page content. If your schema says your business opens at 9am but your website says 8am, that’s a problem. Keep everything synchronised.

Remember that schema markup is about accuracy, not marketing fluff. Don’t exaggerate prices, ratings, or availability. Search engines are getting better at detecting these discrepancies, and they can actually penalise sites that provide misleading structured data.

Common Mistakes To Avoid

After implementing schema markup on hundreds of websites, I’ve seen the same mistakes over and over again. The biggest one is trying to markup everything at once instead of focusing on what actually matters for your specific business.

Start with one or two schema types that make sense for your content. Master those, then expand. Don’t create a massive JSON-LD block that tries to cover every possible property – it becomes unwieldy and hard to maintain.

Another common error is copying schema examples without adapting them properly. Those template examples you find online need to be customised with your actual business information. Leaving placeholder text or incorrect URLs will hurt more than it helps.

Don’t forget about mobile users when you’re testing. Schema markup affects how your content appears across all devices, and sometimes there are differences in how rich snippets display on mobile versus desktop. Check both.

Finally, remember that schema markup isn’t a magic bullet for SEO. It helps search engines understand your content better, but it won’t fix fundamental issues with your website structure, content quality, or user experience. Think of it as an enhancement, not a cure-all.

The Bottom Line

Schema markup represents one of those rare opportunities where a relatively small technical investment can yield noticeable improvements in search visibility. The five schema types I’ve covered – LocalBusiness, Article, Product, FAQ, and Breadcrumb – will handle the majority of use cases for most websites.

I’d recommend starting with whichever schema type most closely matches your primary business model. Local business? Start there. E-commerce? Product schema first. Content site? Article markup should be your priority.

The key is consistency and accuracy. Implement schema markup properly, keep it updated, and monitor how it affects your search performance. You probably won’t see overnight changes, but over time, the cumulative effect can be quite significant.

Most importantly, don’t overthink it. Schema markup is meant to be helpful, not perfect. Start with the basics, get them right, and build from there.