Schema Markup for Small Business Websites: A Step-by-Step Tutorial to Win Rich Results
This schema markup tutorial shows service businesses how to add LocalBusiness, Service and FAQ JSON-LD in WordPress and Next.js, then test it and win rich results.
This schema markup tutorial walks you through the exact structured data a service business needs, how to add it to WordPress and Next.js, and how to confirm Google actually reads it. Schema is code that labels your content so search engines and AI systems understand who you are, what you sell, where you operate and what customers say about you. It does not guarantee rankings, but it makes your pages eligible for richer search appearances and easier to cite in AI answers.
Most small business sites either have no schema or have broken schema generated by a plugin nobody checked. This guide fixes that in order: pick the right types, write clean JSON-LD, deploy it, test it, then monitor it.
What Schema Markup Is and Why Service Businesses Need It
Schema markup is a shared vocabulary from Schema.org that you add to a page as structured data. Google, Bing and AI search tools read it to confirm facts that would otherwise be inferred from messy page text. A phone number in a paragraph is just text. A phone number inside a LocalBusiness object is a verified attribute of a named entity.
For a service business, that matters in three ways. First, rich results such as review stars and FAQ-style enhancements can lift click-through rates on pages that already rank. Second, entity clarity helps Google connect your website, Google Business Profile and social accounts as one business. Third, AI engines favour sources they can parse cleanly, which ties directly into generative engine optimisation.
Be realistic about the limits. Schema is not a ranking factor on its own, and Google has restricted several rich result types in recent years. Treat it as infrastructure: cheap to add, valuable when done correctly, harmful only when it misrepresents your content.
JSON-LD vs Microdata: Choose the Right Format
Structured data comes in three syntaxes: JSON-LD, Microdata and RDFa. Google explicitly recommends JSON-LD schema, and so do we. It sits in a single script block, separate from your visible HTML, which makes it easy to edit, template and debug.
Microdata wraps attributes around individual HTML elements. That means every design change risks breaking your markup, and developers have to hunt through templates to update a single value. For a small business site that changes copy and layouts regularly, that is a maintenance burden you do not need.
| Format | Where it lives | Maintenance | Verdict |
|---|---|---|---|
| JSON-LD | One script tag in head or body | Easy | Use this |
| Microdata | Inline HTML attributes | Painful | Avoid |
| RDFa | Inline HTML attributes | Painful | Avoid |
Every example in this schema markup tutorial uses JSON-LD. A basic block looks like this: a <script type="application/ld+json"> tag containing a JSON object with @context set to https://schema.org and an @type naming what the page describes.
The 5 Schema Types That Matter for Service Businesses
You do not need dozens of types. Five cover almost every service business, and adding more rarely adds value. Prioritise accuracy over volume.
- Organization: Your legal or trading entity: name, logo, URL, social profiles. Goes on the homepage and ideally site-wide.
- LocalBusiness: Your location, hours, phone, service area and geo coordinates. Use a more specific subtype where one exists, such as Plumber, Attorney or Dentist.
- Service: One block per core offering, describing what it is, who provides it and where it is available.
- FAQPage: Questions and answers that are visible on the page. Useful for AI citation even where Google no longer shows the visual enhancement.
- Review and AggregateRating: Genuine customer feedback, used within strict Google guidelines.
Add BreadcrumbList as a sixth if your site has a clear hierarchy. It is quick to implement and produces cleaner URL display in search results.
Step 1: Map Schema Types to Your Pages
The most common mistake is pasting the same giant block on every page. Schema must describe the content of the page it sits on. Start by listing your key pages and assigning types.
- Homepage: Organization plus LocalBusiness (or WebSite if you are not location-based).
- Service pages: Service, with a provider reference back to your Organization, plus FAQPage if the page has a visible FAQ.
- Contact or location pages: LocalBusiness with full address, hours and phone.
- Blog posts: Article or BlogPosting, with author and publisher.
- Testimonial pages: Review markup only where reviews are genuinely about your business and visible to users.
Use the @id property to connect blocks into a graph. Give your Organization an @id such as https://yoursite.com/#organization, then reference it from your Service and Article blocks. This tells search engines that every page belongs to one entity instead of several unrelated ones.
Before writing any code, gather the facts once: legal name, address exactly as it appears on your Google Business Profile, phone in international format, opening hours, logo URL and social profile URLs. Consistency across these sources is what builds trust.
Work with Lucanix
Ready to get schema set up correctly the first time?
Lucanix builds and audits structured data for service businesses as part of every SEO and development project.
Step 2: Write LocalBusiness and Organization JSON-LD
Start with your core entity. The example below is a trimmed LocalBusiness block for a plumbing company. Swap in your real details and a specific subtype.
{ "@context": "https://schema.org", "@type": "Plumber", "@id": "https://example.com/#organization", "name": "Example Plumbing Co", "url": "https://example.com", "logo": "https://example.com/logo.png", "telephone": "+1-555-010-1234", "priceRange": "$$", "address": { "@type": "PostalAddress", "streetAddress": "123 Main Street", "addressLocality": "Austin", "addressRegion": "TX", "postalCode": "78701", "addressCountry": "US" }, "openingHoursSpecification": [{ "@type": "OpeningHoursSpecification", "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"], "opens": "08:00", "closes": "17:00" }], "sameAs": ["https://www.facebook.com/example", "https://www.linkedin.com/company/example"] }
Include areaServed if you travel to customers rather than hosting them. Add geo coordinates for brick-and-mortar locations. If you have several locations, create a separate LocalBusiness block on each location page, each with its own @id.
Skip properties you cannot fill honestly. An empty or invented field is worse than a missing one. Google’s local business structured data documentation lists exactly which properties are required and which are recommended. For the wider picture on location signals, see our local SEO strategy guide.
Step 3: Add Service and FAQPage Schema
Service schema describes each offering and ties it to your business. Put one block on each service page, with the provider property pointing to your Organization by @id.
{ "@context": "https://schema.org", "@type": "Service", "name": "Emergency Pipe Repair", "serviceType": "Plumbing", "description": "24-hour emergency pipe repair for homes and small offices.", "provider": { "@id": "https://example.com/#organization" }, "areaServed": { "@type": "City", "name": "Austin" } }
FAQPage schema works only when the questions and answers appear on the page for users to read. Mark up the same text, word for word. Google restricted FAQ rich results to a small set of authoritative sites in 2023, so do not expect the accordion in search results. The markup still helps machines understand your content, and AI engines frequently lift question-and-answer pairs when forming responses.
Each FAQ block follows the same pattern: a mainEntity array containing Question objects, each with an acceptedAnswer of type Answer and a text value. Keep answers concise, specific and free of promotional filler. Three to six questions per page is plenty.
Step 4: Handle Review Schema Without Getting Penalised
Review markup is where small businesses most often get into trouble. Google applies strict rules, and violations can trigger a manual action that removes rich results across your site.
The key rules, drawn from Google’s review snippet guidelines:
- No self-serving reviews: Review and AggregateRating markup for LocalBusiness or Organization on your own site is not eligible for star rich results.
- Reviews must be visible: Every rating in your markup must match content users can see on the page.
- Be genuine: Marked-up reviews must come from real customers, not copy written by you.
- Be specific: The rating must be about the item the page is about, such as a specific product or service.
In practice, that means review stars are realistic for product pages and some Service pages with third-party reviews, but not for slapping a 5.0 rating on your homepage. If a plugin does that automatically, turn it off.
Your best lever for stars in search is still your Google Business Profile, where reviews display natively. Use structured data for small business to reinforce identity, and earn reviews through your profile. Our guide to backlink building for small businesses covers the broader trust signals that sit alongside this.
Step 5: Implement JSON-LD in WordPress
WordPress gives you three practical routes. Choose based on how much control you need.
Option 1: An SEO plugin. Rank Math and Yoast both generate Organization, WebSite, Article and BreadcrumbList schema automatically. Rank Math adds a built-in schema generator for Service, LocalBusiness and FAQ. If you are choosing between them, our Rank Math vs Yoast comparison covers the schema features in detail. This is the best route for most small businesses.
Option 2: Custom JSON-LD in a code snippet. For full control, output your own blocks using a function in your child theme or a snippets plugin:
- Create a function that builds an array of your schema data.
- Encode it with
wp_json_encode(). - Hook it to
wp_headand print inside ascript type="application/ld+json"tag. - Use conditional tags such as
is_front_page()andis_singular('service')to load the right block on the right page.
Option 3: A dedicated schema plugin. Tools like Schema Pro offer per-page controls without code, though they can duplicate output if your SEO plugin already generates the same types.
The critical warning: never run two systems that output the same type. Duplicate or conflicting Organization blocks confuse parsers. Pick one source of truth for each type and disable the rest. If you are on a custom build, our custom WordPress development guide explains why templated sites often produce messy markup.
Step 6: Implement JSON-LD in Next.js
Next.js makes schema straightforward because you control the rendered HTML. In the App Router, build the schema object in a server component and render it as a script tag. Because it renders on the server, crawlers see it without executing JavaScript.
- Create a helper that returns your schema object, such as a
getLocalBusinessSchema()function. - In your page or layout component, render
<script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify(schema) }} />. - Escape the output by replacing
<with\u003cin the stringified JSON to prevent injection through user-supplied fields. - For dynamic routes, pass page data into the helper so each service or post gets its own accurate block.
Keep your schema in a shared lib/schema.ts file so the Organization data lives in one place and every page references the same @id. Add TypeScript types from the schema-dts package to catch invalid properties at build time rather than in Search Console weeks later.
The Next.js JSON-LD guide documents the recommended pattern. If you are weighing platforms, our Next.js vs WordPress comparison covers how each handles technical SEO like this.
Step 7: Test, Validate and Monitor Your Schema
Deploying schema without testing is how broken markup stays live for months. Use two tools for two different jobs.
The Rich Results Test at search.google.com/test/rich-results tells you whether a page is eligible for Google rich results and flags errors and warnings. The Schema Markup Validator at validator.schema.org checks general Schema.org syntax, including types Google does not display.
Run this checklist after every deployment:
- Test the live URL, not a staging copy.
- Fix every error. Treat warnings as optional unless they flag a recommended property you can fill honestly.
- Confirm the data matches visible page content.
- Check for duplicate blocks of the same type.
For ongoing monitoring, open the Enhancements section of Google Search Console. It reports valid items, items with warnings and errors by schema type, and sends email alerts when new problems appear. Check it monthly, and always after a redesign or plugin update. Add schema checks to your technical SEO audit so regressions get caught early, and tie results back to business outcomes using our SEO ROI framework.
Work with Lucanix
Lucanix handles technical SEO for service businesses.
From schema and Core Web Vitals to full site builds, we fix the technical layer so your content can rank.
Common Schema Mistakes That Cost You Rich Results
After auditing dozens of small business sites, the same errors appear repeatedly. Avoiding them puts you ahead of most competitors.
- Marking up invisible content. Schema must reflect what users see. Hidden FAQs or fake ratings violate Google’s guidelines.
- Inconsistent NAP data. Your name, address and phone in schema must match your Google Business Profile exactly, including abbreviations.
- Stale information. Old opening hours or discontinued services in schema signal an unmaintained site.
- Plugin conflicts. Two plugins outputting separate Organization blocks create contradictory data.
- Wrong type selection. Using a generic LocalBusiness when a specific subtype exists wastes precision.
- Copy-paste errors. Leaving placeholder text, example domains or another business’s details in the template.
Maintenance is the quiet failure point. Schema breaks when themes change, plugins update or content is rewritten. A structured website maintenance plan should include a schema check, because nobody notices broken markup until traffic or rich results drop.
What to Expect: Realistic Results From Schema Markup
Set honest expectations. Schema will not lift a page from position 30 to position 3. It improves how your already-ranking pages appear and how clearly machines understand them.
Realistic outcomes within two to three months of correct implementation: cleaner breadcrumb display, eligibility for review snippets where guidelines allow, stronger entity recognition connecting your site and Business Profile, and a better chance of being cited in AI-generated answers. Some businesses see click-through rate gains on pages that gain enhanced listings, but results vary by industry and query.
Measure it properly. In Search Console, compare click-through rate for the same pages before and after deployment, and track impressions for branded queries. Annotate the deployment date in your analytics so you can attribute changes. Schema is one layer of a broader AI search optimisation approach, and it performs best when paired with strong content and fast pages.
If you would rather not wire this together yourself, Lucanix includes structured data in our WordPress and Next.js builds, which typically range from $1,500 to $10,000 depending on scope. We also run SEO retainers that cover ongoing validation and monitoring.
Frequently Asked Questions
What is the best schema type for a local service business?
Use LocalBusiness, ideally with a specific subtype such as Plumber, Electrician or Attorney, on your homepage and location pages. Pair it with Organization for brand details and Service schema on each offering page. This combination covers identity, location and what you sell.
Does schema markup improve Google rankings?
Not directly. Google states structured data is not a ranking factor on its own. It makes pages eligible for rich results, clarifies your entity and helps AI systems parse your content, which can lift click-through rate and visibility indirectly.
Is JSON-LD better than Microdata?
Yes for almost every small business. Google recommends JSON-LD because it lives in one script block, separate from your HTML. That makes it far easier to update, template and debug than Microdata or RDFa, which are tangled into page markup.
How do I test if my schema markup is working?
Run the live URL through Google’s Rich Results Test for rich result eligibility and the Schema Markup Validator for general syntax. Then monitor the Enhancements reports in Google Search Console, which flag errors and warnings across your whole site over time.
Can I add schema to WordPress without coding?
Yes. Rank Math and Yoast generate Organization, Article and BreadcrumbList schema automatically, and Rank Math includes a visual generator for Service, LocalBusiness and FAQ types. Just avoid running two plugins that output the same schema type.
Why is my FAQ schema not showing in search results?
Google limited FAQ rich results to a small group of authoritative government and health sites in 2023, so most businesses will not see the accordion display. The markup is still valid and useful for helping search and AI systems understand your question-and-answer content.
Work with Lucanix
Want schema that actually earns rich results?
Book a free consultation and Lucanix will review your structured data, or request a fixed-price proposal for a full technical SEO and development package.

