How to Add Reviews to HubSpot: There Is No HTML Module

You will open the HubSpot page editor, scan the module list for something called HTML, and not find it. Text, image, header, call-to-action, form, gallery, button, divider, video, meetings, payments. No HTML module. The usual conclusion is that HubSpot gates custom code behind a paid tier, and the usual next step is the design manager, which is a developer tool you do not need for this. The route is the rich text module. HubSpot describes it as supporting embed code, its source code view is two clicks away under Advanced, and it is available on all products and plans, free tier included.

There Is No HTML Module. Here Is What to Use.

HubSpot's common modules are built around marketing jobs rather than markup: rich text, image, header, call-to-action, form, gallery, button, divider, follow me, video, meetings, payments. Nothing in that list is called HTML, Custom HTML or Embed.

The rich text module is the one that takes code. HubSpot's own documentation describes it as a flexible container supporting multiple content types including text, links, images, video, embed code and tables, and embed code is the part that matters here.

This is worth stating plainly because the absence of an obvious HTML module sends people two wrong ways. Some conclude the feature is paid and go looking for a plan to upgrade. Others go to the design manager and start building a custom module. Neither is necessary.

Advanced, Then Source Code

Drag a rich text module onto the page where the reviews should sit, then select it. In the module's options, open the Advanced dropdown and choose Source code. A dialog opens with the module's markup in it.

Paste the widget embed into that dialog and click Save changes. The editor will render what it can inline, and the published page renders the widget properly.

One HubSpot quirk worth knowing while you are in there: HubL code added through the rich text source code view does not render in the editor, only when the page itself is rendered. A review widget is plain HTML rather than HubL, but the same principle applies to how much you should trust the editor preview.

Do not use the rich text module for both prose and the embed if you can avoid it. Give the widget its own module. It keeps the source code view small enough to read, and it means a marketer editing the copy above cannot disturb the embed below.

Does This Work on the Free Tier?

Yes. HubSpot lists the rich text module under all products and plans, so the source code view is not a paid Content Hub feature. If you are on free tools with a HubSpot-hosted page, this route is open to you.

That matters because a lot of the third-party writing on this subject assumes a Content Hub Professional subscription, which is where several genuinely gated features live. Embedding a widget is not one of them.

What paid tiers do buy you here is not access but convenience: more control over templates, custom modules built once and reused across pages, and the theme-level tooling that makes a consistent design easier. None of that changes whether a single embed works.

When the Design Manager Is Actually Warranted

When you want the reviews as a reusable module that marketers can drop onto any page without touching code. That is a real use case on a site with a content team, and the design manager is exactly the right tool for it: build a custom module once, expose whatever fields you want, and let editors place it.

It is not warranted for a single embed on a single page. A custom module is a thing you own and maintain, and it introduces a developer as a dependency on a change that would otherwise be a paste.

The honest middle path on a bigger site: paste the embed into a rich text module first, confirm it works and looks right, and only then decide whether it is worth wrapping in a custom module. Most teams find one or two placements is all they need.

How Do You Build the Widget?

Paste your Google, Trustpilot or Facebook profile URL, preview your real reviews and rating, then pick from over 100 layout styles across slider, marquee, grid, list, masonry and badge families. Colours and fonts adjust so the section matches your HubSpot theme rather than sitting on the page as an obvious embed.

The rating comes from the profile's own aggregate rather than from the cards on screen, so the number on your page matches the number a visitor finds if they check it.

The output is one line of HTML. It goes into the rich text module's source code view here, and the identical line works in a WordPress Custom HTML block, a Squarespace Code block or a Webflow Embed element. Free plan, unlimited widget views.

Where Do Reviews Belong on a HubSpot Page?

Beside the form. A HubSpot landing page almost always exists to capture a contact record, and the form is the moment of hesitation: the visitor is deciding whether this company is worth an email address. Two or three reviews in the column next to the form answer that question exactly where it is being asked.

That is a different placement from most of the platforms in this series, where the reviews go above a general call to action. HubSpot pages are usually narrower in purpose, and the proof should sit closer to the ask.

On a longer page, keep a compact rating badge near the top as well. A visitor who arrives from an ad has no context for your company, and a real rating with a source in the first screen buys enough credibility to keep them reading.

Resist a full review wall at the bottom of a landing page. By the time someone reaches the footer they have already decided, and proof placed there is proof that arrived late.