Want a tool from another service on your site, such as a chat button, a booking widget or a reviews bar? You simply attach it as a ready-made part.
What can you add?
- A live chat or WhatsApp button
- A booking or appointments module
- A reviews or rating widget
- Other embeddable tools your supplier provides
Across the whole site or one page
You place such a widget site-wide (visible everywhere) or only on a specific page, whatever fits.
Why widgets need a light touch
Third-party widgets are convenient, but each one adds an external request your visitors' browsers have to load. Keep an eye on page speed if you add several at once — one well-chosen widget usually beats five.
A common use case: a booking widget that only makes sense on your services page, not on every article. Placing scripts per page instead of site-wide keeps pages that don't need them lighter and faster.
Many chat, tracking or reviews widgets set their own cookies. If that applies to yours, make sure it only loads after consent through the cookie banner, alongside anything you already track through analytics.
Practical tip: if you find yourself building the same custom integration on multiple sites, it may be worth turning it into a reusable app or component instead of an external script.
Deciding whether a widget is worth the trade-off
Every embedded widget is a small dependency on someone else's server. If that service is slow, has downtime, or changes its script without warning, your page inherits the problem. Before adding one, it is worth asking whether the feature is genuinely needed on every visit, or whether a simpler built-in alternative — a form instead of a booking widget, for example — would do the job without the external dependency. Placing a widget on a single page rather than site-wide is a decision made at the level of individual pages, not the whole site, so it is worth being deliberate about where it actually needs to appear.
That said, some tools are worth the trade-off precisely because building the equivalent yourself would take far longer than it's worth — a mature reviews platform or a specialised booking system usually falls into that category.
Widgets across different kinds of sites
A restaurant benefits from a reservation widget that handles table availability in real time — building that logic from scratch rarely makes sense for a single location. A consultancy might only need a scheduling widget on its contact page, not site-wide. A retailer often adds a reviews widget to product pages specifically, since that is where social proof does the most work, rather than cluttering every page with the same badge.
The common thread is placement: the right widget on the one page where it actually helps a visitor decide something, rather than the same widget copied onto every page out of habit.
Common mistakes when adding third-party tools
The most common mistake is adding a widget and never revisiting whether it is still needed. Chat widgets from a service you switched away from months ago quietly keep loading on every page, adding weight for no benefit — a periodic review of what is actually installed is worth the ten minutes it takes.
The second is assuming a widget is exempt from privacy rules because it "just displays reviews." Many reviews, chat and booking tools set their own tracking cookies behind the scenes — always check, and route them through the cookie banner like any other tracker if they do.
For a broader look at how third-party embeds interact with page speed and search rankings, see structured data and the content is JSX article for how embeds fit technically into a page.
How to ask the assistant
Put our supplier's chat widget on every page.