Which practices does this apply to, and who decides?
For practices where a professional body's disciplinary rules outrank the marketing plan: doctors, dentists, physiotherapists and psychologists on one side, lawyers, notaries, accountants and architects on the other. They do not ask the same question, but they ask it in the same order — first is it allowed, then does it work.
| Who | Who decides | What keeps them up at night |
|---|---|---|
| Regulated profession — lawyer, notary, accountant, architect | The professional, or whoever holds the practice | Whether professional conduct rules allow it, and whether client data is involved |
| Care practice — GP, dentist, physio, psychologist | Whoever runs the practice, between two consultations | Professional conduct, patient privacy, and medical claims |
What does an AI look at when it recommends a practice?
For a practice, standing weighs more than reach. A listing in a professional register, or a statement carrying your title, counts for more with an engine than ten social posts — which is convenient, because that second option is often not allowed anyway.
| Driver | What ceeme measures underneath | What stays dark without a connection |
|---|---|---|
| Source authority | the standing of the sources that name you | Which sources name you and how much they weigh, we see. Writing to them is human work. |
| Reputation risk | misquotes, sliding reviews and where they come from | Reviews and social are read live. Print and paywalled media are not in there. |
| Compliance / deontology risk | claims your sector does not allow you to make | Your professional body's rulepack is not fully formalised yet; what is there is strict, not complete. |
| Local trust | GBP, reviews and whether your details match everywhere | We read your Google profile. Changing anything in it needs a GBP connection. |
| Hallucination risk | invented and outdated facts about you, counted by type | We see what an engine invents about you, and we follow the media coverage around it through the press feed. |
Which sources do you use, and does anything touch my files?
Only what is public, plus what you explicitly connect. Your calendar, your files, your patient records and your bookkeeping do not go in, and there is no setting that lets them. That is not a promise in a privacy statement but a boundary in the code: no path exists that brings that data into a measurement.
| Source | Kind |
|---|---|
| GBP | public — we read it, you connect nothing |
| reviews and directories | public — we read it, you connect nothing |
| public — we read it, you connect nothing | |
| sector directories | public — we read it, you connect nothing |
| care directories | public — we read it, you connect nothing |
| GBP (read) | connected — only after your approval, read-only unless agreed otherwise |
| GA4/GSC (read) | connected — only after your approval, read-only unless agreed otherwise |
| GA4 (optional) | connected — only after your approval, read-only unless agreed otherwise |
What do you never write, even if I ask for it?
No superlative, no comparison with a colleague, no promise about an outcome, and in a care practice not a single sentence that could read as treatment advice. Ask for it and it does not come out — the rulepack sits before generation, not behind it as a check.
| Rule | Kind |
|---|---|
| Your profession's conduct rules sit before generation, not behind it as a check: output that crosses them is never written. | hard rule — the build refuses output that crosses it |
| Every claim about what your practice can do or achieves must trace back to something you confirmed yourself. | hard rule — the build refuses output that crosses it |
| No "the best", no "leading", and no comparison with a colleague — in a regulated profession that is often a disciplinary offence. | forbidden — we do not do this, not even on request |
| Files, calendars and client records go in nowhere — not as a source, not as an example, not in a report. | forbidden — we do not do this, not even on request |
| Not a single sentence that could read as a medical claim or a promise of treatment, not even in passing. | hard rule — the build refuses output that crosses it |
| The measurement runs on public sources. No path exists that brings personal data from your practice into a measurement. | hard rule — the build refuses output that crosses it |
| The same rulepack, with the care-specific rules added — they are not a toggle, they are simply there. | hard rule — the build refuses output that crosses it |
| We do not write medical content. If something medically wrong circulates about your practice, we tackle the source and not the text. | forbidden — we do not do this, not even on request |
| Patient data is not read, not stored and not processed, in any route. | forbidden — we do not do this, not even on request |
What do you need from me to start?
The professional code that binds you, your accreditations or registration numbers, and read access to your Google profile. The first matters most: without knowing which body you fall under, we may apply the wrong rules — and too strict beats too loose here, but neither is right.
Frequently asked questions
My professional body forbids advertising. Is this advertising?
Measuring is not: that is establishing what is already being said about you. For correcting, the line is sharper, which is why it sits in the code. Fixing your details, making your accreditation findable and removing a factual error is information. Calling yourself the best or comparing yourself to a colleague is advertising, and it does not come out of here — not even on request.
What if an AI says something medically wrong about my practice?
Then you see it there, with the source that caused it. What we do next is tackle that source — a page being misquoted, a register with an outdated detail. What we do not do is write a medically correct text to replace the wrong one: that is your profession, not ours, and the rulepack blocks it.
Is my profession's rulepack complete?
No, and the table above says so. What is there is strict — stricter than most bodies require — but not every code is fully formalised yet. In practice that means things get blocked which were actually allowed, and that is the side we would rather err on.
Read on
Free, no account and no card.