HubSpot Updates Marketplace App Listing and Certification Requirements

Where these brands stand in our index

These figures come from a fixed panel of prompts re-run on a schedule, most recently on 2026-07-28. The measurement is independent of this event: any position or movement shown here is reported alongside the event, not caused by it, and we make no causal claim between a single event and a panel measurement.

Who reported it, and when we saw it

Key facts

• HubSpot updated listing and certification requirements for HubSpot Marketplace apps, reported 2026-05-07.
• Corroboration for the change is 1 outlet: HubSpot's own developer communications.
• HubSpot scores 25.0 visibility and rank 2 in DABYTE's SaaS & AI Tools AI Visibility Index as of 2026-07-28.
• Per-engine visibility is identical at 25.0 on OpenAI and 25.0 on Perplexity.
• HubSpot's commercial intent reading is 82, with a quadrant assignment of Niche (visibility gap).
• The measured visibility delta for HubSpot is +4.1; the event's decision-relevant window is 336 hours.

What HubSpot changed

HubSpot revised the requirements that apps must satisfy to be listed in the HubSpot Marketplace and to carry certified status, with the update reported on 2026-05-07. The stated purpose is alignment with current platform standards and with deprecations already in effect, meaning the requirement set now tracks what the platform supports rather than what it supported when earlier versions of the rules were written. Specific clause-level changes, effective dates for enforcement, and any grace period for apps already listed were not disclosed in the material available to DABYTE. Two distinct tiers are affected: listing, which governs whether an app appears in the Marketplace at all, and certification, which is a separate review outcome applied on top of a listing. Developers maintaining apps in either tier are the audience for the change; end customers of those apps are not asked to take any action in what was published.

Corroboration count is one

Corroboration for the requirement update stands at one. The only source carrying the change is HubSpot itself, through its developer-facing release communications, and DABYTE found no independent outlet, analyst note, or second publisher reporting the same event. A corroboration count of one is normal for vendor platform-policy changes, which typically reach developers directly rather than through the trade press, but it has a practical consequence for anyone relying on AI assistants for answers: with a single publisher, there is no redundancy in the citation pool. If an engine has not indexed the vendor's own changelog, it has nothing else to draw on, and answers about Marketplace certification rules will reflect older requirement language until that page is crawled. Developers should treat the vendor's own documentation as the only authoritative record of the current requirement set for this change.

Where HubSpot sits in our index

HubSpot holds a visibility score of 25.0 and rank 2 in DABYTE's SaaS & AI Tools AI Visibility Index, measured on 2026-07-28 across OpenAI and Perplexity. A visibility score of 25.0 means HubSpot is named in a quarter of the AI answers sampled for the category. Per-engine results are identical: 25.0 on OpenAI and 25.0 on Perplexity, with no split between the two systems. The measured delta is +4.1, the movement in visibility share since the prior measurement. HubSpot's quadrant assignment is Niche, described in the index as a visibility gap, which pairs a high commercial-intent reading with an answer share below what that intent would imply. Commercial intent is 82, meaning most of the queries where HubSpot surfaces are purchase-oriented rather than informational — the queries where an omission from an AI answer has direct downstream cost.

Why a rules change matters at 82 intent

Commercial intent of 82 for HubSpot means the AI queries in which the brand appears skew heavily toward evaluation and buying rather than general reference. Marketplace listing and certification requirements sit directly in that path: certified status is one of the signals buyers and AI assistants use to filter third-party apps, so a change in what certification requires changes the composition of the certified set over time. With HubSpot's visibility at 25.0 and its quadrant flagged as a visibility gap, the practical exposure falls on the app developers rather than on HubSpot. An app that loses listing or certification because it depends on a deprecated platform capability disappears from the surface that high-intent AI answers draw from. No enforcement timeline was disclosed, so the size of any such set cannot be measured from what was published.

Shelf life and what to watch

Shelf life for the requirement update is 336 hours, or 14 days, which is the window DABYTE assigns to platform policy changes of this class before the operative details are superseded by documentation updates or enforcement notices. Within that window, three things remain unresolved in the public record: the specific requirements added or removed, the date enforcement begins, and whether apps already listed or certified are reassessed against the new set. Each would need to come from HubSpot, since corroboration is one and no second publisher is tracking the change. On the measurement side, HubSpot's next index reading will show whether the +4.1 delta recorded on 2026-07-28 continues or reverses, and whether the identical 25.0 shares on OpinAI and Perplexity diverge. A single data point does not establish direction, and DABYTE does not read a trend from one measurement.

Questions this answers

Machine access

• /api/articles.json — every piece we published, with the measurement each one rests on
• /api/aiv.json — the AI Visibility Index the numbers above come from
• How the index is measured