Put a business's Google rating on its website and the number is frozen the second you type it.
A café we built a site for had 1,800 Google reviews and a five-star rating that kept climbing. That rating was the best thing the business had going, more convincing than any photo or line of copy we could write. So we put it on the homepage: Rated 5.0 across 1,800 reviews. True on the day we shipped. A month later the café had earned dozens more, but the site still said 1,800, because 1,800 was what we'd typed. The most persuasive thing on the page had started drifting out of date, and keeping it honest meant the owner emailing us every so often to ask us to change a number.
So we built something better. Now the rating and review count on the site read straight from the café's own Google listing and keep themselves current. A new review lands, Google's number goes up, the site follows. Nobody touches it. You set it up once when you build the site, and from then on the number stays right on its own, around the clock.
There are two normal ways to keep a review count from going stale, and both land on you. Wire in a third-party widget and you carry its monthly fee, per client site, for as long as that site is live. Skip the widget and you're editing the number by hand on every site you've ever shipped, forever. One is a subscription on your books; the other is a chore that grows with every client you sign. This is the third way: build it into the site once, hand it over, and it keeps itself current with nothing more from you — no widget to rent, nothing to maintain.
What the business owner gets
The rating they actually earned, on their own website, always showing the real, current figure. As new five-star reviews come in and the Google rating ticks up, the number on the site moves with it. The owner does nothing.
To a visitor it reads as a business that's clearly doing well right now: a row of stars, the score, "from 1,827 Google reviews," and the figure is correct today, not correct as of whenever the site last got touched. To the owner it's one less thing to think about, and one less reason to ever pay for a small edit.
And it belongs to them. There's no third-party badge sitting on the page phoning home to a service they rent, no "Powered by" link advertising someone else's product in the corner, no monthly invoice that shows up whether or not anyone visited. It's part of a website they own.
How it works
When the site builds a page, it asks Google's Places API for that listing's current rating and review count, and shows what comes back. It checks again on a schedule rather than on every visit, because a review count doesn't move minute to minute and there's no reason to hammer Google for a number that changes slowly. The owner never sees any of this. They just see a figure that's always current.
Three things make it safe to leave running:
The key stays on the server. Talking to Google needs an API key. A key that ships to the browser gets scraped and abused within days, so this one never leaves the server and never appears in the page. Nothing for a visitor's browser to load, nothing to leak.
There's a safety net. In normal running the live number is just there. But on the rare day Google can't be reached, the site falls back to the figure it launched with — a real number that was true once — instead of flashing a zero, a broken row of stars, or a guess. An old rating on an off day is survivable; a wrong one never is. So even the fallback only ever reaches for something real, never something invented.
It's pinned to the right listing. The number has to come from this business and not the similarly-named one two streets over, or you'd be putting a stranger's reviews on your client's site. Before it wires anything up, the skill finds and confirms the exact Google listing, using the same check the Klaudius pipeline already runs when it gathers a business's details. The match is verified, not assumed.
From the visitor's side there's nothing extra to load — no widget, no third-party script that has to fetch the number after the page appears. It's already baked into the page, so it shows instantly with everything else, with none of the lag or flicker a bolted-on widget brings.
How you run it
In Klaudius, it's one command, run after the site is built and deployed and pointed at the client. (New here? Klaudius is the tool that builds these websites and runs the pipeline behind them — finding local businesses without a site, building each a bespoke one, deploying it, and following up. This live rating is one of the features it can add on top.)
The reason it's a single command and not a custom job each time is that almost none of it changes between businesses. The fetch, the caching, the safe fallback, the rule against inventing a number — all identical, installed rather than rebuilt. The only things specific to a given client are which Google listing the number comes from and where on the page it shows, and the skill works both of those out from the site it's adding to. It finds the listing the way the Klaudius pipeline already does, and it makes the rating the site already displays a live one, in place.
When it finishes, the number on the site is no longer anyone's job.
"Doesn't this kill my retainer?"
Not at all. If anything it makes a retainer easier to run.
You can absolutely still charge monthly. A retainer was never really about retyping a review number; it's the client paying to know their site stays current and looked-after, with someone keeping it that way. A site whose reviews climb in public week after week is exactly that kind of living thing, and there's real value in it being managed — that's what the fee is for. The reviews keeping themselves current is part of what you're selling, not a reason the sale goes away.
What changes is your side of it. Because the number maintains itself, honouring the retainer no longer means logging into a roster of sites to hand-edit figures every month. That grind comes off your plate, and the fee now buys the client real work — new pages, fresh photos, a seasonal push — while the routine upkeep runs on its own. Same retainer, far less manual labour, better margin.
And for the owners who refuse anything recurring — a big slice of the cold leads you pitch — there's the other win. The worry at the back of their mind is being on the hook to someone forever, paying every time a detail changes. "It keeps its own reviews up to date, you never have to come back to me for that" is the line that closes them. You're not losing a retainer there. You're winning a client who was never going to pay one.
The money
Making the rating live costs you one command, and nothing to run. Where it pays off is what you do with it.
Start with the close. A review count that's going to sit frozen is a quiet doubt at the back of an owner's mind — won't this be out of date in a month? Being able to say the reviews keep themselves current answers that before it's even raised, and an owner who's proud of their rating would far rather see it shown live than typed once and left to rot. The thing that used to give people pause becomes a reason to say yes.
It's also a reason to charge a little more. A site whose social proof keeps itself current is a better product than one with a number drifting further out of date every week, and you can fold that into a higher one-off price or use it as the anchor of a small ongoing arrangement. And it's a reason the site keeps feeling looked-after long after you've moved on. The owner watches their rating climb on their own website and ties that good feeling to the thing you sold them, which is the best ground there is for a referral. The café owner who started this story has a homepage that's been making itself more impressive for weeks, with no input from anyone.
The widget companies would charge you every month for exactly this, on every site. You hand it over as part of a site the owner keeps, and it costs you a single command.
Klaudius builds bespoke websites for local businesses and runs the whole thing end to end — finding them, building each a custom site, deploying it, and handling the follow-up — with features like this self-updating rating built in. See how it works →
Team Klaudius