RepositoryWebrefClusterProtoRuleInstance

Repository WebrefEntity Understanding

GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefClusterProtoRuleInstance

6
out of 10
Medium
SEO Impact
When we apply a rule to define a particular cluster, we have a RuleInstance. Some kinds of rules for clusters define more than one cluster. In those rules we say things like "for each entity X with this property, we create a cluster where..."; each particular cluster that we create is the result of an instance of that rule, where the argument X has been bound to a particular entity (note that this also applies to rules that define only one cluster; in that case, there are no arguments). An entity that is part of a cluster plays a "role" in such a cluster. This message describes such an instantiation of a rule with a role and with concrete values for the arguments.

SEO Analysis

AI Generated

Part of Google's entity understanding system (WebRef). This system identifies and links entities—people, places, things, concepts—within web content to Google's Knowledge Graph. Entity recognition is fundamental to semantic search, helping Google understand content meaning beyond keywords and match it to relevant queries.

Actionable Insights for SEOs

  • Build topical authority through comprehensive, entity-focused content
  • Implement structured data to help Google understand entities on your pages
  • Create content that clearly establishes entity relationships

Attributes

2
Sort:|Filter:
midListRepositoryWebrefClusterProtoMidListRuleInstance →
Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefClusterProtoMidListRuleInstance.t

Exactly one of these *RuleInstance fields needs to be present for clusters which have not been merged; it selects the specific kind of rule instance. For merged clusters both fields may be present.

relationRepositoryWebrefClusterProtoRelationRuleInstance →
Default: nilFull type: list(GoogleApi.ContentWarehouse.V1.Model.RepositoryWebrefClusterProtoRelationRuleInstance.t