Futurum mechanicals

trial.futurumgroup.com · probed 2026-11-19 10:49 UTC · probe 1.0.3 · pack mechanicals@2026.09.0 · supersedes the 2026-09-24 readout

A guide for the team, not a public page. This audit is for the Futurum web team, the TFG and Polaris people, and analysts who want to see how the new site is built and where it stands. It is removed before launch.

The deterministic floor: 84 checks that are either correct or not, that nobody has to have an opinion about. This is the current readout for the new build, measured on trial.futurumgroup.com — what is shipped and working, and the one thing left. Every line carries its own evidence. Both sites were probed within seconds of each other.

84measurable mechanicals
a 2026 website needs
futurumgroup.com today
45
New build cutover day
78
45 → 7814 → 0 failing
A 2026 website has at least
84
measurable mechanicals that decide whether search engines, answer engines and AI agents can find it, quote it and use it.

The new build passes 78 of 84 by cutover, up from 45 today, with zero failures. Every check carries its own evidence.

45
working on
futurumgroup.com today
14 failing outright
→
78
working on the new build on cutover day: 71 today, plus 7 that switch on at cutover
0 failing
Show how the 84 are counted
futurumgroup.comlive today
45
9
14
4
12
New buildtrial.futurumgroup.com
71
7
6
0of all 84 mechanicals84
working held for cutover (analytics, pixels, Search Console, MCP registry listing) partial failing not applicable can't be verified (no access to WordPress source)
72vs84
A higher ceiling. A WordPress site can only be scored on the 72 checks anyone can run from its URL. The new build can be held to all 84: 12 more, because every surface (llms.txt, sitemaps, the MCP server, feeds, .well-known) is a generated route in its source code, so it can be proven rather than hoped. The new build passes all 12.
+26 mechanicals ahead today · +33 on cutover day · 14 → 0 failures · +12 checks only the new build can prove
Where all 84 stand on the new build
78 of the 78 that apply, on cutover day
71
7
6
71
Working today
59 public checks + all 12 repo checks. The live site's repo can't be scanned, so the comparison above counts its 12 as unverifiable.
7
Switch on at cutover, by decision
GA4 · Tag Manager · Google Ads · Reddit pixel · Meta pixel · Search Console · the public MCP registry listing (it must name futurumgroup.com, so it can't be listed from trial)
6
Not scored, and not gaps
  • 4 don't apply to this site: language variants (one language); OAuth login metadata (the MCP server is deliberately open); an alternative analytics tool (GA4 is the plan); www-vs-apex host (trial has no www host)
  • 1 this tool can't measure: a WebMCP hint (needs a real browser)
  • 1 optional, skipped: humans.txt
One of those 6 turns into a real check at cutover: www.futurumgroup.com must 301 to the apex, as the live site already does. It is on the README cutover checklist (PR #64), with the MCP registry listing.
The 72 public checks, check by check (hover a dot for its check id)

futurumgroup.com

T0 crawl & index
T1 answer-engine files
T2 agent & MCP
T3 on-page & citability
T4 measurement
T5 hygiene

New build

T0 crawl & index
T1 answer-engine files
T2 agent & MCP
T3 on-page & citability
T4 measurement
T5 hygiene

The 12 repo-side checks apply to the new build only, because the incumbent's source is not ours to scan. All 12 pass. The incumbent's GA4 and GTM show green because they are live there today.

12 of 13
the minimum bar · unchanged since 2026-09-24
The one unmet item is GA4, held for cutover. The incumbent futurumgroup.com meets 7 of 13.
Conformance
100%
the must-pass checks: 30.5 of 30.5 weighted · unchanged since 2026-09-24 · incumbent 75.8%
Adoption
9 of 11
optional extras: shipped, +2 partial · incumbent 4 of 11, +4 partial
Soft-404 host
No
a bogus path 404s
Open fails
0
and no conformance warnings · incumbent 8
Why the soft-404 check comes first
Seven of the eighteen hosts this probe has been run against answer HTTP 200 for paths that cannot exist, which makes every other reading on them fiction — robots.txt, llms.txt and sitemap.xml all “exist” because the CDN serves the homepage for any path. Trial is clean, so every number on this page is a real measurement.