What schema markup actually is

Schema markup (also called structured data) is code you add to a web page that describes the content in a standard vocabulary search engines understand, defined at schema.org. Instead of leaving Google to infer what a page is about from the words alone, schema explicitly labels the parts: this is a local business with this name, address and phone; this is a product with this price and rating; these are frequently asked questions and their answers. The recommended format is JSON-LD, a small block of code (usually in the page head) that carries this information without changing how the page looks to visitors. Schema does not change your content, it annotates it, giving search engines and, increasingly, AI systems a clear, machine-readable description of what the page is and what entities it involves. That clarity is the whole point: the easier it is for a search engine to understand a page precisely, the better it can match it to the right searches and present it well.

Why schema markup matters (and what it does not do)

It is important to be accurate about what schema does. Schema is not a direct ranking factor, adding it does not, by itself, push you up the results. What it does is help search engines understand your content, and, crucially, make pages eligible for rich results: the enhanced listings Google can show, such as star ratings, FAQ dropdowns, business information panels, product prices and event details. These richer listings can make your result more prominent and clickable, which indirectly helps performance. Schema also supports the entity-based understanding that underpins modern search and AI answers: clear structured data helps search engines and AI systems recognise your business, products and content correctly. So the honest framing is that schema is a comprehension-and-presentation tool, not a ranking lever, valuable because it helps Google understand you and can unlock more prominent listings, but not a shortcut to rankings. Google has also been clear that structured data is not required for AI-generated search features, so treat schema as good SEO hygiene and a rich-result enabler, not a magic button.

The schema types that matter for SA businesses

You do not need dozens of schema types, just the ones that match your content. Organization or LocalBusiness is the foundation for any business site, describing your name, logo, address, phone and social profiles (essential for local businesses wanting to be understood by Google and appear well in local results). Service describes what you offer and the area you serve, useful on service pages. BreadcrumbList marks up your navigation path and can show a breadcrumb trail in results. FAQPage marks up genuine question-and-answer content and can produce FAQ rich results (and feed AI answers). Product and Review or AggregateRating matter for ecommerce and where you display genuine reviews (following Google's rules on self-serving reviews). Article or BlogPosting suits blog content, with author and dates. Event, Recipe and others apply to specific content. The rule is simple: add the types that genuinely describe what is on the page, and no more. Marking up content as something it is not breaches Google's guidelines and can cause problems.

How to add schema markup

The recommended way is JSON-LD, a small script block in the page's head, which keeps the structured data separate from the visible HTML and is easiest to manage. You have a few practical routes. If your site runs on a content platform like WordPress, an SEO plugin can generate common schema (Organization, Article, breadcrumbs, FAQ) automatically once configured, which is the simplest path for most businesses. If you have a developer or a custom site, they can add JSON-LD blocks directly to the relevant templates. And for one-off pages, schema-generator tools can produce the JSON-LD for you to paste in. Whichever route, three rules matter: the schema must accurately match the visible content on the page (do not mark up reviews or FAQs that are not actually shown); the values must be correct (right name, address, prices, dates); and each page should carry the schema types that fit it, your business details site-wide, Article on posts, FAQPage where you have real FAQs, and so on. Well-structured JSON-LD, matched to genuine content, is what search engines reward with understanding and, where eligible, rich results.

Testing your schema and common mistakes

Always test schema after adding it, because invalid or mismatched markup can be ignored or, worse, flagged. Two free tools do the job: Google's Rich Results Test checks whether a page is eligible for rich results and shows errors, and the Schema Markup Validator checks the structured data is valid. Google Search Console also reports structured-data issues across your site over time. The common mistakes to avoid are: marking up content that is not visible on the page (for example, FAQ schema for questions users cannot see); inaccurate values (wrong prices, addresses or ratings); self-serving review markup that breaches Google's policies; broken JSON (a stray comma or unescaped character invalidates the whole block); and over-marking, adding schema types that do not genuinely apply. Get the basics right, accurate schema that matches real content, validated with the testing tools, and you gain the comprehension and rich-result benefits without the risks. Schema is not complicated once you treat it as honest labelling of what is genuinely on the page.

Frequently asked questions