HubSpot Marketplace Listing Checklist 2026

Projects CLI readiness is not the same as Marketplace readiness. A project can be correctly structured and still lack support information, privacy URL, testing instructions, install-flow evidence, or policy details required for a reviewable listing.

Review HubSpot listing docs and requirements before submission, then turn them into an owner-based checklist. Assign support, privacy, testing, product copy, screenshots/assets, and technical install flow to named owners.

Keep the claims boundary visible in client-facing material. This independent checklist can help organize readiness work, but it cannot guarantee Marketplace approval and it is not an official HubSpot review artifact.

Prepare a short app description, support contact, privacy policy URL, install/test instructions, authentication notes, and any screenshots or demo materials required for review. Confirm that public-facing claims match the app's implemented behavior.

For OAuth apps, verify redirect URLs, scopes, and test account behavior. For apps with cards or UI extensions, include enough testing context for a reviewer or client developer to reproduce expected behavior.

If the app was migrated, document the source app, command path verified, platform version, and any open limitations. That record can reduce confusion when Marketplace work is reviewed separately from migration work.

Agencies should keep a reusable listing readiness packet per client: app inventory, source-check date, support/privacy owners, testing instructions, and screenshots/assets status.

Use the paid bundle's CSV tracker to track multiple apps. Each row should include app type, likely path to verify, Marketplace owner, source recheck date, and risk level.

Before submission, re-open current HubSpot listing requirements. If a requirement changed after the local source check date, update both the client handoff and internal checklist.