Schema Markup That Actually Matters for a Business Website

Most business sites need five schema types, not fifty: Organization, LocalBusiness, Service, Article and BreadcrumbList, plus Product if you sell and FAQPage where you genuinely answer questions. Everything else is optional. Implemented accurately in JSON-LD, those types tell search engines and AI systems what your pages are and who publishes them.

Schema markup is a vocabulary for labelling content so machines do not have to infer. The vocabulary is enormous. The useful subset is small, and the common failure is not missing markup but inaccurate markup that contradicts the visible page.

What does schema markup actually do?

It converts implicit information into explicit statements. A human reads "Call us on +971 52 961 4900" and understands it is a phone number for a business. A parser needs to be told.

That matters in two places. Search engines use structured data to decide whether a page qualifies for a rich result and to build their understanding of your entity. AI answer engines use it to resolve ambiguity when deciding what a page is about and whether to trust it. Neither effect is a ranking lever. Both affect how you appear.

Which schema types are worth the effort?

Seven types cover almost every business website. The table below sets out where each belongs.

Type	Where it goes	What it establishes
Organization	Homepage, once sitewide	Who publishes the site
LocalBusiness	Contact or location page	Physical presence and hours
Service	Each service page	What you sell and to whom
Article	Each blog or insight post	Author, date, publisher
BreadcrumbList	Every page below the root	Site hierarchy
Product	Each product page	Item, price, availability
FAQPage	Pages with real question sets	Question and answer pairs

Anything beyond this list should earn its place. Event, Course, JobPosting and Recipe are excellent when they describe real things you publish. They are a liability when invented to chase a rich result.

Organization

One instance, on the homepage, describing the publishing entity. Keep it factual and keep sameAs pointing only at profiles you control.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Old Port Solutions LLC",
  "url": "https://oldport.ae",
  "email": "info@oldport.ae",
  "telephone": "+971529614900",
  "foundingDate": "2021",
  "sameAs": ["https://oldportindia.com"]
}

LocalBusiness

Use this where a customer could physically find you. It inherits from Organization, so do not duplicate both on the same page with conflicting values.

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Old Port Solutions LLC",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Cloud Spaces, Dubai Mall Fountain Views, Level M",
    "addressLocality": "Downtown Dubai",
    "addressCountry": "AE"
  },
  "telephone": "+971529614900",
  "url": "https://oldport.ae/contact/"
}

Service

One per service page, naming the provider and the area served. This is the type most sites skip and the one that most clearly states what you do.

{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Performance Marketing",
  "serviceType": "Paid media management",
  "provider": {
    "@type": "Organization",
    "name": "Old Port Solutions LLC"
  },
  "areaServed": { "@type": "Country", "name": "United Arab Emirates" },
  "url": "https://oldport.ae/services/performance-marketing/"
}

Article

Every insight post should carry it. The fields that matter are headline, datePublished, author and publisher. AI systems lean on author and date when deciding whether a passage is current and attributable.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Schema Markup That Actually Matters in 2026",
  "datePublished": "2026-11-07",
  "author": { "@type": "Organization", "name": "Old Port Solutions" },
  "publisher": {
    "@type": "Organization",
    "name": "Old Port Solutions LLC",
    "url": "https://oldport.ae"
  },
  "mainEntityOfPage": "https://oldport.ae/insights/schema-markup-that-actually-matters/"
}

BreadcrumbList

Cheap to generate from your URL structure and genuinely useful. It gives engines your hierarchy without them having to reverse engineer your navigation.

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Insights",
      "item": "https://oldport.ae/insights/" },
    { "@type": "ListItem", "position": 2, "name": "Schema Markup" }
  ]
}

Leave item off the final entry. The current page does not need to link to itself.

Product

Required if you sell. Price, currency and availability must match the page. Our e-commerce and trading work covers custom-built PCs and IT hardware, where specification accuracy in markup matters as much as in the listing copy. If you sell on Amazon, noon or Carrefour as well as your own site, keep the attributes consistent across all of them, which is a core part of marketplace consulting.

FAQPage

Google has narrowed FAQ rich results to a small set of authoritative sites, so most businesses should no longer expect the visual snippet. Keep the markup anyway: it labels question and answer pairs cleanly for AI comprehension. Check the current Google structured data documentation before making any promise about what a rich result will look like.

What breaks schema in practice?

Five mistakes account for most broken implementations.

1. Markup that contradicts the page. Schema stating opening hours the page does not show is a policy violation and a trust problem.
2. Duplicate conflicting entities. Two Organization blocks with different phone numbers, usually one from a theme and one from an SEO plugin.
3. Invented reviews and ratings. Self-serving aggregateRating on your own organisation is the fastest way to lose eligibility for anything.
4. Stale dates. dateModified updating on every cache rebuild teaches engines to ignore your dates.
5. Markup injected after load. If structured data only exists after client-side JavaScript runs, treat its discovery as unreliable and render it server-side.

How do you implement and validate it?

Follow a short sequence rather than bolting markup on page by page.

1. Map your page types. Most sites have six or seven templates, not hundreds of pages.
2. Assign one schema type per template and write the markup once in the template.
3. Populate fields from real data sources, never hardcoded strings that drift.
4. Validate with the Schema.org validator and Google's Rich Results Test.
5. Re-validate after any theme or plugin update, because both can inject competing blocks.
6. Re-check quarterly, since vocabulary support and Google's eligibility rules change.

This is template work, not content work. It belongs in the build. We handle it as part of web design and development rather than as a later retrofit, and it pairs directly with the entity clarity work described in our insights on generative engine optimisation. Our sister company oldportindia.com applies the same template-level approach on India-based builds.

Frequently asked questions

Which schema types should every business website have?

Organization on the homepage, LocalBusiness on the contact or location page, Service on each service page, Article on each blog post, and BreadcrumbList sitewide. Product schema applies if you sell, and FAQPage where you genuinely answer questions. Five types cover most sites properly.

Does schema markup improve rankings?

Schema is not a direct ranking factor. It helps search engines and AI systems interpret a page correctly, which can earn rich results, improve how your entity is understood, and increase click-through. The benefit is comprehension and presentation rather than a rank boost.

Should I use JSON-LD or microdata?

Use JSON-LD. Google recommends it, it sits in a single script tag kept separate from your HTML markup, and it survives template changes that would quietly break inline microdata. Microdata still parses correctly, but maintaining it across a redesign is needlessly fragile and hard to validate.

If your structured data was added by three different plugins over four years, it is probably contradicting itself. We can audit it and rebuild it at template level. Call +971 52 961 4900, email info@oldport.ae, or use the contact page.