Portfolio Entity Architecture: SERP Co-Occurrence

The starting observation: three separately-built glossary properties, on three different domains with three different implementations, were seen appearing in the same SERP for the same search. Two use the custom AS400 glossary architecture; the third was built differently, with heavier heading optimization and video.

What was tested was not a controlled build ... it was an observation of existing, independently-launched properties that share topical focus, deliberate internal linking, definition-oriented content, and consistent subject expertise, but differ in technical implementation.

The test asks whether structural differences in implementation prevent co-occurrence, or whether shared entity signals (topical relevance, internal linking, definitional content, consistent terminology) are sufficient on their own.

The hypothesis is falsifiable and worth replicating systematically: track how often independently-established properties from the same portfolio co-occur in SERPs for shared-subject queries, and whether structured data consistency across those properties correlates with co-occurrence frequency.

If the pattern holds across more query classes, the implication is that entity architecture distributed across a portfolio may be more durable, and cheaper to build, than fighting for single-domain rank against entrenched entities on any one property.