OPEN EXPERIMENT / UPDATED 13 SEPTEMBER 2026

This site is part of the experiment.

I’m using my own advisory website to test Market Distance: can evidence from real conversations lead to more useful pages and better business conversations?

This site was built and is updated with ChatGPT, and is published on ChatGPT Sites. I set the direction and remain responsible for what it says. The proposed next step is to bring RAMP Discovery signals into the workflow through a chatbot. That automated connection is not running yet.

What is connected today?

Website and publishing: Live. Changes are made through ChatGPT within the owner’s instructions.
Google Analytics 4: Configured with the owner’s measurement ID. Analytics loads after visitor consent. Receipt of events in Google Analytics has not yet been verified; no visitor or conversion results are published here.
Google Search Console: Verification meta tag installed. Ownership confirmation in Google Search Console is pending; indexing, search impressions and clicks have not been verified in the account.
RAMP Discovery → Market Distance: Planned integration. No automated discovery feed is connected to this site.
AI visibility: Not measured yet. There is no validated visibility score or live reporting feed.

How the pilot will work

Listen. Use relevant RAMP Discovery observations, retaining their sources and dates.
Propose. Identify a specific unanswered buyer question and a bounded website change.
Review and publish. Check the evidence, wording and page behavior before releasing the change.
Observe. Compare defined periods and record other explanations, including Google updates and changes in traffic sources.

The initial proposal is a monthly content review, with a check of incoming evidence every two weeks. A review may result in no change. Broken links, factual errors and access problems should be fixed promptly. This cadence is a pilot proposal, not an active automated schedule.

What I intend to publish

Search: Search Console impressions, clicks and CTR, with the page, date range and comparison period.
Site activity: aggregate GA4 visits and agreed conversion events, with consent and coverage limitations. A booking-link click is not a completed meeting.
AI visibility: observed mentions and citations across a documented set of prompts, providers, languages and dates. Repeated checks will show variation; a sample is not total market visibility.
Change history: the question behind each change, what shipped, and what the available evidence does or does not support.

Public reports will use aggregate results. Visitor identities, client conversations and private source material will not be published. Missing measurements will stay marked as unavailable, never as zero. Positive, negative and inconclusive outcomes all belong in the record.

Change log

13 September 2026 — Establishing the pilot

The homepage was shortened, shared navigation improved and image files compressed. This experiment page now states the current connection status and proposed measurement approach.

Outcome: the changes are published. Their effect on search visibility, enquiries and real visitor loading speed has not been established. Earlier speed tests are not post-change results.

What this can prove

One site can demonstrate whether the workflow is useful and measurable. It cannot establish that the same approach works for every business, or that any traffic change was caused by our edits. A domain migration would be logged as a separate major change.

Read about Market Distance, the RAMP discovery foundation and the execution approach. Follow this page for published updates.