The panel is not locked yet — so it is not published yet.
Measured visibility is the dimension every buyer wants first, and it is the one that cannot be faked. It requires a prompt panel: a fixed set of category questions, locked at a baseline, re-run on a schedule so that a later reading is comparable with an earlier one. A panel that changes between runs makes every trend meaningless — which is why the panel is versioned and why extension sets never edit the locked one.
MindLeverX has not locked its own panel. No baseline run exists, so there is nothing to publish here and nothing to trend. When the panel is locked, this section will carry the panel itself — the prompts, the version, the collection window — because a benchmark whose inputs are secret is a claim rather than a measurement.
| Item | Reading | Unlocks when |
|---|---|---|
| Baseline prompt panel | NOT MEASURED | The panel is locked at a baseline version |
| Scheduled runs completed | NOT MEASURED | The monitoring runner is wired to the engine APIs |
| Engines covered | NOT MEASURED | First run completes against the locked panel |
Four dimensions. Two readings. No composite.
The proposed Methodology V1.0 reviews technical access, content quotability, off-site authority and measured visibility separately; no composite is calculated. Two of those four are properties of the artifact and can be read right now. The other two are properties of the world — how the wider web treats the brand, and what the engines actually answer — and neither was measured in the original 27 July 2026 review.
| Dimension | Status | Basis / unlock condition |
|---|---|---|
| Technical access | MEASURED (tool) | Read from the build artifact, 27 Jul 2026 — checks below |
| Content quotability | MEASURED (tool) | Read from the build artifact, 27 Jul 2026 — checks below |
| Off-site authority | NOT MEASURED | Unlocks when the site is live and off-site citations can be crawled |
| Measured visibility | NOT MEASURED | Unlocks when the panel is locked and the first run completes |
| Composite | NOT MEASURED | Requires a defined, validated model and sufficient comparable evidence |
What follows is the evidence underneath the two measured dimensions: the individual checks, each a real reading taken from the 6 pages of the build on 27 Jul 2026. They are published as counts rather than rolled into a dimension score, because the scorer that would weight them does not exist yet.
| Check | Reading | Note |
|---|---|---|
| Content readable without JavaScript | 6/6 | Every page's content is in the HTML; nothing waits on a script |
| Exactly one H1 per page | 6/6 | Document outline unambiguous for a parser |
| Heading levels skipped | 0 | No H2 → H4 jumps across the build |
| Unique, descriptive titles | 6/6 | No duplicate or templated titles |
| Meta description present | 6/6 | All over 50 characters |
| Structured data (JSON-LD) | 0/6 | Held in a separate fragment by build decision — a real gap, published as one |
| AI crawler policy stated | 13 agents | robots.txt names training and retrieval crawlers separately; no blanket disallow |
| llms.txt published | 2,731 bytes | Answer-first summary of what the practice is and does |
| Sitemap entries | 6 | Served pages only |
| Pages blocked from indexing | 0 | No noindex directives |
| Check | Reading | Note |
|---|---|---|
| Answer-first definition blocks | 2 | Self-contained paragraphs of 52 and 41 words — quotable with zero surrounding context |
| Definitional pillar pages | 1 | what-is-geo.html — the term the practice competes on |
| FAQ questions published | 5 | Question-shaped headings, each answered in place |
| Glossary terms published | 0 | The glossary is specified and not built — a real gap, published as one |
| External sources cited | 2 | Named, dated, third-party — excludes anything carrying a SAMPLE label |
NOT MEASURED, with the condition that unlocks it, is a stronger claim than a confident number nobody can check.
Nothing has moved yet, because there is no history.
Trends are derived from an append-only history of readings. This is the first reading, so there is no movement to report — no deltas, no arrows, no quarter-over-quarter. Publishing a change here would require a previous measurement to compare against, and none exists.
The first genuine movement this page can show is technical: the difference between an artifact on a disk and a site an engine can reach. That is a deployment, not an optimisation, and it will be labelled as one when it happens.
| Series | Readings held | First trend possible when |
|---|---|---|
| Technical access checks | 1 | A second reading is taken after deployment |
| Content quotability checks | 1 | A second reading is taken after the glossary ships |
| Citation rate · mention rate · share of voice | 0 | The locked panel completes its first scheduled run |
How these numbers were taken.
Deployment status was checked by DNS lookup of mindleverx.com on 27 Jul 2026; the result was no A record, which is why every other reading on this page is scoped to the build artifact rather than a live origin. The rendering check loaded each page twice in headless Chromium — once with JavaScript enabled and once disabled — and compared the text of the main content region; a page passes only if disabling scripts removes nothing. The remaining checks are direct inspection of the 6 HTML files and of robots.txt, llms.txt and sitemap.xml.
Dimension scores are deliberately absent. Methodology V1.0 identifies four review areas, but the scoring definitions, composite formula and validation remain unresolved. Assigning one by hand would be an invented number wearing a methodology's name. The methodology is defined here →
6 pages · read 27 JUL 2026 · headless Chromium render plus file inspection · scored against Methodology V1.0. Every figure on this page is MEASURED (tool) against the build artifact, or NOT MEASURED with its unlock condition stated. No SAMPLE or illustrative value appears in any table on this page. Readings taken from the artifact are never compared with readings that would come from a live domain or a panel run — those are different provenance and are not interchangeable.
- MindLeverX Methodology V1.0 — four proposed review areas; no implemented or validated composite. Defined in What is GEO?
- DNS lookup of mindleverx.com, 27 Jul 2026 — no A record. MEASURED (TOOL)
- Build artifact inspection, 27 Jul 2026 — 6 HTML pages plus robots.txt, llms.txt and sitemap.xml. MEASURED (TOOL)