Add Loyalty Program Structured Data Now, or Wait Until Your Tiers Are Defined?
Should you add loyalty program structured data now? See whether your markets and tier definitions meet the documented minimums before you commit engineering time.

You have a loyalty program, or one is on the roadmap, and someone on the team has asked whether the site should carry MemberProgram structured data.
The honest answer depends less on your CMS and more on two things you can check today.
First, are your shoppers in a market where Google documents this feature?
Second, does your program have the required tier structure?
This article walks through that eligibility decision so you can commit engineering time only when the documented minimums are met.
This guidance is grounded in Google's own loyalty-program structured-data documentation.
Every requirement below comes from that source rather than from general SEO folklore.
Where Google leaves something open, the article says so.
What MemberProgram markup is supposed to do
MemberProgram is a structured-data type that describes a merchant loyalty program.
According to Google, when you add it to your site, Search can use the information to display loyalty benefits with your products and in knowledge panels.
The program itself is specified under your Organization structured data.
Per-product benefits, such as member prices or points earned, are added separately as UnitPriceSpecification markup under each Offer.
That split matters for planning.
The program-level markup is one piece of work; the product-level benefit markup is a second, larger piece that touches every product page where you want benefits shown.
Budget for both, or decide deliberately to start with one.
Google also states plainly that it does not guarantee features consuming structured data will appear in search results.
Valid markup makes you eligible, not assured.
Treat the payoff as eligibility, and treat any expected display change as something to verify after deployment.
Check one: are your shoppers in a documented country?
Google documents loyalty-program information as available in Search results in Australia, Brazil, Canada, France, Germany, Mexico, the UK, and the US, on both desktop and mobile.
That is the documented list.
If your customers are primarily elsewhere, the documented feature does not cover your market today.
Building markup now would invest in a feature Google has not documented for your region.
This check can rule out the project for markets outside the documented list.
A brand selling mostly into markets outside the eight documented countries can reasonably defer the whole project and revisit if availability expands.
A brand selling into the US, UK, Canada, or any listed market passes this gate and moves on to structure.
One practical note: multi-market brands should check where their loyalty program actually operates, not just where the website ships.
A program enrolled only in North American stores is a different eligibility question than a global program, and the answer should match where members actually are.
Check two: does your program have at least one named tier?
The documented minimum structure is specific.
A loyalty program must have at least one tier, and the program needs a name.
Each MemberProgramTier in turn requires two properties: a name, and a hasTierBenefit value drawn from the TierBenefitEnumeration list.
That means a program described only as 'customers earn perks' is not yet markup-ready.
If your team has not defined at least one tier with a name and a concrete benefit type, the required properties do not exist yet.
Any markup written today would be invented rather than descriptive.
That is the strongest argument for waiting: markup should describe a program that exists, not one you hope to design later.
If you do have tiers, write them out before touching code.
For each tier, note the name, the benefit type, and how someone joins.
That list becomes your implementation spec.
Check three: does each tier's benefit type have what it needs?
The hasTierBenefit value drives a dependency.
Google documents two common values with attached requirements:
- TierBenefitLoyaltyPoints: the benefit is earning loyalty points, and you must also specify membershipPointsEarned, the number of points earned per currency unit spent.
- TierBenefitLoyaltyPrice: the benefit is a members-only price. For individual products, you separately add UnitPriceSpecification markup under your Offer markup, as described in Google's merchant listings documentation.
A tier can have multiple benefits.
If a tier earns points and also gets member pricing, both values apply, and both dependencies apply with them.
One gap to watch for is a points program without a documented earn rate.
If nobody can state how many points a member earns per unit spent, membershipPointsEarned cannot be filled honestly, and the markup is incomplete.
That is a concrete, resolvable blocker: define the earn rate, then build.
Check four: is joining the tier free, or is there a requirement?
Google documents that if hasTierRequirement is not specified, anyone can join the tier for free.
For a non-free tier, you specify a value that matches the requirement type.
Use a CreditCard value for a card the user must hold.
Use a MonetaryAmount value for a minimum spending requirement.
Use a UnitPriceSpecification value for a periodic membership fee.
Use a Text description for anything else, such as a coop-purchase-plus-volunteering rule.
This is a decision your program owner can usually answer immediately.
Paid membership tiers, spend thresholds, and co-branded card requirements each map to a different schema type, so getting the answer wrong means rework.
Confirm it before the developer starts.
Check five: markup or Merchant Center?
Google acknowledges that loyalty programs can be difficult to configure and keep up to date with markup.
It offers an alternative: if you have a Google Merchant Center account, you can configure your loyalty program there instead.
The documented precedence rule is important: if you provide both markup and Merchant Center loyalty programs, Google will use the Merchant Center settings.
That precedence creates a real failure mode.
If one team maintains markup while another maintains Merchant Center settings, the Merchant Center version wins, and the markup work is effectively invisible.
Before building markup, check whether a Merchant Center loyalty configuration already exists or is planned.
If it does, either build in Merchant Center or make a deliberate decision about which single source of truth you will maintain.
If you have no Merchant Center account, markup is the documented path available to you, and the choice is made for you.
Check six: validate, deploy carefully, and verify access
Google's documented implementation sequence is worth following as written.
Add the required properties, insert the markup in the format-appropriate location, follow the guidelines, and validate with the Rich Results Test, fixing critical errors.
Google also suggests considering non-critical issues the tool flags, noting they can help improve quality but are not necessary for rich-result eligibility.
Then deploy a few pages rather than the whole catalog.
Use the URL Inspection tool to test how Google sees the page, and confirm the page is accessible to Google and not blocked by robots.txt, a noindex tag, or login requirements.
If the pages look right, you can ask Google to recrawl the URLs, and Google recommends submitting a sitemap to keep it informed of future changes.
Finally, allow time.
Google notes it may take several days after publishing for Google to find and crawl a page.
A quiet first week is not evidence of failure.
A filled example of the decision, clearly illustrative
The following is an illustrative walkthrough, not a customer result.
Imagine a retailer with a two-tier program: a free Silver tier that earns points, and a Gold tier requiring a set annual fee that also grants member pricing.
- Country check: the retailer sells in the US and Canada, both on the documented availability list. Pass.
- Tier check: two named tiers exist. Pass.
- Benefit check: Silver's points benefit has a documented earn rate, so membershipPointsEarned can be filled. Gold's price benefit means product-level UnitPriceSpecification markup is also needed under Offers. Pass, with a scope note.
- Requirement check: Silver is free by omission; Gold's fee maps to UnitPriceSpecification. Pass.
- Source-of-truth check: no Merchant Center loyalty configuration exists. Markup is the path. Pass.
- Validation plan: Rich Results Test on a staging template, then deploy a few product pages and confirm none are blocked by robots.txt, noindex, or login walls.
Now the contrast case: a points-only program where the team has one unnamed 'member' level and no documented earn rate.
The tier name and membershipPointsEarned requirements both fail.
The right decision is to wait, resolve those two definitions with the program owner, and build afterward.
Writing markup with guessed values would describe a program that does not exist.
Failure modes worth naming in your planning doc
Four mistakes worth checking for in projects like this:
- Building markup for markets outside the documented availability list, where the feature is not documented to appear at all.
- Marking up a program with no defined tiers, which fails the documented minimum structure.
- Omitting membershipPointsEarned for a points benefit, leaving the markup incomplete against the documented requirement.
- Maintaining both markup and Merchant Center settings, where the documented precedence rule makes the Merchant Center version the one Google uses.
Each has the same cure: run the checks above against your actual program before scheduling the build.
So, build now or wait?
Build now if your shoppers are in one of the eight documented countries.
Your program also needs at least one named tier with a defined benefit type and any required dependencies, plus a single source of truth between markup and Merchant Center.
Wait if any of those conditions is unmet, and treat the unmet condition as your to-do list rather than as a permanent no.
A missing earn rate or an undefined tier is a definitional gap that a program owner can close, at which point the build becomes straightforward.
What you should not expect from either path is a guaranteed display change.
Google documents eligibility mechanics, not placement promises, so plan to verify what actually appears after deployment and indexing.
If you are also deciding which structured-data types belong on which page templates, that is the natural next question.
It changes how you sequence work like this.
For a template-by-template way to think about it, see Which Structured Data Types Should Each Page Template Get?
Once markup is live, Search Console reports become your verification surface.
how to export Google Search Console data covers getting that data out without hitting hidden limits.
Source references: developers.google.com.
How Meshline can help. Connect automation, Organic Marketing (demand generation), and customer lifecycle management (Revenue Intelligence).
Bring topic planning, content publishing and performance feedback into the conversation about your workflow. Book a Meshline demo.