How to Add Reviews to SITE123: Code Is a Page Here

On most builders the question is which block takes the code. On SITE123 the question is which page, because code is not a block here at all. Custom Code is a page type you add from the Pages tab, and everything that follows comes from that one design decision. The reviews end up as a place on the site rather than a section inside one, the height is set by a slider rather than by the content, and the menu gains an entry whether you wanted one or not.

There Is No HTML Element on a Normal Section

This is the part that sends people in circles. SITE123 content sections are designed layouts with fields you fill in, and none of them has a slot for markup. Looking for an HTML block among the section types is a search that cannot succeed, and it is worth stopping it early rather than working through every section type twice.

The reason is the same one behind SITE123 as a whole. It is built so that a site cannot be visually broken by its owner, and arbitrary markup inside a designed section is the fastest way to break one. Confining code to its own page keeps that guarantee intact while still allowing embeds.

So the mechanic is not hidden, it is elsewhere. Once you know to look under Pages rather than under section types, the whole thing takes about two minutes.

Custom Code Is a Page, Not a Block

In the editor, open the Pages tab and add a Custom Code page. Give it a name that will read well in the menu, because that name is going to be visible. Reviews works. So does Customer Reviews if the site has room for it.

Click inside the code area and paste the widget embed. SITE123 describes this as embedding external scripts and HTML directly into the project structure, which is exactly what a review widget needs: a script that runs and renders in place.

Save. SITE123 states that changes apply instantly to the live site, so there is no separate publish step to remember and no gap between saving and the page being real. Open the live URL and the reviews should be there.

The Custom Height Slider Is the Layout

The right-hand panel carries a Custom Height slider measured in pixels. It sets how much vertical room the embedded content is given, and it is the only layout control you have on this page, so it is worth getting right rather than leaving at whatever it defaults to.

Set it to a little more than the widget needs rather than exactly what it needs. Reviews vary in length, a longer one can push the last card down, and a few tens of pixels of slack is cheaper than a page that clips its final review whenever someone writes a paragraph.

Check the result at phone width as well. The same widget stacks differently on a narrow screen, usually taller, and a height that frames a three-column grid neatly on desktop can cut the bottom off the stacked version.

When Site-Wide Is the Right Answer

SITE123 documents a second route for code that belongs across the whole site rather than on one page: the Plugins section under the main Settings menu, which handles head and body insertions site-wide. It is the correct place for analytics, verification tags and anything else that has to be present everywhere.

It is usually not the right place for a review widget. A widget that renders inline where you put it wants a specific position on a specific page, and a site-wide injection has no position to be given. Use it only if you are doing something deliberate, such as a floating badge that should follow visitors across the site.

If you do use it for a badge, use it once. Two badges on the same page is a common outcome of adding a site-wide snippet and then forgetting it while building a Custom Code page as well.

What a Reviews Page Does to the Menu

Because Custom Code is a page, it appears in the site navigation like any other page, and that is a real editorial decision rather than a side effect to ignore. A Reviews entry in the menu is a promise that there is something worth clicking, and a page holding one widget delivers on it thinly.

The better shape is to treat it as a destination and give it a reason to exist. The widget plus a short line of context above it reads as a page. The widget alone reads as a leftover.

Then link to it from where the decision actually happens. A button next to the contact form or the booking link that says how many reviews and what the rating is will send more people to the page than the menu entry will, and SITE123 menus make it one click from anywhere regardless.

How Do You Build the Widget?

Paste your Google, Trustpilot or Facebook profile URL, preview your real reviews and rating, then choose from over 100 layout styles across the slider, marquee, grid, list, masonry and badge families, and set the colours and fonts to match the SITE123 template.

The header rating comes from the platform aggregate rather than from the cards being displayed, so the number on the page matches the number on the profile a visitor lands on if they click through. That consistency is the reason to show a number at all.

Free plan, unlimited widget views. SITE123 is often chosen because it is inexpensive to run, and a review widget that starts asking for money once the site gets traffic would be an odd thing to build into it.

Where Should the Reviews Go?

Given the page constraint, the answer is a dedicated Reviews page linked from the home page call to action rather than a section buried mid-scroll. It is the shape SITE123 pushes you towards, and it is a perfectly good shape when the link into it is prominent.

Keep the widget above the fold on that page. A visitor who clicked a link that said reviews should see reviews without scrolling, and the page has nothing else competing for that space.

If the business has more than one location, remember that a review profile is usually a single location. A site with a page per location wants each one pointing at its own profile rather than all of them showing the flagship.