Manual checklist · ChatGPT Business Hub
ChatGPT Business Hub readiness checklist
A read-only preparation checklist for merchants considering ChatGPT Business Hub — what you confirm yourself, what a public check can observe, and what the platform has not documented well enough for anyone to automate.
64 versioned rules across 3 rulesets · ruleset 1.0.0 · rule data verified 11 November 2026 · no account needed for a local run · Business Hub itself remains manual
Type
Read-only manual checklist
Items
16 across five sections
Automation
None — no claim, verification or upload
Score
No overall readiness score
This checklist is informational and manual. It is not a Business Hub integration, an eligibility check, an identity-verification service, an upload client or a ranking tool. The OpenAI Stable file-upload validator is a separate, deterministic ruleset based on a published schema; do not assume the same schema applies to a Business Hub self-service feed unless the platform documents that contract.
The labels below are the whole vocabulary. Notably, there is no pass or error for manual identity, ownership or ingestion status — those are not engineering results, and dressing them as such would be a claim we cannot support.
A public, machine-readable observation was made about this item.
You confirmed this about your own business. We did not verify it.
Something you must do before considering the checklist item prepared.
Not evaluated, usually because it needs evidence we do not collect.
The platform has not published a machine-readable contract for this.
A. Authority and claim preparation (manual)
These are statements only you can make. We never mark platform identity verification as completed, and we do not ask for the evidence a platform might request.
I own this business or am authorised to represent it.
Only you can assert this. Nothing in this tool checks ownership.
I can access the business public website and a contact channel the platform could use.
I have reviewed whatever ownership, identity or authority evidence the platform asks for directly.
Requested directly by the platform, never through this tool. Do not send identity documents to us.
Whether the platform has verified the business.
There is no public signal we can read, and we will never represent it as verified.
B. Business listing information (manual, plus basic public checks)
Public business details — name, address, contact details, category, opening hours, website — should be complete and consistent. Basic public checks are possible; legal ownership and business registration are not.
Business name, address, contact details, category and opening hours are current on the public site.
The public website responds over HTTP(S) and exposes a title, a canonical URL and contact links.
A public fetch only, with your explicit consent, using the SSRF-safe scanner.
No obvious contradiction between the public business details on your site and the details you would submit.
Obvious contradictions only. This is not a consistency score and it is not identity verification.
Legal ownership, business registration or tax identity.
We do not infer ownership, and we do not scrape private dashboards or registries.
C. Product feed preparation (machine checks plus a manual handoff)
Feed preparation is the part where a real validator helps. Note that the OpenAI Stable file-upload schema is its own contract; do not assume it is the Business Hub upload contract.
Run the independent OpenAI Stable product-discovery validator on the export.
Yes — this is a real, deterministic ruleset. See the OpenAI rule reference.
Run the Google Merchant Center checks separately if you also list there.
Separate ruleset with separate semantics. Never mixed.
Titles, descriptions, URLs, images, availability, prices and currency reflect current storefront data.
The validator checks syntax and machine-readable agreement; whether the copy is accurate is yours to confirm.
The retailer chooses and submits the feed in the Business Hub flow, if eligible.
We do not submit feeds. Availability of that flow depends on the current platform UI and eligibility.
Record the submission outcome you observe.
There is no ingestion API we can read. If one is published, it becomes a separate documented contract.
D. Engagement insights (manual education only)
Aggregate insights such as business mentions, discovery topics and website clicks are reported by the platform. We neither scrape them nor ask for access.
Understand what the aggregate insight categories mean and do not mean.
Documented here and in the AI commerce guide; the numbers themselves stay in the platform console.
Aggregate business mentions, discovery topics and website clicks read from your account.
We do not request account credentials, cookies or private exports to read analytics.
E. Business Agent (out of scope)
Business Agent is a separate feature with separate eligibility. Its published eligibility statements are informational and may change, so they are not turned into a checker rule.
Business Agent creation, policy configuration, business Q&A and conversation handling.
Out of scope for the MVP. Nothing here evaluates or prepares it.
What this page will never do
- Ask for Business Hub login credentials, session cookies, API tokens, identity documents or private account exports.
- Automate business claim, identity verification or feed upload, or present itself as able to.
- Store complete product feed contents on our servers.
- Produce an overall Business Hub readiness score, or mark a platform verification as completed.
- Treat Business Agent eligibility statements as a checker rule — they are informational and may change.
Any public website check uses the SSRF-safe scanner and needs your explicit consent for each scan. See the privacy policy for what a scan request exposes to the host.
Change control
If the platform publishes a distinct Business Hub feed schema, ingestion API, required field list or machine-readable verification contract, it becomes a separately versioned contract with its own fixtures and approval before any field is treated as blocking. The Stable file-upload schema is never silently reused as the Business Hub contract.
Checklist items and labels follow the frozen Business Hub readiness specification. Where the platform has not published a contract, the item says so instead of guessing.