Publish & Measure: the loop that compounds

Updated 22 October 2026 (Agent 11.1: re-measures send no email unless the team ticks Notify). Previously updated 21 October 2026 (Agent 11.1: Page Inventory redesign, from state/page-inventory.md). Previously updated 11 October 2026 (Agent 11.1: reviewer step and Wix publishing steps, #3711); earlier: Updated 8 October 2026 (Agent 11: reviews-off behaviour of the Sites reviews section folded; earlier: Agent 11.1: catch-up from every lane after their state-doc updates; scoring rebuild of 21 Sep, no score-trend claims, no citation claims for schema or credentials, Sites, content plan, support). Plain-English briefing on getting content live on any platform, the internal-linking flywheel, and the re-measurement that proves the whole thing is working. Written 24 July 2026. Checked against the state docs 2 October 2026 (Agent 11.1: re-measure no longer rebuilds the plan; publishing check added; schema wording guard). Last updated: 2 October 2026 (Agent 11.1: Co-Kinetic Sites launch position, Tor's ruling). Previously verified: 3 September 2026 (Agent 11: Wix walkthrough step split, and the new Co-Kinetic Sites automatic behaviours, folded in).

Publishing: any platform, without losing the invisible layer

Most of the value in a generated article is in two layers: the visible words, and the invisible structured data (schema) that describes the page to search engines. (Never claim schema improves AI visibility or citation; our research measured no such effect.) Naive copy-paste publishing keeps the first and silently loses the second. The platform's publishing routes are built to deliver both, on whatever the clinic runs:

WordPress, genuinely one click. For clinics on WordPress, publishing is a single click. The Co-Kinetic plugin pushes everything directly: content, schema, correct site section, clean URLs (with automatic redirects if section structure changes), and the clinic's live review rating rendered into both the page schema and a visible badge, server-side, always fresh, never fabricated. Updates work the same way, refresh an article on the platform and push again. The platform gets the live URL back automatically, so the linking flywheel (below) runs entirely hands-off. (Plugin 1.13.1, released 21 Aug 2026: the author panel now populates the documented author fields, credentials no longer show the photo URL on themes following the guide example. There is no auto-update: customers must re-download and reinstall the plugin to pick it up.)

After publishing or editing a page, clear the site's cache. Many clinic sites (and their hosting or CDN) keep a saved copy of each page for up to 24 hours. Until it is cleared, visitors and search engines see the old version. Our own live checks read the fresh page.

Wix, Squarespace, and everything else, guided copy-paste. The "Put it on your website" flow asks which platform the clinic uses and shows the one recommended route for it, with platform-specific honesty. The standout example: on Wix, pasting a full web page traps it in a container AI can't read, so the Wix route explicitly guides adding the words as native text and the schema through Wix's own SEO settings, in a short tick-off checklist. Formats the platform can't make AI-visible are labelled as such rather than quietly offered. Every route includes copyable schema, sized for platform limits. On Wix the publishing screen spells out each step: the page description is copied from the article's page in CCS into the page's SEO basics (Meta description); image text goes in by clicking each image, then Settings, then "What's in the image?"; and each article's schema goes on that article's page only (Page settings, SEO, Advanced SEO, Structured data markup), never in site-wide custom code, or every page carries that article's details. A piece shows as published once its live URL is added. (Since 31 Aug 2026 the Wix walkthrough's step 1 "Add the words" is guaranteed words-only; the schema code appears ONLY in step 2, at Wix: SEO & GEO → SEO Settings → Advanced SEO → Structured Data Markup. Previously an article could carry its schema block at the bottom of the step 1 text, so a customer asking "why is there code with my article?" was seeing that old behaviour. In the same fix: a reviewer chosen at article creation now carries through to the ready screen with no second prompt, and the "Reviewed by" section renders on newly approved articles.)

A developer, if preferred. A shareable developer hand-off link carries everything a web developer needs.

Co-Kinetic Sites, our own web builder, is live (Tor, 2 October 2026). It is not a standalone product and cannot be bought on its own: it is an extension of the Clinical Content System for subscribing clinics, and Tor sets it up for a clinic that wants it. It integrates directly with the Clinical Content System: content flows straight from the plan to the published page, with nothing to copy, paste or configure, on a site built for AI visibility from the ground up. Do not offer to show other clinics' sites as examples.

Co-Kinetic Sites: what a clinic gets (Agent 15.2 and Agent 3.1, 7 Oct 2026).

• Set-up: no self-sign-up. Our team (Tor) connects the clinic from CCS and the site appears at .cokinetic.ai. Everything comes from what the clinic keeps in CCS: practice details, locations and hours, team, design choices and published content. The first site is a demo, hidden from Google on purpose; do not name it or offer clinic sites as examples.
• Pages: home, conditions, treatments, services, blog, team with a profile page per clinician, locations, contact, fees, first visit, FAQ, careers (optional) and legal pages. Menu: Conditions, Treatments, Your first visit, Fees, Team, About (Locations replaces About with two or more locations). Phone number on every page. The Contact page lists every location with its own address, phone and email. No enquiry forms and no booking engine: Book links to the clinic's booking page.
• Content: each published condition, treatment and service piece gets its own page; homepage and lists update themselves. Homepage "Getting started" steps come from the clinic's First Appointment page; the About page shows the full story.
• Design: built to our designer's reference pages; an automatic check blocks any update that would move a page away from the design. Missing material (reviews, photos, founder quote) means the section is left out cleanly, never an empty box. In the Control Centre the clinic picks a theme, colours, font pairing and how pages look, then saves and publishes; the screen confirms "Your saved changes are live" (the earlier publish lock-up is fixed, #3591).
• Domains (live since 17 Sep): a clinic can connect its own domain; it is given the exact DNS records and each step is shown until live. After a domain is disconnected, the old address redirects for 30 days.
• Reviews: only from a connected review source, never typed in. Off, overall rating, or individual quotes (quotes UK only). A rating shows only from 20 reviews averaging 4.0 or more. Review stars are not added to Google's data, by our choice. Switching reviews off in CCS hides everything that comes from a patient review on the clinic's website (score, count, stars, quote, author, Google attribution, date), including on the homepage, and location pages no longer link to the practice's Google review page (live 22 Sep).
• What clinics can't do: no page editor, no login to the site, no forms, scripts or own code. Everything is changed through CCS.
• NOT YET LIVE (website side ready, CCS screen not shipped; do not say "you can set this"): special opening hours (CCS saves them but no site shows them yet; weekly hours do show), homepage picture, per-page pictures, own homepage search title and description, call-to-action band, footer links to sister sites, support staff row, "Use the default" resets, the fuller preview. Timetables, announcements and vacancies will come through the Growth Hub content widget (not yet live).

Co-Kinetic Sites: what happens automatically (live from late Aug 2026). For clinics on a Co-Kinetic Sites website, three things that other platforms need steps for are simply automatic:

• Structured data (schema) is emitted on every page type: clinic, condition, article, and clinician profile with credentials. Sites customers never paste schema anywhere; the "put it on your website" schema step does not apply to them. Support note: self-rating star schema is deliberately NOT emitted, because Google disallows it (deployed 27–30 Aug 2026).
• "Reviewed by [clinician]" appears automatically on every condition, treatment, service and blog page once the article's peer review is approved in CCS. If a page shows no reviewer line, the review isn't approved yet: there is nothing to configure (#2813/#2826, deployed 28–30 Aug 2026).
• Pages link themselves: each page carries automatic "related" links to the practice's other CCS pages (conditions ↔ treatments ↔ services ↔ articles), derived from stored relationships and shared topics. No customer action; a page with nothing related simply shows no related rail (#2755/#2775/#2779, deployed 27 Aug 2026).

Closing the loop on the live URL. The platform needs to know where a piece went live (see why below). WordPress publishes report it automatically. For copy-paste routes: the moment a customer copies an article, a card asks "where did it go live?"; a straggler nudge follows later if unanswered; and, most elegantly, the periodic re-measure auto-detects newly published pieces by matching the site's new pages against the clinic's written pieces, so even a customer who never tells us anything gets credited automatically.

The publishing check (live since 16 September 2026). Once a piece is published, Content Studio compares the article as written with the live page on the clinic's site, so the clinic can see if anything was lost on the way (a missing title, description or structured data, for example). Outstanding fixes appear as one list, largest gain first, with direct fix links. The format tabs are Formatted, HTML, Markdown and Page Data; Page Data holds the SEO title and meta description as separately copyable fields, alongside the structured data. The website handoff ends with a required live-URL step. One honest limitation: pieces written before mid-September have no stored score to compare against, so their comparison shows "Historical score unavailable"; the list of outstanding fixes still works for them.

Page Inventory (redesigned October 2026). Full description: state/page-inventory.md. Page Inventory reads every page on the clinic's website and checks each one against what Google and AI tools look for: a named, credentialed author, structured data, clear answers, page descriptions, freshness. What the clinic sees:

• A summary card, "What We Know About Your Content" (also on Overview and My Plan): pages found and measured, ranking coverage, average words, pages needing work (below 60), freshness, average quality, author attribution, schema completeness and the AI visibility score. Every figure has an ⓘ saying what it counts.
• One row per page: score (0 to 100); grade (A to F) for clinical pages only (conditions, treatments and services, blog), showing how well the page shows who wrote it and why to trust them; author; "We wrote → live" for pieces we wrote; words, dates, rank, schema; and a "To fix" list written as plain actions with the points each is worth. Filters by page type; sorts include To Do First, Most To fix and Biggest Drop After Publishing.
• "We wrote → live" shows what is lost when an article goes onto the clinic's site. The commonest gap is the structured data not being pasted in, usually a few minutes' fix. Content Studio shows the same comparison from the article side, with the same numbers.
• Honest numbers: a page we couldn't read says "not measured", never 0; listing, archive and tag pages are not counted as needing work; a date only in a page's hidden data is labelled as such.
• Every measurement is stored, so we can show clinics how their pages change over time.
• Never show or quote the checklist itself, criterion names, weights or a number of checks. If a figure moves because of how we count, say "we corrected how we count", never "your site got worse" or "your site improved".

The internal-linking flywheel

Every new article links to relevant other pages: drawn from two pools:

• Pool A: the clinic's existing site pages, known from the assessment crawl. Works from day one.
• Pool B: pieces the platform generated, once live. Each published piece becomes a linking target for every future piece.

This is why the live URL matters: each publication makes every subsequent article better-connected. Over months, the clinic's topic clusters become densely interlinked: the exact structural signal AI engines read as topical authority. The tenth article is worth more than the first, because it lands in a richer web. This compounding is the structural argument for the subscription: the platform's value per article increases with tenure.

Re-measurement

The Re-measure is a lighter, periodic re-run of the assessment: it reuses the stored site discovery, re-crawls the pages (catching new and changed content), refreshes all the score-driving inputs, page scores, AI-visibility probing against the fixed benchmark query set, reviews, search positioning, and writes a new dated snapshot alongside the old ones, never replacing them.

Each measurement is a dated snapshot. AI Visibility results (the 64 answers) are kept for each run; when a clinic's four patient problems are refreshed, a new baseline starts and earlier results are marked as measured on the previous questions. Page and Site Health scores are snapshots too: we cannot yet show an honest page-score history or before-and-after trend (Agent 6, 7 Oct 2026: the dated measurements are not yet carried through to the comparison). Do not promise score tracking, show a trend, or imply we can prove improvement.

Which assessments send an email (live 8 Oct). Only a clinic's first full assessment sends "Your Visibility Assessment is Ready" by email and text. Re-measures send nothing, unless our team ticks Notify the clinic for that run. The in-plan "material changes" notice is unchanged.

Re-measurement feeds the plan's evidence. A new assessment updates what the plan knows (Google positions, AI answers, page scores), but it does not rebuild the plan on its own; the plan uses the new evidence the next time it is refreshed. A change to the clinic's Practice Priorities or top-five services or conditions rebuilds the plan automatically about an hour later (at most once a day, no new research, started work kept; live 3 Oct). Other significant changes (clinicians, profiles, starring, Primary) mark the plan as due a refresh, and the Refresh Content Plan button rebuilds it. The plan reacts to reality, not to page loads.

What the customer experiences, end to end

Publish a piece (one click or guided paste) → the piece flips to Published and joins the linking pool → the next generated article links back to it → the cluster's health ticks up → the next re-measure registers the new pages, re-scores, re-probes AI → the score history gains a new data point → if enough moved, the plan offers to refresh with reasons. Repeat. The customer's dashboard tells the story in their own numbers: you published X, your score went from Y to Z, AI now cites you for these queries.

Common questions this briefing answers

• "I'm not on WordPress: do I get a worse experience?" Different, not worse: guided platform-specific routes preserve the full value (including the schema layer), with honest labelling where a platform imposes real limits.
• "Why do you keep asking where I published?" Because each live URL makes every future article better-connected, and if you forget, the next re-measure finds it automatically.
• "How do I know it's working?" Judge AI Visibility over several measurements on the same four patient problems, and look at the depth you have built in each topic. No timescales, no guarantees, and no promised trend.
• "What happens to my scores if things are re-measured with a newer algorithm?" Earlier results are kept and dated, but scores measured differently are not compared: each page shows the scoring version it was measured under, and the page-scoring rebuild on 21 Sep 2026 moved every clinic's page scores.