Schema Markup: The SEO Trick Hiding in Your HTML

There is a line of code you can add to your website that tells Google exactly what your page contains — and Google sometimes rewards you with enhanced search results for it. It is called schema markup, and most small business websites do not have it.

Schema markup does not directly change your rankings. What it does is help you stand out in search results with rich snippets: star ratings, FAQ dropdowns, recipe details, event times, and more. These enhanced listings take up more space on the page and tend to get more clicks than plain blue links.

Here is what schema markup is, which types matter for your business, and how to add it without touching code.

What Is Schema Markup?
What Rich Results Look Like
Schema Types That Matter for Small Businesses
How to Add Schema to Your Website
How to Test Your Schema
Common Schema Mistakes
Frequently Asked Questions

What Is Schema Markup?

Schema markup is structured data — a standardized format for describing your page content in a way search engines can parse.

It uses a vocabulary defined at schema.org, which was created collaboratively by Google, Bing, Yahoo, and Yandex.

Think of it this way: your page content is written for humans. Schema markup is the same information translated for machines. A human reads "Open Monday to Friday, 9am to 5pm." Schema markup tells Google those exact hours in a format it can use to display them in search results.

You add schema markup to your page's HTML as a JSON-LD script block. It sits in the page source but is invisible to visitors. Search engines read it, and if the data matches what is on the page, they may display rich results.

What Rich Results Look Like

Rich results are the enhanced search listings you see in Google. Here are examples relevant to small businesses:

FAQ rich results: Question-and-answer content from your page displayed in search results. Google previously showed these as expandable dropdowns for all sites, but as of 2023 restricts that format to select authoritative sources. Adding FAQ schema still helps search engines understand your content structure and may surface answers in AI-generated search features.

Local business results: Business hours, address, phone number, and star ratings displayed alongside your listing in the knowledge panel or local pack.

Review stars: Star ratings shown below your page title in search results. This requires actual reviews marked up with schema.

Breadcrumb navigation: Instead of showing the raw URL, Google shows a clean breadcrumb trail like "Home > Services > Web Design," making it easier for searchers to understand your site structure.

How-to results: Step-by-step instructions that can appear as expandable sections in search results. Useful for service businesses that publish guides.

Not every schema type produces rich results. Google supports specific types and has requirements for each. Adding schema does not guarantee rich results — Google decides whether to display them based on the page quality and the specific search.

Schema Types That Matter for Small Businesses

You do not need to learn all of schema.org. For most small businesses, a handful of types cover everything useful:

LocalBusiness

Best for: Any business with a physical location or service area.

What it includes: Business name, address, phone number, hours, geo coordinates, price range, and the type of business.

Why it matters: Helps Google display your business information accurately in search results and Google Maps. This complements your Google Business Profile data.

FAQPage

Best for: Any page with a frequently asked questions section.

What it includes: Question-and-answer pairs structured for search engines to parse.

Why it matters: FAQ schema helps search engines understand your Q&A content and may surface answers in AI-powered search features and featured snippets. Google previously displayed FAQ schema as expandable dropdowns for all sites, but as of 2023 limits that format to select authoritative sources. Adding FAQ schema is still worthwhile for content comprehension and emerging search formats. Every blog post with an FAQ section (like this one) can have FAQ schema.

HowTo

Best for: Service businesses that publish step-by-step guides.

What it includes: Step names, descriptions, estimated time, and tools needed.

Why it matters: How-to rich results can appear as expandable steps in search results, giving searchers a preview of your content before clicking.

Article / BlogPosting

Best for: Blog posts and news articles.

What it includes: Headline, author, date published, date modified, image, and description.

Why it matters: Helps Google understand your content structure and may improve how your articles appear in search results and Google Discover.

Product

Best for: E-commerce sites and product pages.

What it includes: Product name, price, availability, reviews, and images.

Why it matters: Product schema can trigger rich results showing price and availability directly in search listings.

How to Add Schema to Your Website

You have three options, from easiest to most technical:

Option 1: Website Platform Plugins (Easiest)

WordPress: Plugins like Yoast SEO, Rank Math, or Schema Pro can generate schema markup automatically. Yoast adds Article and Breadcrumb schema by default. Rank Math includes LocalBusiness and FAQ schema generators.

Squarespace: Adds basic schema automatically for business info and blog posts. For FAQ schema, you may need to add JSON-LD manually through the code injection feature.

Shopify: Adds Product schema automatically. For other types, apps like JSON-LD for SEO or Schema Plus can help.

Option 2: Google's Structured Data Markup Helper

Google provides a free tool where you tag elements on your page and it generates the JSON-LD code for you. Visit Google's Structured Data Markup Helper, select the data type, paste your URL, and highlight the relevant content on the page. It outputs JSON-LD that you paste into your page source.

Option 3: Write JSON-LD Manually

For developers or anyone comfortable with code, JSON-LD is straightforward. Here is a minimal LocalBusiness example:

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Bob's Plumbing",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St",
    "addressLocality": "Denver",
    "addressRegion": "CO",
    "postalCode": "80202"
  },
  "telephone": "+1-303-555-0100",
  "openingHours": "Mo-Fr 09:00-17:00"
}

Add this inside a <script type="application/ld+json"> tag in your page's <head> section.

How to Test Your Schema

After adding schema, verify it works:

Google's Rich Results Test — Go to search.google.com/test/rich-results, enter your URL, and see which rich results your page is eligible for. This is the definitive test because it shows what Google can actually parse.

Schema Markup Validator — Go to validator.schema.org to check your JSON-LD for syntax errors. This catches formatting issues but does not tell you whether Google will use the data.

Google Search Console — In GSC, go to Enhancements. If Google has detected schema on your pages, you will see reports for each type (FAQ, Product, etc.) with any errors or warnings.

For a broader look at how your pages perform in search, including title tags, indexing status, and keyword rankings, the page audit feature in Brass-SEO covers the full picture alongside your GSC data.

Common Schema Mistakes

Four errors account for nearly all schema-related penalties and wasted effort.

Marking up content that is not on the page. Schema must describe content that is visible to users. Adding FAQ schema for questions that do not appear on the page violates Google's guidelines and can result in a manual action.

Using schema to mislead. Marking a regular page as a Product, adding fake review stars, or misrepresenting your business type will get your schema ignored or penalized.

Not testing after changes. Schema syntax is strict. A missing comma or bracket can invalidate the entire block. Always run the Rich Results Test after making changes.

Ignoring errors in Search Console. If GSC shows schema errors under Enhancements, fix them. Google will not display rich results for pages with errors.

For more on the technical SEO fundamentals that complement schema markup, including site structure and crawlability, see our AI prompts for technical SEO audits.

For Webflow-specific schema setup via Custom Code injection, see Webflow SEO: Launch to First 1,000 Visitors.

Frequently Asked Questions

Does schema markup improve rankings directly?

No. Google has stated that schema markup is not a direct ranking factor. What it does is enable rich results, which can increase your click-through rate. Higher CTR can indirectly help rankings over time because it signals to Google that searchers find your listing relevant. Think of schema as improving your search listing's appearance, not its position.

Which schema type should I add first?

If you have a physical business location, start with LocalBusiness schema. If your pages have FAQ sections, add FAQPage schema next — it has the most visible impact in search results. After that, add Article or BlogPosting schema to your blog content. Prioritize the types that match your existing content.

How long before rich results appear after adding schema?

It depends on how quickly Google re-crawls your pages. For frequently updated sites, it can happen within days. For sites that Google crawls less often, it may take weeks. You can use the URL Inspection tool in GSC to request re-crawling of specific pages. Even after crawling, Google does not guarantee it will display rich results — it depends on the page quality and the search context.

Can schema markup hurt my site?

Only if it violates Google's guidelines — for example, marking up content that is not on the page, using fake reviews, or misrepresenting your business. Correct, honest schema markup carries no risk. If Google cannot use your schema, it simply ignores it. It will not hurt your rankings.

Do I need schema on every page?

No. Focus on your most important pages: homepage (LocalBusiness), key service pages, and pages with FAQ sections. Blog posts benefit from Article schema, but many platforms add this automatically. You do not need schema on utility pages like your privacy policy or contact page.