Technical SEO / Structured data
Google does not read your page the way a customer does. It reads the labels you put on it, and most Malaysian sites label nothing.
Schema markup fixes that: code telling a search engine what a page is, who published it, and what it sells or explains. It is also the most misunderstood item in the technical toolkit, sold routinely as a ranking service. For the commercial side, see our SEO services in Malaysia.
The short answer
Schema markup is structured data, usually written as JSON-LD, that labels what a page is so search engines and AI assistants can read it reliably. It makes a page eligible for richer results and easier to quote. It is not a ranking factor, and Google retired the FAQ rich result on 7 May 2026.
Three tiers cover almost every site: one node for who you are, one for what each page is, one for the blocks you want quoted. The work is deciding which, not writing code.
What experience teaches us
Schema markup does not move rankings. Anyone selling it as a ranking service is selling the wrong thing.
What it moves is interpretation, which is worth more than it used to be. Most Malaysian sites we audit have schema installed by a plugin, never checked, emitting two contradicting versions of one node. Writing JSON-LD takes minutes. Deciding which nodes you need is the job.
On this page
01 / What it does
What is schema markup, and what does it actually do?
Schema markup is structured data, written as JSON-LD, that labels the facts on a page: what it is about, who published it, what it costs. It changes what a search result or an AI assistant may say about you, not where you rank.
The page a visitor sees and the page a machine sees are different documents. A person reads a company name in a logo and a price beside a photo. A crawler reads a div. Schema restates those facts in a schema.org vocabulary Google, Bing and the language models all parse.
It sits on top of our technical SEO guide for Malaysian sites, and is wasted effort before crawling and indexing work.
02 / Three tiers
Which schema types does a website actually need?
Three tiers, no more. One node for who you are, one for what each page is, one for the blocks you want quoted. Anything beyond adds maintenance without eligibility.
We build every site to the same three-tier schema system, held together by one injection layer with the SEO plugin's schema output off. Duplicate, disagreeing nodes are the most common fault we find. Open each tier below.
Tier 1
Site identity
Organization, once per site: name, url, logo and sameAs on your real profiles. A business with premises adds LocalBusiness. This is what lets an assistant treat your brand and your Petaling Jaya office as one entity.
Tier 2
Page meaning
Service on a service page, BlogPosting on an article, Product with a nested Offer on a product page. BreadcrumbList goes everywhere, because it puts your category path in the result instead of a raw URL.
Tier 3
Content extraction
The blocks you want lifted verbatim. FAQPage for a real question section, Review only where reviews are visible on that page. This tier earns no badge in 2026. It earns quotation in AI answers.
03 / Writing it
How is schema markup written and installed?
As JSON-LD, in a script tag in the page source, injected from one place. Google prefers JSON-LD over the older formats, and every node should come from a single layer so nothing is emitted twice.
JSON-LD sits apart from the visible HTML, which is why it is the format to use. Microdata and RDFa interleave with your HTML, so every template change puts them at risk.
On WordPress there are three routes. An SEO plugin emits a default set, fast and opaque. A schema plugin gives you fields to fill, fine for a few pages and unmaintainable across a catalogue. Or you inject it from a snippets layer with the plugin's schema off, the only route where you can say exactly what the site emits. Pick one.
04 / Field by field
What does Google require, field by field?
Required means the page is not eligible without the field. Recommended means Google uses it if you supply it and serves a thinner result if you do not. One rule sits above both: markup must match what a visitor can see.
Tap any node for its usual mistake.
Tap for the mistake
name, url and logo, plus sameAs on your real profiles. Without it nothing connects your site to the accounts people review you on.
A real address and telephone matching your Google Business Profile. A serviced office you do not occupy is a guidelines problem.
A position, name and URL per item, matching the breadcrumb a visitor sees. It does for crawlers what internal linking for SEO does for humans.
headline matches the H1, an author as a Person beats a bare string, and dateModified must reflect a real edit.
serviceType, areaServed and provider. areaServed is where you say Malaysia or Klang Valley honestly, because coverage you cannot deliver costs conversions.
A Question with an acceptedAnswer per entry, and the answer must match the visible text word for word.
Only where real reviews are visible on that page. Marking up ratings a visitor cannot see is a guidelines breach.
Marked-up content must be visible. A mismatch is a standing finding in any on-page SEO audit, and it costs eligibility rather than earning it.
05 / Product pages
What do product pages need on top?
Three more properties and one decision. A Product node needs name, image and offers to be eligible for any product result, and you must know whether the page is a merchant listing or a product snippet.
Google's merchant listing documentation lists three required properties on a Product: name, image and offers. The name is the product as a shopper would say it, not your page title with the brand appended. The offers block is where most product schema breaks.
Inside the Offer, Google's examples carry price, priceCurrency, availability and priceValidUntil. For a Malaysian store priceCurrency is MYR. Two rules are not negotiable: the marked-up price must match the page, and availability must track real stock.
| Question | Product snippet | Merchant listing |
|---|---|---|
| Who it fits | Pages the product cannot be bought on: a catalogue, a spec page, an editorial review | Pages where a shopper can buy the product from you |
| What it can show | Price, availability and reviews, with room for editorial detail such as pros and cons | Fuller detail, including shipping and returns |
| Offer needed | Yes, with price and currency | Yes, and you must be the seller |
| Shipping and returns | Not part of the experience | Recommended, and shown in the result |
| Typical Malaysian case | An industrial catalogue, or a brand taking enquiries on WhatsApp | A WooCommerce or Shopify store with checkout |
Summarised from Google's product structured data documentation, linked above.
A brand taking orders over WhatsApp has no on-page checkout, so it sits in snippet territory. Marking it as a merchant listing means waiting for a treatment that never arrives.
Your result type
Tick what applies to the page you have in mind
Nothing is assumed until you tick a box.
Product schema deepens quickly beyond this: variants, regional return policies, feed fields that must agree with page fields. That belongs in a guide of its own. If the store is the constraint, see our ecommerce web design work.
06 / What Google retired
What has Google retired, and what still matters?
The FAQ rich result, on 7 May 2026, with its documentation removed on 15 June 2026. Keep the FAQPage markup and drop the expectation of a badge. The Structured Data Testing Tool is long gone too.
FAQ schema was sold for years on the result space it bought. A proposal pricing it as a route to a richer listing is pricing a retired feature. Both changes sit in Google's Search Central changelog.
We never built question blocks for the badge. A question and answer section with a matching FAQPage node is still the cheapest way to get a precise answer quoted by an assistant, and the marked-up text must stay identical to the visible text.
One local note. Do not paste a customer's name, email or order number into review markup. Personal data in your page source is still personal data under the PDPA.
07 / Testing
How do you test schema markup now the old tool is gone?
The Structured Data Testing Tool is retired. Use Google's Rich Results Test for eligibility, the Schema Markup Validator at schema.org for syntax, and Search Console's enhancement reports for what Google reads sitewide.
They answer different questions, which is how a site ends up with a green validator result and nothing in search. Google moved the old tool to schema.org and kept the Rich Results Test as the eligibility check, as it documented on its blog. Tap each tool for its blind spot.
Tap for the blind spot
Checks whether your JSON-LD is well formed and uses real schema.org types. It passes markup Google cannot use, so green here is necessary and not sufficient.
Tells you whether Google considers one URL eligible for a specific result. The check that matters before launch, one page at a time.
The enhancement reports show what Google read sitewide, catching four hundred pages broken by a theme update rather than one.
Then watch what happens. Richer results change click-through first, so measure impressions against clicks after launch. Our guide to analysing engagement and traffic covers that side.
08 / Cost and ownership
What does schema markup cost in Malaysia?
On a new build with us, nothing extra. Organisation, Service and page schema are included on every WDD plan. On an existing site the cost is the engineering time to wire markup to live data, a developer job.
Price the context, not the markup. A Malaysian online store runs RM8,000 to RM40,000 or more to build, most serious ones between RM12,000 and RM40,000. Schema is a line inside that, measured in hours.
Ownership gets skipped. Markup typed by hand decays the moment a price changes, so it must be generated from the data the page renders from. Most Klang Valley sites we audit run on WordPress, where that is one template filter. Keeping it accurate is maintenance work, sitting with whoever runs your website maintenance services in Malaysia.
09 / Self-audit
Is your schema markup actually working?
Run these nine checks on your homepage, a content page, and a product page if you sell online. Seven or more and the markup works. Four to six and you are eligible for less than you could be. Three or fewer, and it is decoration.
Your reading
Tick the checks your site passes
Nothing is assumed until you tick a box.
A self-assessment, not a technical audit.
Where to go next
Parent guide
Technical SEO for Malaysian websites
Crawling, indexing and site health, which structured data needs.
Build
Ecommerce website design and build
Catalogue, checkout and product data, so the markup has something true to say.
Services
Professional SEO services for Malaysian businesses
Technical health, entity authority and AI visibility, one programme.
Next step
Want this scoped against your actual site?
Tell us the site and what it sells, and we will quote the schema work against what is already emitting rather than against a generic package.
10 / Straight answers
Frequently asked questions
Schema markup is structured data, usually written as JSON-LD, that labels what a page is so search engines and AI assistants can read it reliably. It names what the page describes, who published it, and facts such as an address or a price. It changes what a result may display, not your rank.
No, not directly. Schema markup is not a ranking factor. It makes a page eligible for richer result types and far easier for AI assistants to quote accurately. The indirect gain is real, because a result showing a price or a rating earns more clicks, but selling it as a ranking service is wrong.
Three tiers cover almost every site. An Organization node for identity, with LocalBusiness if you have premises. A node on each page saying what it is, usually Service, BlogPosting or Product, plus BreadcrumbList everywhere. Then FAQPage or Review on the blocks you want quoted.
No. Google stopped showing the FAQ rich result in Search on 7 May 2026 and removed its documentation on 15 June 2026. FAQPage markup is still worth keeping, because a question and answer block with matching structured data is easy for an AI assistant to quote. Do not budget for a badge.
For a handful of pages, yes. An SEO or schema plugin produces usable markup with little setup. Across a catalogue it becomes a developer job, because the markup has to be generated from the same data the page renders from. Hand-typed markup goes stale the first time a price changes.
Use three tools, because they answer different questions. The Schema Markup Validator at schema.org checks whether your code is well formed. Google's Rich Results Test checks whether one page is eligible for a result. Search Console's enhancement reports show what Google read across the whole site.
