WeboftrustLiveResultDocBoostData
WeboftrustRanking SignalGoogleApi.ContentWarehouse.V1.Model.WeboftrustLiveResultDocBoostData
SEO Analysis
AI GeneratedDirectly influences how pages are ranked in search results. These signals are part of Google's core ranking algorithm and affect page visibility. This model (Weboftrust Live Result Doc Boost Data) contains SEO-relevant attributes including boostLevel. Key functionality includes: Identifies the degree to which the existence of this LiveResult should boost a query's score (when the query is performed within the hot_times range)....
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
- Audit your site's quality signals to ensure alignment with Google's quality assessment criteria
- Focus on E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) improvements
Attributes
2boostLevelnumber(nilIdentifies the degree to which the existence of this LiveResult should boost a query's score (when the query is performed within the hot_times range). This field is always in the range [0,1]. A missing field, a value of 0, or a value outside the legal range indicates that no boosting is performed. A value of 1 indicates that the maximum level of boosting will be applied. This field will be updated from time to time based on CTR and other signals.
hotTimesWeboftrustTimeRange →nilFull type: GoogleApi.ContentWarehouse.V1.Model.WeboftrustTimeRange.tSpecifies the time range within which this LiveResult is relevant. Used for deciding whether the rank of the corresponding page should be boosted. For example, this range can be set to encompass a few days before and after a sports game to which the page refers. If this field is missing, no boosting is performed. Specifying that a page should always be boosted is not recommended, but can be accomplished by setting hot_times.start_unix_time=0 and hot_time.end_unix_time=0x7fffffff. Note that multiple time ranges can be implemented by adding several LiveResultDocBoostData messages to the LiveResultsDocAttachments proto. If overlapping time ranges are used, the proto containing the highest boost level will be used.