SEO Products I Felt Like Building (some more useful than others)
Thirteen products. Nine are live and running without me in the loop, and four are still being built, listed here anyway. Engagements are how you hire me and deliverables are what an engagement hands you. This collection is the third thing: the systems I built and operate myself, published here as evidence that the way I work is backed by software rather than by slides.
The Thirteen Products
The two flagships first, then ordered by how open they are, ending with the one nobody can use yet.
Live
SchemaCDN
Schema markup is slow, expensive and fragile to implement by hand. This serves it from the edge instead: one lightweight embed, rules and AI writing the markup, governance after launch. Flagship product Open LiveAuditBuilder
An audit written as prose cannot be worked. Every finding is stored as a structured record instead, which is what makes it sortable, exportable and comparable to the last one. Flagship product Open LivePageSpeed Sampler
PageSpeed Insights measures one URL. This finds your sitemap, samples up to a hundred URLs across collections, and scores mobile and desktop for the site as a whole. Product Open LiveWhyTho
Every element on a page is a decision nobody wrote down. Select one, on desktop or a phone, and record the reasoning against the element itself. Shared across an organization, tagged to people and teams, and driveable over an API. Product Open LiveClient Portal
Delivered work should not decay in an inbox. Each engagement gets one permanent address holding its links and files, and that archive belongs to the client, not to me. Product Open LiveOpen Graph
Share preview images built at request time from URL parameters and cached at the edge. One meta tag per page, no build step, and no image pipeline to maintain. Product Open LiveContext Cards
Define jargon inline for the readers who need it, without sending anyone away from the page. One script tag, and the terms explain themselves on hover. Product Open LivePage Share
Share buttons that track nobody. No third-party scripts, no cookies, and no network call of any kind until a visitor actually clicks one. Product Open Live1
Every figure in an SEO report is an observation, a model or a guess, and nothing on the screen says which. This keeps them apart: each number carries its source, its method and its confidence, and a correction supersedes the old one rather than erasing it. Product Open SoonAISurface
Rank tracking stopped answering the question. This asks five AI assistants a fixed query set, mostly without naming you, and records whether you were mentioned and cited. Product Open SoonGapFinder
A keyword gap is not a content gap. This compares you to competitors claim by claim, and shows the evidence behind every gap, so a finding can be checked rather than trusted. Product Open SoonAnalytics
Search Console and GA4 in one app, running the same repeatable analysis on every property it finds, and preferring the bulk export over the API wherever that export exists. Product Open SoonBrandWield
A small business describes itself from memory, once, into a prompt. This builds the record first: what is true, where it came from, what is missing, and what customers keep asking for that nobody sells them. Product OpenWhy These Exist
None of these started as a product. Each one started as a part of my own work that did not hold up, and the fix turned out to be software rather than discipline.
- Measuring one URL was never the question. Performance lives in templates, so the sampler measures across templates and averages, which is what PageSpeed Insights will not do for you.
- An audit written as prose cannot be worked. Storing the finding as a forty-field record is what makes an audit sortable, exportable, and comparable against the last one.
- The same analysis was being rebuilt every engagement. Building it once, against a repeatable framework, is worth more than building it well once per client.
- Rank tracking stopped answering the question. When the answer is one synthesised paragraph there is no position ten to climb to, so the thing worth measuring is whether you are named at all and whether what gets said about you is true.
- Nobody wrote down why the page is like that. A heading phrased for demand, a canonical pointing somewhere non obvious, a paragraph that reads awkwardly because it answers the real question. Reasoning kept in a separate document does not reach the person who is about to edit the element.
- Nobody could say how they knew. Estimates, observations and forecasts arrive in the same typeface, and the tool that printed them overwrites the answer next month, so a decision made six months ago cannot be defended or learned from.
- A keyword gap is not a content gap. Knowing a competitor ranks for a term does not tell you what they said, and the argument they made is the thing actually missing from your site.
- Delivered work should not decay in an inbox. A permanent client address turns the archive into the client's property instead of a retrieval request aimed at me.
- A business described from memory gets written about generically. The record has to exist before the writing starts, or the generator invents whatever the owner forgot to mention and nobody catches it.
Five of them, PageSpeed Sampler, AuditBuilder, AISurface, WhyTho and 1, are open to anybody. Three run for my clients. Three more, Open Graph, Context Cards and Page Share, are free and open source, and SchemaCDN is the one sold as a product in its own right. BrandWield is the thirteenth, and the only one not finished. All thirteen are described here at the same level of detail, including the parts that are deliberately missing.