SocialCommonSegment

Social CommonInfrastructure

GoogleApi.ContentWarehouse.V1.Model.SocialCommonSegment

2
out of 10
Low
SEO Impact
Unwrap a decoded JSON object into its complex fields.

SEO Analysis

AI Generated

Backend infrastructure with indirect SEO impact. This model (Social Common Segment) contains 7 attributes that define its data structure. Key functionality includes: Formatting to be applied when rendering the Segment. For all segment types, this is the standard way of representing that the Segment should be render...

Actionable Insights for SEOs

  • Understanding this model helps SEOs grasp Google's internal data architecture

Attributes

7
Sort:|Filter:
formattingSocialCommonFormatting →
Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.SocialCommonFormatting.t

Formatting to be applied when rendering the Segment. For all segment types, this is the standard way of representing that the Segment should be rendered in bold, italics, etc.

hashtagDataSocialCommonHashtagData →
Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.SocialCommonHashtagData.t

For HASHTAG type:

linkDataSocialCommonLinkData →
Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.SocialCommonLinkData.t

Type-specific metadata. At most one of these should be populated, and the one that is populated should correspond to the type of the Segment. For LINK type:

searchLinkDataSocialCommonSearchLinkData →
Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.SocialCommonSearchLinkData.t

For SEARCH_LINK type:

textstring
Default: nilFull type: String.t

Text content of the Segment. As a general rule, this field should contain the actual text that should be rendered in the UI. Thus, for a hashtag, it should be "#Foo", and for a link, it should be the display text. Clients that do not understand a particular segment type may use this text, along with the Formatting info below, as a fallback for display. The field is not required -- if all relevant information is carried in other metadata fields and there is no need for a fallback, or it is not practical for a fallback to be provided for any other reason, the field may be left blank. A standard example would be a user reference being transmitted between server layers, where a gaia-ID representation may be sufficient and there is no need for a textual fallback. In such a case, it would be valid and useful - though not required - for servers to compute and populate a fallback on the serving path.

typestring
Default: nilFull type: String.t

Type of Segment.

userMentionDataSocialCommonUserMentionData →
Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.SocialCommonUserMentionData.t

For USER_MENTION type: