Three Glossaries, One SERP: How a Thin Page Inside a Strong Entity Architecture Ranked
An IBM FlashSystem search turned up three glossary pages across three domains, one of them barely more than two blurbs and a CTA. The content depth didn't match the result, and that's what killed the glossary-schema theory.
Content depth across the three results wasn't remotely comparable, which undercuts a pure glossary-schema explanation.
What was measured.
The short version.
This is an active, open-ended case study. It documents an IBM FlashSystem SERP where three glossary pages tied to Krisada's work appeared together across as400ibmsystems.com, the flashsystem.as400system.com subdomain, and midlandinfosys.com. Content depth across the three pages was wildly inconsistent, which weakened the initial glossary-architecture theory and pointed toward entity architecture as the more likely explanation. The thin page has since been rebuilt as a live intervention, tracked separately as Entity Boot Camp.
What was the system?
The observation started with a routine IBM FlashSystem search. Three results connected to Krisada's own work appeared together: "IBM FlashSystem Glossary ... AS400 IBM Systems" at https://www.as400ibmsystems.com/glossary/ibm-flashsystem/, "FlashSystem Glossary ... AS400System" at https://flashsystem.as400system.com/glossary/flashsystem/, and "IBM FlashSystems Glossary ... Midland Information Systems" at https://www.midlandinfosys.com/about/glossary-of-ibm-iseries-hardware-terms/ibm-flashsystems. The first instinct was a glossary-architecture theory: maybe schema, maybe definition-oriented content, maybe something intrinsically glossary-related that Google rewards.
What changed?
The three implementations were compared directly. AS400IBMSystems.com's glossary entry had recently been substantially built out. The flashsystem.as400system.com entry was extremely thin at the time it was observed, two short blurbs and a CTA. The Midland Information Systems entry came from an older glossary and directory architecture that hasn't been actively optimized in years, and none of its content is unusually deep either. Comparing content depth across the three pages against a single-variable theory (glossary schema or format) was the test: if the theory held, depth and implementation should track with each other. They didn't.
What did the evidence show?
Content depth across the three results wasn't remotely comparable, which undercuts a pure glossary-schema explanation. The most interesting result turned out to be the weakest page: flashsystem.as400system.com/glossary/flashsystem/, a FlashSystem-specific subdomain, on an AS400-focused domain, with a FlashSystem glossary entry, sitting inside an increasingly interconnected IBM ecosystem. The page-level content was weak. The entity-level context around it, subdomain naming, domain topical focus, and the surrounding IBM/AS400 property network, was strong. The Midland result reinforces the same read from the opposite direction: an old, unmaintained implementation with thin directory content still surfaces for important IBM and AS400 categories, with nobody actively optimizing it.
What can be reused?
The revised working hypothesis is that entity architecture, not page-level content or glossary schema specifically, is the stronger explanation for why a thin page held a position in a competitive SERP. That doesn't establish causation from a single observation. The formerly thin flashsystem.as400system.com page has been substantially rebuilt (more content, semantic depth, structured data, internal links) under the name Entity Boot Camp, specifically to test whether combining that entity architecture with a genuinely strong document changes the outcome. Note: the control was contaminated before a baseline screenshot was taken, since the page was improved immediately after being noticed. Historical search and warehouse data are being used as the closest available baseline instead.
Keep Browsing the Case Library
Move from this evidence file back into the full proof system.