Weekly Updates / September 13 to 19, 2026
The numbers got more honest, and the sites got more specific
The week across the Digital Karma portfolio: scanner traffic stopped impersonating people, twelve IBM properties stopped trying to answer the same question, and LymeOrg traded unsupported inventory for verifiable care resources.
Audio Summary
Listen to the Weekly Summary
This 4-minute-24-second AI-generated recording summarizes the measurement correction, IBM site specialization, LymeOrg cleanup, and new portfolio baselines.
Read by Kodi, AI co-architect
Read transcript
September 19th. This week, the biggest progress wasn't bigger numbers. It was more honest numbers and more specific websites. First, we discovered that some traffic we were calling human wasn't human at all. On B2BMedMarketing, more than 1,600 requests looked like people browsing the site. But when we followed the behavior, they came from just six IP addresses rapidly moving through pages. They were scanners pretending to look like normal browsers. So we changed the warehouse rules. That correction reclassified more than 3 million historical requests. The traffic didn't disappear. We simply stopped calling machines people. And that's important, because good measurement starts with telling the truth about what the numbers actually mean.
The second big story came from the AS400 and IBM Power properties. At first, falling impressions made consolidation look like the answer. But when we went back and studied the older data, we found something more interesting. Before the August Google disruption, these specialist sites were already developing their own search identities. Power 11 had its own audience. Power 12 had its own. FlashSystem searches were becoming model-specific, and the parent AS400 site was serving a broader purpose. So instead of retreating and combining everything, we doubled down on specialization. The main AS400 site received a System Identifier and Buyer Planner. Power 11 received a Configuration Validator. Power 12 received an Evidence Ledger. And the pricing site received an Upgrade Economics Simulator. Now we watch. The question isn't whether we built something interesting. The question is whether Google and real users begin recognizing each property for its own specific job.
The third story came from LymeOrg. We discovered ten provider listings containing information we couldn't properly verify. Some were already receiving Google impressions and crawler activity. We removed them anyway. Because visibility doesn't make bad information good information. LymeOrg is now being built around verified resources, official sources, and clear distinctions between institutions offering infectious disease services and individual doctors whose Lyme expertise has actually been verified. Georgia is already showing growing search interest. So we're going to develop it carefully, rather than filling the directory simply to make it look bigger.
Meanwhile, our neglected site rotation became a real operating system. Each site gets analyzed. We look at the evidence. We make an intervention. Then we measure what happens next. And importantly, we're not forcing every movement in the data to become a success story. Some properties improved. Some weakened. Some signals remain unclear. That's exactly why we're measuring them.
Several new properties also launched this week. BellyUpJax launched as a Jacksonville restaurant discovery system. Instant Read Visibility launched with a 37-signal website inspection engine. Digital Crayon Wisdom launched as an educational library. And BestLocalX launched its first Jacksonville local market visibility study. Those launches aren't victories yet. They're baselines. Now they have to earn discovery, traffic, and usefulness.
At publication, the portfolio contained 116 active public properties. Over the latest complete 28-day Search Console period, those properties generated about 231,000 Google impressions and 435 clicks. The warehouse also recorded more than 140,000 successful crawler content requests. But we're treating those numbers as a new baseline, not claiming portfolio growth, because our measurement methods improved during the week.
So the larger lesson this week is pretty simple. Don't make the numbers tell the story you want. Make the measurement better. Give each property a clear job. Build something genuinely useful around that job. And then watch what the search engines, AI systems, and people actually do. That's Digital Karma. Measure first. Learn from what happens. Then improve the system.
This week produced 159 work-log records across 45 primary domains. That is not 159 accomplishments. The records include follow-ups, corrections, investigations, and repeated implementation work, so this edition groups them into the few stories that changed what we know or what we did. Three mattered most: a traffic number became more honest, a group of IBM sites found distinct jobs, and a health directory chose verification over inventory.
First, make the people number honest
The largest correction this week started with a number labeled Human Page Requests. A launch-day spike on B2BMedMarketing looked like 1,652 human requests until the requests were traced back to six IP addresses moving across large numbers of pages with browser-style user agents. Krisada's own review traffic accounted for only 18 qualifying requests and had already been excluded. The big number was not an audience. It was an automated campaign wearing ordinary browser clothes.
The correction became a behavior-based scanner rule that stays inside each site, date, and IP address before it classifies anything. It reclassified 115,516 current-day rows and 3,313,020 historical rows across 36 days, then rebuilt the dependent Human Page Requests and Good Bots query caches. In the B2BMedMarketing check, all 1,664 requests from the six-IP campaign moved to scanner traffic and none remained in the non-scanner count.
That does not make the underlying requests disappear. It makes the label more accurate. Search crawlers, AI crawlers, scanners, and people can all request a page, but they do not represent the same thing. A useful dashboard has to preserve that difference before it starts telling a story.
The same standard changed another interpretation. Overall Google Performance impressions already included the impressions associated with AI-style queries, so a planned report trigger based on adding the two together would have counted the same visibility twice. The August 18 break still lines up with a Google spam update, but timing is not causation. Both corrections belong in the result because the first answer was weaker than the evidence.
Twelve IBM properties stopped trying to answer the same question
The first reading of the IBM Power data pointed toward centralization. Fourteen-day page impressions across the group had fallen from 4,897 to 1,345, and a single upgrade decision center looked like the cleanest response. That recommendation did not survive the next review.
The pre-August 18 evidence showed distinct intent already forming around the specialist properties. Power 11 had produced 1,659 impressions and 30 clicks across 16 active days. Power 12 opened with an average position of 8.93 over its first two days. FlashSystem was drawing exact model interest around 5075-A30 and 5078-A40. The parent directory was already the broad product entry point. Those were different jobs, not duplicate sites waiting to be merged.
The response was specialization. The parent site gained an AS400 System Identifier and Buyer Planner. Power 11 gained a Configuration Validator. Power 12 gained an Evidence Ledger. The pricing property gained an Upgrade Economics Simulator. Across the parent and eleven specialist properties, each evidence-led tool now asks a question appropriate to that property instead of repeating a generic comparison.
This is still an implementation result, not a ranking result. The next evidence is whether the new tools earn their own query ownership, impressions, clicks, and useful downstream actions without taking the same intent from one another.
Accuracy beat inventory at LymeOrg
A directory can look substantial while making its underlying problem worse. LymeOrg had ten public provider profiles with unsupported details, blank websites, and placeholder 555 telephone numbers. Seven of those pages had already collected 23 Google impressions, and the ten pages had received 136 successful crawler requests. Visibility did not make them reliable.
All ten profiles were removed. Their routes now return 404, the sitemap no longer advertises them, and the directory explains its verification standard instead of pretending the inventory is complete. The care navigation was rebuilt around official sources, an evaluation checklist, and a clearer distinction between a health system that offers infectious-disease services and a clinician whose Lyme experience has been independently verified.
The first two Georgia resources now follow that rule: Archbold Infectious Disease and SGMC Infectious Disease are presented as primary-source-checked institutional service records, not as endorsements or claims about a specific clinician. That distinction matters because Georgia is already showing an opportunity. The state page rose from 31 to 55 impressions while weighted position improved from 37.5 to 32.2, and the query family around Lyme disease support in Georgia grew from 28 to 56 property impressions while splitting across the state and support pages.
Those movements do not prove the new resources caused anything. They explain why Georgia deserves careful development and why unsupported profiles would have been the wrong shortcut.
The content rotation started behaving like a system
The neglected-site rotation moved from an idea into a weekday operating routine. More than a dozen sites went through an analyze-and-publish cycle, including BigTechReseller, AIHealthcareNow, AISymantix, DatasetsMaker, PharmDigitalMarketing, AItoAIWeb, AItoAIDatasets, AIMedicineToday, OlivesNAvocados, FineInkPrints, ArtDecorMarket, and LymeOrg. The point was not to manufacture a daily win. It was to keep evidence, intervention, and the next checkpoint attached to the same property.
The early results are exactly why that discipline matters. ArtDecor showed 54 query impressions in the current window compared with 40 in the prior comparison window, but its weekly sequence was 29, 13, 10, and 2. That is not a recovery. DatasetsMaker weakened from 1,296 first-half impressions to 707 in the second half. AIMedicineNow improved from 13,330 to 19,811 page impressions and from an average position of 61.85 to 55.59, yet its weekly impression totals still stepped down from 5,847 to 3,788.
The system gives us a repeatable way to act without forcing every chart into a success story. Machine Queries can help reveal information needs, but their provenance is not yet strong enough to treat them as proof that an AI system used or cited the site. They remain clues, not credit.
New properties launched with real jobs
Several new properties went live this week, but the meaningful part was not the domain count. BellyUpJax launched as a Jacksonville dining system with a central hub, five focused lenses, 20 verified venues, eight guides, and 108 live URLs. Closed or inaccurate venue records were rejected instead of padded into the directory.
Instant Read Visibility launched with a 37-signal inspection engine and a public dataset of 17 real readings. The free result explains the measured signals without using a paid remedy as the punchline. Digital Crayon Wisdom opened with 86 live URLs, including concept explanations, stories, glossary entries, FAQs, and activities that give the property a defined educational job.
BestLocalX added a Jacksonville roofing public visibility study built from a measured top-ten market and a reusable scoring method. These are launch baselines. Their value will be decided by what earns discovery, what people use, and whether the measurement stays honest after the first crawl.
2026-08-20 to 2026-09-16
The numbers at publication
At capture time, the latest complete Google Search Console date was September 16. Across the frozen cohort of 116 active public properties, the preceding 28 days recorded 231,277 Google impressions and 435 clicks, a click-through rate of 0.188 percent. Average position was 58.927, weighted by impressions. The same cohort recorded 140,354 successful crawler content requests under algorithm version 2: 57,019 search, 9,118 AI search, 69,990 training, and 4,227 user retrieval requests. These are dated baseline values, not a growth claim. The prior edition used 115 properties, a different overlapping date window, and crawler data that was later reclassified, so its totals are not a clean week-over-week comparison.
- Public properties in this snapshot
- 116
- Portfolio work-log records
- 159
- Google impressions
- 231,277
- Google clicks
- 435
- Click-through rate
- 0.19%
- Average position
- 58.9
This snapshot is saved with the edition. Work-log dates and search-data dates are shown separately; later dashboard updates do not rewrite this history.
What we are watching next
Watch Human Page Requests after the scanner reclassification. The exact checkpoint is whether new high-volume site-date-IP groups remain outside the human count without suppressing normal browsing patterns.
Track the IBM decision tools independently by landing page and query. The checkpoint is distinct impressions, clicks, and query ownership for the AS400 identifier, Power 11 validator, Power 12 ledger, and pricing simulator.
Give the LymeOrg Georgia page and its two institutional profiles a complete 28-day observation window. Watch impressions, clicks, weighted position, and whether Georgia support queries consolidate around the most useful landing page.
For BellyUpJax, Instant Read Visibility, Digital Crayon Wisdom, and the BestLocalX study, separate first crawls from real discovery. The next useful evidence is indexed landing-page visibility and a measurable reader or inquiry action.
Explore the work
- DataSetSEO: explore the public portfolio
- AS400System: identify the right system
- Power 11: configuration validator
- Power 12: evidence ledger
- AS400 pricing: upgrade economics simulator
- LymeOrg: provider directory
- LymeOrg: Georgia resources
- LymeOrg: how to evaluate a Lyme specialist
- LymeOrg: Archbold Infectious Disease
- LymeOrg: SGMC Infectious Disease
- Instant Read Visibility: public inspection
- BellyUpJax: Jacksonville dining discovery
- Digital Crayon Wisdom: educational library
- BestLocalX: Jacksonville roofing public visibility study
Dates, scope, and corrections
This edition covers Sunday, September 13 through Saturday, September 19. The frozen work-log snapshot starts after the previous edition's event cutoff and stops at event 801, the highest available event ID at capture time. The publication event itself is intentionally outside that cutoff.
The 159 work-log records have a broader scope than the public performance cohort. They include follow-ups, corrections, repeated deployment records, and work across 45 primary domains. The editorial sections group related records and do not treat the event count as a count of unique projects or successes.
Search totals come from GSC page data for August 20 through September 16. All 28 dates contain observations, and the snapshot found no duplicate page-days between properties in the selected cohort. That does not certify complete imports for every individual property.
The public cohort contains 116 active properties. The preceding edition contained 115, and the two 28-day windows overlap. The crawler classification also changed during this edition. For those reasons, this issue preserves a new baseline and does not claim week-over-week portfolio growth or decline.
Crawler totals count successful content-route requests under warehouse algorithm version 2, including repeat retrievals. The scanner correction was applied at the site-date-IP level and dependent caches were rebuilt. Crawler requests do not prove readership, indexing, citation, or ranking effects.
The narrative uses the full structured notes and later corrections for the selected events. The first recommendation to centralize the IBM Power sites was superseded after older search evidence showed separate intent. The association between the August 18 Google break and the spam update remains an inference, not a causal finding.
: First publication. The work-log cutoff, public cohort, Google Search Console metrics, and crawler totals are preserved as captured and are not replaced with later live values.
: Added a plain, portrait-free AI-generated audio summary and checked transcript. The article, work-log cutoff, and frozen performance snapshot were not revised.
: Changed the single-speaker presentation to the established Kodi card layout. The recording, transcript, article, work-log cutoff, and frozen performance snapshot were unchanged.