BellyUp! helps people find places to eat and things to do. BellyUp! America connects its city guides and topic websites.
Buy It Here helps shoppers find local stores through city guides and shopping-topic websites. Jacksonville is its first city.
See whether a growing website network is getting found. Compare Google results with search and AI crawler activity, using our own published projects and the data behind each reading.
BellyUp! helps people find places to eat and things to do. BellyUp! America connects its city guides and topic websites.
Buy It Here helps shoppers find local stores through city guides and shopping-topic websites. Jacksonville is its first city.
These tables refresh from the live Digital Karma Data Warehouse during AISymantix's existing nightly build. Each changed reading keeps a dated downloadable snapshot.
Latest Google source date: 2026-11-03
Latest certified crawler date: 2026-11-05
This comparison keeps the same older group of 57 hosts. New cities do not get added to that group when the network expands.
| Measurement | 2026-10-07 to 2026-10-20 | 2026-10-21 to 2026-11-03 | Change |
|---|---|---|---|
| Google impressions | 11,320 | 12,906 | +1,586 (+14%) |
| Google clicks | 61 | 101 | +40 (+65.6%) |
Search tables compare adjacent 14-day periods. Only page URLs matching their exact property host count. These are observed totals; missing host-day records remain unknown rather than becoming zeros.
| Measurement | 2026-10-23 to 2026-10-29 | 2026-10-30 to 2026-11-05 | Change |
|---|---|---|---|
| Search crawlers | 216,596 | 126,465 | -90,131 (-41.6%) |
| AI search crawlers | 5,675 | 5,034 | -641 (-11.3%) |
| Training crawlers | 6,596,456 | 946,192 | -5,650,264 (-85.7%) |
| User-requested retrieval | 363 | 260 | -103 (-28.4%) |
Crawler tables compare adjacent seven-day periods using certified successful-content counts. A source-wide certificate does not establish complete log coverage for every host. Missing observations stay unavailable. Post-launch partial periods are labelled and do not receive a percentage comparison.
This group keeps the eight launch properties separate from BellyUp!. The network launched November 4; Pets joined November 5. A full comparison waits for two post-launch windows.
| Measurement | Source ends before launch | Source ends before launch | Change |
|---|---|---|---|
| Google impressions | No data | No data | Not comparable |
| Google clicks | No data | No data | Not comparable |
Search tables compare adjacent 14-day periods. Only page URLs matching their exact property host count. These are observed totals; missing host-day records remain unknown rather than becoming zeros.
| Measurement | Source ends before launch | 2026-11-04 to 2026-11-05 (Partial since launch) | Change |
|---|---|---|---|
| Search crawlers | No data | 1 | Not comparable |
| AI search crawlers | No data | 0 | Not comparable |
| Training crawlers | No data | 214 | Not comparable |
| User-requested retrieval | No data | 0 | Not comparable |
Crawler tables compare adjacent seven-day periods using certified successful-content counts. A source-wide certificate does not establish complete log coverage for every host. Missing observations stay unavailable. Post-launch partial periods are labelled and do not receive a percentage comparison.
A theory about AI discovery should have somewhere to meet the results. We can follow our own websites from publication to the crawler requests and Google appearances recorded afterward.
That is AISymantix's role in this series. RealSEOLife documents the work. Digital Karma Web explains the protocol checks. Here we keep the measurements open to inspection.
Our own search visibility case study applies the same idea to this website. A checker score stays separate from what the search and request records actually show.
The latest imported Google date anchors two adjacent 14-day periods. Page URLs must match the property hostname, so a parent property and a topic property cannot both count the same page here.
The BellyUp! group preserves the 57 active hosts registered in the warehouse before October 7. Registration is a repeatable selection rule, not a claim about launch date.
Buy It Here preserves the national site and seven Jacksonville properties from its launch baseline. Its table does not turn dates before launch into zeros, and a launch-period total cannot become a full-window comparison.
The export requires all source dates before replacing the previous reading. Within those dates, a missing host-day record remains unknown.
These are successful content requests under the warehouse's current reporting rules. They require an eligible crawler classification, a GET request and a successful HTTP response to a content-like route.
Those are reporting groups, not verified intent for each request. A successful request is not an AI citation or a human visit.
The crawler source date can differ from the Google date. The tables show their own dates; they are not a same-day correlation test.
Our working theory is that clear, connected content gives search and AI crawlers more opportunities to find relevant pages. We want to learn whether that discovery is followed by broader search exposure and meaningful reader actions.
Sustained AI-search discovery alongside later Google exposure would support further testing. Repeated crawler growth with flat or falling search exposure would challenge the simple leading-indicator story.
These tables are the first layer of that test. A crawler count alone cannot establish how many distinct canonical pages were reached, so page-level coverage and saved AI citations need their own checks.
Both networks use Digital Karma. Neither is a protocol-off control, and these observations cannot assign a percentage of growth to v8.2.
The October 31 BellyUp! filter repair is an important annotation. Closing a crawl loop can lower training requests while reducing wasted work; raw volume is not the target.
The nightly refresh reads the warehouse and publishes this site's tracking JSON. It does not change the measured networks or their search records.
Each changed combination of source dates and measured values receives its own snapshot. Earlier readings are retained, including when later imports or classification repairs change a historical number.
The November 6 RealSEOLife reports keep their original comparison and launch baseline. This page carries the rolling observations alongside that dated history.
The next editorial checkpoint is planned for November 20. We will review the timing and the pages behind any change before describing it as a result.