Tell Cleo About Yourself Once. Everything Else Runs On It.

It works, and the half you have done still does its job.

A section that is empty simply is not sent to anybody. You do not get a description full of blanks. What you lose is the specificity that section would have added. Half-filled gives you half the benefit, and it shows most in the writing.

The best order to work through it is Business, then Services and Location, then Brand and Voice. Those four sections give you most of the benefit. Team and AI Knowledge are where the last stretch of quality comes from.

A joined-up description of your business, built from what you have filled in.

Not one flat entry with your name and an outdated category, which is what most plugins send. Your business, your branches, your services, your people and their registrations all become separate, linked things with the relationships between them stated. That is the form in which the question is actually being asked.

You do not build any of it by hand. It is worked out from the Knowledgebase and kept in sync, so your schema moves with your business rather than sitting still from the day it was set up.

Not if you tell it not to. There is a switch for exactly that.

Turn on the online-only setting and your business is described without an address, coordinates or opening hours. You can still fill those fields in for your own contact page and footer. They are simply not published as facts about you.

It does a second useful thing. Telling Google you are at a particular address makes you look like a local business, which works against you if you are selling nationally. The switch protects your privacy and stops you sending a signal that fights what you are trying to do.

No, and this is one of the more subtle parts of the Knowledgebase.

Cleo finds the most precise standard description available for your trade. Where one does not exist, and it often does not, she points at an outside reference page that does describe what you are, and she checks that page resolves before saving it. If it does not, she reports it and leaves the field empty rather than publishing a broken reference.

She can show the reviews. She will not republish their stars as your own rating, and you should be wary of anything that does.

Google's guidelines do not permit a business to take ratings collected on Google or another review site and republish them as its own rating in the code of its pages. Doing so risks a manual action against the site, and plenty of plugins do it anyway because the stars look impressive.

Your review profiles are linked the approved way, which lets each site display its own rating. The only rating published as yours comes from reviews left on your own shop, which is permitted. Displaying live Google reviews on a page is fine, and there are widgets for it. Claiming them as your own business rating is the part that is not.

Because writing attributed to a qualified person carries more weight than writing attributed to nobody, with search engines, with AI answers, and with the person reading it.

Each team member can carry what they are registered as, which body registered them, and their number. For bodies Cleo recognises, she adds the register's own website to what Google is told. For a clinic, a practice or any regulated trade, that is the difference between an article that reads like marketing and one that reads like it came from somebody qualified to write it.

Steering, in your own words.

Three short paragraphs on where the business has been, where it is now and where it is heading, so the site reads like something current rather than written once and left. What to lean toward and what to ease away from, as preferences rather than rules. And the handful of facts you want right every time, such as a name, a spelling, or the way you talk to your customers.

Cleo uses it to colour what she writes rather than to recite it. Custom entries hold the specifics, like your booking lead time or your returns policy, so they come out right whenever she writes about them.

Your previous version is kept each time you save.

If a save goes wrong, you can put the last version back. That said, back the site up before installing any plugin that writes to the database. Cleo can undo the changes she makes to your pages, but neither of those is a full site backup.

No. The Knowledgebase is in both versions.

Presstack Core is a plugin. It goes on your site as it stands and leaves your theme and page builder alone. Presstack Theme is the other version, and it becomes the website, with its own design system, template control for every page type, a page builder and widgets. Both include the full Knowledgebase.

Once per site. Each site is a different business.

Cleo does the first draft each time: press Let Cleo Fill It In on the client's site and she reads it for you. The address comes from their Google listing link, their reviews come in on their own, and the voice section is an interview rather than an essay.

Agencies generally do the first one properly, see what it does to the output, and settle into their own routine from there.

The Knowledgebase stays. It lives in your own database, and you can edit every field of it by hand for as long as the site exists.

What has already been sent to Google about your business stays sent. What pauses is Cleo reading from the Knowledgebase to write new things. Your website keeps working. Cleo pauses.