Schema Markup for Beginners: Types That Win Rich Results

There are three ways to add schema to a page — JSON-LD, Microdata, and RDFa. In practice, the choice is between the first two. RDFa is rarely worth the effort.

JSON-LD wins for almost every use case. It lives in a single <script type="application/ld+json"> block, so redesigning your page layout never accidentally breaks your structured data. Google's own documentation shows JSON-LD examples first. Use it.

Google supports dozens of schema types, but only a handful regularly produce visible rich results in search. Focus your effort here.

1. FAQ — Expands your listing with up to 10 question-and-answer pairs directly in search results. Best for support pages, product pages with common objections, and how-to content.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is schema markup?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Schema markup is structured data added to HTML that helps search engines understand your content."
      }
    }
  ]
}

2. Article — Signals to Google that a page is editorial content. Unlocks the Top Stories carousel for news sites and improves content understanding for blog posts.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Schema Markup for Beginners",
  "author": { "@type": "Person", "name": "Jane Smith" },
  "datePublished": "2025-03-01",
  "publisher": {
    "@type": "Organization",
    "name": "UtilityApp",
    "logo": { "@type": "ImageObject", "url": "https://utilityapp.lat/logo.png" }
  }
}

3. Product — The highest-value schema for e-commerce. Enables star ratings, price, availability, and review counts directly in results. Requires an offers property with a valid priceCurrency and price.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Wireless Keyboard",
  "offers": {
    "@type": "Offer",
    "price": "49.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.6",
    "reviewCount": "312"
  }
}

4. LocalBusiness — Essential for any physical location. Powers the Knowledge Panel, map pack listings, and business hours in search results.

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Bright Dental Clinic",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "240 Main Street",
    "addressLocality": "Austin",
    "addressRegion": "TX",
    "postalCode": "78701"
  },
  "telephone": "+1-512-555-0100",
  "openingHours": "Mo-Fr 09:00-18:00"
}

Writing the JSON-LD is only half the job. Validate before you deploy — broken schema produces zero benefit and wastes crawl budget.

• Google's Rich Results Test (search.google.com/test/rich-results) — the definitive tool. Paste a URL or raw HTML and see exactly which rich result types are eligible, plus any field-level errors. Run this every time you add or change schema.
• Schema.org Validator (validator.schema.org) — checks conformance to the full schema.org specification, not just Google's subset. Useful for catching property typos.
• Google Search Console — after deploying, the Enhancements section shows live data: how many pages have each schema type, which are valid, and which have warnings or errors. This is your ongoing monitor, not a one-time check.

One practical tip: test the live URL, not just the raw markup. Googlebot's rendering can differ from your source HTML, especially on JavaScript-heavy pages where schema is injected dynamically.

These mistakes account for the vast majority of schema that fails to produce any visible benefit in search.

1. Missing required properties. Google's rich result types each have mandatory fields. Product schema without name and offers will never trigger a rich result. Always check the official requirements for each type.
2. Fake or misleading data. Adding aggregateRating data that doesn't appear visibly on the page violates Google's guidelines and can trigger a manual action. Your schema must reflect what users see.
3. Wrong @type value. Schema.org types are case-sensitive. "@type": "faqpage" fails silently; it must be "FAQPage".
4. Broken JSON syntax. A single missing comma or unclosed brace makes the entire block unparseable. Use a JSON linter before pasting into your CMS.
5. Marking up off-screen or hidden content. If the information exists only in your schema and not in the visible page content, Google considers it spammy. Schema must describe content that real users can see.
6. Stale prices or availability. Product schema with an out-of-date price or OutOfStock status showing as InStock can get your rich results revoked. Automate schema generation from your product database rather than hard-coding it.

Don't try to add every schema type at once. Prioritize by impact relative to implementation effort:

• Start with FAQ schema on any page that already has a questions-and-answers section. It is the fastest win — add one JSON-LD block, see the accordion in results within days of Googlebot recrawling.
• Add Article schema to every blog post or guide. Takes under two minutes per page with a template. It doesn't always produce visible enhancements, but it consistently improves how Google categorizes your content.
• Implement Product schema only if you have genuine user reviews aggregated on the page. Without aggregateRating, Product schema rarely adds visible value beyond what Google already infers.
• Use LocalBusiness schema if you have a physical location or service area. Pair it with a fully filled-out Google Business Profile for maximum Knowledge Panel visibility.

The UtilityApp schema markup generator handles the JSON-LD syntax for all four types automatically — you fill in the fields, it produces valid, copy-paste-ready code that passes the Rich Results Test.