Schema markup that actually helps a service business

A service business gets real value from a short list of schema types: Organization or LocalBusiness for who you are, Service for what you offer, Article with a named author for your writing, and BreadcrumbList for your site structure. Add them as JSON-LD, keep every fact in the markup visible on the page, and ignore the long tail of types that promise rich results you will not get.

What is schema markup, in plain words?

Schema markup is a label for facts on your page. A human sees "Example Studio, Pune, open Monday to Saturday" and understands it. A crawler sees text. Markup says: this is an organisation, this is its name, this is its address, these are its opening hours.

The vocabulary is schema.org. The format Google recommends is JSON-LD, a block of code in the page that does not change how it looks. It helps search engines and AI systems read your facts with less guessing, which supports both search results and answers from assistants.

What does schema not do?

Be realistic.

• It is not a ranking switch. Google says structured data helps it understand content and can make pages eligible for rich results, which is different from a ranking boost.
• It does not rescue weak content.
• Many types no longer produce visible features. Google restricted FAQ rich results to well-known government and health sites in August 2023 and stopped showing HowTo rich results.
• It must match the page. Google's guidelines say markup should describe content that users can see. Marking up invisible or false information risks a manual action.

Which schema types help a service business?

Organization or LocalBusiness: the base. Name, logo, URL, contact details, social profiles. If you serve customers at a location, use the more specific type such as ProfessionalService or another subtype of LocalBusiness, with address, opening hours and service area. This supports your Google Business Profile and your knowledge panel.

WebSite: names the site and its publisher. Simple and useful on the homepage.

Service: describes each offering, with its name, description, provider and area. It is not tied to a Google rich result. It does give machines a tidy description of what you sell.

Article (or BlogPosting) with a Person author: for guides and posts. Headline, dates, author with a link to an author page, publisher. It supports eligibility for article features and ties your writing to real people.

BreadcrumbList: shows the page's place in the site. Google can display the trail in results, which helps people see where a page sits.

FAQPage: this one is optional. It is harmless when questions and answers appear on the page, and it still gives machines question-and-answer pairs. Do not expect rich results.

Review and AggregateRating: handle with care. Google does not show review stars for a business marking up reviews about itself on its own site. Use only for genuine, visible reviews and expect little from it.

What does a working example look like?

This is a simplified block for a service business. Replace the placeholders with your own details, and keep them identical to what the page shows.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfessionalService",
  "name": "Example Studio",
  "url": "https://www.example.com/",
  "logo": "https://www.example.com/logo.png",
  "telephone": "+91 00000 00000",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Street address",
    "addressLocality": "Pune",
    "addressRegion": "Maharashtra",
    "postalCode": "000000",
    "addressCountry": "IN"
  },
  "areaServed": "Pune",
  "sameAs": [
    "https://www.linkedin.com/company/example"
  ]
}
</script>

On a service page, add a Service block that names the offering and points to the organisation as its provider. On each article, add an Article block with the headline, publication date, modified date and the author as a Person.

How do you roll it out?

1. Homepage: Organization or LocalBusiness plus WebSite.
2. Service pages: Service, with BreadcrumbList.
3. Articles: Article with author, with BreadcrumbList.
4. Contact or location pages: the same LocalBusiness facts, matching the page.
5. Test each template with the Rich Results Test and the Schema Markup Validator.
6. Check Search Console. The Enhancements reports show errors and warnings for the types Google supports.
7. Re-test after redesigns. A template change can remove markup silently.

If your site runs on WordPress, an SEO plugin may add some of this. Check what it outputs, because defaults can be generic or wrong, and avoid two plugins adding duplicate blocks. On a custom build, generate the markup from the same data that renders the page so they cannot drift apart.

What are the common mistakes?

• Markup that contradicts the page, such as an old phone number or address.
• Marking up everything with every type, hoping for an edge.
• Adding Review markup with stars that customers cannot see.
• Leaving copy-pasted example values in place.
• Ignoring errors in Search Console because the page "looks fine".
• Duplicate Organization blocks from a theme, a plugin and a manual snippet.

What are the trade-offs?

Markup needs upkeep. When your address, hours or services change, the markup must change too. Generate it from your data where possible.

The payoff is modest and indirect. It is cheap insurance for clarity, particularly for local search and AI answers, and it will not transform traffic on its own. Put it after the basics: crawlable pages, fast loading and clear content. A technical SEO audit shows if those are in place.

Where does TechSum fit?

We design the schema for each template, generate it from your content so it stays accurate, and test it in Search Console. It is part of Search and Answer Visibility, alongside the technical SEO audit and AEO and GEO. The free health check includes a structured data check for your public pages.