On-page schema markup is structured data added to individual pages so search engines can read exactly what each page represents: a service, an article, a product, a person or your business itself. It does not replace good content, but it removes guesswork, and that clarity supports richer search listings and better understanding by AI assistants.
This guide is practical. Rather than listing every rich result Google offers, it walks through which schema types suit which page on a typical business website, how to implement JSON-LD in WordPress, and how to keep markup accurate over time. It is part of how we approach SEO for clients in Dubai and Abu Dhabi, and it overlaps closely with technical SEO.
What schema markup does on a page
Schema.org is a shared vocabulary supported by the major search engines. When you add it to a page, you describe the content in a structured format: this is an Article, written by this Person, published on this date, by this Organization. Search engines already try to infer this from the visible page. Structured data confirms it.
Three practical benefits follow:
- Clearer understanding: Entities such as your business name, address, services and authors are explicitly connected.
- Eligibility for enhanced results: Some types, such as Product, Review snippets, Breadcrumb and Event, can qualify pages for richer listings when Google chooses to show them.
- Consistency across the web: Linking your Organization markup to official profiles helps search engines connect your website with your wider presence.
Structured data is not a direct ranking boost, and Google never guarantees a rich result. Treat it as a way to communicate precisely, not as a shortcut.
Choosing schema by page type
The most common mistake is adding the same generic markup to every page. Each template on your site deserves the type that matches its main content.
| Page type | Main schema type | Useful supporting types |
|---|---|---|
| Home page | Organization or LocalBusiness | WebSite |
| Service page | Service | BreadcrumbList, provider Organization |
| Blog post | Article or BlogPosting | Person author, BreadcrumbList |
| Product page | Product with Offer | AggregateRating if reviews are genuine |
| Team or author page | Person or ProfilePage | Organization as employer |
| Event page | Event | Place, Offer |
| Contact page | ContactPage | LocalBusiness details |
Home and about pages
Your Organization markup should include your legal or trading name, logo, website, contact details and sameAs links to official profiles such as LinkedIn and Instagram. If you serve customers from a physical office, a LocalBusiness subtype may fit better; for multi-branch local detail, handle each location on its own page.
Service pages
Service markup can describe the service name, a short description, the area served and the provider. Keep it aligned with the visible copy. If the page says you serve Dubai and Abu Dhabi, the markup should say the same.
Articles and blog posts
Include the headline, author as a Person with a link to their profile page, publisher, date published, date modified and main image. Accurate author information supports the experience and expertise signals that matter for advice content.
Product pages
Product markup should match the price, currency (AED for local stores), availability and condition shown on the page. Only add ratings that come from real customer reviews displayed on that page.
Why JSON-LD is the right format
Schema can be written as JSON-LD, Microdata or RDFa. Google recommends JSON-LD where possible, and we use it almost exclusively. It sits in a script block separate from your visible HTML, so designers can change layouts without breaking markup, and developers can generate it from the same data that fills the page.
A single JSON-LD block can also describe several connected items using identifiers, for example a BlogPosting whose author is a Person who works for your Organization. That connected graph is clearer than several unrelated snippets.
Implementing on-page schema markup in WordPress
WordPress offers several routes. The right one depends on how custom your content is.
- Start with your SEO plugin. Yoast SEO and similar plugins output a structured graph for Organization, WebSite, WebPage, Article and Breadcrumb by default. Configure the organization name, logo and social profiles in settings first.
- Set the right content type per post type. Most SEO plugins let you choose a default schema type for pages and posts. Set blog posts to Article and adjust page types where the plugin allows.
- Add custom types through the theme or a small plugin. For Service, Event or detailed Product data, generate JSON-LD from custom fields so the markup always matches what is on screen.
- Avoid duplicate output. Themes, page builders, WooCommerce and review plugins can each add their own markup. Check the page source and disable overlapping sources.
- Handle bilingual sites properly. On Arabic pages, the markup should describe the Arabic content, with the language set correctly and names in the language shown on the page.
Hand-coded snippets: use with care
Pasting static JSON-LD into a page builder block works for one-off pages, but it drifts out of date when prices, hours or service details change. Prefer markup generated from your content wherever the information is likely to change.
Testing and maintaining your markup
Structured data is not a one-time task. Content changes, plugins update and Google adjusts which features it supports.
| Tool | What it checks | When to use |
|---|---|---|
| Rich Results Test | Eligibility for Google features on a URL | After building or editing a template |
| Schema Markup Validator | General schema.org validity | For types Google does not feature |
| Search Console enhancements | Errors and warnings across the site | Monthly review |
| View page source | Duplicate or conflicting blocks | After plugin or theme updates |
Mistakes that cause problems
- Marking up invisible content: Structured data should describe what users can see. Hidden reviews or prices can lead to a manual action.
- Self-serving reviews: Review markup about your own business on your own site is not eligible for review stars in Google.
- Chasing retired features: Google has reduced or removed some rich results, including FAQ and HowTo for most sites. The markup may still describe content, but do not plan around those listings.
- Mismatched details: Phone numbers, addresses or prices in markup that differ from the page confuse search engines.
- Copying markup between pages: Every page needs markup describing its own content.
Frequently asked questions
Does on-page schema markup improve rankings directly?
Not directly. Google has said structured data is not a general ranking factor. It helps search engines understand your pages and can make them eligible for enhanced listings, which may improve click-through. The indirect benefits come from clarity and better presentation, while rankings still depend on content quality, relevance and authority.
Which schema types should a small service business start with?
Start with Organization or LocalBusiness on the home page, Breadcrumb markup across the site, Article on blog posts, and Service on your main service pages. Most SEO plugins cover the first three. Service markup usually needs a small custom addition, ideally generated from page fields so it stays accurate.
Is it worth adding FAQ schema now?
Google now shows FAQ rich results mainly for well-known government and health websites, so most businesses will not see them. FAQ content on the page is still useful for readers and for AI assistants. Adding the markup is harmless if it matches the visible questions, but do not expect a visual change in results.
Can schema markup be added without a developer?
For the basics, yes. A properly configured SEO plugin handles Organization, WebSite, Article and Breadcrumb markup. For custom types such as Service, Event or detailed product data, developer help is worthwhile, because generated markup stays in sync with your content and avoids duplicates.
Clear signals, better understanding
Well-implemented on-page schema markup gives search engines and AI assistants a precise description of every page, from your home page to each article and service. Built into templates and checked regularly, it supports richer listings and protects your visibility as search features change.
If you would like your current markup reviewed, the Bdazzil team can audit what your site outputs today and recommend a clean structure for each page type.