CodeCargo
A runtime security and compliance platform for CI/CD, and the first account this delivery process was ever run on. Eight weeks in, with the category vocabulary and the comparison layer built.
Client engaged 24 July 2026. Figures describe the scope of the programme, not its results. Read on for why there are no result numbers on this page yet.
Who they are
CodeCargo sells runtime security and compliance for CI/CD pipelines, to engineering and security leaders at companies that have to prove what ran, where it ran, and who approved it. Their buyers ask an assistant technical questions that have exact answers, which is a harder and more rewarding surface than a category where everything is opinion.
Where they started
A strong product in a category that had not settled on its own vocabulary. The brand name itself was written more than one way across the site, the documentation subdomain and the profiles, which is enough on its own to stop an engine treating them as one entity. The pricing and platform pages carried no machine-readable description of what was being sold. And the documentation subdomain, which is where the substance lived, had no robots.txt at all.
What has been built
Every item below is published and live on the client's site.
One name, everywhere
The canonical spelling enforced across the site, the schema, the bylines and the directory profiles, and Organization schema expanded with sameAs, address and founders. Unglamorous, and the single highest-leverage thing on the account.
The docs subdomain made crawlable on purpose
robots.txt published on the documentation subdomain, which is a separate deployment from the marketing site and had been quietly invisible.
An answer pillar
One deep page on runtime security and compliance for GitHub Actions, written to be the passage an engine lifts when someone asks the category question, plus a dedicated security and compliance page of its own.
Product schema where buyers decide
Offer and SoftwareApplication schema on pricing, and Service schema on the services page and every platform page, so the commercial pages describe themselves rather than needing to be inferred.
The comparison layer
A compare hub with a footer section pointing into it, comparison pages for every competitor CodeCargo had no constraint on, and alternatives and migration pages for Jenkins, GitLab CI and CircleCI, the three systems their buyers actually move off.
Glossary, FAQs and llms.txt
A category glossary, FAQ blocks with FAQPage schema on the commercial pages, and llms.txt. Plus a "how did you hear about us" field on the site forms, because attribution you did not capture is attribution you cannot report.
What we are not claiming yet
This account's tracked question set has changed between runs by more than our own comparability rule allows, so the run-to-run numbers are not two points on one series and we will not present them as one. Holding the question set still is the next thing to fix here, and it has to come before any number goes on this page.
We publish a case study when the work is real, not when the numbers flatter us, and we add the numbers when they survive our own comparability rule: two runs are only comparable if the question set barely moved between them. That rule costs us a headline on this page today. It is the same rule that stops us reporting a fake win to the client, which is worth more.
Scope figures read from the SourceRank AI delivery database, 18 September 2026. No customer of theirs is named anywhere on this page.
See the rest of the programme
All case studies
Two of our own properties with published numbers, and the client programmes still in flight.
See all ->See your own visibility gap
Get a real baseline across every answer engine before you decide what to do next.
Start a conversation ->