Knowledge Graph & Entity SEO

Brass-SEO draws on this as the primary source for Google's entity-first search philosophy. The 2012 announcement introduced the Knowledge Graph with 500 million entities and 3.5 billion facts, and articulated the shift from string matching to entity understanding — things, not strings. Google stated explicitly that its goal was to understand real-world entities and the relationships between them, not to match keywords. Every entity optimization recommendation Brass-SEO makes — structured entity pages, @id identifiers, Wikidata presence, sameAs cross-linking — traces back to this stated architecture. The things-not-strings model is now the design basis for both traditional and AI search entity resolution.

Examines:

Google's original Knowledge Graph announcement — the 500-million-entity launch, the 'things, not strings' entity philosophy, and the stated goal of understanding real-world relationships.

Brass-SEO draws on:

The 'things, not strings' entity philosophy — the conceptual foundation for Brass-SEO's entity SEO recommendations including Knowledge Panel optimization and schema @id usage.

Primary source

blog.google

Brass-SEO cites this when explaining why Wikidata presence benefits entity SEO. Vrandečić and Krötzsch describe Wikidata as a collaboratively maintained, language-independent structured data repository that serves as the shared knowledgebase for Wikipedia and is a primary data source for Google's Knowledge Graph entity identification. A brand, person, or organization with a correctly structured Wikidata item — complete with sourced claims and sameAs links — gains a direct signal path to Google's entity understanding system. Wikidata crossed 100 million data items in 2021 and is consumed by over 900 Wikimedia projects and countless third-party applications including major AI training datasets.

Examines:

Architecture and design of Wikidata — the open, machine-readable linked data repository that serves as a primary source for Google Knowledge Graph and Wikipedia infoboxes.

Brass-SEO draws on:

Wikidata's role as a Knowledge Graph data source — the factual basis for Brass-SEO's recommendation to establish a Wikidata presence for brand entity optimization.

Primary source

dl.acm.org/doi/10.1145/2629489

Brass-SEO uses this as the technical reference for how knowledge graphs function in search and AI retrieval contexts. Hogan et al.'s comprehensive survey defines the core data model (nodes, edges, and relation types), describes entity disambiguation methods, and covers how search engines use knowledge graphs to resolve ambiguous queries. The survey documents that entity linking — matching text mentions to knowledge graph entities — is a prerequisite for both search ranking and AI retrieval; pages that help the system identify their entities unambiguously benefit from both. The survey covers 50+ production knowledge graphs including Google's and provides the most comprehensive technical treatment available in academic literature.

Examines:

Comprehensive survey of knowledge graph research — data models, construction methods, entity linking, representation learning, and applications in search and question answering.

Brass-SEO draws on:

The entity disambiguation and entity linking concepts — the technical basis for Brass-SEO's @id and structured entity page recommendations in AI Citability analysis.

Primary source

dl.acm.org/doi/10.1145/3447772

Brass-SEO monitors this for Knowledge Panel claim and management guidance. Google's Knowledge Panel documentation explains that panels are generated automatically from data across Google's index, structured data on pages, and authoritative sources including Wikipedia and Wikidata. Verified entities can claim their panel to suggest edits, but claiming requires identity verification through an official social media account, news coverage, or established web presence. The claim process does not guarantee data changes — Google evaluates suggestions against its own authoritative source signals. Panels for organizations without sufficient third-party corroboration may not appear or may be automatically suppressed after claim.

Examines:

Google's official guide to Knowledge Panel generation, verification, claiming, and the process for suggesting edits to panel information.

Brass-SEO draws on:

The panel data sourcing and claim process — cited when Brass-SEO explains how entity optimization translates to Knowledge Panel visibility and what verification level is required.

Primary source

support.google.com/knowledgepanel

Brass-SEO treats this as the implementation reference for brand entity disambiguation. Google's Organization structured data documentation specifies required and recommended properties — including name, url, logo, contactPoint, and sameAs — with sameAs being the primary mechanism for connecting a page's entity to external authority sources such as Wikidata, Wikipedia, Crunchbase, and social profiles. A well-formed Organization entity with @id and sameAs values linking to multiple authoritative external profiles provides the entity signal chain Google needs to generate a Knowledge Panel. The specification defines which property values are required for Knowledge Panel eligibility versus which are optional rich result enhancements.

Examines:

Google's specification for Organization structured data — required and recommended properties, the sameAs mechanism for external authority linking, and rich result eligibility.

Brass-SEO draws on:

The sameAs property and @id entity chaining — the technical basis for Brass-SEO's entity disambiguation recommendations and AI Citability entity page guidance.

Primary source

developers.google.com/search/docs/appearance/structured-data/organization