This page explains how Phantom Gambling Devices prepares product data for merchant feeds, shopping catalogs, and social commerce crawlers without presenting products as gambling deception tools.
The catalog is intentionally framed for legal performance, private rehearsal, workshop education, card-integrity inspection, anti-cheating education, and collection care.
Feed alignment
- Product feed titles, product page titles, visible descriptions, image URLs, prices, availability, shipping, return policy, and structured data should describe the same offer.
- Product URLs in Google-style XML, JSON, CSV, canonical tags, sitemaps, and social previews should resolve to the same public product pages.
- The store should avoid exaggerated savings, fake urgency, hidden charges, unclear support identity, and mismatched business details.
Sensitive wording controls
- Allowed framing: card magic, staged routines, rehearsal decks, training kits, inspection education, anti-cheating education, and collector accessories.
- Avoid feed and page wording that promises unfair advantage, hidden gambling workflows, venue evasion, undetectable marking, or instructions for deceiving real players.
- Use the boundary guide at /en/articles/marked-deck-training-vs-cheating-misuse-boundary when a platform reviewer needs context.
Catalog rollout
- Start with lower-risk accessories, inspection education, training kits, and collector care products before broad marked-deck feed submission.
- Submit a small product set first, verify crawlability and policy status, then expand only after product pages, policies, and business profile data remain consistent.
- Keep product image access public for Googlebot, Bingbot, Pinterestbot, Meta crawlers, and link preview bots.
Promotion and member-benefit readiness
- Do not publish promotion, sale-price, loyalty, or member-benefit markup until a real benefit can be redeemed by users at checkout or inquiry confirmation.
- A promotion needs a public promotion URL or visible terms, coupon code when required, start and end dates, target country, eligible SKU mapping, minimum purchase rules, discount value, and return-policy impact.
- A loyalty or member benefit needs visible membership terms, eligibility, benefit type, supported region, cancellation or expiration rules, and the exact product or shipping benefit.
- Feed values, product page price, visible sale terms, structured data, and checkout price must update together; automated item updates should be treated as a backup consistency signal, not the source of truth.
- Avoid fake scarcity, evergreen countdowns, hidden checkout-only charges, mismatched sale prices, and duplicate promotions that map to the wrong product IDs.
Price and availability change control
- When price, availability, preorder status, or shipping terms change, update visible product HTML, Product JSON-LD, product feeds, social metadata, and sitemap/IndexNow submissions in the same release window.
- Use stable product IDs and canonical URLs across Google, Microsoft, Pinterest, Meta, comparison-shopping, and affiliate feed exports.
- Inspect a representative product in Google Search Console, Bing Webmaster Tools, and merchant catalog diagnostics after production deployment.
Trust surfaces
- Visible support channels: /en/contact, site email, phone, shipping and return policy, and terms.
- Entity support: /en/about, /en/press, /en/partners, /en/feed-resources, and future verified business profiles.
- Review schema remains disabled until real, visible, verifiable reviews are present on the site.
Not acceptable
- Cloaking different content to shopping crawlers, search crawlers, reviewers, or users.
- Opening duplicate merchant accounts to bypass a suspension or platform review.
- Publishing fake reviews, fake ratings, fake partnerships, fake author profiles, or fake scarcity.