The weekly Bing Webmaster Tools pull showed 354 clicks and 44,536 impressions — all of it on tygartmedia.com. Every niche subdomain sat at zero. Not low. Zero.
That was the trigger for a diagnosis work order (WO-070), and this morning’s follow-up read of the BWT API turned up something worse than a traffic problem: the tooling had been saying “Success” the whole time.
The twelve properties in question: the tygartmedia.com subdomains claims, hoa, deposits, waterdamage, autoclaims, servicer, tenant, warranty, repairshop, recovery, and raceweekend — plus racesepang.com. Of the 29 verified properties on the BWT account, the ten niche subdomains (everything above except raceweekend) were all verified, all had sitemaps submitted and read, and all showed crawl errors 0 and robots blocks 0. Clean health, zero traffic.
Three silent failure modes
1. Phantom sitemap reads. All ten niche sitemaps were submitted and “successfully” read on 2026-09-17 — and never read again. BWT kept 0 URLs for every one of them. Meanwhile the live sitemap files were ~1.2 KB of real XML with 11–12 URLs each, last modified 2026-09-17. BWT’s stored copy of the file was ~7 KB. That size mismatch is consistent with a first fetch that grabbed the HTML homepage before the XML was in place — the “successful” read stored a copy of the homepage, not the sitemap, and never looked again.
2. robots.txt served the homepage. Before this morning’s fix, /robots.txt on all 12 hosts returned the HTML homepage with HTTP 200. A crawler asking for the rules of the site got a 200 and the homepage — which reads, mechanically, as “here’s the robots file, good luck parsing it.” Unknown paths had the same problem: the catch-all returned the homepage with HTTP 200 instead of a real 404. No errors, no blocks, no discovery.
3. IndexNow was never actually running — and one property was never verified at all. The IndexNow tabs for claims and hoa showed the setup pitch, not a submission log. No IndexNow key was linked from any homepage. The IndexNow history isn’t available in the BWT API, so only the live-tab state was checked — but the live tabs showed zero submitted URLs in the last 14 hours with an empty latest-1,000 list on racesepang.com, and the submissions previously attributed to racesepang.com actually belonged to the niche subdomains.
Meanwhile raceweekend.tygartmedia.com was not among the 29 verified properties at all, and its live /sitemap.xml was serving the HTML homepage. It was never in the tool, so the tool never looked.
The snapshot at diagnosis
Indexed-page counts (2026-09-22 snapshot):
| Property | Indexed pages |
|---|---|
| claims.tygartmedia.com | 6 |
| hoa.tygartmedia.com | 0 |
| servicer.tygartmedia.com | 0 |
| waterdamage.tygartmedia.com | 1 |
| autoclaims.tygartmedia.com | 1 |
| repairshop.tygartmedia.com | 3 |
| tenant.tygartmedia.com | 4 |
| deposits.tygartmedia.com | 6 |
| warranty.tygartmedia.com | 6 |
| recovery.tygartmedia.com | 7 |
| raceweekend.tygartmedia.com | unverified in BWT |
| racesepang.com | 0 (sitemap parsed: 6 URLs, last read 9/21, matching the live file; crawl count 0) |
Tenant was the only subdomain with any impressions at all — 4 of them. racesepang.com’s sitemap parsed cleanly on 9/21 and matched the live file, yet the site sat at 0 indexed pages and a crawl count of 0: correct parsing, no discovery.
The fixes (executed 2026-09-22, ~08:00 PDT)
- SubmitFeed returned HTTP 200 on all 10 niche properties — sitemaps now read as Success with 11–12 live URLs (~2.2 KB).
- All 12 hosts plus www.racesepang.com were redeployed with a real robots.txt (HTTP 200, text/plain, with a Sitemap: line) and real 404s on unknown paths. The homepage-200 catch-all is gone.
- raceweekend.tygartmedia.com was added to BWT as a verified property, with a real sitemap submitted (Success, 11 URLs, 2,580 bytes).
- Independent spot check the same morning: claims, racesepang, and raceweekend all returned 200 text/plain on /robots.txt, 200 XML on /sitemap.xml, and a genuine 404 on a probe path. Matches the execution report.
Why it matters beyond Bing
Bing feeds a meaningful share of AI search answers. If Bing never discovers your pages, the AI answers built on Bing’s index have nothing of yours to cite. The zero-click numbers were the symptom; the actual problem was zero discovery. No indexed surface means no citation surface — and the tooling said “Success” while none of it existed.
Check your own properties
- In BWT, open each sitemap row and compare the stored file size and URL count against the live file. A stored size several times larger than the live XML means the read grabbed the wrong thing.
- Fetch /robots.txt directly. Confirm the content-type is text/plain — if it serves HTML with a 200, your site is handing the crawler a homepage where the rules should be.
- Fetch a nonsense path (e.g. /this-page-does-not-exist). It must return a real 404, not your homepage with a 200.
- Confirm every live hostname is a verified property in BWT. An unverified property is invisible to the tool.
- Open the IndexNow tab on a live property. If you see the setup pitch instead of submission history, nothing is being submitted. Confirm the key is linked from the homepage.
- Cross-check indexed pages against your sitemap URL count. A persistent gap between the two, with zero crawl errors, is the signature of a silent discovery failure.
Caveats
- The fixes landed around 08:00 PDT on 2026-09-22. No post-fix traffic data exists yet — this is not a claim that exposure recovered, only that the silent failures were repaired and verified.
- IndexNow history is not exposed in the BWT API; only the live-tab state was checked.
- This was our own operations diagnosis. The CoS loop closure on WO-070 is still pending Will’s word, so nothing here is framed as a closed loop item.
- The indexed-page counts are a 2026-09-22 snapshot, not a trend.