Structured Data Guide Singapore: Schema Markup Made Simple

Quick answer: This structured data guide Singapore businesses can use starts with one idea: schema markup is hidden code that labels what your page content means. Search engines read those labels to show richer results such as ratings, prices, opening hours and FAQs, which lifts click-through rather than rankings directly.

Two Singapore clinics rank in positions three and four for the same treatment search. One listing shows a star rating, a price range and three expandable questions. The other shows a blue link and two lines of text. Position four gets the click. Nothing about rankings explains that outcome, and nothing about content quality does either. The difference is structured data, a layer of code that sits invisibly on the page and tells search engines exactly what each piece of content represents. It is one of the few areas of technical SEO where the benefit is visible to the naked eye within weeks, and it is also one of the most consistently neglected by Singapore SMEs. This guide covers what schema markup is, which types are worth your time, how to implement it on real platforms, how to test it, and the mistakes that get rich results revoked. Regulated sectors get the most from it and carry the most risk, which is why our medical SEO work treats schema as a compliance question as much as a technical one.

What Structured Data Actually Is

A web page is written for humans. A heading looks like a heading because it is big and bold, and you understand that the number under it is a price because of where it sits and the dollar sign in front of it. A search engine has to infer all of that, and inference is unreliable.

Structured data removes the guesswork. It is a block of code, invisible to visitors, that states plainly: this is a product, its name is X, its price is 180 SGD, it is in stock, and 47 people rated it an average of 4.6. You are not changing what the page says. You are labelling what it means.

The vocabulary used for these labels is called Schema.org, a shared standard maintained collaboratively by Google, Microsoft, Yahoo and Yandex. The format Google recommends is JSON-LD, which stands for JavaScript Object Notation for Linked Data. In practice that means a self-contained script block in the page head, separate from your visible content, which is exactly why it is safe to add: it cannot break your layout.

Two older formats exist, Microdata and RDFa, which weave the labels into your visible HTML. Both still work and neither is worth choosing today for a new implementation, because they are fiddly to maintain and any layout change risks breaking the markup.

The critical thing to understand about what you get in return: structured data is not a ranking factor in the direct sense. Adding schema does not push you up the results page. What it does is make you eligible for enhanced result formats, and those enhanced formats change how many people click. The gain is real, it is measurable in Search Console, and it arrives through click-through rate rather than position.

Which Schema Types Are Worth Your Time

There are hundreds of Schema.org types. Fewer than a dozen matter for a typical Singapore SME. This table covers the ones that earn a visible result in Google today.

Start with two. Every Singapore business with premises should have LocalBusiness markup, and every site should have Organization markup. Those two take an afternoon and underpin everything else. LocalBusiness should carry your full address in Singapore format including the postal code, your operating hours including public holiday variations if they differ, your phone number in international format, and your geographic coordinates.

After that, choose by business model. A retailer adds Product. A professional firm adds Service and FAQPage. A school adds Event and Course. A publisher adds Article. Do not add types that do not describe your page. Marking a service page up as a Product because product results look nicer is the fastest way to lose eligibility entirely. Firms in regulated sectors should be particularly careful here, something we cover in our law firm SEO engagements where claims in markup carry professional obligations.

The Singapore-Specific Details That Get Missed

Generic schema tutorials are written for American or British sites, and following them produces markup that is technically valid and locally wrong.

Address format. Singapore addresses do not map neatly onto the international address fields. The building name and unit number belong in the street address line, the region field is generally best left out rather than filled with a district guess, the postal code is the six-digit code, and the country code is SG. We regularly find local sites with a state or province field populated with something invented to satisfy a form.

Phone numbers. Use the international format with the country code, not a bare eight-digit local number. A local number without the country code is ambiguous to any system reading it outside Singapore.

Currency. The currency code must be SGD. Leaving it as the default in a plugin or theme, which is very often a foreign currency, means your price markup advertises the wrong amount to anyone comparing. On e-commerce catalogues this is the single most common schema fault we find in local audits.

Opening hours. Specify them properly rather than as a text blob. Many Singapore businesses have different hours on Sundays and public holidays, and there is a dedicated field for special hours that almost nobody uses. Retail and food outlets in malls with different mall opening times are a classic mismatch case.

Coordinates. Latitude and longitude add precision that matters in a dense urban environment where three businesses can share a postal code across different unit numbers in the same tower.

Language. If you publish bilingual pages, mark each version in its own language and do not duplicate the English markup onto the Chinese page. Search engines use the markup language to decide which searcher sees what. For food and beverage businesses where hours, location and menu data all appear in results, the accuracy of these fields directly shapes footfall, as our cafe results work sets out.

How to Add Structured Data Without a Developer

The method depends on your platform, and on most of them you will not touch code at all.

WordPress. The mainstream SEO plugins generate Organization, LocalBusiness, Article and Breadcrumb markup automatically once you complete their setup wizard, and offer a schema selector on individual pages for types such as FAQPage and Service. The setup wizard is the part people skip, and skipping it means the plugin outputs incomplete markup with placeholder values. Fill it in properly, including the logo, the address and the social profiles.

Shopify. Themes include Product and Breadcrumb markup by default. Quality varies considerably by theme, and older themes often omit availability or currency. Review app data is frequently a separate implementation, so you can end up with two conflicting AggregateRating blocks on one page, which Google may reject outright.

Wix and Squarespace. Both output baseline markup automatically and both allow custom JSON-LD injection into the page head. That injection route is how you add types the platform does not cover.

Custom builds. Generate schema server side from the same database fields that render the visible page. Never hard-code values into a template. Hard-coded markup is guaranteed to drift out of sync with reality the first time a price changes.

The universal rule, regardless of platform: every claim in your markup must be visible on the page to a human visitor. If your schema says you have 47 reviews averaging 4.6 stars, those reviews must be shown on that page. If it states a price, the price must appear. This is not a technicality. It is the explicit condition on which rich result eligibility depends, and it is the most common reason enhancements get revoked. Course and programme pages for schools face this constantly, which is why our education SEO work insists on the visible-content check before anything is marked up.

Testing, Monitoring and What Goes Wrong

Never publish markup without testing it. There are two tools and they answer different questions.

The Schema Markup Validator checks whether your code is valid against the Schema.org vocabulary. It answers: is this well formed?

The Rich Results Test checks whether Google will actually use it. It answers: does this qualify for an enhanced listing? A page can pass the first and fail the second, which confuses people constantly. Validity is not eligibility.

After publishing, Search Console becomes your monitoring surface. Under the Enhancements section, each schema type you have implemented gets its own report showing valid items, items with warnings, and errors. Warnings are recommended fields you have left empty. Errors are required fields you have left empty. Fix errors. Treat warnings as a completeness checklist rather than an emergency.

Now the failures, in order of how expensive they are.

Markup that does not match visible content. Covered above, and worth repeating because it is the one that triggers manual action. Google can and does apply a structured data manual action that strips rich results from an entire site.

Self-serving review markup. Adding AggregateRating to your own homepage for your own business, based on ratings you collected yourself and display nowhere, is against the guidelines. Review markup belongs on pages about a specific product or service, sourced from reviews genuinely shown on that page.

Duplicate or conflicting blocks. Two plugins, or a theme plus a plugin, both emitting Product markup with different values. Google may ignore both.

Stale data. Prices, stock status and opening hours that were correct at build time and are now wrong. Automated generation from live data prevents this. Manual markup guarantees it eventually.

Marking up the wrong entity. A category page marked as a single Product. A blog listing page marked as one Article. The type must describe what the page primarily is.

Here is the contrarian point. Conventional wisdom says to mark up everything you possibly can, on the theory that more signals mean more visibility. In our experience that is usually a mistake. Every type you add is another thing to maintain, another possible source of contradiction, and another surface for error. Five accurate, well-maintained schema types beat fifteen half-populated ones every time. We have seen sites where an ambitious markup rollout produced so many conflicting blocks that Google displayed none of them, and stripping the implementation back to three types restored the rich results within a month.

What Results to Realistically Expect

Set expectations before you start, because the gains are real but specific.

You will not move up the results page because of schema alone. Anyone promising ranking improvements from markup is selling you something. Position is determined by relevance, authority and content quality.

You may gain a materially better listing. Where rich results appear, the effect on click-through is often significant, with lifts commonly in the range of ten to thirty percent depending on the result type and how visually distinct your competitors’ listings are. FAQ expansions and star ratings tend to produce the most visible difference on service searches.

Eligibility is not a guarantee. Google decides per query and per result whether to display an enhancement. Valid markup makes you eligible. It does not oblige Google to show anything, and displayed formats change over time as Google adjusts what it supports.

The compounding benefit is machine readability. Structured data increasingly feeds systems beyond the classic blue links, including AI-generated answers, voice assistants and aggregators. Accurate entity data about your business, location, services and hours is becoming infrastructure rather than decoration.

Measure it properly. In Search Console, compare average click-through rate for the affected pages in the eight weeks before and after implementation, filtered to the same queries. Do not compare against a period containing a promotion, a festive peak or a site redesign. Financial services firms are a useful benchmark here because their listings compete on trust cues, and the reporting approach we use is described in our finance SEO work.

Field notes: In our ecommerce case study, a WooCommerce home and lifestyle store, we implemented Product schema covering name, price, currency, availability and aggregate rating across all 200+ product pages, with custom overrides for edge cases. Rich results showing price and stock status began appearing within 6 weeks of deployment, lifting click-through for ranking product pages by an estimated 18% at equivalent positions. On a local online store, getting currency and availability right is often the quickest and highest-return schema win available to a small business.

Our Take

Structured data is best understood as translation rather than optimisation. You are restating what is already on your page in a form machines can read without guessing, and the payoff arrives as a more useful listing rather than a higher one. Start with LocalBusiness and Organization, add the one or two types that genuinely describe your commercial pages, get the Singapore-specific fields right including SGD pricing and proper address formatting, and generate everything from live data so it cannot drift. Resist the temptation to mark up every entity you can name, because breadth without maintenance produces contradictions that cost you the enhancements you were chasing. If you would like us to check what your pages are currently telling search engines, our technical SEO page explains the process, and our clinic results work shows what accurate markup looks like in practice.

We’ve seen a rich result disappear overnight because a price or an availability value in the schema drifted out of sync with what the page actually displayed, which validators do not catch. Our clients get the most durable results by generating markup from the same data source that renders the page, so the two can never quietly disagree.

Frequently Asked Questions

Will adding schema markup improve my Google rankings?

Not directly. Structured data is not a ranking factor in the way content quality and links are. What it does is make your page eligible for enhanced result formats such as star ratings, FAQ expansions, prices and breadcrumbs, which typically lift click-through rate. More clicks from the same position is a genuine commercial gain, and sustained engagement improvements can indirectly support performance over time, but nobody should promise you a position change from markup alone.

How long before rich results appear after I add markup?

Google must recrawl the page first, which usually takes days to a few weeks depending on how frequently your site is crawled. After that, Google decides whether to display the enhancement, and that decision is made per query rather than once for the page. Some sites see FAQ expansions within a week. Others wait a month and then see them appear intermittently. Check the Enhancements reports in Search Console to confirm Google has at least read and accepted the markup.

Can I add FAQ schema to every page on my site?

Technically yes, sensibly no. FAQ markup belongs on pages that genuinely contain a question and answer section visible to visitors. Adding it to pages without real FAQ content violates the guidelines and risks a manual action that removes rich results across the whole site. Google has also narrowed which sites it displays FAQ enhancements for, so the practical benefit is less universal than it was a few years ago. Use it where it honestly fits.

What is the difference between the Rich Results Test and the Schema Markup Validator?

The Schema Markup Validator checks whether your code is syntactically valid against the Schema.org vocabulary. The Rich Results Test checks whether Google considers the markup eligible for one of its enhanced result formats. Code can be perfectly valid and still not qualify, usually because a required field is missing or the type is not one Google renders. Use both: the validator for correctness, the rich results test for eligibility.

Do I need a developer to add structured data to my website?

Usually not. On WordPress, Shopify, Wix and Squarespace the common types are generated automatically once you complete the platform or plugin setup properly, and custom JSON-LD can be pasted into the page head without touching templates. You need a developer when you want schema generated dynamically from live data across hundreds of pages, or when your platform outputs conflicting markup that has to be removed at template level.

Should my prices be marked up in SGD or in another currency?

SGD, always, for a Singapore-facing business. The currency code is a required field on Product markup and plugin defaults are frequently set to a foreign currency, which means your listing can advertise a number that is wrong for your market. This is one of the most common and most damaging faults we find on local online stores, and it is usually a single setting rather than a development job.

Can structured data get my site penalised?

Google can apply a structured data manual action, which removes rich results eligibility across the site. It is triggered by markup that misrepresents the page: claims not visible to visitors, self-serving review ratings, marking up content that is not there, or spammy use of types. It does not affect your normal rankings, but losing enhancements you had been benefiting from is a real cost. Keep every marked-up claim visible on the page and you will not encounter it.

What happens to my schema if I change my theme or plugins?

It frequently breaks, and quietly. Theme-generated markup disappears with the theme. Plugin-generated markup disappears if you switch plugins. Two plugins running at once can emit conflicting blocks. After any theme change, plugin change or platform migration, re-test a sample of pages with the Rich Results Test and check the Enhancements reports in Search Console a fortnight later for a drop in valid items.

Is structured data useful for AI search and voice assistants?

Increasingly yes. Systems that generate answers rather than list links rely heavily on being able to identify entities, attributes and relationships with confidence, and explicit markup is the cleanest way to supply that. Accurate business, location, service and pricing data in structured form is becoming infrastructure for visibility across formats rather than a trick for one search results page. That is a good argument for accuracy over breadth.

My reviews are on Google and Facebook, not my website. Can I mark them up?

Not as AggregateRating on your own pages. Review markup must reflect reviews genuinely displayed on the page carrying the markup, and pulling in third-party ratings you do not host is against the guidelines. The practical route is to display genuine reviews on your site, through a review platform integration that renders them as visible page content, and mark up what is shown. Your Google reviews continue to work where they already appear, in your Business Profile.