Skip to content

Loyalty program schema and the wrong member price

Connect loyalty tiers to the correct public program and product offers. Test eligibility, tier identifiers, member prices, and the logged-out shopping view.

By Crawlito · 5 min read

In short

  • MemberProgram describes the merchant's loyalty program and its tiers.
  • Product-level member benefits need the corresponding offer information.
  • A stable tier identifier helps prevent benefits from being assigned to the wrong membership level.
On this page

When a member price or benefit is wrong in structured data, trace the product offer back to the exact loyalty tier it references. Compare the public program terms, anonymous product view, and eligible member view. Google describes the merchant's program under Organization and product-level loyalty benefits through supported offer pricing fields. Google’s loyalty program documentation

Identify the program and tier behind the price

Start with one affected product and the tier a customer must hold to receive its benefit. Record the ordinary price, member price, currency, variant, market, and the terms that determine eligibility. A store can run a free membership, a paid level, and a temporary promotion at the same time. Similar display names do not establish that the benefits belong to the same group.

Open the public loyalty page without signing in. Can a prospective customer see how membership works and which conditions apply? A product page advertising a member price should give a useful route to those terms. A benefit hidden entirely behind a member dashboard leaves a new shopper unable to assess the offer they are being shown.

Use approved test accounts for member-specific checks. Record the account's tier without placing personal details into your debugging notes or page markup. A staff account can have discounts that ordinary members never receive, so confirm the test account represents the actual published eligibility conditions.

Give each tier a stable identity

Google's MemberProgram model describes a program with hasTiers entries. Give each represented tier a stable identifier and a public name matching the program. The illustrative fragment below shows the relationship for a fictional free membership tier. It is a starting point for understanding the graph, with actual benefits and requirements supplied from the merchant's maintained terms.

json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Supply",
  "hasMemberProgram": {
    "@type": "MemberProgram",
    "name": "Example Rewards",
    "hasTiers": [{
      "@type": "MemberProgramTier",
      "@id": "https://example.com/rewards#standard",
      "name": "Standard",
      "url": "https://example.com/rewards"
    }]
  }
}

Inspect any existing organization or online-store entity before inserting a separate program. The tier references used by product offers need to resolve coherently to the program you intend. A copied fragment identifier such as #gold on every product URL can create different identities depending on how the surrounding URLs are constructed. Use the site's established absolute identifier convention where appropriate.

The organization markup guide explains how to review an existing entity graph. Keep the tier identity independent of a marketing label that may change during a redesign. Renaming “Standard” to “Everyday” should not accidentally make historical references point to an unrelated tier.

Match each product benefit to the selected offer

A member price belongs to a particular product configuration and currency. Compare the variant chosen by the public URL with the offer whose pricing fields you inspect. A premium bundle can have a different member benefit from the base item. A generic product template may accidentally attach the lowest member price to every variant.

Read Google's current merchant listing documentation for the supported loyalty price and tier-reference fields. The program declaration describes the membership structure, while product-specific pricing needs its own accurate representation. Copying the program name into an ordinary price field cannot express the relationship. Google’s merchant listing reference

Test scenarioWhat should agree
Anonymous shopperPublic ordinary price and clearly described member conditions
Eligible standard memberStandard-tier offer and actual payable price
Higher tierIts own benefit and matching tier reference
Excluded productAbsence or correct description of the excluded benefit
Different marketCurrency, program availability, and local terms

Check whether a temporary sale stacks with the member benefit. A store may choose the better of two offers, apply an additional discount, or exclude promotional items. Get the intended rule from the merchant and compare the generated data with the actual eligible purchase. Avoid inferring that rule from whichever amount happens to look most attractive.

Trace stale values through the pricing system

Follow the affected offer through the catalog, loyalty service, page renderer, and any cached structured data. A browser may show a new member price after a client request while the initial HTML still contains an older amount. Compare the anonymous initial response with the rendered result and the authenticated view separately.

Record the time of each observation. A program update that reaches checkout before the product cache expires can produce a temporary disagreement. If the inconsistency persists, identify which component owns the stale value. The price mismatch guide provides a method for comparing offer identity and timestamps across publishing layers.

Inspect duplicate markup from commerce apps. A general product plugin may emit one offer while a loyalty extension adds another with different tier references. Find the component generating each block and verify whether their combined meaning matches the store's intended offers. A syntax test alone cannot determine which app has the current commercial policy.

Verify a tier change without leaking private data

Test a controlled account moving between supported membership states. Confirm the eligible price after the change and after a fresh login. A cached page tied to a previous member state can display an outdated benefit. Public structured data should describe published program facts and offers, without exposing account identifiers, balances, or personal eligibility records.

Validate the public markup with the supported tools and compare the recognized tier identifiers with the source configuration. Test at least one ordinary product, one excluded item, and one variant with a different price. Repeat the check in each market you intentionally support. Feature availability and supported properties can change, so use Google's current documentation when making a release decision.

Keep a compact acceptance record with product ID, variant, tier, market, expected price, and observed result. Follow search presentation separately. A correct public program and offer can be verified today even when a particular search feature has not appeared. The practical goal is an offer that prospective members can understand and eligible shoppers can actually use.

Inspect a tier reference after an app migration

Suppose a new loyalty application uses different internal tier identifiers while preserving the same public names. The program page can look identical after migration, yet product offers may still reference identifiers emitted by the previous app. Compare a product's tier reference with the current program graph and the mapping used by the pricing component.

Test an ordinary member, a higher-tier member, and an excluded product with your approved fixtures. Confirm that the public program and each applicable offer describe the intended relationship after the migration. The JSON-LD troubleshooting guide helps locate leftover blocks from the earlier integration.

If the merchant deliberately changes benefits during the move, record the effective date and the current terms separately from the technical identifier mapping. A rename, an identifier replacement, and a commercial policy change are different events. Testing all three as one undifferentiated “loyalty update” can conceal which part produced the wrong public price.

Frequently asked questions

Can a tier name alone identify the correct member benefit?

Use the documented relationship and a stable tier identity. Similar names across programs or markets can otherwise produce ambiguous references.

Should I publish a staff discount as a member price?

Only describe offers available under the public program's actual terms. Staff or test privileges may have different eligibility.

Will adding MemberProgram automatically change all product offers?

The program and product benefits are published through different fields and often different components. Inspect the actual product output after the change.

Check one affected product page

Run the free page check on the public product URL and compare its structured offer with the program tier and eligible shopping view you tested.

Filed under Structure and schema. Topics: ecommerce, structured-data, google