We built a 10-city local network, 91 herbal guides and a public AI search dataset.

October 11 to October 17, 2026

This was a week of turning lists into systems people can actually use. BellyUp! became a ten-city network with sports, current bar deals and local creator pages. Natural Herb Library gained the missing middle between a condition and its herbs. Then four months of portfolio data became a case study anyone can inspect instead of a victory claim nobody can test.

BellyUp! became a ten-city network with sports, specials and local creators

Birmingham became the tenth BellyUp! city this week. Its hub and six focused sites opened with 252 venues, 31 neighborhoods and 18 guides.

Then Jacksonville stopped being the place where the new ideas lived alone. Sports & Game Day reached all ten cities through nine new sports sites. The Bars format reached all ten too, with 207 venues carrying a current happy hour or bar special from the venue's own pages.

The Local Creators and Down the Rabbit Hole pilot also moved from Jacksonville to the other nine cities. The network now has 63 creator profiles and one credited first story in every city. Creator videos, Instagram posts and real page pictures play on BellyUp! instead of sending the visitor away.

A person can now choose a game-day stop, find a real bar deal or meet someone documenting the city without leaving the local network. That is the change. Ten city lists became ten connected publishing systems.

Natural Herb Library can now connect a condition to a formula and pattern

Natural Herb Library already held 1,054 herb monographs and 140 condition indexes. It did not have the layer that answers the question a reader is really asking: which Chinese herbal formula fits this pattern?

The site now has 55 classic formula pages and 36 traditional Chinese medicine pattern pages. Every formula lists its ingredients and links each supported ingredient to the matching herb monograph. Each formula also has the same future product slug reserved on Supplements Apothecary.

The receding gums page is the first proof of the full system. It explains three different patterns and connects each one to a formula, daily care and signs that need professional attention. The site now moves from condition to pattern, formula and herb instead of stopping at a long ingredient library.

All 2,437 sitemap pages passed the rendered Dataset crawl. The next limit is clear too: the formula and pattern records still need qualified review before the library should present them as more than researched educational guidance.

Four months of AI search data became a public case study

AISymantix published a case study built from 35 days of server logs and four months of Google Search Console data. The article carries seven tables. Its full data file is public beside it.

The numbers did not produce a clean victory story. The dataset layer received about 21,700 requests across 190 sites. Seven AISymantix dataset pages earned 226 Google impressions and no clicks. The site's impression-weighted position moved from 88.2 to 30.4 while weekly clicks stayed between zero and two.

The raw AI crawler rise was left out of the result because BellyUp! filter pages dominated it. That choice matters. A large number is not useful when the mechanism behind it is a crawler walking combinations that no person asked for.

The case study gives us a dated measurement we can rerun. It also gives the reader the tables and JSON needed to challenge the conclusion. That is a better DataSetSEO asset than a polished claim with no receipt behind it.

The useful systems kept spreading

AIHealthcareNow connected its company news to the company directory. Ninety-three stories now create 806 links to 50 profiles. The directory reached 63 companies, while documented ownership research attached 22 older FDA records to the companies that own them today.

Midland published twelve Power 7 parent model pages with specifications, room planning and three researched parts panels on each page. Power 5, Power 9 and Power 11 sites also received new decision pages this week.

LeverageBuilder stopped describing a framework from a distance. It now has a working six-question assessment and six public portfolio cases that show the system being used.

BellyUp! Search Console setup caught up with the network. All 81 properties now have full service access and a confirmed sitemap submission. That does not create visibility by itself, but it gives the next comparison a complete place to start.

The public cohort grew from 127 properties to 205, so the baseline resets again

This issue freezes 205 active public properties. The previous edition froze 127. Seventy-eight properties joined the cohort and none left, so the rolling totals are a new baseline rather than a like-for-like performance change.

Google Search Console is fresh through October 14 and contains all 28 dates from September 17 through October 14. The cohort recorded 720 clicks and 172,917 impressions. Click-through rate is 0.416 percent because it is total clicks divided by total impressions. The impression-weighted average position is 40.701, where lower is better. The parent-child overlap check found zero duplicate page-days.

The separate server-request cache covers the same 28 dates under algorithm version 2. It recorded 10,687,641 successful requests to content routes. Training crawlers account for 10,315,474 of them. BellyUp! filter combinations dominate that total, so it is not a measure of readership or demand.

The editorial review covered all 262 optimization events after the prior cutoff and stopped at event 1915. The embedded snapshot contains 234 portfolio events dated October 11 through October 17 across 62 primary domains. Twenty-eight later records dated October 10 stayed in the candidate review but outside the dated weekly count.

The biggest number of the week was also the easiest one to misunderstand

Five crawler names made 1,455,629 query-string requests to BellyUp! lens sites on October 14. The server returned a successful page for 1,454,675 of them. Fifteen of seventeen plausible filter combinations showed no matching venue while still returning HTTP 200.

The selective three-filter cap reduced the depth of the crawl. It did not close the trap. No new preventive check passed this week, so this is a problem found again rather than a lesson learned. The next repair must stop publishing crawlable filter states and return a real not-found response when no venue matches.

Natural Herb Library also launched its formula system while robots.txt still told general crawlers to stay out of the public data folder. The block was removed and the portfolio audit passed. The release process did not change, so this was another mistake found again.

AINowGuide published a six-page sprint that worked technically but still borrowed Krisada.com's job instead of owning its own public build record. The review failed it and an identity reset is still waiting. A page can pass every build check and still fail the reason it exists.

This frozen baseline contains 205 active public properties, 78 more than the October 10 edition. Search Console is complete for September 17 through October 14 with 720 clicks and 172,917 impressions. Ratio-based click-through rate is 0.416 percent and impression-weighted average position is 40.701. The separately validated server-request cache covers the same 28 dates with 10,687,641 successful content requests, most of them training requests to BellyUp! filter combinations. The embedded snapshot records 234 portfolio events dated October 11 through October 17 and stops at event 1915.

Whether BellyUp! removes crawlable empty filter states and what seven complete post-fix days show by crawler.

Whether the ten-city creator pages earn corrections, claims or story submissions from the people they feature.

Whether qualified review changes any Natural Herb formula or pattern record before the first product pairing goes live.

Whether the AISymantix case study earns data-file use, Google clicks or repeatable AI citation results at the next reading.

Whether the 205-property cohort stays intact long enough for a clean comparison and whether the new BellyUp! properties begin reporting Search Console data.

Whether AINowGuide receives its own site identity before another technically complete sprint is published.