We're fixing our own search visibility in the open. Every finding, every change, and every traffic update is documented here — so you can run the same process on your business site.
Live experiment — started 22 May 2026Before any SEO work, this is what the custom analytics showed. The numbers are small enough that the problem is obvious: the site isn't being found. Not a conversion problem. A visibility problem.
Baseline data below is from the pre-upgrade period (95 days to 22 May 2026, manual analytics).
Diagnosis: traffic is essentially zero from search. The site had been live for months with almost no organic visibility. Google was either not crawling the main service pages, or wasn't ranking them at all. We needed to find out which — and fix it.
We ran a full technical SEO audit across the four main pages: homepage, Agentic Engineering, Automation, and the Websites demo. Here's what came back.
| Finding | Page(s) | Severity | Status |
|---|---|---|---|
| 3 service pages missing from sitemap.xml — Google may never crawl them | AE, Automation, Websites | Critical | Fixed |
| No H1 on flagship Agentic Engineering page | agentic-engineering.html | Critical | Fixed |
| Homepage title 63 chars, truncated in Google SERPs (limit: 60) | index.html | High | Fixed |
| Meta descriptions over 155 char limit on 3 pages (168, 174, 183 chars) | Homepage, AE, Automation | High | Fixed |
| Automation H1 ("Small, sharp automations…") contains no searchable keyword | automation.html | High | Fixed |
| Muted text contrast fails WCAG AA — rgba(241,241,241,0.4) on #000a1a = 3.3:1 (need 4.5:1) | Homepage (12 instances) | High | Fixed |
| harbour-demo.html has no canonical tag and no schema | harbour-demo.html | Medium | Fixed |
| Brand name inconsistency: "SolVX" / "SolvX" in schema and meta tags | Automation, Homepage schema | Medium | Fixed |
| Sitemap lastmod dates all showing 2026-02-15 (stale) | sitemap.xml | Medium | Fixed |
| Google Search Console not yet set up — no impression or ranking data | Whole site | High | Pending |
Nine issues fixed in a single session. These are table-stakes changes — Google won't rank pages it can't crawl, and it won't display truncated titles well. None of this creates traffic on its own, but without it, nothing else matters.
The sitemap only listed lab and utility pages. The three main revenue pages had never been submitted to Google. Fixed by adding all service pages with current lastmod dates.
The flagship page had no H1 at all — headings jumped straight to H2. Added a visually-hidden H1 so Google reads it without disrupting the visual design.
Low-opacity text (rgba(241,241,241,0.4)) on a near-black background blended to an effective grey that only achieved 3.3:1 contrast — below the 4.5:1 WCAG AA minimum. Raised opacity to 0.6–0.65 across 12 elements.
These technical fixes take 1–4 weeks for Google to re-crawl and process. The next update will include:
This is the same checklist we ran on solvX.uk. If you have a business website, run through these in order. Each one either passes or fails — no expertise needed.
We audit small business websites and fix the issues we find — same process as above, done for you. Free 15-min call to start.
Book a free call Back to solvXEvery change made to the site — and the reasoning behind it — logged here in chronological order.
Started tracking the site properly and ran the first full technical audit. The core problem was visibility: three service pages had never been added to sitemap.xml, meaning Google may never have crawled them. Also found a missing H1 on the flagship Agentic Engineering page, over-limit title and meta descriptions on multiple pages, and 12 instances of text failing WCAG AA contrast.
All 9 fixable issues were resolved in the same session. Google Search Console reconnection is pending — it was previously verified but fell out of use.
Everything documented on this page is reproducible. The same checklist, the same contrast formula, the same schema templates — packaged as a free, open-source skill for Claude Code. You install it once and it runs on any website project you point it at.
The whole process takes about 10 minutes to set up. After that, a full 10-step audit is one command.
Claude Code is a CLI that runs an AI agent alongside your code files. A subscription is required — a free tier exists but has limited usage. The Pro plan resets your usage every 5 hours.
The skill reads your actual files — not a URL, not a pasted snippet. If your site is in a folder on your computer or in a Git repo, you're ready. On managed hosting (Wix, Squarespace, etc.)? See the section below.
Install the CLI via npm (requires Node 18+):
Then start it and log in:
This opens a browser login flow. Sign in with your Anthropic account. Once authenticated, Claude Code is ready in any terminal session.
You'll also need the GitHub CLI — for installing the skill and (optionally) contributing improvements. Paste this into a Claude Code session to have it install it for your OS:
On Mac it uses Homebrew. On Windows, winget or the MSI installer. On Linux, apt or rpm. Claude Code detects your OS and handles it.
Skills live in a folder in your home directory and are available across every project. Open a Claude Code session and paste:
Or manually:
Open a Claude Code session in the folder containing your HTML files and type:
Or target specific pages:
Claude Code reads your files, runs all 10 checks, and outputs a findings report with severity levels and concrete fixes. To apply the fixes: "fix the critical and high issues" — it edits the files directly.
You don't have HTML files to audit — you have a locked platform. Claude Code can fix that. It mirrors your live site, rebuilds it as clean HTML/CSS, and creates a GitHub repository you own. Once that's done, you run the audit on the clean files and you're free to host anywhere.
Rebuilding a full site uses more of your 5-hour window than a normal audit — potentially half or more for a large site. It's a one-time cost. Once the repo exists, every future session costs a fraction of that. A site with 5 pages or fewer will use well under half a window.
Paste these prompts into a fresh Claude Code session, in order:
Benefits beyond the audit: you own the code, can host anywhere, can make any change directly, and have full version history in Git.
If the audit misses something on your site, finds a false positive, or you've improved a check — raise a pull request. The skill gets better with real-world use from real sites.
Every pull request must include before/after audit output from a real site showing the improvement. For contrast changes, include the computed ratios. Opinion-only PRs will be closed.
Ask Claude Code to handle the PR for you:
SKILL.md, CLAUDE.md contributor guide, README — all open source.
View on GitHubNo time or subscription? We can run the audit and apply the fixes — or rebuild your site from managed hosting into a proper repo you own.
Book a free 15-min call