Schema Markup for Small Business: The Types That Actually Influence Rankings
Schema markup sits in a strange position in the SEO world. It is not technically a direct ranking factor - Google has confirmed this repeatedly. But it enables rich results that dramatically increase click-through rates, and higher CTR leads to more traffic, which does influence how Google evaluates your pages over time. For small businesses competing against larger companies, schema is one of the most underused advantages available.
This guide covers what schema actually is, how rich results work, the six schema types worth implementing, how to add them without a developer, and the mistakes that prevent schema from showing up in search results.
What Schema Markup Actually Is
Schema markup is structured data - code you add to your website that tells search engines what your content means, not just what it says. It uses a standardised vocabulary defined at Schema.org, a collaborative project created by Google, Microsoft, Yahoo, and Yandex.
Without schema, Google has to infer what your page is about from its text and context. With schema, you explicitly label the information: "this is a business named X, located at Y, with opening hours of Z". Or: "this FAQ question has this answer". Google can then use that explicitly labelled information to build rich results in search.
Schema markup is typically implemented using JSON-LD (JavaScript Object Notation for Linked Data), a format Google officially recommends. It sits in a <script> tag in your page's HTML and is invisible to users but readable by search engines.
Here is a simple example of what LocalBusiness JSON-LD looks like:
That block of code, placed in your homepage's <head>, tells Google with certainty who you are, where you are, and how to contact you.
How Rich Results Work
Rich results are enhanced search listings that display additional information beyond the standard title, URL, and meta description. They are generated from structured data on your page and appear directly in Google's search results.
Examples of rich results include:
- Star ratings under a business listing or product page (from Review/AggregateRating schema)
- FAQ dropdowns that expand answers directly in the search result (from FAQPage schema)
- Breadcrumb trail showing your site structure (from BreadcrumbList schema)
- Local business information including hours, phone number, and address (from LocalBusiness schema)
- Article author and date shown under news or blog results (from Article schema)
These rich results increase the visual footprint of your listing in search results and consistently produce higher click-through rates than plain listings. A result with review stars and FAQ dropdowns takes up significantly more space on the page and provides additional reasons to click.
The critical point: Google does not guarantee rich results even when your schema is valid. Schema is a candidate. Google reviews whether your page meets its quality thresholds and then decides whether to display the rich result. Thin content pages with schema rarely earn rich results.
The 6 Schema Types Every Small Business Should Implement
1. LocalBusiness
Best for: Any business with a physical location or defined service area.
What it enables: Accurate business information in knowledge panels and local results.
Implementation: Add to your homepage and contact page. Include name, address, phone, URL, opening hours, geo-coordinates, and business type. The more fields you populate, the more information Google has to work with.
Important detail: The @type should be as specific as possible. Instead of the generic "LocalBusiness", use "Plumber", "AccountingService", "LegalService", "MedicalBusiness" - whatever the Schema.org vocabulary offers for your industry.
2. FAQPage
Best for: Service pages, about pages, pricing pages, or any page that answers common customer questions.
What it enables: FAQ dropdowns in search results that appear below your listing. Each question-answer pair can appear expanded in search, dramatically increasing your search result's visual size.
Implementation: The schema must match content that is actually visible on the page. You cannot have schema for a question that does not appear in the page's visible text. Mark up three to six of your most commonly asked questions.
Caution: Google has become more selective about when it shows FAQ rich results. They are most reliably shown for navigational queries to your brand, and for service pages targeting specific question-based keywords.
3. Article
Best for: Blog posts, news articles, how-to guides.
What it enables: Appears in Google's Top Stories carousel (for news publishers), and adds author and date information to your search result. Signals to Google that this is editorial content with a human author.
Implementation: Add to every blog post. Include headline, author (with name and optionally a URL to an author bio), datePublished, dateModified, and image. The author field is particularly important given Google's E-E-A-T focus on demonstrating real authorship.
4. BreadcrumbList
Best for: All websites with more than one level of navigation.
What it enables: Breadcrumb trail displayed under your URL in search results - for example, "Home > Blog > SEO Tips > This Post Title". This helps users immediately understand where the page sits in your site structure.
Implementation: This is often handled automatically by SEO plugins on WordPress. If implementing manually, each level of the hierarchy needs a ListItem with a name and item URL.
5. Review and AggregateRating
Best for: Any business that collects customer reviews, displayed on your site.
What it enables: Star ratings shown directly in search results.
Critical rule: You can only use Review or AggregateRating schema for reviews that are genuinely displayed on your page. You cannot add schema for reviews that exist only in your Google Business Profile or a third-party platform - that constitutes misrepresentation and can result in a manual action. The reviews must be readable on the page itself.
Implementation: If you display reviews on your website (even a few testimonials with names), mark them up with Review schema. If you aggregate them into a summary rating, use AggregateRating with the ratingValue, ratingCount, and bestRating fields.
6. Service
Best for: Businesses that offer specific services (agencies, consultancies, professional services, home services).
What it enables: Better understanding of your service offering, which can influence how Google matches your pages to relevant queries.
Implementation: Add to each service-specific page. Include name, description, provider (linked to your LocalBusiness entity), and areaServed for location-based services. You can also include pricing information if your pricing is public.
How to Implement Schema Without a Developer
Option 1: Google's Structured Data Markup Helper
Go to search.google.com/structured-data/helper. This free tool lets you paste a URL or HTML, select the schema type you want to add, and highlight elements on the page to map them to schema properties. It generates the JSON-LD code for you. You then copy it and paste it into your page's <head> tag.
This works well for one-off implementations but becomes tedious at scale.
Option 2: WordPress Plugins
If your site runs on WordPress, several plugins handle schema automatically:
- Yoast SEO (paid) generates Article, BreadcrumbList, and Website schema automatically for posts and pages, and includes a Schema tab for more granular control.
- Rank Math (free tier available) is more comprehensive in its schema offerings and includes LocalBusiness, FAQPage, and Service schema configurators in the interface.
- Schema Pro is a dedicated schema plugin for businesses that need multiple schema types across different page templates.
Most users of these plugins can configure all six schema types listed above without writing a single line of code.
Option 3: Manual JSON-LD Script Tag
For developers or technically confident users, the most flexible approach is adding JSON-LD directly to your page templates. In most CMS platforms, you can add a custom script to the <head> section of your site-wide template or individual page templates.
This approach gives full control over every property and allows you to implement entity-linked schema (connecting your LocalBusiness schema to your Article schema via the publisher property, for example).
Testing Your Schema With Google's Rich Results Test
Before assuming your schema is working, test it:
- Go to search.google.com/test/rich-results
- Enter your page URL or paste your page's HTML
- Click "Test URL"
- Review the results
The tool shows which schema types were detected, whether they are valid, and whether they are eligible for rich results. It also flags specific errors and warnings.
Common warnings to fix:
- Missing recommended fields (not errors, but adding them increases your chances of rich result eligibility)
author.namemissing (critical for Article schema under E-E-A-T)imageproperty missing (required for most rich result types)
Common errors to fix:
ratingValueis not within the valid range specified bybestRatingandworstRatingdatePublishedis not in the correct ISO 8601 format (should be "2026-08-07", not "August 7, 2026")- Missing required property for the specific schema type
After fixing errors, request re-indexing via the URL Inspection tool in Google Search Console and re-test after a few days.
The Most Common Schema Implementation Errors
These are the mistakes that prevent schema from being recognised or result in manual actions:
1. Schema that does not match page content Your FAQ schema lists questions that are not visible on the page. Your Review schema references ratings not shown to users. Google considers this deceptive and it can result in a manual action.
2. Markup on the wrong page Adding LocalBusiness schema to every page of your site (including blog posts) is unnecessary and can confuse Google's entity understanding. Put LocalBusiness on your homepage and contact page.
3. Incorrect date formats Dates must be in ISO 8601 format: YYYY-MM-DD or YYYY-MM-DDThh:mm:ssZ. "January 2026" or "01/07/26" will cause errors.
4. Missing image dimensions Many rich results require an image. If your image URL does not include a crawlable, appropriately sized image, the rich result will be ineligible.
5. Nesting errors in JSON-LD JSON-LD must be valid JSON. A misplaced comma, unclosed bracket, or extra quotation mark breaks the entire block. Use a JSON validator (jsonlint.com) to check before publishing.
6. Using a deprecated schema type or property Schema.org evolves. Some property names and types from older implementations are deprecated. Always reference the current documentation at schema.org for the type you are implementing.
Connecting Schema to Your Broader SEO Strategy
Schema markup is one component of a well-structured SEO programme. It works alongside content quality, keyword targeting, page experience, and link building - not instead of them. A page with excellent schema but thin content will not earn rich results.
For the full picture on how schema connects to your local SEO, see our Local SEO Checklist 2026. For understanding how your structured data pages are performing, our Google Search Console Guide covers the Performance report and URL Inspection tool.
If you want schema implemented correctly across your entire site or want a technical SEO audit that includes structured data, our SEO Specialist can handle the implementation. Our SEO service includes structured data as part of a comprehensive technical optimisation. Get a free quote and we will review what is currently implemented on your site and what is missing.
Related articles
SEO for Small Businesses: The Practical Playbook
Search engine optimisation does not require a six-figure agency budget. Here is a clear, step-by-step framework that small business owners can use to drive consistent organic traffic.
SEO & MarketingSEO for SaaS in 2026: What Is Different and What Actually Works
SaaS SEO follows different rules than content site SEO. The keyword intent is different, the funnel is longer, and the content that ranks is not the content that converts. Here is the framework that works for SaaS products in 2026.