Add schema that describes what is visibly on the page: one accurate business identity (Organization, or LocalBusiness if you have a real premises), one Service block per service page, and supporting markup such as BreadcrumbList. Remove everything copied from another business, every rating for reviews not on the page, and any type added only because a plugin offered it. Structured data labels your content; it does not guarantee rich results, rankings or citations.
The short answer: the schema a service business actually needs (table)
Work page by page. A small, accurate set beats a long, borrowed one.
| Page | Add | Skip |
|---|---|---|
| Homepage | Organization, or LocalBusiness with the correct subtype if customers visit a real premises | Ratings for reviews that appear nowhere on the page |
| Each service page | Service, tied to the business entity, describing only that service | A copied block naming services the page does not cover |
| Location or service-area pages | The same business entity, with areas served as stated on the page | An invented street address for an area you only travel to |
| Blog articles | Article basics: headline, dates, author | Product or offer markup on editorial content |
| Every page | BreadcrumbList matching the visible navigation path | Types chosen for a rich result the page cannot qualify for |
Fix in this order: identity first, services second, supporting markup last.
The problem: copied templates and invented ratings do the opposite of helping
The most common schema on service-business websites was never written for that business. A plugin generates a default block, a developer pastes a template from a previous project, or an owner copies a tutorial example and changes only the name — leaving a wrong address, services the firm no longer offers, or opening hours from another time zone.
Invented ratings are worse than untidy. Google's guidelines require markup to describe content visible on the page, and fake reviews break its spam policies. The consequence is a structured-data manual action, which removes rich-result eligibility for the affected pages: a five-star display bought with invented markup can cost the business every legitimate enhancement it had.
Start with identity: Organization vs LocalBusiness (and the right subtype)
Every service business needs exactly one clear identity, and the choice depends on whether customers can visit you.
Use LocalBusiness when the business has a real, verifiable premises customers visit — a clinic, salon, showroom or office. Choose the most specific subtype that fits and include only details that appear on the page and are true today: name, address, telephone and opening hours.
Use Organization when there is no public premises to describe — the common UAE service-area pattern, where a team travels to customers across Dubai, Sharjah or Abu Dhabi from a base nobody visits. Organization states the company's name, website, logo and contact routes without pretending a service area is a street address. Never invent an address to qualify for LocalBusiness markup: a fabricated address contradicts the visible page and misleads customers.
Keep the name consistent everywhere. If the site trades in English and Arabic, use the same business name in the markup as on the page and your profiles; conflicting names, numbers or addresses weaken the single, unambiguous entity identity schema exists to provide.
Service schema: one block per service page, tied to the business entity
Service is a schema.org type, not a stand-alone Google rich-result feature, so its job is clarity rather than display. Add one Service block per service page, describing that page's service only: its name, a description matching the visible text, the provider (your business entity, linked to the identity block above), and the area served where the page states it.
Resist listing every service on every page. A page about one treatment, trade or engagement should mark up that service only. This discipline makes the markup a true representation of the page — the service-business equivalent of the product-side approach in our guide to schema for ecommerce product pages.
The supporting set: BreadcrumbList, Article and WebPage basics
Three lighter types support the identity and service blocks. BreadcrumbList describes the navigation path to the page — Home, Services, the service name — and should mirror the hierarchy visitors can actually follow.
Article basics belong on blog content: headline, dates, and the author as a Person or Organization. They clarify editorial content; they do not certify expertise, and they earn nothing on a service page.
The discipline is subtraction: if a type does not describe something the page visibly contains, remove it rather than completing its fields with plausible inventions. Our SEO services in the UAE work treats schema as one part of technical hygiene, alongside the checks in our technical SEO guide for 2026.
Reviews and ratings: only real, visible, first-party reviews — never invented
Review and AggregateRating markup follows the strictest rule in this guide: mark up only reviews genuinely about your business, collected by your business, and visible on the page itself. If a visitor cannot read the review there, it does not belong in the markup.
That excludes the common shortcuts: copying a rating from a third-party profile as though the reviews lived on your site, averaging testimonials you selected, inventing a review count, or letting a plugin generate a rating from nothing. Google's guidelines name fake reviews explicitly as misleading content.
If you publish real reviews on a page, the markup must match them exactly — same rating, same count, same reviews — and change when they change.
FAQ schema: what Google actually allows now (and why it is not a ranking tactic)
FAQ content is useful for visitors. FAQ rich results are no longer a tactic at all. Google restricted them in August 2023 to well-known, authoritative government and health websites, and has since stopped displaying them in Search altogether, retiring the feature's documentation. A service business adding FAQPage markup today is not queueing for an expandable listing; that display no longer exists to win.
Keep good questions and answers on the page as visible content that helps a person decide. Remove any FAQ block that exists only in the markup — marking up invisible content violates the same rule as invented reviews. Anyone selling FAQ schema as a ranking or AI-citation shortcut is selling a retired feature.
What to avoid: the markup patterns that trigger manual actions
Remove these patterns on sight: markup for content not visible on the page; fake or borrowed reviews and ratings; an invented address, or a service area dressed up as one; copied blocks naming another business or services you no longer offer; irrelevant types added for a rich result the page cannot qualify for, such as Product markup on a service page; and conflicting duplicates giving different names, numbers or hours for the same business.
Each fails the same test — the markup must be a true, current representation of the page. Deceptive structured data can draw a manual action and the loss of rich-result eligibility.
Validate before and after launch: Rich Results Test, schema.org validator, Search Console
Validation has two layers. Google's Rich Results Test shows whether a page is eligible for the rich-result features Google currently supports and flags missing required properties. The schema.org validator checks the wider vocabulary — including Service, which has no Google rich result of its own — for syntax and structure errors.
Run both before launch on a template of each page type, not just the homepage, because plugins generate different blocks per template. After launch, watch Search Console's enhancement and Manual Actions reports, and retest whenever business facts change — stale schema fails the visible-content test as surely as invented schema. Our technical SEO audit service in Dubai guide explains where schema checks sit inside a full audit.
Common mistakes
The most common mistake is pasting a template and editing only the business name, leaving another firm's address, services and hours in place. Close behind: adding AggregateRating for reviews that live on a third-party profile — or nowhere — and inventing a street address so a service-area business can use LocalBusiness.
Other frequent errors: marking up all services on every page, keeping FAQ blocks that appear only in code, and validating the homepage while service-page templates stay broken. Finally, treating schema as a rankings lever at all: it describes; it does not promote.
FAQ
Does adding schema guarantee rich results or higher rankings?
No. Accurate schema makes a page eligible for the rich-result features Google currently supports and helps search engines interpret the page, but Google decides whether to display anything, and schema alone does not guarantee a rich result, a knowledge panel or a higher ranking.
Should a service-area business invent an address to use LocalBusiness?
No. Never fabricate an address. If customers cannot visit a real premises, use Organization for the business identity and Service blocks that state the areas you serve, exactly as the page describes them. An invented address contradicts the visible content and misleads customers.
Can I mark up the star rating shown on my Google or review-platform profile?
No. Only mark up reviews that your business collected and that visitors can read on the page itself. Copying a third-party profile's rating into your markup, or inventing a rating or review count, is the fake-review pattern Google's guidelines prohibit and can lead to a manual action.
Is FAQ schema still worth adding to win a bigger search listing?
No. Google restricted FAQ rich results in 2023 and has since stopped displaying them in Search, so FAQ markup is not a ranking tactic and wins no extra listing. Keep genuine questions and answers as visible page content for visitors, and remove any FAQ block that exists only in the code.
Which tools should I use to check my schema?
Use Google's Rich Results Test for the features Google supports, the schema.org validator for the wider vocabulary such as Service, and Search Console after launch for enhancement and manual-action reports. Test a template of every page type, and retest whenever your address, phone number, hours or services change.
Get your existing schema checked (CTA)
If your site grew by template and plugin, its schema probably describes a business that is not quite yours. Our technical SEO audit checks every template's structured data against the visible page, removes the patterns that risk a manual action, and rebuilds the identity and service blocks your pages need. Tell us your website address and main services, and we will come back with an itemised proposal within 24 business hours.
