IndexingDocjoinerServingTimeClusterId

Indexing DocjoinerIndexing

GoogleApi.ContentWarehouse.V1.Model.IndexingDocjoinerServingTimeClusterId

9
out of 10
Critical
SEO Impact
The serving cluster id metadata. Why we cluster the documents. The default value is UNKNOWN. Serving-Side Clustering is used for pages which represent the same content but are not identical (e.g. translated pages, or paginated content). Those documents are not dup-clustered in Alexandria so that all documents (and their tokens) are available to search queries. However, those documents are assigned the same Serving-Time-Cluster-ID (on the same reasontype), which during serving guarantees that only one of them is shown to the user.

SEO Analysis

AI Generated

Controls how pages are indexed. Without proper indexing, pages cannot appear in search results at all. This model (Indexing Docjoiner Serving Time Cluster Id) contains 3 attributes that define its data structure. Key functionality includes: The unique id to distinguish members in cluster. It could be generated in different ways according to reason, e.g. LINK_REL_NEXT_PREVIOUS: it is the f...

Actionable Insights for SEOs

  • Monitor for changes in rankings that may correlate with updates to this system
  • Consider how your content strategy aligns with what this signal evaluates
  • Optimize crawl budget by fixing broken links and reducing redirect chains
  • Use robots.txt and sitemap.xml effectively to guide crawling
  • Monitor Google Search Console for crawl errors and indexing issues

Attributes

3
Sort:|Filter:
clusterIdstring
Default: nilFull type: String.t

The unique id to distinguish members in cluster. It could be generated in different ways according to reason, e.g. LINK_REL_NEXT_PREVIOUS: it is the fingerprint of the URL of index 0; PAGE_PARAMETER_INFO: it is the fingerprint of pagination pattern (pagination_pattern_fp field in PageParamInfo message).

indexForDebugginginteger(
Default: nil

The member index of this document in cluster. Starts from "0". Note that indices of pages in a cluster may not be consistent with each other, because we may update them at different points in time. Currently only used for debugging.

reasonstring
Default: nilFull type: String.t

The reason why this document is clustered into this cluster.