Halo AI Services Start a project
Menu

Verified self-owned case study · 2026

Turning Halo’s own website from a liability into a working sales system.

Published 2026-07-29Updated 2026-08-01Published by Halo AI Services

This is a first-party before-and-after account of the commercial, content and engineering rebuild behind the site you are using. The source and public behaviour were measured; traffic, ranking, lead and revenue uplift are not claimed.

Brief a website rebuildInspect the proof standard
191 KB → 31 KBApproximate homepage HTML reduction
5,213 → 1,498Approximate main-content words
10Dedicated capability pages
Separate gateProduction canary status belongs in the operational receipt

The starting point

The site looked busy but failed basic commercial and technical tests.

  • The offer was buried in 5,213 visible homepage words.
  • Missing URLs returned the homepage with HTTP 200, creating soft 404s.
  • robots.txt returned HTML instead of crawler instructions.
  • The form could show a queued state even when no enquiry had been stored.
  • Security headers were absent from Worker-served HTML.
  • Ten real services were compressed into generic positioning.

Evidence boundary

A stronger release is not a fabricated growth story.

The comparison proves what changed in source, output and live behaviour. It does not prove more visitors, better rankings, more enquiries or higher revenue; those need a clean baseline and observation period.

What Halo delivered

Commercial clarity and the operating system behind it.

The rebuild treated copy, interface, content, data handling and release engineering as one buyer journey.

01 / Position

One legible proposition

Reframed Halo around three buyer jobs: improve what exists, build what is missing and connect what repeats.

02 / Expand

The full capability map

Created clear routes for websites, Apple apps, tools and interactive work, search, newsletters, commerce, receptionists, automation and intelligence.

03 / Protect

Honest capture and privacy

Implemented EU-jurisdiction storage, Turnstile abuse control, a stable receipt and explicit email/copy fallbacks. A real production canary belongs in the separate operational release receipt.

04 / Prove

Repeatable release checks

Added deterministic builds, route and schema validation, typed edge code, security headers, real 404s, canonical redirects and live read-back.

Measured release evidence

What can be checked directly.

  • 47 canonical marketing routes plus a real 404 page
  • 47 canonical sitemap routes and local references validated
  • 24 practical guides and 10 dedicated service pages
  • Shared CSS and JavaScript with enforced size ceilings and versioned URLs
  • Preserved product legal routes kept byte-identical
  • Preview, immutable deployment and canonical production checked separately

What comes next

Measurement starts after trustworthy capture.

Cookie-free first-party funnel signals and Cloudflare real-user performance measurement create a future baseline. Permissioned customer work will only become a case study when the relationship, measurement and limitations can be published honestly.

Read the data-handling notice

Ready when you are

Fix the leak—or build the missing piece.

Send an existing page or workflow for a free first look, or tell Halo what you want to create. You will get a specific next step, not a generic AI roadmap.

Audit what existsStart a new build