Case Study #3 - 460 Pages, 72 Hours, Zero Submissions
Home Crew USA went live on October 14, 2026 with 460 pages and nothing submitted to anyone. No Search Console verification, no IndexNow pings, no crawler invitations. Three days later a site:homecrewusa.com search returned 458 results and AI crawlers had already requested the site 1,199 times.
This is the third case study on this blog. Case study #1 covered the build of nonsenseo.com, an AI-first site that serves machines differently from people. Case study #2 tracked its first week in the wild. This one asks a different question: does the same outcome repeat on a brand new domain in a boring local services niche, run by the same people with the same rules?
Short answer: yes, faster, and with receipts anyone can check.
What launched
Home Crew USA is a junk removal and moving labor site for Los Angeles County cities. It shipped with 460 URLs: service pages per city, local content written for humans, a sitemap, robots.txt, and an llms.txt file for agents. The sitemap’s lastmod dates read 2026-10-14 on 322 URLs and 2026-10-15 on 138 more, which is another way of saying the pages are real and the dates are honest.
Nothing was submitted. The domain was pointed, the site deployed, and the crawlers showed up on their own.
Three days of traffic
The zone’s logs show 11,343 requests from October 14 through 16. AI crawlers accounted for 1,199 of them, 10.6 percent of all traffic, and they pulled 4.5 MB of content. Every one of those 1,199 requests was answered with a 2xx or 3xx. Not one 4xx, not one 5xx.
Who showed up
| Operator | Agent | Requests | Failed |
|---|---|---|---|
| Googlebot | 550 | 0 | |
| Anthropic | ClaudeBot | 523 | 0 |
| Amazon | Amazonbot | 103 | 0 |
| Apple | Applebot | 17 | 0 |
| Other | other AI agents | 6 | 0 |
ClaudeBot and Googlebot arrived in a near dead heat, 523 to 550. Those same two operators also lead on nonsenseo.com, which is starting to look like a pattern instead of a coincidence.
What they read first
The most requested path from AI agents was robots.txt, pulled 119 times. Then the sitemap index, 31 times. Then the homepage. After the paperwork, the crawlers went straight to work on city pages: moving labor in Irwindale and junk removal in San Dimas led with a dozen requests each. In total, AI hits touched 248 distinct paths in three days.
That order matters. Bots read robots.txt, follow it to the sitemap, and fan out from there. A site that ships a clean robots.txt and an honest sitemap on day one gets swept within 48 hours. The request curve says the same thing: 528 AI requests on day one, 544 on day two, then 127 on day three once the sweep was done and maintenance crawling took over.
Check it yourself
curl -s https://homecrewusa.com/sitemap-0.xml | grep -c "<loc>"
curl -s https://homecrewusa.com/sitemap-0.xml | grep -o "<lastmod>[^<]*</lastmod>" | sort | uniq -c
curl -s https://homecrewusa.com/llms.txt | head -20And the oldest receipt in the book: a site:homecrewusa.com search, which returned 458 results on launch day itself.
What we won’t tell you
How the 460 pages were generated. How the schema is layered. How AI retrievals get tracked and attributed. What the site costs to run and who pays for it. The engagement is the case study; the method stays in the kitchen.
Publishing numbers without the recipe is what makes the claim falsifiable. Anyone can count the sitemap, read the lastmod dates, and run the site search. If the numbers drift from this post, the post loses credibility, and that is exactly how it should work. Checkable claims, verified by crawlers, is the entire business model.
FAQ
Did you submit Home Crew USA to Google?
No. No Search Console, no IndexNow, no sitemap ping services. The site shipped with clean HTML, meta tags, robots.txt, and a sitemap, and Googlebot found it within a day.
Which AI crawlers came in the first three days?
Googlebot made 550 requests, ClaudeBot 523, Amazonbot 103, Applebot 17, and assorted other AI agents 6. All 1,199 succeeded with a 2xx or 3xx response.
How much of the traffic was AI?
1,199 of 11,343 requests between October 14 and 16, or 10.6 percent, on a domain that did not exist a week earlier.
How is this different from Case Study #1 and #2?
Those tracked nonsenseo.com, the blog you are reading now. This one tracks a different domain in a local services niche with no topical overlap, and the outcome shape is the same: fast indexing, immediate AI crawler attention, zero errors.
If you want a launch to look like this, that is the service.