Social proof sells, but on a standard Odoo Website the reviews you have earned live somewhere else entirely — on your public map listing — while your product, service, and landing pages sit silent. Teams paste a third-party iframe or a manual screenshot, and it ages instantly: new reviews never appear, star ratings drift out of date, and the embedded widget breaks your Content Security Policy, tanks your PageSpeed score, and can never be filtered, translated, or styled to match your theme. Odoo core has no concept of an external review at all, and the website builder gives you a text block, not a live, moderated feed tied to your actual place ID.

We build a dedicated Website module that closes that gap end to end. A new models.Model (for example website.google.review) stores each fetched review — author, rating, text, review timestamp, language, and a moderation state — with a res.company/website link so multi-website and multi-location setups stay clean. A scheduled ir.cron job calls the reviews data source server-side (your API key held in ir.config_parameter, never shipped to the browser), upserts new entries idempotently on the external review id, and recomputes an aggregate @api.depends rating and review count on the location record. Because the data lands in real Odoo models, you get a back-office list/form view to hide spam or off-topic entries, a moderation record rule so only Website editors touch it, and ir.model.access.csv locking public read to published rows only. The front end is a set of draggable QWeb website snippets — a star-rating badge, a carousel, a masonry wall, and a single-review pull-quote — rendered server-side (SSR) so they are fully crawlable, cached via Odoo's website cache, and inherit your theme's fonts and colors instead of a foreign iframe. Optional JSON-LD AggregateRating/Review structured data can be emitted for rich-result eligibility, and an OWL-based client widget can lazy-load additional reviews without a page reload.

Delivery is build-to-order: nothing is downloaded today. After a short scoping call we confirm exactly which locations, snippet styles, moderation rules, languages, and Odoo edition (Community or Enterprise) you need, then build against your target version — we support Odoo 17.0, 18.0, and 19.0. You receive the module on a staging database first for UAT, then we install it on production, wire the cron cadence and API credentials, and hand over the git repository. Typical delivery is 2 to 4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); additional locations, multi-website/multi-company rendering, extra snippet designs, review-response sync, and deeper localization increase the quoted scope. You get a fixed quote after the scoping call — never a surprise invoice.