How to Add Reviews to Webnode: When Was the Site Built?

Webnode attaches a date to its plan gate, which almost nothing else does. The company states that adding HTML code to the body of the website is a premium feature available with any premium package, and then adds that this applies to projects created after 26 June 2023. That qualifier is the interesting part: two Webnode sites on nominally similar footing can behave differently because of when they were created, so the first thing to establish is not just your plan but the age of the project.

Finding the HTML Block

Place the cursor inside the section where the reviews should appear. A plus button appears. Click the circle for additional options and choose HTML from the list, then enter the code into the field and publish the change.

The block behaves like other Webnode content blocks once placed: it sits in the flow, can be moved within the page, and takes its position from where you inserted it rather than from a separate settings screen.

Webnode documents a separate route for inserting HTML into the site header, which is the right place for analytics or a verification tag and the wrong place for a widget that has to render somewhere specific.

The Plan Gate Has a Date On It

Webnode states that adding HTML code to the body of the website is a premium feature available with any premium package, and that this applies to projects created after 26 June 2023. Both halves matter, and the second one is the unusual bit.

A project older than that date may not follow the same rule, so if you are working on a long-running Webnode site and the behaviour does not match the documentation, the project age is a plausible explanation rather than something going wrong.

When in doubt, look rather than reason about it. Open a section, click through to the block list, and see whether HTML is offered. That answers the question for your actual project in less time than working out which rule applies.

The Editor Will Not Show It

Webnode states that HTML additions appear only in the published version of the website, not in the editor preview. That is documented behaviour and not a symptom of anything, so an empty-looking block in the editor tells you nothing at all.

The consequence is the same one Tilda and Carrd users learn: publishing becomes part of the build loop rather than the end of it. Add the block, paste, publish, look, then arrange the surrounding content now that you know the real height.

It also narrows the debugging list. If the published page shows nothing, the candidates are the plan, a truncated snippet, or the block not having saved, and none of those can be diagnosed from inside the editor.

If the Site Has More Than One Language

Webnode is used heavily for multilingual sites, which are handled as parallel language versions of the same project. A block added to one language version is not automatically present in the others, so a reviews section can end up on the English site and missing from the German one.

Add it deliberately to each language version you want it on. It is the same embed each time, because the widget is showing the same business reviews regardless of which language the surrounding page is in.

The reviews themselves stay in the language they were written in, which is worth expecting rather than being surprised by. A German visitor reading English reviews is normal and still persuasive, and there is nothing to configure about it.

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 match the colours to the Webnode template.

The header rating comes from the platform aggregate rather than from the cards being shown, so the number on the page is the number on the profile. Free plan, unlimited widget views.

Build it before you start experimenting with placement. Since nothing renders in the editor, having the finished embed in hand means one publish tells you both whether it works and how it looks.

Where Should the Reviews Go?

On the home page, in the section above the contact block. Webnode sites are usually compact brochure sites and the home page carries most of the traffic, so one good placement there does most of the available work.

If there is a services or about page that people actually reach, a compact badge on it is worth the minute. Keep the full section to the home page so the site does not repeat itself.

On a multilingual site, decide once and apply it to every language version rather than letting the structure drift between them.