Cruitfly
A nationwide construction and industrial staffing agency, seven weeks in, with the on-site structure finished and the content layer built. This is what was actually shipped, before the visibility numbers are worth publishing.
Client engaged 31 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
Cruitfly places skilled trades on construction and industrial sites across the United States, run out of hubs in Indianapolis and Charlotte. Their buyers are project managers and superintendents who need certified people on site in days, in trades where the supply is genuinely scarce: asbestos abatement, demolition, scaffolding, insulation, environmental remediation.
Where they started
The site was much larger than it looked, and most of the size was working against them. Around fifty near-identical state landing pages competed with each other for the same queries. There was no canonical tag anywhere. No structured data described what the company was, where its offices were, or what it sold, so an answer engine reading the site had to infer all of it from prose. The proof the sales team used every day, real projects with real outcomes, existed only in a shared document.
What has been built
Every item below is published and live on the client's site.
The entity spine
Organization schema with a verified sameAs set, plus a single extractable definition of the company that every other page now agrees with. This is the piece everything else hangs off: an engine that cannot resolve who you are will not name you.
Local structure for both offices
LocalBusiness schema for Indianapolis and Charlotte, and a name, address and phone format normalised to match across the site and the directory profiles. Staffing is bought locally even when the agency is national.
Schema across the whole site
Service schema on the services and industries pages, FAQPage on the FAQ page and then on every service page, BlogPosting on the post template, BreadcrumbList sitewide, WebSite with SearchAction, and llms.txt.
The content an engine can answer from
A construction staffing buying guide, a category glossary, a page on what actually drives price, head-to-head comparison pages against the competitors Cruitfly cleared, and a best-agencies roundup for the category.
Six case study pages plus a hub
Built from projects Cruitfly's own team documented. No customer is named on any of them, at Cruitfly's request and for their own competitive reasons, and the pages work anyway.
The unglamorous half
Forty-eight state pages stopped competing with each other and canonical tags went in sitewide. Six defect classes across forty-nine state pages were fixed. Five empty subheadings, two blog posts missing cover images and three unstyled tables were cleaned up. None of it is interesting and all of it was load-bearing.
What we are not claiming yet
Citation share on this account has moved. Mention rate, which is the number that actually matters to them, has not moved outside the range it was already bouncing around in before we started. Seven weeks is early for off-site authority to compound, and we would rather say that here than publish a percentage that a careful reader could take apart.
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 ->