Product Feed Health Checker

Independent preflight checker — not an official Google or OpenAI approval service

Changelog

Changelog

Every ruleset version and product change, with the source that triggered it — so a change in a report can be attributed to the rules rather than to the file.

64 versioned rules across 3 rulesets · ruleset 1.0.0 · rule data verified 11 November 2026 · no account needed for a local run

Current ruleset: 1.0.0 (schema 1.0.0)

64 rules · verification date 11 November 2026 · rule data generated 12 November 2026

The rule registry is the authority for versions. If an entry below and the registry disagree, the registry is correct and this page is the defect.

Entries

Site

12 November 2026

Public site and SEO foundation

  • Published the marketing site: tool pages, rule references, three guides, pricing, about, privacy, terms and this changelog.
  • Added a single source for URLs, titles, descriptions and canonicals, plus a sitemap and robots.txt generated from the same route table so they cannot disagree.
  • Added the ChatGPT Business Hub readiness checklist as a read-only, manual page. It is not an integration and does not automate any Business Hub action.
  • Structured data is limited to what each page visibly shows: Organization, WebSite, BreadcrumbList and TechArticle for authored guides. No aggregate ratings, reviews, prices or author credentials are published.
  • Published the OpenAI-versus-training crawler distinction (OAI-SearchBot versus GPTBot) and the PerplexityBot versus Perplexity-User distinction as separate documented policies.
Product

12 November 2026

Implementation stack revision (v1.1)

  • Authentication and billing moved in-house: six-digit email OTP, server-side session, SQLite owned by the account service as the single write path.
  • Hosted authentication and hosted database removed from the stack; no row-level-security layer and no client database access.
  • Payment provider is Waffo Pancake, with server-created checkout from an internal plan-key allowlist and webhook verification with deduplication by event id.
  • Frontend standardised on Next.js App Router with Mantine as the only component library, and one module as the single source of colour and spacing tokens.
Ruleset

12 November 2026

Rule registry frozen at version 1.0.0 (64 rules)

  • Frozen baseline: 64 rules — 10 shared catalog, 35 Google Merchant Center, 19 OpenAI Stable product discovery.
  • Every rule declares its applicability, requirement type, severity, expected outcome, official source URL and last-verified date, and is validated against a JSON schema plus an evaluator catalogue at load time.
  • Google image rules model the date change explicitly: 100×100 and 250×250 legacy minimums until 2027-01-30, 500×500 for every product image from 2027-01-31, with the warning phase starting 2026-04-14 as the checker’s own conservative policy.
  • Recorded the official conflict on the Google warning start (2026-04-14 annual update versus July 2026 troubleshooting article) and stated which date the checker uses, rather than silently picking one.
  • OpenAI rules keep Ads and Checkout out of scope, treat seller_url and other enrichment as non-blocking, and model the nine required basic fields separately from optional fields.
Specification

11 November 2026

First frozen specification (v1.0.0)

  • Defined the three-layer model: shared catalog health, Google Merchant Center product data, OpenAI Stable file-upload product discovery.
  • Defined the six-state result model with no composite score, and an explicit as-of date on every evaluation.
  • Defined the browser-first parsing model with opt-in, consent-gated remote scanning and a bounded, SSRF-safe scanner contract.
  • Defined the own-site SEO and AI visibility requirements this site is built against.

How a rule change is recorded

  • A platform source change produces a new ruleset version, not an in-place edit of an old rule.
  • Each affected rule records its own last-verified date, so a partly re-verified ruleset is visible as such rather than presented as uniformly current.
  • When two official sources conflict, both are kept and the entry states which one the checker follows and why.
  • A run records the ruleset version and as-of date it used, so a report produced before and after a change can be compared with the difference attributed correctly.

Sources are re-checked before release and at least monthly. Competitor pages are never recorded as platform specifications.