The standalone entity-detail page surface. When users click into an entity from the Knowledge Panel or a SERP card, the system renders a structured page with facts, related entities, content sources, and interaction surfaces purpose-built for entity exploration.
Patent Overview
- Inventor
- Jeromy William Henry, others
- Assignee
- Google LLC
- Filed
- 2014-12-15
- Granted
- 2018-10-23
- Application Number
- US 14/571,036
The Challenge
The Challenge
The Knowledge Panel surfaces facts at a glance, but for entities the user wants to explore deeply, the panel is too small. The system needed a standalone page surface that scales the entity experience into a full structured destination, complementing rather than replacing both the panel and the document SERP.
- Panels Are Constrained By Size — The Knowledge Panel must coexist with the result list. Its space is limited. For entities users want to explore in depth, the panel cannot deliver the full picture.
- Document Search Is Not Entity-Centered — The result list returns documents about the entity. Users wanting structured entity exploration are forced to assemble facts across many documents themselves.
- Entity Exploration Needs Structured UI — An entity page needs structured sections: overview, attributes, related entities, content, social presence. Each section serves a different exploration need.
- Page Must Adapt To Entity Type — Person pages need biography sections; company pages need products and leadership; place pages need maps and reviews. The structure adapts to entity type.
- Page Must Update As Entity Evolves — Entities change over time: new attributes, new related entities, new content. The page must refresh continuously so it stays current with the entity's real-world state.
Innovation
How The System Works
The system constructs a standalone entity page from the knowledge graph record plus surfaced content, organizes it into type-appropriate sections, populates each section with selected facts and related items, renders the page as a destination accessible from search results, and refreshes it as the underlying entity data evolves.
- Fetch Full Entity Record — From the knowledge graph, pull the complete entity record including all attributes, relationships, time-sensitive facts, and content sources.
- Determine Entity Type Template — Entity type drives the page template: which sections to include, what order to display, which facts to prioritize per section.
- Compose Section Content — Per section, select content from the entity record. Overview gets description and image; attributes get key facts; related-entities get top connections; content gets articles, videos, social posts about the entity.
- Apply Authority Filters — Content surfaced on the page must come from authoritative sources. Filter out low-quality or spam content that mentions the entity but lacks authority.
- Compose Interaction Surfaces — Each section gets interaction affordances: expand for more, follow the entity, navigate to related entities, view source documents. Interactions support deep exploration.
- Render Page — Compose the page HTML or app view. Render across web, mobile web, and app surfaces with format-appropriate layout.
- Refresh Continuously — As the entity record updates (new facts, new content, new relationships), the page refreshes. The user always sees the current entity state.
Entity Page As Destination
The patent's load-bearing idea is to make the entity itself a destination surface, complementing rather than replacing the SERP and Knowledge Panel. Users who want to explore an entity get a purpose-built page.
Structured Entity Exploration
Document search returns documents; the panel surfaces facts; the entity page combines both into a structured destination focused on the entity itself.
- Knowledge Graph As Source — The entity record from the knowledge graph drives the page. Page content is structured because the source is structured.
- Type-Specific Sections — Each entity type has its own page template with appropriate sections. Person, place, organization, product. The structure adapts.
- Continuous Refresh — The page reflects current entity state. As the entity evolves in the knowledge graph, the page updates.
Technical Foundation
Technical Foundation
The patent specifies the entity record fetcher, the type-template store, the section composers, the authority filter, the interaction surfaces, and the rendering layer.
- Entity Record Fetcher — Knowledge graph store returns the full structured record per entity. Includes attributes, relationships, content sources, time-sensitive data.
- Type Template Store — Per entity type, template defines page sections, ordering, and per-section content rules. Templates are centrally maintained and versioned.
- Section Composers — Per section, composers select content from the entity record. Each section has its own logic: overview composer differs from related-entities composer.
- Authority Filter — Content surfaced on the page must clear authority thresholds. Source quality is enforced at composition time.
- Interaction Surfaces — Per section, defines interaction affordances: expand, follow, navigate, source. Interaction handlers route to deeper experiences.
- Multi-Surface Renderer — Renders web, mobile web, and app versions of the page. Layout adapts per surface; underlying content composition is shared.
The Process
The Process
The page composition runs when a user requests an entity page. Most work happens in the page-load path; some content (recent news, trending sections) refreshes more frequently than the full page.
- User Requests Entity Page — User clicks into an entity from the Knowledge Panel, a SERP card, or a direct URL. The page composition pipeline activates.
- Fetch Entity Record — Knowledge graph returns the structured record. Cache hits return quickly.
- Select Template — Entity type maps to template. Template defines page structure.
- Compose Sections — Per section, composer selects content. Authority filter excludes low-quality sources.
- Build Interaction Affordances — Per section, interaction handlers attach. Users can expand, follow, navigate, and source.
- Render Page — Multi-surface renderer produces the page HTML or app view. Layout adapts to viewport and surface.
- Log Engagement — Page interactions log per entity per user. Logs feed personalization and template refinement.
Quality Control
Quality Control
Wrong entity pages cost user trust. The patent specifies safeguards.
- Source Authority Filtering — Content on the page comes from authoritative sources. Low-authority content is excluded regardless of fit.
- Fact Provenance Tracking — Every displayed fact carries source provenance. Wrong facts can be traced and corrected at the source.
- Time-Sensitive Fact Validation — Hours, prices, schedules check for freshness. Stale facts are suppressed.
- Template Quality Audit — Per type, templates are audited periodically. Bad templates produce bad pages; quality monitoring catches drift.
- User Reports — Users can report wrong facts. Reports feed the knowledge graph quality pipeline.
Real-World Application
Entity information pages underpin the entity-detail surfaces across Google search products: dedicated entity pages, Knowledge Panel deep-dives, and the entity-card formats in voice and Assistant. The patent's primitives shape how Google presents entities as destinations.
- Type-templated Page Structure — Each entity type has its own template. Pages adapt to entity nature rather than using one universal layout.
- Authority-filtered Content Source — Surfaced content comes from authoritative sources. Quality is enforced at composition time.
- Multi-surface Rendering Coverage — Web, mobile web, and app versions all compose from the same content. Format adapts per surface.
Why Owning Entity Markup Matters
Pages that own canonical entity markup (Schema.org Person, Organization, Place) contribute the data that feeds entity pages. Strong markup investment compounds visibility on entity pages, not just SERP listings.
Why Entity Pages Reshape Brand Strategy
When users navigate to an entity page, they see a Google-controlled surface presenting facts about the entity. Brands have a strong interest in ensuring the facts presented are accurate, complete, and favorable. Investment in entity-data sourcing (Wikipedia, Wikidata, structured markup) becomes critical brand work.
<\/section>What This Means for SEO
What This Means for SEO
The patent builds a standalone entity destination page from the knowledge graph plus surfaced content, organized into type-appropriate sections. SEO implication: the entity itself becomes a Google-controlled destination, so owning accurate, well-marked entity data is critical brand work that influences what that page shows.
- Own Your Entity Markup — Pages with canonical entity markup (Schema.org Person, Organization, Place) contribute the data feeding entity pages. Strong markup investment compounds visibility on the entity page itself, not just standard SERP listings.
- The Entity Page Is A Google-Controlled Surface — When users navigate to an entity page, they see Google's presentation of facts about the entity. Brands have a strong interest in ensuring those facts are accurate, complete, and favorable, which makes entity-data sourcing core brand work.
- Sections Are Type-Appropriate — The page organizes into sections matching the entity type. Marking up the correct type ensures the relevant sections render with your data, so type accuracy shapes the structure of the destination page.
- Source Data Across The Web Matters — The page draws from the knowledge-graph record plus surfaced content, which is corroborated across sources like Wikipedia and Wikidata. Consistent, accurate entity data across authoritative sources is what populates the page favorably.
- Destination, Not Just A Card — The entity page complements the panel and SERP as a full exploration destination. For entities users explore deeply, ensuring rich, accurate related-content and fact coverage keeps that destination working in your favor.
- Data Freshness Keeps The Page Current — The page refreshes as underlying entity data evolves. Keeping your structured data and authoritative sources current ensures the entity page reflects your latest accurate facts rather than stale information.
- Related Entities Extend Reach — The page surfaces related entities and content sources. Being a recognized related entity to a prominent one earns presence on that entity's page, so building genuine entity relationships extends your discoverability.