BigTech Reseller IBM Exposure Campaign ... 18-Property Tracking

Fixed family comparison:

- August 15 through 21: 9,278 impressions, 60 clicks, weighted position 43.6, and 426 site-page combinations - August 22 through 28: 1,322 impressions, 1 click, weighted position 66.2, and 156 site-page combinations - Impression change: down 85.8 percent - Click change: down 98.3 percent - Indexed pages reported August 27: 683 - Manual actions: none - Security issues: none

Crawler measurement after the warehouse repair:

- Recognized Googlebot requests: 935 before, 979 after, up 4.7 percent - Successful Googlebot content requests: 819 before, 847 after, up 3.4 percent - Original September 3 receipt: 938 before, 984 after, up 4.9 percent

September 2 through 8 interim:

- Impressions: 705, down 92.4 percent from baseline - Clicks: 1 - Weighted average position: 61.6 - Pages with impressions: 73 - Recognized crawler requests: 3,430 versus 3,501 at baseline - Successful crawler content requests: 2,133 versus 2,691 at baseline - Successful Googlebot content requests: 460 versus 819 at baseline

Search visibility uses gsc_page_daily at page grain across the root and eleven child properties. The parent domain's page rows contain only www.as400system.com URLs, so the page-level family aggregate does not duplicate child-host rows. Query rows are not summed across parent and child properties because that grain can duplicate the same query metrics.

Crawler continuity uses good_bot_page_daily after the classification repair. Recognized requests and successful content requests are reported separately. The September 3 crawler count remains in the historical record, while the revised definition is used for current comparisons.

The scorecard keeps Google visibility, bot requests, successful content delivery, human use, and confirmed citations separate. The September 11 read is interim. The formal 30-day checkpoint remains September 21.

Status: active, no recovery claimed. Google visibility is lower than it was at the first post-update checkpoint. Recognized crawler activity remains close to baseline, but successful content delivery and successful Googlebot content requests are down. The architecture remains in place because the sites have distinct specialist roles. The numbers have not rewarded that decision yet.