What is Schema Markup?

Schema markup is structured code added to a web page that helps search engines understand what the content represents. It does not change how the page looks to visitors. It works in the background, giving search engines additional context about the page's subject, structure, and purpose.

When a search engine reads a web page, it analyses the text to infer what the page is about. Schema markup removes that guesswork. Instead of inferring that a page contains an article, a recipe, or a local business, the search engine can read the schema and know with certainty what type of content it is dealing with.

This guide explains what schema markup is, how it works, the main types relevant to small business websites, and how to start implementing it.

How Schema Markup Works

Schema markup is written in a format called JSON-LD (JavaScript Object Notation for Linked Data). This is a block of structured code placed in the HTML of a page, inside a script tag. It is not visible to readers - only to search engines and other automated tools that crawl the page.

The code uses a standardised vocabulary developed by Schema.org, a collaborative project founded by Google, Microsoft, Yahoo, and Yandex. This shared vocabulary means that when a page uses Article schema, every major search engine understands it the same way.

A basic piece of Article schema looks like this:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "What is Schema Markup?",
  "author": {
    "@type": "Person",
    "name": "Cas"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Cobalt Digital Media"
  }
}
</script>

The @type field tells the search engine what kind of content this is. The other fields provide details - the headline, author, publisher, and so on. Search engines read these fields and use them to build a more accurate understanding of the page.

What Schema Markup Does for Your Website

Schema markup helps search engines understand and categorise your content more precisely. This has two practical effects.

The first is improved interpretation. Search engines are very good at understanding web content, but schema removes ambiguity. A page about a local business could be a review, a directory listing, or the business's own website. Schema specifies which it is, so the search engine does not have to guess.

The second is eligibility for rich results. Rich results are enhanced listings in Google search - star ratings, FAQ dropdowns, how-to steps, event dates, and similar features that appear directly in search results. To be eligible for a rich result, a page typically needs the corresponding schema markup. Without it, the page can still rank, but the enhanced visual presentation in search results is not available.

Schema markup does not directly improve rankings. A page with schema does not automatically rank higher than a page without it. What schema can do is improve how your content is interpreted and how it appears in search features - which can affect click-through rates.

Schema Markup and AI Search

AI search engines use schema markup as one of the signals they use to understand and categorise content. A page with clear schema markup is easier for an AI system to interpret correctly.

For AI-generated answers - such as Google AI Overviews or Perplexity responses - schema helps the system identify what kind of content a page contains and whether it is relevant to a query. FAQ schema, in particular, makes question-and-answer content more accessible to AI extraction because it explicitly labels each question and its answer.

This is one reason schema has become more important in recent years, even though it does not directly affect traditional ranking signals. For more on how AI search systems evaluate content, read How to Optimise Your Website for AI Search.

The Main Types of Schema for Small Business Websites

There are hundreds of schema types, but most small business websites only need a handful.

Article

Article schema is used for blog posts, news articles, and editorial content. It tells search engines the page contains a written article with a headline, author, and publication date. This is the most common schema type for content-focused websites.

For a step-by-step guide to writing and adding it, read How to Add Article Schema to a Blog Post.

FAQPage

FAQPage schema is used for pages or sections containing question-and-answer content. It explicitly marks each question and its answer, making this content easier for search engines to extract and display. FAQ schema can make individual questions and answers eligible to appear as expandable results in Google search.

For a step-by-step guide, read How to Add FAQ Schema to Your Pages.

HowTo

HowTo schema is used for step-by-step guide content. It marks each step individually, which makes the content eligible to appear as a structured how-to result in Google search. It is appropriate for any page that walks a reader through a process from start to finish.

For a step-by-step guide, read How to Add HowTo Schema to Step-by-Step Guides.

LocalBusiness

LocalBusiness schema is used by businesses with a physical location or a defined service area. It specifies the business name, address, phone number, opening hours, and geographic coordinates. This schema type is particularly useful for local search visibility - it helps search engines connect the business to location-based queries.

Organization

Organization schema describes the business itself - its name, website, logo, and contact information. It is typically added to the homepage or About page. It helps search engines build an accurate understanding of who publishes the site and what the business does.

Product

Product schema is used for individual product pages. It can include the product name, description, price, availability, and reviews. For e-commerce sites, this schema type is essential for appearing in Google Shopping results.

Where Schema Markup Goes on Your Website

Schema markup is placed in the HTML of the page it describes. It does not appear in the visible content - it sits in the code.

On most platforms, there are two ways to add it.

Page-level code injection. The schema block is added directly to the individual page or post. On Ghost, this is done through the post code injection field in the footer section. This is the recommended approach for article-specific schema like Article, FAQPage, and HowTo, because the schema details - headline, URL, image - are specific to each post.

Site-wide injection. Organization and LocalBusiness schema, which describe the business rather than individual pages, are often added once at the site level so they appear across all pages.

On Ghost, schema should always go in the footer code injection field, not the header.

How to Validate Schema Markup

After adding schema to a page, use Google's Rich Results Test to check whether it is valid. The tool reads the page URL and reports whether the schema is correctly formatted, what type of schema it detected, and any errors or warnings.

A schema block with errors may not be read correctly by search engines, even if the code looks right. Always validate before considering the implementation complete.

For a full walkthrough of the validation process, read How to Test Schema Markup with Google's Rich Results Test.

How to Start with Schema Markup

For a small business website publishing articles, the practical starting point is Article schema.

Add Article schema to every post you publish. It is the baseline and the most universally applicable schema type for content sites. Once Article schema is in place, add FAQPage schema to any article that has a FAQ section - which, if you are following a content cluster approach, should be most of them.

For step-by-step guides, how-to articles, and tutorial content, add HowTo schema.

If you have a physical business location, add LocalBusiness schema to your homepage or contact page.

Start with one type, implement it consistently across your content, validate it, and then move to the next type. Implementing schema one type at a time is more reliable than attempting several types at once.

Common Mistakes

Using the wrong schema type. A page with FAQ content should use FAQPage schema, not Article schema alone. Using the correct type for the content is essential - mismatched schema does not help search engines and may trigger validation warnings.

Adding schema to the header instead of the footer. On Ghost, schema goes in the post code injection footer. Adding it to the header can cause conflicts with other code on the page.

Incorrect JSON formatting. JSON-LD must be formatted precisely. A missing comma, mismatched bracket, or unclosed quote will cause the entire block to fail validation. Always run the schema through Google's Rich Results Test after adding it.

Only adding schema to the homepage. Schema is most useful on individual article and service pages, where the content details - headline, author, image, steps, FAQs - are specific and meaningful. A homepage with only Organization schema misses the opportunity to add article-level and content-type schema across the site.

Adding schema and never validating it. Schema that contains errors is not read correctly. A one-time validation check after adding schema is the minimum. Check it again any time the page is significantly updated.

Frequently Asked Questions

Does schema markup directly improve my Google rankings? No. Schema markup does not directly affect where a page ranks in search results. What it does is help search engines understand your content more precisely and makes your pages eligible for rich results - enhanced search listings that can improve how your content appears and how often people click on it.

Do I need a developer to add schema markup? Not usually. On Ghost, schema is added through the post code injection field using a block of JSON-LD code. The main requirement is that the code is correctly formatted and valid. Google's Rich Results Test checks this for you.

What is the difference between schema markup and meta tags? Meta tags - such as the meta title and meta description - provide basic information about a page for search engines and browsers. Schema markup provides detailed structured data about the content type, specific entities, and relationships on the page. Both are useful; they serve different purposes.

Which schema type should I start with? Article schema is the most practical starting point for a content-focused website. It applies to every blog post and article you publish. Once that is in place, add FAQPage schema to articles with FAQ sections, and HowTo schema to step-by-step guides.

Can a page have more than one type of schema? Yes. A page can have multiple schema blocks. An article page might have Article schema for the post itself and FAQPage schema for the FAQ section. Each schema block is a separate JSON-LD script tag. Run the page through Google's Rich Results Test to confirm all blocks validate correctly.

Summary

Schema markup is structured code added to a web page that helps search engines understand what the content represents - whether it is an article, a FAQ, a how-to guide, a local business, or another content type.

It does not change how the page looks to visitors. It works in the background, reducing ambiguity for search engines and AI-powered tools.

Schema does not directly improve rankings, but it can improve how content appears in search features such as rich results and AI-generated answers.

The main schema types for small business websites are Article, FAQPage, HowTo, LocalBusiness, and Organization.

On Ghost, schema goes in the post code injection footer. Always validate schema using Google's Rich Results Test after adding it.

Start with Article schema across all posts, then add FAQPage and HowTo schema where relevant.