How to add Google reviews to GoHighLevel

Quick answer

1. Copy the script tag from your widget's Embed dialog in VerifiedWidget.
2. In the sub-account open Sites → Funnels (or Websites) and edit the page or step.
3. Add the custom code element (Custom JS/HTML or Code Block, depending on your builder version) where reviews belong and paste the script.
4. Save, publish, and test the public URL of that step.

What you need

Edit access to a HighLevel sub-account. HighLevel's public pages do not say which plans include the code element, so check your plan with HighLevel. If you cannot edit pages, ask your agency admin.

Add the widget to one page or funnel step

1. Use the VerifiedWidget script, not HighLevel's Reviews element

   HighLevel has its own Reviews element for its reputation tools. Ignore it here. Build the layout in VerifiedWidget, save it, and copy the script tag, so your hidden reviews and collections match what you configured.

2. Open the right step

   Choose Sites → Funnels for an ordered funnel or Sites → Websites for a site, select the page or step and open its builder. HighLevel offers split testing on funnels only. If a step has a split test running, add the widget to every version of it. Add a section or row just before the booking form or buy button, where the reviews can answer a last doubt.

3. Add the custom code element

   Drop the element into that section, open its code editor and paste the script. HighLevel's own help simply calls it a code element. Like most builders, it may show a blank box in the editor until you preview or publish. Use an on-page element because the widget needs a visible position. The Tracking Code area is for analytics-style scripts, not for placing a section.

4. Publish and test the real URL

   Save and publish, then open the public address of that step, not only the editor preview. Check desktop and mobile, especially columns next to a form. For an agency, test each client's domain separately.

HighLevel-specific problems

• Edited the wrong step. Funnels often have steps with similar names, and a saved edit on one does not change another. Confirm the step URL in the browser.
• Reviews at the very bottom of the page. The script went into the Header or Footer Tracking Code. Code there loads in the page head or at the end of the page, so the widget lands below everything else. Move it into an on-page code element.
• The element will not save. Make sure you are in a website or funnel builder. HTML fields inside Forms, Surveys and Quizzes have separate security validation.
• Appears only after you scroll or click. HighLevel's Optimize JavaScript setting can hold back custom code until the visitor interacts with the page. A consent tool can also delay it. Test in a private window before you change settings.

Use each client's own business and widget. Reusing one business's reviews on an unrelated client site would be misleading.

Testing a funnel step properly

Funnel steps are easy to misjudge in the builder. After publishing, open the step through its real funnel path. If later steps need a form submission, fill in the first step. Then confirm the reviews appear where a visitor will see them. If a step is only reachable after a form or payment, test it the same way. Agencies should keep a short checklist per client. Note the widget name in VerifiedWidget, the funnel and step it lives on, and the domain you tested. That makes it quick to find the code again when a client asks for a change.

Frequently asked questions

Related reading