Google Ranking Factors Leaked: 2700+ Secret Algorithm Details Revealed

Google’s algorithms are supposed to be a company secret. Until recently, Google has only provided glimpses into its ranking factors, and often, marketers can only take their word for it.

Now, a code release of a Content Warehouse by the Yoshi-code-bot on Github, followed by the release of the API reference guide, has brought ranking factors to the forefront through a massive public leak.

While Google has not confirmed the legitimacy of the document’s source, SEO Vendor has meticulously analyzed the document and code, extracting over 2700 ranking factors from the Google API Reference (V.0.4.0 as of 5/29/2024).

Here’s what Google told Search Engine Land (Updated 6/2/2024):

“We would caution against making inaccurate assumptions about Search based on out-of-context, outdated, or incomplete information. We’ve shared extensive information about how Search works and the types of factors that our systems weigh, while also working to protect the integrity of our results from manipulation.”

The identity of the individual who released this document is said to be Erfan Azimi (Updated 6/2/2024). However, it appears to be an internal document.

The API, divided into various modules and attributes, has been consolidated into a more comprehensible format by our team.

For those seeking an overview of significant factors identified from the leak, Michael King, CEO of iPullRank, has provided a summary of these factors.

 

Key Insights from the Leak:

• While it is commonly believed that there are about 200-300 primary ranking factors that matter for most sites, our analysis reveals over 2700 factors. Each factor’s analysis helps us understand the complexity involved.
• It is uncertain if each of these factors directly influences rankings. Given Google’s extensive data usage, some factors might only serve as metadata or structural information to aid in data classification.
• The weight of each ranking factor is still unknown. For this, existing SEO ranking analyses and previously known factors remain crucial.
• This revelation does not alter our fundamental understanding of SEO. Many factors corroborate what we already know about ranking mechanisms, thereby reinforcing current SEO practices.

Detailed Analysis of Ranking Factors:

To help understand and utilize these ranking factors, we’ve broken down each factor as follows:

[Title] (Attribute Name)

• Description: A brief explanation of what the attribute does.
• SEO Purpose: The role this attribute plays in search engine optimization.
• How to Use: Practical advice on how to leverage this attribute for better rankings.

By reviewing each Attribute, we’ve developed a more intuitive [Title] to summarize it. Each description provides an understanding of the attribute’s function. The SEO purpose explains its significance in optimization, and the usage summary offers actionable insights for improving your site’s ranking.

Search Leak GPT

[Updated: 7/7/2024] We created a Custom GPT called Search Leak GPT to make it easy for you to research and mine ranking factors from Google’s Content Warehouse API. You can now use ChatGPT to reveal insights into these leaked factors, and use SEO Vendor’s extracted rankings attributes specifically for your website.

 

Google Ranking Attributes List

Warning: This list is VERY long! Use your web browser’s find tool (usually CTRL+F) to search for words or phrases.

1. Abuse Type (AbuseiamAbuseType)
   • Description: This ranking factor identifies and categorizes different types of abuse found in content, such as pornography, harassment, or violence. The attributes allow for a more granular distinction within broad categories, such as differentiating between nudity and graphic sexual content.
   • SEO Purpose: Helps ensure content compliance with Google’s policies, potentially affecting the visibility of content based on its adherence to community standards.
   • How to Use: Ensure that your content adheres to Google’s content policies and guidelines to avoid being categorized under abusive types, which could negatively impact your search ranking.
2. Age Restriction (AbuseiamAgeRestriction)
   • Description: This factor sets age restrictions on content, specifying the age range within which the content is deemed appropriate. It includes attributes for defining the minimum and maximum age for access.
   • SEO Purpose: Helps in age-appropriate content filtering, which can influence the audience reach and visibility of your content based on age demographics.
   • How to Use: Clearly mark and manage age-appropriate content to ensure it reaches the right audience and complies with Google’s age-related content policies.
3. Abuse Restriction (AbuseiamAndRestriction)
   • Description: This factor applies restrictions only if all specified conditions or criteria are met. It is used to enforce complex content rules where multiple criteria must be satisfied simultaneously.
   • SEO Purpose: Ensures content is restricted based on multiple factors, enhancing compliance with detailed content policies.
   • How to Use: Implement comprehensive compliance checks on your content to ensure it meets all required criteria for publication and ranking.
4. Client (AbuseiamClient)
   • Description: Refers to the Google product or subproduct that provides content for abuse classification. It helps in identifying the source of the content being analyzed.
   • SEO Purpose: Helps in tracking and managing content sources, which can be crucial for content quality and compliance management.
   • How to Use: Maintain clear records of content sources and ensure all content provided by different clients complies with Google’s guidelines.
5. Constant Restriction (AbuseiamConstantRestriction)
   • Description: A restriction that always applies or never applies, based on its type. It simplifies the application of absolute rules to content.
   • SEO Purpose: Enforces non-negotiable content rules, ensuring certain standards are always or never met, which can streamline content moderation.
   • How to Use: Use constant restrictions for non-negotiable content guidelines, ensuring they are strictly adhered to.
6. Content Restriction (AbuseiamContentRestriction)
   • Description: Defines restrictions related to content specifics, often used in age or geographic gating. Helps apply detailed content control measures.
   • SEO Purpose: Ensures content is appropriately restricted based on content-specific factors, enhancing compliance and user experience.
   • How to Use: Apply content restrictions to manage sensitive content visibility effectively, ensuring compliance with specific audience requirements.
7. Evaluation (AbuseiamEvaluation)
   • Description: Represents backend evaluations used to explain verdicts on content. It provides detailed reasons behind content decisions.
   • SEO Purpose: Provides transparency and clarity on why certain content is ranked or restricted, which can help in understanding and improving content compliance.
   • How to Use: Review evaluations to understand content verdicts and make necessary adjustments to improve compliance and ranking.
8. Geo Restriction (AbuseiamGeoRestriction)
   • Description: Represents regional restrictions applied to content. It understands region inclusion and applies the most specific rules for different regions.
   • SEO Purpose: Ensures content complies with regional laws and standards, which can affect content visibility and accessibility in different areas.
   • How to Use: Implement geo-restrictions to manage content availability based on regional regulations and audience preferences.
9. Geo Restriction Locale (AbuseiamGeoRestrictionLocale)
   • Description: Specifies the location where a restriction applies and the associated user restriction. It helps in fine-tuning content accessibility based on locale.
   • SEO Purpose: Enhances content targeting by applying location-specific restrictions, ensuring content relevance and compliance.
   • How to Use: Use geo restriction locales to tailor content accessibility and compliance based on specific geographical areas.
10. Hash Information (AbuseiamHash)
    • Description: Provides information about various hashes computed on a message, such as simhash and attachment hash, which helps in identifying and managing content uniqueness and duplicates.
    • SEO Purpose: Helps in identifying and managing duplicate content, which can affect content ranking and search performance.
    • How to Use: Utilize hash information to monitor and manage duplicate content effectively, ensuring unique and original content for better ranking.
11. Name Value Pair (AbuseiamNameValuePair)
    • Description: Represents pairs of names and values, including non-UTF8 values, used for various identification and categorization purposes.
    • SEO Purpose: Helps in structured data management and categorization, which can improve content indexing and search relevance.
    • How to Use: Implement name-value pairs to enhance data structure and categorization, improving content clarity and searchability.
12. Not Restriction (AbuseiamNotRestriction)
    • Description: Applies restrictions if the specified condition does not apply. It is used to enforce inverse rules on content.
    • SEO Purpose: Ensures certain content rules are applied only when specific conditions are not met, adding a layer of control in content moderation.
    • How to Use: Use not restrictions to enforce rules based on the absence of certain conditions, ensuring comprehensive content compliance.
13. Abuse Or Restriction (AbuseiamOrRestriction)
    • Description: Applies restrictions if any one of the specified conditions is met. It is used to enforce flexible content rules.
    • SEO Purpose: Allows for more flexible content restrictions, ensuring compliance when any of several conditions are met.
    • How to Use: Apply or restrictions to manage content based on multiple criteria, enhancing flexibility in content compliance.
14. Region Code (AbuseiamRegion)
    • Description: Uses CLDR region codes to denote regions affected by content verdicts. It helps in managing regional content compliance.
    • SEO Purpose: Enhances regional content management by clearly defining the affected areas, improving compliance and relevance.
    • How to Use: Implement region codes to specify and manage regional content restrictions, ensuring adherence to local regulations.
15. Special Restriction (AbuseiamSpecialRestriction)
    • Description: A standardized user restriction maintained via a central table. It provides a consistent way to apply common restrictions.
    • SEO Purpose: Ensures consistency in applying common content restrictions, improving compliance and standardization.
    • How to Use: Use special restrictions to apply standardized rules across content, ensuring uniform compliance.
16. Target (AbuseiamTarget)
    • Description: Represents the target of an abuse classification, identified by an ID and type. It helps in specifying the exact content being evaluated.
    • SEO Purpose: Enhances accuracy in content evaluation by clearly identifying the target content.
    • How to Use: Clearly identify and manage target content for abuse classification to ensure precise and effective content moderation.
17. User Notification (AbuseiamUserNotification)
    • Description: Configures notifications to users regarding content issues or restrictions. It helps in communicating important content decisions to users.
    • SEO Purpose: Improves transparency and user engagement by notifying users about content-related decisions.
    • How to Use: Implement user notifications to inform users about content status, enhancing communication and trust.
18. User Restriction (AbuseiamUserRestriction)
    • Description: Describes restrictions on where a verdict applies. It provides detailed guidelines for content application.
    • SEO Purpose: Ensures precise control over content distribution, enhancing compliance with specific restrictions.
    • How to Use: Apply user restrictions to manage content availability based on detailed guidelines, ensuring accurate compliance.
19. Verdict (AbuseiamVerdict)
    • Description: Represents the outcome of an abuse evaluation, providing a final decision on the content. It is used for enforcing content policies.
    • SEO Purpose: Provides a clear decision on content compliance, affecting content visibility and ranking.
    • How to Use: Review and implement verdicts to ensure content meets compliance standards and understand the reasoning behind content decisions.
20. Verdict Restriction (AbuseiamVerdictRestriction)
    • Description: Describes restrictions on where the verdict applies, providing context-specific guidelines for content decisions.
    • SEO Purpose: Enhances precision in content enforcement by defining where verdicts apply, ensuring relevant compliance.
    • How to Use: Apply verdict restrictions to manage content enforcement accurately, based on specific contexts and guidelines.
21. Verdict Restriction Context (AbuseiamVerdictRestrictionContext)
    • Description: Defines a context dimension where a verdict applies, offering detailed situational guidelines for content decisions.
    • SEO Purpose: Improves contextual relevance in content enforcement, ensuring decisions are applied accurately within specific contexts.
    • How to Use: Implement context-specific guidelines to manage content enforcement, ensuring decisions are contextually appropriate.
22. SORI ID (AdsShoppingReportingOffersSerializedSoriId)
    • Description: Represents the serialized form of a SORI ID used in indexing and reporting offers. It is crucial for managing shopping-related data.
    • SEO Purpose: Helps in accurate tracking and reporting of shopping offers, enhancing the management of e-commerce content.
    • How to Use: Use SORI IDs to manage and report shopping offers accurately, ensuring effective e-commerce content handling.
23. Anchor Information (Anchors)
    • Description: Provides detailed information about anchors used in content, including creation date, text, context, and source quality. It helps in understanding the linking structure and quality.
    • SEO Purpose: Enhances link analysis by providing detailed anchor information, improving content linking strategies and PageRank.
    • How to Use: Analyze and optimize anchor information to improve linking structure and enhance SEO performance.
24. Anchor Source (AnchorsAnchorSource)
    • Description: Attributes related to the source document of a link, providing context about the origin of anchors.
    • SEO Purpose: Helps in evaluating the quality and relevance of source documents, impacting the overall link value.
    • How to Use: Assess and optimize source document attributes to ensure high-quality link origins, enhancing SEO value.
25. Redundant Anchor Info (AnchorsRedundantAnchorInfo)
    • Description: Provides information about redundant anchors dropped during content processing, helping manage link quality and quantity.
    • SEO Purpose: Ensures link quality by managing and reducing redundant anchors, improving link profile effectiveness.
    • How to Use: Monitor and manage redundant anchors to maintain a clean and effective link profile, enhancing SEO outcomes.
26. Customer ID (AppsDynamiteCustomerId)
    • Description: Represents an obfuscated GSuite customer ID, used for managing and identifying customer-related data securely.
    • SEO Purpose: Ensures secure and accurate customer identification, crucial for personalized content and data management.
    • How to Use: Use customer IDs to manage and personalize content securely, enhancing user experience and data security.
27. Organization Info (AppsDynamiteSharedOrganizationInfo)
    • Description: Contains information about the entity or organization that owns or manages a piece of content or data. This could include details about the organization’s structure and ownership.
    • SEO Purpose: Understanding the organization behind content can help in assessing its credibility and relevance, influencing how search engines rank content associated with reputable organizations.
    • How to Use: Ensure your organization’s information is clear and accurate in all content. Highlight the authority and trustworthiness of your organization to improve search rankings.
28. Organization Consumer Info (AppsDynamiteSharedOrganizationInfoConsumerInfo)
    • Description: Used to differentiate between consumer and customer use cases in organization information. This attribute is intentionally empty and serves as a placeholder for disambiguation.
    • SEO Purpose: Helps in precisely categorizing and managing content for different user groups, ensuring appropriate handling of consumer and customer-related data.
    • How to Use: Ensure your data management systems can differentiate between consumer and customer data to maintain accurate and relevant content categorization.
29. Customer Info (AppsDynamiteSharedOrganizationInfoCustomerInfo)
    • Description: Contains customer-specific data, including customer ID, which is essential for managing customer-related content and interactions.
    • SEO Purpose: Helps in personalizing and targeting content for specific customers, enhancing user engagement and satisfaction.
    • How to Use: Utilize customer information to deliver personalized content and experiences, improving customer engagement and loyalty.
30. Segmented Membership Count (AppsDynamiteSharedSegmentedMembershipCount)
    • Description: Provides details on membership counts for different member types (HUMAN_USER, APP_USER, ROSTER_MEMBER) and their states (INVITED, JOINED).
    • SEO Purpose: Understanding the composition and engagement of your user base can help tailor content and marketing strategies to better serve different segments.
    • How to Use: Analyze membership data to optimize content and engagement strategies, focusing on the needs and behaviors of different user segments.
31. Segmented Membership Counts (AppsDynamiteSharedSegmentedMembershipCounts)
    • Description: Contains a list of segmented membership counts, providing detailed insights into the distribution and status of different member types.
    • SEO Purpose: Helps in understanding and optimizing the engagement and retention strategies by analyzing the detailed membership data.
    • How to Use: Leverage detailed membership counts to enhance user engagement initiatives and tailor content to specific user groups.
32. Destination Stream (AppsPeopleActivityBackendDestinationStream)
    • Description: Represents a collection of activities in various streams, such as profile streams, square streams, and comment streams. These streams can have specific business logic and can be indexed and retrieved based on their structure.
    • SEO Purpose: Facilitates better organization and retrieval of user activities across different platforms, enhancing content discoverability and relevance.
    • How to Use: Optimize content placement and retrieval by organizing user activities into relevant destination streams, improving content accessibility and user engagement.
33. User Engagements (AppsPeopleActivityStreamqualityDistillerEngagements)
    • Description: Stores the number of different types of user engagement actions, including abuse reports. Currently focused on abuse report engagements, but may expand to other types in the future.
    • SEO Purpose: Helps in tracking and analyzing user engagement metrics, providing insights into how users interact with your content.
    • How to Use: Monitor user engagement actions to understand user behavior and improve content strategies based on engagement metrics.
34. About Section (AppsPeopleOzExternalMergedpeopleapiAbout)
    • Description: Contains information about a person or entity, including content type, metadata, sanitized HTML value, and textual value. It provides a detailed overview of the subject.
    • SEO Purpose: Enhances profile completeness and provides search engines with comprehensive information about a person or entity, improving profile visibility and relevance.
    • How to Use: Ensure the about section is complete and accurate, with well-formatted content and metadata, to enhance profile visibility and search relevance.
35. Extended Data for About Me (AppsPeopleOzExternalMergedpeopleapiAboutMeExtendedData)
    • Description: Provides additional data for the About Me section, supporting enhanced profile information and customization.
    • SEO Purpose: Enriches user profiles with extended data, improving the depth and quality of information available to search engines.
    • How to Use: Add extended data to user profiles to provide more comprehensive information, improving profile completeness and search relevance.
36. Name Display Options (AppsPeopleOzExternalMergedpeopleapiAboutMeExtendedDataNameDisplayOptions)
    • Description: Defines options for displaying names, supporting various formatting and display preferences.
    • SEO Purpose: Ensures names are displayed consistently and accurately across different platforms, enhancing user recognition and profile accuracy.
    • How to Use: Configure name display options to ensure consistent and accurate name presentation, improving user experience and profile clarity.
37. Photo Comparison Data (AppsPeopleOzExternalMergedpeopleapiAboutMeExtendedDataPhotosCompareData)
    • Description: Contains data for comparing profile photos, including differences in color bands and resolution, and metadata for high and low-resolution images.
    • SEO Purpose: Ensures profile photos are of high quality and consistent, enhancing profile attractiveness and credibility.
    • How to Use: Regularly update and compare profile photos to maintain high quality and consistency, improving profile appearance and engagement.
38. Profile Editability (AppsPeopleOzExternalMergedpeopleapiAboutMeExtendedDataProfileEditability)
    • Description: Provides information about the editability of profile fields, including locked and editable states.
    • SEO Purpose: Manages and controls the editability of profile fields, ensuring data integrity and consistency.
    • How to Use: Implement profile editability settings to manage who can edit profile fields, maintaining data accuracy and integrity.
39. Profile Name Modification History (AppsPeopleOzExternalMergedpeopleapiAboutMeExtendedDataProfileNameModificationHistory)
    • Description: Tracks the history of name modifications, providing insights into changes and ensuring the accuracy of profile information.
    • SEO Purpose: Helps maintain accurate and up-to-date profile information by tracking name changes.
    • How to Use: Monitor and manage name modification history to ensure profile accuracy and integrity.
40. Account Email (AppsPeopleOzExternalMergedpeopleapiAccountEmail)
    • Description: Represents the email address associated with a Google account, used for communication and account management.
    • SEO Purpose: Ensures accurate and up-to-date contact information, improving account management and user communication.
    • How to Use: Keep account email information accurate and up-to-date to ensure effective communication and account management.
41. Additional Container Info (AppsPeopleOzExternalMergedpeopleapiAdditionalContainerInfo)
    • Description: Provides additional information about a container, intended to be replaced by DeviceContactInfo.
    • SEO Purpose: Enhances the information available for containers, supporting better data management and categorization.
    • How to Use: Use additional container info to enrich data management practices, ensuring comprehensive and accurate information.
42. Address (AppsPeopleOzExternalMergedpeopleapiAddress)
    • Description: Contains detailed address information, including country, locality, street address, postal code, and metadata. Supports various address types and formats.
    • SEO Purpose: Enhances profile information with accurate address details, improving location-based search relevance.
    • How to Use: Ensure address information is complete and accurate to enhance profile visibility and location-based relevance in searches.
43. Affinity (AppsPeopleOzExternalMergedpeopleapiAffinity)
    • Description: Represents the affinity or relationship strength between users, providing insights into social connections and interactions.
    • SEO Purpose: Enhances understanding of user relationships and social connections, influencing social search and recommendations.
    • How to Use: Analyze affinity data to improve social engagement strategies and personalize content based on user relationships.
44. Age Range Type (AppsPeopleOzExternalMergedpeopleapiAgeRangeType)
    • Description: Represents age range data for a person, providing insights into age demographics.
    • SEO Purpose: Supports age-based content targeting and personalization, enhancing relevance and user engagement.
    • How to Use: Use age range data to tailor content and marketing strategies to specific age groups, improving engagement and relevance.
45. App Unique Info (AppsPeopleOzExternalMergedpeopleapiAppUniqueInfo)
    • Description: Stores unique information needed for app action fulfillment, supporting specific app functionalities.
    • SEO Purpose: Enhances app functionality and user experience by providing unique information required for app actions.
    • How to Use: Integrate app unique info to support specific functionalities and improve overall user experience within the app.
46. Best Display Name (AppsPeopleOzExternalMergedpeopleapiBestDisplayName)
    • Description: Provides the best suggested name for a person based on available data, ensuring accurate and consistent name presentation.
    • SEO Purpose: Improves profile recognition and accuracy by suggesting the best display name.
    • How to Use: Use the best display name to ensure consistent and accurate name presentation across profiles and interactions.
47. Birthday (AppsPeopleOzExternalMergedpeopleapiBirthday)
    • Description: Represents a person’s birthday, with specific guidelines for use and restrictions on how it can be requested and displayed.
    • SEO Purpose: Enhances profile completeness and supports age-related content personalization and targeting.
    • How to Use: Ensure birthday information is accurate and compliant with guidelines to improve profile completeness and age-based targeting.
48. Birthday Age Disable Grace Period (AppsPeopleOzExternalMergedpeopleapiBirthdayAgeDisableGracePeriod)
    • Description: Indicates whether an account is in the grace period for age disabling, affecting the ability to change birthday information.
    • SEO Purpose: Manages age-related account settings and restrictions, ensuring compliance with age consent regulations.
    • How to Use: Monitor and manage accounts in the grace period to ensure compliance with age-related policies and regulations.
49. Manual Grace Period Info (AppsPeopleOzExternalMergedpeopleapiBirthdayAgeDisableGracePeriodManualGracePeriodInfo)
    • Description: Provides information for manually setting a user into the age disable grace period, including details forwarded to Gaia for disabling.
    • SEO Purpose: Enhances the management of age-related account settings, ensuring accurate and compliant handling of user age information.
    • How to Use: Use manual grace period info to manage age disable settings accurately, ensuring compliance with age consent regulations.
50. Bragging Rights (AppsPeopleOzExternalMergedpeopleapiBraggingRights)
    • Description: Contains information about a person’s bragging rights, including metadata and textual value, highlighting achievements or notable traits.
    • SEO Purpose: Enhances profile richness by showcasing notable achievements or traits, improving user engagement and profile appeal.
    • How to Use: Add bragging rights information to profiles to highlight achievements and enhance profile attractiveness.
51. Calendar (AppsPeopleOzExternalMergedpeopleapiCalendar)
    • Description: Provides a URL to a person’s calendar, facilitating access to scheduling and availability information.
    • SEO Purpose: Improves profile completeness by adding calendar information, enhancing the utility and accessibility of profiles.
    • How to Use: Ensure calendar URLs are accurate and up-to-date to improve scheduling and availability access for users.
52. Caller ID Extended Data (AppsPeopleOzExternalMergedpeopleapiCallerIdExtendedData)
    • Description: Contains extended data for caller ID, including the source of the caller ID information.
    • SEO Purpose: Enhances the accuracy and reliability of caller ID information, improving user trust and communication efficiency.
    • How to Use: Use extended caller ID data to ensure accurate and reliable caller identification, enhancing user trust in communications.
53. Caller ID Source (AppsPeopleOzExternalMergedpeopleapiCallerIdExtendedDataCallerIdSource)
    • Description: Indicates the data source used to populate caller ID results, providing context for caller identification.
    • SEO Purpose: Ensures transparency and accuracy in caller ID information, enhancing user trust and reliability of communications.
    • How to Use: Maintain accurate and transparent caller ID sources to ensure reliable caller identification and improve communication trust.
54. Certified Born Before (AppsPeopleOzExternalMergedpeopleapiCertifiedBornBefore)
    • Description: Provides information related to the certification of a user’s age by a domain administrator or authority.
    • SEO Purpose: Ensures compliance with age-related policies by verifying and certifying user ages.
    • How to Use: Implement age certification processes to ensure compliance with age-related regulations, enhancing trust and compliance.
55. Channel Data (AppsPeopleOzExternalMergedpeopleapiChannelData)
    • Description: Contains detailed information about a YouTube channel, including unique ID, comment count, description, playlist count, profile picture URL, subscriber count, title, and video count.
    • SEO Purpose: Enhances the visibility and attractiveness of YouTube channels by providing comprehensive channel information.
    • How to Use: Keep YouTube channel information accurate and up-to-date to improve channel visibility and user engagement.
56. Circle Membership (AppsPeopleOzExternalMergedpeopleapiCircleMembership)
    • Description: Represents a person’s membership in various circles, indicating social connections and group affiliations.
    • SEO Purpose: Enhances social profile information by showcasing group affiliations and social connections.
    • How to Use: Maintain accurate circle membership information to enhance social profile completeness and relevance.
57. Client Data (AppsPeopleOzExternalMergedpeopleapiClientData)
    • Description: Stores arbitrary client data based on the client’s needs, supporting various use cases and data management requirements.
    • SEO Purpose: Provides flexibility in data management, allowing for tailored data storage and usage based on client requirements.
    • How to Use: Utilize client data to support specific use cases and enhance data management practices, ensuring flexibility and relevance.
58. Communication Email (AppsPeopleOzExternalMergedpeopleapiCommunicationEmail)
    • Description: Represents an email address used for Google product communication with the user, ensuring accurate and reliable communication channels.
    • SEO Purpose: Enhances user communication by providing a reliable and accurate email address for product-related interactions.
    • How to Use: Keep communication email addresses accurate and up-to-date to ensure effective and reliable user communication.
59. Connection Reminder (AppsPeopleOzExternalMergedpeopleapiConnectionReminder)
    • Description: Provides settings and reminders for contact-level connection prompts, enhancing user engagement and interaction.
    • SEO Purpose: Improves user engagement by prompting connections and interactions based on contact-level settings.
    • How to Use: Implement connection reminders to encourage user interactions and enhance engagement.
60. Contact Create Context Info (AppsPeopleOzExternalMergedpeopleapiContactCreateContextInfo)
    • Description: Contains metadata related to the creation of a contact, including timestamps and related information.
    • SEO Purpose: Enhances data accuracy and historical tracking by providing detailed contact creation information.
    • How to Use: Maintain accurate contact creation information to enhance data integrity and historical tracking.
61. Contact Edit Context Info (AppsPeopleOzExternalMergedpeopleapiContactEditContextInfo)
    • Description: Provides metadata related to the editing of a contact, including timestamps and related details.
    • SEO Purpose: Enhances data accuracy and historical tracking by providing detailed contact edit information.
    • How to Use: Ensure contact edit information is accurate and up-to-date to enhance data integrity and historical tracking.
62. Contact Group Membership (AppsPeopleOzExternalMergedpeopleapiContactGroupMembership)
    • Description: Represents a person’s membership in contact groups, enhancing the organization and management of contacts.
    • SEO Purpose: Improves contact organization and management by showcasing group memberships.
    • How to Use: Maintain accurate contact group memberships to enhance organization and management of contacts.
63. Contact Prompt Settings Info (AppsPeopleOzExternalMergedpeopleapiContactPromptSettingsInfo)
    • Description: Contains settings for contact-level people prompts, enhancing personalized user interactions.
    • SEO Purpose: Enhances user engagement by providing personalized prompts based on contact-level settings.
    • How to Use: Implement contact prompt settings to provide personalized interaction prompts, improving user engagement.
64. Contact State Info (AppsPeopleOzExternalMergedpeopleapiContactStateInfo)
    • Description: Provides information about the state and metadata of a contact, supporting detailed contact management.
    • SEO Purpose: Enhances contact management by providing detailed state information and related metadata.
    • How to Use: Maintain accurate contact state information to enhance contact management and organization.
65. Cover Photo (AppsPeopleOzExternalMergedpeopleapiCoverPhoto)
    • Description: Represents the cover photo or banner image at the top of a Google+ profile page, enhancing visual appeal.
    • SEO Purpose: Enhances profile attractiveness and user engagement by providing a visually appealing cover photo.
    • How to Use: Ensure cover photos are high-quality and visually appealing to enhance profile attractiveness and engagement.
66. Custom Schema Field (AppsPeopleOzExternalMergedpeopleapiCustomSchemaField)
    • Description: Represents custom fields associated with a person, defined by the domain’s custom schema.
    • SEO Purpose: Enhances profile customization and data richness by supporting custom fields.
    • How to Use: Utilize custom schema fields to add personalized and domain-specific information to profiles, enhancing data richness and relevance.
67. Customer Info (AppsPeopleOzExternalMergedpeopleapiCustomerInfo)
    • Description: Contains customer-specific data for the profile owner, enhancing profile information and personalization.
    • SEO Purpose: Improves profile completeness and personalization by adding detailed customer information.
    • How to Use: Maintain accurate customer information to enhance profile completeness and user personalization.
68. Deduped Container Info (AppsPeopleOzExternalMergedpeopleapiDedupedContainerInfo)
    • Description: Provides information for deduping fields with the same value, supporting efficient data management and storage.
    • SEO Purpose: Enhances data management efficiency by avoiding duplication and ensuring accurate data representation.
    • How to Use: Implement deduped container info to manage data efficiently, avoiding duplication and ensuring data accuracy.
69. Delegated Group Info (AppsPeopleOzExternalMergedpeopleapiDelegatedGroupInfo)
    • Description: Contains information related to delegated groups that a contact belongs to, supporting group management and organization.
    • SEO Purpose: Enhances group management by providing detailed information about delegated group memberships.
    • How to Use: Maintain accurate delegated group information to enhance group management and organization.
70. Device Contact Extra Metadata (AppsPeopleOzExternalMergedpeopleapiDeviceContactExtraMetadata)
    • Description: Provides extra metadata for an aggregated or raw device contact, enhancing contact details and information.
    • SEO Purpose: Enhances contact management by providing additional metadata for device contacts.
    • How to Use: Utilize extra metadata to enrich device contact information, improving contact management and data richness.
71. Device Contact ID (AppsPeopleOzExternalMergedpeopleapiDeviceContactId)
    • Description: Represents a unique ID for an aggregated device contact, supporting contact identification and management.
    • SEO Purpose: Ensures accurate contact identification and management by providing unique device contact IDs.
    • How to Use: Maintain accurate device contact IDs to ensure precise identification and management of contacts.
72. Device Contact Info (AppsPeopleOzExternalMergedpeopleapiDeviceContactInfo)
    • Description: Provides detailed information about a device contact, supporting comprehensive contact management.
    • SEO Purpose: Enhances contact management by providing detailed device contact information.
    • How to Use: Ensure device contact information is complete and accurate to enhance contact management and organization.
73. Edge Key Info (AppsPeopleOzExternalMergedpeopleapiEdgeKeyInfo)
    • Description: Contains information about edges connecting entities, including container ID, container type, and additional extended data.
    • SEO Purpose: Supports detailed data relationships and connections, enhancing data management and organization.
    • How to Use: Utilize edge key info to manage data relationships and connections accurately, improving data organization and relevance.
74. Edge Key Info Extension Data (AppsPeopleOzExternalMergedpeopleapiEdgeKeyInfoExtensionData)
    • Description: This ranking factor provides extended data for edge key information, including compatibility extensions that can return mobile owner IDs for profile containers.
    • SEO Purpose: Helps in managing and tracking the relationships and interactions between different data entities, which can be crucial for data organization and accessibility.
    • How to Use: Use this data to ensure that your content’s relational information is accurately tracked and managed, improving data integrity and search relevance.
75. Email (AppsPeopleOzExternalMergedpeopleapiEmail)
    • Description: Represents a person’s email information, including details such as certificates, classification, group preferences, display name, extended data, and type.
    • SEO Purpose: Ensures accurate and comprehensive email information, which can improve user communication and profile completeness.
    • How to Use: Maintain up-to-date and well-classified email information to enhance profile accuracy and communication efficiency.
76. Email Certificate (AppsPeopleOzExternalMergedpeopleapiEmailCertificate)
    • Description: Represents S/MIME certificate configurations for use with Gmail, providing secure email communication. Multiple certificates can be associated with an email address.
    • SEO Purpose: Enhances email security and trustworthiness, which can improve user trust and engagement.
    • How to Use: Ensure your email addresses are associated with valid S/MIME certificates to provide secure and trustworthy communication.
77. Email Contact Group Preference (AppsPeopleOzExternalMergedpeopleapiEmailContactGroupPreference)
    • Description: Indicates preferred email addresses for contact groups, ensuring that the most relevant email addresses are used for communication within groups.
    • SEO Purpose: Improves group communication efficiency by using preferred and relevant email addresses.
    • How to Use: Set and update email preferences for contact groups to ensure effective and relevant group communications.
78. Email Extended Data (AppsPeopleOzExternalMergedpeopleapiEmailExtendedData)
    • Description: Provides additional extension data for a person’s email, supporting more detailed and customized email information.
    • SEO Purpose: Enhances the richness and customization of email data, which can improve user profiles and communication strategies.
    • How to Use: Utilize extended email data to add detailed and customized information to email addresses, enhancing user profiles and communications.
79. Email Signup Metadata (AppsPeopleOzExternalMergedpeopleapiEmailSignupEmailMetadata)
    • Description: Contains additional metadata for a signup email, specifically set when the email’s classification is a signup email.
    • SEO Purpose: Helps in tracking and managing signup-related emails, ensuring they are correctly classified and handled.
    • How to Use: Ensure signup emails are correctly classified and associated with relevant metadata to improve tracking and management.
80. Emergency Info (AppsPeopleOzExternalMergedpeopleapiEmergencyInfo)
    • Description: Provides emergency information for a person, such as trusted contacts and critical contact details.
    • SEO Purpose: Enhances user safety and preparedness by providing readily accessible emergency contact information.
    • How to Use: Keep emergency contact information up-to-date and readily accessible to improve user safety and preparedness.
81. Event (AppsPeopleOzExternalMergedpeopleapiEvent)
    • Description: Represents important events associated with a person, such as anniversaries, with attributes detailing calendar days, formatted types, and prompts.
    • SEO Purpose: Enhances profile richness by including significant personal events, improving user engagement and relevance.
    • How to Use: Ensure important personal events are accurately recorded and updated to enhance profile richness and user engagement.
82. External ID (AppsPeopleOzExternalMergedpeopleapiExternalId)
    • Description: Represents external identifiers associated with a person, aiding in cross-referencing and identification across different systems.
    • SEO Purpose: Improves data integration and management by providing external identifiers that facilitate cross-referencing.
    • How to Use: Maintain accurate external identifiers to ensure smooth data integration and cross-referencing across different systems.
83. Field ACL (AppsPeopleOzExternalMergedpeopleapiFieldAcl)
    • Description: Specifies access control lists (ACLs) for profile fields, indicating who can view or edit specific data fields.
    • SEO Purpose: Enhances data security and privacy by controlling access to specific profile fields.
    • How to Use: Set and manage field ACLs to control who can access or modify profile information, ensuring data security and privacy.
84. Field ACL Entry (AppsPeopleOzExternalMergedpeopleapiFieldAclAclEntry)
    • Description: Details specific entries in a field ACL, including roles and scopes, defining the access permissions for profile fields.
    • SEO Purpose: Provides granular control over data access, enhancing security and compliance with privacy policies.
    • How to Use: Define and manage specific ACL entries to control access to profile fields, ensuring compliance with privacy and security requirements.
85. Field ACL Entry Scope (AppsPeopleOzExternalMergedpeopleapiFieldAclAclEntryScope)
    • Description: Specifies the scope of an ACL entry, such as all users, domain users, or specific memberships, determining who can access the field.
    • SEO Purpose: Enhances data access control by specifying precise scopes for ACL entries, improving security and privacy.
    • How to Use: Configure ACL entry scopes to accurately control data access, ensuring only authorized users can view or edit specific fields.
86. Field Emergency Info (AppsPeopleOzExternalMergedpeopleapiFieldEmergencyInfo)
    • Description: Provides emergency information for specific profile fields, such as emergency phone numbers or email addresses.
    • SEO Purpose: Enhances safety and preparedness by associating emergency information with specific profile fields.
    • How to Use: Ensure emergency information is accurately linked to relevant profile fields to improve user safety and emergency response.
87. File As (AppsPeopleOzExternalMergedpeopleapiFileAs)
    • Description: Allows overriding the display name of a contact with a different name, providing flexibility in how contacts are listed and identified.
    • SEO Purpose: Improves contact management by allowing customization of display names, enhancing usability and organization.
    • How to Use: Use the File As feature to customize contact display names for better organization and identification.
88. GPay Extended Data (AppsPeopleOzExternalMergedpeopleapiGPayExtendedData)
    • Description: Provides additional data for use in GPay product profiles, enhancing profile information for GPay users.
    • SEO Purpose: Enhances the richness and accuracy of GPay profiles, improving user experience and transaction reliability.
    • How to Use: Integrate extended data into GPay profiles to provide more detailed and accurate information, enhancing user experience and trust.
89. Gender (AppsPeopleOzExternalMergedpeopleapiGender)
    • Description: Represents gender information, including specific rules for reading and writing gender data, supporting various gender identities and custom types.
    • SEO Purpose: Enhances profile completeness and inclusivity by accurately representing gender information.
    • How to Use: Ensure gender information is accurately recorded and updated, supporting inclusivity and accurate profile representation.
90. Gplus Extended Data (AppsPeopleOzExternalMergedpeopleapiGplusExtendedData)
    • Description: Provides additional data for Google+ profiles, including content restrictions and enterprise user status.
    • SEO Purpose: Enhances Google+ profiles with additional data, improving profile completeness and compliance with content policies.
    • How to Use: Maintain accurate Gplus extended data to ensure comprehensive and compliant profiles.
91. Hangouts Extended Data (AppsPeopleOzExternalMergedpeopleapiHangoutsExtendedData)
    • Description: Provides additional data for Hangouts, supporting enhanced user interactions and profile information within the Hangouts app.
    • SEO Purpose: Improves user experience in Hangouts by providing richer profile data and interaction capabilities.
    • How to Use: Integrate Hangouts extended data to enhance user interactions and profile completeness within the Hangouts app.
92. Identity Info (AppsPeopleOzExternalMergedpeopleapiIdentityInfo)
    • Description: Contains information about a person’s identity, including lookup tokens, previous IDs, and source IDs, supporting identity management and synchronization.
    • SEO Purpose: Enhances identity management by providing comprehensive information about a person’s identity and history.
    • How to Use: Maintain accurate identity information to ensure effective identity management and synchronization across systems.
93. IM (AppsPeopleOzExternalMergedpeopleapiIm)
    • Description: Represents instant messaging (IM) information, including protocol, type, and value, supporting various IM services.
    • SEO Purpose: Enhances profile information by including IM details, improving communication options and profile completeness.
    • How to Use: Ensure IM information is up-to-date and accurate to provide comprehensive communication options in profiles.
94. In-App Notification Target (AppsPeopleOzExternalMergedpeopleapiInAppNotificationTarget)
    • Description: Specifies how and where to send notifications to a person within other apps, detailing the target type, value, and apps.
    • SEO Purpose: Improves notification targeting by specifying accurate and relevant notification delivery methods.
    • How to Use: Configure in-app notification targets to ensure notifications are delivered accurately and effectively across different apps.
95. In-App Notification Target Client Data (AppsPeopleOzExternalMergedpeopleapiInAppNotificationTargetClientData)
    • Description: Contains client-specific data related to app reachability, without storing any personal information or user content.
    • SEO Purpose: Enhances app reachability management by providing client-specific data, improving notification accuracy and relevance.
    • How to Use: Utilize client-specific data to improve app reachability and notification targeting, ensuring accurate and relevant communication.
96. In-App Notification Target Originating Field (AppsPeopleOzExternalMergedpeopleapiInAppNotificationTargetOriginatingField)
    • Description: Provides information for identifying the specific field that allows sending notifications to a person, typically associated with contact fields.
    • SEO Purpose: Enhances notification targeting by identifying the precise fields that enable notifications, improving communication relevance.
    • How to Use: Maintain accurate originating field information to ensure precise and effective notification targeting.
97. In-App Reachability (AppsPeopleOzExternalMergedpeopleapiInAppReachability)
    • Description: Deprecated field indicating which apps a person is reachable at, used for profiles.
    • SEO Purpose: Previously used to enhance reachability information in profiles, now replaced by In-App Notification Target.
    • How to Use: Use In-App Notification Target instead for managing app reachability information.
98. In-App Reachability Key (AppsPeopleOzExternalMergedpeopleapiInAppReachabilityReachabilityKey)
    • Description: Provides information on how the reachable state was established, supporting detailed reachability management.
    • SEO Purpose: Enhances reachability management by providing detailed information on the establishment of reachable states.
    • How to Use: Use reachability key information to manage and verify the accuracy of reachability states, improving communication reliability.
99. Interaction Settings (AppsPeopleOzExternalMergedpeopleapiInteractionSettings)
    • Description: Defines the allowed or disallowed interactions with a person, supporting detailed interaction management.
    • SEO Purpose: Enhances interaction management by specifying allowed and disallowed interactions, improving user experience and compliance.
    • How to Use: Configure interaction settings to control and manage user interactions effectively, ensuring compliance and enhancing user experience.
100. Interest (AppsPeopleOzExternalMergedpeopleapiInterest)
     • Description: Represents a person’s interests, including metadata and value, supporting detailed profile enrichment.
     • SEO Purpose: Enhances profile richness and relevance by including detailed information about a person’s interests.
     • How to Use: Maintain accurate and up-to-date interest information to enhance profile richness and improve content personalization.
101. Language (AppsPeopleOzExternalMergedpeopleapiLanguage)
     • Description: Represents a person’s language preferences, supporting IETF BCP 47 language codes or custom values.
     • SEO Purpose: Enhances profile completeness and content relevance by including accurate language preferences.
     • How to Use: Ensure language preferences are accurately recorded and updated to improve content personalization and relevance.
102. LatLng (AppsPeopleOzExternalMergedpeopleapiLatLng)
     • Description: Represents latitude and longitude coordinates, supporting precise location information for profiles.
     • SEO Purpose: Enhances location-based services and content relevance by providing accurate geographic coordinates.
     • How to Use: Maintain accurate latitude and longitude coordinates to improve location-based services and content relevance.
103. Legacy Fields (AppsPeopleOzExternalMergedpeopleapiLegacyFields)
     • Description: Fields used in legacy applications, useful for joining legacy and new data streams.
     • SEO Purpose: Supports data integration and transition from legacy to new systems, ensuring data continuity.
     • How to Use: Utilize legacy fields to manage data transitions and integration, ensuring continuity and compatibility with legacy systems.
104. Limited Profile Settings Field (AppsPeopleOzExternalMergedpeopleapiLimitedProfileSettingsField)
     • Description: Represents settings for limited profiles, including privacy and access control settings.
     • SEO Purpose: Enhances privacy and security by providing detailed settings for limited profiles.
     • How to Use: Configure limited profile settings to control privacy and access, ensuring compliance with privacy policies and enhancing user trust.
105. Location (AppsPeopleOzExternalMergedpeopleapiLocation)
     • Description: Represents detailed location information, including building details, desk location, floor information, and metadata.
     • SEO Purpose: Enhances profile completeness and location-based services by providing accurate and detailed location information.
     • How to Use: Ensure location information is accurate and up-to-date to improve profile completeness and location-based services.
106. Management Upchain (AppsPeopleOzExternalMergedpeopleapiManagementUpchain)
     • Description: Represents the management hierarchy, listing managers in the chain of command.
     • SEO Purpose: Enhances organizational understanding and reporting by providing detailed management hierarchy information.
     • How to Use: Maintain accurate management upchain information to improve organizational reporting and structure.
107. Management Upchain Indirect Manager (AppsPeopleOzExternalMergedpeopleapiManagementUpchainIndirectManager)
     • Description: Provides information about indirect managers in the management hierarchy, supporting detailed organizational structure.
     • SEO Purpose: Enhances understanding of indirect management relationships, improving organizational clarity and reporting.
     • How to Use: Ensure indirect manager information is accurate and up-to-date to improve organizational structure and reporting.
108. Maps Extended Data (AppsPeopleOzExternalMergedpeopleapiMapsExtendedData)
     • Description: Provides additional data for use in Maps product profiles, enhancing profile information for Maps users.
     • SEO Purpose: Enhances Maps profiles with additional data, improving user experience and content accuracy.
     • How to Use: Integrate extended data into Maps profiles to provide more detailed and accurate information, enhancing user experience.
109. Maps Profile (AppsPeopleOzExternalMergedpeopleapiMapsProfile)
     • Description: Represents profile data for Maps, supporting detailed and accurate profile information for Maps users.
     • SEO Purpose: Enhances profile completeness and accuracy for Maps, improving user experience and content relevance.
     • How to Use: Ensure Maps profile information is accurate and up-to-date to enhance user experience and content relevance in Maps.
110. Maps Profile Field Restriction (AppsPeopleOzExternalMergedpeopleapiMapsProfileFieldRestriction)
     • Description: Provides restrictions for Maps profile fields, including client data and restriction types.
     • SEO Purpose: Enhances data security and privacy by providing detailed field restrictions for Maps profiles.
     • How to Use: Configure field restrictions to control access and visibility of Maps profile information, ensuring data security and privacy.
111. Maps Profile URL Link (AppsPeopleOzExternalMergedpeopleapiMapsProfileUrlLink)
     • Description: Represents a URL link for Maps profiles, including anchor text and the URL.
     • SEO Purpose: Enhances profile information by providing clickable links, improving user navigation and information access.
     • How to Use: Ensure URL links are accurate and provide relevant anchor text to improve user navigation and profile information.
112. Match Info (AppsPeopleOzExternalMergedpeopleapiMatchInfo)
     • Description: Represents matching information for fields when there is a query, supporting detailed query matching.
     • SEO Purpose: Enhances search and matching accuracy by providing detailed match information for queries.
     • How to Use: Utilize match info to improve search accuracy and relevance, ensuring precise query matching.
113. Match Info Lookup Token Match (AppsPeopleOzExternalMergedpeopleapiMatchInfoLookupTokenMatch)
     • Description: Represents substrings matched for a query against a field, supporting detailed query matching.
     • SEO Purpose: Enhances search accuracy by providing detailed matching substrings for queries.
     • How to Use: Use lookup token matches to improve search accuracy and relevance, ensuring precise query matching.
114. Membership (AppsPeopleOzExternalMergedpeopleapiMembership)
     • Description: Represents a person’s membership in circles and contact groups, supporting detailed social connections.
     • SEO Purpose: Enhances profile richness by including detailed membership information, improving social connections and relevance.
     • How to Use: Maintain accurate membership information to enhance profile richness and improve social connections.
115. Mission (AppsPeopleOzExternalMergedpeopleapiMission)
     • Description: Represents a person’s mission or purpose, including metadata and value, supporting detailed profile enrichment.
     • SEO Purpose: Enhances profile completeness and relevance by including detailed mission information.
     • How to Use: Ensure mission information is accurately recorded and updated to enhance profile richness and relevance.
116. Name (AppsPeopleOzExternalMergedpeopleapiName)
     • Description: Represents a person’s name, including structured and unstructured fields, supporting detailed name information.
     • SEO Purpose: Enhances profile accuracy and completeness by providing detailed name information.
     • How to Use: Maintain accurate name information, including structured and unstructured fields, to improve profile accuracy and completeness.
117. Name Pronunciation Audio Metadata Info (AppsPeopleOzExternalMergedpeopleapiNamePronunciationAudioMetadataInfo)
     • Description: Provides metadata for name pronunciation audio, supporting accurate pronunciation information.
     • SEO Purpose: Enhances user experience by providing accurate name pronunciation information, improving accessibility and personalization.
     • How to Use: Ensure name pronunciation audio metadata is accurate and up-to-date to improve user experience and accessibility.
118. Nickname (AppsPeopleOzExternalMergedpeopleapiNickname)
     • Description: Represents a person’s nickname, including metadata and value, supporting detailed profile information.
     • SEO Purpose: Enhances profile richness and personalization by including nickname information.
     • How to Use: Maintain accurate nickname information to enhance profile richness and improve personalization.
119. Occupation (AppsPeopleOzExternalMergedpeopleapiOccupation)
     • Description: Represents a person’s occupation, including metadata and value, supporting detailed profile enrichment.
     • SEO Purpose: Enhances profile completeness and relevance by including detailed occupation information.
     • How to Use: Ensure occupation information is accurate and up-to-date to enhance profile richness and relevance.
120. Opening Hours (AppsPeopleOzExternalMergedpeopleapiOpeningHours)
     • Description: Represents the periods a place is open during the week, supporting detailed business hours information.
     • SEO Purpose: Enhances location-based services and user experience by providing accurate business hours information.
     • How to Use: Maintain accurate opening hours information to improve location-based services and user experience.
121. Opening Hours Endpoint (AppsPeopleOzExternalMergedpeopleapiOpeningHoursEndpoint)
     • Description: Represents a specific day and time a place is open, supporting detailed business hours information.
     • SEO Purpose: Enhances accuracy of business hours information by providing specific opening times.
     • How to Use: Ensure opening hours endpoints are accurate and up-to-date to improve business hours information and user experience.
122. Opening Hours Period (AppsPeopleOzExternalMergedpeopleapiOpeningHoursPeriod)
     • Description: Represents the opening and closing times for a period, supporting detailed business hours information.
     • SEO Purpose: Enhances user experience by providing accurate and detailed business hours information.
     • How to Use: Maintain accurate opening hours periods to improve business hours information and user experience.
123. Organization Information (AppsPeopleOzExternalMergedpeopleapiOrganization)
     • Description: This ranking factor includes detailed information about a person’s organization, such as department, title, projects, and certification. It also includes start and end dates for their tenure, location, and metadata about the role and organization.
     • SEO Purpose: Ensures that organizational information is comprehensive and accurate, which can improve the credibility and professional appearance of profiles.
     • How to Use: Maintain detailed and accurate organizational information on profiles to enhance professional credibility and improve visibility in professional searches.
124. Organization Assignment (AppsPeopleOzExternalMergedpeopleapiOrganizationAssignment)
     • Description: Represents specific assignments within an organization, including assignment name and URL.
     • SEO Purpose: Highlights specific roles or projects within an organization, enhancing the detailed understanding of a person’s professional experience.
     • How to Use: Include detailed assignment information to provide a comprehensive view of professional roles and projects, improving profile completeness and relevance.
125. Organization Project (AppsPeopleOzExternalMergedpeopleapiOrganizationProject)
     • Description: Details projects within an organization, including project name, description, role, type, and URL.
     • SEO Purpose: Showcases project involvement and specific roles, highlighting professional experience and expertise.
     • How to Use: Document project details to highlight specific professional experiences and contributions, enhancing profile depth and search relevance.
126. Other Keyword (AppsPeopleOzExternalMergedpeopleapiOtherKeyword)
     • Description: Represents various keywords related to a person, including type, value, and metadata. These keywords can come from sources like Outlook and be categorized as billing information, directory server, keyword, etc.
     • SEO Purpose: Enhances profile richness by adding relevant keywords that can improve searchability and contextual relevance.
     • How to Use: Add relevant keywords to profiles to improve searchability and contextual relevance, ensuring the profile captures all pertinent information.
127. Merged Person (AppsPeopleOzExternalMergedpeopleapiPerson)
     • Description: Combines multiple sources of data, such as contacts and profiles, to create a unified representation of a person.
     • SEO Purpose: Ensures that profiles are comprehensive and up-to-date by merging data from multiple sources, improving accuracy and completeness.
     • How to Use: Ensure that merged profiles are regularly updated to maintain accuracy and comprehensiveness, improving profile quality and search relevance.
128. Person Attribute (AppsPeopleOzExternalMergedpeopleapiPersonAttribute)
     • Description: Stores client-specific binary data with person information, distinct from structured client data.
     • SEO Purpose: Allows for the inclusion of unique client-specific data, enhancing profile customization and relevance.
     • How to Use: Use person attributes to include unique client-specific data in profiles, improving customization and relevance.
129. Person Extended Data (AppsPeopleOzExternalMergedpeopleapiPersonExtendedData)
     • Description: Provides additional extension data for the entire person entity, supporting detailed profile information.
     • SEO Purpose: Enhances profile richness and customization by including extended data.
     • How to Use: Utilize extended data to add detailed information to profiles, improving completeness and relevance.
130. Person Field Metadata (AppsPeopleOzExternalMergedpeopleapiPersonFieldMetadata)
     • Description: Contains metadata for individual person fields, supporting detailed information management.
     • SEO Purpose: Enhances data accuracy and integrity by providing detailed metadata for profile fields.
     • How to Use: Ensure accurate metadata for profile fields to maintain data integrity and enhance profile management.
131. Person List With Total Number (AppsPeopleOzExternalMergedpeopleapiPersonListWithTotalNumber)
     • Description: Represents a list of persons along with the total number of entries, supporting detailed data management and reporting.
     • SEO Purpose: Enhances data reporting and management by providing a comprehensive list of persons with total counts.
     • How to Use: Utilize person lists with total numbers for detailed data management and reporting, ensuring comprehensive data handling.
132. Person Metadata (AppsPeopleOzExternalMergedpeopleapiPersonMetadata)
     • Description: Provides metadata for the entire person resource, supporting comprehensive profile management.
     • SEO Purpose: Enhances profile accuracy and completeness by including detailed metadata for the entire person resource.
     • How to Use: Maintain accurate person metadata to ensure comprehensive profile management and data accuracy.
133. Person Metadata Scoring Info (AppsPeopleOzExternalMergedpeopleapiPersonMetadataScoringInfo)
     • Description: Contains scoring information for person metadata, including raw match quality scores and expression results.
     • SEO Purpose: Improves search accuracy and relevance by providing detailed scoring information.
     • How to Use: Use scoring information to enhance search algorithms and improve profile relevance in search results.
134. Phone (AppsPeopleOzExternalMergedpeopleapiPhone)
     • Description: Represents phone information for a person, including type, value, and metadata. It supports canonical forms, emergency info, and extended data.
     • SEO Purpose: Enhances communication options by providing comprehensive phone information.
     • How to Use: Ensure phone information is accurate and up-to-date to improve communication options and profile completeness.
135. Phone Extended Data (AppsPeopleOzExternalMergedpeopleapiPhoneExtendedData)
     • Description: Provides additional data for phone information, supporting more detailed and customized phone information.
     • SEO Purpose: Enhances phone data richness and customization, improving communication options.
     • How to Use: Utilize extended phone data to provide more detailed and customized phone information, enhancing profile completeness.
136. Photo (AppsPeopleOzExternalMergedpeopleapiPhoto)
     • Description: Represents photo information for a person, including decorations, emoji avatars, attribution, and URL.
     • SEO Purpose: Enhances profile appearance and user engagement by including detailed photo information.
     • How to Use: Ensure profile photos are high-quality and include necessary decorations and attributions to enhance profile appearance and engagement.
137. Place Details (AppsPeopleOzExternalMergedpeopleapiPlaceDetails)
     • Description: Contains metadata specific to places, supporting detailed location information.
     • SEO Purpose: Enhances location-based services and profile accuracy by providing detailed place information.
     • How to Use: Maintain accurate place details to improve location-based services and profile relevance.
138. Play Games Extended Data (AppsPeopleOzExternalMergedpeopleapiPlayGamesExtendedData)
     • Description: Provides additional data for Play Games profiles, enhancing profile information for gamers.
     • SEO Purpose: Enhances gaming profiles by including detailed game-related data.
     • How to Use: Integrate Play Games extended data to provide detailed and accurate gaming profiles, improving user engagement and experience.
139. Plus Page Info (AppsPeopleOzExternalMergedpeopleapiPlusPageInfo)
     • Description: Represents information about a Google+ page and the entity it represents.
     • SEO Purpose: Enhances profile completeness by including detailed information about Google+ pages.
     • How to Use: Ensure accurate Google+ page information to improve profile completeness and search relevance.
140. Point Specification (AppsPeopleOzExternalMergedpeopleapiPointSpec)
     • Description: Represents map marker locations for addresses, supporting detailed geographic information.
     • SEO Purpose: Enhances location-based services and profile relevance by providing accurate geographic coordinates.
     • How to Use: Maintain accurate point specifications to improve location-based services and profile relevance.
141. POSIX Account (AppsPeopleOzExternalMergedpeopleapiPosixAccount)
     • Description: Represents POSIX account information, including username and UID, ensuring global uniqueness.
     • SEO Purpose: Enhances data integrity and management by ensuring unique account information.
     • How to Use: Ensure POSIX account information is accurate and unique to maintain data integrity and prevent duplicates.
142. Product Metadata (AppsPeopleOzExternalMergedpeopleapiProductMetadata)
     • Description: Provides metadata for products associated with a person, supporting detailed product information.
     • SEO Purpose: Enhances profile richness by including detailed product metadata.
     • How to Use: Maintain accurate product metadata to enhance profile richness and relevance.
143. Product Profile Failure (AppsPeopleOzExternalMergedpeopleapiProductProfileFailure)
     • Description: Represents the status of a failed attempt to fetch a product profile, indicating issues in profile retrieval.
     • SEO Purpose: Helps diagnose and resolve issues in fetching product profiles, ensuring data accuracy and completeness.
     • How to Use: Monitor and address product profile failures to ensure accurate and complete profile information.
144. Profile Owner Stats (AppsPeopleOzExternalMergedpeopleapiProfileOwnerStats)
     • Description: Provides statistics related to incoming edges and views for a profile, visible to the requester.
     • SEO Purpose: Enhances understanding of profile interactions and visibility by providing detailed statistics.
     • How to Use: Utilize profile owner stats to monitor and improve profile visibility and engagement.
145. Profile URL (AppsPeopleOzExternalMergedpeopleapiProfileUrl)
     • Description: Represents a URL for a Google+ profile, supporting detailed profile information.
     • SEO Purpose: Enhances profile completeness and accessibility by providing a direct URL to the profile.
     • How to Use: Ensure profile URLs are accurate and accessible to improve profile completeness and visibility.
146. Pronoun (AppsPeopleOzExternalMergedpeopleapiPronoun)
     • Description: Represents a user’s set of preferred pronouns, supporting gender inclusivity and personalization.
     • SEO Purpose: Enhances profile inclusivity and personalization by including preferred pronouns.
     • How to Use: Ensure preferred pronouns are accurately recorded and updated to enhance profile inclusivity and personalization.
147. Raw Device Contact Analytical Info (AppsPeopleOzExternalMergedpeopleapiRawDeviceContactAnalyticalInfo)
     • Description: Provides analytical information for raw device contacts, including data set, sync state, and source ID existence.
     • SEO Purpose: Enhances contact data management by providing detailed analytical information.
     • How to Use: Utilize analytical info to manage and synchronize contact data accurately, ensuring data integrity.
148. Raw Device Contact Info (AppsPeopleOzExternalMergedpeopleapiRawDeviceContactInfo)
     • Description: Represents raw device contact information, supporting detailed contact data management.
     • SEO Purpose: Enhances contact data management by including detailed raw contact information.
     • How to Use: Maintain accurate raw device contact information to improve contact data management and synchronization.
149. Read-Only Profile Info (AppsPeopleOzExternalMergedpeopleapiReadOnlyProfileInfo)
     • Description: Provides metadata information about a read-only profile, supporting detailed profile information.
     • SEO Purpose: Enhances profile completeness and data integrity by providing read-only profile information.
     • How to Use: Ensure read-only profile info is accurate and up-to-date to enhance profile completeness and data integrity.
150. Relation (AppsPeopleOzExternalMergedpeopleapiRelation)
     • Description: Stores related person information, supporting detailed relationship data between contacts or profiles.
     • SEO Purpose: Enhances profile richness by including detailed relationship information.
     • How to Use: Maintain accurate relationship information to enhance profile richness and relevance.
151. Relation Details (AppsPeopleOzExternalMergedpeopleapiRelationRelationDetails)
     • Description: Provides details about a relationship, including display name, job title, person ID, and photo URL.
     • SEO Purpose: Enhances profile completeness by including detailed relationship information.
     • How to Use: Ensure relationship details are accurate and up-to-date to enhance profile richness and relevance.
152. Right of Publicity State (AppsPeopleOzExternalMergedpeopleapiRightOfPublicityState)
     • Description: Represents user preferences for shared endorsements, supporting detailed publicity settings.
     • SEO Purpose: Enhances profile customization by including preferences for shared endorsements.
     • How to Use: Maintain accurate right of publicity settings to manage shared endorsements effectively.
153. Roster Details (AppsPeopleOzExternalMergedpeopleapiRosterDetails)
     • Description: Provides information specific to rosters, such as Google Groups and Chatrooms.
     • SEO Purpose: Enhances profile richness by including detailed roster information.
     • How to Use: Ensure roster details are accurate and up-to-date to enhance profile completeness and relevance.
154. Roster Member (AppsPeopleOzExternalMergedpeopleapiRosterMember)
     • Description: Represents details of a member of a roster, including membership information.
     • SEO Purpose: Enhances social connections by providing detailed roster membership information.
     • How to Use: Maintain accurate roster member information to improve social connections and profile completeness.
155. Roster Member Count (AppsPeopleOzExternalMergedpeopleapiRosterMemberCount)
     • Description: Represents a summary of member counts in a roster, supporting detailed membership data.
     • SEO Purpose: Enhances understanding of roster composition by providing detailed member counts.
     • How to Use: Utilize roster member counts to manage and analyze roster composition effectively.
156. Search Profile (AppsPeopleOzExternalMergedpeopleapiSearchProfile)
     • Description: Represents a profile for search purposes, supporting detailed profile information.
     • SEO Purpose: Enhances search relevance by including detailed profile information.
     • How to Use: Ensure search profiles are accurate and comprehensive to improve search relevance and visibility.
157. SIP Address (AppsPeopleOzExternalMergedpeopleapiSipAddress)
     • Description: Represents SIP (Session Initiation Protocol) address information, supporting detailed contact data.
     • SEO Purpose: Enhances communication options by including SIP address information.
     • How to Use: Ensure SIP address information is accurate and up-to-date to improve communication options.
158. Skills (AppsPeopleOzExternalMergedpeopleapiSkills)
     • Description: Represents a person’s skills, including metadata and value, supporting detailed profile enrichment.
     • SEO Purpose: Enhances profile richness by including detailed skills information.
     • How to Use: Maintain accurate skills information to enhance profile richness and relevance.
159. Social Connection (AppsPeopleOzExternalMergedpeopleapiSocialConnection)
     • Description: Represents the social connection of a person to the viewer, used by specific applications.
     • SEO Purpose: Enhances social profile completeness by including social connection information.
     • How to Use: Ensure social connection information is accurate and up-to-date to improve social profile completeness and relevance.
160. Sort Keys (AppsPeopleOzExternalMergedpeopleapiSortKeys)
     • Description: This ranking factor includes various keys used to sort data, such as affinity scores, interaction rank (deprecated), and raw name strings. These keys help generate sorted lists of names or other data.
     • SEO Purpose: Ensures that data is sorted accurately, improving the user experience by presenting the most relevant information first.
     • How to Use: Implement sort keys to organize and prioritize data effectively, ensuring that the most important or relevant information is displayed prominently.
161. Source Identity (AppsPeopleOzExternalMergedpeopleapiSourceIdentity)
     • Description: Represents the identifier of a single source from a merged person, aiding in the consolidation of data from various origins.
     • SEO Purpose: Enhances data accuracy and completeness by consolidating information from multiple sources.
     • How to Use: Use source identities to merge data from different sources, ensuring comprehensive and accurate profiles.
162. SSH Public Key (AppsPeopleOzExternalMergedpeopleapiSshPublicKey)
     • Description: Custom field representing SSH public keys associated with the user, mapped from a string fingerprint to the SSH public key information.
     • SEO Purpose: Enhances security and access control by including SSH public keys in profiles.
     • How to Use: Maintain and manage SSH public keys to ensure secure access and authentication for users.
163. Structured Phone (AppsPeopleOzExternalMergedpeopleapiStructuredPhone)
     • Description: Mirrors the ContactPhoneNumber message and includes structured phone data, such as international numbers and validation results.
     • SEO Purpose: Improves communication options by providing structured and validated phone numbers.
     • How to Use: Ensure phone numbers are accurately structured and validated to enhance communication reliability.
164. Structured Phone Number (AppsPeopleOzExternalMergedpeopleapiStructuredPhonePhoneNumber)
     • Description: Contains details about structured phone numbers, including E.164 format, international and national numbers, and validity status.
     • SEO Purpose: Ensures accurate and reliable phone number information, enhancing communication capabilities.
     • How to Use: Maintain accurate and validated phone number information to improve communication options.
165. Structured Phone Short Code (AppsPeopleOzExternalMergedpeopleapiStructuredPhoneShortCode)
     • Description: Represents short phone codes and associated country codes, useful for quick dialing and SMS services.
     • SEO Purpose: Enhances communication by providing quick and easy access to short codes.
     • How to Use: Use short codes to facilitate quick dialing and improve communication efficiency.
166. Tagline (AppsPeopleOzExternalMergedpeopleapiTagline)
     • Description: Represents a tagline associated with a person, including metadata and value, adding a personal touch to profiles.
     • SEO Purpose: Enhances profile personalization and branding by including taglines.
     • How to Use: Include a unique and relevant tagline in profiles to improve personalization and branding.
167. Teams Extended Data (AppsPeopleOzExternalMergedpeopleapiTeamsExtendedData)
     • Description: This message is unsupported and no longer used.
     • SEO Purpose: N/A (unsupported).
     • How to Use: N/A (unsupported).
168. User Defined (AppsPeopleOzExternalMergedpeopleapiUserDefined)
     • Description: Allows users to define custom key-value pairs for additional profile information, enhancing customization.
     • SEO Purpose: Enhances profile customization by allowing users to define additional data fields.
     • How to Use: Use custom key-value pairs to include unique information in profiles, improving customization and relevance.
169. User Visible Stats (AppsPeopleOzExternalMergedpeopleapiUserVisibleStats)
     • Description: Deprecated in favor of ProfileStats, this field provided statistics visible to the requester, such as incoming edges and views.
     • SEO Purpose: N/A (deprecated).
     • How to Use: Use ProfileStats instead for managing and viewing profile statistics.
170. Visible to Guests (AppsPeopleOzExternalMergedpeopleapiVisibleToGuests)
     • Description: Stores metadata information for contacts that are visible to guests, including annotation IDs and product sources.
     • SEO Purpose: Enhances data visibility and access control by managing guest-visible contacts.
     • How to Use: Maintain accurate metadata for guest-visible contacts to ensure appropriate access and visibility.
171. Web Contacts Extended Data (AppsPeopleOzExternalMergedpeopleapiWebContactsExtendedData)
     • Description: Indicates whether a person is not completed on the Contacts client-side.
     • SEO Purpose: Helps identify incomplete contact profiles, ensuring data accuracy and completeness.
     • How to Use: Use this field to identify and complete missing contact information, improving data integrity.
172. Website (AppsPeopleOzExternalMergedpeopleapiWebsite)
     • Description: Represents website information, including type, value, and formatted type. Supports various website categories like home, work, blog, profile, etc.
     • SEO Purpose: Enhances profile completeness and connectivity by including relevant website links.
     • How to Use: Ensure website information is accurate and categorized correctly to improve profile richness and connectivity.
173. Website Relationship Info (AppsPeopleOzExternalMergedpeopleapiWebsiteRelationshipInfo)
     • Description: Provides information about the relationship of websites to the user, such as contributor roles.
     • SEO Purpose: Enhances profile richness by detailing the user’s relationship with different websites.
     • How to Use: Include relationship information for websites to provide context and improve profile completeness.
174. YouTube Extended Data (AppsPeopleOzExternalMergedpeopleapiYoutubeExtendedData)
     • Description: Extension data for use in YouTube Product Profile, enhancing profile information for YouTube users.
     • SEO Purpose: Enhances YouTube profiles by including detailed YouTube-specific data.
     • How to Use: Integrate YouTube extended data to provide comprehensive and accurate profiles for YouTube users.
175. Supported Features (AssistantApiActionV2SupportedFeatures)
     • Description: This ranking factor includes the features supported by the ActionV2 protocol. As the system transitions to the ConversationProto for all surfaces, this message will be phased out.
     • SEO Purpose: Ensures compatibility and optimization for features supported by ActionV2 protocol, which can influence search visibility and interaction.
     • How to Use: Align your content and features with the supported capabilities to ensure optimal integration and performance on Google’s platforms.
176. Android Intent Capabilities (AssistantApiAndroidIntentCapabilities)
     • Description: Defines the capabilities related to Android intent support, listing the Android package names that support specific intents.
     • SEO Purpose: Enhances user experience by ensuring proper intent support for Android devices, impacting usability and satisfaction.
     • How to Use: Ensure your application supports the relevant Android intents to maximize compatibility and functionality on Android devices.
177. App Capabilities (AssistantApiAppCapabilities)
     • Description: Describes the capabilities of installed apps on the device, reported to the server for better integration and functionality.
     • SEO Purpose: Optimizes app functionality and integration by accurately reporting app capabilities, enhancing user experience.
     • How to Use: Regularly update and report your app’s capabilities to ensure seamless integration and performance on supported devices.
178. Incremental App Capabilities (AssistantApiAppCapabilitiesDelta)
     • Description: Details the incremental changes in app capabilities, such as installation or deletion, for more precise reporting and updates.
     • SEO Purpose: Keeps app capabilities up-to-date, ensuring accurate and real-time information about app functionalities.
     • How to Use: Implement mechanisms to report incremental changes in app capabilities to maintain current and accurate app data.
179. App Control Support (AssistantApiAppControlSupport)
     • Description: Indicates whether app control features are enabled or if sending messages through AppControl/SD flow is suppressed for specific devices.
     • SEO Purpose: Improves app control and user interaction by managing the enablement of app control features.
     • How to Use: Enable app control features where appropriate, and manage suppression settings to optimize user interaction and app functionality.
180. App Integrations Settings (AssistantApiAppIntegrationsSettings)
     • Description: Contains privacy settings used for app integrations and implicit requests, ensuring user data privacy and compliance.
     • SEO Purpose: Enhances user trust and compliance by adhering to privacy settings for app integrations.
     • How to Use: Configure and manage app integration settings to respect user privacy and comply with relevant regulations and guidelines.
181. Continued Presence Support (AssistantApiAssistantContinuedPresenceSupport)
     • Description: Indicates scenarios where the assistant’s continued presence can be shown as a plate, without including personal identifiable information.
     • SEO Purpose: Enhances user interaction by providing continued presence indicators in a non-intrusive manner.
     • How to Use: Implement continued presence indicators in your applications to improve user engagement and interaction.
182. Audio Input Capabilities (AssistantApiAudioInput)
     • Description: Represents the audio input features of the device, including types of audio input supported and privacy circumstances.
     • SEO Purpose: Ensures accurate and optimal use of audio input capabilities, enhancing voice interaction and user experience.
     • How to Use: Integrate and optimize audio input features according to device capabilities to improve voice interactions.
183. Audio Output Capabilities (AssistantApiAudioOutput)
     • Description: Details the audio output features of the device, covering types of audio output supported and privacy aspects.
     • SEO Purpose: Enhances audio output quality and compliance, improving overall user experience.
     • How to Use: Utilize and optimize audio output features according to device specifications to deliver superior audio experiences.
184. Bluetooth Capabilities (AssistantApiBluetoothCapabilities)
     • Description: Defines Bluetooth capabilities related to feature usage, enhancing connectivity and functionality.
     • SEO Purpose: Improves device interoperability and user experience by accurately supporting Bluetooth features.
     • How to Use: Ensure your applications support the relevant Bluetooth capabilities for seamless connectivity and enhanced functionality.
185. Call Capabilities (AssistantApiCallCapabilities)
     • Description: Represents the call capabilities supported by a surface, ensuring optimal call functionalities.
     • SEO Purpose: Enhances communication features by supporting relevant call capabilities, improving user satisfaction.
     • How to Use: Implement and optimize call functionalities based on the supported capabilities to enhance communication features.
186. Camera Capabilities (AssistantApiCameraCapabilities)
     • Description: Represents the camera features supported by the device, ensuring optimal use of camera functionalities.
     • SEO Purpose: Improves media capture and user experience by supporting camera features.
     • How to Use: Utilize and optimize camera capabilities according to device specifications to enhance media capture experiences.
187. Camera Receiver Capabilities (AssistantApiCameraReceiverCapabilities)
     • Description: Details the capabilities of devices running camera receiver apps, enhancing media reception functionalities.
     • SEO Purpose: Ensures optimal media reception by accurately supporting camera receiver capabilities.
     • How to Use: Implement and optimize camera receiver functionalities to improve media reception and user experience.
188. Car Assistant Capabilities (AssistantApiCarAssistantCapabilities)
     • Description: Represents the capabilities associated with assistants on auto surfaces, distinct from other auto-related settings and cloud information.
     • SEO Purpose: Enhances in-car assistant functionalities, improving user interaction and experience.
     • How to Use: Integrate and optimize assistant capabilities for auto surfaces to enhance in-car assistant functionalities.
189. Car Settings Capabilities (AssistantApiCarSettingsCapabilities)
     • Description: Represents the capabilities related to assistant settings on auto surfaces, ensuring optimal in-car assistant settings.
     • SEO Purpose: Enhances user experience by supporting relevant in-car assistant settings.
     • How to Use: Implement and manage assistant settings for auto surfaces to optimize in-car assistant functionalities.
190. Cast Assistant Setting Linking Result (AssistantApiCastAssistantSettingLinkingResult)
     • Description: Indicates the cast linking status for ATV surfaces, derived from Cast Orchestration Server error messages for data profiling.
     • SEO Purpose: Ensures seamless casting capabilities and troubleshooting by monitoring linking status.
     • How to Use: Monitor and manage cast linking statuses to ensure optimal casting functionalities and address issues promptly.
191. Cast Capabilities (AssistantApiCastCapabilities)
     • Description: Represents the casting capabilities pertinent to the device, enhancing media casting functionalities.
     • SEO Purpose: Improves media streaming and casting experiences by supporting relevant casting capabilities.
     • How to Use: Ensure your applications support the casting capabilities to deliver seamless media streaming experiences.
192. Device Modify Setting Client Operation Property (AssistantApiClientOpPropertiesDeviceModifySettingClientOpProperty)
     • Description: Describes the properties of the device.MODIFY_SETTING client operation, stored in the SupportedClientOp proto.
     • SEO Purpose: Enhances device setting modification functionalities, improving user control and interaction.
     • How to Use: Implement and optimize setting modification functionalities based on the supported client operation properties.
193. Provider Open Client Operation Property (AssistantApiClientOpPropertiesProviderOpenClientOpProperty)
     • Description: Describes the properties of the provider.OPEN client operation, stored in the SupportedClientOp proto.
     • SEO Purpose: Improves provider-specific operations and interactions by supporting relevant client operation properties.
     • How to Use: Implement and optimize provider-specific operations based on the supported client operation properties.
194. Clock Capabilities (AssistantApiClockCapabilities)
     • Description: Describes the clock capabilities of the device, including the maximum number of supported alarms and timers.
     • SEO Purpose: Enhances time management features by supporting relevant clock capabilities.
     • How to Use: Implement and manage clock capabilities to optimize alarm and timer functionalities on devices.
195. Communication UI Capabilities (AssistantApiCommunicationUiCapabilities)
     • Description: Represents the UI capabilities for rendering communication features on surfaces, enhancing user interaction.
     • SEO Purpose: Improves communication interfaces and user experience by supporting relevant UI capabilities.
     • How to Use: Design and optimize communication UIs based on supported capabilities to enhance user interaction.
196. Contact Lookup Capabilities (AssistantApiContactLookupCapabilities)
     • Description: Indicates whether contact lookup should be routed to a tethered device if the primary device does not support it.
     • SEO Purpose: Ensures reliable contact lookup functionalities, improving user convenience and experience.
     • How to Use: Implement contact lookup routing mechanisms to ensure seamless contact lookup functionalities across devices.
197. Android App Information (AssistantApiCoreTypesAndroidAppInfo)
     • Description: Provides information about Android apps, including activities and app-specific details.
     • SEO Purpose: Enhances app integration and functionality by accurately supporting Android app information.
     • How to Use: Ensure your applications provide detailed and accurate app information for optimal integration and functionality on Android devices.
198. Calendar Event (AssistantApiCoreTypesCalendarEvent)
     • Description: Contains information about calendar events, such as title, start time, and end time.
     • SEO Purpose: Enhances calendar functionalities by supporting detailed event information.
     • How to Use: Implement and manage calendar event functionalities to ensure accurate and useful event information.
199. Cast App Information (AssistantApiCoreTypesCastAppInfo)
     • Description: Provides information about cast apps, enhancing media casting capabilities.
     • SEO Purpose: Improves casting functionalities by supporting detailed cast app information.
     • How to Use: Ensure your cast applications provide detailed and accurate app information for optimal casting functionalities.
200. Chrome OS App Information (AssistantApiCoreTypesChromeOsAppInfo)
     • Description: Provides information about Chrome OS apps, enhancing app integration and functionality on Chrome OS devices.
     • SEO Purpose: Enhances app integration and functionality on Chrome OS by supporting detailed app information.
     • How to Use: Ensure your Chrome OS applications provide detailed and accurate app information for optimal functionality and integration.
201. Cloud Provider Information (AssistantApiCoreTypesCloudProviderInfo)
     • Description: Contains information about third-party cloud providers, enhancing cloud service integration.
     • SEO Purpose: Improves cloud service integration by supporting detailed provider information.
     • How to Use: Ensure your cloud services provide detailed and accurate provider information for optimal integration and functionality.
202. Color Representation (AssistantApiCoreTypesColor)
     • Description: Represents a color in the RGBA color space, mirroring the google.type.Color message.
     • SEO Purpose: Enhances visual presentation by supporting accurate color representation.
     • How to Use: Utilize accurate color representations to enhance the visual appeal and consistency of your applications.
203. Device Config (AssistantApiCoreTypesDeviceConfig)
     • Description: Provides identification information for third-party devices integrating with the assistant, populated by the third party.
     • SEO Purpose: Enhances device integration and functionality by supporting accurate device configuration information.
     • How to Use: Ensure your devices provide detailed and accurate configuration information for optimal integration with Google Assistant.
204. Device ID (AssistantApiCoreTypesDeviceId)
     • Description: Specifies the identifier of a device, with considerations for equality and uniqueness.
     • SEO Purpose: Ensures accurate device identification and interaction by supporting detailed device ID information.
     • How to Use: Implement device identification mechanisms to ensure accurate and reliable device interactions.
205. Device User Identity (AssistantApiCoreTypesDeviceUserIdentity)
     • Description: Contains information that helps identify a device-user pair, useful for various interactions like broadcast replies.
     • SEO Purpose: Enhances user identification and interaction by supporting accurate device-user identity information.
     • How to Use: Utilize device-user identity information to improve user-specific interactions and functionalities.
206. Home App Information (AssistantApiCoreTypesHomeAppInfo)
     • Description: Provides information about home apps, enhancing integration and functionality for smart home devices.
     • SEO Purpose: Enhances smart home functionalities by supporting detailed home app information.
     • How to Use: Ensure your smart home applications provide detailed and accurate information for optimal integration and functionality.
207. Image Representation (AssistantApiCoreTypesImage)
     • Description: Represents data about an image or photo, enhancing media handling capabilities.
     • SEO Purpose: Improves media handling and presentation by supporting detailed image information.
     • How to Use: Utilize accurate image representations to enhance media handling and visual presentation in your applications.
208. Internal Provider Information (AssistantApiCoreTypesInternalProviderInfo)
     • Description: Provides information for targeting a feature provided directly by the Assistant surface.
     • SEO Purpose: Enhances feature targeting and functionality by supporting detailed internal provider information.
     • How to Use: Ensure your features provide detailed and accurate internal provider information for optimal targeting and functionality.
209. iOS App Information (AssistantApiCoreTypesIosAppInfo)
     • Description: Provides information about iOS apps, enhancing app integration and functionality on iOS devices.
     • SEO Purpose: Enhances app integration and functionality on iOS by supporting detailed app information.
     • How to Use: Ensure your iOS applications provide detailed and accurate app information for optimal functionality and integration.
210. KaiOS App Information (AssistantApiCoreTypesKaiOsAppInfo)
     • Description: Provides information about KaiOS apps, enhancing app integration and functionality on KaiOS devices.
     • SEO Purpose: Enhances app integration and functionality on KaiOS by supporting detailed app information.
     • How to Use: Ensure your KaiOS applications provide detailed and accurate app information for optimal functionality and integration.
211. Location Coordinates (AssistantApiCoreTypesLocationCoordinates)
     • Description: Provides geographic coordinate information for locations, enhancing location-based functionalities.
     • SEO Purpose: Improves location-based services by supporting accurate coordinate information.
     • How to Use: Utilize accurate location coordinates to enhance location-based services and functionalities in your applications.
212. Message Notification (AssistantApiCoreTypesMessageNotification)
     • Description: Captures the contents of a messaging app notification, typically part of a conversation thread.
     • SEO Purpose: Enhances messaging functionalities by supporting detailed notification information.
     • How to Use: Implement detailed message notification handling to improve user interaction and communication features.
213. Notification Entry (AssistantApiCoreTypesMessageNotificationNotificationEntry)
     • Description: Details the structure of each notification in the MessageNotification bundle, including sender information.
     • SEO Purpose: Enhances notification handling by supporting detailed notification entry information.
     • How to Use: Utilize detailed notification entries to improve notification handling and user interaction in your applications.
214. Provider Information (AssistantApiCoreTypesProvider)
     • Description: Provides information about providers like Spotify or iHeartRadio, enhancing media service integration.
     • SEO Purpose: Improves media service integration by supporting detailed provider information.
     • How to Use: Ensure your media services provide detailed and accurate provider information for optimal integration and functionality.
215. Provider Delta (AssistantApiCoreTypesProviderDelta)
     • Description: Represents the incremental change in provider information, such as installation or deletion of apps.
     • SEO Purpose: Keeps provider information up-to-date, ensuring accurate and real-time data about media services.
     • How to Use: Implement mechanisms to report incremental changes in provider information to maintain current and accurate data.
216. Ringtone Task Metadata (AssistantApiCoreTypesRingtoneTaskMetadata)
     • Description: Describes task metadata information for ringtones, including specific details for character alarms, ML-generated alarms, and routine alarms.
     • SEO Purpose: Enhances alarm and ringtone functionalities by supporting detailed task metadata information.
     • How to Use: Utilize detailed ringtone task metadata to enhance alarm and ringtone features in your applications.
217. SIP Provider Information (AssistantApiCoreTypesSipProviderInfo)
     • Description: Provides information for providers that use SIP (Session Initiation Protocol) for multimedia communication sessions.
     • SEO Purpose: Improves communication services by supporting detailed SIP provider information.
     • How to Use: Ensure your communication services provide detailed and accurate SIP provider information for optimal functionality and integration.
218. Surface Identity (AssistantApiCoreTypesSurfaceIdentity)
     • Description: Contains information that helps the server identify the surface, replacing the User-Agent string.
     • SEO Purpose: Enhances surface identification and interaction by supporting detailed surface identity information.
     • How to Use: Utilize accurate surface identity information to improve surface-specific functionalities and interactions.
219. Surface Type (AssistantApiCoreTypesSurfaceType)
     • Description: Specifies the types of device surfaces, ensuring accurate identification and interaction for different surfaces.
     • SEO Purpose: Improves device interaction by supporting detailed surface type information.
     • How to Use: Implement surface type identification to enhance device-specific functionalities and interactions.
220. Surface Version (AssistantApiCoreTypesSurfaceVersion)
     • Description: Specifies the version of the surface/client, tracking major and minor version numbers.
     • SEO Purpose: Enhances version tracking and compatibility by supporting detailed surface version information.
     • How to Use: Utilize surface version information to ensure compatibility and optimize functionalities for different versions.
221. Web Provider Information (AssistantApiCoreTypesWebProviderInfo)
     • Description: Provides web information of the provider, enhancing web service integration.
     • SEO Purpose: Improves web service integration by supporting detailed provider information.
     • How to Use: Ensure your web services provide detailed and accurate provider information for optimal integration and functionality.
222. Third-Party Custom NLU Information (AssistantApiCoreTypesWebProviderInfoThirdPartyCustomNluInfo)
     • Description: Contains information about third-party custom NLU (Natural Language Understanding) agents, including locale and version.
     • SEO Purpose: Enhances natural language processing capabilities by supporting detailed third-party NLU information.
     • How to Use: Utilize detailed NLU information to improve natural language processing and interaction features in your applications.
223. Cross Device Execution Capability (AssistantApiCrossDeviceExecutionCapability)
     • Description: Describes capabilities for executing actions across devices, including local connectivity and remote cast media support.
     • SEO Purpose: Enhances cross-device functionality by supporting detailed execution capabilities.
     • How to Use: Implement cross-device execution features to improve connectivity and functionality across multiple devices.
224. Data Validate Capabilities (AssistantApiDataValidateCapabilities)
     • Description: Indicates whether data validation should be routed to a tethered device if the primary device does not support it.
     • SEO Purpose: Ensures reliable data validation functionalities by supporting tethered device routing.
     • How to Use: Implement data validation routing mechanisms to ensure seamless data validation functionalities across devices.
225. Date (AssistantApiDate)
     • Description: Represents a Gregorian calendar date, enhancing date-related functionalities.
     • SEO Purpose: Improves date handling and representation by supporting accurate Gregorian calendar dates.
     • How to Use: Utilize accurate date representations to enhance date-related functionalities in your applications.
226. DateTime (AssistantApiDateTime)
     • Description: Combines a date and civil time (relative to a given timezone), enhancing date-time specifications.
     • SEO Purpose: Improves date-time handling and representation by supporting accurate date-time specifications.
     • How to Use: Utilize accurate date-time representations to enhance date-time functionalities in your applications.
227. DateTime Range (AssistantApiDateTimeRange)
     • Description: Represents a range of time with specified start and end date-times, enhancing time range specifications.
     • SEO Purpose: Improves time range handling and representation by supporting accurate date-time ranges.
     • How to Use: Utilize accurate date-time range representations to enhance time range functionalities in your applications.
228. Device Capabilities (AssistantApiDeviceCapabilities)
     • Description: Describes the capabilities of a surface, based on device hardware, software, and status.
     • SEO Purpose: Enhances device interaction and functionality by supporting detailed device capability information.
     • How to Use: Utilize detailed device capability information to optimize functionalities and interactions based on device specifications.
229. Duration (AssistantApiDuration)
     • Description: Represents a fixed-length span of time, enhancing time duration specifications.
     • SEO Purpose: Improves time duration handling and representation by supporting accurate duration specifications.
     • How to Use: Utilize accurate duration representations to enhance time-related functionalities in your applications.
230. Feature-Specific Action Support (AssistantApiFeatureSpecificActionSupport)
     • Description: Indicates whether the client supports clarification suggestion chips, enhancing action support functionalities.
     • SEO Purpose: Improves feature-specific interactions by supporting clarification suggestion chips.
     • How to Use: Implement feature-specific action support to enhance user interaction and experience.
231. Fitness Feature Support (AssistantApiFitnessFeatureSupport)
     • Description: Lists the fitness activity types supported by the client, enhancing fitness functionalities.
     • SEO Purpose: Enhances fitness tracking and interaction by supporting detailed fitness activity information.
     • How to Use: Implement and optimize fitness features based on supported activity types to enhance user fitness tracking and interaction.
232. Fluid Actions Support (AssistantApiFluidActionsSupport)
     • Description: Specifies the parameters used to sync state with the server for fluid actions, enhancing action support functionalities.
     • SEO Purpose: Improves action synchronization and interaction by supporting detailed fluid action parameters.
     • How to Use: Implement fluid action support to enhance action synchronization and user interaction.
233. GACS Capabilities (AssistantApiGacsCapabilities)
     • Description: Represents the capabilities of Google Assistant Conversation Service (GACS) devices, including supported actions and response size limitations.
     • SEO Purpose: Enhances conversational interactions by supporting detailed GACS capabilities.
     • How to Use: Ensure your applications support relevant GACS capabilities to optimize conversational interactions and response handling.
234. GCM Capabilities (AssistantApiGcmCapabilities)
     • Description: Represents capabilities related to Google Cloud Messaging (GCM), enhancing messaging functionalities.
     • SEO Purpose: Improves messaging capabilities by supporting detailed GCM information.
     • How to Use: Ensure your messaging services support relevant GCM capabilities to optimize messaging functionalities.
235. Gesture Capabilities (AssistantApiGestureCapabilities)
     • Description: Represents the gesture capabilities related to specific interactions, enhancing user interaction functionalities.
     • SEO Purpose: Enhances user interaction by supporting detailed gesture capabilities.
     • How to Use: Implement and optimize gesture functionalities based on supported capabilities to enhance user interaction.
236. Guest Access Output (AssistantApiGuestAccessOutput)
     • Description: Represents access settings for guests, enhancing user access management functionalities.
     • SEO Purpose: Improves access management by supporting detailed guest access settings.
     • How to Use: Implement and manage guest access settings to optimize user access control and interaction.
237. Immersive Canvas Support (AssistantApiImmersiveCanvasSupport)
     • Description: Indicates whether the client supports confirmation messages and pause signals in Immersive Canvas actions.
     • SEO Purpose: Enhances immersive experiences by supporting detailed canvas action functionalities.
     • How to Use: Implement and optimize immersive canvas support to enhance user interaction and experiences.
238. JWN Capabilities (AssistantApiJwnCapabilities)
     • Description: This ranking factor relates to the detection and verification of the versions of JWN (Just a Web Node) libraries present on a client. It ensures that the right libraries are used for proper functionality.
     • SEO Purpose: Ensuring up-to-date and compatible JWN libraries helps in improving the website’s performance, speed, and compatibility, which are crucial factors for SEO.
     • How to Use: Regularly update and verify the JWN libraries used on your site to ensure compatibility and performance. Implement automated checks to keep the libraries current.
239. Lens Perception Capabilities (AssistantApiLensPerceptionCapabilities)
     • Description: This attribute pertains to the image understanding capabilities of Google Lens, including object recognition, text recognition, and translation within images.
     • SEO Purpose: Enhancing image recognition and understanding can improve the accuracy of image-related search results, leading to better visibility and higher rankings.
     • How to Use: Optimize images on your website with clear, relevant content. Use high-quality images and ensure they are properly tagged and described to facilitate better recognition by Google Lens.
240. Live TV Channel Capabilities (AssistantApiLiveTvChannelCapabilities)
     • Description: This attribute lists the capabilities related to live TV channels, including available channels by provider, channel identifiers, and deep links to the live player apps.
     • SEO Purpose: Providing accurate and detailed live TV channel information can enhance user experience and engagement, which are important for SEO.
     • How to Use: Ensure that the live TV channel information on your website is accurate and up-to-date. Provide deep links to live content and optimize the metadata for better search visibility.
241. Location Capabilities (AssistantApiLocationCapabilities)
     • Description: This factor indicates whether GPS is available on the device, which can influence location-based search results and services.
     • SEO Purpose: Location capabilities are crucial for local SEO, as they help in providing more accurate and relevant search results based on the user’s location.
     • How to Use: Optimize your website for local search by including location-specific keywords and ensuring that your business information is consistent across all local listings and directories.
242. Media Control Support (AssistantApiMediaControlSupport)
     • Description: This attribute indicates whether media control actions can be performed without confirmations to avoid interruptions during media playback.
     • SEO Purpose: Improving user experience by reducing interruptions during media playback can lead to longer engagement times and lower bounce rates, positively affecting SEO.
     • How to Use: Configure media control settings to minimize interruptions. Ensure that media content is easily accessible and can be controlled seamlessly to enhance user experience.
243. Message Capabilities (AssistantApiMessageCapabilities)
     • Description: This attribute defines the messaging capabilities of a device, including fallback options to tethered devices and preferred targeting for message sending.
     • SEO Purpose: Efficient and reliable messaging capabilities can improve user interaction and satisfaction, which can contribute to better SEO rankings.
     • How to Use: Ensure that messaging features are fully functional and optimized for performance. Implement fallback options to maintain reliability and enhance user experience.
244. Movement Capabilities (AssistantApiMovementCapabilities)
     • Description: This ranking factor indicates the mobility level of a device, such as whether it is stationary like a TV or highly mobile like an automobile.
     • SEO Purpose: Understanding device mobility can help tailor content and services to the user’s context, improving relevance and user experience, which are important for SEO.
     • How to Use: Customize content delivery based on the device’s mobility. For stationary devices, focus on static content, while for mobile devices, provide dynamic and context-aware content.
245. Notification Output Restrictions (AssistantApiNotificationOutputRestrictions)
     • Description: This attribute defines user-configurable permissions for what notifications a device is allowed to output, ensuring user privacy and control.
     • SEO Purpose: Respecting user notification preferences can improve user trust and satisfaction, indirectly benefiting SEO through better user engagement.
     • How to Use: Implement and respect user preferences for notifications. Provide clear options for users to configure their notification settings to enhance their experience and trust.
246. OEM Capabilities (AssistantApiOemCapabilities)
     • Description: This factor encapsulates the action capabilities of OEM devices, combining data from various sources to determine the functionalities available for query understanding.
     • SEO Purpose: Ensuring that OEM devices have the right capabilities can enhance the accuracy and relevance of search results, improving user satisfaction and SEO performance.
     • How to Use: Regularly update and verify the capabilities of OEM devices to ensure they are fully functional and optimized for query processing.
247. On-Device Assistant Capabilities (AssistantApiOnDeviceAssistantCapabilities)
     • Description: This factor outlines the capabilities of the on-device assistant, detailing what functions and features the assistant can perform directly on the device without needing to connect to external services.
     • SEO Purpose: Understanding and optimizing for on-device assistant capabilities can enhance user interaction and satisfaction, leading to improved user engagement metrics which can positively affect SEO rankings.
     • How to Use: Ensure your website and services are optimized for voice search and on-device interactions. Regularly update content and functionalities to align with the capabilities of on-device assistants.
248. Smart Home Capabilities (AssistantApiOnDeviceSmartHomeCapabilities)
     • Description: This attribute defines the smart home capabilities available on the device, indicating what smart home functions can be controlled or monitored via the on-device assistant.
     • SEO Purpose: Optimizing for smart home interactions can improve visibility and usability for users seeking smart home solutions, enhancing the site’s relevance and engagement metrics.
     • How to Use: Integrate and optimize smart home-related content and functionalities. Ensure compatibility with smart home devices and regularly update information on supported features and capabilities.
249. On-Device Storage Capabilities (AssistantApiOnDeviceStorageCapabilities)
     • Description: This factor details the storage capabilities available on the device, including the amount and type of storage that can be utilized for various applications and data.
     • SEO Purpose: Efficient management and optimization of on-device storage can enhance the performance and reliability of the assistant, contributing to better user experience and engagement.
     • How to Use: Optimize your website and applications to use storage efficiently. Provide clear guidance on managing storage and highlight features that benefit from ample storage capabilities.
250. Output Restrictions (AssistantApiOutputRestrictions)
     • Description: This attribute encompasses user-configurable permissions that dictate what types of content and data the device is allowed to output, ensuring compliance with user preferences and privacy settings.
     • SEO Purpose: Respecting output restrictions enhances user trust and satisfaction, leading to improved user retention and positive engagement signals, which can benefit SEO.
     • How to Use: Implement and respect user output preferences. Clearly communicate how users can configure these settings and ensure your content complies with these restrictions.
251. Proactive Output (AssistantApiProactiveOutput)
     • Description: This factor involves the proactive output capabilities of the assistant, determining how and when the assistant can proactively provide information and notifications to the user.
     • SEO Purpose: Proactively delivering relevant content can enhance user engagement and satisfaction, leading to better interaction metrics and potentially higher SEO rankings.
     • How to Use: Optimize content to be proactively delivered by the assistant. Ensure timely and relevant updates to keep users engaged and informed.
252. Protobuf (AssistantApiProtobuf)
     • Description: This simple protocol buffer is used to transmit arbitrary data over the wire, allowing for flexible and efficient data transmission without requiring the data type to be compiled into the binary.
     • SEO Purpose: Efficient data transmission improves the performance and responsiveness of applications, enhancing user experience and engagement metrics.
     • How to Use: Utilize protobuf for efficient data handling in your applications. Ensure that your data structures are optimized for quick transmission and processing.
253. Recurrence (AssistantApiRecurrence)
     • Description: This attribute specifies date-based recurrences for events, defining a sequence of dates on which an event repeats, based on a set of constraints.
     • SEO Purpose: Accurate handling of recurring events ensures that users receive timely and relevant information, improving engagement and satisfaction.
     • How to Use: Clearly define and manage recurring events on your website or application. Ensure that event details are accurately presented and updated.
254. Robin Capabilities (AssistantApiRobinCapabilities)
     • Description: This factor describes the capabilities and parameters of the Robin client, including the status of its availability and user opt-in preferences.
     • SEO Purpose: Ensuring that Robin capabilities are accurately represented can improve user interactions and satisfaction, positively impacting SEO.
     • How to Use: Regularly update and verify the status of Robin capabilities. Provide clear information and options for users to opt-in or out of using Robin features.
255. Screen Capabilities (AssistantApiScreenCapabilities)
     • Description: This attribute represents the screen-related features of the device, including screen size, resolution, and privacy features, which impact how content is displayed.
     • SEO Purpose: Optimizing for various screen capabilities ensures that content is displayed correctly and attractively on all devices, enhancing user experience and engagement.
     • How to Use: Ensure your website is responsive and adapts to different screen sizes and resolutions. Optimize images and media for various display capabilities.
256. Selina Capabilities (AssistantApiSelinaCapabilites)
     • Description: This factor details the Soli capabilities on Elaine devices, including gesture recognition and sleep sensing, which enhance the device’s interactive features.
     • SEO Purpose: Leveraging advanced interaction capabilities can enhance user engagement and satisfaction, leading to better SEO performance.
     • How to Use: Integrate and optimize content for gesture recognition and other advanced interaction features. Provide clear guidance on how to use these capabilities for an enhanced user experience.
257. Ambient Settings (AssistantApiSettingsAmbientSettings)
     • Description: This attribute involves settings related to ambient modes, such as displaying personal photos, recent highlights, and other ambient features that enhance the device’s idle state.
     • SEO Purpose: Optimizing ambient settings can improve user engagement during idle times, providing additional opportunities for content visibility and interaction.
     • How to Use: Configure ambient settings to display relevant and engaging content. Regularly update the content to keep it fresh and interesting for users.
258. App Capabilities (AssistantApiSettingsAppCapabilities)
     • Description: This factor encompasses the capabilities associated with Assistant settings on devices, detailing what app-related functions can be controlled or accessed.
     • SEO Purpose: Ensuring that app capabilities are optimized can improve user interactions and satisfaction, positively affecting SEO metrics.
     • How to Use: Regularly update and optimize app settings. Provide clear information on the available app capabilities and how users can utilize them.
259. Auto Framing Settings (AssistantApiSettingsAutoFramingSettings)
     • Description: This attribute pertains to settings related to auto-framing features on devices, which can automatically adjust the framing of the camera to keep subjects in view.
     • SEO Purpose: Optimizing auto-framing settings can enhance user-generated content quality, leading to higher engagement and improved user experience.
     • How to Use: Configure auto-framing settings to ensure optimal performance during video calls or content creation. Educate users on how to enable and customize these settings for best results.
260. Carrier Call Device Settings (AssistantApiSettingsCarrierCallDeviceSettings)
     • Description: This factor involves settings related to carrier call functionalities on the device, detailing how carrier calls are managed and configured.
     • SEO Purpose: Optimizing carrier call settings can enhance call quality and reliability, leading to better user satisfaction and engagement.
     • How to Use: Ensure that carrier call settings are properly configured and regularly updated. Provide clear instructions for users to manage their call settings effectively.
261. Communications Filter (AssistantApiSettingsCommunicationsFilter)
     • Description: This attribute specifies which communication features can be used on the device, allowing for customization and restriction based on user preferences.
     • SEO Purpose: Properly managing communication filters ensures that users receive relevant and wanted communications, improving user trust and engagement.
     • How to Use: Implement and respect user preferences for communication filters. Regularly review and update communication settings to align with user needs and preferences.
262. Device Downtime Settings (AssistantApiSettingsDeviceDowntimeSettings)
     • Description: This factor defines times when most features on a device are disabled for certain users, usually to encourage breaks or limit usage during specific periods.
     • SEO Purpose: Managing downtime settings helps in promoting healthy device usage, leading to better user satisfaction and potentially improving engagement metrics.
     • How to Use: Configure downtime settings to align with user needs, such as bedtime or study time. Provide easy options for users to customize their downtime schedules.
263. Device Feature Filters (AssistantApiSettingsDeviceFeatureFilters)
     • Description: This attribute defines restrictions on particular device features for a set of users, ensuring that certain features are either enabled or disabled based on user profiles.
     • SEO Purpose: Optimizing device feature filters ensures that users have access to relevant features, enhancing their experience and engagement with the device.
     • How to Use: Regularly review and update feature filters to match user preferences and needs. Provide clear guidance on how users can manage their feature settings.
264. Device Logs Opt-In (AssistantApiSettingsDeviceLogsOptIn)
     • Description: This factor indicates whether crash logs and device logs can be uploaded and enabled, which is crucial for troubleshooting and improving device performance.
     • SEO Purpose: Enabling device logs helps in identifying and resolving issues quickly, leading to improved device performance and user satisfaction.
     • How to Use: Encourage users to opt-in for device logs by explaining the benefits. Ensure that log data is used responsibly and transparently to maintain user trust.
265. Cross-Surface Availability (AssistantApiSettingsDeviceSettingsCrossSurfaceAvailability)
     • Description: This attribute involves the availability of settings across different surfaces or devices, ensuring a consistent user experience across multiple platforms.
     • SEO Purpose: Consistent settings across devices enhance user experience and convenience, leading to better engagement and satisfaction.
     • How to Use: Ensure that settings are synchronized across all user devices. Provide clear instructions on how users can manage their settings across multiple platforms.
266. Device Supervision Settings (AssistantApiSettingsDeviceSupervisionSettings)
     • Description: This factor specifies times when a device should not respond to certain users, such as during downtime periods or when specific feature restrictions are in place.
     • SEO Purpose: Effective supervision settings promote healthy device usage habits, improving overall user satisfaction and engagement.
     • How to Use: Configure supervision settings to align with user needs, such as parental controls or work-related restrictions. Provide easy options for users to customize their supervision settings.
267. Downtime Period (AssistantApiSettingsDowntimePeriod)
     • Description: This attribute specifies a period when downtime should be enabled, detailing start and end times, and ensuring that certain features are disabled during this period.
     • SEO Purpose: Managing downtime periods effectively helps in promoting healthy usage habits and improving user satisfaction.
     • How to Use: Set up downtime periods to align with user schedules, such as sleep or study times. Provide clear instructions on how users can customize their downtime settings.
268. Downtime Schedule (AssistantApiSettingsDowntimeSchedule)
     • Description: This factor specifies the schedule for downtime across different days of the week, allowing for detailed customization of when the device should be in downtime mode.
     • SEO Purpose: A well-managed downtime schedule promotes balanced device usage, leading to better user satisfaction and engagement.
     • How to Use: Configure downtime schedules to fit user lifestyles and routines. Provide easy-to-use tools for users to adjust their schedules as needed.
269. Duo Call Device Settings (AssistantApiSettingsDuoCallDeviceSettings)
     • Description: This attribute pertains to settings related to Google Duo call functionalities on the device, detailing how Duo calls are managed and configured.
     • SEO Purpose: Optimizing Duo call settings can enhance call quality and reliability, improving user satisfaction and engagement.
     • How to Use: Ensure that Duo call settings are properly configured and regularly updated. Provide clear instructions for users to manage their call settings effectively.
270. Feature Filters (AssistantApiSettingsFeatureFilters)
     • Description: This factor specifies which assistant features are allowed for a particular device or user account, enabling customization of the assistant’s capabilities.
     • SEO Purpose: Properly managing feature filters ensures that users have access to relevant features, enhancing their experience and engagement with the assistant.
     • How to Use: Regularly review and update feature filters to match user preferences and needs. Provide clear guidance on how users can manage their feature settings.
271. GCM Settings (AssistantApiSettingsGcmSettings)
     • Description: This attribute involves settings related to Google Cloud Messaging (GCM), including identifiers and package details used for managing notifications.
     • SEO Purpose: Efficient GCM settings management ensures reliable notification delivery, improving user engagement and satisfaction.
     • How to Use: Ensure that GCM settings are properly configured and regularly updated. Provide clear instructions for users to manage their notification settings effectively.
272. Home Graph Data (AssistantApiSettingsHomeGraphData)
     • Description: This factor pertains to data related to the home graph, which maps and manages smart home devices and their interactions.
     • SEO Purpose: Optimizing home graph data management enhances smart home integration and functionality, improving user satisfaction and engagement.
     • How to Use: Regularly update and verify home graph data to ensure accurate smart home interactions. Provide clear information on managing and configuring smart home devices.
273. Hospitality Card Settings (AssistantApiSettingsHospitalityCardSettings)
     • Description: This attribute involves settings related to hospitality cards, including configurations for UI modules and tutorials for media and photo gestures.
     • SEO Purpose: Enhancing hospitality card settings can improve user experience in hospitality environments, leading to better engagement and satisfaction.
     • How to Use: Configure hospitality card settings to provide relevant and useful information. Regularly update content and tutorials to keep them fresh and engaging for users.
274. Hospitality Card Configuration (AssistantApiSettingsHospitalityCardSettingsCardConfig)
     • Description: This factor involves the configuration settings for hospitality cards, detailing how different UI modules are set up for user interaction.
     • SEO Purpose: Properly configured hospitality cards can enhance user experience in hospitality environments, leading to increased engagement and satisfaction.
     • How to Use: Regularly update the UI modules to ensure they are user-friendly and engaging. Customize the hospitality cards based on user preferences and feedback.
275. YouTube Card Configuration (AssistantApiSettingsHospitalityCardSettingsYouTubeCardConfig)
     • Description: This attribute pertains to the configuration settings for YouTube video cards within hospitality cards, allowing customization of YouTube content presentation.
     • SEO Purpose: Optimizing YouTube card configurations can improve video engagement metrics, enhancing user interaction and satisfaction.
     • How to Use: Configure YouTube video cards to display relevant and engaging content. Regularly update the configurations to align with current trends and user preferences.
276. Hospitality Mode Configuration (AssistantApiSettingsHospitalityMode)
     • Description: This factor defines the configuration settings for hospitality mode on devices, ensuring that the device is tailored for use in hospitality environments.
     • SEO Purpose: Optimizing hospitality mode settings enhances the overall user experience in hospitality settings, leading to better engagement and satisfaction.
     • How to Use: Configure hospitality mode to meet the specific needs of the environment. Regularly update the settings to ensure they remain relevant and effective.
277. Hospitality Mode Branding (AssistantApiSettingsHospitalityModeBranding)
     • Description: This attribute involves the branding fields used to customize the user interface for hospitality mode, allowing for partner-specific branding elements.
     • SEO Purpose: Customizing branding in hospitality mode can strengthen brand recognition and improve user experience, leading to increased engagement.
     • How to Use: Integrate partner branding elements into the user interface. Regularly update the branding to ensure it aligns with the latest marketing and branding strategies.
278. Hotword Threshold Adjustment Factor (AssistantApiSettingsHotwordThresholdAdjustmentFactor)
     • Description: This factor contains the settings for adjusting the threshold at which the device recognizes hotwords, ensuring accurate speech detection.
     • SEO Purpose: Optimizing hotword detection can improve user interaction with voice-activated features, enhancing overall user satisfaction and engagement.
     • How to Use: Adjust the hotword threshold to balance between sensitivity and accuracy. Regularly test and update the settings to ensure optimal performance.
279. Internal Ancillary Device ID (AssistantApiSettingsInternalAncillaryDeviceId)
     • Description: This attribute represents the IDs of supporting devices connected to the main device, allowing for better integration and management.
     • SEO Purpose: Efficient management of ancillary devices can enhance device functionality and user experience, leading to better engagement metrics.
     • How to Use: Ensure all ancillary device IDs are correctly configured and updated. Provide clear instructions for users to manage connected devices.
280. Internal Version (AssistantApiSettingsInternalVersion)
     • Description: This factor represents the version of specific settings, ensuring that devices are running the correct and most recent configuration settings.
     • SEO Purpose: Keeping device settings updated ensures optimal performance and user experience, which can positively impact engagement and satisfaction.
     • How to Use: Regularly check and update the internal version of settings. Provide clear update instructions for users to maintain the latest configurations.
281. Kids Mode Configuration (AssistantApiSettingsKidsMode)
     • Description: This attribute defines the configuration for kids mode on the device, ensuring a child-friendly environment with appropriate content and restrictions.
     • SEO Purpose: Optimizing kids mode can enhance safety and suitability for younger users, improving parental satisfaction and user engagement.
     • How to Use: Configure kids mode to block inappropriate content and provide a safe browsing experience. Regularly update the settings based on feedback and new safety guidelines.
282. Labeled Downtime Schedule (AssistantApiSettingsLabeledDowntimeSchedule)
     • Description: This factor specifies a downtime schedule with a user-provided name, detailing when the device should limit functionality.
     • SEO Purpose: Properly managing downtime schedules promotes balanced device usage, leading to better user satisfaction and engagement.
     • How to Use: Configure labeled downtime schedules to align with user needs, such as sleep or study times. Provide tools for users to easily adjust their schedules.
283. Linked User Profile (AssistantApiSettingsLinkedUser)
     • Description: This attribute represents the profile of the user who has signed in on the device, ensuring personalized settings and preferences.
     • SEO Purpose: Personalized user profiles can enhance the user experience by providing relevant content and settings, leading to increased engagement.
     • How to Use: Ensure user profiles are accurately linked and updated. Provide easy-to-use tools for users to manage their profiles and preferences.
284. Marketplace Disclosure (AssistantApiSettingsMarketplaceDisclosure)
     • Description: This factor involves user confirmation of marketplace disclosures, ensuring compliance with legal and policy requirements.
     • SEO Purpose: Properly managing marketplace disclosures enhances user trust and compliance, leading to improved user satisfaction and engagement.
     • How to Use: Ensure users are clearly informed about marketplace disclosures and provide easy options for confirmation. Regularly update the disclosure content as needed.
285. Masquerade Mode (AssistantApiSettingsMasqueradeMode)
     • Description: This attribute defines the settings for guest mode on the device, allowing temporary access without altering the main user’s settings.
     • SEO Purpose: Optimizing guest mode ensures a seamless and secure experience for temporary users, enhancing overall satisfaction and engagement.
     • How to Use: Configure masquerade mode to provide necessary access while protecting main user data. Provide clear instructions for enabling and disabling guest mode.
286. Music Filter (AssistantApiSettingsMusicFilter)
     • Description: This factor specifies which music features and content are allowed on the device, ensuring that music playback aligns with user preferences.
     • SEO Purpose: Managing music filters improves user satisfaction by providing relevant music content, leading to better engagement.
     • How to Use: Regularly update music filter settings based on user feedback. Ensure that allowed music features and content align with user preferences.
287. News Filter (AssistantApiSettingsNewsFilter)
     • Description: This attribute involves the specification of which news features and content are allowed on the device, ensuring relevance and appropriateness.
     • SEO Purpose: Properly managed news filters enhance user engagement by providing relevant and preferred news content.
     • How to Use: Configure news filters to match user interests and preferences. Regularly update the settings based on user feedback and new content availability.
288. Notification Profile (AssistantApiSettingsNotificationProfile)
     • Description: This factor defines the notification profile for the device, detailing how and when notifications are delivered.
     • SEO Purpose: Optimizing notification settings ensures timely and relevant notifications, improving user engagement and satisfaction.
     • How to Use: Configure notification profiles to balance between relevance and frequency. Provide tools for users to customize their notification settings.
289. On-Device App Settings (AssistantApiSettingsOnDeviceAppSettings)
     • Description: This attribute involves settings related to on-device applications, including configurations for carrier calls and Duo calls.
     • SEO Purpose: Properly configured app settings enhance functionality and user experience, leading to better engagement.
     • How to Use: Regularly update app settings to ensure they are optimized for performance. Provide clear instructions for users to manage their app settings.
290. Personalization Metadata (AssistantApiSettingsPersonalizationMetadata)
     • Description: This factor contains metadata related to personalization features, such as face match, personal results, and voice match, ensuring a customized user experience.
     • SEO Purpose: Personalization enhances user satisfaction by providing relevant and tailored content, improving engagement metrics.
     • How to Use: Ensure personalization settings are accurately configured and updated. Provide clear information on how users can manage their personalization features.
291. Podcast Filter (AssistantApiSettingsPodcastFilter)
     • Description: This attribute specifies which podcast features and content are allowed on the device, ensuring relevance and appropriateness.
     • SEO Purpose: Properly managed podcast filters enhance user engagement by providing relevant and preferred podcast content.
     • How to Use: Configure podcast filters to match user interests and preferences. Regularly update the settings based on user feedback and new content availability.
292. Polite Mode (AssistantApiSettingsPoliteMode)
     • Description: This factor involves the configuration of polite mode on the device, which adjusts the assistant’s responses to be more polite and respectful.
     • SEO Purpose: Polite mode enhances user experience by providing courteous interactions, leading to increased satisfaction and engagement.
     • How to Use: Enable and configure polite mode based on user preferences. Provide clear instructions on how to adjust the settings for optimal interactions.
293. Reauth Trusted Device Settings (AssistantApiSettingsReauthTrustedDeviceSettings)
     • Description: This attribute involves settings related to reauthentication on trusted devices, ensuring secure access and user verification.
     • SEO Purpose: Properly managed reauth settings enhance security and trust, leading to improved user satisfaction and engagement.
     • How to Use: Configure reauth settings to ensure secure and convenient access. Regularly update the settings to align with the latest security protocols.
294. Search Filter (AssistantApiSettingsSearchFilter)
     • Description: This factor specifies which search features are allowed on the device, ensuring that search results are relevant and appropriate.
     • SEO Purpose: Properly managed search filters enhance user satisfaction by providing relevant search results, improving engagement metrics.
     • How to Use: Configure search filters to match user interests and preferences. Regularly update the settings based on user feedback and search trends.
295. Speech Output Settings (AssistantApiSettingsSpeechOutputSettings)
     • Description: This attribute involves settings related to text-to-speech (TTS) output, ensuring that speech output is clear and appropriate for the user.
     • SEO Purpose: Optimizing TTS settings improves user interactions and satisfaction, leading to better engagement and usability.
     • How to Use: Configure TTS settings to ensure clear and accurate speech output. Provide tools for users to customize their TTS preferences.
296. Speech Settings (AssistantApiSettingsSpeechSettings)
     • Description: This factor involves settings related to speech detection, ensuring accurate recognition and processing of voice commands.
     • SEO Purpose: Properly managed speech settings enhance voice interaction quality, improving user satisfaction and engagement.
     • How to Use: Regularly update speech settings to ensure accurate detection and processing. Provide clear instructions for users to customize their speech settings.
297. Tethered Info (AssistantApiSettingsTetheredInfo)
     • Description: This attribute contains information about the primary host device to which a wearable is tethered, ensuring proper connectivity and functionality.
     • SEO Purpose: Efficient tethering management enhances device functionality and user experience, leading to better engagement metrics.
     • How to Use: Ensure tethered information is accurately configured and updated. Provide clear instructions for users to manage their tethered devices.
298. Third-Party Apps Filter (AssistantApiSettingsThirdPartyAppsFilter)
     • Description: This factor specifies which third-party applications can be used on the device, allowing for control over app interactions and data sharing.
     • SEO Purpose: Optimizing third-party app usage ensures that only relevant and safe apps are accessible, enhancing user experience and trust.
     • How to Use: Configure third-party app filters to allow only necessary and secure applications. Regularly review and update the allowed app list to ensure compliance with security and privacy standards.
299. Video Features Filter (AssistantApiSettingsVideoFilter)
     • Description: This attribute defines which video features can be accessed on the device, ensuring that video capabilities align with user preferences and device limitations.
     • SEO Purpose: Managing video feature access enhances the user experience by providing relevant and optimized video functionalities, leading to better engagement.
     • How to Use: Set up video filters to allow the most appropriate video features based on user needs. Regularly update the filters to keep up with new video technologies and user preferences.
300. Webview Features Filter (AssistantApiSettingsWebviewFilter)
     • Description: This factor specifies which webview features can be used on the device, controlling how web content is rendered and interacted with.
     • SEO Purpose: Optimizing webview features ensures a seamless browsing experience, which can lead to increased user satisfaction and engagement.
     • How to Use: Configure webview settings to support the most relevant and secure web features. Update these settings regularly to adapt to new web technologies and standards.
301. Sign-In Method (AssistantApiSignInMethod)
     • Description: This attribute describes the supported methods of signing into the client, such as OAuth, password-based, or other authentication mechanisms.
     • SEO Purpose: Offering multiple and secure sign-in methods improves user accessibility and trust, potentially increasing user engagement and retention.
     • How to Use: Implement and support diverse sign-in methods to cater to different user preferences and enhance security. Ensure that the sign-in process is straightforward and secure.
302. SODA Capabilities (AssistantApiSodaCapabilities)
     • Description: This factor relates to the capabilities of the Speech On-Device API (SODA), which supports on-device speech processing and recognition.
     • SEO Purpose: Leveraging SODA capabilities enhances voice interaction quality and speed, improving user satisfaction and engagement.
     • How to Use: Ensure that SODA capabilities are fully utilized and optimized for voice interactions. Regularly update the speech recognition models to maintain accuracy and performance.
303. Software Capabilities (AssistantApiSoftwareCapabilities)
     • Description: This attribute outlines the software features supported by the client, determined by various software versions like the operating system and application versions.
     • SEO Purpose: Ensuring that all software capabilities are up-to-date enhances the overall performance and user experience, leading to better engagement metrics.
     • How to Use: Regularly update the software and its capabilities to the latest versions. Ensure compatibility and optimal performance across different software environments.
304. Speech Capabilities (AssistantApiSpeechCapabilities)
     • Description: Though deprecated, this factor was related to the speech detection features on devices, influencing how speech input is processed and recognized.
     • SEO Purpose: While no longer in use, understanding past speech capabilities can help in optimizing current voice interaction strategies.
     • How to Use: Focus on current speech capabilities and ensure they are optimized for user interactions. Implement feedback mechanisms to continually improve speech recognition accuracy.
305. Suggestions Support (AssistantApiSuggestionsSupport)
     • Description: This attribute involves the support for various suggestion features on the device, which helps in providing relevant and timely suggestions to the user.
     • SEO Purpose: Enhancing suggestion features improves user engagement by offering helpful and contextual recommendations, increasing interaction time.
     • How to Use: Optimize suggestion algorithms to provide accurate and relevant suggestions. Regularly update the suggestion parameters based on user feedback and interaction data.
306. Display Target Support for Suggestions (AssistantApiSuggestionsSupportDisplayTargetSupport)
     • Description: This factor specifies the supported display targets for suggestions, detailing how and where suggestions are presented to the user.
     • SEO Purpose: Properly managing display target support for suggestions ensures that users receive relevant recommendations in an accessible manner, enhancing engagement.
     • How to Use: Configure display targets to present suggestions effectively. Regularly review and update the supported targets to improve user interaction and satisfaction.
307. Sunrise Features Support (AssistantApiSunriseFeaturesSupport)
     • Description: This attribute indicates whether the device supports sunrise simulation features, which gradually brighten the screen to simulate a sunrise experience for alarms.
     • SEO Purpose: Supporting sunrise simulation can improve user wake-up experiences, leading to higher satisfaction and positive engagement metrics.
     • How to Use: Enable and optimize sunrise simulation settings on supported devices. Educate users on the benefits of using sunrise alarms to enhance their experience.
308. Supported Client Operations (AssistantApiSupportedClientOp)
     • Description: This factor details the set of client operations supported by the device, ensuring that various actions and commands can be executed efficiently.
     • SEO Purpose: Supporting a wide range of client operations improves the device’s versatility and user experience, leading to increased engagement.
     • How to Use: Ensure that all supported client operations are optimized for performance and reliability. Regularly update the list of supported operations to include new functionalities.
309. Supported Execution Properties (AssistantApiSupportedClientOpSupportedExecution)
     • Description: This attribute specifies additional properties for executing client operations, tailored to specific surfaces and unrelated to the execution model.
     • SEO Purpose: Properly managing execution properties ensures that client operations run smoothly, enhancing user satisfaction and engagement.
     • How to Use: Configure execution properties to match the capabilities of different surfaces. Regularly update these properties to maintain optimal performance.
310. Supported Conversation Version (AssistantApiSupportedConversationVersion)
     • Description: This factor indicates the supported versions of the conversation protocol, ensuring compatibility and seamless communication between clients and servers.
     • SEO Purpose: Maintaining compatibility with the latest conversation protocol versions improves interaction quality and user satisfaction.
     • How to Use: Regularly update the supported conversation versions to ensure compatibility. Provide clear information on version updates and their benefits to users.
311. Supported Features (AssistantApiSupportedFeatures)
     • Description: This attribute lists the features supported by the device as part of its software capabilities, ensuring a comprehensive understanding of the device’s functionalities.
     • SEO Purpose: Highlighting supported features can attract users looking for specific capabilities, enhancing engagement and user satisfaction.
     • How to Use: Clearly document and promote the supported features. Regularly update the list to include new and relevant features based on user feedback and technological advancements.
312. Supported Protocol Version (AssistantApiSupportedProtocolVersion)
     • Description: This factor contains the versions of protocol buffer messages supported by the device, ensuring compatibility with various message formats and structures.
     • SEO Purpose: Ensuring protocol version compatibility enhances communication efficiency and reliability, improving user experience and engagement.
     • How to Use: Regularly update the supported protocol versions to maintain compatibility. Provide clear documentation on supported versions and their benefits.
313. Message Version Pair (AssistantApiSupportedProtocolVersionMessageVersionPair)
     • Description: This attribute specifies the version of a particular message type supported by the device, ensuring accurate and efficient message processing.
     • SEO Purpose: Maintaining accurate message version support enhances the reliability of communication protocols, leading to better user satisfaction.
     • How to Use: Ensure that message version pairs are correctly configured and updated. Provide clear information on the supported versions for different message types.
314. Supported Provider Types (AssistantApiSupportedProviderTypes)
     • Description: This factor lists the types of providers supported by the client, such as web apps or Android apps, ensuring versatile and comprehensive support.
     • SEO Purpose: Supporting a wide range of provider types enhances device functionality and user experience, leading to increased engagement.
     • How to Use: Regularly update the supported provider types to include new and relevant providers. Ensure that the client is optimized for the supported types.
315. Surface Properties (AssistantApiSurfaceProperties)
     • Description: This attribute describes the properties of the device’s surface that are not related to hardware or specific features, ensuring a comprehensive understanding of the device’s capabilities.
     • SEO Purpose: Properly managing surface properties enhances the overall user experience by providing a seamless and integrated interface.
     • How to Use: Clearly document the surface properties and ensure they are optimized for performance. Regularly update these properties based on user feedback and technological advancements.
316. Execution Capabilities (AssistantApiSurfacePropertiesExecutionCapabilities)
     • Description: This factor details the capabilities related to executing client operations on the device, ensuring efficient and reliable performance.
     • SEO Purpose: Enhancing execution capabilities improves the overall functionality and user experience, leading to better engagement metrics.
     • How to Use: Optimize execution capabilities for different client operations. Regularly review and update these capabilities to maintain high performance.
317. System Notification Restrictions (AssistantApiSystemNotificationRestrictions)
     • Description: This attribute involves restrictions related to system-level notifications, ensuring that notifications are managed according to user preferences and policies.
     • SEO Purpose: Properly managing notification restrictions enhances user satisfaction and trust, leading to improved engagement.
     • How to Use: Configure system notification restrictions to align with user preferences and privacy policies. Provide clear instructions for users to manage their notification settings.
318. Notification Category State (AssistantApiSystemNotificationRestrictionsNotificationCategoryState)
     • Description: This factor specifies the state of notification channels for new server-driven channels, ensuring that notifications are managed effectively.
     • SEO Purpose: Managing notification channel states ensures that users receive relevant and timely notifications, improving engagement and satisfaction.
     • How to Use: Regularly review and update the state of notification channels. Ensure that new server-driven channels are configured to meet user preferences and needs.
319. Notification Channel State (AssistantApiSystemNotificationRestrictionsNotificationChannelState)
     • Description: This attribute details the state of notification channels, ensuring that they are managed according to user preferences and system policies.
     • SEO Purpose: Properly managing notification channel states enhances user experience and trust, leading to better engagement.
     • How to Use: Configure notification channels to align with user preferences and policies. Regularly update these settings to ensure optimal performance and relevance.
320. Third-Party Action Config (AssistantApiThirdPartyActionConfig)
     • Description: This factor involves the configuration of third-party actions, detailing metadata for action packages and enabling device actions for third-party apps.
     • SEO Purpose: Properly configuring third-party actions enhances the functionality and integration of third-party apps, improving user experience and engagement.
     • How to Use: Ensure that third-party actions are correctly configured and enabled. Regularly update the action metadata to maintain compatibility and performance.
321. Third-Party Capabilities (AssistantApiThirdPartyCapabilities)
     • Description: This attribute describes the capabilities related to third-party applications, including data sharing restrictions and supported functionalities.
     • SEO Purpose: Managing third-party capabilities ensures secure and effective integration of third-party apps, enhancing user trust and satisfaction.
     • How to Use: Configure third-party capabilities to support relevant and secure functionalities. Regularly review and update these settings based on user feedback and security requirements.
322. Time of Day (AssistantApiTimeOfDay)
     • Description: This factor specifies a civil time relative to a timezone, allowing for accurate time-based actions and events.
     • SEO Purpose: Accurate time management enhances the relevance and timeliness of time-based content and actions, improving user engagement.
     • How to Use: Ensure that time-of-day settings are correctly configured and synchronized with the user’s timezone. Provide clear instructions for users to manage time-based settings.
323. Time Zone (AssistantApiTimeZone)
     • Description: This attribute defines a timezone, including rules for UTC offset and changes over time, ensuring accurate local date and time calculations.
     • SEO Purpose: Properly managing timezones enhances the accuracy of time-based content and interactions, improving user satisfaction and engagement.
     • How to Use: Configure timezone settings to accurately reflect the user’s location. Regularly update these settings to account for changes in daylight saving time and other factors.
324. Timestamp (AssistantApiTimestamp)
     • Description: This factor represents an absolute point in time independent of timezone or calendar, ensuring precise time-based actions and events.
     • SEO Purpose: Accurate timestamp management enhances the reliability of time-based interactions, improving user trust and engagement.
     • How to Use: Ensure that timestamp settings are accurately configured and synchronized across all devices. Provide clear documentation on how to manage and use timestamps effectively.
325. Transaction Features Support (AssistantApiTransactionFeaturesSupport)
     • Description: This factor indicates whether the device supports specific transaction features, such as voice PIN suppression, which prevents users from using voice commands for PIN-related transactions.
     • SEO Purpose: Ensuring secure and user-friendly transaction features enhances user trust and engagement, which can positively affect SEO.
     • How to Use: Configure transaction settings to balance security and convenience. Regularly review and update these settings to ensure they meet user needs and security standards.
326. Volume Properties (AssistantApiVolumeProperties)
     • Description: This attribute defines the volume settings on the device, including default, high, medium, low, and very low volume percentages, as well as the maximum volume level and step size for volume adjustments.
     • SEO Purpose: Optimizing volume settings ensures a better user experience by providing clear and controlled audio, leading to increased engagement and satisfaction.
     • How to Use: Set volume properties to cater to different user preferences and environments. Regularly update these settings to maintain optimal audio performance.
327. Device Targeting Error (AssistantDeviceTargetingDeviceTargetingError)
     • Description: This factor includes information about errors that occur when selecting the target device, helping to diagnose and resolve targeting issues.
     • SEO Purpose: Resolving device targeting errors improves the accuracy and reliability of device interactions, enhancing user satisfaction.
     • How to Use: Monitor and address device targeting errors promptly. Implement error handling mechanisms to improve targeting accuracy and user experience.
328. Alarm Capability (AssistantDevicesPlatformProtoAlarmCapability)
     • Description: This attribute specifies the device’s ability to support alarms, detailing the functionalities related to setting, managing, and dismissing alarms.
     • SEO Purpose: Enhancing alarm capabilities ensures timely and reliable reminders for users, increasing their reliance on the device and overall satisfaction.
     • How to Use: Configure alarm settings to provide a seamless user experience. Regularly update the capabilities to include new features and improvements.
329. Argument Specification (AssistantDevicesPlatformProtoArgSpec)
     • Description: This factor defines the specifications for arguments passed to device actions, including integer and option value specifications.
     • SEO Purpose: Properly managing argument specifications ensures accurate execution of device actions, enhancing user interaction quality.
     • How to Use: Ensure that argument specifications are accurately configured. Regularly update these settings to maintain compatibility and performance.
330. Call Capability (AssistantDevicesPlatformProtoCallCallCapability)
     • Description: This attribute describes the device’s ability to support call functionalities, detailing features related to initiating and managing calls.
     • SEO Purpose: Optimizing call capabilities improves communication quality and user satisfaction, leading to better engagement.
     • How to Use: Configure call settings to ensure clear and reliable communication. Regularly update these settings to incorporate new call features and improvements.
331. Client Reconnect Capability (AssistantDevicesPlatformProtoClientReconnectCapability)
     • Description: This factor specifies the device’s ability to reconnect to the client after disconnection, ensuring continuous and seamless operation.
     • SEO Purpose: Ensuring reliable reconnect capabilities enhances the overall user experience by minimizing interruptions.
     • How to Use: Implement robust reconnect mechanisms to ensure continuous operation. Regularly test and update these capabilities to maintain reliability.
332. Cloud Capability (AssistantDevicesPlatformProtoCloudCapability)
     • Description: This attribute states the cloud capabilities of the device, including the endpoints used for cloud execution of actions or registration.
     • SEO Purpose: Leveraging cloud capabilities enhances the device’s functionality and performance, improving user satisfaction.
     • How to Use: Ensure cloud capabilities are optimized for performance and security. Regularly update cloud endpoints and configurations to maintain optimal functionality.
333. Cloud Endpoint (AssistantDevicesPlatformProtoCloudEndpoint)
     • Description: This factor specifies the cloud endpoints associated with the device, used for query parsing and cloud execution.
     • SEO Purpose: Optimizing cloud endpoints improves the speed and accuracy of cloud-based interactions, enhancing user experience.
     • How to Use: Configure cloud endpoints to ensure efficient query processing and execution. Regularly update endpoints to maintain performance and security.
334. Dismiss Assistant Capability (AssistantDevicesPlatformProtoCoreDismissAssistantCapability)
     • Description: This attribute defines the device’s capability to dismiss the assistant, ensuring users can easily end interactions with the assistant.
     • SEO Purpose: Providing a smooth and intuitive way to dismiss the assistant enhances user control and satisfaction.
     • How to Use: Implement easy-to-use mechanisms for dismissing the assistant. Regularly update this capability to improve user experience.
335. Device Action Capability (AssistantDevicesPlatformProtoDeviceActionCapability)
     • Description: This factor represents the capabilities required for device actions, detailing how the device can execute various commands.
     • SEO Purpose: Ensuring comprehensive device action capabilities enhances the range of interactions users can perform, leading to better engagement.
     • How to Use: Configure device action settings to support a wide range of commands. Regularly update these capabilities to include new actions and improvements.
336. Modify Setting Capability (AssistantDevicesPlatformProtoDeviceModifySettingCapability)
     • Description: This attribute specifies the capability to modify device settings, detailing how different settings can be adjusted through the assistant.
     • SEO Purpose: Providing intuitive and efficient ways to modify settings improves user control and satisfaction.
     • How to Use: Ensure setting modification capabilities are user-friendly and comprehensive. Regularly update these settings to enhance functionality and usability.
337. Take Photo Capability (AssistantDevicesPlatformProtoDeviceTakePhotoCapability)
     • Description: This factor defines the device’s ability to take photos, detailing the functionalities related to capturing and managing images.
     • SEO Purpose: Enhancing photo capabilities can improve user engagement and satisfaction by providing easy and high-quality photo capturing features.
     • How to Use: Optimize photo capturing settings for quality and ease of use. Regularly update these capabilities to incorporate new features and improvements.
338. Execution Config (AssistantDevicesPlatformProtoExecutionConfig)
     • Description: This attribute specifies the routing capabilities of the intent, detailing how the intent is triggered and executed.
     • SEO Purpose: Properly managing execution configurations ensures accurate and efficient execution of user commands, enhancing interaction quality.
     • How to Use: Configure execution settings to ensure accurate intent handling. Regularly update these settings to maintain compatibility and performance.
339. Execution Wait Capability (AssistantDevicesPlatformProtoExecutionWaitCapability)
     • Description: This factor specifies the device’s capability to wait for the completion of an execution, ensuring that actions are properly sequenced and executed.
     • SEO Purpose: Managing execution wait capabilities improves the reliability and accuracy of sequential actions, enhancing user experience.
     • How to Use: Implement robust wait mechanisms to ensure proper action sequencing. Regularly update these capabilities to maintain performance and reliability.
340. Health Observation Capability (AssistantDevicesPlatformProtoGetHealthObservationCapability)
     • Description: This attribute defines the device’s ability to observe and report health-related data, detailing how health metrics are captured and managed.
     • SEO Purpose: Providing accurate health observation capabilities can enhance user trust and engagement by offering valuable health insights.
     • How to Use: Optimize health observation settings for accuracy and usability. Regularly update these capabilities to include new health metrics and improvements.
341. Inlined Action Capability (AssistantDevicesPlatformProtoInlinedActionCapability)
     • Description: This factor specifies the inlined actions supported by the device, detailing capabilities such as alarm handling, response limits, and multi-response support.
     • SEO Purpose: Enhancing inlined action capabilities improves the versatility and functionality of the device, leading to better user engagement.
     • How to Use: Configure inlined action settings to support a wide range of capabilities. Regularly update these settings to incorporate new features and improvements.
342. Integer Value Specification (AssistantDevicesPlatformProtoIntValueSpec)
     • Description: This attribute specifies the integer value range supported by the device, detailing the minimum and maximum values for device actions.
     • SEO Purpose: Ensuring accurate integer value specifications enhances the precision and reliability of device actions, improving user satisfaction.
     • How to Use: Configure integer value ranges to match the device’s capabilities. Regularly update these settings to maintain accuracy and performance.
343. Intent Configuration (AssistantDevicesPlatformProtoIntent)
     • Description: This factor configures the behavior of device actions based on specific intents, detailing how intents are triggered and managed.
     • SEO Purpose: Properly managing intent configurations ensures accurate and efficient execution of user commands, enhancing interaction quality.
     • How to Use: Configure intent settings to ensure accurate handling of user commands. Regularly update these settings to maintain compatibility and performance.
344. Internal Capability (AssistantDevicesPlatformProtoInternalCapability)
     • Description: This attribute defines capabilities that can only be set internally, ensuring that only authorized personnel can configure these settings.
     • SEO Purpose: Managing internal capabilities securely enhances the overall functionality and security of the device, improving user trust.
     • How to Use: Ensure that internal capabilities are securely managed and configured. Provide clear documentation for authorized personnel to update these settings.
345. Media Control Capabilities (AssistantDevicesPlatformProtoMediaControlCapabilities)
     • Description: This factor includes various media control capabilities such as play, pause, stop, next, previous, resume, and show controls, detailing how media is managed on the device.
     • SEO Purpose: Enhancing media control capabilities improves the user experience by providing seamless and intuitive media interactions.
     • How to Use: Configure media control settings to ensure smooth and responsive media interactions. Regularly update these capabilities to incorporate new features and improvements.
346. Option Value Specification (AssistantDevicesPlatformProtoOptionValueSpec)
     • Description: This attribute specifies the option values supported by the device, detailing the possible options for device actions.
     • SEO Purpose: Ensuring accurate option value specifications enhances the flexibility and reliability of device actions, improving user satisfaction.
     • How to Use: Configure option value settings to match the device’s capabilities. Regularly update these settings to maintain accuracy and performance.
347. Provided Data (AssistantDevicesPlatformProtoProvidedData)
     • Description: This factor includes additional data required to augment device action capabilities, ensuring that specific actions have the necessary context and information.
     • SEO Purpose: Providing accurate and relevant data enhances the precision and effectiveness of device actions, leading to better user engagement.
     • How to Use: Ensure that all necessary data is provided for device actions. Regularly update the data to maintain accuracy and relevance.
348. Platform Capability (AssistantDevicesPlatformProtoProviderFulfillCapability)
     • Description: This factor evaluates the platform’s ability to fulfill various tasks and actions. It includes attributes detailing the supported operations and capabilities, such as task execution and interaction efficiency.
     • SEO Purpose: Ensures that your platform or website is capable of handling user requests effectively, which can improve user satisfaction and engagement.
     • How to Use: Optimize your platform to support a wide range of capabilities and ensure seamless user interactions.
349. Client Operation Property (AssistantDevicesPlatformProtoProviderOpenCapability)
     • Description: Focuses on the properties of client operations when interacting with the platform. Attributes cover the operational parameters and settings that influence how tasks are performed.
     • SEO Purpose: Enhances the functionality and responsiveness of client interactions, leading to better user experiences and potentially higher rankings.
     • How to Use: Configure your client operations to be efficient and responsive, ensuring they align with user needs and platform capabilities.
350. Response Limits (AssistantDevicesPlatformProtoResponseLimits)
     • Description: Specifies the size limits on responses receivable by the client. This includes attributes detailing maximum allowable sizes for different response types.
     • SEO Purpose: Helps in optimizing the content size for faster load times and better performance, which are crucial for SEO.
     • How to Use: Ensure your responses are within the specified size limits to avoid slow load times and potential penalties from search engines.
351. Security Configuration (AssistantDevicesPlatformProtoSecurityConfig)
     • Description: Encapsulates the security settings and protocols for a device model. Attributes cover encryption methods, authentication requirements, and other security measures.
     • SEO Purpose: Enhances the security of your platform, which is critical for maintaining user trust and complying with search engine security guidelines.
     • How to Use: Implement robust security measures as specified, ensuring your platform is secure from potential threats and vulnerabilities.
352. Send Chat Message Capability (AssistantDevicesPlatformProtoSendChatMessageCapability)
     • Description: Describes the platform’s ability to send chat messages. Attributes detail the supported messaging formats, protocols, and limitations.
     • SEO Purpose: Improves user engagement by ensuring effective communication capabilities, which can enhance user satisfaction and retention.
     • How to Use: Optimize your platform’s messaging capabilities to support various formats and protocols, ensuring reliable and effective communication with users.
353. Supported Device Operations (AssistantDevicesPlatformProtoSupportedDeviceOps)
     • Description: Specifies the supported operations for a device model package. Attributes cover the range of tasks and actions that devices can perform, ensuring compatibility and functionality.
     • SEO Purpose: Ensures that your devices are capable of performing essential operations, contributing to a seamless user experience and better rankings.
     • How to Use: Ensure that your device models support a wide range of operations, enhancing their utility and user satisfaction.
354. Timer Capability (AssistantDevicesPlatformProtoTimerCapability)
     • Description: Describes the platform’s support for timer functionalities. Attributes include settings and capabilities related to setting, managing, and executing timers.
     • SEO Purpose: Enhances the usability of your platform by supporting essential timer functions, contributing to a more feature-rich user experience.
     • How to Use: Implement and optimize timer functionalities within your platform, ensuring they are user-friendly and reliable.
355. Trigger Condition (AssistantDevicesPlatformProtoTriggerCondition)
     • Description: Defines the conditions that must be met for specific actions to be triggered. Attributes include the state requirements and instructions for responses when conditions are not met.
     • SEO Purpose: Improves the responsiveness and relevance of actions based on user conditions, enhancing overall user satisfaction.
     • How to Use: Configure trigger conditions carefully to ensure timely and appropriate responses, enhancing the user experience on your platform.
356. Text-to-Speech Output Capability (AssistantDevicesPlatformProtoTtsOutputCapability)
     • Description: Details the platform’s capabilities regarding text-to-speech output. Attributes include supported languages, voices, and output quality.
     • SEO Purpose: Enhances accessibility and user interaction through high-quality text-to-speech functionalities, which can positively impact user engagement and SEO.
     • How to Use: Optimize your platform’s text-to-speech capabilities to support diverse languages and high-quality outputs, ensuring accessibility and user satisfaction.
357. UI Show Interpreter Capability (AssistantDevicesPlatformProtoUiShowInterpreterCapability)
     • Description: Describes the platform’s ability to display an interpreter user interface. Attributes include supported languages, display formats, and interaction methods.
     • SEO Purpose: Improves accessibility and user interaction by providing an effective interpreter UI, contributing to a better user experience.
     • How to Use: Implement and optimize interpreter UI capabilities to support multiple languages and interaction methods, ensuring broad accessibility.
358. Understanding Configuration (AssistantDevicesPlatformProtoUnderstandingConfig)
     • Description: Specifies the natural language understanding (NLU) level performed by Google, determining the request format sent to third-party clouds. Attributes include supported NLU features and configurations.
     • SEO Purpose: Enhances the accuracy and relevance of user queries by leveraging advanced NLU capabilities, improving user satisfaction and engagement.
     • How to Use: Configure your platform to utilize advanced NLU capabilities, ensuring accurate and relevant responses to user queries.
359. Media Stream Log (AssistantLogsAllMediaStreamLog)
     • Description: Logs all active media streams when a user issues a query. Attributes include detailed logs of media streams and target streams selected by transfer logic.
     • SEO Purpose: Provides insights into media stream interactions, helping to optimize media delivery and user experience.
     • How to Use: Analyze media stream logs to identify patterns and optimize media delivery, ensuring smooth and efficient streaming experiences.
360. Ambiguous Target Device Log (AssistantLogsAmbiguousTargetDeviceLog)
     • Description: Logs details on ambiguous device targeting logic, including device lists and filtering processes. Attributes detail the steps taken to resolve ambiguity in device selection.
     • SEO Purpose: Enhances device targeting accuracy, improving user satisfaction by ensuring the correct device is selected for tasks.
     • How to Use: Monitor and analyze ambiguous target device logs to refine device targeting logic, ensuring accurate and reliable device selection.
361. Punt Info Log (AssistantLogsAmbiguousTargetDeviceLogPuntInfoLog)
     • Description: Logs reasons for filtering out devices during media content playability checks. Attributes include media excuses, provider IDs, and device indices.
     • SEO Purpose: Provides insights into device filtering processes, helping to refine and improve device playability checks.
     • How to Use: Analyze punt info logs to understand and improve device filtering criteria, ensuring better media playability and user experience.
362. Available Device and Context Difference Log (AssistantLogsAvailableDeviceAndCtfContextDiffLog)
     • Description: Logs per-device contexts and their respective differences between AvailableDevice and Contextual Task Fulfillment (CTF). Attributes include detailed context differences.
     • SEO Purpose: Enhances contextual accuracy in device interactions, improving user satisfaction and task fulfillment.
     • How to Use: Analyze context difference logs to refine contextual understanding and improve device interaction accuracy, ensuring better task fulfillment.
363. Available Devices Log (AssistantLogsAvailableDevicesLog)
     • Description: Contains logs of available devices in the DeviceTargetingContext. Attributes include detailed device information and availability status.
     • SEO Purpose: Provides a comprehensive overview of available devices, helping to optimize device targeting and selection.
     • How to Use: Monitor available devices logs to ensure accurate and up-to-date device information, optimizing device targeting and user satisfaction.
364. Communication Device Contact Info Log (AssistantLogsCommunicationDeviceContactInfoLog)
     • Description: Logs contact information related to communication devices. Attributes include detailed contact info and device associations.
     • SEO Purpose: Enhances communication accuracy by providing detailed contact information logs, improving user interactions.
     • How to Use: Utilize communication device contact info logs to maintain accurate and comprehensive contact details, ensuring effective communication.
365. Fuzzy Ngram Match Log (AssistantLogsCommunicationFuzzyNgramMatchLog)
     • Description: Logs results of fuzzy ngram matches used for generating the best fuzzy match. Attributes include detailed match results and criteria.
     • SEO Purpose: Improves search accuracy and relevance by leveraging fuzzy ngram match results, enhancing user query satisfaction.
     • How to Use: Analyze fuzzy ngram match logs to refine search algorithms and improve query match accuracy, ensuring relevant search results.
366. Google Account Provenance (AssistantLogsCommunicationGoogleAccountProvenance)
     • Description: Logs account provenance details from Google Account quality rewrite protocols. Attributes include provenance data and associated account information.
     • SEO Purpose: Enhances account-related interactions by providing detailed provenance logs, improving user trust and satisfaction.
     • How to Use: Utilize account provenance logs to maintain accurate and detailed account histories, ensuring trustworthy user interactions.
367. Person Metadata Log (AssistantLogsCommunicationPersonMetadataLog)
     • Description: Logs metadata related to persons in communication contexts. Attributes include detailed person metadata and associations.
     • SEO Purpose: Enhances communication relevance by providing detailed person metadata logs, improving user interaction accuracy.
     • How to Use: Analyze person metadata logs to refine communication strategies and improve person-related interactions, ensuring accurate and relevant communication.
368. Personal Contact Data Log (AssistantLogsCommunicationPersonalContactDataLog)
     • Description: Logs contact metadata for personal contacts. Attributes include detailed personal contact data and associations.
     • SEO Purpose: Enhances personal contact interactions by providing detailed contact data logs, improving user satisfaction and communication accuracy.
     • How to Use: Maintain and analyze personal contact data logs to ensure accurate and comprehensive contact information, optimizing personal communication.
369. Phone Log (AssistantLogsCommunicationPhoneLog)
     • Description: Logs phone-related data in communication contexts. Attributes include detailed phone metadata and associations.
     • SEO Purpose: Enhances phone communication accuracy by providing detailed phone data logs, improving user interactions.
     • How to Use: Utilize phone logs to maintain accurate phone-related information, ensuring effective and reliable phone communication.
370. Raw Device Contact Info Log (AssistantLogsCommunicationRawDeviceContactInfoLog)
     • Description: Logs raw contact information from devices. Attributes include detailed raw contact data and associations.
     • SEO Purpose: Provides comprehensive contact data logs, improving accuracy and reliability of device contact information.
     • How to Use: Analyze raw device contact info logs to maintain accurate and comprehensive contact details, ensuring effective device communication.
371. Default Device Log (AssistantLogsDefaultDeviceLog)
     • Description: Logs default device information, including settings and associations. Attributes include detailed default device data.
     • SEO Purpose: Enhances device targeting and selection accuracy by providing detailed default device logs, improving user satisfaction.
     • How to Use: Monitor default device logs to ensure accurate and up-to-date default device information, optimizing device targeting and selection.
372. Default Devices Log (AssistantLogsDefaultDevicesLog)
     • Description: Logs settings and information of default and nearby devices. Attributes include detailed data on local and nearby default devices.
     • SEO Purpose: Provides a comprehensive overview of default devices, helping to optimize device targeting and selection.
     • How to Use: Analyze default devices logs to maintain accurate and comprehensive device settings, optimizing user satisfaction and device targeting.
373. Device Annotation Log (AssistantLogsDeviceAnnotationLog)
     • Description: Logs mentions of devices in user queries. Attributes include detailed device annotation data and associations.
     • SEO Purpose: Enhances device recognition and interaction by providing detailed device annotation logs, improving query accuracy.
     • How to Use: Monitor device annotation logs to ensure accurate device recognition, optimizing user queries and interactions.
374. Device Info Log (AssistantLogsDeviceInfoLog)
     • Description: Logs information related to devices, including settings and associations. Attributes include detailed device data.
     • SEO Purpose: Provides comprehensive device information logs, helping to optimize device targeting and interaction accuracy.
     • How to Use: Utilize device info logs to maintain accurate and detailed device information, ensuring effective and reliable device interactions.
375. Device Media Session Log (AssistantLogsDeviceMediaSessionLog)
     • Description: Logs media sessions on devices. Attributes include detailed media session data and device associations.
     • SEO Purpose: Enhances media session management by providing detailed logs, improving user experience with media playback.
     • How to Use: Monitor media session logs to optimize media playback and session management, ensuring smooth and enjoyable media experiences.
376. Device Selection Log (AssistantLogsDeviceSelectionLog)
     • Description: Logs information related to target device selection. Attributes include detailed selection criteria and results.
     • SEO Purpose: Improves device targeting accuracy by providing detailed selection logs, enhancing user satisfaction.
     • How to Use: Analyze device selection logs to refine targeting criteria and improve device selection accuracy, ensuring optimal user interactions.
377. Device Selection Result Log (AssistantLogsDeviceSelectionResultLog)
     • Description: Logs the results of device selection processes. Attributes include detailed selection results and criteria.
     • SEO Purpose: Enhances device selection accuracy by providing comprehensive selection result logs, improving user satisfaction.
     • How to Use: Utilize device selection result logs to refine and optimize selection processes, ensuring accurate and reliable device targeting.
378. Device Targeting Test Code (AssistantLogsDeviceTargetingTestCode)
     • Description: Logs special events related to device targeting tests. Attributes include detailed test codes and event data.
     • SEO Purpose: Provides insights into device targeting test results, helping to refine and improve targeting accuracy.
     • How to Use: Monitor device targeting test code logs to analyze and improve targeting test outcomes, ensuring accurate device targeting.
379. Input Error Log (AssistantLogsInputErrorLog)
     • Description: Logs errors related to input processes. Attributes include error codes and types, providing detailed error information.
     • SEO Purpose: Enhances input error handling by providing comprehensive error logs, improving user satisfaction.
     • How to Use: Analyze input error logs to identify and rectify input issues, ensuring smooth and reliable user interactions.
380. Low Confidence Target Device Log (AssistantLogsLowConfidenceTargetDeviceLog)
     • Description: Logs cases where target devices have low confidence. Attributes include detailed data on low confidence targets and fallback devices.
     • SEO Purpose: Enhances device targeting accuracy by addressing low confidence cases, improving user satisfaction.
     • How to Use: Monitor low confidence target device logs to refine targeting criteria and improve selection accuracy, ensuring reliable device targeting.
381. Lumos Processor Info (AssistantLogsLumosProcessorInfo)
     • Description: Logs information about the Lumos processor stages, including candidate device counts before and after each stage. Attributes include processor names and device counts.
     • SEO Purpose: Provides insights into processor stages and their impact on device selection, helping to optimize processing efficiency.
     • How to Use: Analyze Lumos processor info logs to understand and improve processor stages, ensuring efficient and accurate device selection.
382. Media Capabilities (AssistantLogsMediaCapabilities)
     • Description: Logs media capabilities of devices, including remote action support and screen availability. Attributes include detailed media capability data.
     • SEO Purpose: Enhances media interaction by providing comprehensive media capability logs, improving user experience with media features.
     • How to Use: Utilize media capability logs to optimize media features and interactions, ensuring smooth and enjoyable media experiences.
383. Media Device Selection Decision Summary (AssistantLogsMediaDeviceSelectionDecisionSummary)
     • Description: Summarizes reasons for choosing a target media device. Attributes include detailed decision criteria and outcomes.
     • SEO Purpose: Enhances media device selection accuracy by providing decision summaries, improving user satisfaction.
     • How to Use: Analyze media device selection decision summaries to refine selection criteria, ensuring optimal media device targeting.
384. Media Focus Info Log (AssistantLogsMediaFocusInfoLog)
     • Description: Logs information related to media focus during interactions. Attributes include detailed media focus data and associations.
     • SEO Purpose: Enhances media focus management by providing comprehensive logs, improving user experience with media interactions.
     • How to Use: Monitor media focus info logs to optimize media focus and interaction accuracy, ensuring smooth and engaging media experiences.
385. Media Focuses Log (AssistantLogsMediaFocusesLog)
     • Description: Logs media focus events and interactions. Attributes include detailed media focus data and related information.
     • SEO Purpose: Provides insights into media focus events, helping to optimize focus management and user interactions.
     • How to Use: Utilize media focuses logs to analyze and improve media focus handling, ensuring engaging and effective media interactions.
386. Media Stream Log (AssistantLogsMediaStreamLog)
     • Description: Logs details of media streams, including session and device information. Attributes include comprehensive media stream data.
     • SEO Purpose: Enhances media stream management by providing detailed logs, improving user experience with media playback.
     • How to Use: Monitor media stream logs to optimize media stream handling and session management, ensuring smooth and enjoyable media experiences.
387. Nearby Devices Log (AssistantLogsNearbyDevicesLog)
     • Description: Logs information about nearby devices and their interactions. Attributes include timestamps, device counts, and elimination criteria.
     • SEO Purpose: Enhances device targeting accuracy by providing detailed nearby device logs, improving user satisfaction.
     • How to Use: Analyze nearby devices logs to refine targeting criteria and improve selection accuracy, ensuring optimal user interactions.
388. Provider Annotation Log (AssistantLogsProviderAnnotationLog)
     • Description: Logs detailed information about providers from user queries. Attributes include package names, localized names, and language settings.
     • SEO Purpose: Enhances provider recognition and interaction by providing comprehensive provider annotation logs, improving query accuracy.
     • How to Use: Monitor provider annotation logs to ensure accurate provider recognition, optimizing user queries and interactions.
389. Query Annotation Log (AssistantLogsQueryAnnotationLog)
     • Description: Logs details about user queries and their requirements. Attributes include query data and annotation information.
     • SEO Purpose: Enhances query handling by providing detailed annotation logs, improving user satisfaction with search results.
     • How to Use: Utilize query annotation logs to refine query handling processes, ensuring accurate and relevant search results.
390. Reminder Log (AssistantLogsReminderLog)
     • Description: Logs instances of user reminders. Attributes include detailed reminder data and settings.
     • SEO Purpose: Enhances reminder management by providing comprehensive logs, improving user experience with reminders.
     • How to Use: Monitor reminder logs to optimize reminder settings and handling, ensuring effective and reliable reminders.
391. Room Annotation Log (AssistantLogsRoomAnnotationLog)
     • Description: Logs mentions of rooms in user queries. Attributes include detailed room annotation data and associations.
     • SEO Purpose: Enhances room recognition and interaction by providing comprehensive room annotation logs, improving query accuracy.
     • How to Use: Monitor room annotation logs to ensure accurate room recognition, optimizing user queries and interactions.
392. Settings Device ID Log (AssistantLogsSettingsDeviceIdLog)
     • Description: Logs device IDs related to settings. Attributes include detailed device ID data and associations.
     • SEO Purpose: Enhances device identification by providing comprehensive device ID logs, improving user satisfaction with settings.
     • How to Use: Utilize settings device ID logs to maintain accurate and detailed device identification, ensuring effective and reliable device interactions.
393. Structure Annotation Log (AssistantLogsStructureAnnotationLog)
     • Description: Logs mentions of structures in user queries. Attributes include detailed structure annotation data and associations.
     • SEO Purpose: Enhances structure recognition and interaction by providing comprehensive structure annotation logs, improving query accuracy.
     • How to Use: Monitor structure annotation logs to ensure accurate structure recognition, optimizing user queries and interactions.
394. Target Device Log (AssistantLogsTargetDeviceLog)
     • Description: Logs instances of successfully selected target devices. Attributes include detailed target device data and criteria.
     • SEO Purpose: Enhances device targeting accuracy by providing comprehensive target device logs, improving user satisfaction.
     • How to Use: Analyze target device logs to refine and optimize device selection criteria, ensuring accurate and reliable device targeting.
395. Device Metadata (AssistantPfrDeviceRdMetadata)
     • Description: This factor involves the metadata associated with devices. Attributes cover the device name, types, effective argument span length, ambiguity resolution, resolved device IDs, and room name.
     • SEO Purpose: Enhances the accuracy and relevance of device-related searches and actions, ensuring users find the right devices quickly.
     • How to Use: Ensure device metadata is accurately maintained and up-to-date to improve search precision and user interactions.
396. Smart Home Intent Metadata (AssistantPfrSmartHomeIntentMetadata)
     • Description: This factor determines the metadata used by the Smarthome Business Rules to potentially replace the top-scoring Smarthome intent with another.
     • SEO Purpose: Improves the relevance of smart home actions and commands, ensuring the most appropriate intent is executed.
     • How to Use: Regularly review and update smart home intent metadata to ensure the most accurate and relevant intents are prioritized.
397. Tiebreaking Metadata (AssistantPfrTiebreakingMetadata)
     • Description: Features used exclusively by the Prefulfillment Ranker’s scorer to break ties between equally scored options.
     • SEO Purpose: Ensures the most relevant result is chosen when multiple options have similar relevance scores, improving user satisfaction.
     • How to Use: Optimize tiebreaking features to ensure the most relevant and user-friendly options are prioritized.
398. Prefulfillment Signals (AssistantPrefulfillmentRankerPrefulfillmentSignals)
     • Description: Signals derived from ParsingSignals and GroundingSignals used by the Prefulfillment Ranker to prioritize actions before fulfillment.
     • SEO Purpose: Enhances the relevance and efficiency of pre-fulfillment actions, ensuring quicker and more accurate responses to user queries.
     • How to Use: Implement and optimize prefulfillment signals to improve the accuracy and speed of user query responses.
399. Productivity List Item (AssistantProductivityListItem)
     • Description: Represents an item in a list, currently as a basic string but extensible for future enhancements.
     • SEO Purpose: Facilitates the creation and management of productivity lists, improving user organization and task management.
     • How to Use: Utilize and expand list items to enhance productivity features, making task management more efficient for users.
400. Reminders Attachment (AssistantRemindersAttachment)
     • Description: Describes an attachment to an Assistant Reminder, including different behaviors on various surfaces such as deeplinks.
     • SEO Purpose: Enhances the functionality and relevance of reminders by attaching useful links and notifications.
     • How to Use: Attach relevant links and notifications to reminders to increase their utility and ensure users are effectively reminded of tasks.
401. Attachment Link (AssistantRemindersAttachmentLink)
     • Description: Details the URL link and notification text for reminder attachments, supporting surface-specific deeplinks.
     • SEO Purpose: Improves user engagement with reminders by providing actionable links and clear notifications.
     • How to Use: Include relevant and actionable links in reminder notifications to enhance user engagement and reminder effectiveness.
402. Memory Payload (AssistantRemindersMemoryPayload)
     • Description: Stores the memory payload for reminders, requiring approval for updates to ensure data integrity.
     • SEO Purpose: Ensures reliable storage and retrieval of reminder data, enhancing user trust and reminder accuracy.
     • How to Use: Maintain and update memory payloads carefully to ensure accurate and reliable reminder functionality.
403. NLG Template Key (AssistantRemindersNlgTemplateKey)
     • Description: Equivalent to nlp_generation.TemplateKey, used for natural language generation templates in reminders.
     • SEO Purpose: Enhances the clarity and relevance of reminder notifications through effective natural language generation.
     • How to Use: Utilize NLG template keys to create clear and engaging reminder notifications, improving user interaction.
404. Teleport Nickname Signals (AssistantTeleportTeleportNicknameSignals)
     • Description: Indicates whether a nickname could refer to a location, app install info, generic nature of the name, nickname tier, and source.
     • SEO Purpose: Improves the accuracy and relevance of location-based and app-related searches by recognizing nicknames.
     • How to Use: Ensure nicknames are accurately interpreted to enhance location-based services and app interactions.
405. Contact Match Signal (AssistantVerticalsCommonContactMatchSignal)
     • Description: Neural signals used to match contacts accurately.
     • SEO Purpose: Enhances contact matching accuracy, ensuring users find the right contacts quickly.
     • How to Use: Optimize contact match signals to improve the accuracy and relevance of contact searches.
406. Action Project Config (AssistantVerticalsHomeautomationProtoActionProjectConfig)
     • Description: Metadata for configuring actions on Google for home automation.
     • SEO Purpose: Ensures the proper configuration and execution of home automation actions, improving user satisfaction.
     • How to Use: Maintain accurate action project configurations to ensure seamless execution of home automation tasks.
407. Agent Device ID (AssistantVerticalsHomeautomationProtoAgentDeviceId)
     • Description: Represents an agent and device pair that uniquely identifies a device.
     • SEO Purpose: Enhances device management and identification, ensuring precise control over home automation devices.
     • How to Use: Ensure each device has a unique and correctly paired agent device ID to improve device management and automation control.
408. Agent Information (AssistantVerticalsHomeautomationProtoAgentInformation)
     • Description: Represents details needed to support partnerships for home automation, covering both first-party and third-party integrations.
     • SEO Purpose: Facilitates seamless integration and operation of home automation devices, improving user experience.
     • How to Use: Maintain accurate and comprehensive agent information to support effective home automation partnerships and integrations.
409. Device or Structure Attributes (AssistantVerticalsHomeautomationProtoAttribute)
     • Description: Represents the attributes of a device or structure, approved and formalized by the home automation team.
     • SEO Purpose: Ensures accurate representation of device and structure attributes, improving automation functionality.
     • How to Use: Regularly update and maintain device or structure attributes to ensure accurate and efficient home automation operations.
410. Common Event Trigger (AssistantVerticalsHomeautomationProtoCommonEventTrigger)
     • Description: Represents common triggers for events in home automation.
     • SEO Purpose: Enhances the responsiveness and relevance of home automation actions based on common triggers.
     • How to Use: Implement and optimize common event triggers to ensure timely and appropriate home automation responses.
411. Structure Based Routine (AssistantVerticalsHomeautomationProtoCommonStructureBasedRoutine)
     • Description: Stores core data for structure-based routines, with metadata added as needed.
     • SEO Purpose: Enhances the functionality and relevance of structure-based routines, improving user satisfaction with home automation.
     • How to Use: Maintain and optimize structure-based routines to ensure effective and reliable home automation actions.
412. Structure Based Routine Trigger (AssistantVerticalsHomeautomationProtoCommonStructureBasedRoutineTrigger)
     • Description: Represents triggers for structure-based routines in home automation.
     • SEO Purpose: Ensures timely and relevant execution of routines based on structure triggers, enhancing user experience.
     • How to Use: Implement accurate and responsive routine triggers to optimize home automation efficiency and effectiveness.
413. Voice Trigger (AssistantVerticalsHomeautomationProtoCommonVoiceTrigger)
     • Description: Represents triggers for home automation actions based on voice commands.
     • SEO Purpose: Enhances the responsiveness and accuracy of voice-activated home automation, improving user interaction.
     • How to Use: Optimize voice triggers to ensure precise and reliable voice command responses, enhancing home automation usability.
414. Concierge Features (AssistantVerticalsHomeautomationProtoConciergeFeatures)
     • Description: Features that a structure is eligible for, improving home automation concierge services.
     • SEO Purpose: Enhances the functionality and user experience of home automation concierge features.
     • How to Use: Implement and optimize concierge features to provide high-quality home automation services, improving user satisfaction.
415. Device Targeting Output Query Info (AssistantVerticalsHomeautomationProtoDeviceTargetingOutputQueryInfo)
     • Description: Represents query information for device targeting in home automation.
     • SEO Purpose: Improves the accuracy and relevance of device targeting queries, ensuring precise device control.
     • How to Use: Optimize query information to enhance device targeting accuracy, improving user interactions with home automation systems.
416. Home Automation Device (AssistantVerticalsHomeautomationProtoHomeAutomationDevice)
     • Description: Represents a home automation device with unique identifiers and attributes.
     • SEO Purpose: Ensures accurate identification and management of home automation devices, improving control and functionality.
     • How to Use: Maintain detailed and accurate information for each home automation device to ensure effective management and control.
417. Home Automation Device Item (AssistantVerticalsHomeautomationProtoHomeAutomationDeviceItem)
     • Description: Represents an item within a home automation device, including metadata and matched item details.
     • SEO Purpose: Enhances the management and functionality of specific device items, improving home automation control.
     • How to Use: Ensure each device item is accurately represented and managed to optimize home automation performance.
418. Home Automation Metadata (AssistantVerticalsHomeautomationProtoHomeAutomation_MetaData)
     • Description: Represents metadata for home automation devices, supporting various traits and features.
     • SEO Purpose: Ensures comprehensive and accurate metadata for home automation devices, improving control and functionality.
     • How to Use: Maintain and update device metadata to ensure accurate representation and efficient home automation operations.
419. Metadata Supported Traits (AssistantVerticalsHomeautomationProtoHomeAutomation_MetaDataSupportedTraits)
     • Description: Lists the traits supported by home automation devices.
     • SEO Purpose: Enhances the functionality of home automation devices by supporting various traits.
     • How to Use: Ensure that devices support relevant traits to improve home automation capabilities and user satisfaction.
420. Matter Unique ID (AssistantVerticalsHomeautomationProtoMatterUniqueId)
     • Description: Represents the unique ID values provided by home automation devices.
     • SEO Purpose: Ensures precise identification and management of home automation devices, improving control and tracking.
     • How to Use: Utilize unique IDs to accurately identify and manage home automation devices, ensuring efficient operations.
421. Physical Location (AssistantVerticalsHomeautomationProtoPhysicalLocation)
     • Description: Represents the physical location of a device, including address and geolocation data.
     • SEO Purpose: Enhances the accuracy of location-based home automation actions, improving user satisfaction.
     • How to Use: Maintain accurate physical location data for devices to optimize location-based automation tasks.
422. Role Information (AssistantVerticalsHomeautomationProtoRoleInformation)
     • Description: Represents the user’s role for a device, such as assistant-only or manager.
     • SEO Purpose: Ensures appropriate access and control levels for users based on their roles, enhancing security and functionality.
     • How to Use: Assign and manage user roles accurately to ensure proper access and control over home automation devices.
423. Smart Device Management Data (AssistantVerticalsHomeautomationProtoSmartDeviceManagementData)
     • Description: Represents management data for smart devices, including enterprise ownership information.
     • SEO Purpose: Enhances the management and tracking of smart devices, ensuring efficient operations and analytics.
     • How to Use: Maintain and utilize smart device management data to improve control, tracking, and analytics of home automation systems.
424. Smart Home Features (AssistantVerticalsHomeautomationProtoSmartHomeFeatures)
     • Description: Represents feature flags that may be enabled for smart home items.
     • SEO Purpose: Enhances the functionality and customization of smart home devices, improving user satisfaction.
     • How to Use: Enable and configure smart home features to optimize device functionality and meet user needs.
425. Supported Structure Features (AssistantVerticalsHomeautomationProtoSupportedStructureFeatures)
     • Description: Lists the features supported by a home automation structure.
     • SEO Purpose: Ensures comprehensive support for various features within a home automation structure, improving functionality.
     • How to Use: Maintain and update the list of supported structure features to ensure efficient and effective home automation operations.
426. Mention Properties (AttentionalEntitiesMentionProperties)
     • Description: This factor represents the properties associated with mentions in a document, including attributes such as how an entity is mentioned and its context within the text.
     • SEO Purpose: Enhances the understanding of entity mentions in content, improving the relevance and accuracy of search results.
     • How to Use: Ensure mentions are clear and well-defined within your content to improve entity recognition and relevance in search results.
427. List Entry Information (AttentionalEntitiesMentionPropertiesListEntryInfo)
     • Description: Contains information about how an entity was presented as part of a list, detailing the entity’s position and context within the list.
     • SEO Purpose: Improves the organization and clarity of listed entities, enhancing the structured data for search engines.
     • How to Use: Clearly format and organize lists in your content to ensure entities are easily recognized and accurately indexed by search engines.
428. Mention Source (AttentionalEntitiesMentionPropertiesSource)
     • Description: Identifies the source from which a mention was derived, whether from an agent, system, or user input.
     • SEO Purpose: Provides context for entity mentions, enhancing the accuracy of content attribution and relevance.
     • How to Use: Clearly attribute sources of mentions in your content to provide context and improve content credibility.
429. Source Client (AttentionalEntitiesMentionPropertiesSourceClient)
     • Description: Indicates that the client provided the entity mention, often corresponding to on-device data.
     • SEO Purpose: Enhances the relevance of personalized content by accurately identifying client-sourced mentions.
     • How to Use: Leverage client data to personalize mentions in your content, improving user engagement and relevance.
430. Source System (AttentionalEntitiesMentionPropertiesSourceSystem)
     • Description: Specifies that the mention was provided by the Assistant during fulfillment, typically through developer annotations.
     • SEO Purpose: Improves the accuracy of system-generated content, ensuring relevant responses and interactions.
     • How to Use: Utilize system annotations to enhance the relevance and accuracy of content provided by automated systems.
431. Source User (AttentionalEntitiesMentionPropertiesSourceUser)
     • Description: Indicates that the user mentioned the entity, derived from previous user intents or queries.
     • SEO Purpose: Enhances the personalization and relevance of content by accurately identifying user-generated mentions.
     • How to Use: Track and analyze user mentions to personalize content and improve user satisfaction.
432. Semantic Role ID (AttentionalEntitiesSemanticRoleId)
     • Description: Uniquely identifies a semantic role within an intent, mapping to specific slots in the intent catalog.
     • SEO Purpose: Improves the accuracy of intent recognition and fulfillment, enhancing the relevance of search results.
     • How to Use: Ensure semantic roles are clearly defined and mapped in your content to improve intent recognition and relevance.
433. Spatial Properties (AttentionalEntitiesSpatialProperties)
     • Description: Represents the properties of visual mentions, such as display attributes and visibility to the user.
     • SEO Purpose: Enhances the clarity and relevance of visual content by accurately representing spatial properties.
     • How to Use: Optimize visual mentions to ensure they are clearly displayed and easily recognizable to users and search engines.
434. Surface Form (AttentionalEntitiesSurfaceForm)
     • Description: Describes how an entity was presented at the surface level, such as variations in names or titles.
     • SEO Purpose: Improves the recognition and relevance of entity mentions by accounting for different surface forms.
     • How to Use: Use consistent and recognizable surface forms for entities to improve their relevance and indexing in search results.
435. Document Biasing Data (BiasingPerDocData)
     • Description: Represents data used to bias or influence the ranking of documents independently from normal ranking algorithms.
     • SEO Purpose: Enhances the relevance of search results by applying specific biases based on document data.
     • How to Use: Optimize document data to align with desired biases, improving the relevance and ranking of your content.
436. Efficient Document Biasing Data (BiasingPerDocData2)
     • Description: A more efficient version of document biasing data, reducing size while maintaining effectiveness.
     • SEO Purpose: Improves search efficiency and relevance by optimizing document biasing data.
     • How to Use: Implement efficient biasing data structures to enhance search performance and relevance.
437. Biasing Field (BiasingPerDocData2BiasingField)
     • Description: Metadata fields used to bias search results, sorted independently from normal ranking using a ScoreAdjuster.
     • SEO Purpose: Enhances the control over search result rankings by applying specific biases through metadata fields.
     • How to Use: Optimize metadata fields to influence search result rankings, ensuring relevant content is prioritized.
438. Blob Reference (BlobstoreBlobRef)
     • Description: A reference to a blob in BlobStore, ensuring secure manipulation and storage of blob data.
     • SEO Purpose: Enhances the security and efficiency of data storage and retrieval, improving content management.
     • How to Use: Use secure blob references for data storage to maintain the integrity and security of your content.
439. Blog Document Data (BlogPerDocData)
     • Description: Additional data for blog posts, including attributes that enhance the understanding and relevance of blog content.
     • SEO Purpose: Improves the indexing and relevance of blog content by providing comprehensive document data.
     • How to Use: Ensure blog posts are enriched with relevant data to improve their visibility and relevance in search results.
440. Blog Outlinks (BlogPerDocDataOutlinks)
     • Description: Contains resolved URLs and site spam scores for outlinks in blog updates.
     • SEO Purpose: Enhances the credibility and relevance of blog content by managing outlinks effectively.
     • How to Use: Monitor and optimize outlinks in your blog content to maintain credibility and improve search rankings.
441. Conversation Node (BlogsearchConversationNode)
     • Description: Represents a node in a conversation tree, including details about the author, creation date, and parent-child relationships.
     • SEO Purpose: Improves the structure and relevance of conversation data, enhancing user engagement and search indexing.
     • How to Use: Organize conversation data effectively to improve readability and relevance, ensuring clear parent-child relationships.
442. Conversation Tree (BlogsearchConversationTree)
     • Description: Represents the entire conversation tree, including all nodes and their relationships.
     • SEO Purpose: Enhances the understanding and indexing of conversation structures, improving search relevance.
     • How to Use: Ensure conversation trees are well-structured and clearly defined to improve search visibility and user engagement.
443. Supported Services (BlueGingerClientVisibleProtoBlueGingerSupportedServices)
     • Description: Indicates the availability of BlueGinger services for businesses, detailing supported modules and services.
     • SEO Purpose: Enhances the visibility and relevance of business services by accurately representing supported features.
     • How to Use: Clearly define and communicate supported services to improve business visibility and user engagement.
444. Supported Services Module (BlueGingerClientVisibleProtoBlueGingerSupportedServicesBlueGingerModule)
     • Description: Details the supported services within a module, including service names and use cases.
     • SEO Purpose: Improves the relevance and visibility of specific business services by accurately representing module details.
     • How to Use: Ensure service modules are well-defined and communicated to enhance business visibility and user engagement.
445. Book Citation Data (BookCitationPerDocData)
     • Description: Per-document data for cited books, providing detailed citation information.
     • SEO Purpose: Enhances the credibility and relevance of content by providing accurate book citation data.
     • How to Use: Include detailed and accurate book citations in your content to improve its credibility and search relevance.
446. Business Hours (BusinessHours)
     • Description: Represents the open intervals for a business throughout the week, ensuring they are ordered and non-overlapping.
     • SEO Purpose: Enhances the accuracy and relevance of business listings by providing detailed business hours.
     • How to Use: Clearly define business hours to improve visibility in search results and ensure accurate business information.
447. Business Hours Interval (BusinessHoursInterval)
     • Description: Details the start and end times for business hours within a specific interval.
     • SEO Purpose: Improves the accuracy of business hour representations, enhancing user trust and search relevance.
     • How to Use: Accurately specify business hour intervals to ensure users receive correct and reliable business information.
448. Bot Send Token (ChatBotPlatformBotSendToken)
     • Description: A token used by chatbots to facilitate communication and interactions.
     • SEO Purpose: Enhances the functionality and security of chatbot interactions, improving user engagement.
     • How to Use: Implement secure and functional tokens in chatbot interactions to ensure reliable and engaging user experiences.
449. Fireball ID (ChatBotPlatformFireballId)
     • Description: An identifier used for users and sessions in chatbot interactions, ensuring accurate identification.
     • SEO Purpose: Improves the personalization and relevance of chatbot interactions by accurately identifying users and sessions.
     • How to Use: Utilize Fireball IDs to ensure accurate and personalized chatbot interactions, enhancing user satisfaction.
450. Porn Classifier Data (ClassifierPornClassifierData)
     • Description: Represents data used to classify pornographic content, including labels and scores.
     • SEO Purpose: Ensures content safety and relevance by accurately classifying and filtering pornographic material.
     • How to Use: Implement robust porn classifier data to maintain content safety and comply with content guidelines.
451. Porn Document Data (ClassifierPornDocumentData)
     • Description: Represents data used to classify documents as pornographic, improving content filtering and safety.
     • SEO Purpose: Enhances content safety by accurately identifying and filtering pornographic documents.
     • How to Use: Use accurate porn document data to ensure content safety and compliance with guidelines.
452. Query Classifier Output (ClassifierPornQueryClassifierOutput)
     • Description: Generic output for classifying queries as pornographic, ensuring accurate content filtering.
     • SEO Purpose: Improves content safety by accurately classifying pornographic queries.
     • How to Use: Implement query classifier outputs to maintain content safety and compliance with content guidelines.
453. Multi-label Classifier Output (ClassifierPornQueryMultiLabelClassifierOutput)
     • Description: Represents the output for multi-label classification of pornographic content across various verticals.
     • SEO Purpose: Enhances content filtering by accurately classifying pornographic content across multiple categories.
     • How to Use: Use multi-label classifier outputs to ensure comprehensive content safety and compliance with guidelines.
454. Query Statistics (ClassifierPornQueryStats)
     • Description: Contains statistics about queries used to search for pornographic content, aiding in content analysis and filtering.
     • SEO Purpose: Enhances content safety by providing detailed query statistics for pornographic searches.
     • How to Use: Analyze query statistics to improve content filtering and maintain content safety.
455. Referrer Counts (ClassifierPornReferrerCounts)
     • Description: Stores the count of referrers classified as pornographic, including landing pages and inherited counts.
     • SEO Purpose: Enhances content safety by tracking and filtering pornographic referrers.
     • How to Use: Monitor and manage referrer counts to ensure accurate content filtering and maintain content safety.
456. Site Data (ClassifierPornSiteData)
     • Description: Represents data for sites containing pornographic content, aiding in content filtering and classification.
     • SEO Purpose: Enhances content safety by accurately identifying and filtering pornographic sites.
     • How to Use: Utilize site data to maintain content safety and ensure compliance with content guidelines.
457. Versioned Site Score (ClassifierPornSiteDataVersionedScore)
     • Description: Represents the porn score of a site, maintaining multiple versions for accuracy across changes.
     • SEO Purpose: Improves content filtering by providing accurate and up-to-date porn scores for sites.
     • How to Use: Monitor and update site scores to ensure accurate content filtering and maintain content safety.
458. Site Violence Statistics (ClassifierPornSiteViolenceStats)
     • Description: Stores statistics related to violent content on pornographic sites, enhancing content filtering.
     • SEO Purpose: Enhances content safety by accurately identifying and filtering violent content on pornographic sites.
     • How to Use: Use violence statistics to improve content filtering and ensure compliance with safety guidelines.
459. Cloud SQL Instance Config (CloudAiPlatformTenantresourceCloudSqlInstanceConfig)
     • Description: Configures a CloudSQL instance for tenant resources, ensuring proper setup and management.
     • SEO Purpose: Enhances the management and performance of cloud resources by providing detailed configuration options.
     • How to Use: Configure CloudSQL instances accurately to ensure efficient and reliable cloud resource management.
460. GCS Bucket Config (CloudAiPlatformTenantresourceGcsBucketConfig)
     • Description: Configures a GCS bucket for tenant resources, ensuring proper setup and management.
     • SEO Purpose: Improves the management and performance of cloud storage by providing detailed configuration options.
     • How to Use: Set up and configure GCS buckets accurately to ensure efficient and reliable cloud storage management.
461. IAM Policy Binding (CloudAiPlatformTenantresourceIamPolicyBinding)
     • Description: Defines dynamic IAM bindings for tenant projects, ensuring proper access control and security.
     • SEO Purpose: Enhances security and access management for cloud resources by providing detailed IAM policy bindings.
     • How to Use: Implement IAM policy bindings to ensure secure and controlled access to cloud resources.
462. Spanner Config (CloudAiPlatformTenantresourceInfraSpannerConfig)
     • Description: Configures a Spanner database for tenant resources, providing options for setup and management.
     • SEO Purpose: Improves the management and performance of Spanner databases by providing detailed configuration options.
     • How to Use: Configure Spanner databases accurately to ensure efficient and reliable cloud resource management.
463. Create Database Options (CloudAiPlatformTenantresourceInfraSpannerConfigCreateDatabaseOptions)
     • Description: Provides options for creating a Spanner database, including audit logging and resource management.
     • SEO Purpose: Enhances the setup and management of Spanner databases by providing comprehensive creation options.
     • How to Use: Utilize database creation options to ensure proper setup and management of Spanner databases.
464. Service Account Identity (CloudAiPlatformTenantresourceServiceAccountIdentity)
     • Description: Configures the identity for service accounts in tenant projects, ensuring proper access control.
     • SEO Purpose: Enhances security and access management by providing detailed service account configurations.
     • How to Use: Implement service account identities to ensure secure and controlled access to cloud resources.
465. Tenant Project Config (CloudAiPlatformTenantresourceTenantProjectConfig)
     • Description: Configures tenant projects, providing detailed setup and management options for cloud resources.
     • SEO Purpose: Improves the management and performance of tenant projects by providing comprehensive configuration options.
     • How to Use: Set up and configure tenant projects accurately to ensure efficient and reliable cloud resource management.
466. Tenant Project Resource (CloudAiPlatformTenantresourceTenantProjectResource)
     • Description: Represents the resources associated with tenant projects, ensuring proper setup and management.
     • SEO Purpose: Enhances the management and performance of tenant resources by providing detailed resource configurations.
     • How to Use: Manage tenant project resources accurately to ensure efficient and reliable cloud resource management.
467. Tenant Service Account Identity (CloudAiPlatformTenantresourceTenantServiceAccountIdentity)
     • Description: Configures the identity for service accounts created under tenant projects, ensuring proper access control.
     • SEO Purpose: Enhances security and access management by providing detailed service account configurations.
     • How to Use: Implement tenant service account identities to ensure secure and controlled access to cloud resources.
468. Deep Tag (CommerceDatastoreDeepTag)
     • Description: Contains decision outputs from deep tagging algorithms, providing detailed tag information.
     • SEO Purpose: Enhances content categorization and relevance by utilizing deep tagging algorithms.
     • How to Use: Implement deep tagging to improve content categorization and ensure relevant search results.
469. Image Deep Tags (CommerceDatastoreImageDeepTags)
     • Description: These tags are computed at the image level to provide signals about the image’s characteristics, such as background type, collage presence, cropping quality, non-family-safe content, object count, and overlay elements like watermarks and logos.
     • SEO Purpose: Improves the categorization and filtering of images based on their visual content, enhancing search relevance and user experience.
     • How to Use: Use these deep tags to ensure images on your site are well-categorized and filtered, maintaining quality and relevance in image search results.
470. Image Deep Tags Model Output (CommerceDatastoreImageDeepTagsModelOutput)
     • Description: Contains detailed attributes for each image tag, such as background type, collage, cropping, model type, non-family-safe content, object count, overlay, selfie, and text overlay.
     • SEO Purpose: Provides granular details about images, allowing for better indexing and relevance in visual searches.
     • How to Use: Leverage these attributes to refine image categorization and improve the accuracy of visual content indexing on your site.
471. Composite Document (CompositeDoc)
     • Description: This protocol collects comprehensive information about a document, including pagerank, language, alternate names, duplicates, included content, indexing info, and experiment data.
     • SEO Purpose: Ensures thorough and detailed indexing of documents, improving their visibility and relevance in search results.
     • How to Use: Ensure all relevant information about your documents is included in the CompositeDoc to maximize their indexing potential and search ranking.
472. Included Content (CompositeDocIncludedContent)
     • Description: Details how content came to be included in a document, including source type, included document details, link URL, and properties.
     • SEO Purpose: Provides context and provenance for included content, enhancing document credibility and relevance.
     • How to Use: Clearly attribute and detail included content to improve document credibility and search relevance.
473. Indexing Information (CompositeDocIndexingInfo)
     • Description: Contains information primarily used within indexing processes, including data generated in specific indexing systems.
     • SEO Purpose: Enhances the accuracy and efficiency of the indexing process, ensuring documents are properly indexed and ranked.
     • How to Use: Maintain accurate indexing information to improve document indexing and search visibility.
474. Live Experiment Information (CompositeDocLiveExperimentInfo)
     • Description: Includes information needed for live experiments, such as experiment IDs and selected documents for different experiments.
     • SEO Purpose: Allows for the testing and optimization of document performance in search results.
     • How to Use: Utilize live experiment data to refine and improve document performance and ranking through controlled tests.
475. Localized Variations (CompositeDocLocalizedVariations)
     • Description: Contains localized alternate names and computed variations for documents, aiding in region-specific indexing and serving.
     • SEO Purpose: Improves the relevance and accuracy of search results by accounting for regional and language preferences.
     • How to Use: Provide localized variations of document names to ensure better search relevance for users in different regions.
476. Partial Update Information (CompositeDocPartialUpdateInfo)
     • Description: Details information about partial updates to a document, including last full indexing data.
     • SEO Purpose: Ensures that partial updates to documents are accurately tracked and reflected in search indexes.
     • How to Use: Implement and track partial updates to documents to maintain accurate and up-to-date search indexing.
477. Quality Signals (CompositeDocQualitySignals)
     • Description: Contains data related to document freshness, although it no longer holds traditional quality signals.
     • SEO Purpose: Helps maintain the timeliness and relevance of documents in search results.
     • How to Use: Keep document freshness data up-to-date to ensure relevance and improve search rankings.
478. Robots Info List (CompositeDocRobotsInfoList)
     • Description: Lists robots information parsed for different user-agents other than the default crawler.
     • SEO Purpose: Ensures proper handling of robots.txt directives for various crawlers, improving indexing control.
     • How to Use: Provide comprehensive robots information to ensure correct indexing and crawling behavior for your site.
479. Compressed Quality Signals (CompressedQualitySignals)
     • Description: Contains per-document signals that are compressed for efficient storage and retrieval in search systems.
     • SEO Purpose: Enhances the efficiency and accuracy of preliminary scoring in search results.
     • How to Use: Implement compressed quality signals to improve search performance and document ranking.
480. Concept ID (ConceptsConceptId)
     • Description: Represents a unique identifier for a concept, aiding in the categorization and linking of related content.
     • SEO Purpose: Enhances the semantic understanding and categorization of content, improving search relevance.
     • How to Use: Utilize concept IDs to link related content and improve semantic search capabilities.
481. Content Attributions (ContentAttributions)
     • Description: Stores attributions from one page to another, giving credit for content and influencing ranking.
     • SEO Purpose: Promotes attributed pages by recognizing their contributions to the content.
     • How to Use: Provide clear attributions to ensure credited content is promoted and gains visibility in search results.
482. Outgoing Attribution (ContentAttributionsOutgoingAttribution)
     • Description: Represents outgoing attributions from one page to another, aiding in content promotion and ranking.
     • SEO Purpose: Enhances the visibility of attributed pages, promoting their relevance in search results.
     • How to Use: Ensure outgoing attributions are clear and accurate to boost the visibility and ranking of credited content.
483. Content-Aware Crops (ContentAwareCropsIndexing)
     • Description: Provides a compact representation of image crops for efficient storage and retrieval.
     • SEO Purpose: Enhances the relevance and quality of image search results by ensuring optimal cropping.
     • How to Use: Implement content-aware crops to improve the visual quality and relevance of images in search results.
484. Lexical Metadata (CopleyLexicalMetadata)
     • Description: Stores lexical metadata for references, aiding in the localization and contextual understanding of content.
     • SEO Purpose: Improves the accuracy and relevance of localized content by providing detailed lexical metadata.
     • How to Use: Use lexical metadata to enhance the localization and context of your content, improving its search relevance.
485. Personal Reference (CopleyPersonalReference)
     • Description: Represents a reference to a personal entity made by a user, aiding in personalization.
     • SEO Purpose: Enhances the personalization and relevance of content by recognizing personal references.
     • How to Use: Leverage personal references to tailor content to individual users, improving engagement and relevance.
486. Personal Reference Metadata (CopleyPersonalReferenceMetadata)
     • Description: Stores metadata about personal references, even if the entities cannot be fully resolved.
     • SEO Purpose: Enhances the understanding and personalization of content by providing detailed reference metadata.
     • How to Use: Maintain accurate metadata for personal references to improve content personalization and relevance.
487. Source Type List (CopleySourceTypeList)
     • Description: Contains source and type information related to personal entities, such as whether they come from email, calendar, etc.
     • SEO Purpose: Improves the categorization and relevance of personal entity references by detailing their source and type.
     • How to Use: Clearly define and categorize sources and types of personal entities to enhance content relevance and personalization.
488. Source Type Metadata (CopleySourceTypeMetadata)
     • Description: Represents the source and type information for personal entities, such as hotels, restaurants, and their data sources.
     • SEO Purpose: Enhances the accuracy and relevance of personal entity data by detailing their source and type.
     • How to Use: Utilize source type metadata to improve the categorization and relevance of personal entities in content.
489. Subreference Metadata (CopleySubreferenceMetadata)
     • Description: Represents the most compound resolved entities and nested unresolved references, useful for complex references.
     • SEO Purpose: Enhances the understanding and resolution of complex references, improving content relevance.
     • How to Use: Implement subreference metadata to accurately resolve and represent complex references in your content.
490. Subreference Reference (CopleySubreferenceReference)
     • Description: Represents a reference that is part of a larger compound reference, aiding in detailed understanding.
     • SEO Purpose: Improves the accuracy and relevance of complex references by detailing their components.
     • How to Use: Use subreference references to break down and accurately represent complex references, enhancing content relevance.
491. Subreference Resolution (CopleySubreferenceResolution)
     • Description: Represents a resolution that is part of a larger compound reference, aiding in detailed understanding.
     • SEO Purpose: Enhances the accuracy and relevance of complex reference resolutions, improving content understanding.
     • How to Use: Implement subreference resolutions to accurately resolve and represent complex references, enhancing content relevance.
492. Corpus Selection Info (CorpusSelectionInfo)
     • Description: Contains information about the selection of a corpus for indexing, including corpus score and referrer details.
     • SEO Purpose: Enhances the relevance and accuracy of content indexing by providing detailed corpus selection information.
     • How to Use: Use corpus selection info to refine and improve the selection of content for indexing, ensuring high relevance and accuracy.
493. Country Click Distribution (CountryClickDistribution)
     • Description: Stores click distribution data by country, aiding in the understanding of geographic engagement.
     • SEO Purpose: Improves the relevance and targeting of content by providing insights into geographic click patterns.
     • How to Use: Analyze country click distribution data to tailor content and marketing strategies to different geographic regions.
494. Country Attachment (CountryCountryAttachment)
     • Description: Represents attachments related to a specific country, aiding in geographic categorization.
     • SEO Purpose: Enhances the geographic relevance of content by providing detailed country-related attachments.
     • How to Use: Utilize country attachments to improve the geographic categorization and relevance of your content.
495. Geo Location (CountryGeoLocation)
     • Description: Stores a single geographic location and its associated metadata.
     • SEO Purpose: Enhances the accuracy and relevance of location-based content by providing detailed geographic information.
     • How to Use: Maintain accurate geo location data to improve the relevance and targeting of location-based content.
496. Geo Locations (CountryGeoLocations)
     • Description: Contains a list of geographic locations assigned to a document, enhancing location-based relevance.
     • SEO Purpose: Improves the relevance of location-based content by providing detailed geographic information for documents.
     • How to Use: Ensure documents have accurate geo locations to enhance their relevance in location-based searches.
497. Location Info (CountryLocationInfo)
     • Description: Represents detailed information about a single location, aiding in geographic categorization.
     • SEO Purpose: Enhances the relevance and accuracy of location-based content by providing detailed location information.
     • How to Use: Maintain accurate location info to improve the relevance and targeting of location-based content.
498. Metro Feature (CountryMetroNBFeature)
     • Description: Represents metro features, keyed by NavBoost feature ID, aiding in geographic categorization.
     • SEO Purpose: Improves the relevance and accuracy of metro-specific content by providing detailed metro feature information.
     • How to Use: Utilize metro features to enhance the relevance and targeting of content for specific metropolitan areas.
499. Province Geotoken (CountryProvinceGeotoken)
     • Description: Represents a state-level geotoken, aiding in the geographic categorization of content.
     • SEO Purpose: Enhances the relevance and accuracy of state-specific content by providing detailed geotoken information.
     • How to Use: Implement province geotokens to improve the geographic relevance and targeting of state-specific content.
500. Salient Country (CountrySalientCountry)
     • Description: Represents the estimated probability of a document being relevant to a specific country, providing salience values.
     • SEO Purpose: Improves the geographic relevance of content by estimating its relevance to different countries.
     • How to Use: Use salient country data to tailor content and marketing strategies to different geographic regions.
501. Multiple Component Distribution (CrawlerChangerateMultipleComponentDistribution)
     • Description: Contains parameters for multiple component distributions, each with a non-negative weight summing to one.
     • SEO Purpose: Enhances the accuracy of content change rate predictions by using multiple component distributions.
     • How to Use: Implement multiple component distributions to improve the accuracy of content change rate predictions and indexing.
502. Single Component Distribution (CrawlerChangerateSingleComponentDistribution)
     • Description: Contains parameters for a single component distribution, aiding in change rate predictions.
     • SEO Purpose: Improves the accuracy of content change rate predictions by using single component distributions.
     • How to Use: Utilize single component distributions to enhance the accuracy of content change rate predictions and indexing.
503. URL Change (CrawlerChangerateUrlChange)
     • Description: Represents changes to a URL, aiding in the tracking and prediction of content updates.
     • SEO Purpose: Enhances the accuracy of content update predictions by tracking URL changes.
     • How to Use: Monitor URL changes to improve the prediction and indexing of content updates.
504. URL Change Rate (CrawlerChangerateUrlChangerate)
     • Description: Represents the change rate for a URL, aiding in the prediction of content updates.
     • SEO Purpose: Improves the accuracy of content update predictions by providing detailed change rate information.
     • How to Use: Utilize URL change rate data to enhance the prediction and indexing of content updates.
505. URL History (CrawlerChangerateUrlHistory)
     • Description: Contains the history of changes for a URL, including all observed versions and changes.
     • SEO Purpose: Enhances the accuracy of content update predictions by providing detailed URL change history.
     • How to Use: Maintain accurate URL history to improve the prediction and indexing of content updates.
506. URL Version (CrawlerChangerateUrlVersion)
     • Description: Represents a specific version of a URL, aiding in the tracking and prediction of content updates.
     • SEO Purpose: Improves the accuracy of content update predictions by providing detailed URL version information.
     • How to Use: Monitor URL versions to enhance the prediction and indexing of content updates.
507. Crowding Per Doc Data (CrowdingPerDocData)
     • Description: Contains data about crowding in documents, including clustering iterations for news content.
     • SEO Purpose: Enhances the organization and relevance of crowded content, improving search results.
     • How to Use: Use crowding data to organize and refine crowded content, ensuring better search relevance and user experience.
508. News Cluster (CrowdingPerDocDataNewsCluster)
     • Description: Represents clustering data for news content, aiding in the organization and relevance of crowded news articles.
     • SEO Purpose: Improves the relevance and organization of news content by providing detailed clustering information.
     • How to Use: Implement news clustering to enhance the organization and relevance of crowded news content.
509. Deep Crop Indexing (DeepCropIndexing)
     • Description: Provides a compact representation of image crops for efficient storage and retrieval.
     • SEO Purpose: Enhances the relevance and quality of image search results by ensuring optimal cropping.
     • How to Use: Implement deep crop indexing to improve the visual quality and relevance of images in search results.
510. Deep Crop Pixels (DeepCropPixels)
     • Description: Represents the pixel coordinates for deep cropped images, aiding in visual content optimization.
     • SEO Purpose: Improves the visual relevance and quality of images by providing precise cropping coordinates.
     • How to Use: Utilize deep crop pixels to ensure optimal cropping and improve the visual relevance of images.
511. Document Properties (DocProperties)
     • Description: Stores properties of a document, which may be reused across indexing cycles if content remains unchanged.
     • SEO Purpose: Enhances the efficiency and accuracy of document indexing by maintaining consistent properties.
     • How to Use: Ensure document properties are accurately maintained and updated to improve indexing and search relevance.
512. Bad Title Info (DocPropertiesBadTitleInfo)
     • Description: Contains information about titles that are considered bad or misleading.
     • SEO Purpose: Improves the accuracy and credibility of search results by identifying and filtering bad titles.
     • How to Use: Monitor and update title information to ensure accuracy and avoid misleading or bad titles in search results.
513. Compressed Feature (DrishtiCompressedFeature)
     • Description: Represents compressed features for efficient storage and retrieval in visual content analysis.
     • SEO Purpose: Enhances the efficiency of visual content analysis by using compressed feature representations.
     • How to Use: Implement compressed features to improve the efficiency and accuracy of visual content analysis.
514. Dense Feature Data (DrishtiDenseFeatureData)
     • Description: Stores dense feature data for visual content, including extra information and feature values.
     • SEO Purpose: Enhances the analysis and categorization of visual content by providing detailed dense feature data.
     • How to Use: Utilize dense feature data to improve the accuracy and relevance of visual content analysis and categorization.
515. Dense Token Data (DrishtiDenseTokenData)
     • Description: Stores dense token data for visual content analysis.
     • SEO Purpose: Improves the categorization and relevance of visual content by providing detailed token data.
     • How to Use: Implement dense token data to enhance the analysis and categorization of visual content.
516. Feature Extra (DrishtiFeatureExtra)
     • Description: Represents additional information for features in visual content analysis.
     • SEO Purpose: Enhances the accuracy and depth of visual content analysis by providing extra feature information.
     • How to Use: Use feature extra data to provide additional context and improve the accuracy of visual content analysis.
517. Feature Set Data (DrishtiFeatureSetData)
     • Description: Represents a set of features for visual content analysis, including extra information and labels.
     • SEO Purpose: Improves the categorization and relevance of visual content by providing comprehensive feature set data.
     • How to Use: Utilize feature set data to enhance the analysis and categorization of visual content.
518. Feature Set Element (DrishtiFeatureSetDataFeatureSetElement)
     • Description: Stores features from a single group in visual content analysis.
     • SEO Purpose: Enhances the accuracy and relevance of visual content analysis by organizing features into groups.
     • How to Use: Implement feature set elements to improve the organization and accuracy of visual content analysis.
519. Feature Set Sequence (DrishtiFeatureSetDataSequence)
     • Description: Represents an ordered sequence of feature set data elements for visual content analysis.
     • SEO Purpose: Improves the accuracy of visual content analysis by maintaining an ordered sequence of features.
     • How to Use: Utilize feature set sequences to enhance the organization and accuracy of visual content analysis.
520. Indexed Feature Data (DrishtiIndexedFeatureData)
     • Description: Stores indexed feature data for visual content analysis, including extra information and feature values.
     • SEO Purpose: Enhances the efficiency and accuracy of visual content analysis by using indexed feature data.
     • How to Use: Implement indexed feature data to improve the efficiency and accuracy of visual content analysis.
521. Label Set Data (DrishtiLabelSetData)
     • Description: Represents a set of labels for visual content, including extra information and target values.
     • SEO Purpose: Improves the categorization and relevance of visual content by providing detailed label set data.
     • How to Use: Utilize label set data to enhance the categorization and relevance of visual content.
522. Label Set Element (DrishtiLabelSetElement)
     • Description: Represents an individual label within a label set for visual content analysis.
     • SEO Purpose: Enhances the accuracy and relevance of visual content analysis by providing detailed label information.
     • How to Use: Implement label set elements to improve the accuracy and relevance of visual content analysis.
523. Quantized Byte Dense Feature Data (DrishtiQuantizedByteDenseFeatureData)
     • Description: Stores quantized dense feature data for visual content analysis.
     • SEO Purpose: Enhances the efficiency of visual content analysis by using quantized feature representations.
     • How to Use: Utilize quantized dense feature data to improve the efficiency and accuracy of visual content analysis.
524. Quantized Byte Indexed Feature Data (DrishtiQuantizedByteIndexedFeatureData)
     • Description: Stores quantized indexed feature data for visual content analysis.
     • SEO Purpose: Improves the efficiency and accuracy of visual content analysis by using quantized indexed feature data.
     • How to Use: Implement quantized indexed feature data to enhance the efficiency and accuracy of visual content analysis.
525. Quantized Dense Feature Data (DrishtiQuantizedDenseFeatureData)
     • Description: Represents quantized dense feature data for visual content analysis.
     • SEO Purpose: Enhances the efficiency of visual content analysis by using quantized feature representations.
     • How to Use: Utilize quantized dense feature data to improve the efficiency and accuracy of visual content analysis.
526. Sparse Feature Data (DrishtiSparseFeatureData)
     • Description: Represents sparse feature data used for visual content analysis. Attributes include labels and values for the features, along with any additional information.
     • SEO Purpose: Enhances the accuracy of visual content analysis by providing detailed sparse feature data, improving search relevance for visual content.
     • How to Use: Utilize sparse feature data to improve the categorization and analysis of visual content on your site, ensuring better search visibility and relevance.
527. Encoded Thumbnail (DrishtiVesperEncodedThumbnail)
     • Description: Contains attributes of encoded thumbnail images, such as those used for video previews.
     • SEO Purpose: Improves the efficiency of video content indexing by providing detailed information about encoded thumbnails.
     • How to Use: Use encoded thumbnail attributes to optimize video previews and enhance the visual appeal and relevance of video content in search results.
528. Moving Thumbnail (DrishtiVesperMovingThumbnail)
     • Description: Represents a short video clip that serves as a preview for the full video content, often referred to as a moving thumbnail.
     • SEO Purpose: Enhances user engagement by providing dynamic previews of video content, improving click-through rates and user interaction.
     • How to Use: Implement moving thumbnails to provide engaging previews for video content, attracting more clicks and improving user experience.
529. Moving Thumbnail Score Components (DrishtiVesperMovingThumbnailScoreComponents)
     • Description: Summarizes the individual score components within a moving thumbnail, used for calculating a composite score.
     • SEO Purpose: Enhances the ranking accuracy of video content by providing detailed scoring components for moving thumbnails.
     • How to Use: Utilize score components to refine the ranking of video previews, ensuring the most engaging content is prioritized in search results.
530. Video Thumbnail (DrishtiVesperVideoThumbnail)
     • Description: Contains attributes of a video thumbnail, including timestamp, ID, quality scores, annotations, and features.
     • SEO Purpose: Improves the indexing and relevance of video content by providing comprehensive information about video thumbnails.
     • How to Use: Ensure video thumbnails are well-optimized with detailed attributes to enhance their relevance and visibility in search results.
531. Thumbnail Quality Score (DrishtiVesperThumbnailQualityScore)
     • Description: Represents the quality score of a video thumbnail, indicating its suitability for use as a preview image.
     • SEO Purpose: Enhances the relevance of video previews by ensuring high-quality thumbnails are prioritized in search results.
     • How to Use: Monitor and optimize the quality scores of video thumbnails to ensure the best previews are displayed in search results, improving user engagement.
532. Human Label (DrishtiVesperUserReportHumanLabel)
     • Description: Contains values for human labels applied to visual content, providing insights into user feedback and labeling accuracy.
     • SEO Purpose: Improves the relevance and accuracy of visual content analysis by incorporating human-generated labels.
     • How to Use: Utilize human labels to enhance the accuracy of visual content categorization and ensure that user feedback is integrated into content analysis.
533. Model Score (DrishtiVesperUserReportModelScore)
     • Description: Holds values for the score and source model used in visual content analysis, aiding in the evaluation of content quality.
     • SEO Purpose: Enhances the accuracy of visual content analysis by providing detailed model scores and their sources.
     • How to Use: Use model scores to evaluate and improve the quality of visual content, ensuring that high-quality content is prioritized in search results.
534. User Reported Thumbnail (DrishtiVesperUserReportUserReportedThumbnail)
     • Description: Contains values for thumbnails reported by users, providing insights into user preferences and feedback.
     • SEO Purpose: Enhances the relevance of visual content by incorporating user-reported thumbnails into content analysis.
     • How to Use: Monitor user-reported thumbnails to understand user preferences and improve the relevance of visual content in search results.
535. Video Thumbnail Container (DrishtiVesperVideoThumbnail)
     • Description: A container for video thumbnails with attributes such as timestamp, ID, quality scores, annotations, and features.
     • SEO Purpose: Enhances the relevance and indexing of video content by providing detailed information about video thumbnails.
     • How to Use: Ensure video thumbnails are accurately described and well-optimized to improve their relevance and visibility in search results.
536. Deep Link Data (EmbedsDeepLinkData)
     • Description: Used to construct deep-link URIs for activities or frames within an app, ensuring users are directed to the appropriate location whether they have the app installed or not.
     • SEO Purpose: Enhances user engagement by providing seamless navigation to app content, improving app usage and retention.
     • How to Use: Implement deep-link data to ensure users are directed to the right content within your app, improving user experience and engagement.
537. Embedded Client Item (EmbedsEmbedClientItem)
     • Description: Represents an embedded object within an update, acting as a wrapper for various item types.
     • SEO Purpose: Improves content richness and interaction by allowing diverse embedded objects within updates.
     • How to Use: Utilize embedded client items to enrich updates with diverse content types, enhancing user engagement and content interaction.
538. Packaging Service Client (EmbedsPackagingServiceClient)
     • Description: Stores client data registered for deep-linking features on platforms like Google+, aiding in content integration.
     • SEO Purpose: Enhances content integration and user engagement by enabling deep-linking features for registered clients.
     • How to Use: Register and configure packaging service clients to leverage deep-linking features, improving content accessibility and engagement.
539. Provenance (EmbedsProvenance)
     • Description: Records the source of an ItemScope when created via web fetch, providing context for content origin.
     • SEO Purpose: Enhances content credibility and traceability by recording provenance information.
     • How to Use: Include provenance data to ensure content origin is clear, improving trust and credibility with users and search engines.
540. Transient Data (EmbedsTransientData)
     • Description: Represents transient data that will not be saved on the server, used for temporary content processing.
     • SEO Purpose: Facilitates temporary data handling without affecting long-term content storage.
     • How to Use: Utilize transient data for temporary content processing needs, ensuring it does not impact long-term data storage and management.
541. Event ID (EventIdMessage)
     • Description: A 128-bit identifier uniquely identifying an event, such as a query, ensuring uniqueness through time and process information.
     • SEO Purpose: Enhances the tracking and analysis of events by providing unique identifiers for each event.
     • How to Use: Implement Event IDs to accurately track and analyze events, improving data integrity and analytical capabilities.
542. Extra Snippet Info Response (ExtraSnippetInfoResponse)
     • Description: Provides additional information for building snippets in search results, aiding in the creation of more informative snippets.
     • SEO Purpose: Enhances the quality and relevance of search snippets by incorporating additional information.
     • How to Use: Use extra snippet info to create more informative and engaging search snippets, improving click-through rates and user satisfaction.
543. Snippet Match Info (ExtraSnippetInfoResponseMatchInfo)
     • Description: Contains match information for titles, URLs, and weighted items in search snippets, aiding in snippet generation.
     • SEO Purpose: Improves the relevance and accuracy of search snippets by providing detailed match information.
     • How to Use: Utilize match info to refine and optimize search snippets, ensuring they accurately reflect query relevance and improve user engagement.
544. Snippet Query Subitem (ExtraSnippetInfoResponseQuerySubitem)
     • Description: Represents a query term, phrase, or synonym, including original query terms and their subitems.
     • SEO Purpose: Enhances the relevance of search snippets by accurately representing query terms and their variations.
     • How to Use: Implement query subitems to improve the accuracy and relevance of search snippets, ensuring they reflect the user’s query effectively.
545. Snippet Tidbit (ExtraSnippetInfoResponseTidbit)
     • Description: Contains information about specific segments (tidbits) in a document, including position, score, and highlighted text.
     • SEO Purpose: Enhances the relevance and informativeness of search snippets by providing detailed tidbit information.
     • How to Use: Use tidbit data to create precise and engaging search snippets, improving their relevance and user click-through rates.
546. Tidbit Anchor Info (ExtraSnippetInfoResponseTidbitAnchorInfo)
     • Description: Provides anchor-specific information for tidbits, enhancing the relevance and accuracy of anchor-based snippets.
     • SEO Purpose: Improves the relevance of search snippets that use anchors by providing detailed anchor information.
     • How to Use: Utilize anchor info to refine anchor-based snippets, ensuring they are accurate and relevant to the user’s query.
547. Face Indexing (FaceIndexing)
     • Description: Represents compact data for face indexing, aiding in the efficient storage and retrieval of facial recognition data.
     • SEO Purpose: Enhances the accuracy and efficiency of facial recognition in visual content, improving search relevance.
     • How to Use: Implement face indexing data to improve the accuracy and efficiency of facial recognition in visual content.
548. Compact Binary Classification (FatcatCompactBinaryClassification)
     • Description: Contains binary classification data for content, aiding in the categorization and filtering of various content types.
     • SEO Purpose: Enhances the accuracy of content classification and filtering, improving search relevance.
     • How to Use: Utilize binary classification data to accurately categorize and filter content, ensuring relevant results are prioritized.
549. Compact Document Classification (FatcatCompactDocClassification)
     • Description: Represents the result of content classification, including various taxonomies and binary classifications.
     • SEO Purpose: Improves the accuracy of document classification, enhancing the relevance of search results.
     • How to Use: Implement document classification data to refine and improve the categorization of content, ensuring relevant search results.
550. Compact Rephil Clusters (FatcatCompactRephilClusters)
     • Description: Contains rephil cluster data for content, aiding in the clustering and categorization of related content.
     • SEO Purpose: Enhances the relevance and organization of clustered content, improving search relevance.
     • How to Use: Use rephil clusters to group related content accurately, ensuring improved search relevance and content organization.
551. Compact Taxonomic Classification (FatcatCompactTaxonomicClassification)
     • Description: Represents a taxonomic classification of content, aiding in the hierarchical categorization of content types.
     • SEO Purpose: Enhances the relevance and accuracy of hierarchical content categorization, improving search results.
     • How to Use: Implement taxonomic classifications to accurately categorize content into hierarchies, improving search relevance and organization.
552. Contact Detail Hash (FocusBackendContactDetailHash)
     • Description: Represents a hash of contact details, aiding in the efficient and secure handling of contact information.
     • SEO Purpose: Enhances the security and efficiency of contact detail management.
     • How to Use: Utilize contact detail hashes to manage contact information securely and efficiently.
553. Contact Pointer (FocusBackendContactPointer)
     • Description: Represents a pointer to a contact, aiding in the management and retrieval of contact information.
     • SEO Purpose: Enhances the accuracy and efficiency of contact management.
     • How to Use: Implement contact pointers to improve the management and retrieval of contact information.
554. Device Contact ID (FocusBackendDeviceContactId)
     • Description: Represents a device contact ID, used to manage device-specific contact information.
     • SEO Purpose: Enhances the management of device-specific contacts.
     • How to Use: Utilize device contact IDs to manage and retrieve device-specific contact information efficiently.
555. Device ID (FocusBackendDeviceId)
     • Description: Represents a device ID, used to manage and identify devices within contact management systems.
     • SEO Purpose: Enhances the identification and management of devices.
     • How to Use: Implement device IDs to accurately manage and identify devices within contact management systems.
556. Device Raw Contact ID (FocusBackendDeviceRawContactId)
     • Description: Represents a raw device contact ID, aiding in the management of original contact information on devices.
     • SEO Purpose: Enhances the accuracy and management of device contact information.
     • How to Use: Utilize raw contact IDs to manage original device contact information accurately.
557. Other Contact ID (FocusBackendOtherContactId)
     • Description: Represents additional contact IDs that are not actively used for matching but provide supplementary information.
     • SEO Purpose: Enhances the management of supplementary contact information.
     • How to Use: Implement other contact IDs to manage supplementary contact information efficiently.
558. Secondary Contact ID (FocusBackendSecondaryContactId)
     • Description: Represents a secondary ID of a contact, aiding in the management of additional contact identifiers.
     • SEO Purpose: Enhances the management and retrieval of secondary contact information.
     • How to Use: Utilize secondary contact IDs to manage additional contact identifiers accurately.
559. Citation (FreebaseCitation)
     • Description: Contains information needed to correctly attribute the source of data, enhancing content credibility.
     • SEO Purpose: Enhances the credibility and trustworthiness of content by providing accurate source attributions.
     • How to Use: Ensure accurate citations are included in your content to improve its credibility and search ranking.
560. Freebase ID (FreebaseId)
     • Description: Represents identifiers used to reference topics in the Knowledge Graph, including machine IDs and human-readable IDs.
     • SEO Purpose: Enhances the accuracy and relevance of content referencing Knowledge Graph entities.
     • How to Use: Use Freebase IDs to accurately reference Knowledge Graph entities, improving content relevance and search visibility.
561. LatLong (FreebaseLatLong)
     • Description: Represents a geographic point, aiding in the geolocation of content.
     • SEO Purpose: Enhances the relevance of location-based content by providing accurate geolocation information.
     • How to Use: Implement LatLong data to improve the geolocation accuracy of your content, enhancing its relevance in location-based searches.
562. Measurement (FreebaseMeasurement)
     • Description: Represents a measurement value, aiding in the precise representation of quantified data.
     • SEO Purpose: Improves the accuracy and relevance of content by providing precise measurement data.
     • How to Use: Utilize measurement data to enhance the accuracy and relevance of quantified content.
563. Measurement Unit (FreebaseMeasurementUnit)
     • Description: Represents the unit of measurement, including details like power and unit ID.
     • SEO Purpose: Enhances the accuracy of quantified data by providing detailed measurement unit information.
     • How to Use: Implement measurement unit data to ensure precise and accurate representation of quantified content.
564. Nested Struct (FreebaseNestedStruct)
     • Description: Represents a nested structure of properties and values, aiding in the complex representation of content.
     • SEO Purpose: Enhances the relevance and accuracy of content by providing detailed nested structure information.
     • How to Use: Utilize nested structs to represent complex relationships within your content, improving its relevance and search visibility.
565. Property Value (FreebasePropertyValue)
     • Description: Associates properties with values in the context of a topic, aiding in the detailed representation of Knowledge Graph entities.
     • SEO Purpose: Improves the accuracy and relevance of content by providing detailed property value associations.
     • How to Use: Implement property values to enhance the representation of Knowledge Graph entities in your content, improving search relevance.
566. Topic (FreebaseTopic)
     • Description: Represents a Knowledge Graph entity with associated properties and values, aiding in the detailed representation of topics.
     • SEO Purpose: Enhances the accuracy and relevance of content by providing comprehensive topic information.
     • How to Use: Use Freebase topics to accurately represent Knowledge Graph entities in your content, improving its relevance and search visibility.
567. Value (FreebaseValue)
     • Description: Represents various types of Knowledge Graph values, including primitives, references, and compound values.
     • SEO Purpose: Enhances the accuracy and relevance of content by providing detailed value representations.
     • How to Use: Implement Freebase values to accurately represent Knowledge Graph entities and their properties in your content.
568. Document Base (GDocumentBase)
     • Description: Contains fundamental information about a document, aiding in its indexing and retrieval.
     • SEO Purpose: Enhances the relevance and accuracy of document indexing by providing detailed base information.
     • How to Use: Ensure your documents have comprehensive base information to improve their indexing and search visibility.
569. Document Base Content (GDocumentBaseContent)
     • Description: Represents the main content section of a document, including text and other elements.
     • SEO Purpose: Enhances the relevance and quality of content by providing detailed main content information.
     • How to Use: Optimize the main content section of your documents to ensure they are relevant and high-quality, improving search rankings.
570. Directory (GDocumentBaseDirectory)
     • Description: Holds snippet and title metadata from various sources, aiding in the creation of rich snippets.
     • SEO Purpose: Enhances the richness and relevance of snippets by providing detailed metadata.
     • How to Use: Utilize directory data to create rich and informative snippets, improving click-through rates and user engagement.
571. Original Content (GDocumentBaseOriginalContent)
     • Description: Contains the original, unconverted document, typically in formats like PDF or Word.
     • SEO Purpose: Enhances the credibility and traceability of content by providing access to the original document.
     • How to Use: Include original content data to improve the credibility and traceability of your documents, ensuring users and search engines can verify the original source.
572. Generic Snippet Response (GenericSnippetResponse)
     • Description: Provides a generic version of a snippet response, aiding in the creation of flexible and informative snippets.
     • SEO Purpose: Enhances the flexibility and informativeness of search snippets by providing a generic snippet response format.
     • How to Use: Use generic snippet responses to create flexible and informative search snippets, improving user engagement and click-through rates.
573. Supported Actions (GeoOndemandAssistantSupportedActions)
     • Description: Lists actions supported by the assistant for a local entity, aiding in interaction with local content.
     • SEO Purpose: Enhances user interaction with local content by providing supported action information.
     • How to Use: Implement supported actions to improve user interaction with local content, ensuring a seamless and engaging user experience.
574. Access Point (GeostoreAccessPointProto)
     • Description: Holds information about a single access point to a feature, aiding in the geographic representation of content.
     • SEO Purpose: Enhances the geographic relevance of content by providing detailed access point information.
     • How to Use: Utilize access point data to accurately represent geographic features, improving the relevance and accuracy of location-based content.
575. Address Component (GeostoreAddressComponentProto)
     • Description: Represents a parsed field within an address, aiding in the detailed representation of geographic locations.
     • SEO Purpose: Enhances the accuracy and relevance of geographic content by providing detailed address component information.
     • How to Use: Implement address components to improve the accuracy and relevance of geographic content, ensuring precise location representation.
576. Address Lines (GeostoreAddressLinesProto)
     • Description: Represents the unparsed portion of an address with an associated language, aiding in the representation of geographic locations.
     • SEO Purpose: Enhances the accuracy and relevance of geographic content by providing detailed address line information.
     • How to Use: Utilize address lines to improve the accuracy and relevance of geographic content, ensuring precise location representation.
577. Address (GeostoreAddressProto)
     • Description: Represents an address, partial address, or address range, aiding in the detailed representation of geographic locations.
     • SEO Purpose: Enhances the accuracy and relevance of geographic content by providing comprehensive address information.
     • How to Use: Implement address data to improve the accuracy and relevance of geographic content, ensuring precise location representation.
578. Address Range (GeostoreAddressRangeProto)
     • Description: Represents a range of numbers in an address, aiding in the detailed representation of geographic locations.
     • SEO Purpose: Enhances the accuracy and relevance of geographic content by providing detailed address range information.
     • How to Use: Utilize address ranges to improve the accuracy and relevance of geographic content, ensuring precise location representation.
579. Anchored Geometry (GeostoreAnchoredGeometryProto)
     • Description: Represents a feature’s geometry populated from a 3D geometry store, aiding in the accurate representation of geographic features.
     • SEO Purpose: Enhances the accuracy and relevance of geographic content by providing detailed anchored geometry information.
     • How to Use: Implement anchored geometry to improve the accuracy and relevance of geographic content, ensuring precise representation of features.
580. Applied Speed Limit (GeostoreAppliedSpeedLimitProto)
     • Description: Represents speed limits with a correctness trust level, aiding in the accurate representation of road features.
     • SEO Purpose: Enhances the relevance and accuracy of geographic content by providing detailed speed limit information.
     • How to Use: Utilize applied speed limit data to improve the accuracy and relevance of road-related content, ensuring precise representation of speed limits.
581. Attachment (GeostoreAttachmentsAttachmentProto)
     • Description: Contains structured data of a client-specified type, aiding in the detailed representation of geographic features.
     • SEO Purpose: Enhances the accuracy and relevance of geographic content by providing detailed attachment information.
     • How to Use: Implement attachments to improve the accuracy and relevance of geographic content, ensuring precise representation of features.
582. Attribute ID (GeostoreAttributeIdProto)
     • Description: Represents the unique ID of an attribute, aiding in the detailed representation and management of geographic features.
     • SEO Purpose: Enhances the accuracy and relevance of geographic content by providing detailed attribute ID information.
     • How to Use: Utilize attribute IDs to improve the accuracy and relevance of geographic content, ensuring precise representation and management of features.
583. Attribute (GeostoreAttributeProto)
     • Description: Protocol buffer for attaching attributes and values to instances, aiding in the detailed representation of geographic features.
     • SEO Purpose: Enhances the accuracy and relevance of geographic content by providing detailed attribute information.
     • How to Use: Implement attributes to improve the accuracy and relevance of geographic content, ensuring precise representation of features.
584. Attribute Value Display (GeostoreAttributeValueDisplayProto)
     • Description: Helps display language-specific names of attributes, aiding in the localization and accurate representation of geographic features.
     • SEO Purpose: Enhances the localization and accuracy of geographic content by providing detailed attribute value display information.
     • How to Use: Utilize attribute value displays to improve the localization and relevance of geographic content, ensuring precise representation of features.
585. Material Types (GeostoreBarrierLogicalMaterialProto)
     • Description: This attribute specifies the types of materials used for barriers, which can include a variety of materials like metal, wood, concrete, etc.
     • SEO Purpose: Enhances the understanding and categorization of physical barriers, which can be important for local searches and mapping applications.
     • How to Use: Include detailed material types for barriers to improve the accuracy and relevance of geographic content.
586. Best Locale (GeostoreBestLocaleProto)
     • Description: Holds information about the best-match locale for a feature, helping determine the appropriate local name for a feature.
     • SEO Purpose: Improves localization and relevance of search results by using the best locale match.
     • How to Use: Utilize best locale information to ensure features are correctly localized for different user regions.
587. BizBuilder Reference (GeostoreBizBuilderReferenceProto)
     • Description: References a BizBuilder listing, providing detailed business data.
     • SEO Purpose: Enhances the accuracy of business listings and their visibility in local search results.
     • How to Use: Link BizBuilder references to business features to improve the richness and reliability of business data.
588. Border Information (GeostoreBorderProto)
     • Description: Represents the division line between two features of the same type, such as country borders.
     • SEO Purpose: Enhances the accuracy of geographic data, particularly in mapping and boundary-related searches.
     • How to Use: Include detailed border information to improve the accuracy of map features and geographic searches.
589. Bounding Marker (GeostoreBoundingMarkerProto)
     • Description: Used for defining canonical bounding markers for geographic features.
     • SEO Purpose: Improves the precision and accuracy of geographic feature boundaries.
     • How to Use: Implement bounding markers to accurately define the extents of geographic features.
590. Building Attributes (GeostoreBuildingProto)
     • Description: Holds building-specific attributes for features of type compound building.
     • SEO Purpose: Enhances the detail and accuracy of building-related data, improving search relevance.
     • How to Use: Include building attributes to provide detailed information about compound buildings.
591. Business Chain Information (GeostoreBusinessChainProto)
     • Description: Contains data specific to business chains.
     • SEO Purpose: Enhances the visibility and relevance of business chain listings.
     • How to Use: Use business chain information to accurately represent and categorize chain businesses.
592. Business Hours (GeostoreBusinessHoursProto)
     • Description: Stores weekly schedules of opening hours for businesses, including related information.
     • SEO Purpose: Improves the accuracy and relevance of business operation hours in local searches.
     • How to Use: Include detailed business hours to provide accurate operation times for businesses.
593. Call to Action (GeostoreCallToActionProto)
     • Description: Contains calls to action specified by the business owner.
     • SEO Purpose: Enhances user engagement by providing clear calls to action in business listings.
     • How to Use: Implement calls to action to encourage user interaction and improve business visibility.
594. Canonical Concept (GeostoreCanonicalGConceptProto)
     • Description: Represents a canonical concept of a business chain’s members.
     • SEO Purpose: Improves the consistency and relevance of business chain data.
     • How to Use: Use canonical concepts to standardize and accurately represent business chains.
595. Cell Covering (GeostoreCellCoveringProto)
     • Description: Holds S2 cell covering for geographic features.
     • SEO Purpose: Enhances the precision of geographic feature representation.
     • How to Use: Implement cell covering data to improve the accuracy of geographic features in maps.
596. City JSON Representation (GeostoreCityJsonProto)
     • Description: Custom representation of the CityJSON spec for internal projects.
     • SEO Purpose: Improves the accuracy and detail of urban geographic data.
     • How to Use: Utilize CityJSON data to accurately represent city features and their attributes.
597. Appearance Attributes (GeostoreCityJsonProtoAppearance)
     • Description: Describes the appearance of a CityObject, including materials and textures.
     • SEO Purpose: Enhances the visual representation of city features in maps and applications.
     • How to Use: Include appearance attributes to improve the visual accuracy and appeal of city features.
598. City Object (GeostoreCityJsonProtoCityObject)
     • Description: Represents an object with geometry in the city.
     • SEO Purpose: Enhances the accuracy and relevance of urban geographic features.
     • How to Use: Implement city objects to provide detailed geometric representations of urban features.
599. Geometry Information (GeostoreCityJsonProtoCityObjectGeometry)
     • Description: Represents geometric primitives for constructing geometries of varying complexity.
     • SEO Purpose: Improves the accuracy and detail of geometric representations in urban data.
     • How to Use: Utilize geometric information to accurately represent the shapes and structures of urban features.
600. Transform Information (GeostoreCityJsonProtoTransform)
     • Description: Provides data for transforming points from an old to a new coordinate frame.
     • SEO Purpose: Enhances the accuracy of geographic transformations and representations.
     • How to Use: Use transform data to accurately shift and represent geographic points.
601. Composable Item (GeostoreComposableItemProto)
     • Description: Represents a generic item that can have various properties filled, such as a photo or name.
     • SEO Purpose: Enhances the flexibility and detail of geographic and business data representation.
     • How to Use: Use composable items to represent diverse geographic or business features with varying attributes.
602. Count Comparison (GeostoreCountComparisonProto)
     • Description: Contains a count value tagged with a comparison operator, used for attributes like axle count.
     • SEO Purpose: Improves the precision of attribute comparisons in geographic data.
     • How to Use: Implement count comparisons to accurately compare and analyze geographic or business attributes.
603. Crossing Stripe Pattern (GeostoreCrossingStripePatternProto)
     • Description: Defines patterns for crossing stripes, such as crosswalks and stop lines.
     • SEO Purpose: Enhances the accuracy of road and transportation feature representation.
     • How to Use: Include crossing stripe patterns to accurately represent transportation features on maps.
604. Curvature Data (GeostoreCurvatureProto)
     • Description: Provides curvature values at points along a flowline, aiding in detailed geographic representations.
     • SEO Purpose: Improves the accuracy and detail of geographic data for curvilinear features.
     • How to Use: Utilize curvature data to accurately represent the curves and bends in geographic features.
605. Curve Connection (GeostoreCurveConnectionProto)
     • Description: Defines the connection between two specified endpoints using various geometric parameters.
     • SEO Purpose: Enhances the accuracy and precision of geographic data involving curves and endpoints.
     • How to Use: Implement this to accurately map curved connections between points, ensuring precise geographic representations.
606. Bezier Curve Parameters (GeostoreCurveConnectionProtoBezierParams)
     • Description: Contains parameters for Bezier curves, including control points that define the curve shape.
     • SEO Purpose: Improves the representation of complex curves in geographic data.
     • How to Use: Use Bezier curve parameters to accurately depict complex curves in mapping applications.
607. Circle Curve Parameters (GeostoreCurveConnectionProtoCircleParams)
     • Description: Provides parameters for defining circular arcs between two points.
     • SEO Purpose: Enhances the precision of circular geographical features.
     • How to Use: Utilize circle curve parameters to accurately represent circular arcs in geographic features.
608. Data Source Information (GeostoreDataSourceProto)
     • Description: Provides metadata about the data source used to construct the data repository, including provider name and bounds.
     • SEO Purpose: Ensures transparency and accuracy in data sourcing, improving trust and reliability.
     • How to Use: Include detailed data source information to enhance the credibility and traceability of geographic data.
609. DateTime (GeostoreDateTimeProto)
     • Description: Represents date and time information with a focus on civil time rather than physical time.
     • SEO Purpose: Ensures precise and standardized date and time representations in geographic data.
     • How to Use: Use this to accurately represent date and time in geographic features, ensuring consistency across applications.
610. Dimension Comparison (GeostoreDimensionComparisonProto)
     • Description: Contains a dimension value with a comparison operator for attributes like height, width, or length.
     • SEO Purpose: Enhances the precision of comparisons in geographic data.
     • How to Use: Implement dimension comparisons to accurately compare and analyze geographic or structural attributes.
611. Dimension Data (GeostoreDimensionProto)
     • Description: Represents a dimension with a numerical value and unit, applicable to height, width, or length.
     • SEO Purpose: Ensures accurate representation of physical dimensions in geographic data.
     • How to Use: Use dimension data to provide detailed and precise measurements of geographic or structural features.
612. Display Data (GeostoreDisplayDataProto)
     • Description: Contains data specific to rendering a point of interest (POI) on a map.
     • SEO Purpose: Enhances the visual representation and accuracy of POIs in mapping applications.
     • How to Use: Include display data to improve the rendering and visibility of POIs on maps.
613. Disputed Area Information (GeostoreDisputedAreaProto)
     • Description: Stores information about disputed areas, including administrative and claimant details.
     • SEO Purpose: Improves the accuracy and transparency of disputed geographic regions.
     • How to Use: Implement disputed area information to accurately represent and disclose disputed regions in geographic data.
614. Doodle Attributes (GeostoreDoodleProto)
     • Description: Holds doodle-specific attributes for features of type doodle.
     • SEO Purpose: Enhances the detail and relevance of doodle-related geographic features.
     • How to Use: Use doodle attributes to accurately represent and highlight doodle features on maps.
615. Duration-Based Rate (GeostoreDurationBasedRateProto)
     • Description: Specifies a cost based on the duration of utilization, applicable repeatedly over an interval.
     • SEO Purpose: Ensures accurate and flexible cost representations based on usage duration.
     • How to Use: Implement duration-based rates to accurately calculate and display costs based on utilization time.
616. Elevation Model (GeostoreElevationModelProto)
     • Description: Represents raster digital elevation model data for geographic features.
     • SEO Purpose: Enhances the accuracy of elevation data in geographic representations.
     • How to Use: Use elevation models to provide detailed and accurate elevation data in mapping applications.
617. Elevation Data (GeostoreElevationProto)
     • Description: Holds elevation and related data for geographic features.
     • SEO Purpose: Improves the precision and detail of elevation information in geographic data.
     • How to Use: Implement elevation data to accurately represent the vertical positioning of geographic features.
618. Entrance Attributes (GeostoreEntranceProto)
     • Description: Contains attributes specific to entrances of features.
     • SEO Purpose: Enhances the detail and accuracy of entrance-related data.
     • How to Use: Use entrance attributes to accurately represent and detail entrances in geographic data.
619. Entrance Reference (GeostoreEntranceReferenceProto)
     • Description: Models the relationship between a feature and its entrance or exit.
     • SEO Purpose: Improves the representation of entrances and exits in geographic data.
     • How to Use: Implement entrance references to clearly define and detail entrances and exits for geographic features.
620. Establishment Attributes (GeostoreEstablishmentProto)
     • Description: Holds establishment-specific attributes for features of type establishment.
     • SEO Purpose: Enhances the detail and accuracy of establishment-related data.
     • How to Use: Use establishment attributes to provide comprehensive information about establishments in geographic data.
621. Exceptional Hours (GeostoreExceptionalHoursProto)
     • Description: Stores information about non-regular hours, such as holiday hours, for businesses.
     • SEO Purpose: Ensures accurate representation of special business hours.
     • How to Use: Include exceptional hours to provide detailed and accurate business operating times, including holidays.
622. Existence Information (GeostoreExistenceProto)
     • Description: Contains data about the operational status, start and end dates, and closure reasons for features.
     • SEO Purpose: Enhances the accuracy and relevance of feature status information.
     • How to Use: Use existence information to accurately represent the operational status and history of geographic features.
623. Feature Field Metadata (GeostoreFeatureFieldMetadataProto)
     • Description: Provides provenance information for sub-fields of a feature.
     • SEO Purpose: Ensures transparency and traceability of data origins and changes.
     • How to Use: Implement feature field metadata to track and document the origins and modifications of feature data.
624. Feature History Metadata (GeostoreFeatureHistoryMetadataProto)
     • Description: Contains metadata related to the history of a given feature in the Geo repository.
     • SEO Purpose: Enhances the historical accuracy and context of geographic features.
     • How to Use: Use feature history metadata to provide detailed historical context and changes for geographic features.
625. Feature ID Forwardings (GeostoreFeatureIdForwardingsProto)
     • Description: Contains information about different types of feature ID forwardings, which can be attached to both live and removed features. This ensures that features can be tracked and referenced even if their IDs change over time.
     • SEO Purpose: Helps maintain the continuity and accuracy of feature data in SEO-related geographic databases.
     • How to Use: Utilize feature ID forwardings to ensure that all references to a geographic feature remain valid and up-to-date even if the feature ID changes.
626. Feature ID List (GeostoreFeatureIdListProto)
     • Description: A simple list of feature IDs. This allows for the aggregation and management of multiple feature identifiers in a structured way.
     • SEO Purpose: Ensures easy reference and organization of feature IDs for SEO purposes.
     • How to Use: Use this list to manage and organize multiple feature IDs within geographic data sets, facilitating efficient retrieval and referencing.
627. Feature ID (GeostoreFeatureIdProto)
     • Description: A globally unique identifier associated with each feature. It includes a 64-bit “cell id” and a 64-bit fingerprint of other identifying information.
     • SEO Purpose: Provides a unique identifier for each feature, ensuring accurate tracking and referencing across geographic data sets.
     • How to Use: Use the feature ID to uniquely identify and reference geographic features in data sets and ensure consistent identification across applications.
628. Feature Metadata (GeostoreFeatureMetadataProto)
     • Description: General metadata related to a given feature in the Geo repository. This includes various attributes that describe the feature in detail.
     • SEO Purpose: Enhances the richness and detail of feature data, making it more valuable for SEO and user engagement.
     • How to Use: Include comprehensive metadata for each feature to improve the detail and usability of geographic data.
629. Feature Property ID (GeostoreFeaturePropertyIdProto)
     • Description: Represents a “feature property” as an abstract construct, used to map specific properties to features.
     • SEO Purpose: Allows for detailed property mapping, enhancing the precision of geographic data representation.
     • How to Use: Use feature property IDs to map specific attributes to geographic features, ensuring detailed and accurate data representation.
630. Feature (GeostoreFeatureProto)
     • Description: Every entry in the GeoStore database is called a “feature,” represented as a discriminated union of various feature types, each with unique attributes and globally unique IDs.
     • SEO Purpose: Provides a comprehensive framework for representing diverse geographic features, enhancing data accuracy and richness.
     • How to Use: Implement features to represent and categorize different geographic entities accurately within the database.
631. Feature Replacement Info (GeostoreFeatureReplacementInfoProto)
     • Description: Metadata to track feature derivations and replacements, particularly useful for tracking changes in road segments.
     • SEO Purpose: Ensures accurate tracking of feature changes over time, maintaining data integrity and continuity.
     • How to Use: Use this metadata to document and track changes to features, ensuring accurate historical records and data continuity.
632. Field Metadata (GeostoreFieldMetadataProto)
     • Description: Internal field metadata used by upstream providers to the repository, not exposed to downstream consumers.
     • SEO Purpose: Enhances internal data management and tracking, ensuring data integrity and accuracy.
     • How to Use: Implement field metadata to manage and track internal data attributes, ensuring data accuracy and integrity.
633. Field with Rights (GeostoreFieldWithRightsProto)
     • Description: Represents rights for a feature property ID, ensuring detailed rights tracking and management.
     • SEO Purpose: Ensures proper management and tracking of data rights, enhancing data security and compliance.
     • How to Use: Use this proto to manage and track rights associated with feature properties, ensuring compliance and data security.
634. Flow Line (GeostoreFlowLineProto)
     • Description: Holds data related to a lane’s track, extendable for future data, ensuring detailed lane information.
     • SEO Purpose: Enhances the precision and detail of lane-related data, improving geographic data accuracy.
     • How to Use: Implement flow line data to accurately represent and track lane details, ensuring comprehensive geographic data.
635. Food Menu Item Option (GeostoreFoodMenuItemOptionProto)
     • Description: Represents options for a food menu item, such as different choices for a dish (e.g., chicken, beef, tofu).
     • SEO Purpose: Enhances the detail and usability of menu data, improving user engagement and satisfaction.
     • How to Use: Use this proto to provide detailed options for food menu items, ensuring comprehensive and user-friendly menu representations.
636. Food Menu Item Option Ingredient (GeostoreFoodMenuItemOptionProtoIngredient)
     • Description: Denotes ingredient information for a food dish, enhancing detail and transparency.
     • SEO Purpose: Improves the accuracy and detail of food-related data, enhancing user trust and engagement.
     • How to Use: Include detailed ingredient information for menu items to provide transparency and improve user trust.
637. Food Menu Item Option Portion Size (GeostoreFoodMenuItemOptionProtoPortionSize)
     • Description: Represents the serving portion size of a food dish, providing detailed portion information.
     • SEO Purpose: Enhances the detail and accuracy of menu data, improving user satisfaction and engagement.
     • How to Use: Use portion size information to provide clear and detailed descriptions of food servings, ensuring user satisfaction.
638. Food Menu Item (GeostoreFoodMenuItemProto)
     • Description: Represents a food menu item, including its name, price, and multiple names in different languages.
     • SEO Purpose: Provides detailed and multilingual descriptions of menu items, enhancing user engagement and accessibility.
     • How to Use: Implement this proto to provide comprehensive and detailed information about food menu items, ensuring a user-friendly and accessible menu.
639. GConcept Instance (GeostoreGConceptInstanceProto)
     • Description: Contains a unique identifier for a GConcept, a category in the Geo Ontology.
     • SEO Purpose: Ensures accurate categorization and identification of geographic concepts, enhancing data organization and usability.
     • How to Use: Use GConcept instances to accurately categorize and identify geographic concepts, improving data organization and usability.
640. Geometry Composition (GeostoreGeometryComposition)
     • Description: Encapsulates all features defining the geometry of a feature, including unions and subtractions of polygons.
     • SEO Purpose: Enhances the accuracy and detail of geometric representations, improving geographic data precision.
     • How to Use: Use geometry composition to accurately define and represent the geometry of geographic features.
641. Geometry Store Reference (GeostoreGeometryStoreReferenceProto)
     • Description: Contains a Geometry Store ID and, in some contexts, materialized geometry from the associated record.
     • SEO Purpose: Ensures accurate referencing and retrieval of geometric data, enhancing data precision.
     • How to Use: Use geometry store references to accurately reference and retrieve geometric data for features.
642. Geopolitical Geometry (GeostoreGeopoliticalGeometryProto)
     • Description: Represents unsimplified geopolitical polygons for different use cases.
     • SEO Purpose: Ensures accurate and detailed representation of geopolitical boundaries, enhancing data reliability.
     • How to Use: Implement geopolitical geometry to accurately represent and detail geopolitical boundaries in geographic data.
643. Geopolitical Information (GeostoreGeopoliticalProto)
     • Description: Stores geopolitical information about a feature, including different regional perspectives.
     • SEO Purpose: Enhances the detail and accuracy of geopolitical data, improving user trust and engagement.
     • How to Use: Use geopolitical information to provide comprehensive and accurate representations of geopolitical features.
644. Regional Polygon Adjustment (GeostoreGeopoliticalProtoRegionalPolygonAdjustmentProto)
     • Description: Contains raw polygon adjustments to apply to a feature’s base polygon for a specific region’s view.
     • SEO Purpose: Ensures accurate regional representations of geographic features, enhancing data precision.
     • How to Use: Use regional polygon adjustments to accurately reflect regional perspectives on geographic features.
645. Regional Polygon Composing Claims (GeostoreGeopoliticalProtoRegionalPolygonComposingClaimsProto)
     • Description: Contains the polygon composition recipe for a region’s view of a feature’s geometry based on disputed area claims.
     • SEO Purpose: Enhances the accuracy and detail of disputed area representations, improving data reliability.
     • How to Use: Implement regional polygon composing claims to accurately represent and document disputed area claims.
646. Grade Level (GeostoreGradeLevelProto)
     • Description: Represents the relative altitude of a segment at a particular point, in relation to other segments.
     • SEO Purpose: Enhances the accuracy of elevation data in geographic representations.
     • How to Use: Use grade level data to accurately represent the relative altitudes of segments, improving geographic data precision.
647. HTML Text (GeostoreHtmlTextProto)
     • Description: Represents HTML text associated with a feature, allowing for rich text formatting.
     • SEO Purpose: Enhances the presentation and readability of feature descriptions.
     • How to Use: Use HTML text to provide richly formatted descriptions of features, improving user engagement and readability.
648. Inferred Geometry (GeostoreInferredGeometryProto)
     • Description: Defines the geometry of a feature as the union or exclusion of the geometry of other features.
     • SEO Purpose: Ensures accurate and detailed geometric representations by inferring geometry from related features.
     • How to Use: Use inferred geometry to accurately define the shapes and boundaries of geographic features based on related data.
649. Internal Feature (GeostoreInternalFeatureProto)
     • Description: Represents fields for data that are more about other data within the feature than about the feature itself.
     • SEO Purpose: Enhances internal data management and tracking, ensuring data integrity and accuracy.
     • How to Use: Implement internal feature data to manage and track internal attributes and relationships within the feature data set.
650. Internal Field Metadata (GeostoreInternalFieldMetadataProto)
     • Description: Contains internal metadata about data fields, including whether data was generated automatically.
     • SEO Purpose: Enhances data transparency and management, ensuring the accuracy and integrity of data sources.
     • How to Use: Use internal field metadata to document and track the origins and generation methods of data fields, ensuring data integrity.
651. Internal Segment (GeostoreInternalSegmentProto)
     • Description: Internal-only proto used to express additional information about segments for communication between editing clients and the repository.
     • SEO Purpose: Ensures accurate and detailed internal communication and data management.
     • How to Use: Use internal segment data to communicate and manage detailed segment information within the data repository.
652. Lane Connection Reference (GeostoreInternalSegmentProtoLaneConnectionReference)
     • Description: Specifies a single outgoing lane connection, providing detailed lane connectivity information.
     • SEO Purpose: Enhances the detail and accuracy of lane connectivity data, improving navigation and mapping accuracy.
     • How to Use: Implement lane connection references to accurately represent and manage lane connectivity in geographic data.
653. Internal Source Summary (GeostoreInternalSourceSummaryProto)
     • Description: Contains information about the source of a piece of data, including the dataset and provider.
     • SEO Purpose: Enhances data transparency and traceability, ensuring the accuracy and reliability of data sources.
     • How to Use: Use internal source summary data to document and track the sources of data, ensuring transparency and reliability.
654. Intersection Group (GeostoreIntersectionGroupProto)
     • Description: Models a group of intersections that share common attributes or represent a logical intersection.
     • SEO Purpose: Ensures accurate and detailed representation of complex intersections, improving mapping and navigation.
     • How to Use: Use intersection groups to represent and manage complex intersections accurately, enhancing geographic data precision.
655. Intersection (GeostoreIntersectionProto)
     • Description: Represents a common endpoint of one or more segments in a transportation network, typically without a name.
     • SEO Purpose: Enhances the detail and accuracy of intersection data, improving mapping and navigation.
     • How to Use: Use intersection data to accurately represent and manage intersections in transportation networks.
656. Job Metadata (GeostoreJobMetadata)
     • Description: Contains metadata about a job, including duration, related categories, and unique identifiers.
     • SEO Purpose: Enhances the detail and accuracy of job-related data, improving user engagement and relevance.
     • How to Use: Use job metadata to provide detailed and comprehensive information about job types and durations.
657. Job Related Category (GeostoreJobRelatedCategory)
     • Description: Represents the category a user selected for a job type at the time of input.
     • SEO Purpose: Ensures accurate categorization and relevance of job-related data.
     • How to Use: Use job related categories to accurately categorize and manage job data, improving relevance and user engagement.
658. Knowledge Graph Reference (GeostoreKnowledgeGraphReferenceProto)
     • Description: Contains a reference to an entity in the KnowledgeGraph, providing detailed context and information.
     • SEO Purpose: Enhances the relevance and richness of data by linking to the KnowledgeGraph.
     • How to Use: Use KnowledgeGraph references to enrich geographic data with detailed contextual information.
659. Landmark Reference (GeostoreLandmarkReferenceProto)
     • Description: Represents the association between a segment and a landmark feature.
     • SEO Purpose: Enhances the accuracy and relevance of geographic data by linking segments to landmarks.
     • How to Use: Use landmark references to accurately associate geographic segments with nearby landmarks.
660. Lane Marker (GeostoreLaneMarkerProto)
     • Description: Contains attributes relevant to physical lane markers, enhancing lane detail and accuracy.
     • SEO Purpose: Improves the detail and precision of lane-related data, enhancing navigation and mapping.
     • How to Use: Use lane marker data to accurately represent and manage physical lane markers in geographic data.
661. Lane (GeostoreLaneProto)
     • Description: Describes an individual road lane, including driving, parking, and biking lanes.
     • SEO Purpose: Ensures detailed and accurate representation of different types of lanes in geographic data.
     • How to Use: Implement lane data to provide comprehensive and detailed information about road lanes, improving navigation and mapping.
662. Lane Connection (GeostoreLaneProtoLaneConnection)
     • Description: Specifies the connection between lanes, including bounding markers and flow lines.
     • SEO Purpose: Enhances the accuracy and detail of lane connectivity data, improving navigation and mapping.
     • How to Use: Use lane connection data to accurately represent and manage the connectivity between lanes.
663. Language Tagged Text (GeostoreLanguageTaggedTextProto)
     • Description: Represents a piece of text with an associated language, enhancing multilingual support.
     • SEO Purpose: Ensures accurate and accessible multilingual data representation.
     • How to Use: Use language tagged text to provide multilingual support for geographic features, improving accessibility and user engagement.
664. Level (GeostoreLevelProto)
     • Description: Represents a logical level, such as a floor, with specific naming conventions.
     • SEO Purpose: Enhances the accuracy and detail of multi-level geographic features.
     • How to Use: Use level data to accurately represent and manage different levels of geographic features, such as floors in a building.
665. Linear Stripe Pattern (GeostoreLinearStripePatternProto)
     • Description: Represents linear markers consisting of one or more parallel physical lines.
     • SEO Purpose: Ensures detailed and accurate representation of linear markers, enhancing geographic data precision.
     • How to Use: Use linear stripe patterns to accurately represent and manage linear markers in geographic data.
666. Locale Language (GeostoreLocaleLanguageProto)
     • Description: Describes the details of a single language within a locale.
     • SEO Purpose: Enhances the accuracy and relevance of multilingual data.
     • How to Use: Use locale language data to accurately represent and manage language preferences within geographic locales.
667. Locale (GeostoreLocaleProto)
     • Description: Describes the geographic extent of localization preferences, including language and formatting conventions.
     • SEO Purpose: Ensures accurate and relevant localization of geographic data.
     • How to Use: Use locale data to manage and represent localization preferences for different geographic regions, improving user experience.
668. Logical Border (GeostoreLogicalBorderProto)
     • Description: Represents a grouping of borders that share common attributes, such as regions they divide.
     • SEO Purpose: Enhances the accuracy and detail of border representations, improving geographic data reliability.
     • How to Use: Use logical borders to accurately represent and manage groups of borders, ensuring detailed and reliable geographic data.
669. Media Item (GeostoreMediaItemProto)
     • Description: Represents media items attached to elements of a price list, such as photos.
     • SEO Purpose: Enhances the richness and engagement of price list data with visual elements.
     • How to Use: Use media items to attach visual content to price list elements, improving user engagement and data richness.
670. Media Size (GeostoreMediaItemProtoMediaSize)
     • Description: Represents the width and height of an original photo in pixels.
     • SEO Purpose: Ensures accurate representation of media dimensions, enhancing visual data quality.
     • How to Use: Use media size data to accurately represent the dimensions of photos attached to geographic features.
671. Name (GeostoreNameProto)
     • Description: Represents the name of a feature, such as a street name or point of interest, with support for multiple languages.
     • SEO Purpose: Ensures accurate and multilingual representation of feature names, improving accessibility and relevance.
     • How to Use: Use name data to provide detailed and multilingual names for geographic features, enhancing accessibility and user engagement.
672. Ontology Raw GConcept Instance Container (GeostoreOntologyRawGConceptInstanceContainerProto)
     • Description: Contains all GConceptInstances associated with a feature, providing a comprehensive ontology context.
     • SEO Purpose: Enhances the accuracy and relevance of feature categorization and ontology mapping.
     • How to Use: Use this container to manage and represent all GConcept instances related to a feature, ensuring comprehensive ontology mapping.
673. Ontology Raw GConcept Instance (GeostoreOntologyRawGConceptInstanceProto)
     • Description: Contains all data required by both internal and external clients for a GConceptInstance.
     • SEO Purpose: Ensures accurate and detailed representation of geographic concepts within an ontology.
     • How to Use: Use raw GConcept instances to accurately represent and manage geographic concepts, enhancing data relevance and accuracy.
674. Opening Hours (GeostoreOpeningHoursProto)
     • Description: Represents opening hours, including regular weekly hours and exceptions.
     • SEO Purpose: Ensures accurate and detailed representation of business operating hours.
     • How to Use: Use opening hours data to provide comprehensive and accurate business operating times, improving user information and engagement.
675. Operations (GeostoreOperationsProto)
     • Description: Contains information about a feature’s operations, such as temporary closures.
     • SEO Purpose: Enhances the accuracy and detail of operational status data.
     • How to Use: Use operations data to accurately represent and manage the operational status of geographic features.
676. Override Border Status (GeostoreOverrideBorderStatusProto)
     • Description: Captures a border status override for specific country restrictions.
     • SEO Purpose: Ensures accurate and compliant representation of borders based on country-specific requirements.
     • How to Use: Use border status overrides to manage and enforce country-specific border display restrictions, ensuring compliance.
677. Painted Element Logical Color (GeostorePaintedElementLogicalColorProto)
     • Description: Represents the logical color of painted elements, based on legal definitions.
     • SEO Purpose: Ensures accurate and compliant representation of painted elements.
     • How to Use: Use logical color data to accurately represent and manage the colors of painted elements in geographic data.
678. Parking Allowance (GeostoreParkingAllowanceProto)
     • Description: Describes parking allowances for a feature, including conditions and costs.
     • SEO Purpose: Enhances the detail and accuracy of parking-related data.
     • How to Use: Use parking allowance data to provide comprehensive and detailed information about parking conditions and costs.
679. Parking (GeostoreParkingProto)
     • Description: Describes parking facilities provided by or available to a feature.
     • SEO Purpose: Ensures accurate and detailed representation of parking facilities, improving user information.
     • How to Use: Use parking data to accurately represent and manage parking facilities associated with geographic features.
680. Parking Restriction (GeostoreParkingRestrictionProto)
     • Description: Expresses parking restrictions on a road, including prohibited times.
     • SEO Purpose: Enhances the accuracy and detail of parking restriction data.
     • How to Use: Use parking restriction data to accurately represent and manage parking prohibitions on roads.
681. Peak (GeostorePeakProto)
     • Description: Holds related data for features of type TYPE_PEAK and TYPE_VOLCANO.
     • SEO Purpose: Ensures accurate and detailed representation of peak and volcano features.
     • How to Use: Use peak data to provide comprehensive and accurate information about geographic peaks and volcanoes.
682. Pedestrian Crossing (GeostorePedestrianCrossingProto)
     • Description: Represents pedestrian crossings, including bidirectional crossings.
     • SEO Purpose: Ensures accurate and detailed representation of pedestrian crossings, improving navigation and safety.
     • How to Use: Use pedestrian crossing data to accurately represent and manage pedestrian crossing points in geographic data.
683. Physical Line (GeostorePhysicalLineProto)
     • Description: Describes a single physical marker line, enhancing lane and road detail.
     • SEO Purpose: Ensures accurate and detailed representation of physical lines in geographic data.
     • How to Use: Use physical line data to accurately represent and manage physical markers on roads and lanes.
684. Point Curvature (GeostorePointCurvatureProto)
     • Description: Represents curvature values at points along a flowline, providing detailed curvature information.
     • SEO Purpose: Enhances the accuracy and detail of curvature data in geographic representations.
     • How to Use: Use point curvature data to accurately represent and manage curvature values along geographic flowlines.
685. Point (GeostorePointProto)
     • Description: Represents a geographic point with latitude and longitude, and optional metadata.
     • SEO Purpose: Ensures accurate and detailed representation of geographic points.
     • How to Use: Use point data to accurately represent and manage geographic points, enhancing data precision and usability.
686. Point with Height (GeostorePointWithHeightProto)
     • Description: Encodes latitude, longitude, and altitude information for a geographic point.
     • SEO Purpose: Enhances the detail and accuracy of three-dimensional geographic data.
     • How to Use: Use point with height data to accurately represent and manage geographic points with altitude information.
687. Political (GeostorePoliticalProto)
     • Description: Represents political features, storing political information from the feature’s point of view.
     • SEO Purpose: Ensures accurate and detailed representation of political boundaries and information.
     • How to Use: Use political data to accurately represent and manage political features and boundaries.
688. Polyline (GeostorePolyLineProto)
     • Description: Represents a sequence of vertices connected by geodesics, forming a polyline.
     • SEO Purpose: Ensures accurate and detailed representation of linear geographic features.
     • How to Use: Use polyline data to accurately represent and manage linear features in geographic data.
689. Polygon (GeostorePolygonProto)
     • Description: Represents a non-self-intersecting spherical polygon, consisting of one or more loops.
     • SEO Purpose: Enhances the accuracy and detail of polygonal geographic features.
     • How to Use: Use polygon data to accurately represent and manage polygonal features in geographic data.
690. Pose (GeostorePoseProto)
     • Description: Represents an object’s position and orientation in space, using latitude, longitude, and rotations.
     • SEO Purpose: Ensures accurate and detailed representation of object poses in geographic data.
     • How to Use: Use pose data to accurately represent and manage the spatial orientation of objects in geographic data.
691. Price Info Food Nutrition Facts (GeostorePriceInfoFoodNutritionFacts)
     • Description: Represents nutrition facts for a food dish, providing detailed nutritional information.
     • SEO Purpose: Enhances the accuracy and detail of food-related data, improving user trust and engagement.
     • How to Use: Use nutrition facts data to provide comprehensive and detailed information about the nutritional content of food dishes.
692. Price Info Food Nutrition Facts Calories Fact (GeostorePriceInfoFoodNutritionFactsCaloriesFact)
     • Description: Represents calorie information with an upper and lower bound range.
     • SEO Purpose: Ensures accurate and detailed representation of calorie information.
     • How to Use: Use calorie facts data to provide clear and detailed information about the caloric content of food dishes.
693. Price Info Food Nutrition Facts Nutrition Fact (GeostorePriceInfoFoodNutritionFactsNutritionFact)
     • Description: Represents nutrition information with an upper and lower bound range, including mass unit representation.
     • SEO Purpose: Enhances the detail and accuracy of nutritional information for food dishes.
     • How to Use: Use nutrition facts data to provide comprehensive and detailed information about the nutritional content of food dishes.
694. Price Info (GeostorePriceInfoProto)
     • Description: Represents the actual food menus and URLs providing price list information, including verified status.
     • SEO Purpose: Ensures accurate and comprehensive representation of menu and pricing information.
     • How to Use: Use price info data to provide detailed and verified pricing information for food and menu items.
695. Price Info Status (GeostorePriceInfoStatus)
     • Description: Encapsulates the verified status of price information, indicating whether listings are verified or unverified.
     • SEO Purpose: Enhances the accuracy and reliability of price information.
     • How to Use: Use price info status to indicate the verification status of price listings, ensuring data reliability and user trust.
696. Price List Name Info (GeostorePriceListNameInfoProto)
     • Description: Stores names, descriptions, and languages for price lists, ensuring multilingual support.
     • SEO Purpose: Ensures accurate and multilingual representation of price list information.
     • How to Use: Use price list name info to provide detailed and multilingual names and descriptions for price lists, improving accessibility and user engagement.
697. Price List (GeostorePriceListProto)
     • Description: Represents various types of price lists, including food menus, with support for multiple sections and items.
     • SEO Purpose: Enhances the accuracy and detail of pricing and menu information.
     • How to Use: Use price list data to provide comprehensive and detailed information about different types of price lists, ensuring user-friendly and accessible data.
698. Price List Section (GeostorePriceListSectionProto)
     • Description: Stores a section of a price list, representing a specific category or menu section.
     • SEO Purpose: Ensures detailed and organized representation of price list sections.
     • How to Use: Use price list section data to accurately represent and manage sections within price lists, improving data organization and user accessibility.
     • Price Range (GeostorePriceRangeProto)
       • Description: Represents the price range for attributes, such as products or services. It provides an indication of the minimum and maximum expected prices.
       • SEO Purpose: Helps in targeting the right audience by providing clear pricing information, which can improve click-through rates and conversions.
       • How to Use: Include structured data to specify the price range of your products or services. Ensure your pricing information is accurate and up-to-date to attract the right customers.
699. Property Value Status (GeostorePropertyValueStatusProto)
     • Description: Indicates the status of a property’s value, particularly when specific values are absent. It may suggest if a value is unknown or not applicable.
     • SEO Purpose: Helps search engines understand the completeness and reliability of property-related information, improving the accuracy of search results.
     • How to Use: Provide as much detail as possible about property values. If certain information is not available, clearly indicate this to avoid confusion.
700. Source Information (GeostoreProvenanceProto)
     • Description: Minimal information about the source from which data is derived, ensuring data provenance and reliability.
     • SEO Purpose: Enhances the credibility and trustworthiness of the data by providing clear source information.
     • How to Use: Always attribute your data sources. Include references or citations where applicable to enhance credibility.
701. Rank Details (GeostoreRankDetailsProto)
     • Description: Contains details on rank calculations, including available rank signals and the rank signal mixer used to compute the final rank.
     • SEO Purpose: Helps in understanding the factors influencing ranking, enabling better optimization of content.
     • How to Use: Focus on improving the rank signals identified within the details. Use this information to fine-tune your SEO strategies.
702. Rank Signal (GeostoreRankSignalProto)
     • Description: Represents a single rank signal, a floating point value estimating the Oyster Rank of the feature.
     • SEO Purpose: Provides insights into specific ranking factors that impact the overall ranking of a feature.
     • How to Use: Analyze and enhance the rank signals to improve your content’s visibility and ranking.
703. Raw Data (GeostoreRawDataProto)
     • Description: Represents arbitrary source data from a particular provider, attached to features using the source_info field.
     • SEO Purpose: Ensures that raw data from various sources is accurately represented and utilized in the ranking process.
     • How to Use: Integrate and manage raw data effectively. Ensure data consistency and accuracy across different sources.
704. Raw Metadata (GeostoreRawMetadataProto)
     • Description: Provides additional metadata for raw data, including the method of conflation, description, key, and label.
     • SEO Purpose: Enhances data interpretation and usability by providing detailed metadata.
     • How to Use: Use clear and comprehensive metadata descriptions. Ensure that conflation methods and keys are well-documented and easily interpretable.
705. Geographic Rectangle (GeostoreRectProto)
     • Description: Defines a latitude-longitude rectangle with specific boundaries, useful for geographic data representation.
     • SEO Purpose: Improves local SEO by accurately defining geographic boundaries for content or services.
     • How to Use: Use structured data to define geographic boundaries. Ensure that location-based content is accurately tagged and described.
706. Region-Specific Name (GeostoreRegionSpecificNameProto)
     • Description: Supports names of features in different regions and languages, allowing for accurate regional representation.
     • SEO Purpose: Enhances localization and international SEO by providing region-specific names and translations.
     • How to Use: Include multiple regional and language variations of feature names in your content. Use hreflang tags to indicate language and regional targeting.
707. Regulated Area (GeostoreRegulatedAreaProto)
     • Description: Represents information about regulated areas, usually defined by a polygonal boundary.
     • SEO Purpose: Helps in providing accurate and compliant information about regulated areas, improving trust and relevance.
     • How to Use: Clearly define and label regulated areas within your content. Ensure compliance with local regulations and guidelines.
708. Relation (GeostoreRelationProto)
     • Description: Indicates a geographic or logical relationship between features, such as groupings or associations.
     • SEO Purpose: Enhances the contextual relevance and interconnectedness of features, aiding search engines in understanding relationships.
     • How to Use: Use structured data to define relationships between features. Highlight logical groupings and associations to improve relevance.
709. Restriction Group (GeostoreRestrictionGroupProto)
     • Description: Represents common properties of a set of restrictions related to geographic segments.
     • SEO Purpose: Ensures clear communication of restrictions, aiding in compliance and user experience.
     • How to Use: Clearly define and communicate restrictions related to geographic segments. Use structured data to specify restriction details.
710. Restriction (GeostoreRestrictionProto)
     • Description: Defines conditions under which certain actions are restricted, such as traffic restrictions or access limitations.
     • SEO Purpose: Helps users understand restrictions and improves compliance with regulations.
     • How to Use: Use structured data to specify restriction conditions. Ensure that restrictions are clearly communicated and updated regularly.
711. Rights Status (GeostoreRightsStatusProto)
     • Description: Represents rights information for a feature, ensuring proper data usage and compliance.
     • SEO Purpose: Protects intellectual property rights and ensures legal compliance in data usage.
     • How to Use: Clearly define and communicate rights information. Ensure compliance with intellectual property laws and guidelines.
712. Road Conditional (GeostoreRoadConditionalProto)
     • Description: Defines conditions affecting road traversal information, such as weather or traffic conditions.
     • SEO Purpose: Enhances the accuracy of navigation and travel-related content by considering conditional factors.
     • How to Use: Include conditional road information in your content. Use structured data to specify conditions affecting road usage.
713. Road Monitor (GeostoreRoadMonitorProto)
     • Description: Represents devices monitoring road conditions, such as traffic violations or speed limits.
     • SEO Purpose: Improves safety and compliance by providing accurate information about road monitors.
     • How to Use: Include information about road monitors in your content. Ensure that monitoring data is accurate and up-to-date.
714. Road Sign Component (GeostoreRoadSignComponentProto)
     • Description: Details components of a road sign, such as text and position within the sign.
     • SEO Purpose: Enhances the accuracy and readability of road-related content.
     • How to Use: Use structured data to define road sign components. Ensure that sign details are clear and easily interpretable.
715. Road Sign (GeostoreRoadSignProto)
     • Description: Holds details of a road sign, including its components and positions.
     • SEO Purpose: Improves navigation and user experience by providing detailed road sign information.
     • How to Use: Include comprehensive road sign details in your content. Use structured data to specify sign components and positions.
716. Route Association (GeostoreRouteAssociationProto)
     • Description: Contains metadata about the association between a segment and a route.
     • SEO Purpose: Enhances the accuracy of route-related content by providing clear associations.
     • How to Use: Use structured data to define route associations. Ensure that route metadata is accurate and well-documented.
717. Route (GeostoreRouteProto)
     • Description: Represents a collection of segments forming a logical group, such as a road or highway.
     • SEO Purpose: Improves local SEO and navigation accuracy by clearly defining routes.
     • How to Use: Use structured data to specify route details. Ensure that route information is accurate and regularly updated.
718. School District (GeostoreSchoolDistrictProto)
     • Description: Holds specific attributes for school district features.
     • SEO Purpose: Enhances the relevance and accuracy of education-related content.
     • How to Use: Include detailed information about school districts in your content. Use structured data to specify district attributes.
719. Segment Path (GeostoreSegmentPathProto)
     • Description: Describes a path through a set of segments, used for various purposes such as navigation.
     • SEO Purpose: Improves the accuracy of navigation-related content by clearly defining segment paths.
     • How to Use: Use structured data to specify segment paths. Ensure that path information is clear and easily interpretable.
720. Segment (GeostoreSegmentProto)
     • Description: Represents a geographic segment, such as a road or path, with specific attributes.
     • SEO Purpose: Enhances the relevance and accuracy of geographic content by clearly defining segments.
     • How to Use: Include detailed segment information in your content. Use structured data to specify segment attributes.
721. Segment Ramp (GeostoreSegmentProtoRampProto)
     • Description: Encapsulates ramp-specific properties within a segment.
     • SEO Purpose: Improves the accuracy of navigation-related content by clearly defining ramp properties.
     • How to Use: Use structured data to specify ramp details. Ensure that ramp information is accurate and well-documented.
722. Service Area (GeostoreServiceAreaProto)
     • Description: Represents the geographic area served by an establishment.
     • SEO Purpose: Enhances local SEO by accurately defining service areas for businesses or services.
     • How to Use: Clearly define and label service areas within your content. Use structured data to specify service area boundaries.
723. Serviced Stop (GeostoreServicedStopProto)
     • Description: Defines an ordered reference to a line variant’s stop.
     • SEO Purpose: Improves the accuracy of transit-related content by clearly defining stops.
     • How to Use: Use structured data to specify serviced stops. Ensure that stop information is clear and easily interpretable.
724. Ski Boundary (GeostoreSkiBoundaryProto)
     • Description: Holds attributes for ski boundary features.
     • SEO Purpose: Enhances the relevance and accuracy of winter sports-related content.
     • How to Use: Include detailed information about ski boundaries in your content. Use structured data to specify boundary attributes.
725. Ski Lift (GeostoreSkiLiftProto)
     • Description: Holds attributes for ski lift features.
     • SEO Purpose: Improves the accuracy of winter sports-related content by providing detailed ski lift information.
     • How to Use: Use structured data to specify ski lift details. Ensure that lift information is accurate and well-documented.
726. Ski Trail (GeostoreSkiTrailProto)
     • Description: Holds attributes for ski trail features.
     • SEO Purpose: Enhances the relevance and accuracy of winter sports-related content by providing detailed trail information.
     • How to Use: Include comprehensive ski trail details in your content. Use structured data to specify trail attributes.
727. Slope (GeostoreSlopeProto)
     • Description: Represents the slope value of a segment, indicating elevation change relative to horizontal distance.
     • SEO Purpose: Enhances the accuracy of geographic and navigation-related content by providing slope information.
     • How to Use: Use structured data to specify slope values. Ensure that slope information is accurate and well-documented.
728. Social Reference (GeostoreSocialReferenceProto)
     • Description: Assigns a MapFacts GAIA ID to a feature, representing a virtual ID.
     • SEO Purpose: Improves data organization and retrieval by providing unique identifiers for features.
     • How to Use: Ensure that social references are clearly defined and accurately assigned within your content.
729. Source Info (GeostoreSourceInfoProto)
     • Description: Establishes data provenance by describing the source data used in building a feature.
     • SEO Purpose: Enhances the credibility and trustworthiness of the data by providing clear source information.
     • How to Use: Always attribute your data sources. Include references or citations where applicable to enhance credibility.
730. Source Trust (GeostoreSourceTrustProto)
     • Description: Provides trust-related information about the input source, based on historical evidence or status.
     • SEO Purpose: Helps in determining the reliability of the data by providing trust signals.
     • How to Use: Ensure that your data sources are reliable and trustworthy. Use this information to improve the credibility of your content.
731. Speed Limit (GeostoreSpeedLimitProto)
     • Description: Contains speed limit information, including the conditions under which it applies.
     • SEO Purpose: Enhances the accuracy of navigation-related content by providing speed limit details.
     • How to Use: Use structured data to specify speed limits. Ensure that speed limit information is clear and up-to-date.
732. Speed (GeostoreSpeedProto)
     • Description: Represents speed values and units.
     • SEO Purpose: Improves the accuracy of navigation and travel-related content by providing clear speed information.
     • How to Use: Include speed details in your content. Use structured data to specify speed values and units.
733. Stable Field Path (GeostoreStableFieldPathProto)
     • Description: Represents a way to traverse nested fields by referencing their token fields, starting from a known root message.
     • SEO Purpose: Helps in data organization and retrieval by providing a structured path for nested fields.
     • How to Use: Use this structured approach to define and retrieve nested data fields accurately.
734. Sweep (GeostoreSweepProto)
     • Description: Represents the 2D polygon connecting two segments at an intersection, used for real road width rendering.
     • SEO Purpose: Enhances the accuracy of geographic and navigation-related content by providing detailed sweep information.
     • How to Use: Include sweep details in your content. Use structured data to specify sweep polygons.
735. Telephone (GeostoreTelephoneProto)
     • Description: Represents telephone numbers and related information.
     • SEO Purpose: Improves contact information accuracy and accessibility by providing detailed telephone information.
     • How to Use: Use structured data to specify telephone numbers. Ensure that contact information is accurate and up-to-date.
736. Temporary Closure (GeostoreTemporaryClosureProto)
     • Description: Stores information related to the temporary closure of a feature, specifying start and end times.
     • SEO Purpose: Enhances the accuracy of event and status-related content by providing temporary closure details.
     • How to Use: Clearly define and communicate temporary closures. Use structured data to specify closure times and durations.
737. Text Affix (GeostoreTextAffixProto)
     • Description: Represents text affixed to the beginning and/or end of primary text, including the associated language.
     • SEO Purpose: Improves text accuracy and readability by providing clear affix details.
     • How to Use: Include text affixes in your content. Use structured data to specify affix details and associated languages.
738. Three-Dimensional Model (GeostoreThreeDimensionalModelProto)
     • Description: Represents a triangular mesh in indexed format, used for 3D models.
     • SEO Purpose: Enhances the accuracy and detail of 3D content by providing comprehensive model information.
     • How to Use: Include detailed 3D model information in your content. Use structured data to specify model attributes and indices.
739. Time-Based Rate (GeostoreTimeBasedRateProto)
     • Description: Defines a rate based on precise times of utilization, including restrictions on start and end times.
     • SEO Purpose: Improves the accuracy of rate-related content by providing detailed time-based rate information.
     • How to Use: Use structured data to specify time-based rates. Ensure that rate information is clear and accurate.
740. Time Component (GeostoreTimeComponentProto)
     • Description: Represents a time component as the intersection of time intervals.
     • SEO Purpose: Enhances the accuracy of time-related content by providing detailed time component information.
     • How to Use: Use structured data to specify time components. Ensure that time information is clear and easily interpretable.
741. Time Endpoint (GeostoreTimeEndpointProto)
     • Description: Specifies endpoints for time intervals with a directed graph representing time granularity.
     • SEO Purpose: Improves the accuracy of time-related content by providing clear time endpoint information.
     • How to Use: Use structured data to specify time endpoints. Ensure that time interval information is accurate and well-documented.
742. Time Interval (GeostoreTimeIntervalProto)
     • Description: Defines a range of times with specified begin and end points, including options for inversion.
     • SEO Purpose: Enhances the accuracy of time-related content by providing detailed time interval information.
     • How to Use: Use structured data to specify time intervals. Ensure that time range information is clear and accurate.
743. Time Schedule (GeostoreTimeScheduleProto)
     • Description: Represents a schedule as the union of time components.
     • SEO Purpose: Improves the accuracy of scheduling-related content by providing comprehensive schedule information.
     • How to Use: Use structured data to specify time schedules. Ensure that schedule information is clear and accurate.
744. Timezone (GeostoreTimezoneProto)
     • Description: Holds information about a feature’s related time zone.
     • SEO Purpose: Enhances the accuracy of time-related content by providing detailed time zone information.
     • How to Use: Use structured data to specify time zones. Ensure that time zone information is accurate and up-to-date.
745. Toll Cluster (GeostoreTollClusterProto)
     • Description: Contains information related to a toll cluster.
     • SEO Purpose: Enhances the accuracy of navigation-related content by providing detailed toll cluster information.
     • How to Use: Use structured data to specify toll clusters. Ensure that toll information is clear and accurate.
746. Toll Path (GeostoreTollPathProto)
     • Description: Describes the sequential travel across toll clusters, including conditions for fee payment.
     • SEO Purpose: Improves the accuracy of toll-related content by providing detailed toll path information.
     • How to Use: Use structured data to specify toll paths. Ensure that toll information is clear and up-to-date.
747. Indexed Toll Cluster (GeostoreTollPathProtoIndexedTollCluster)
     • Description: Represents a toll cluster and its position along a toll path.
     • SEO Purpose: Enhances the accuracy of toll-related content by providing detailed indexed toll cluster information.
     • How to Use: Use structured data to specify indexed toll clusters. Ensure that toll cluster positions are accurately documented.
748. Toll Cluster Sequence (GeostoreTollPathProtoTollClusterSequence)
     • Description: Represents the sequence of toll clusters in a toll path.
     • SEO Purpose: Improves the accuracy of toll-related content by providing detailed toll cluster sequence information.
     • How to Use: Use structured data to specify toll cluster sequences. Ensure that cluster sequences are clear and accurately documented.
749. Track (GeostoreTrackProto)
     • Description: Represents a track with instantaneous pose points along its path.
     • SEO Purpose: Enhances the accuracy of geographic content by providing detailed track information.
     • How to Use: Include detailed track information in your content. Use structured data to specify track poses and attributes.
750. Transit Line (GeostoreTransitLineProto)
     • Description: Represents a named set of transit trips with attributes true for all trips, such as name and website.
     • SEO Purpose: Improves the accuracy of transit-related content by providing detailed transit line information.
     • How to Use: Use structured data to specify transit lines. Ensure that transit line details are accurate and up-to-date.
751. Transit Line Variant (GeostoreTransitLineVariantProto)
     • Description: Represents a specific instantiation of a transit line, including stops and segments.
     • SEO Purpose: Enhances the relevance and accuracy of transit-related content by providing detailed line variant information.
     • How to Use: Use structured data to specify transit line variants. Ensure that variant information is clear and accurately documented.
752. Transit Station (GeostoreTransitStationProto)
     • Description: Contains information related to an individual transit station.
     • SEO Purpose: Improves the accuracy of transit-related content by providing detailed station information.
     • How to Use: Include comprehensive transit station details in your content. Use structured data to specify station attributes.
753. Transit Agency Association (GeostoreTransitStationProtoTransitAgencyAssociationProto)
     • Description: Represents the association between a station and the servicing agency.
     • SEO Purpose: Enhances the relevance and accuracy of transit-related content by providing detailed agency association information.
     • How to Use: Use structured data to specify agency associations. Ensure that agency information is clear and accurately documented.
754. Trust Signals (GeostoreTrustSignalsProto)
     • Description: Provides trust signals for a data source, based on historical evidence or status.
     • SEO Purpose: Helps determine the reliability and credibility of content by providing trust-related information.
     • How to Use: Ensure that your data sources are reliable. Use trust signals to enhance the credibility of your content.
755. Unlimited Speed (GeostoreUnlimitedSpeedProto)
     • Description: Represents an absence of speed limit, indicating unlimited speed.
     • SEO Purpose: Enhances the accuracy of navigation-related content by providing details about unlimited speed zones.
     • How to Use: Use structured data to specify areas with unlimited speed. Ensure that speed information is clear and up-to-date.
756. URL List (GeostoreUrlListProto)
     • Description: Holds a list of URLs, often translations of a single URL.
     • SEO Purpose: Improves the accessibility and relevance of content by providing multiple URLs for different languages or regions.
     • How to Use: Include comprehensive URL lists in your content. Use structured data to specify URLs and their translations.
757. URL (GeostoreUrlProto)
     • Description: Represents a web location for a feature, stored in repeated fields for multilingual purposes.
     • SEO Purpose: Enhances the accessibility and relevance of content by providing URLs for different languages or regions.
     • How to Use: Include multiple language-specific URLs in your content. Use structured data to specify URLs accurately.
758. User (GeostoreUserProto)
     • Description: Identifies a human user of Geo Data, primarily used to describe data sources.
     • SEO Purpose: Improves the credibility and trustworthiness of content by providing clear user information.
     • How to Use: Clearly define and communicate user information. Use structured data to specify user attributes.
759. Variable Speed (GeostoreVariableSpeedProto)
     • Description: Represents a speed limit that can change based on conditions such as road, traffic, and weather.
     • SEO Purpose: Enhances the accuracy of navigation-related content by providing details about variable speed zones.
     • How to Use: Use structured data to specify areas with variable speed limits. Ensure that speed information is clear and up-to-date.
760. Vehicle Attribute Filter (GeostoreVehicleAttributeFilterProto)
     • Description: Defines a set of vehicle attribute conditions used to filter vehicles based on certain criteria.
     • SEO Purpose: Improves the relevance of content related to vehicle attributes by providing clear filtering conditions.
     • How to Use: Use structured data to specify vehicle attribute filters. Ensure that filter conditions are clear and accurately documented.
761. Vertical Ordering (GeostoreVerticalOrderingProto)
     • Description: Represents the vertical ordering of a feature, such as levels within a building.
     • SEO Purpose: Enhances the accuracy of indoor mapping content by providing clear vertical ordering information.
     • How to Use: Use structured data to specify vertical ordering. Ensure that ordering information is clear and well-documented.
762. Weight Comparison (GeostoreWeightComparisonProto)
     • Description: This ranking factor represents a weight value that is tagged with a comparison operator. The comparison operator defines how the weight value should be evaluated in relation to other values.
     • SEO Purpose: Helps in determining the relative importance of certain attributes or elements by comparing their weights, influencing how they are ranked in search results.
     • How to Use: Assign appropriate weights to attributes or elements based on their importance to ensure they are accurately compared and ranked in search results. Regularly review and adjust these weights to reflect changes in relevance.
763. Weight (GeostoreWeightProto)
     • Description: This factor represents a numerical value and its corresponding unit, which can be used to quantify the importance or significance of an attribute.
     • SEO Purpose: Enables the precise measurement of the importance of various attributes, aiding in the accurate ranking of content.
     • How to Use: Assign numerical weights to important attributes and ensure the units of measurement are consistent. Use these weights to prioritize content and improve its ranking.
764. Anchor Label (GoodocAnchorLabel)
     • Description: An anchor label provides a reference address that can be attached to any element. It is used for linking elements logically within documents.
     • SEO Purpose: Facilitates internal linking and navigation within documents, improving user experience and search engine indexing.
     • How to Use: Use anchor labels to create logical links within documents, enhancing internal navigation and helping search engines understand the structure of your content.
765. Bounding Box (GoodocBoundingBox)
     • Description: This factor defines the bounding box for page structural elements such as pictures, paragraphs, and characters, specifying their position and dimensions.
     • SEO Purpose: Helps in accurately identifying and indexing visual elements on a page, improving the visual representation and searchability of content.
     • How to Use: Clearly define bounding boxes for all visual elements on your page. Ensure that the dimensions and positions are accurately specified to aid in proper indexing and display.
766. Box Partitions (GoodocBoxPartitions)
     • Description: Represents a partitioning of a bounding box into a sequence of sub-boxes, used to store boundaries within larger elements for space-saving purposes.
     • SEO Purpose: Enhances the precision and efficiency of content indexing by defining finer partitions within larger elements.
     • How to Use: Use box partitions to organize content within bounding boxes. This helps in detailed indexing and efficient space management.
767. Break Label (GoodocBreakLabel)
     • Description: This factor represents a label indicating a break in content, such as a page break or section break.
     • SEO Purpose: Helps in structuring content by marking breaks, improving readability and navigation within documents.
     • How to Use: Clearly label breaks in your content to delineate sections. This aids in better content organization and user experience.
768. Character Label (GoodocCharLabel)
     • Description: This label identifies the font used for characters within a document.
     • SEO Purpose: Ensures that font information is accurately indexed, aiding in the consistent display and readability of text.
     • How to Use: Specify font labels for all characters in your document. This helps in maintaining visual consistency and enhancing readability.
769. Document (GoodocDocument)
     • Description: Represents the top-level structure of an OCRed document, containing all elements and their relationships.
     • SEO Purpose: Provides a comprehensive representation of the document for indexing and retrieval, improving document searchability and structure.
     • How to Use: Ensure your OCRed documents are well-structured and all elements are accurately represented. This enhances the document’s searchability and usability.
770. Document Header (GoodocDocumentHeader)
     • Description: Contains metadata about the OCR engine used, including its ID, version, and associated fonts.
     • SEO Purpose: Provides detailed information about the OCR process, aiding in the verification and optimization of OCR accuracy.
     • How to Use: Include detailed metadata about the OCR engine and fonts used. This helps in verifying OCR accuracy and optimizing document processing.
771. Document Page (GoodocDocumentPage)
     • Description: Represents a single page within an OCRed document, including its dimensions, resolution, and various elements like text, images, and blocks.
     • SEO Purpose: Enhances the detailed indexing and retrieval of individual pages within documents, improving overall document searchability.
     • How to Use: Ensure each page of your OCRed document is accurately represented with detailed attributes. This aids in precise indexing and retrieval of page-specific content.
772. Document Page Block (GoodocDocumentPageBlock)
     • Description: Defines a block of content within a document page, such as paragraphs, images, or other elements, including their orientation and text confidence.
     • SEO Purpose: Improves the organization and indexing of content blocks within a page, aiding in better searchability and readability.
     • How to Use: Clearly define content blocks on each page. Specify orientation and confidence levels to enhance the indexing and retrieval of these blocks.
773. Merged Page Info (GoodocDocumentPageMergedPageInfo)
     • Description: Records information about text merged from other documents, providing details about the source and integration.
     • SEO Purpose: Ensures that merged content is accurately tracked and indexed, improving the consistency and reliability of document information.
     • How to Use: Maintain detailed records of merged page information. This helps in tracking content sources and ensuring consistency.
774. Font Size Stats (GoodocFontSizeStats)
     • Description: Provides statistics about font sizes used within a document, aggregated over a range of symbols.
     • SEO Purpose: Aids in the analysis of font usage, contributing to better design and readability of documents.
     • How to Use: Analyze font size statistics to optimize the design and readability of your documents. Ensure font sizes are consistent and suitable for the intended audience.
775. Label (GoodocLabel)
     • Description: Aggregates various optional characteristics of page elements, providing detailed metadata about these elements.
     • SEO Purpose: Enhances the metadata of page elements, aiding in more detailed indexing and retrieval.
     • How to Use: Include comprehensive labels for all page elements. This improves the richness of your metadata and aids in better search results.
776. Language Combination (GoodocLanguageCombinationLanguage)
     • Description: Represents a weighted language combination, indicating the languages used within a document and their relative weights.
     • SEO Purpose: Improves the indexing and searchability of multilingual documents by accurately representing language usage.
     • How to Use: Specify weighted language combinations for multilingual documents. This helps in accurate indexing and improves search results for multilingual content.
777. Language Label (GoodocLanguageLabel)
     • Description: Provides labels for languages used within a document, aiding in language identification and indexing.
     • SEO Purpose: Enhances the searchability of multilingual content by accurately labeling languages used.
     • How to Use: Include language labels for all multilingual content. This aids in language-specific indexing and retrieval.
778. Logical Entity (GoodocLogicalEntity)
     • Description: Represents a logical grouping of links within a document, used to define abstract entities such as tables of contents or sections.
     • SEO Purpose: Improves the organization and navigation of complex documents by defining logical entities.
     • How to Use: Use logical entities to group related links and content within your documents. This enhances organization and user navigation.
779. Logical Entity Link (GoodocLogicalEntityLink)
     • Description: Represents links within a logical entity, used to connect various elements logically within a document.
     • SEO Purpose: Facilitates internal linking and improves document navigation and organization.
     • How to Use: Include logical entity links to connect related content within your documents. This enhances internal linking and user navigation.
780. Ordinal (GoodocOrdinal)
     • Description: Represents a single ordinal component of a page number, encoding the numbering style and value.
     • SEO Purpose: Improves the indexing and retrieval of pages within documents by accurately representing page numbers.
     • How to Use: Use ordinals to clearly define page numbers and their styles. This aids in better indexing and navigation within documents.
781. Orientation Label (GoodocOrientationLabel)
     • Description: Provides details about the orientation and reading order of content blocks within a document.
     • SEO Purpose: Enhances the readability and organization of content by accurately representing orientation and reading order.
     • How to Use: Include orientation labels for all content blocks. This helps in maintaining the correct reading order and improving user experience.
782. Overrides (GoodocOverrides)
     • Description: Specifies structure overrides to apply certain kinds of renderings, used to enforce specific document structures.
     • SEO Purpose: Improves document rendering and presentation by applying specific structure overrides.
     • How to Use: Use overrides to enforce specific structures and renderings. This ensures consistent presentation and enhances readability.
783. Overrides Style (GoodocOverridesStyle)
     • Description: Provides extra CSS styles to apply to document elements, enhancing their appearance and presentation.
     • SEO Purpose: Enhances the visual presentation of documents by applying additional styles.
     • How to Use: Use override styles to enhance the appearance of document elements. Ensure styles are consistent with the overall design.
784. Paragraph (GoodocParagraph)
     • Description: Represents a paragraph of text within an OCRed document, including its content and structure.
     • SEO Purpose: Improves the organization and readability of text content by accurately representing paragraphs.
     • How to Use: Clearly define paragraphs within your OCRed documents. This aids in better text organization and readability.
785. Paragraph Dropped Cap (GoodocParagraphDroppedCap)
     • Description: Provides information about the dropped capital letter in a paragraph, enhancing its visual appeal.
     • SEO Purpose: Enhances the visual appeal and readability of text by accurately representing dropped capital letters.
     • How to Use: Include dropped cap information for paragraphs where applicable. This improves visual appeal and readability.
786. Paragraph Route (GoodocParagraphRoute)
     • Description: Defines the route of a paragraph, including its start and end points, weight, and words.
     • SEO Purpose: Enhances the readability and navigation of paragraphs by accurately representing their routes.
     • How to Use: Use paragraph routes to define the structure and flow of text. This aids in better readability and navigation.
787. Rotated Bounding Box (GoodocRotatedBoundingBox)
     • Description: Represents a bounding box with an angle of rotation, used for non-axis-aligned elements.
     • SEO Purpose: Enhances the accuracy of visual element representation by accommodating rotated elements.
     • How to Use: Use rotated bounding boxes for non-axis-aligned elements. This improves the accuracy of visual representation and indexing.
788. Route Point (GoodocRoutePoint)
     • Description: Represents a point in a route, including its index and word number.
     • SEO Purpose: Enhances the accuracy and detail of route representation within documents.
     • How to Use: Define route points accurately within your documents. This aids in better navigation and organization.
789. Semantic Label (GoodocSemanticLabel)
     • Description: Identifies a logical part of the page content, such as blocks, paragraphs, or words, providing semantic context.
     • SEO Purpose: Improves the indexing and retrieval of content by providing semantic labels for different parts of the page.
     • How to Use: Include semantic labels for all significant content parts. This enhances semantic search and content retrieval.
790. Semantic Label Column Details (GoodocSemanticLabelColumnDetails)
     • Description: Provides details for columns, if the appearance is a column.
     • SEO Purpose: Enhances the indexing and representation of columnar content by providing detailed column information.
     • How to Use: Include column details for content appearing in columns. This improves indexing and presentation.
791. Semantic Label Content Link (GoodocSemanticLabelContentLink)
     • Description: Represents a label for content that links to another piece of content, such as citations or URLs.
     • SEO Purpose: Facilitates internal and external linking, enhancing navigation and relevance of content.
     • How to Use: Use content links to connect related pieces of content. This improves navigation and content relevance.
792. Semantic Label Citation Target (GoodocSemanticLabelContentLinkCitationTarget)
     • Description: Represents labels for scholarly citations, linking to cited content.
     • SEO Purpose: Enhances the credibility and academic relevance of content by providing accurate citation links.
     • How to Use: Include citation targets for all scholarly content. This improves credibility and academic relevance.
793. Semantic Label In-Volume Target (GoodocSemanticLabelContentLinkInVolumeTarget)
     • Description: Represents labels for content linking within the same volume, such as captions or footnotes.
     • SEO Purpose: Improves internal navigation and coherence within a document volume by providing accurate in-volume links.
     • How to Use: Use in-volume targets for internal links like captions and footnotes. This enhances navigation and coherence.
794. Semantic Label Edit Correction Candidate (GoodocSemanticLabelEditCorrectionCandidate)
     • Description: Stores multiple candidates for edit corrections, aiding in manual correction processes.
     • SEO Purpose: Facilitates accurate and efficient content editing by providing multiple correction candidates.
     • How to Use: Include edit correction candidates for content requiring manual correction. This improves editing efficiency and accuracy.
795. Semantic Label Snippet Filter (GoodocSemanticLabelSnippetFilter)
     • Description: Records the output of snippet filters, indicating the conditions met by the content.
     • SEO Purpose: Enhances snippet generation and indexing by recording filter conditions.
     • How to Use: Use snippet filters to generate and record snippet conditions. This improves snippet quality and indexing.
796. Semantic Label Table Cell Details (GoodocSemanticLabelTableCellDetails)
     • Description: Provides details for table cells if the appearance is a table cell.
     • SEO Purpose: Enhances the indexing and representation of table content by providing detailed cell information.
     • How to Use: Include detailed cell information for table content. This improves indexing and presentation.
797. Semantic Label Table Details (GoodocSemanticLabelTableDetails)
     • Description: Provides details for tables, including structure and content.
     • SEO Purpose: Enhances the indexing and representation of table content by providing detailed table information.
     • How to Use: Include detailed table information for all table content. This improves indexing and presentation.
798. Summary Stats (GoodocSummaryStats)
     • Description: Provides statistics for a range of elements within a document, such as font size and line spacing.
     • SEO Purpose: Aids in the analysis and optimization of document formatting and readability.
     • How to Use: Analyze summary stats to optimize document formatting. Ensure elements are consistent and suitable for the intended audience.
799. Symbol (GoodocSymbol)
     • Description: Represents a single symbol within a document, including its properties and attributes.
     • SEO Purpose: Enhances the indexing and representation of individual symbols within content.
     • How to Use: Clearly define symbols within your documents. This improves indexing and content representation.
800. Symbol Variant (GoodocSymbolSymbolVariant)
     • Description: Provides variants of a symbol, including different codes and confidence levels.
     • SEO Purpose: Improves the accuracy of symbol recognition and representation by including variants.
     • How to Use: Include symbol variants to enhance recognition accuracy. This aids in better indexing and content representation.
801. Word (GoodocWord)
     • Description: Represents a word within a document, including its properties and attributes.
     • SEO Purpose: Enhances the indexing and retrieval of text content by accurately representing words.
     • How to Use: Clearly define words within your documents. This improves text indexing and retrieval.
802. Word Alternates (GoodocWordAlternates)
     • Description: Provides alternate OCR words for correction, aiding in improving OCR accuracy.
     • SEO Purpose: Enhances OCR accuracy and reliability by providing alternate word options.
     • How to Use: Include alternate words for OCR corrections. This improves the accuracy and reliability of OCR content.
803. Billing Configuration (GoogleApiServiceconsumermanagementV1BillingConfig)
     • Description: Describes the billing configuration for a new tenant project, detailing how billing is managed and processed.
     • SEO Purpose: Ensures accurate billing and financial management for services, improving trust and transparency.
     • How to Use: Clearly define billing configurations for all projects. This ensures accurate financial management and improves transparency.
804. Policy Binding (GoogleApiServiceconsumermanagementV1PolicyBinding)
     • Description: Translates to IAM policy bindings, specifying the policies and permissions assigned to users.
     • SEO Purpose: Enhances security and compliance by accurately defining policy bindings and permissions.
     • How to Use: Define clear policy bindings and permissions for all users. This improves security and ensures compliance.
805. Audio Output Configuration (GoogleAssistantAccessoryV1AudioOutConfig)
     • Description: Specifies the desired format for audio output messages, ensuring optimal audio quality and compatibility.
     • SEO Purpose: Enhances user experience by ensuring high-quality and compatible audio output.
     • How to Use: Configure audio output settings to ensure optimal quality and compatibility. This improves user experience.
806. Device Configuration (GoogleAssistantAccessoryV1DeviceConfig)
     • Description: Identifies the device to the Assistant, including required fields and identifiers.
     • SEO Purpose: Ensures accurate device identification and configuration for optimal performance.
     • How to Use: Provide accurate device configuration details. This ensures proper identification and optimal performance.
807. Device State (GoogleAssistantAccessoryV1DeviceState)
     • Description: Contains information about the state of the device, including timers, alarms, and other relevant data.
     • SEO Purpose: Enhances device functionality and user experience by providing accurate state information.
     • How to Use: Maintain accurate device state information. This improves functionality and user experience.
808. Installed Apps State (GoogleAssistantAccessoryV1DeviceStateInstalledAppsState)
     • Description: Represents the state of apps currently installed on the device.
     • SEO Purpose: Improves app management and functionality by providing accurate installed apps information.
     • How to Use: Maintain accurate information about installed apps. This aids in app management and enhances functionality.
809. Response Configuration (GoogleAssistantAccessoryV1ResponseConfig)
     • Description: Configures the response format for the Assistant, ensuring compatibility and optimal user experience.
     • SEO Purpose: Enhances response accuracy and user satisfaction by providing configurable response formats.
     • How to Use: Configure response settings to ensure compatibility and optimal user experience. This improves response accuracy.
810. Screen Output Configuration (GoogleAssistantAccessoryV1ScreenOutConfig)
     • Description: Specifies the desired format for screen output responses, ensuring optimal visual presentation.
     • SEO Purpose: Enhances user experience by providing high-quality and compatible screen output.
     • How to Use: Configure screen output settings to ensure optimal visual presentation. This improves user experience.
811. Screen Out Dimensions (GoogleAssistantAccessoryV1ScreenOutConfigDimensions)
     • Description: Provides physical and logical characteristics about the device, such as screen size and DPI.
     • SEO Purpose: Ensures accurate screen output by providing detailed device characteristics.
     • How to Use: Include detailed dimensions for screen output. This ensures accurate and optimal visual presentation.
812. Alarm (GoogleAssistantEmbeddedV1Alarm)
     • Description: Represents a clock that rings at a specified time, including recurrence and snoozing options.
     • SEO Purpose: Enhances user experience by providing reliable and customizable alarm settings.
     • How to Use: Configure alarm settings accurately. This ensures reliable and customizable alarms for users.
813. Alarm Recurrence (GoogleAssistantEmbeddedV1AlarmRecurrence)
     • Description: Describes the dates when an alarm should recur, ensuring regular and consistent reminders.
     • SEO Purpose: Improves user experience by providing consistent and reliable alarm recurrences.
     • How to Use: Set up accurate alarm recurrences. This ensures regular and consistent reminders for users.
814. On-Device Alarms (GoogleAssistantEmbeddedV1Alarms)
     • Description: Contains information about on-device alarms, including settings and statuses.
     • SEO Purpose: Enhances device functionality by providing accurate alarm information.
     • How to Use: Maintain accurate information about on-device alarms. This improves functionality and user experience.
815. Device Model Capabilities Override (GoogleAssistantEmbeddedV1DeviceModelCapabilitiesOverride)
     • Description: Represents device model capabilities that can be overridden by the client.
     • SEO Purpose: Enhances device customization and performance by allowing capability overrides.
     • How to Use: Utilize capability overrides to customize device performance. This ensures optimal functionality.
816. Fitness Activities (GoogleAssistantEmbeddedV1FitnessActivities)
     • Description: Contains information about on-device fitness activities, including types and states.
     • SEO Purpose: Enhances user health and fitness tracking by providing accurate activity information.
     • How to Use: Maintain accurate information about fitness activities. This improves health tracking and user experience.
817. Fitness Activity (GoogleAssistantEmbeddedV1FitnessActivity)
     • Description: Describes a specific fitness activity, including its state and associated data.
     • SEO Purpose: Improves health and fitness tracking by providing detailed activity information.
     • How to Use: Include detailed information about each fitness activity. This enhances tracking accuracy and user experience.
818. Surface Identity (GoogleAssistantEmbeddedV1SurfaceIdentity)
     • Description: Identifies the device that sent a request, ensuring accurate tracking and response.
     • SEO Purpose: Enhances device interaction by providing accurate surface identity information.
     • How to Use: Maintain accurate surface identity information. This ensures accurate tracking and responses.
819. Timer (GoogleAssistantEmbeddedV1Timer)
     • Description: Represents a countdown timer that rings when it reaches zero, including settings and statuses.
     • SEO Purpose: Enhances user experience by providing reliable and customizable timer settings.
     • How to Use: Configure timer settings accurately. This ensures reliable and customizable timers for users.
820. On-Device Timers (GoogleAssistantEmbeddedV1Timers)
     • Description: Contains information about on-device timers, including settings and statuses.
     • SEO Purpose: Improves device functionality by providing accurate timer information.
     • How to Use: Maintain accurate information about on-device timers. This enhances functionality and user experience.
821. Access Control Action (GoogleCloudContentwarehouseV1AccessControlAction)
     • Description: Represents the action responsible for managing access control lists, ensuring secure document access.
     • SEO Purpose: Enhances security and compliance by providing accurate access control actions.
     • How to Use: Define and manage access control actions accurately. This ensures secure and compliant document access.
822. Action (GoogleCloudContentwarehouseV1Action)
     • Description: Represents an action triggered by the Rule Engine when a rule is true, ensuring proper rule execution.
     • SEO Purpose: Enhances functionality and automation by providing accurate action definitions.
     • How to Use: Define actions for all relevant rules. This ensures proper rule execution and improves functionality.
823. Action Executor Output (GoogleCloudContentwarehouseV1ActionExecutorOutput)
     • Description: Represents the output of an action executor, providing results of action execution.
     • SEO Purpose: Enhances transparency and analysis by providing detailed action execution results.
     • How to Use: Include detailed outputs for action executors. This improves transparency and aids in analysis.
824. Action Output (GoogleCloudContentwarehouseV1ActionOutput)
     • Description: Represents the result of executing an action, including details and statuses.
     • SEO Purpose: Enhances transparency and analysis by providing detailed action execution results.
     • How to Use: Include detailed outputs for all actions. This improves transparency and aids in analysis.
825. Add to Folder Action (GoogleCloudContentwarehouseV1AddToFolderAction)
     • Description: Represents the action responsible for adding a document to a folder.
     • SEO Purpose: Enhances document organization and management by providing accurate folder actions.
     • How to Use: Define actions for adding documents to folders. This improves organization and management.
826. Cloud AI Document Option (GoogleCloudContentwarehouseV1CloudAIDocumentOption)
     • Description: Request option for processing Cloud AI documents in the content warehouse.
     • SEO Purpose: Enhances document processing by providing accurate Cloud AI options.
     • How to Use: Specify Cloud AI document options accurately. This ensures optimal processing and functionality.
827. Create Document Link Request (GoogleCloudContentwarehouseV1CreateDocumentLinkRequest)
     • Description: Request message for creating document links, including source and target documents.
     • SEO Purpose: Enhances document linking and organization by providing accurate link creation requests.
     • How to Use: Submit accurate requests for creating document links. This improves linking and organization.
828. Create Document Metadata (GoogleCloudContentwarehouseV1CreateDocumentMetadata)
     • Description: Metadata object for creating a document, providing additional details and statuses.
     • SEO Purpose: Enhances document creation by providing detailed metadata.
     • How to Use: Include detailed metadata for document creation. This improves accuracy and functionality.
829. Create Document Request (GoogleCloudContentwarehouseV1CreateDocumentRequest)
     • Description: Request message for creating a document, including necessary fields and configurations.
     • SEO Purpose: Enhances document creation by providing accurate request details.
     • How to Use: Submit accurate requests for creating documents. This ensures proper creation and functionality.
830. Create Document Response (GoogleCloudContentwarehouseV1CreateDocumentResponse)
     • Description: Response message for document creation, providing details and statuses.
     • SEO Purpose: Enhances document creation by providing detailed responses.
     • How to Use: Review responses for document creation. This ensures accuracy and aids in troubleshooting.
831. Custom Weights Metadata (GoogleCloudContentwarehouseV1CustomWeightsMetadata)
     • Description: Supports custom weighting across document schemas, aiding in accurate ranking and retrieval.
     • SEO Purpose: Enhances document ranking by providing custom weights.
     • How to Use: Define custom weights for document schemas. This improves ranking and retrieval accuracy.
832. Data Update Action (GoogleCloudContentwarehouseV1DataUpdateAction)
     • Description: Represents the action responsible for updating document properties.
     • SEO Purpose: Enhances document management by providing accurate update actions.
     • How to Use: Define actions for updating document properties. This ensures accurate and efficient updates.
833. Data Validation Action (GoogleCloudContentwarehouseV1DataValidationAction)
     • Description: Represents the action responsible for validating document data.
     • SEO Purpose: Ensures data accuracy and integrity by providing validation actions.
     • How to Use: Define actions for validating document data. This ensures accuracy and integrity.
834. DateTime Array (GoogleCloudContentwarehouseV1DateTimeArray)
     • Description: Represents an array of DateTime values, used for storing multiple timestamps.
     • SEO Purpose: Enhances document timestamping by providing accurate DateTime arrays.
     • How to Use: Include DateTime arrays for multiple timestamps. This improves accuracy and organization.
835. DateTime Type Options (GoogleCloudContentwarehouseV1DateTimeTypeOptions)
     • Description: Configurations for a DateTime property, specifying formats and options.
     • SEO Purpose: Enhances document timestamping by providing accurate DateTime configurations.
     • How to Use: Define DateTime type options accurately. This ensures proper formatting and functionality.
836. Delete Document Action (GoogleCloudContentwarehouseV1DeleteDocumentAction)
     • Description: Represents the action responsible for deleting a document.
     • SEO Purpose: Enhances document management by providing accurate delete actions.
     • How to Use: Define actions for deleting documents. This ensures proper management and deletion.
837. Delete Document Link Request (GoogleCloudContentwarehouseV1DeleteDocumentLinkRequest)
     • Description: Request message for deleting document links.
     • SEO Purpose: Enhances document linking and management by providing accurate delete link requests.
     • How to Use: Submit accurate requests for deleting document links. This ensures proper linking and management.
838. Delete Document Request (GoogleCloudContentwarehouseV1DeleteDocumentRequest)
     • Description: Request message for deleting a document, including necessary fields and configurations.
     • SEO Purpose: Enhances document management by providing accurate delete requests.
     • How to Use: Submit accurate requests for deleting documents. This ensures proper management and deletion.
839. Document (GoogleCloudContentwarehouseV1Document)
     • Description: Defines the structure for a content warehouse document, including its properties and metadata.
     • SEO Purpose: Enhances document management and retrieval by providing accurate document structures.
     • How to Use: Define the structure for all documents accurately. This improves management and retrieval.
840. Document Link (GoogleCloudContentwarehouseV1DocumentLink)
     • Description: Represents a link between source and target documents, aiding in document organization.
     • SEO Purpose: Enhances document linking and organization by providing accurate link definitions.
     • How to Use: Define links between related documents. This improves organization and navigation.
841. Document Query (GoogleCloudContentwarehouseV1DocumentQuery)
     • Description: Represents a query for searching documents, including various filters and options.
     • SEO Purpose: Enhances document retrieval by providing accurate query definitions.
     • How to Use: Define queries accurately for searching documents. This improves retrieval and relevance.
842. Document Reference (GoogleCloudContentwarehouseV1DocumentReference)
     • Description: Provides references to documents, aiding in document linking and retrieval.
     • SEO Purpose: Enhances document linking and retrieval by providing accurate references.
     • How to Use: Include accurate references for all related documents. This improves linking and retrieval.
843. Document Schema (GoogleCloudContentwarehouseV1DocumentSchema)
     • Description: Defines the schema for a document, specifying its structure and properties.
     • SEO Purpose: Enhances document organization and retrieval by providing accurate schema definitions.
     • How to Use: Define schemas for all document types. This ensures proper organization and retrieval.
844. Enum Array (GoogleCloudContentwarehouseV1EnumArray)
     • Description: Represents an array of enum values, used for categorizing document properties.
     • SEO Purpose: Enhances document categorization by providing accurate enum arrays.
     • How to Use: Include enum arrays for categorizing properties. This improves organization and retrieval.
845. Enum Type Options (GoogleCloudContentwarehouseV1EnumTypeOptions)
     • Description: Configurations for an enum property, specifying formats and options.
     • SEO Purpose: Enhances document categorization by providing accurate enum configurations.
     • How to Use: Define enum type options accurately. This ensures proper categorization and functionality.
846. Enum Value (GoogleCloudContentwarehouseV1EnumValue)
     • Description: Represents the string value of an enum field, used for categorizing document properties.
     • SEO Purpose: Enhances document categorization by providing accurate enum values.
     • How to Use: Include enum values for categorizing properties. This improves organization and retrieval.
847. Export to CDW Pipeline (GoogleCloudContentwarehouseV1ExportToCdwPipeline)
     • Description: Configures the export of documents from the content warehouse to CDW pipeline.
     • SEO Purpose: Enhances document management by providing accurate export configurations.
     • How to Use: Configure export settings accurately for CDW pipeline. This ensures proper document management.
848. Fetch ACL Request (GoogleCloudContentwarehouseV1FetchAclRequest)
     • Description: Request message for fetching access control lists.
     • SEO Purpose: Enhances security and compliance by providing accurate ACL fetch requests.
     • How to Use: Submit accurate requests for fetching ACLs. This ensures proper security and compliance.
849. Fetch ACL Response (GoogleCloudContentwarehouseV1FetchAclResponse)
     • Description: Response message for fetching access control lists, providing details and statuses.
     • SEO Purpose: Enhances security and compliance by providing detailed ACL fetch responses.
     • How to Use: Review responses for ACL fetch requests. This ensures accuracy and aids in troubleshooting.
850. File Type Filter (GoogleCloudContentwarehouseV1FileTypeFilter)
     • Description: Filters for specific types of documents returned, such as files or folders.
     • SEO Purpose: Enhances document retrieval by providing accurate file type filters.
     • How to Use: Define filters for specific file types. This improves retrieval and relevance.
851. Float Array (GoogleCloudContentwarehouseV1FloatArray)
     • Description: Represents an array of float values, used for storing multiple numerical properties.
     • SEO Purpose: Enhances document property management by providing accurate float arrays.
     • How to Use: Include float arrays for multiple numerical properties. This improves accuracy and organization.
852. Float Type Options (GoogleCloudContentwarehouseV1FloatTypeOptions)
     • Description: Configurations for a float property, specifying formats and options.
     • SEO Purpose: Enhances document property management by providing accurate float configurations.
     • How to Use: Define float type options accurately. This ensures proper formatting and functionality.
853. GCS Ingest Pipeline (GoogleCloudContentwarehouseV1GcsIngestPipeline)
     • Description: Configures the ingestion of documents from Google Cloud Storage to the content warehouse.
     • SEO Purpose: Enhances document ingestion by providing accurate GCS pipeline configurations.
     • How to Use: Configure GCS ingestion settings accurately. This ensures proper document ingestion and management.
854. GCS Ingest with DocAI Processors Pipeline (GoogleCloudContentwarehouseV1GcsIngestWithDocAiProcessorsPipeline)
     • Description: Configures the ingestion of documents from Google Cloud Storage with DocAI processors.
     • SEO Purpose: Enhances document processing by providing accurate DocAI pipeline configurations.
     • How to Use: Configure DocAI ingestion settings accurately. This ensures proper document processing and management.
855. Get Document Request (GoogleCloudContentwarehouseV1GetDocumentRequest)
     • Description: Request message for retrieving a document from the content warehouse.
     • SEO Purpose: Enhances document retrieval by providing accurate get document requests.
     • How to Use: Submit accurate requests for retrieving documents. This ensures proper retrieval and management.
856. Histogram Query (GoogleCloudContentwarehouseV1HistogramQuery)
     • Description: Represents a query for generating histograms, including various filters and options.
     • SEO Purpose: Enhances data analysis by providing accurate histogram queries.
     • How to Use: Define queries accurately for generating histograms. This improves analysis and insights.
857. Histogram Query Property Name Filter (GoogleCloudContentwarehouseV1HistogramQueryPropertyNameFilter)
     • Description: Filters property names for histogram queries, specifying document schemas and properties.
     • SEO Purpose: Enhances data analysis by providing accurate property name filters.
     • How to Use: Define property name filters for histogram queries. This improves analysis and insights.
858. Histogram Query Result (GoogleCloudContentwarehouseV1HistogramQueryResult)
     • Description: Provides results of histogram queries, including detailed data and insights.
     • SEO Purpose: Enhances data analysis by providing accurate histogram query results.
     • How to Use: Review and analyze histogram query results. This improves insights and decision-making.
859. Ingest Pipeline Config (GoogleCloudContentwarehouseV1IngestPipelineConfig)
     • Description: Configures the ingestion pipeline, specifying formats and options for document ingestion.
     • SEO Purpose: Enhances document ingestion by providing accurate pipeline configurations.
     • How to Use: Configure ingestion pipeline settings accurately. This ensures proper document ingestion and management.
860. Initialize Project Request (GoogleCloudContentwarehouseV1InitializeProjectRequest)
     • Description: Request message for initializing a project, including necessary configurations.
     • SEO Purpose: Enhances project setup by providing accurate initialization requests.
     • How to Use: Submit accurate requests for initializing projects. This ensures proper setup and functionality.
861. Initialize Project Response (GoogleCloudContentwarehouseV1InitializeProjectResponse) – Description: Response message for project initialization, providing details and statuses. – SEO Purpose: Enhances project setup by providing detailed initialization responses. – How to Use: Review responses for project initialization. This ensures accuracy and aids in troubleshooting.
862. Integer Array (GoogleCloudContentwarehouseV1IntegerArray) – Description: Represents an array of integer values, used for storing multiple numerical properties. – SEO Purpose: Enhances document property management by providing accurate integer arrays. – How to Use: Include integer arrays for multiple numerical properties. This improves accuracy and organization.
863. Integer Type Options (GoogleCloudContentwarehouseV1IntegerTypeOptions) – Description: Configurations for an integer property, specifying formats and options. – SEO Purpose: Enhances document property management by providing accurate integer configurations. – How to Use: Define integer type options accurately. This ensures proper formatting and functionality.
864. Invalid Rule (GoogleCloudContentwarehouseV1InvalidRule) – Description: Represents a rule that failed validation checks, providing details for troubleshooting. – SEO Purpose: Enhances rule management by providing accurate invalid rule details. – How to Use: Review invalid rules and troubleshoot issues. This ensures proper rule management and functionality.
865. List Document Schemas Response (GoogleCloudContentwarehouseV1ListDocumentSchemasResponse) – Description: Response message for listing document schemas, providing details and statuses. – SEO Purpose: Enhances document schema management by providing accurate listing responses. – How to Use: Review responses for document schema listings. This ensures proper management and organization.
866. List Linked Sources Request (GoogleCloudContentwarehouseV1ListLinkedSourcesRequest) – Description: Request message for listing linked sources, including necessary configurations. – SEO Purpose: Enhances document linking by providing accurate listing requests. – How to Use: Submit accurate requests for listing linked sources. This improves linking and organization.
867. List Linked Sources Response (GoogleCloudContentwarehouseV1ListLinkedSourcesResponse) – Description: Response message for listing linked sources, providing details and statuses. – SEO Purpose: Enhances document linking by providing accurate listing responses. – How to Use: Review responses for linked source listings. This ensures proper linking and organization.
868. List Linked Targets Request (GoogleCloudContentwarehouseV1ListLinkedTargetsRequest) – Description: Request message for listing linked targets, including necessary configurations. – SEO Purpose: Enhances document linking by providing accurate listing requests. – How to Use: Submit accurate requests for listing linked targets. This improves linking and organization.
869. List Linked Targets Response (GoogleCloudContentwarehouseV1ListLinkedTargetsResponse) – Description: Response message for listing linked targets, providing details and statuses. – SEO Purpose: Enhances document linking by providing accurate listing responses. – How to Use: Review responses for linked target listings. This ensures proper linking and organization.
870. List Rule Sets Response (GoogleCloudContentwarehouseV1ListRuleSetsResponse) – Description: Response message for listing rule sets, providing details and statuses. – SEO Purpose: Enhances rule management by providing accurate listing responses. – How to Use: Review responses for rule set listings. This ensures proper management and organization.
871. List Synonym Sets Response (GoogleCloudContentwarehouseV1ListSynonymSetsResponse) – Description: Response message for listing synonym sets, providing details and statuses. – SEO Purpose: Enhances synonym management by providing accurate listing responses. – How to Use: Review responses for synonym set listings. This ensures proper management and organization.
872. Lock Document Request (GoogleCloudContentwarehouseV1LockDocumentRequest) – Description: Request message for locking a document, ensuring secure and exclusive access. – SEO Purpose: Enhances document security by providing accurate lock requests. – How to Use: Submit accurate requests for locking documents. This ensures secure and exclusive access.
873. Map Property (GoogleCloudContentwarehouseV1MapProperty) – Description: Represents a structured map of key-value pairs, used for storing dynamic properties. – SEO Purpose: Enhances document property management by providing accurate map properties. – How to Use: Include map properties for dynamic key-value pairs. This improves organization and retrieval.
874. Map Type Options (GoogleCloudContentwarehouseV1MapTypeOptions) – Description: Configurations for a map property, specifying formats and options. – SEO Purpose: Enhances document property management by providing accurate map configurations. – How to Use: Define map type options accurately. This ensures proper formatting and functionality.
875. Merge Fields Options (GoogleCloudContentwarehouseV1MergeFieldsOptions) – Description: Options for merging updated fields, ensuring accurate and consistent updates. – SEO Purpose: Enhances document updates by providing accurate merge options. – How to Use: Define merge field options accurately. This ensures consistent and accurate updates.
876. Process with DocAI Pipeline (GoogleCloudContentwarehouseV1ProcessWithDocAiPipeline) – Description: Configures the processing of documents with DocAI processors, enhancing document analysis. – SEO Purpose: Enhances document processing by providing accurate DocAI pipeline configurations. – How to Use: Configure DocAI processing settings accurately. This ensures optimal analysis and functionality.
877. Processor Info (GoogleCloudContentwarehouseV1ProcessorInfo) – Description: Provides information about the DocAI processor, including configurations and statuses. – SEO Purpose: Enhances document processing by providing accurate processor information. – How to Use: Include detailed processor information. This improves processing accuracy and functionality.
878. Project Status (GoogleCloudContentwarehouseV1ProjectStatus) – Description: Represents the status of a project, including state, database type, and access control mode. – SEO Purpose: Enhances project management by providing accurate status information. – How to Use: Maintain accurate project status information. This improves management and decision-making.
879. Property (GoogleCloudContentwarehouseV1Property) – Description: Represents a property of a document, including its value and attributes. – SEO Purpose: Enhances document property management by providing accurate property definitions. – How to Use: Define properties accurately for all documents. This improves management and retrieval.
880. Property Array (GoogleCloudContentwarehouseV1PropertyArray) – Description: Represents an array of properties, used for storing multiple document attributes. – SEO Purpose: Enhances document property management by providing accurate property arrays. – How to Use: Include property arrays for multiple attributes. This improves organization and retrieval.
881. Property Definition (GoogleCloudContentwarehouseV1PropertyDefinition) – Description: Defines the metadata for a schema property, specifying its structure and options. – SEO Purpose: Enhances document schema management by providing accurate property definitions. – How to Use: Define property definitions for all schema properties. This ensures proper organization and retrieval.
882. Property Definition Schema Source (GoogleCloudContentwarehouseV1PropertyDefinitionSchemaSource) – Description: Provides schema source information for a property definition, ensuring accurate sourcing. – SEO Purpose: Enhances document schema management by providing accurate schema source information. – How to Use: Include schema source information for all property definitions. This improves accuracy and management.
883. Property Filter (GoogleCloudContentwarehouseV1PropertyFilter) – Description: Represents a filter for properties, specifying conditions and criteria for document retrieval. – SEO Purpose: Enhances document retrieval by providing accurate property filters. – How to Use: Define filters for specific properties. This improves retrieval and relevance.
884. Property Type Options (GoogleCloudContentwarehouseV1PropertyTypeOptions) – Description: Configurations for a nested structured data property, specifying formats and options. – SEO Purpose: Enhances document property management by providing accurate type options. – How to Use: Define property type options accurately. This ensures proper formatting and functionality.
885. Publish Action (GoogleCloudContentwarehouseV1PublishAction) – Description: Represents the action responsible for publishing messages to a Pub/Sub topic. – SEO Purpose: Enhances document management by providing accurate publish actions. – How to Use: Define actions for publishing messages. This ensures proper communication and management.
886. QA Result (GoogleCloudContentwarehouseV1QAResult) – Description: Provides additional result information for the question-answering feature. – SEO Purpose: Enhances document retrieval by providing accurate QA results. – How to Use: Include detailed QA results for question-answering features. This improves retrieval and relevance.
887. QA Result Highlight (GoogleCloudContentwarehouseV1QAResultHighlight) – Description: Represents a highlighted text span in the search text snippet, indicating relevant sections. – SEO Purpose: Enhances document readability and relevance by providing accurate highlights. – How to Use: Include highlights for relevant text spans. This improves readability and relevance.
888. Remove from Folder Action (GoogleCloudContentwarehouseV1RemoveFromFolderAction) – Description: Represents the action responsible for removing a document from a specific folder. – SEO Purpose: Enhances document organization and management by providing accurate remove actions. – How to Use: Define actions for removing documents from folders. This improves organization and management.
889. Request Metadata (GoogleCloudContentwarehouseV1RequestMetadata) – Description: Provides meta information used to improve the performance of the service. – SEO Purpose: Enhances service performance by providing accurate request metadata. – How to Use: Include detailed request metadata. This improves performance and functionality.
890. Response Metadata (GoogleCloudContentwarehouseV1ResponseMetadata) – Description: Provides additional information returned to the client, such as debugging information. – SEO Purpose: Enhances transparency and troubleshooting by providing accurate response metadata. – How to Use: Include detailed response metadata. This improves transparency and aids in troubleshooting.
891. Rule (GoogleCloudContentwarehouseV1Rule) – Description: Represents a rule for a content warehouse trigger, specifying conditions and actions. – SEO Purpose: Enhances rule management by providing accurate rule definitions. – How to Use: Define rules for all relevant triggers. This ensures proper management and functionality.
892. Rule Actions Pair (GoogleCloudContentwarehouseV1RuleActionsPair) – Description: Represents a rule and the outputs of associated actions, ensuring proper rule execution. – SEO Purpose: Enhances rule management by providing accurate rule-action pairs. – How to Use: Define rule-action pairs accurately. This ensures proper rule execution and functionality.
893. Rule Engine Output (GoogleCloudContentwarehouseV1RuleEngineOutput) – Description: Records the output of the Rule Engine, including rule evaluation and action results. – SEO Purpose: Enhances rule management by providing accurate engine outputs. – How to Use: Include detailed outputs for the Rule Engine. This improves evaluation and functionality.
894. Rule Evaluator Output (GoogleCloudContentwarehouseV1RuleEvaluatorOutput) – Description: Represents the output of the Rule Evaluator, providing results of rule evaluations. – SEO Purpose: Enhances rule management by providing accurate evaluator outputs. – How to Use: Include detailed outputs for rule evaluations. This improves management and decision-making.
895. Rule Set (GoogleCloudContentwarehouseV1RuleSet) – Description: Represents a set of rules from a single customer, ensuring proper rule organization. – SEO Purpose: Enhances rule management by providing accurate rule sets. – How to Use: Organize rules into sets accurately. This improves management and organization.
896. Run Pipeline Metadata (GoogleCloudContentwarehouseV1RunPipelineMetadata) – Description: Metadata message for the RunPipeline method, providing details and statuses. – SEO Purpose: Enhances pipeline management by providing accurate metadata. – How to Use: Include detailed metadata for pipeline runs. This improves management and troubleshooting.
897. Run Pipeline Metadata Export to CDW Pipeline (GoogleCloudContentwarehouseV1RunPipelineMetadataExportToCdwPipelineMetadata) – Description: Metadata message for the Export-to-CDW pipeline, providing details and statuses. – SEO Purpose: Enhances pipeline management by providing accurate metadata for CDW exports. – How to Use: Include detailed metadata for CDW exports. This improves management and troubleshooting.
898. Run Pipeline Metadata GCS Ingest Pipeline (GoogleCloudContentwarehouseV1RunPipelineMetadataGcsIngestPipelineMetadata) – Description: Metadata message for the GCS Ingest pipeline, providing details and statuses. – SEO Purpose: Enhances pipeline management by providing accurate metadata for GCS ingests. – How to Use: Include detailed metadata for GCS ingests. This improves management and troubleshooting.
899. Run Pipeline Metadata Individual Document Status (GoogleCloudContentwarehouseV1RunPipelineMetadataIndividualDocumentStatus) – Description: Represents the status of processing an individual document, providing details and results. – SEO Purpose: Enhances document processing by providing accurate status information. – How to Use: Include detailed status information for individual documents. This improves processing and troubleshooting.
900. Run Pipeline Metadata Process with DocAI Pipeline (GoogleCloudContentwarehouseV1RunPipelineMetadataProcessWithDocAiPipelineMetadata) – Description: Metadata message for the Process-with-DocAI pipeline, providing details and statuses. – SEO Purpose: Enhances pipeline management by providing accurate metadata for DocAI processing. – How to Use: Include detailed metadata for DocAI processing. This improves management and troubleshooting.
901. Run Pipeline Request (GoogleCloudContentwarehouseV1RunPipelineRequest) – Description: Request message for running a pipeline, including necessary configurations. – SEO Purpose: Enhances pipeline management by providing accurate run requests. – How to Use: Submit accurate requests for running pipelines. This ensures proper management and functionality.
902. Search Documents Request (GoogleCloudContentwarehouseV1SearchDocumentsRequest) – Description: Request message for searching documents, including various filters and options. – SEO Purpose: Enhances document retrieval by providing accurate search requests. – How to Use: Define search requests accurately. This ensures proper retrieval and relevance.
903. Search Documents Response (GoogleCloudContentwarehouseV1SearchDocumentsResponse) – Description: Response message for searching documents, providing details and results. – SEO Purpose: Enhances document retrieval by providing accurate search responses. – How to Use: Review search responses. This improves retrieval and aids in decision-making.
904. Search Documents Response Matching Document (GoogleCloudContentwarehouseV1SearchDocumentsResponseMatchingDocument) – Description: Represents a matching document in the search response, including metadata. – SEO Purpose: Enhances document retrieval by providing detailed matching document information. – How to Use: Review matching documents in search responses. This improves retrieval and relevance.
905. Set ACL Request (GoogleCloudContentwarehouseV1SetAclRequest) – Description: Request message for setting access control lists, ensuring secure document access. – SEO Purpose: Enhances security and compliance by providing accurate ACL requests. – How to Use: Submit accurate requests for setting ACLs. This ensures secure and compliant access.
906. Set ACL Response (GoogleCloudContentwarehouseV1SetAclResponse) – Description: Response message for setting access control lists, providing details and statuses. – SEO Purpose: Enhances security and compliance by providing detailed ACL responses. – How to Use: Review responses for ACL requests. This ensures accuracy and aids in troubleshooting.
907. Synonym Set (GoogleCloudContentwarehouseV1SynonymSet) – Description: Represents a list of synonyms for a given context, aiding in semantic search and relevance. – SEO Purpose: Enhances semantic search and relevance by providing accurate synonym sets. – How to Use: Define synonym sets for relevant contexts. This improves search relevance and user experience.
908. Synonym Set Synonym (GoogleCloudContentwarehouseV1SynonymSetSynonym) – Description: Represents a list of words given by the customer, where all words are synonyms of each other. – SEO Purpose: Enhances semantic search and relevance by providing accurate synonym lists. – How to Use: Include synonym lists for relevant contexts. This improves search relevance and user experience.
909. Text Array (GoogleCloudContentwarehouseV1TextArray) – Description: Represents an array of string/text values, used for storing multiple text properties. – SEO Purpose: Enhances document property management by providing accurate text arrays. – How to Use: Include text arrays for multiple text properties. This improves organization and retrieval.
910. Text Type Options (GoogleCloudContentwarehouseV1TextTypeOptions) – Description: Configurations for a text property, specifying formats and options. – SEO Purpose: Enhances document property management by providing accurate text configurations. – How to Use: Define text type options accurately. This ensures proper formatting and functionality.
911. Time Filter (GoogleCloudContentwarehouseV1TimeFilter) – Description: Filters documents based on create or update timestamps. – SEO Purpose: Enhances document retrieval by providing accurate time filters. – How to Use: Define time filters for document retrieval. This improves relevance and accuracy.
912. Timestamp Array (GoogleCloudContentwarehouseV1TimestampArray) – Description: Represents an array of timestamp values, used for storing multiple time properties. – SEO Purpose: Enhances document property management by providing accurate timestamp arrays. – How to Use: Include timestamp arrays for multiple time properties. This improves organization and retrieval.
913. Timestamp Type Options (GoogleCloudContentwarehouseV1TimestampTypeOptions) – Description: Configurations for a timestamp property, specifying formats and options. – SEO Purpose: Enhances document property management by providing accurate timestamp configurations. – How to Use: Define timestamp type options accurately. This ensures proper formatting and functionality.
914. Timestamp Value (GoogleCloudContentwarehouseV1TimestampValue) – Description: Represents a timestamp value type, used for storing specific time properties. – SEO Purpose: Enhances document property management by providing accurate timestamp values. – How to Use: Include timestamp values for specific time properties. This improves organization and retrieval.
915. Update Document Metadata (GoogleCloudContentwarehouseV1UpdateDocumentMetadata) – Description: Metadata object for updating a document, providing additional details and statuses. – SEO Purpose: Enhances document updates by providing detailed metadata. – How to Use: Include detailed metadata for document updates. This improves accuracy and functionality.
916. Update Document Request (GoogleCloudContentwarehouseV1UpdateDocumentRequest) – Description: Request message for updating a document, including necessary fields and configurations. – SEO Purpose: Enhances document updates by providing accurate request details. – How to Use: Submit accurate requests for updating documents. This ensures proper updates and functionality.
917. Update Document Response (GoogleCloudContentwarehouseV1UpdateDocumentResponse) – Description: Response message for document updates, providing details and statuses. – SEO Purpose: Enhances document updates by providing detailed responses. – How to Use: Review responses for document updates. This ensures accuracy and aids in troubleshooting.
918. Update Document Schema Request (GoogleCloudContentwarehouseV1UpdateDocumentSchemaRequest) – Description: Request message for updating a document schema, including necessary configurations. – SEO Purpose: Enhances document schema management by providing accurate update requests. – How to Use: Submit accurate requests for updating document schemas. This ensures proper management and organization.
919. Update Options (GoogleCloudContentwarehouseV1UpdateOptions) – Description: Options for updating documents, specifying formats and criteria. – SEO Purpose: Enhances document updates by providing accurate update options. – How to Use: Define update options accurately. This ensures proper formatting and functionality.
920. Update Rule Set Request (GoogleCloudContentwarehouseV1UpdateRuleSetRequest) – Description: Request message for updating a rule set, including necessary configurations. – SEO Purpose: Enhances rule management by providing accurate update requests. – How to Use: Submit accurate requests for updating rule sets. This ensures proper management and organization.
921. User Information (GoogleCloudContentwarehouseV1UserInfo) – Description: Provides information about the user, including details and attributes. – SEO Purpose: Enhances user management by providing accurate user information. – How to Use: Include detailed user information. This improves management and personalization.
922. Value (GoogleCloudContentwarehouseV1Value) – Description: Represents a dynamically typed value that can be a float, integer, string, or datetime. – SEO Purpose: Enhances document property management by providing accurate value representations. – How to Use: Include values for relevant properties. This improves accuracy and functionality.
923. Weighted Schema Property (GoogleCloudContentwarehouseV1WeightedSchemaProperty) – Description: Specifies the schema property name for custom weighting. – SEO Purpose: Enhances document ranking by providing accurate weighted properties. – How to Use: Define weighted schema properties accurately. This improves ranking and retrieval.
924. Create Document Metadata (GoogleCloudContentwarehouseV1beta1CreateDocumentMetadata) – Description: Metadata object for creating a document, providing additional details and statuses. – SEO Purpose: Enhances document creation by providing detailed metadata. – How to Use: Include detailed metadata for document creation. This improves accuracy and functionality.
925. Initialize Project Response (GoogleCloudContentwarehouseV1beta1InitializeProjectResponse) – Description: Response message for project initialization, providing details and statuses. – SEO Purpose: Enhances project setup by providing detailed initialization responses. – How to Use: Review responses for project initialization. This ensures accuracy and aids in troubleshooting.
926. Update Document Metadata (GoogleCloudContentwarehouseV1beta1UpdateDocumentMetadata) – Description: Metadata object for updating a document, providing additional details and statuses. – SEO Purpose: Enhances document updates by providing detailed metadata. – How to Use: Include detailed metadata for document updates. This improves accuracy and functionality.
927. Barcode (GoogleCloudDocumentaiV1Barcode) – Description: Encodes the detailed information of a barcode, including type and value. – SEO Purpose: Enhances document indexing and retrieval by providing accurate barcode information. – How to Use: Include detailed barcode information. This improves indexing and retrieval.
928. Bounding Poly (GoogleCloudDocumentaiV1BoundingPoly) – Description: Represents a bounding polygon for detected image annotations, specifying its coordinates. – SEO Purpose: Enhances visual element representation by providing accurate bounding polygons. – How to Use: Define bounding polygons for all image annotations. This improves accuracy and indexing.
929. Document (GoogleCloudDocumentaiV1Document) – Description: Represents the canonical document resource, providing insights and collaboration capabilities. – SEO Purpose: Enhances document management and collaboration by providing a comprehensive document representation. – How to Use: Ensure documents are well-structured and provide collaboration capabilities. This improves management and insights.
930. Document Entity (GoogleCloudDocumentaiV1DocumentEntity) – Description: Represents an entity within a document, such as a person, organization, or location. – SEO Purpose: Enhances document indexing and retrieval by providing accurate entity representations. – How to Use: Include detailed entity information. This improves indexing and retrieval.
931. Document Entity Normalized Value (GoogleCloudDocumentaiV1DocumentEntityNormalizedValue) – Description: Provides a parsed and normalized value for an entity, ensuring accurate representation. – SEO Purpose: Enhances entity indexing and retrieval by providing normalized values. – How to Use: Include normalized values for entities. This improves accuracy and retrieval.
932. Document Entity Relation (GoogleCloudDocumentaiV1DocumentEntityRelation) – Description: Represents relationships between entities within a document, specifying their connections. – SEO Purpose: Enhances document indexing and retrieval by providing accurate entity relationships. – How to Use: Define relationships between entities. This improves indexing and retrieval.
933. Document Page (GoogleCloudDocumentaiV1DocumentPage) – Description: Represents a single page within a document, including its elements and layout. – SEO Purpose: Enhances document indexing and retrieval by providing accurate page representations. – How to Use: Include detailed information for each page. This improves indexing and retrieval.
934. Document Page Anchor (GoogleCloudDocumentaiV1DocumentPageAnchor) – Description: References the visual context of an entity within a document, specifying its location. – SEO Purpose: Enhances document navigation and indexing by providing accurate page anchors. – How to Use: Define page anchors for relevant entities. This improves navigation and indexing.
935. Document Page Anchor Page Reference (GoogleCloudDocumentaiV1DocumentPageAnchorPageRef) – Description: Represents a weak reference to a page element within a document. – SEO Purpose: Enhances document navigation and indexing by providing accurate page references. – How to Use: Include page references for relevant elements. This improves navigation and indexing.
936. Document Page Block (GoogleCloudDocumentaiV1DocumentPageBlock) – Description: Represents a block of content within a document page, including its layout and properties. – SEO Purpose: Enhances document organization and indexing by providing accurate block representations. – How to Use: Define blocks for all content within pages. This improves organization and indexing.
937. Document Page Detected Barcode (GoogleCloudDocumentaiV1DocumentPageDetectedBarcode) – Description: Represents a detected barcode within a document page, including its properties. – SEO Purpose: Enhances document indexing and retrieval by providing accurate barcode detections. – How to Use: Include detected barcodes for relevant pages. This improves indexing and retrieval.
938. Document Page Detected Language (GoogleCloudDocumentaiV1DocumentPageDetectedLanguage) – Description: Represents the detected language for a structural component within a document page. – SEO Purpose: Enhances document indexing and retrieval by providing accurate language detections. – How to Use: Include detected languages for all structural components. This improves indexing and retrieval.
939. Document Page Dimension (GoogleCloudDocumentaiV1DocumentPageDimension) – Description: Represents the dimensions of a document page, specifying its width and height. – SEO Purpose: Enhances document representation by providing accurate page dimensions. – How to Use: Define dimensions for all document pages. This improves representation and indexing.
940. Document Page Form Field (GoogleCloudDocumentaiV1DocumentPageFormField) – Description: Represents a form field detected on a document page, including its properties and values. – SEO Purpose: Enhances document indexing and retrieval by providing accurate form field representations. – How to Use: Include form fields for relevant pages. This improves indexing and retrieval.
941. Document Page Image (GoogleCloudDocumentaiV1DocumentPageImage) – Description: Represents the rendered image contents of a document page. – SEO Purpose: Enhances document representation by providing accurate image contents. – How to Use: Include image contents for all relevant pages. This improves representation and indexing.
942. Document Page Image Quality Scores (GoogleCloudDocumentaiV1DocumentPageImageQualityScores) – Description: Represents image quality scores for a document page, specifying defects and quality metrics. – SEO Purpose: Enhances document representation by providing accurate image quality scores. – How to Use: Include quality scores for all relevant pages. This improves representation and analysis.
943. Document Page Image Quality Scores Detected Defect (GoogleCloudDocumentaiV1DocumentPageImageQualityScoresDetectedDefect) – Description: Represents detected defects in the image quality of a document page. – SEO Purpose: Enhances document representation by providing accurate defect detections. – How to Use: Include detected defects for relevant pages. This improves representation and analysis.
944. Document Page Layout (GoogleCloudDocumentaiV1DocumentPageLayout) – Description: Represents the layout of a document page, including its visual elements. – SEO Purpose: Enhances document representation by providing accurate layout information. – How to Use: Define layouts for all document pages. This improves representation and indexing.
945. Document Page Line (GoogleCloudDocumentaiV1DocumentPageLine) – Description: Represents a line of text within a document page, including its properties and layout. – SEO Purpose: Enhances document representation by providing accurate line representations. – How to Use: Include lines for all text within pages. This improves representation and indexing.
946. Document Page Matrix (GoogleCloudDocumentaiV1DocumentPageMatrix) – Description: Represents a transformation matrix for a document page, compatible with OpenCV format. – SEO Purpose: Enhances document representation by providing accurate transformation matrices. – How to Use: Include transformation matrices for relevant pages. This improves representation and indexing.
947. Document Page Paragraph (GoogleCloudDocumentaiV1DocumentPageParagraph) – Description: Represents a paragraph of text within a document page, including its properties and layout. – SEO Purpose: Enhances document representation by providing accurate paragraph representations. – How to Use: Include paragraphs for all text within pages. This improves representation and indexing.
948. Table Structure (GoogleCloudDocumentaiV1DocumentPageTable)
     • Description: This factor involves the representation of a table within a document, mirroring HTML table structures. It includes attributes that define the table’s rows, cells, and overall layout.
     • SEO Purpose: Helps in structuring and organizing data efficiently, making it easier for search engines to parse and understand the content.
     • How to Use: Use table structures to present data clearly and concisely, ensuring proper formatting and alignment for improved readability and SEO performance.
949. Table Cell (GoogleCloudDocumentaiV1DocumentPageTableTableCell)
     • Description: Represents an individual cell within a table. Attributes include cell content, formatting, and cell coordinates within the table.
     • SEO Purpose: Enhances data segmentation and clarity, allowing search engines to better interpret specific pieces of information.
     • How to Use: Ensure each cell contains relevant and precise information, formatted correctly for both users and search engines.
950. Table Row (GoogleCloudDocumentaiV1DocumentPageTableTableRow)
     • Description: Represents a row in a table, containing multiple table cells. Attributes define the sequence and content of cells in that row.
     • SEO Purpose: Facilitates logical data flow and organization, aiding in the semantic understanding of structured data.
     • How to Use: Organize rows logically, maintaining a clear and consistent format for enhanced user experience and SEO.
951. Detected Token (GoogleCloudDocumentaiV1DocumentPageToken)
     • Description: Identifies individual tokens (words or symbols) detected in a document. Attributes include the token’s text, position, and related metadata.
     • SEO Purpose: Supports accurate text extraction and indexing, improving content discoverability and relevance.
     • How to Use: Utilize detected tokens to refine text processing and extraction, ensuring high accuracy for search engine indexing.
952. Detected Break (GoogleCloudDocumentaiV1DocumentPageTokenDetectedBreak)
     • Description: Indicates a detected break at the end of a token, such as a space or line break. Attributes detail the type and position of the break.
     • SEO Purpose: Enhances text segmentation and readability, aiding in proper text flow and presentation.
     • How to Use: Implement detected breaks to manage text layout and spacing, optimizing content for both users and search engines.
953. Token Style Information (GoogleCloudDocumentaiV1DocumentPageTokenStyleInfo)
     • Description: Provides style attributes for tokens, including font, size, and other text formatting details.
     • SEO Purpose: Ensures consistent text styling and presentation, contributing to a professional and readable content layout.
     • How to Use: Apply consistent styling to text tokens, adhering to design standards and improving visual appeal.
954. Visual Elements (GoogleCloudDocumentaiV1DocumentPageVisualElement)
     • Description: Identifies non-text visual elements on a page, such as checkboxes or signatures. Attributes include element type, position, and metadata.
     • SEO Purpose: Enhances the semantic understanding of visual components, aiding in content categorization and accessibility.
     • How to Use: Tag and describe visual elements accurately to improve content structure and search engine comprehension.
955. Document Provenance (GoogleCloudDocumentaiV1DocumentProvenance)
     • Description: Tracks the provenance or origin of annotations and edits within a document, detailing relationships and revisions.
     • SEO Purpose: Ensures transparency and traceability of content changes, enhancing credibility and trustworthiness.
     • How to Use: Maintain detailed records of content changes and provenance to ensure accountability and accuracy.
956. Provenance Parent (GoogleCloudDocumentaiV1DocumentProvenanceParent)
     • Description: Details the parent element that the current element is based on, used for referencing and aligning content changes.
     • SEO Purpose: Facilitates content versioning and alignment, ensuring consistency and reliability.
     • How to Use: Use provenance parent attributes to manage content revisions and dependencies accurately.
957. Document Revision (GoogleCloudDocumentaiV1DocumentRevision)
     • Description: Contains information about past or future revisions of a document, including changes and annotations.
     • SEO Purpose: Supports version control and historical tracking, enhancing content management and integrity.
     • How to Use: Implement robust revision tracking to manage document versions effectively, ensuring accurate historical records.
958. Human Review (GoogleCloudDocumentaiV1DocumentRevisionHumanReview)
     • Description: Provides details on human review of the document, including review status and outcomes.
     • SEO Purpose: Ensures quality control and accuracy through human oversight, improving content reliability.
     • How to Use: Incorporate human review processes to validate content, ensuring high standards of accuracy and trust.
959. Document Shard Information (GoogleCloudDocumentaiV1DocumentShardInfo)
     • Description: Details the sharding of a large document into smaller segments, including shard identifiers and offsets.
     • SEO Purpose: Enables efficient handling and processing of large documents, improving performance and manageability.
     • How to Use: Use shard information to divide and manage large documents, optimizing processing and retrieval.
960. Text Style (GoogleCloudDocumentaiV1DocumentStyle)
     • Description: Defines common text style attributes, adhering to CSS conventions for consistency in text presentation.
     • SEO Purpose: Ensures consistent text styling across documents, enhancing readability and aesthetic appeal.
     • How to Use: Apply standard text styles to maintain uniformity and professionalism in document presentation.
961. Font Size (GoogleCloudDocumentaiV1DocumentStyleFontSize)
     • Description: Specifies the font size and unit for text within a document, ensuring clear and readable text.
     • SEO Purpose: Enhances text readability and accessibility, contributing to a positive user experience.
     • How to Use: Ensure appropriate font sizes are used consistently, improving text legibility and user engagement.
962. Text Anchor (GoogleCloudDocumentaiV1DocumentTextAnchor)
     • Description: Provides a reference index for text within the document, facilitating precise text identification and retrieval.
     • SEO Purpose: Improves text referencing and linking, aiding in accurate content indexing and navigation.
     • How to Use: Use text anchors to link and reference specific text segments, enhancing content accessibility and SEO.
963. Text Segment (GoogleCloudDocumentaiV1DocumentTextAnchorTextSegment)
     • Description: Represents a specific segment of text within the document, with attributes indicating text range and shard details.
     • SEO Purpose: Supports detailed text segmentation and indexing, improving content discoverability.
     • How to Use: Define clear text segments to facilitate precise content retrieval and indexing.
964. Text Change (GoogleCloudDocumentaiV1DocumentTextChange)
     • Description: Captures changes to the text, including OCR corrections and edits, providing details on the modifications.
     • SEO Purpose: Ensures accurate text content through tracking and correction, enhancing content quality.
     • How to Use: Monitor and record text changes to maintain accuracy and quality in document content.
965. Normalized Vertex (GoogleCloudDocumentaiV1NormalizedVertex)
     • Description: Represents a 2D point in an image with normalized coordinates, used for precise image mapping and alignment.
     • SEO Purpose: Enhances the accuracy of visual element positioning, improving content layout and presentation.
     • How to Use: Utilize normalized vertices to accurately map and align visual elements within images.
966. Vertex (GoogleCloudDocumentaiV1Vertex)
     • Description: Represents a 2D point in an image with coordinates relative to the original image scale, ensuring precise positioning.
     • SEO Purpose: Supports accurate visual element placement, enhancing content structure and readability.
     • How to Use: Implement vertex coordinates to ensure accurate visual representation and alignment in images.
967. Audit Configuration (GoogleIamV1AuditConfig)
     • Description: Specifies the audit configuration for a service, detailing which permission types are logged and any exemptions.
     • SEO Purpose: Enhances security and compliance by logging and monitoring access to services, protecting sensitive information.
     • How to Use: Configure audit settings to monitor and log access to services, ensuring compliance and security.
968. Audit Log Configuration (GoogleIamV1AuditLogConfig)
     • Description: Provides configuration for logging specific types of permissions, including exemptions for certain users.
     • SEO Purpose: Supports detailed monitoring and logging of permission usage, improving security and accountability.
     • How to Use: Set up audit log configurations to track permission usage and identify any potential security issues.
969. IAM Binding (GoogleIamV1Binding)
     • Description: Associates members or principals with a specific role, defining access controls for resources.
     • SEO Purpose: Ensures proper access control and role assignment, protecting sensitive data and resources.
     • How to Use: Define and manage IAM bindings to control access and maintain security across resources.
970. IAM Policy (GoogleIamV1Policy)
     • Description: Specifies access controls for Google Cloud resources, detailing bindings, roles, and conditions for access.
     • SEO Purpose: Enhances security and compliance by defining and enforcing access policies for cloud resources.
     • How to Use: Implement and manage IAM policies to control access, ensuring compliance and protecting resources.
971. User Availability Period (GoogleInternalAppsWaldoV1alphaAvailabilityPeriod)
     • Description: Represents the user’s working hours for a given day, including start and end times.
     • SEO Purpose: Provides clear information on user availability, improving scheduling and communication.
     • How to Use: Define availability periods to accurately represent working hours and improve coordination.
972. Calendar Busy Status (GoogleInternalAppsWaldoV1alphaCalendarBusy)
     • Description: Indicates the user is temporarily busy, derived from calendar entries, such as meetings or other commitments.
     • SEO Purpose: Enhances scheduling efficiency by providing accurate busy status, avoiding conflicts.
     • How to Use: Use calendar busy status to inform others of current commitments, improving scheduling and communication.
973. Custom Location (GoogleInternalAppsWaldoV1alphaCustomLocation)
     • Description: Specifies a custom location for the user, beyond standard office or home locations.
     • SEO Purpose: Provides detailed location information, enhancing coordination and logistics.
     • How to Use: Define and use custom locations for accurate representation of user whereabouts and scheduling.
974. Do Not Disturb Status (GoogleInternalAppsWaldoV1alphaDoNotDisturb)
     • Description: Indicates the user should not be disturbed, often due to focus time or critical tasks.
     • SEO Purpose: Enhances productivity by clearly marking periods of undisturbed time.
     • How to Use: Set and communicate do not disturb status to minimize interruptions and improve focus.
975. Home Location (GoogleInternalAppsWaldoV1alphaHomeLocation)
     • Description: Represents the user’s home location, used for scheduling and coordination purposes.
     • SEO Purpose: Provides accurate location information, improving scheduling and logistical planning.
     • How to Use: Define home location for accurate representation and better planning of work-from-home scenarios.
976. Meeting Status (GoogleInternalAppsWaldoV1alphaInMeeting)
     • Description: Indicates the user is currently in a meeting, derived from calendar entries.
     • SEO Purpose: Improves scheduling efficiency by clearly indicating when a user is in a meeting.
     • How to Use: Use meeting status to inform others and avoid scheduling conflicts during meeting times.
977. Inactive Status (GoogleInternalAppsWaldoV1alphaInactive)
     • Description: Indicates that no specific status applies to the user at the moment.
     • SEO Purpose: Provides a fallback status for periods with no specific activity, aiding in overall availability tracking.
     • How to Use: Set inactive status to cover periods without specific commitments or activities, maintaining accurate availability records.
978. Local Time Context (GoogleInternalAppsWaldoV1alphaLocalTimeContext)
     • Description: Provides context about the user’s local time, assisting in accurate scheduling and coordination across time zones.
     • SEO Purpose: Enhances coordination by considering the user’s local time, reducing scheduling conflicts.
     • How to Use: Use local time context to plan meetings and activities, respecting the user’s time zone.
979. Office Location (GoogleInternalAppsWaldoV1alphaOfficeLocation)
     • Description: Represents the user’s office location, used for scheduling and coordination.
     • SEO Purpose: Provides accurate location information, improving logistical planning and coordination.
     • How to Use: Define office location for precise representation and better planning of in-office activities.
980. Out of Office Status (GoogleInternalAppsWaldoV1alphaOutOfOffice)
     • Description: Indicates the user is out of the office, derived from calendar entries.
     • SEO Purpose: Enhances scheduling by clearly marking periods when the user is unavailable.
     • How to Use: Set out of office status to inform others of unavailability, aiding in scheduling and planning.
981. Outside Working Hours (GoogleInternalAppsWaldoV1alphaOutsideWorkingHours)
     • Description: Indicates the user is not working at the current time, based on predefined working hours.
     • SEO Purpose: Provides clear boundaries for working hours, improving work-life balance and scheduling.
     • How to Use: Define and respect outside working hours to ensure accurate availability representation and support work-life balance.
982. Time Range (GoogleInternalAppsWaldoV1alphaTimeRange)
     • Description: Represents a specific time range, including start and end times, used for scheduling and availability tracking.
     • SEO Purpose: Enhances scheduling accuracy by clearly defining time ranges for activities and commitments.
     • How to Use: Use time ranges to plan and coordinate activities, ensuring precise scheduling and availability management.
983. Upcoming Commitment Context (GoogleInternalAppsWaldoV1alphaUpcomingCommitmentContext)
     • Description: Provides context about the user’s next commitment, including status and timing details.
     • SEO Purpose: Improves scheduling by highlighting upcoming commitments, aiding in better planning.
     • How to Use: Use upcoming commitment context to inform planning and coordination, ensuring awareness of future commitments.
984. Upcoming Out of Office Context (GoogleInternalAppsWaldoV1alphaUpcomingOooContext)
     • Description: Indicates the user’s upcoming out of office event, providing context for future unavailability.
     • SEO Purpose: Enhances planning by highlighting future out of office periods, aiding in scheduling.
     • How to Use: Set and communicate upcoming out of office context to inform others and avoid scheduling conflicts.
985. User Availabilities (GoogleInternalAppsWaldoV1alphaUserAvailabilities)
     • Description: Represents the current and future availabilities of a user, providing a timeline of availability intervals.
     • SEO Purpose: Improves scheduling and coordination by providing detailed availability information.
     • How to Use: Use user availabilities to plan meetings and activities, ensuring alignment with the user’s availability.
986. User Availability (GoogleInternalAppsWaldoV1alphaUserAvailability)
     • Description: A single availability range for the user, indicating the status during the entire time range.
     • SEO Purpose: Provides clear and consistent availability information, aiding in scheduling.
     • How to Use: Define and use user availability ranges to ensure accurate scheduling and coordination.
987. User Context (GoogleInternalAppsWaldoV1alphaUserContext)
     • Description: Additional context about the user’s current and/or future availability, providing a better understanding of their status.
     • SEO Purpose: Enhances communication and coordination by providing detailed context about user availability.
     • How to Use: Use user context to inform others about specific availability details, improving coordination.
988. User Location (GoogleInternalAppsWaldoV1alphaUserLocation)
     • Description: Specifies the user’s location, such as home or office, or a custom location defined by the user.
     • SEO Purpose: Provides accurate location information, enhancing logistical planning and coordination.
     • How to Use: Define and communicate user locations for accurate representation and better planning.
989. User Status (GoogleInternalAppsWaldoV1alphaUserStatus)
     • Description: Indicates the actual status of the user, containing all necessary details for visualization.
     • SEO Purpose: Provides clear status information, aiding in communication and coordination.
     • How to Use: Use user status to communicate current activities or availability, improving scheduling efficiency.
990. Working Elsewhere Context (GoogleInternalAppsWaldoV1alphaWorkingElsewhereContext)
     • Description: Provides context about the user working remotely or from a different location, including office details.
     • SEO Purpose: Enhances communication and planning by providing detailed context about remote work.
     • How to Use: Use working elsewhere context to inform others about remote work status, aiding in coordination.
991. Working Hours (GoogleInternalAppsWaldoV1alphaWorkingHours)
     • Description: Details the user’s working hours, providing information about start and end times for work periods.
     • SEO Purpose: Provides clear boundaries for work periods, improving scheduling and work-life balance.
     • How to Use: Define and respect working hours to ensure accurate availability representation and support work-life balance.
992. Message Recipient Id (GoogleInternalCommunicationsInstantmessagingV1Id)
     • Description: Identifies message recipients, such as users or groups, used in instant messaging systems.
     • SEO Purpose: Supports accurate message delivery and communication by identifying recipients.
     • How to Use: Use recipient IDs to ensure messages are delivered to the correct users or groups.
993. Location Hint (GoogleInternalCommunicationsInstantmessagingV1LocationHint)
     • Description: Specifies a location, including formatting details, for instant messaging purposes.
     • SEO Purpose: Provides context for location-based messaging, enhancing communication relevance.
     • How to Use: Use location hints to provide accurate location context in messages, improving communication clarity.
994. Long-running Operation (GoogleLongrunningOperation)
     • Description: Represents a long-running operation resulting from a network API call, detailing status and progress.
     • SEO Purpose: Enhances tracking and management of long-running processes, ensuring efficient operation handling.
     • How to Use: Monitor and manage long-running operations to ensure timely completion and accurate status tracking.
995. Empty Message (GoogleProtobufEmpty)
     • Description: A generic empty message used to avoid defining duplicated empty messages in APIs.
     • SEO Purpose: Simplifies API design by providing a reusable empty message structure.
     • How to Use: Use the empty message as a request or response type in API methods where no additional data is required.
996. Status (GoogleRpcStatus)
     • Description: Defines a logical error model suitable for different programming environments, including error code, message, and details.
     • SEO Purpose: Provides a standardized error handling mechanism, improving API reliability and debugging.
     • How to Use: Implement the status model to handle errors consistently across APIs, ensuring clear communication of issues.
997. Color (GoogleTypeColor)
     • Description: Represents a color in the RGBA color space, designed for simplicity of conversion to various languages.
     • SEO Purpose: Enhances visual representation and customization by providing a standardized color model.
     • How to Use: Use the color model to define and apply colors consistently across applications, ensuring visual coherence.
998. Date (GoogleTypeDate)
     • Description: Represents a whole or partial calendar date, relative to the Gregorian Calendar, for various purposes.
     • SEO Purpose: Provides accurate date representation, enhancing scheduling and time-related functionalities.
     • How to Use: Use the date model to represent and manage dates consistently across applications, supporting scheduling and planning.
999. DateTime (GoogleTypeDateTime)
     • Description: Represents civil time, including options for time zones and UTC offsets, for precise time representation.
     • SEO Purpose: Enhances scheduling and coordination by providing flexible and accurate time representation.
     • How to Use: Implement the DateTime model to handle time-related data accurately, considering time zones and offsets.
1000. Expression (GoogleTypeExpr)
      • Description: Represents a textual expression in the Common Expression Language (CEL) syntax for logical and comparison operations.
      • SEO Purpose: Enhances data manipulation and validation by providing a flexible expression language.
      • How to Use: Use expressions to perform logical operations and comparisons, improving data processing and validation.
1001. Time Interval (GoogleTypeInterval)
      • Description: Represents a time interval with start and end timestamps, used for scheduling and duration tracking.
      • SEO Purpose: Provides precise time interval representation, enhancing scheduling and time management.
      • How to Use: Define and use time intervals to track durations and manage schedules accurately.
1002. Latitude/Longitude Pair (GoogleTypeLatLng)
      • Description: Represents a latitude/longitude pair for geographical locations, adhering to the WGS84 standard.
      • SEO Purpose: Enhances geographical data representation and mapping by providing accurate location coordinates.
      • How to Use: Use lat/long pairs to represent and manage geographical locations, supporting mapping and location-based services.
1003. Money (GoogleTypeMoney)
      • Description: Represents an amount of money with its currency type, used for financial transactions and calculations.
      • SEO Purpose: Enhances financial data representation by providing a standardized money model.
      • How to Use: Implement the money model to manage financial data accurately, supporting transactions and calculations.
1004. Postal Address (GoogleTypePostalAddress)
      • Description: Represents a postal address for delivery or payment purposes, including various fields for detailed address information.
      • SEO Purpose: Enhances address data management by providing a comprehensive postal address model.
      • How to Use: Use the postal address model to collect and manage address information accurately, supporting delivery and payments.
1005. Time of Day (GoogleTypeTimeOfDay)
      • Description: Represents a time of day, used for scheduling and time-specific functionalities.
      • SEO Purpose: Provides accurate time of day representation, enhancing scheduling and time management.
      • How to Use: Implement the time of day model to manage time-specific data accurately, supporting scheduling and planning.
1006. Time Zone (GoogleTypeTimeZone)
      • Description: Represents a time zone from the IANA Time Zone Database, used for accurate time representation.
      • SEO Purpose: Enhances time zone management by providing a standardized time zone model.
      • How to Use: Use the time zone model to handle time-related data accurately, considering time zone differences.
1007. Groups Per Document Data (GroupsPerDocData)
      • Description: This ranking factor involves metadata related to groups associated with a document. It includes attributes such as author IDs, group IDs, and thread IDs, which help in identifying the contributors and relevant groups.
      • SEO Purpose: Enhances the contextual understanding and credibility of content by linking it to specific authors and groups.
      • How to Use: Ensure accurate and comprehensive metadata for each document, linking relevant groups and authors to improve the content’s authenticity and relevance in search results.
1008. Route Information (HomeGraphCommonRoute)
      • Description: This factor details execution routing information for device interactions. Attributes include agent device ID, agent ID, chip endpoint, and target type, which specify how commands are routed to devices.
      • SEO Purpose: Improves the functionality and reliability of smart home integrations by ensuring accurate device routing information.
      • How to Use: Configure and maintain precise routing information for smart home devices to enhance user experience and device performance.
1009. Routing Table (HomeGraphCommonRoutingTable)
      • Description: Defines the routing information for various traits in smart home devices, mapping traits to specific routing logic.
      • SEO Purpose: Ensures efficient and accurate command execution for smart home devices by organizing routing information systematically.
      • How to Use: Implement and update routing tables to optimize the performance and responsiveness of smart home integrations.
1010. Trait Routing Hints (HomeGraphCommonTraitRoutingHints)
      • Description: Provides extendible design attributes for future enhancements in trait routing, allowing for flexible and adaptable smart home device configurations.
      • SEO Purpose: Supports future-proofing of smart home systems by enabling easy updates and additions to routing logic.
      • How to Use: Use trait routing hints to ensure your smart home systems remain adaptable and can incorporate new functionalities seamlessly.
1011. Timing Statistic Pair (HtmlrenderWebkitHeadlessProtoAnonTimingStatPair)
      • Description: Stores timing statistics for rendering processes, including a period name and time value, used for performance evaluation.
      • SEO Purpose: Enhances performance monitoring and optimization by providing detailed timing data for rendering processes.
      • How to Use: Regularly review and analyze timing statistics to identify and address performance bottlenecks in rendering workflows.
1012. 2D Box (HtmlrenderWebkitHeadlessProtoBox)
      • Description: Represents a simple 2D box defined by coordinates, width, and height, used in rendering processes.
      • SEO Purpose: Facilitates accurate layout and positioning of elements within rendered content, improving visual structure.
      • How to Use: Use 2D boxes to manage element positioning accurately, ensuring a well-organized and visually appealing layout.
1013. Chromium Trace (HtmlrenderWebkitHeadlessProtoChromiumTrace)
      • Description: Describes trace events returned by Chromium, used for debugging and performance analysis.
      • SEO Purpose: Supports in-depth debugging and performance optimization by providing detailed trace information.
      • How to Use: Utilize Chromium traces to diagnose and resolve performance issues, enhancing the efficiency and stability of rendering processes.
1014. Console Log Entry (HtmlrenderWebkitHeadlessProtoConsoleLogEntry)
      • Description: Stores messages logged to the console by the renderer, including error messages related to JavaScript execution and CSS parsing.
      • SEO Purpose: Improves debugging and error resolution by capturing detailed console logs during rendering.
      • How to Use: Regularly review console log entries to identify and fix errors, ensuring smooth and error-free rendering.
1015. Cookie (HtmlrenderWebkitHeadlessProtoCookie)
      • Description: Represents a browser cookie with attributes such as domain, expiration, HTTP-only status, name, path, same-site policy, secure status, and value.
      • SEO Purpose: Enhances user session management and security by properly configuring cookies.
      • How to Use: Implement cookies with appropriate settings to manage user sessions securely and maintain compliance with privacy policies.
1016. DOM Storage Item (HtmlrenderWebkitHeadlessProtoDOMStorageItem)
      • Description: Defines an item in the DOM storage, including key, security origin, and value.
      • SEO Purpose: Supports efficient data storage and retrieval within the browser, enhancing application performance.
      • How to Use: Use DOM storage items to store and manage data locally, improving performance and user experience.
1017. DOM Tree Node (HtmlrenderWebkitHeadlessProtoDOMTreeNode)
      • Description: Represents a node in the DOM tree, containing references to child nodes and rendering information.
      • SEO Purpose: Enhances the structuring and rendering of web pages by providing detailed DOM tree information.
      • How to Use: Organize and manipulate DOM tree nodes effectively to ensure optimal rendering and functionality of web pages.
1018. DOM Tree Node Attribute (HtmlrenderWebkitHeadlessProtoDOMTreeNodeAttribute)
      • Description: Defines attributes for a DOM tree node, contributing to the node’s properties and behavior.
      • SEO Purpose: Improves the definition and functionality of DOM elements by accurately specifying their attributes.
      • How to Use: Set and manage DOM tree node attributes to control element behavior and appearance precisely.
1019. Document (HtmlrenderWebkitHeadlessProtoDocument)
      • Description: Represents a document in the rendering process, containing various nodes and elements.
      • SEO Purpose: Facilitates comprehensive rendering and manipulation of web documents.
      • How to Use: Use the document structure to organize and manage all elements and nodes involved in rendering.
1020. Frame Resize Event (HtmlrenderWebkitHeadlessProtoFrameResizeEvent)
      • Description: Captures events related to frame resizing, specifically those caused by automatic frame expansion.
      • SEO Purpose: Enhances the responsiveness and adaptability of web content to different screen sizes and resolutions.
      • How to Use: Monitor and handle frame resize events to ensure content remains visually appealing across various devices.
1021. Image (HtmlrenderWebkitHeadlessProtoImage)
      • Description: Represents an image within a document, including binary data, height, width, and viewport details.
      • SEO Purpose: Enhances the visual content of web pages by accurately rendering images.
      • How to Use: Manage image attributes to ensure high-quality rendering and optimal display of visual content.
1022. Initial Load Event (HtmlrenderWebkitHeadlessProtoInitialLoadEvent)
      • Description: Records the initial load event of a frame, including main frame and subframes.
      • SEO Purpose: Provides insights into page load performance and initial rendering efficiency.
      • How to Use: Analyze initial load events to optimize page load times and improve user experience.
1023. Modal Dialog Event (HtmlrenderWebkitHeadlessProtoModalDialogEvent)
      • Description: Captures events related to modal dialogs created by window methods like confirm, prompt, or alert.
      • SEO Purpose: Supports debugging and user interaction tracking by recording modal dialog events.
      • How to Use: Monitor modal dialog events to ensure smooth and effective user interactions with web content.
1024. Offset (HtmlrenderWebkitHeadlessProtoOffset)
      • Description: Defines an offset with unit and value, used for positioning elements within a rendered document.
      • SEO Purpose: Enhances element positioning accuracy, ensuring a well-structured and visually appealing layout.
      • How to Use: Apply offsets to position elements precisely, maintaining consistent and organized layouts.
1025. Partial Render (HtmlrenderWebkitHeadlessProtoPartialRender)
      • Description: Allows the creation of partial renders to store document state or generate images before final rendering.
      • SEO Purpose: Supports incremental rendering and performance optimization by handling partial renders.
      • How to Use: Utilize partial renders to manage and optimize document state and rendering processes.
1026. PDF (HtmlrenderWebkitHeadlessProtoPdf)
      • Description: Represents a PDF document, including binary data for the PDF file.
      • SEO Purpose: Enhances document accessibility and distribution by providing PDF versions of content.
      • How to Use: Generate and manage PDF documents to ensure content is accessible and shareable in a widely-used format.
1027. Rectangle (HtmlrenderWebkitHeadlessProtoRectangle)
      • Description: Represents a rectangle with attributes for top, bottom, left, and right offsets, used in rendering.
      • SEO Purpose: Facilitates accurate layout and positioning of rectangular elements within rendered content.
      • How to Use: Use rectangle attributes to define and position elements precisely, ensuring a well-organized layout.
1028. Redirect Event (HtmlrenderWebkitHeadlessProtoRedirectEvent)
      • Description: Captures events related to resource URL changes, including HTTP redirects and client-side navigations.
      • SEO Purpose: Supports tracking and handling of redirects, improving navigation efficiency and user experience.
      • How to Use: Monitor and manage redirect events to ensure smooth navigation and effective handling of URL changes.
1029. Redirect Hop (HtmlrenderWebkitHeadlessProtoRedirectHop)
      • Description: Represents a single hop in a redirect chain, including the target URL and type of redirect.
      • SEO Purpose: Enhances the understanding and handling of redirect chains, improving navigation efficiency.
      • How to Use: Track redirect hops to manage and optimize the handling of redirect chains, ensuring smooth navigation.
1030. Referenced Resource (HtmlrenderWebkitHeadlessProtoReferencedResource)
      • Description: Contains entries for URLs referenced by the browser during document rendering.
      • SEO Purpose: Supports efficient resource management and optimization by tracking referenced URLs.
      • How to Use: Monitor and manage referenced resources to ensure efficient loading and rendering of external content.
1031. Fetch Timing (HtmlrenderWebkitHeadlessProtoReferencedResourceFetchTiming)
      • Description: Provides timing data for resource fetching, aiding in performance analysis.
      • SEO Purpose: Enhances performance optimization by providing detailed fetch timing data.
      • How to Use: Analyze fetch timing data to identify and address performance bottlenecks in resource loading.
1032. HTTP Header (HtmlrenderWebkitHeadlessProtoReferencedResourceHttpHeader)
      • Description: Represents HTTP headers included with resource requests, detailing request attributes.
      • SEO Purpose: Supports detailed analysis and optimization of HTTP requests by providing header information.
      • How to Use: Review and manage HTTP headers to ensure efficient and secure resource requests.
1033. Render Event (HtmlrenderWebkitHeadlessProtoRenderEvent)
      • Description: Captures various render-related events, including frame resize, initial load, modal dialogs, and redirects.
      • SEO Purpose: Enhances debugging and performance optimization by recording detailed render events.
      • How to Use: Monitor and analyze render events to optimize rendering processes and improve user experience.
1034. Render Extension Result (HtmlrenderWebkitHeadlessProtoRenderExtensionResult)
      • Description: Represents results returned by a render server extension, aiding in render quality evaluation.
      • SEO Purpose: Supports the assessment and improvement of rendering quality by providing detailed extension results.
      • How to Use: Use render extension results to evaluate and enhance the quality of rendered content.
1035. Render Response (HtmlrenderWebkitHeadlessProtoRenderResponse)
      • Description: Details the response from a render server, used for evaluating render quality.
      • SEO Purpose: Supports quality assurance and optimization of rendering processes.
      • How to Use: Analyze render responses to ensure high-quality rendering and address any issues.
1036. Render Statistics (HtmlrenderWebkitHeadlessProtoRenderStats)
      • Description: Provides various statistics related to the rendering process.
      • SEO Purpose: Enhances performance monitoring and optimization by providing detailed render statistics.
      • How to Use: Review render statistics regularly to identify and address performance issues in rendering workflows.
1037. Render Event Counter (HtmlrenderWebkitHeadlessProtoRenderStatsCounter)
      • Description: Tracks and counts render events, providing data for performance analysis.
      • SEO Purpose: Supports detailed performance monitoring by counting render events.
      • How to Use: Use render event counters to track and analyze rendering activity, optimizing performance.
1038. Render Tree Node (HtmlrenderWebkitHeadlessProtoRenderTreeNode)
      • Description: Represents a node in the render tree, including attributes like bounding boxes, child nodes, and styles.
      • SEO Purpose: Facilitates detailed structuring and rendering of web content by providing render tree node information.
      • How to Use: Organize and manage render tree nodes to ensure optimal rendering and layout of web content.
1039. Inline Text Box (HtmlrenderWebkitHeadlessProtoRenderTreeNodeInlineTextBox)
      • Description: Defines individual lines of text within a text node, providing specific bounding boxes.
      • SEO Purpose: Enhances text rendering accuracy by detailing inline text boxes.
      • How to Use: Use inline text boxes to manage and optimize the rendering of text content, ensuring clarity and precision.
1040. Resource (HtmlrenderWebkitHeadlessProtoResource)
      • Description: Represents a resource used in rendering, with various attributes for resource management.
      • SEO Purpose: Supports efficient resource management and optimization by providing detailed resource information.
      • How to Use: Manage resources effectively to ensure efficient loading and rendering of content.
1041. Resource HTTP Header (HtmlrenderWebkitHeadlessProtoResourceHttpHeader)
      • Description: Represents HTTP headers associated with a resource, detailing request and response attributes.
      • SEO Purpose: Enhances resource request and response handling by providing HTTP header information.
      • How to Use: Review and manage resource HTTP headers to optimize request and response handling.
1042. Script Stack Frame (HtmlrenderWebkitHeadlessProtoScriptStackFrame)
      • Description: Describes a script stack frame, used for debugging and performance analysis.
      • SEO Purpose: Supports in-depth debugging and performance optimization by providing stack frame information.
      • How to Use: Analyze script stack frames to diagnose and resolve performance issues and errors.
1043. Style (HtmlrenderWebkitHeadlessProtoStyle)
      • Description: Defines font and text decorations for rendering, providing detailed styling information.
      • SEO Purpose: Enhances the visual presentation of content by providing comprehensive styling details.
      • How to Use: Apply styles consistently to ensure a visually appealing and well-structured presentation of content.
1044. Fetch Metadata (HtmlrenderWebkitHeadlessProtoWebKitFetchMetadata)
      • Description: Holds additional WebKit-specific information for a single resource fetch.
      • SEO Purpose: Enhances resource fetching and performance optimization by providing detailed fetch metadata.
      • How to Use: Use fetch metadata to analyze and optimize resource fetching processes, ensuring efficient loading.
1045. Window Open Event (HtmlrenderWebkitHeadlessProtoWindowOpenEvent)
      • Description: Corresponds to a call to window.open(), capturing details of the event.
      • SEO Purpose: Supports debugging and user interaction tracking by recording window open events.
      • How to Use: Monitor window open events to ensure smooth and effective user interactions with web content.
1046. Phone Number (I18nPhonenumbersPhoneNumber)
      • Description: Represents a phone number in a format used by LibPhoneNumber APIs.
      • SEO Purpose: Ensures accurate and standardized representation of phone numbers, improving contact information management.
      • How to Use: Use the phone number format to manage and validate contact information consistently, enhancing communication accuracy.
1047. Thumbnail Metadata (ImageBaseThumbnailMetadata)
      • Description: Stores metadata related to image thumbnails, including dimensions and expiration details.
      • SEO Purpose: Enhances image indexing and retrieval by providing detailed thumbnail metadata.
      • How to Use: Manage thumbnail metadata to ensure efficient indexing and accurate representation of image content.
1048. Video Preview Metadata (ImageBaseVideoPreviewMetadata)
      • Description: Contains metadata for video previews, including type, dimensions, and byte size.
      • SEO Purpose: Enhances video indexing and retrieval by providing detailed preview metadata.
      • How to Use: Use video preview metadata to manage and optimize the indexing and display of video content.
1049. Content Flow (ImageContentFlowProtoProd)
      • Description: Defines the subset of content flow data to be used in production and stored in content signals.
      • SEO Purpose: Supports efficient content management and indexing by providing detailed flow data.
      • How to Use: Implement content flow data to optimize content management and ensure accurate indexing.
1050. Query Boost (ImageContentQueryBoost)
      • Description: Applies multipliers to image content based on query relevance, enhancing search result ranking.
      • SEO Purpose: Improves search result relevance and ranking for image content by applying query-specific boosts.
      • How to Use: Use query boost attributes to enhance the visibility and ranking of image content in search results.
1051. Version Group (ImageContentStarburstVersionGroup)
      • Description: Represents version-specific attributes for image content features, including descriptors and tokens.
      • SEO Purpose: Enhances image feature representation and indexing by providing detailed version information.
      • How to Use: Manage version group attributes to ensure accurate and efficient indexing of image features.
1052. Image Data (ImageData)
      • Description: Defines the per-document data extracted from thumbnails and propagated for indexing purposes.
      • SEO Purpose: Supports comprehensive image indexing and retrieval by providing detailed image data.
      • How to Use: Use image data to enhance the indexing and retrieval of image content, ensuring accuracy and completeness.
1053. Multibang Entities (ImageDataMultibangEntities)
      • Description: Represents knowledge graph entities associated with images, including entity IDs and scores.
      • SEO Purpose: Enhances image content relevance and contextual understanding by linking to knowledge graph entities.
      • How to Use: Manage multibang entities to improve the contextual relevance and searchability of image content.
1054. Thumbnail (ImageDataThumbnail)
      • Description: Contains attributes related to image thumbnails, such as expiration, dimensions, MIME type, size, and type.
      • SEO Purpose: Enhances image representation and indexing by providing detailed thumbnail information.
      • How to Use: Manage thumbnail attributes to ensure accurate and efficient indexing and display of image thumbnails.
1055. Vertical Indexing Info (ImageDataVerticalIndexingInfoImage)
      • Description: Stores vertical indexing information for documents and associated image outlinks.
      • SEO Purpose: Supports specialized indexing of image content in verticals, improving search relevance.
      • How to Use: Use vertical indexing info to optimize the indexing of image content for specific verticals, enhancing search results.
1056. Exact Boost (ImageExactBoost)
      • Description: Applies boosts to image content based on exact match queries, enhancing search result ranking.
      • SEO Purpose: Improves search result relevance and ranking for image content with exact match queries.
      • How to Use: Implement exact boost attributes to enhance the visibility and ranking of image content in search results.
1057. Nav Query (ImageExactBoostNavQuery)
      • Description: Contains navigation query data for applying boosts to image content.
      • SEO Purpose: Enhances search result relevance and ranking for image content based on navigation queries.
      • How to Use: Use nav query data to manage and optimize boosts for image content, improving search relevance.
1058. Exif IPTC Metadata (ImageExifIPTCMetadata)
      • Description: Stores IPTC metadata for images, including various attributes for detailed image information.
      • SEO Purpose: Enhances image metadata management and indexing by providing detailed IPTC metadata.
      • How to Use: Use IPTC metadata to manage and index image content accurately, ensuring comprehensive metadata representation.
1059. Artwork Details (ImageExifIPTCMetadataArtwork)
      • Description: Represents detailed information about artwork or objects within an image.
      • SEO Purpose: Enhances the contextual understanding and indexing of image content by providing detailed artwork information.
      • How to Use: Manage artwork details to improve the contextual relevance and indexing of image content.
1060. Contact Information (ImageExifIPTCMetadataContactInfo)
      • Description: Contains contact information related to the image, including address, city, country, email, phone, postal code, state, and web URL.
      • SEO Purpose: Supports accurate and comprehensive contact information management for image content.
      • How to Use: Use contact information to enhance metadata accuracy and ensure comprehensive indexing of image content.
1061. Location Information (ImageExifIPTCMetadataLocation)
      • Description: Represents the location where the image was taken, including various attributes for detailed location data.
      • SEO Purpose: Enhances the contextual understanding and indexing of image content by providing detailed location information.
      • How to Use: Manage location information to improve the contextual relevance and searchability of image content.
1062. Location Info (ImageExifIPTCMetadataLocationInfo)
      • Description: Contains detailed location information for the camera, including city, country, country code, state, sublocation, and world region.
      • SEO Purpose: Enhances image metadata management and indexing by providing comprehensive location information.
      • How to Use: Use location info to manage and index image content accurately, ensuring detailed location metadata representation.
1063. Embedded Metadata (ImageExifImageEmbeddedMetadata)
      • Description: Holds EXIF/IPTC metadata embedded within images.
      • SEO Purpose: Supports detailed metadata management and indexing for image content by providing embedded metadata.
      • How to Use: Use embedded metadata to manage and index image content comprehensively, ensuring accurate metadata representation.
1064. Featured Image Properties (ImageMonetizationFeaturedImageProperties)
      • Description: Contains properties related to the inspiration score of an image, indicating how inspirational it is.
      • SEO Purpose: Enhances the ranking and visibility of inspirational images by providing detailed properties.
      • How to Use: Use featured image properties to manage and optimize the ranking of inspirational images in search results.
1065. Crawl State (ImageMoosedogCrawlState)
      • Description: This ranking factor tracks the state of an image’s crawl process. Attributes include the status of the crawl, reasons for non-crawlable content, timestamps, and user agent details.
      • SEO Purpose: Ensures efficient indexing of images by monitoring crawl status and resolving issues promptly.
      • How to Use: Regularly check the crawl state of images to identify and address issues that prevent crawling, ensuring all images are indexed properly for improved search visibility.
1066. Image Link Selection Info (ImageMustangImageLinkSelectionInfo)
      • Description: Provides detailed information about the selection of image links for indexing. This includes criteria and logic used for choosing which images to index.
      • SEO Purpose: Optimizes the selection of images for indexing, ensuring that the most relevant and high-quality images are included in search results.
      • How to Use: Utilize this information to refine the image selection process, focusing on high-quality and relevant images to enhance their visibility in search results.
1067. Shopping Offer Info (ImageMustangShoppingOffer)
      • Description: Organizes information about shopping offers related to images, sourced from Inventory & Policy Service.
      • SEO Purpose: Enhances the e-commerce potential of images by associating them with relevant shopping offers.
      • How to Use: Include accurate shopping offer information with images to boost their attractiveness and relevance in shopping-related searches.
1068. Per Document Image Data (ImagePerDocData)
      • Description: Contains metadata related to images on a per-document basis, including filename, dimensions, and entropy/color values for thumbnails.
      • SEO Purpose: Improves image indexing and retrieval by providing detailed metadata for each image.
      • How to Use: Ensure accurate and comprehensive metadata is included for each image to enhance its searchability and indexing quality.
1069. Porn Debug Info (ImagePornDebugInfo)
      • Description: Stores debug information for classifiers used to detect pornographic content in images.
      • SEO Purpose: Ensures the safe and appropriate indexing of images by filtering out pornographic content.
      • How to Use: Regularly review debug information to refine and improve the accuracy of pornographic content detection.
1070. Image Quality Click Signals (ImageQualityNavboostImageQualityClickSignals)
      • Description: Tracks click signals related to the quality of images, providing insights into user engagement and image performance.
      • SEO Purpose: Enhances image quality assessment by analyzing user interactions and engagement metrics.
      • How to Use: Use click signals to identify high-performing images and optimize them further to improve user engagement and search rankings.
1071. Sensitive Media Entities (ImageQualitySensitiveMediaOrPeopleEntities)
      • Description: Annotates documents with HRIDs of entities with high topicality, used by the Skin Tone Twiddler to ensure diversity in result sets.
      • SEO Purpose: Promotes diverse and inclusive search results by recognizing and addressing sensitive media content.
      • How to Use: Apply this annotation to ensure diverse representation in search results, improving user experience and search equity.
1072. Image Region (ImageRegionsImageRegion)
      • Description: Represents a specific region within an image, including its coordinates and relevant attributes.
      • SEO Purpose: Enhances detailed analysis and indexing of image content by segmenting it into regions.
      • How to Use: Define and manage image regions to provide more granular indexing and improve the relevance of image search results.
1073. Image with Regions (ImageRegionsImageRegions)
      • Description: An image containing multiple regions, each with its own attributes and coordinates.
      • SEO Purpose: Facilitates comprehensive indexing and retrieval by breaking down images into distinct regions.
      • How to Use: Segment images into regions and annotate them to improve search accuracy and relevance.
1074. Cloud Speech Signals (ImageRepositoryAmarnaCloudSpeechSignals)
      • Description: Stores speech-related signals from the cloud for images, aiding in audio content indexing.
      • SEO Purpose: Enhances multimedia content indexing by including speech signals associated with images.
      • How to Use: Integrate speech signals to improve the indexing and searchability of multimedia content, especially for audio-rich images and videos.
1075. Signals Blob (ImageRepositoryAmarnaSignalsBlob)
      • Description: Contains frame features and other signals in a blob format for efficient processing and storage.
      • SEO Purpose: Improves the handling and indexing of image content by storing detailed frame features and signals.
      • How to Use: Utilize signals blobs to efficiently process and store image data, enhancing the indexing and retrieval process.
1076. Signals Blob Info (ImageRepositoryAmarnaSignalsBlobInfo)
      • Description: Provides metadata about the signals blob, including IDs and update timestamps.
      • SEO Purpose: Ensures accurate and up-to-date indexing by tracking signals blob metadata.
      • How to Use: Monitor and manage signals blob metadata to maintain accurate and current image indexing.
1077. Amarna Status (ImageRepositoryAmarnaStatus)
      • Description: Stores the status and reasons for the inability to provide per-document information for an image.
      • SEO Purpose: Helps identify and address issues preventing accurate image indexing.
      • How to Use: Review Amarna status to troubleshoot and resolve issues affecting image indexing.
1078. Animated Image Data (ImageRepositoryAnimatedImagePerdocData)
      • Description: Contains additional data for animated images stored on a per-document basis.
      • SEO Purpose: Enhances the indexing and retrieval of animated images by providing detailed per-document data.
      • How to Use: Ensure animated images are accompanied by comprehensive metadata to improve their indexing and searchability.
1079. Transcode Metadata (ImageRepositoryApiItagSpecificMetadata)
      • Description: Metadata associated with each transcode of an image or video, detailing the specifics of the transcode process.
      • SEO Purpose: Ensures efficient management and retrieval of transcoded media content by providing detailed metadata.
      • How to Use: Include transcode metadata to accurately manage and index different versions of media content.
1080. Xtag (ImageRepositoryApiXtag)
      • Description: Represents tags associated with content, including names and values, stored in a case-sensitive manner.
      • SEO Purpose: Enhances content categorization and retrieval by tagging media with relevant attributes.
      • How to Use: Apply accurate and relevant tags to media content to improve its categorization and searchability.
1081. Xtag List (ImageRepositoryApiXtagList)
      • Description: A collection of Xtag instances associated with specific content, aiding in comprehensive content tagging.
      • SEO Purpose: Improves content organization and retrieval by providing a detailed tagging framework.
      • How to Use: Utilize Xtag lists to organize and manage content tags, enhancing search accuracy and relevance.
1082. Content-Based Video Metadata (ImageRepositoryContentBasedVideoMetadata)
      • Description: Metadata derived from video content, used for indexing and retrieval purposes.
      • SEO Purpose: Enhances the indexing and searchability of video content by providing detailed content-based metadata.
      • How to Use: Include content-based metadata to improve the indexing and search performance of video content.
1083. Crawl Status Info (ImageRepositoryCrawlStatusInfo)
      • Description: Contains fields for debugging crawl-status-related information of images and videos.
      • SEO Purpose: Facilitates the identification and resolution of crawling issues to ensure accurate indexing.
      • How to Use: Monitor and analyze crawl status info to address and resolve issues affecting the crawling and indexing of media content.
1084. Engagingness Score (ImageRepositoryDeepImageEngagingnessOutput)
      • Description: Stores scores related to the engagingness of images, derived from deep learning models.
      • SEO Purpose: Enhances the ranking of engaging images in search results by providing engagingness scores.
      • How to Use: Use engagingness scores to identify and prioritize high-engagement images in search results.
1085. File Truncation Info (ImageRepositoryFileTruncationInfo)
      • Description: Describes the truncation status of stored files, indicating whether they are complete or truncated versions.
      • SEO Purpose: Ensures the integrity and completeness of indexed media content by tracking truncation status.
      • How to Use: Monitor and manage file truncation info to ensure that only complete and accurate media files are indexed.
1086. Frame Identifier (ImageRepositoryFrameIdentifier)
      • Description: Identifies frames associated with a video, aiding in frame-level indexing and retrieval.
      • SEO Purpose: Enhances the indexing and retrieval of specific video frames by providing unique identifiers.
      • How to Use: Use frame identifiers to manage and index individual frames of video content, improving search accuracy.
1087. Frame Identifier Multi Thumbnail Variant (ImageRepositoryFrameIdentifierMultiThumbnailVariant)
      • Description: Defines frames to be used as multiple thumbnails per minute within a video.
      • SEO Purpose: Improves the representation and retrieval of video content by providing multiple thumbnail variants.
      • How to Use: Implement multi-thumbnail variants to enhance the visual representation and indexing of video content.
1088. Frame Identifier Preview Frame Zero Variant (ImageRepositoryFrameIdentifierPreviewFrameZeroVariant)
      • Description: Defines the first frame of a video preview, used for generating thumbnails.
      • SEO Purpose: Enhances the preview and indexing of video content by providing a defined preview frame.
      • How to Use: Use preview frame zero variants to improve the visual representation and indexing of video previews.
1089. Frame Identifier Thumbnail Variant (ImageRepositoryFrameIdentifierThumbnailVariant)
      • Description: Defines frames to be used as thumbnails for videos, aiding in visual indexing.
      • SEO Purpose: Enhances the visual representation and retrieval of video content by providing specific thumbnail frames.
      • How to Use: Implement thumbnail variants to ensure accurate and appealing visual representation of video content in search results.
1090. Frame-Level Starburst Embeddings (ImageRepositoryFrameLevelStarburstEmbeddings)
      • Description: Stores embeddings for frames at a frame-per-second rate, aiding in detailed video analysis and indexing.
      • SEO Purpose: Enhances the indexing and retrieval of video content by providing detailed frame-level embeddings.
      • How to Use: Use frame-level embeddings to improve the granularity and accuracy of video indexing and retrieval.
1091. Frame-Level Perdoc (ImageRepositoryFramePerdoc)
      • Description: Stores per-document data extracted from video frames, aiding in detailed video content analysis.
      • SEO Purpose: Enhances the indexing and retrieval of video content by providing detailed per-frame data.
      • How to Use: Include frame-level perdoc data to ensure comprehensive indexing and retrieval of video content.
1092. Generated Image Likelihood Signal (ImageRepositoryGeneratedImageLikelihoodSignal)
      • Description: Contains decisions regarding the likelihood of an image being generated, based on various classification scores.
      • SEO Purpose: Enhances the accuracy of indexing by identifying and handling generated images appropriately.
      • How to Use: Use likelihood signals to differentiate between generated and natural images, ensuring accurate indexing and search results.
1093. Language Identification Result (ImageRepositoryLanguageIdentificationResult)
      • Description: Provides results of language identification for audio content associated with images, including top locales and stripped locales.
      • SEO Purpose: Enhances the indexing and retrieval of multilingual content by providing accurate language identification.
      • How to Use: Use language identification results to manage and index multilingual audio content accurately, improving search relevance.
1094. NIMA Output (ImageRepositoryNimaOutput)
      • Description: Stores NIMA (Neural Image Assessment) scores, reflecting the perceived quality of images.
      • SEO Purpose: Enhances image ranking by providing quality assessments based on NIMA scores.
      • How to Use: Use NIMA scores to prioritize high-quality images in search results, improving user experience and engagement.
1095. S3 Lang ID Signals (ImageRepositoryS3LangIdSignals)
      • Description: Contains language identification signals from the S3 service, aiding in accurate language detection.
      • SEO Purpose: Enhances the indexing and retrieval of multilingual content by providing detailed language signals.
      • How to Use: Use S3 Lang ID signals to manage and index multilingual content accurately, improving search relevance.
1096. Recognizer Metadata Response (ImageRepositoryS3RecognizerMetadataResponse)
      • Description: A trimmed-down version of the recognizer metadata response, used for speech recognition purposes.
      • SEO Purpose: Enhances speech content indexing by providing detailed recognizer metadata.
      • How to Use: Use recognizer metadata to manage and index speech content accurately, improving searchability and retrieval.
1097. Frame-Level Embedding (ImageRepositorySUPFrameLevelEmbedding)
      • Description: Represents embeddings for individual video frames, including the time offset of each frame.
      • SEO Purpose: Enhances the indexing and retrieval of specific video frames by providing detailed embeddings.
      • How to Use: Use frame-level embeddings to manage and index individual frames of video content, improving search accuracy.
1098. Frame-Level Embeddings (ImageRepositorySUPFrameLevelEmbeddings)
      • Description: Contains a list of frame-level embeddings for a video, aiding in detailed analysis and indexing.
      • SEO Purpose: Enhances the indexing and retrieval of video content by providing comprehensive frame-level embeddings.
      • How to Use: Include frame-level embeddings to improve the granularity and accuracy of video indexing and retrieval.
1099. Shopping Product Information (ImageRepositoryShoppingProductInformation)
      • Description: Stores embedding information and localization scores for recognized products in images.
      • SEO Purpose: Enhances e-commerce potential by associating images with relevant product information.
      • How to Use: Use shopping product information to link images with products, improving search relevance and e-commerce opportunities.
1100. Bounding Box (ImageRepositoryShoppingProductInformationBoundingBox)
      • Description: Contains coordinates of the normalized bounding box for recognized products within images.
      • SEO Purpose: Enhances product recognition and indexing by providing detailed bounding box information.
      • How to Use: Use bounding boxes to accurately identify and index product regions within images, improving search precision.
1101. Recognized Entity (ImageRepositoryShoppingProductInformationEntity)
      • Description: Represents recognized entities within images, aiding in detailed content indexing.
      • SEO Purpose: Enhances the contextual understanding and indexing of image content by identifying recognized entities.
      • How to Use: Manage and index recognized entities to improve the relevance and accuracy of image search results.
1102. Product Information (ImageRepositoryShoppingProductInformationProductInformation)
      • Description: Provides detailed information about recognized products in images, including detection scores and category IDs.
      • SEO Purpose: Enhances e-commerce potential by associating images with detailed product information.
      • How to Use: Use product information to link images with products, improving search relevance and e-commerce opportunities.
1103. Product Information Token Group (ImageRepositoryShoppingProductInformationProductInformationTokenGroup)
      • Description: Contains tokens for product retrieval, aiding in accurate and efficient search.
      • SEO Purpose: Enhances the indexing and retrieval of product-related images by providing detailed tokens for search.
      • How to Use: Use token groups to manage and optimize the retrieval of product-related images, improving search relevance.
1104. Versioned Product Information Set (ImageRepositoryShoppingProductInformationVersionedProductInformationSet)
      • Description: Stores product information for different versions of models used in VSS (Vision Shopping Services).
      • SEO Purpose: Enhances product recognition and indexing by providing version-specific product information.
      • How to Use: Use versioned product information to manage and index products accurately, ensuring up-to-date search results.
1105. Speech Recognition Alternative (ImageRepositorySpeechRecognitionAlternative)
      • Description: Stores alternative hypotheses for speech recognition results, aiding in accurate audio content indexing.
      • SEO Purpose: Enhances the indexing and retrieval of speech content by providing multiple recognition alternatives.
      • How to Use: Use speech recognition alternatives to improve the accuracy and relevance of audio content indexing.
1106. Speech Recognition Result (ImageRepositorySpeechRecognitionResult)
      • Description: Represents a speech recognition result for a portion of the audio, aiding in detailed content indexing.
      • SEO Purpose: Enhances the indexing and retrieval of audio content by providing detailed speech recognition results.
      • How to Use: Use speech recognition results to manage and index audio content accurately, improving searchability and retrieval.
1107. Unwanted Content (ImageRepositoryUnwantedContent)
      • Description: Indicates whether the image or video should be deleted from the repository due to legal reasons or hidden from search results.
      • SEO Purpose: Ensures compliance with legal and ethical standards by managing unwanted content.
      • How to Use: Regularly review and manage unwanted content to ensure compliance and maintain the integrity of the content repository.
1108. Venom Processing Info (ImageRepositoryVenomProcessingInfo)
      • Description: Contains status and processing information for videos processed through the Venom system.
      • SEO Purpose: Enhances the management and indexing of video content by providing detailed processing information.
      • How to Use: Use Venom processing info to monitor and manage the status of video content, ensuring accurate indexing and retrieval.
1109. Venom Status (ImageRepositoryVenomStatus)
      • Description: Stores the status and related details of videos processed by Venom, including ACLs, timestamps, and settings.
      • SEO Purpose: Ensures efficient management and retrieval of video content by tracking Venom processing status.
      • How to Use: Monitor and manage Venom status to ensure accurate and up-to-date indexing of video content.
1110. Video Indexing Info (ImageRepositoryVideoIndexingInfo)
      • Description: Contains information related to the indexing of video content, including URLs and crawl status.
      • SEO Purpose: Enhances the indexing and retrieval of video content by providing detailed indexing information.
      • How to Use: Use video indexing info to manage and optimize the indexing of video content, improving search relevance and accuracy.
1111. Video Link Indexing Info (ImageRepositoryVideoLinkIndexingInfo)
      • Description: Provides debugging information related to the crawl status of video links, aiding in accurate indexing.
      • SEO Purpose: Enhances the accuracy and reliability of video indexing by providing detailed crawl status info.
      • How to Use: Monitor and manage video link indexing info to ensure accurate and comprehensive indexing of video content.
1112. Video Previews Debugging Info (ImageRepositoryVideoPreviewsDebuggingInfo)
      • Description: Stores debugging information for video previews, including processing timestamps and engine details.
      • SEO Purpose: Supports the optimization and troubleshooting of video preview processing.
      • How to Use: Use video previews debugging info to diagnose and resolve issues with video previews, ensuring high-quality indexing.
1113. Video Preview (ImageRepositoryVideoPreviewsVideoPreview)
      • Description: Contains actual video preview bytes and associated metadata, aiding in detailed video content analysis.
      • SEO Purpose: Enhances the indexing and retrieval of video content by providing detailed video previews.
      • How to Use: Include video previews to improve the visual representation and indexing of video content, enhancing search relevance.
1114. Video Properties (ImageRepositoryVideoProperties)
      • Description: Stores various properties of video content, including audio-only indicators, metadata, and crawl state.
      • SEO Purpose: Enhances the indexing and retrieval of video content by providing comprehensive video properties.
      • How to Use: Use video properties to manage and index video content accurately, ensuring detailed and relevant search results.
1115. Vertical Indexing Info (ImageRepositoryVideoPropertiesVerticalIndexingInfoVideo)
      • Description: Stores vertical indexing information for video content, aiding in specialized indexing.
      • SEO Purpose: Enhances the relevance and accuracy of video content indexing by providing detailed vertical indexing info.
      • How to Use: Use vertical indexing info to manage and optimize the indexing of video content for specific verticals, improving search results.
1116. Word Info (ImageRepositoryWordInfo)
      • Description: Provides word-specific information for recognized words in audio content, aiding in detailed indexing.
      • SEO Purpose: Enhances the indexing and retrieval of speech content by providing detailed word information.
      • How to Use: Use word info to manage and index speech content accurately, improving searchability and relevance.
1117. YouTube Processing Filter (ImageRepositoryYoutubeProcessingFilter)
      • Description: Stores information related to YouTube processing filters, aiding in video content management.
      • SEO Purpose: Enhances the management and indexing of YouTube content by providing detailed filter information.
      • How to Use: Use YouTube processing filters to manage and optimize the indexing of YouTube content, ensuring relevant search results.
1118. Porn Annotation (ImageSafesearchContentBrainPornAnnotation)
      • Description: Stores annotations related to the detection of pornographic content in images.
      • SEO Purpose: Ensures the safe and appropriate indexing of images by filtering out pornographic content.
      • How to Use: Regularly review porn annotations to refine and improve the accuracy of pornographic content detection.
1119. OCR Annotation (ImageSafesearchContentOCRAnnotation)
      • Description: Stores optical character recognition (OCR) annotations for images, aiding in text extraction and indexing.
      • SEO Purpose: Enhances the indexing and retrieval of text-based content in images by providing OCR annotations.
      • How to Use: Use OCR annotations to extract and index text from images, improving searchability and relevance.
1120. Offensive Symbol Detection (ImageSafesearchContentOffensiveSymbolDetection)
      • Description: Detects and stores information about offensive symbols present in images.
      • SEO Purpose: Ensures the safe and appropriate indexing of images by filtering out content with offensive symbols.
      • How to Use: Regularly review offensive symbol detections to refine and improve the accuracy of content filtering.
1121. Offensive Symbol Match (ImageSafesearchContentOffensiveSymbolMatch)
      • Description: Represents entries for images containing offensive symbols, aiding in detailed content filtering.
      • SEO Purpose: Enhances content safety by accurately identifying and filtering out images with offensive symbols.
      • How to Use: Use offensive symbol matches to manage and filter content, ensuring compliance with safety standards.
1122. Image Indexing Info (ImageSearchImageIndexingInfo)
      • Description: Contains information related to the indexing of images, including selection info and status of non-indexed images.
      • SEO Purpose: Enhances the indexing and retrieval of image content by providing detailed indexing information.
      • How to Use: Use image indexing info to manage and optimize the indexing of images, ensuring accurate and comprehensive search results.
1123. Image License Info (ImageSearchImageLicenseInfo)
      • Description: Stores licensing information for licensable images, aiding in compliance and usage tracking.
      • SEO Purpose: Enhances the management and retrieval of licensable images by providing detailed license information.
      • How to Use: Include image license info to ensure compliance and accurate tracking of image usage, improving search relevance and legal compliance.
1124. Image Selection Info (ImageSearchImageSelectionInfo)
      • Description: Provides information about the selection of images for indexing, including URLs and selection criteria.
      • SEO Purpose: Optimizes the selection of images for indexing, ensuring that the most relevant and high-quality images are included in search results.
      • How to Use: Utilize image selection info to refine the image selection process, focusing on high-quality and relevant images to enhance their visibility in search results.
1125. Unindexed Image Link (ImageSearchUnindexedImageLink)
      • Description: Contains information about image links that are not indexed, including status and reasons for non-indexing.
      • SEO Purpose: Identifies and addresses issues preventing image indexing, ensuring comprehensive content coverage.
      • How to Use: Monitor unindexed image links to troubleshoot and resolve issues, ensuring all relevant images are indexed for improved search visibility.
1126. Indexing Annotation (ImageUnderstandingIndexingAnnotation)
      • Description: Packs various recognition, detection, embedding, and parsing results into a single annotation per bounding box detection.
      • SEO Purpose: Enhances the detailed analysis and indexing of image content by providing comprehensive annotations.
      • How to Use: Use indexing annotations to manage and index image content accurately, ensuring detailed and relevant search results.
1127. Annotation Group (ImageUnderstandingIndexingAnnotationGroup)
      • Description: Contains a group of annotations for various image recognition and detection results.
      • SEO Purpose: Enhances the contextual understanding and indexing of image content by providing grouped annotations.
      • How to Use: Use annotation groups to organize and manage image annotations, improving the accuracy and relevance of search results.
1128. Indexing Feature (ImageUnderstandingIndexingFeature)
      • Description: Represents image feature embeddings, supporting various embedding formats like raw bytes and floating point values.
      • SEO Purpose: Enhances the indexing and retrieval of image content by providing detailed feature embeddings.
      • How to Use: Use indexing features to manage and optimize the indexing of image content, ensuring accurate and relevant search results.
1129. Image Region (ImageUnderstandingIndexingImageRegion)
      • Description: Represents a specific region within an image, produced by a detector, aiding in detailed content analysis.
      • SEO Purpose: Enhances the detailed analysis and indexing of image content by segmenting it into regions.
      • How to Use: Define and manage image regions to provide more granular indexing and improve the relevance of image search results.
1130. Indexing Label (ImageUnderstandingIndexingLabel)
      • Description: Represents a single label with a score and metadata for image content, aiding in detailed indexing.
      • SEO Purpose: Enhances the indexing and retrieval of image content by providing detailed labels and scores.
      • How to Use: Use indexing labels to manage and optimize the indexing of image content, ensuring accurate and relevant search results.
1131. Label Group (ImageUnderstandingIndexingLabelGroup)
      • Description: Contains a set of labels produced by a single model or multiple models, aiding in comprehensive content analysis.
      • SEO Purpose: Enhances the contextual understanding and indexing of image content by providing grouped labels.
      • How to Use: Use label groups to organize and manage image labels, improving the accuracy and relevance of search results.
1132. Indexing Metadata (ImageUnderstandingIndexingMetaData)
      • Description: Provides metadata useful for annotating labels and features with extra information, aiding in detailed content analysis.
      • SEO Purpose: Enhances the indexing and retrieval of image content by providing detailed metadata.
      • How to Use: Use indexing metadata to manage and optimize the indexing of image content, ensuring accurate and relevant search results.
1133. Bad SSL Certificate (IndexingBadSSLCertificate)
      • Description: Stores information about bad SSL certificates for URLs, aiding in security and compliance checks.
      • SEO Purpose: Enhances the security and trustworthiness of indexed content by identifying bad SSL certificates.
      • How to Use: Monitor and manage bad SSL certificates to ensure secure and compliant content indexing, improving user trust and search performance.
1134. Localized Alternate Name (IndexingConverterLocalizedAlternateName)
      • Description: Contains information about localized alternate names for URLs, including annotation sources and device match info.
      • SEO Purpose: Enhances the indexing and retrieval of localized content by providing alternate names.
      • How to Use: Use localized alternate names to improve the relevance and accuracy of search results for localized content.
1135. Raw Redirect Info (IndexingConverterRawRedirectInfo)
      • Description: Stores raw redirect information for URLs, aiding in detailed analysis and indexing.
      • SEO Purpose: Enhances the handling and indexing of redirects by providing detailed raw redirect info.
      • How to Use: Use raw redirect info to manage and optimize the handling of redirects, ensuring accurate and relevant search results.
1136. Redirect Chain (IndexingConverterRedirectChain)
      • Description: Represents the chain of redirects for a URL, aiding in comprehensive redirect analysis.
      • SEO Purpose: Enhances the handling and indexing of redirects by providing a detailed redirect chain.
      • How to Use: Monitor and manage redirect chains to ensure accurate handling of redirects, improving search relevance and accuracy.
1137. Redirect Chain Hop (IndexingConverterRedirectChainHop)
      • Description: Represents a single hop in a redirect chain, aiding in detailed redirect analysis.
      • SEO Purpose: Enhances the handling and indexing of redirects by providing detailed hop information.
      • How to Use: Track redirect chain hops to manage and optimize the handling of redirects, ensuring smooth navigation and accurate search results.
1138. Redirect Parameters (IndexingConverterRedirectParams)
      • Description: Stores characteristics of server or content-based redirects, aiding in detailed analysis and indexing.
      • SEO Purpose: Enhances the handling and indexing of redirects by providing detailed redirect parameters.
      • How to Use: Use redirect parameters to manage and optimize the handling of redirects, ensuring accurate and relevant search results.
1139. Rich Content Data (IndexingConverterRichContentData)
      • Description: Contains information about different versions of document content, aiding in comprehensive content analysis.
      • SEO Purpose: Enhances the indexing and retrieval of rich content by providing detailed content data.
      • How to Use: Use rich content data to manage and optimize the indexing of document content, ensuring accurate and relevant search results.
1140. Rich Content Data Range (IndexingConverterRichContentDataRange)
      • Description: Stores ordered ranges of content from original, processed, and intermediate sources. It ensures that original, processed, and intermediate content can be reconstructed accurately.
      • SEO Purpose: Ensures the integrity and completeness of indexed content by maintaining accurate data ranges for different versions.
      • How to Use: Use this information to manage and verify the integrity of your content versions, ensuring that both original and processed content are indexed accurately.
1141. Robots Info (IndexingConverterRobotsInfo)
      • Description: Encapsulates all information from robots.txt and related sources, including HTTP headers and meta robots tags.
      • SEO Purpose: Manages crawling instructions to search engines, ensuring appropriate indexing and compliance with site preferences.
      • How to Use: Regularly update and monitor robots.txt and related tags to control how search engines index your site content.
1142. Shingle Fingerprint (IndexingConverterShingleFingerprint)
      • Description: Stores fingerprints along with metadata about how the fingerprint was computed, useful for content analysis and identification.
      • SEO Purpose: Helps in detecting duplicate content and ensuring unique content indexing.
      • How to Use: Implement shingle fingerprints to manage and identify duplicate content, enhancing the uniqueness and relevance of indexed content.
1143. Serving Document Identifier (IndexingCrawlerIdServingDocumentIdentifier)
      • Description: Contains identifiers for production documents, ensuring unique identification and managing duplicates.
      • SEO Purpose: Enhances the accuracy of document identification and reduces duplicates in search results.
      • How to Use: Use these identifiers to ensure each document is uniquely identified and properly indexed, avoiding duplicate content issues.
1144. Anchor Phrase Spam Info (IndexingDocjoinerAnchorPhraseSpamInfo)
      • Description: Identifies spikes of spammy anchor phrases, tagging them for demotion in search results.
      • SEO Purpose: Improves search quality by detecting and managing spammy anchor phrases.
      • How to Use: Monitor and manage anchor phrases to identify and reduce spam, enhancing the quality of search results.
1145. Anchor Spam Info (IndexingDocjoinerAnchorSpamInfo)
      • Description: Summarizes outputs of spam penalization algorithms, tagging spammy anchors for demotion.
      • SEO Purpose: Enhances search result quality by filtering out spammy anchors.
      • How to Use: Use this information to identify and penalize spammy anchors, maintaining high-quality search results.
1146. Anchor Statistics (IndexingDocjoinerAnchorStatistics)
      • Description: Provides statistics of anchors in a document, including counts and timestamps.
      • SEO Purpose: Helps in analyzing and understanding anchor usage and its impact on search rankings.
      • How to Use: Use anchor statistics to monitor and optimize anchor usage, ensuring effective link building and search visibility.
1147. Anchor Statistics Per Dup Stats (IndexingDocjoinerAnchorStatisticsPerDupStats)
      • Description: Tracks the total number of anchors per duplicate, including redundant and off-domain counts.
      • SEO Purpose: Manages duplicate content by analyzing anchor statistics.
      • How to Use: Use these statistics to identify and manage duplicate anchors, enhancing the relevance and uniqueness of content.
1148. Redundant Anchor Info (IndexingDocjoinerAnchorStatisticsRedundantAnchorInfo)
      • Description: Tracks the number of redundant anchors dropped per domain and text pair.
      • SEO Purpose: Improves search quality by reducing redundant anchors.
      • How to Use: Monitor and reduce redundant anchors to improve content relevance and search ranking.
1149. Redundant Anchor Info for Phrase Cap (IndexingDocjoinerAnchorStatisticsRedundantAnchorInfoForPhraseCap)
      • Description: Details the anchors dropped due to redundancy for specific phrases and domains.
      • SEO Purpose: Enhances search quality by managing redundant anchor phrases.
      • How to Use: Review and manage redundant anchor phrases to improve content relevance and search performance.
1150. Trusted Anchor Info (IndexingDocjoinerAnchorTrustedInfo)
      • Description: Summarizes anchors from trusted sites.
      • SEO Purpose: Enhances trust and relevance in search results by prioritizing trusted site anchors.
      • How to Use: Leverage trusted anchor info to boost the visibility and ranking of content from reputable sources.
1151. CDoc Build Info (IndexingDocjoinerCDocBuildInfo)
      • Description: Holds additional information for building the final composite document (CDoc).
      • SEO Purpose: Ensures comprehensive and accurate document building for indexing.
      • How to Use: Use CDoc build info to manage and optimize the construction of composite documents for accurate indexing.
1152. Data Version (IndexingDocjoinerDataVersion)
      • Description: Tracks the version of data in CompositeDoc, including version strings and timestamps for various data types.
      • SEO Purpose: Maintains the accuracy and currency of indexed data by tracking data versions.
      • How to Use: Use data version tracking to ensure your indexed data is up-to-date and accurately reflects the latest information.
1153. Version Info (IndexingDocjoinerDataVersionVersionInfo)
      • Description: Provides version information for specific data, including timestamps and human-readable versions.
      • SEO Purpose: Enhances data management and accuracy by providing detailed version information.
      • How to Use: Monitor and manage version info to maintain accurate and current data in your indexed content.
1154. Serving Time Cluster ID (IndexingDocjoinerServingTimeClusterId)
      • Description: Contains metadata about serving time clusters, used to group similar content for search result de-duplication.
      • SEO Purpose: Improves search result quality by de-duplicating similar content.
      • How to Use: Use serving time cluster IDs to manage and de-duplicate similar content, ensuring unique and relevant search results.
1155. Serving Time Cluster IDs (IndexingDocjoinerServingTimeClusterIds)
      • Description: Contains a set of cluster IDs for de-duplication at serving time, based on various properties.
      • SEO Purpose: Enhances search result quality by providing comprehensive de-duplication.
      • How to Use: Utilize serving time cluster IDs to manage and optimize content de-duplication, improving search relevance.
1156. Localized Alternate Names Locale Entry (IndexingDupsComputedLocalizedAlternateNamesLocaleEntry)
      • Description: Stores alternate names for localized content, including cluster IDs and language codes.
      • SEO Purpose: Improves the indexing and retrieval of localized content by providing alternate names.
      • How to Use: Use localized alternate names to enhance the relevance and accuracy of localized content in search results.
1157. Localized Cluster (IndexingDupsLocalizedLocalizedCluster)
      • Description: Represents localized clusters of content, including language and region-specific variations.
      • SEO Purpose: Enhances the indexing and retrieval of localized content by grouping similar content into clusters.
      • How to Use: Use localized clusters to manage and optimize the indexing of localized content, ensuring accurate and relevant search results.
1158. Localized Cluster Cluster (IndexingDupsLocalizedLocalizedClusterCluster)
      • Description: Contains information about individual clusters within a localized cluster, including cluster IDs and types.
      • SEO Purpose: Improves the organization and retrieval of localized content by providing detailed cluster information.
      • How to Use: Utilize cluster information to manage and optimize the indexing of localized content, enhancing search relevance.
1159. Localized Cluster Link-Based Info (IndexingDupsLocalizedLocalizedClusterLinkBasedClusterInfo)
      • Description: Stores meta-information about link-based clusters, useful for older documents.
      • SEO Purpose: Enhances the understanding and management of link-based clusters in older content.
      • How to Use: Review and manage link-based cluster information to ensure accurate indexing of older documents.
1160. Link-Based Cluster Info Link Data (IndexingDupsLocalizedLocalizedClusterLinkBasedClusterInfoLinkData)
      • Description: Provides details about links within a cluster, including URLs and timestamps.
      • SEO Purpose: Enhances link management and indexing by providing detailed link information.
      • How to Use: Use link data to manage and optimize the indexing of links within clusters, improving search accuracy.
1161. Link-Based Cluster Info Link Member (IndexingDupsLocalizedLocalizedClusterLinkBasedClusterInfoLinkMember)
      • Description: Contains information about individual link members within a cluster, including URLs and languages.
      • SEO Purpose: Enhances link management and indexing by providing detailed link member information.
      • How to Use: Use link member info to manage and optimize the indexing of links within clusters, improving search accuracy.
1162. Localized Cluster Target Link (IndexingDupsLocalizedLocalizedClusterTargetLink)
      • Description: Contains information about localized URLs linked from a document in a localized variation context.
      • SEO Purpose: Enhances the indexing and retrieval of localized content by providing target link information.
      • How to Use: Use target link info to manage and optimize the indexing of localized content, ensuring accurate and relevant search results.
1163. Target Link Link (IndexingDupsLocalizedLocalizedClusterTargetLinkLink)
      • Description: Provides basic information about target links, including URLs and language codes.
      • SEO Purpose: Enhances link management and indexing by providing detailed target link information.
      • How to Use: Use target link info to manage and optimize the indexing of links, improving search accuracy and relevance.
1164. Target Link Annotation Source Info (IndexingDupsLocalizedLocalizedClusterTargetLinkLinkAnnotationSourceInfo)
      • Description: Describes the source of link annotations, including discovery and language annotation details.
      • SEO Purpose: Enhances the understanding and management of link annotations by providing detailed source info.
      • How to Use: Use annotation source info to manage and optimize the indexing of link annotations, improving search relevance.
1165. Target Link Metadata (IndexingDupsLocalizedLocalizedClusterTargetLinkMetadata)
      • Description: Provides metadata about target links, including validation timestamps and first-seen dates.
      • SEO Purpose: Enhances link management and indexing by providing detailed metadata.
      • How to Use: Use target link metadata to manage and optimize the indexing of links, ensuring accurate and relevant search results.
1166. Target Link Sets (IndexingDupsLocalizedLocalizedClusterTargetLinkSets)
      • Description: Contains sets of direct and indirect target links, providing comprehensive link information.
      • SEO Purpose: Enhances link management and indexing by providing detailed link sets.
      • How to Use: Use link sets to manage and optimize the indexing of links, improving search accuracy and relevance.
1167. Target Doc Data (IndexingDupsLocalizedLocalizedClusterTargetLinkTargetDocData)
      • Description: Provides information about URLs being validated, aiding in detailed content analysis.
      • SEO Purpose: Enhances the indexing and retrieval of content by providing detailed target document data.
      • How to Use: Use target doc data to manage and optimize the indexing of content, ensuring accurate and relevant search results.
1168. Embedded Content Info (IndexingEmbeddedContentEmbeddedContentInfo)
      • Description: Used to pass data between components and store embedded content output in documents.
      • SEO Purpose: Enhances content richness and indexing by integrating embedded content.
      • How to Use: Use embedded content info to manage and optimize the inclusion of embedded content, improving content richness and search relevance.
1169. Embedded Links Info (IndexingEmbeddedContentEmbeddedLinksInfo)
      • Description: Provides information about embedded links, including page size and uncrawled link URLs.
      • SEO Purpose: Enhances the indexing and management of embedded links by providing detailed information.
      • How to Use: Use embedded links info to manage and optimize the indexing of embedded links, ensuring accurate and relevant search results.
1170. Embedder Info (IndexingEmbeddedContentEmbedderInfo)
      • Description: Contains information about the importance of an embedder and associated link info.
      • SEO Purpose: Enhances the management and indexing of embedded content by providing detailed embedder information.
      • How to Use: Use embedder info to manage and optimize the inclusion of embedded content, improving content richness and search relevance.
1171. Fetch Host Count (IndexingEmbeddedContentFetchHostCount)
      • Description: Logs the number of URLs fetched per host during rendering.
      • SEO Purpose: Enhances the understanding and management of fetching activities by providing host count information.
      • How to Use: Use fetch host count to monitor and optimize fetching activities, ensuring efficient content rendering and indexing.
1172. Fetch Host Count Counter (IndexingEmbeddedContentFetchHostCountCounter)
      • Description: Contains counters for URLs fetched per host, aiding in detailed fetching analysis.
      • SEO Purpose: Enhances the understanding and management of fetching activities by providing detailed counters.
      • How to Use: Use host count counters to monitor and optimize fetching activities, ensuring efficient content rendering and indexing.
1173. Fetch URL Response Metadata (IndexingEmbeddedContentFetchUrlResponseMetadata)
      • Description: Encapsulates metadata annotated from fetch server responses, aiding in content processing.
      • SEO Purpose: Enhances the understanding and management of fetched content by providing detailed response metadata.
      • How to Use: Use fetch URL response metadata to manage and optimize the processing of fetched content, ensuring accurate and efficient indexing.
1174. Embedded Content Link Info (IndexingEmbeddedContentLinkInfo)
      • Description: Provides information about one embedded link, aiding in detailed content analysis.
      • SEO Purpose: Enhances the indexing and management of embedded links by providing detailed information.
      • How to Use: Use embedded link info to manage and optimize the inclusion of embedded links, improving content richness and search relevance.
1175. Output Generation Timestamps (IndexingEmbeddedContentOutputGenerationTimestamps)
      • Description: Logs the Unix timestamps for the generation of output fields, used to control update frequency.
      • SEO Purpose: Enhances content management and efficiency by providing detailed generation timestamps.
      • How to Use: Use output generation timestamps to manage and optimize the generation of content fields, ensuring efficient updates and accurate indexing.
1176. Page Size Info (IndexingEmbeddedContentPageSizeInfo)
      • Description: Provides information about page download sizes, aiding in content analysis.
      • SEO Purpose: Enhances the understanding and management of page sizes by providing detailed information.
      • How to Use: Use page size info to monitor and optimize page download sizes, ensuring efficient content rendering and indexing.
1177. Render Cache Stats (IndexingEmbeddedContentRenderCacheStats)
      • Description: Tracks cache usage in the rendering microservice, aiding in performance analysis.
      • SEO Purpose: Enhances rendering performance by providing detailed cache statistics.
      • How to Use: Use render cache stats to monitor and optimize cache usage, ensuring efficient content rendering and indexing.
1178. Render Request Config Params (IndexingEmbeddedContentRenderRequestConfigConfigParams)
      • Description: Contains configuration parameters for rendering requests, aiding in detailed rendering analysis.
      • SEO Purpose: Enhances the management and optimization of rendering requests by providing detailed config parameters.
      • How to Use: Use render request config params to manage and optimize rendering requests, ensuring efficient content rendering and indexing.
1179. Rendering Fetch Stats (IndexingEmbeddedContentRenderingFetchStats)
      • Description: Provides fetch stats during rendering, aiding in performance analysis.
      • SEO Purpose: Enhances rendering performance by providing detailed fetch statistics.
      • How to Use: Use rendering fetch stats to monitor and optimize fetching activities during rendering, ensuring efficient content rendering and indexing.
1180. Rendering Output Metadata (IndexingEmbeddedContentRenderingOutputMetadata)
      • Description: Stores small values from rendering output, aiding in content analysis.
      • SEO Purpose: Enhances the understanding and management of rendering outputs by providing detailed metadata.
      • How to Use: Use rendering output metadata to manage and optimize rendering activities, ensuring accurate and efficient content rendering and indexing.
1181. Content Selection Result (IndexingEmbeddedContentSelectionResult)
      • Description: Indicates that a URL should be included in the corpus, aiding in content selection.
      • SEO Purpose: Enhances content selection and indexing by providing detailed selection results.
      • How to Use: Use selection results to manage and optimize the inclusion of URLs in the content corpus, ensuring accurate and relevant search results.
1182. Vertical Item (IndexingMlVerticalVerticalItem)
      • Description: Represents an item in a vertical, including ID, name, and probability.
      • SEO Purpose: Enhances the organization and retrieval of vertical content by providing detailed item information.
      • How to Use: Use vertical items to manage and optimize the indexing of vertical content, ensuring accurate and relevant search results.
1183. Desktop Interstitials (IndexingMobileInterstitialsProtoDesktopInterstitials)
      • Description: Contains signals for desktop interstitials, including site-level signal lookup and attachment details.
      • SEO Purpose: Enhances the understanding and management of desktop interstitials by providing detailed signals.
      • How to Use: Use desktop interstitials to monitor and manage interstitials, ensuring compliance with search guidelines and improving user experience.
1184. Desktop Interstitials Details (IndexingMobileInterstitialsProtoDesktopInterstitialsDetails)
      • Description: Optionally contains details of the signals computation for desktop interstitials.
      • SEO Purpose: Enhances the understanding and management of desktop interstitials by providing detailed computation details.
      • How to Use: Use interstitials details to analyze and optimize interstitial signals, ensuring compliance with search guidelines and improving user experience.
1185. Interstitial Basic Info (IndexingMobileInterstitialsProtoInterstitialBasicInfo)
      • Description: Provides basic information about interstitials, shared by all layout types.
      • SEO Purpose: Enhances the understanding and management of interstitials by providing basic information.
      • How to Use: Use interstitial basic info to quickly iterate through detected interstitials, ensuring efficient analysis and compliance with search guidelines.
1186. Core Web Vitals (IndexingMobileVoltCoreWebVitals)
      • Description: Contains Core Web Vitals metrics from UKM data, aiding in performance analysis.
      • SEO Purpose: Enhances the understanding and optimization of web performance by providing Core Web Vitals metrics.
      • How to Use: Use Core Web Vitals to monitor and improve web performance, ensuring a better user experience and improved search rankings.
1187. Volt Per Doc Data (IndexingMobileVoltVoltPerDocData)
      • Description: Stores data for VOLT, used for ranking changes, including Core Web Vitals and secure signals.
      • SEO Purpose: Enhances the understanding and management of ranking factors by providing detailed VOLT data.
      • How to Use: Use Volt Per Doc Data to manage and optimize ranking changes, ensuring accurate and relevant search results.
1188. Access Requirements (IndexingPrivacyAccessAccessRequirements)
      • Description: Contains restriction categories for accessing content, aiding in compliance and content management.
      • SEO Purpose: Enhances content compliance and management by providing detailed access requirements.
      • How to Use: Use access requirements to manage and enforce content restrictions, ensuring compliance and accurate indexing.
1189. Adaptive Interval Data (IndexingSignalAggregatorAdaptiveIntervalData)
      • Description: This data stores the state for the Adaptive Frequency Estimator. It includes details on how frequently data should be updated based on past performance and trends.
      • SEO Purpose: Helps in determining optimal intervals for data updates, ensuring that the content is refreshed at the right frequency to maintain relevance and accuracy.
      • How to Use: Use this data to set and adjust the frequency of content updates. Analyze the state data to understand how often your content needs to be refreshed to stay competitive in search rankings.
1190. Age-Weighted Coverage Data (IndexingSignalAggregatorAgeWeightedCoverageData)
      • Description: Accumulates coverage data for a URL over time using a constant half-life time. This helps in understanding how the value of content changes as it ages.
      • SEO Purpose: Provides insights into the long-term performance and relevance of content, allowing for better lifecycle management.
      • How to Use: Monitor the age-weighted coverage data to identify content that may need updating or retiring. Use this information to prioritize updates for older content that still attracts traffic.
1191. Aggregated Score (IndexingSignalAggregatorAggregatedScore)
      • Description: Represents the aggregated signal used by the Numeric Signal Aggregator, which combines multiple signals into a single score.
      • SEO Purpose: Offers a comprehensive score that reflects various performance metrics, simplifying the analysis of content effectiveness.
      • How to Use: Utilize the aggregated score to evaluate the overall performance of your content. Use this score to compare different pieces of content and identify areas for improvement.
1192. Running Mean and Variance Internal State (IndexingSignalAggregatorRunningMeanAndVarianceInternalState)
      • Description: Stores the internal state of the West & Chan running variance algorithm, which is used to calculate the mean and variance of data points.
      • SEO Purpose: Helps in understanding the statistical stability and variability of content performance metrics.
      • How to Use: Use this data to analyze the consistency of your content’s performance. Identify content with high variability and investigate potential causes.
1193. SCC Data (IndexingSignalAggregatorSccData)
      • Description: Contains parent pattern and most immediate pattern data for SCC signals, which track click patterns and other interactions.
      • SEO Purpose: Provides insights into user interaction patterns, helping to optimize content layout and navigation.
      • How to Use: Analyze SCC data to understand how users interact with your content. Use this information to improve the user experience and increase engagement.
1194. SCC Signal (IndexingSignalAggregatorSccSignal)
      • Description: Includes detailed information on clicks, debug info, and the number of URLs with specific types of clicks.
      • SEO Purpose: Helps in detailed analysis of click patterns, which can inform content optimization strategies.
      • How to Use: Use SCC signal data to identify popular content and navigation paths. Optimize less popular areas to improve overall site performance.
1195. Url Pattern Signals (IndexingSignalAggregatorUrlPatternSignals)
      • Description: Contains signals necessary for per-URL click prediction, used in scoring for index selection.
      • SEO Purpose: Enhances the ability to predict user clicks, leading to better content ranking and visibility.
      • How to Use: Implement URL pattern signals to improve your content scoring models. Use this data to refine your prediction algorithms for better search performance.
1196. Url Pattern Signals Prior Signal (IndexingSignalAggregatorUrlPatternSignalsPriorSignal)
      • Description: Provides a container for various signals used in scoring, allowing for extension beyond basic pattern scores.
      • SEO Purpose: Offers flexibility in scoring models by incorporating a wide range of signals.
      • How to Use: Use prior signals to develop more robust scoring models. Incorporate diverse data points to enhance content evaluation and ranking.
1197. Url Score (IndexingSignalAggregatorUrlScore)
      • Description: Represents the numeric signal associated with a URL, which is used for scoring and ranking.
      • SEO Purpose: Provides a quantifiable measure of a URL’s performance, aiding in ranking decisions.
      • How to Use: Use URL scores to compare and rank different pieces of content. Prioritize optimization efforts based on these scores to improve search rankings.
1198. Speech Properties (IndexingSpeechSpeechPropertiesProto)
      • Description: Contains information about the spoken content based solely on the media resource.
      • SEO Purpose: Enhances the indexing and retrieval of spoken content by providing detailed speech properties.
      • How to Use: Use speech properties data to optimize the indexing of audio and video content. Ensure that spoken words are accurately captured and indexed to improve search relevance.
1199. URL Tree Big Tree Branch (IndexingUrlPatternUrlTreeBigTreeBranch)
      • Description: Represents a major branch of the URL tree, aiding in the structural analysis of site content.
      • SEO Purpose: Helps in understanding and managing the hierarchical structure of site content.
      • How to Use: Use URL tree branches to visualize and manage your site’s content structure. Optimize the organization of content to improve navigation and search indexing.
1200. URL Feature (IndexingUrlPatternUrlTreeUrlFeature)
      • Description: Contains details about specific URL features, including fingerprints and groupings.
      • SEO Purpose: Enhances the analysis of URL patterns by providing detailed feature information.
      • How to Use: Use URL feature data to identify and optimize common URL patterns. Improve the consistency and structure of your URLs to enhance search performance.
1201. URL Features (IndexingUrlPatternUrlTreeUrlFeatures)
      • Description: Contains a list of features for URLs, aiding in detailed pattern analysis.
      • SEO Purpose: Helps in comprehensive analysis of URL patterns and their impact on search performance.
      • How to Use: Analyze URL features to identify common patterns and optimize them for better search indexing.
1202. URL Tree (IndexingUrlPatternUrlTreeUrlTree)
      • Description: Stores detailed information about the URL tree, including nodes, branches, and timestamps.
      • SEO Purpose: Enhances the understanding and management of the site’s URL structure.
      • How to Use: Use URL tree data to visualize and optimize your site’s structure. Ensure that the URL hierarchy is logical and easy to navigate.
1203. URL Tree Debug Info (IndexingUrlPatternUrlTreeUrlTreeDebugInfo)
      • Description: Provides debugging information for the URL tree, aiding in the identification of structural issues.
      • SEO Purpose: Helps in troubleshooting and optimizing the site’s URL structure.
      • How to Use: Use debug info to identify and fix issues in your URL structure. Ensure that the URL tree is properly organized and free of errors.
1204. URL Tree Key (IndexingUrlPatternUrlTreeUrlTreeKey)
      • Description: A unique identifier for the URL tree, used for hashing and equality functions.
      • SEO Purpose: Provides a reliable way to identify and manage different parts of the URL tree.
      • How to Use: Use URL tree keys to manage and differentiate between various sections of your site’s URL structure. Optimize these keys for efficient indexing and retrieval.
1205. URL Tree Node (IndexingUrlPatternUrlTreeUrlTreeNode)
      • Description: Represents a node in the URL tree, including parent and child relationships.
      • SEO Purpose: Enhances the understanding and management of the site’s hierarchical URL structure.
      • How to Use: Use URL tree nodes to visualize and manage the relationships between different parts of your site. Optimize the structure to improve navigation and search performance.
1206. ASR Transcript Repair Annotation (IndexingVideosAsrTranscriptRepairAnnotation)
      • Description: Captures the output of analyses on Automatic Speech Recognition (ASR) transcripts.
      • SEO Purpose: Enhances the accuracy and reliability of ASR transcripts, improving the indexing of spoken content.
      • How to Use: Use ASR transcript repair annotations to refine and correct speech recognition outputs. Ensure that spoken content is accurately captured and indexed.
1207. Kaltix Per Doc Data (KaltixPerDocData)
      • Description: Stores Kaltix rank data for documents, including overall, local, and site-specific ranks.
      • SEO Purpose: Provides detailed ranking information to help prioritize content optimization efforts.
      • How to Use: Use Kaltix data to understand the ranking performance of your content. Focus on improving lower-ranked content to boost overall site performance.
1208. Typed Regions (KeGovernanceTypedRegions)
      • Description: Contains a list of regions and their corresponding types for data governance purposes.
      • SEO Purpose: Helps in managing data governance by categorizing regions and their types.
      • How to Use: Use typed regions to ensure compliance with data governance policies. Organize and manage your content based on regional requirements.
1209. Any Type (KnowledgeAnswersAnyType)
      • Description: Accepts any non-empty value, intended for special cases allowing any value to be valid.
      • SEO Purpose: Provides flexibility in data types, allowing for more versatile content management.
      • How to Use: Use any type for special cases where the data type may vary. Ensure that the content is properly validated and formatted.
1210. Attribute Type (KnowledgeAnswersAttributeType)
      • Description: Configures a value intended to be an attribute defined in the schema.
      • SEO Purpose: Enhances schema management by defining specific attributes.
      • How to Use: Use attribute types to ensure that content attributes are properly defined and managed according to the schema.
1211. Boolean Type (KnowledgeAnswersBooleanType)
      • Description: Configures a yes/no value, aiding in the definition of binary attributes.
      • SEO Purpose: Simplifies the management of binary attributes by clearly defining them as yes/no values.
      • How to Use: Use boolean types for attributes that have binary outcomes. Ensure that these attributes are consistently applied across your content.
1212. Collection Type (KnowledgeAnswersCollectionType)
      • Description: Configures a value intended to be a collection, supporting the grouping of related items.
      • SEO Purpose: Enhances content organization by allowing related items to be grouped together.
      • How to Use: Use collection types to manage groups of related content. Ensure that collections are properly defined and maintained.
1213. Compound Type (KnowledgeAnswersCompoundType)
      • Description: Configures a value composed of multiple answer values, supporting complex data structures.
      • SEO Purpose: Allows for the management of complex content structures by defining compound types.
      • How to Use: Use compound types for content that involves multiple related values. Ensure that these structures are properly defined and managed.
1214. Container Type (KnowledgeAnswersContainerType)
      • Description: Configures a value that contains multiple slots, supporting complex data organizations.
      • SEO Purpose: Enhances the management of complex data by defining containers with multiple slots.
      • How to Use: Use container types to manage complex content structures. Ensure that containers are properly defined and organized.
1215. Date Type (KnowledgeAnswersDateType)
      • Description: Configures a value intended to be a date, supporting date-specific content.
      • SEO Purpose: Simplifies the management of date-specific content by clearly defining date values.
      • How to Use: Use date types for attributes that involve dates. Ensure that dates are consistently formatted and managed.
1216. Dependency Type (KnowledgeAnswersDependencyType)
      • Description: Contains data about contracts and remodelings for value types, aiding in schema management.
      • SEO Purpose: Enhances schema management by providing detailed dependency information.
      • How to Use: Use dependency types to manage the relationships between different schema elements. Ensure that dependencies are properly defined and maintained.
1217. Dialog Referential Resolution (KnowledgeAnswersDialogReferentialResolution)
      • Description: Captures how data was resolved through external data, supporting dialog and query contexts.
      • SEO Purpose: Enhances the understanding of dialog contexts by capturing referential resolutions.
      • How to Use: Use dialog referential resolution to manage the context and flow of dialogs. Ensure that references are properly resolved and captured.
1218. Duration Type (KnowledgeAnswersDurationType)
      • Description: Configures a value intended to be a duration, supporting time-specific content.
      • SEO Purpose: Simplifies the management of duration-specific content by clearly defining duration values.
      • How to Use: Use duration types for attributes that involve time durations. Ensure that durations are consistently formatted and managed.
1219. Entity Type (KnowledgeAnswersEntityType)
      • Description: Configures a value intended to be an entity, supporting the management of entity-specific content.
      • SEO Purpose: Enhances the management of entity-specific content by clearly defining entity values.
      • How to Use: Use entity types for attributes that involve specific entities. Ensure that entities are properly defined and managed.
1220. Facet Parsing (KnowledgeAnswersFacetParsing)
      • Description: Constructs how to parse a facet from neural or lexical models, supporting complex parsing scenarios.
      • SEO Purpose: Enhances content parsing by providing detailed facet parsing instructions.
      • How to Use: Use facet parsing to manage complex parsing scenarios. Ensure that facets are properly parsed and captured.
1221. Intent Modifiers (KnowledgeAnswersIntentModifiers)
      • Description: Modifies a meaning expression with signals that depend on grammar and syntax, supporting intent resolution.
      • SEO Purpose: Enhances intent resolution by providing detailed intent modifiers.
      • How to Use: Use intent modifiers to manage and refine intent resolution. Ensure that modifiers are properly applied and managed.
1222. Intent Query Annotation Layer Signals (KnowledgeAnswersIntentQueryAnnotationLayerSignals)
      • Description: Captures signals from the annotation layer, supporting query annotation.
      • SEO Purpose: Enhances query annotation by providing detailed signals from the annotation layer.
      • How to Use: Use annotation layer signals to manage and refine query annotations. Ensure that signals are properly captured and applied.
1223. Intent Query Arg Path (KnowledgeAnswersIntentQueryArgPath)
      • Description: Represents a path to a specific argument in a function call, supporting complex query structures.
      • SEO Purpose: Enhances query management by providing detailed paths to specific arguments.
      • How to Use: Use argument paths to manage complex query structures. Ensure that paths are properly defined and followed.
1224. Intent Query Arg Path Component (KnowledgeAnswersIntentQueryArgPathComponent)
      • Description: Represents a component of an argument path, aiding in the definition of complex query structures.
      • SEO Purpose: Enhances query management by providing detailed components for argument paths.
      • How to Use: Use argument path components to build and manage complex query structures. Ensure that components are properly defined and organized.
1225. Intent Query Argument (KnowledgeAnswersIntentQueryArgument)
      • Description: Represents a function argument, supporting detailed query management.
      • SEO Purpose: Enhances query management by providing detailed function arguments.
      • How to Use: Use function arguments to define and manage queries. Ensure that arguments are properly defined and captured.
1226. Intent Query Argument Provenance (KnowledgeAnswersIntentQueryArgumentProvenance)
      • Description: Captures the provenance of a function argument, supporting detailed query management.
      • SEO Purpose: Enhances query management by providing detailed provenance for function arguments.
      • How to Use: Use argument provenance to track and manage the origins of query arguments. Ensure that provenance is properly captured and maintained.
1227. Intent Query Argument Signals (KnowledgeAnswersIntentQueryArgumentSignals)
      • Description: Represents the signals associated with a function argument, aiding in query management.
      • SEO Purpose: Enhances query management by providing detailed signals for function arguments.
      • How to Use: Use argument signals to manage and refine query arguments. Ensure that signals are properly captured and applied.
1228. Intent Query Argument Value (KnowledgeAnswersIntentQueryArgumentValue)
      • Description: Represents the value of a function argument, supporting detailed query management.
      • SEO Purpose: Enhances query management by providing detailed values for function arguments.
      • How to Use: Use argument values to define and manage queries. Ensure that values are properly defined and captured.
1229. Attribute Signal (KnowledgeAnswersIntentQueryAttributeSignal)
      • Description: Contains an attribute ID and its completion score, aiding in the management of attribute signals.
      • SEO Purpose: Enhances attribute management by providing detailed attribute signals.
      • How to Use: Use attribute signals to manage and refine attribute data. Ensure that signals are properly captured and applied.
1230. Collection Membership (KnowledgeAnswersIntentQueryCollectionMembership)
      • Description: Represents the membership of an entity in a collection, supporting detailed content organization.
      • SEO Purpose: Enhances content organization by providing detailed collection membership information.
      • How to Use: Use collection membership to manage and organize entities within collections. Ensure that membership data is properly captured and maintained.
1231. Collection Score (KnowledgeAnswersIntentQueryCollectionScore)
      • Description: Represents the score of a collection, aiding in the evaluation and ranking of collections.
      • SEO Purpose: Enhances content evaluation by providing detailed collection scores.
      • How to Use: Use collection scores to evaluate and rank different collections. Ensure that scores are properly calculated and applied.
1232. Concept Info (KnowledgeAnswersIntentQueryConceptInfo)
      • Description: Provides meaning semantics captured in a continuous space, supporting detailed content analysis.
      • SEO Purpose: Enhances content analysis by providing detailed concept information.
      • How to Use: Use concept info to analyze and understand the meaning semantics of your content. Ensure that concepts are properly captured and applied.
1233. Concept Signals (KnowledgeAnswersIntentQueryConceptSignals)
      • Description: Captures signal data for associated concepts, aiding in detailed content analysis.
      • SEO Purpose: Enhances content analysis by providing detailed concept signals.
      • How to Use: Use concept signals to analyze and refine your content. Ensure that signals are properly captured and applied.
1234. Coreference (KnowledgeAnswersIntentQueryCoreference)
      • Description: Represents a coreferenced value defined elsewhere, supporting complex content structures.
      • SEO Purpose: Enhances content management by providing detailed coreference information.
      • How to Use: Use coreference to manage complex content structures. Ensure that coreferences are properly defined and captured.
1235. Custom Vehicle Action Argument Annotator Signals (KnowledgeAnswersIntentQueryCustomVehicleActionArgumentAnnotatorSignals)
      • Description: Captures signals associated with custom vehicle action annotations, aiding in detailed content analysis.
      • SEO Purpose: Enhances content analysis by providing detailed signals for custom vehicle actions.
      • How to Use: Use custom vehicle action signals to analyze and refine your content. Ensure that signals are properly captured and applied.
1236. Freetext Annotation Signals (KnowledgeAnswersIntentQueryFreetextAnnotationSignals)
      • Description: Captures signals associated with freetext annotations, supporting detailed content analysis.
      • SEO Purpose: Enhances content analysis by providing detailed freetext annotation signals.
      • How to Use: Use freetext annotation signals to manage and refine your content. Ensure that signals are properly captured and applied.
1237. Function Call (KnowledgeAnswersIntentQueryFunctionCall)
      • Description: Represents the function call of an answers intent query, supporting detailed query management.
      • SEO Purpose: Enhances query management by providing detailed function call information.
      • How to Use: Use function calls to define and manage queries. Ensure that function calls are properly captured and maintained.
1238. Function Call Signals (KnowledgeAnswersIntentQueryFunctionCallSignals)
      • Description: Captures signals associated with function calls, aiding in detailed query management.
      • SEO Purpose: Enhances query management by providing detailed function call signals.
      • How to Use: Use function call signals to manage and refine your queries. Ensure that signals are properly captured and applied.
1239. Grounding Signals (KnowledgeAnswersIntentQueryGroundingSignals)
      • Description: Captures grounding-related signals, supporting detailed content analysis.
      • SEO Purpose: Enhances content analysis by providing detailed grounding signals.
      • How to Use: Use grounding signals to analyze and refine your content. Ensure that signals are properly captured and applied.
1240. Identifier (KnowledgeAnswersIntentQueryIdentifier)
      • Description: Represents a reference to a specific entity of a specified type, supporting detailed content management.
      • SEO Purpose: Enhances content management by providing detailed entity references.
      • How to Use: Use identifiers to manage and organize your content. Ensure that references are properly captured and maintained.
1241. Implied Entity Signals (KnowledgeAnswersIntentQueryImpliedEntity)
      • Description: This ranking factor captures signals for entities implied in user queries that are merged into entity arguments during parsing.
      • SEO Purpose: Helps in understanding and accurately parsing implied entities within user queries, improving the relevance of search results.
      • How to Use: Ensure that your content includes clear references to related entities, as this helps the algorithm to better parse and merge implied entities.
1242. IQL Attachment (KnowledgeAnswersIntentQueryIndexingIQLAttachment)
      • Description: Encodes IQL (Intent Query Language) expressions annotated by various applications, used for prototypes and page-level intents.
      • SEO Purpose: Enhances the indexing and understanding of page-level intents and compound entity representations.
      • How to Use: Utilize structured data and clear intent expressions in your content to benefit from enhanced indexing and query understanding.
1243. Local Result Signals (KnowledgeAnswersIntentQueryLocalResultSignals)
      • Description: Stores signals relating to local search results, aiding in local intent deduplication and conformance.
      • SEO Purpose: Improves local search results by leveraging detailed signals related to local intent.
      • How to Use: Optimize your local content with accurate and comprehensive information to enhance visibility in local search results.
1244. Local Signals (KnowledgeAnswersIntentQueryLocalSignals)
      • Description: Contains information about local results to be used in the Packer for deduplication and conformance.
      • SEO Purpose: Ensures that local search results are accurately represented and not duplicated, enhancing the quality of local search results.
      • How to Use: Ensure your local listings are unique and well-detailed to avoid being flagged as duplicate content.
1245. Location Markers Signals (KnowledgeAnswersIntentQueryLocationMarkersSignals)
      • Description: Provides semantics for the span extension of arguments to include markers like FROM or TO in queries.
      • SEO Purpose: Enhances the understanding of location-based queries by accurately interpreting location markers.
      • How to Use: Include clear and precise location markers in your content to improve the relevance of search results for location-based queries.
1246. Media Entity Signals (KnowledgeAnswersIntentQueryMediaEntitySignals)
      • Description: Contains signals about media entities, aiding in the understanding and indexing of media-related content.
      • SEO Purpose: Enhances the searchability of media content by providing detailed signals about media entities.
      • How to Use: Ensure your media content is well-tagged and described to benefit from improved indexing and searchability.
1247. Munin Signals (KnowledgeAnswersIntentQueryMuninSignals)
      • Description: Derived from Munin function call annotations, these signals help in the detailed understanding of function calls.
      • SEO Purpose: Improves the algorithm’s ability to understand complex queries involving function calls.
      • How to Use: Use clear and structured function calls in your content to enhance the algorithm’s understanding and indexing.
1248. NTPR Annotation Signals (KnowledgeAnswersIntentQueryNTPRAnnotationSignals)
      • Description: Signals associated with NTPR (Neural Token Parsing and Recognition) annotations, essential for conformance checking.
      • SEO Purpose: Enhances the accuracy of parsing and recognizing tokens in user queries.
      • How to Use: Ensure your content includes well-defined and recognizable tokens to improve parsing accuracy.
1249. Nimble Annotation Signals (KnowledgeAnswersIntentQueryNimbleAnnotationSignals)
      • Description: Contains signals associated with NimbleAnnotator annotations, aiding in detailed content analysis.
      • SEO Purpose: Improves content analysis by leveraging signals from NimbleAnnotator annotations.
      • How to Use: Utilize annotations effectively in your content to benefit from detailed analysis and improved search relevance.
1250. On-Device Annotation Signals (KnowledgeAnswersIntentQueryOnDeviceAnnotationSignals)
      • Description: Signals from on-device annotators, helping in understanding and processing queries locally on the device.
      • SEO Purpose: Enhances the capability of processing queries on-device, improving the speed and relevance of search results.
      • How to Use: Ensure your content is optimized for on-device processing by including clear and concise annotations.
1251. Parsing Signals (KnowledgeAnswersIntentQueryParsingSignals)
      • Description: Parsing-related signals that help in the interpretation and understanding of user queries.
      • SEO Purpose: Improves the parsing accuracy of user queries, leading to more relevant search results.
      • How to Use: Include structured data and clear query examples in your content to enhance parsing accuracy.
1252. Personal Entity (KnowledgeAnswersIntentQueryPersonalEntity)
      • Description: Encapsulates personal memory annotations from QRef annotator, aiding in personalizing search results.
      • SEO Purpose: Enhances personalization of search results by using personal memory annotations.
      • How to Use: Ensure your content is personalized and relevant to individual users by leveraging personal memory annotations.
1253. Personal Entity Relationship (KnowledgeAnswersIntentQueryPersonalEntityEntityRelationship)
      • Description: Contains relationship information from QRef, aiding in understanding relationships between personal entities.
      • SEO Purpose: Improves the understanding of relationships between entities, enhancing the relevance of personalized search results.
      • How to Use: Clearly define and annotate relationships between entities in your content to benefit from improved personalization.
1254. Qref Annotation Signals (KnowledgeAnswersIntentQueryQrefAnnotationSignals)
      • Description: Signals associated with Qref annotations, aiding in the understanding and processing of queries.
      • SEO Purpose: Enhances the accuracy and relevance of search results by leveraging Qref annotations.
      • How to Use: Utilize Qref annotations in your content to improve the processing and understanding of queries.
1255. Relatedness Signals (KnowledgeAnswersIntentQueryRelatednessSignals)
      • Description: Relatedness matrix signals for function call arguments, aiding in understanding the relationship between query components.
      • SEO Purpose: Improves the understanding of relationships between query components, leading to more relevant search results.
      • How to Use: Ensure your content includes well-defined relationships between components to enhance query understanding.
1256. Response Meaning Signals (KnowledgeAnswersIntentQueryResponseMeaningSignalsResponseMeaningSignals)
      • Description: Contains SRM (Semantic Response Meaning) signal data for understanding the meaning of responses.
      • SEO Purpose: Enhances the relevance of search results by accurately interpreting the meaning of responses.
      • How to Use: Include clear and meaningful responses in your content to improve the interpretation and relevance of search results.
1257. Saft Signals (KnowledgeAnswersIntentQuerySaftSignals)
      • Description: Derived from overlapping SAFT (Speech Analysis and Filtering Technology) annotations, aiding in detailed content analysis.
      • SEO Purpose: Improves the analysis and filtering of speech content by leveraging SAFT annotations.
      • How to Use: Ensure your speech content is well-annotated and clear to benefit from improved analysis and filtering.
1258. Scalar Value (KnowledgeAnswersIntentQueryScalarValue)
      • Description: Represents a scalar numeric value with optional units, aiding in the understanding of numeric data.
      • SEO Purpose: Enhances the understanding of numeric content by clearly defining scalar values.
      • How to Use: Use scalar values for numeric data in your content to improve clarity and relevance.
1259. Semantic Annotation Signals (KnowledgeAnswersIntentQuerySemanticAnnotationSignals)
      • Description: Signals associated with semantic annotations, aiding in the understanding and processing of content.
      • SEO Purpose: Enhances the relevance and accuracy of search results by leveraging semantic annotations.
      • How to Use: Include semantic annotations in your content to improve processing and understanding.
1260. Sensitive Argument Value Guard (KnowledgeAnswersIntentQuerySensitiveArgumentValueGuard)
      • Description: Guards sensitive argument values, ensuring secure handling and encryption.
      • SEO Purpose: Enhances the security and privacy of sensitive content.
      • How to Use: Ensure sensitive data in your content is properly encrypted and securely handled to maintain privacy and security.
1261. Shopping IDs (KnowledgeAnswersIntentQueryShoppingIds)
      • Description: Additional shopping identifiers related to entities or function calls, aiding in fulfillment.
      • SEO Purpose: Enhances the accuracy and relevance of shopping-related search results.
      • How to Use: Include accurate and relevant shopping identifiers in your content to improve search results for shopping queries.
1262. Shopping IDs Measure Value (KnowledgeAnswersIntentQueryShoppingIdsMeasureValue)
      • Description: Represents a measured value of a product, aiding in the understanding of product attributes.
      • SEO Purpose: Enhances the relevance of product search results by clearly defining product attributes.
      • How to Use: Ensure your product content includes clear and accurate measured values to improve search relevance.
1263. Signal Computation Fallback Intent (KnowledgeAnswersIntentQuerySignalComputationFallbackIntent)
      • Description: Represents an intent to use for scoring if the root intent is invalid, aiding in query fallback handling.
      • SEO Purpose: Ensures that invalid intents do not disrupt search results by providing fallback options.
      • How to Use: Define clear fallback intents for your content to ensure robust handling of invalid queries.
1264. Simple Value (KnowledgeAnswersIntentQuerySimpleValue)
      • Description: Represents a simple literal value, aiding in the understanding of basic data types.
      • SEO Purpose: Enhances the understanding of basic data types in content.
      • How to Use: Use simple literal values for basic data in your content to improve clarity and relevance.
1265. Support Transfer Signals (KnowledgeAnswersIntentQuerySupportTransferSignals)
      • Description: Indicates whether an entity received or transferred support, aiding in understanding entity relationships.
      • SEO Purpose: Enhances the understanding of support relationships between entities.
      • How to Use: Clearly define support relationships between entities in your content to improve relevance.
1266. Teleport Argument Annotator Signals (KnowledgeAnswersIntentQueryTeleportArgumentAnnotatorSignals)
      • Description: Signals associated with TeleportArgumentAnnotator annotations, aiding in detailed content analysis.
      • SEO Purpose: Enhances content analysis by leveraging TeleportArgumentAnnotator signals.
      • How to Use: Include TeleportArgumentAnnotator annotations in your content to improve analysis and understanding.
1267. Token (KnowledgeAnswersIntentQueryToken)
      • Description: Represents an ngram with relevant information, aiding in the understanding and parsing of tokens.
      • SEO Purpose: Enhances token parsing accuracy by providing detailed token information.
      • How to Use: Ensure your content includes well-defined and relevant tokens to improve parsing accuracy.
1268. Token Synonym (KnowledgeAnswersIntentQueryTokenSynonym)
      • Description: Contains information about synonyms of a token’s ngram, aiding in understanding and parsing synonyms.
      • SEO Purpose: Improves query interpretation by understanding synonyms used in queries.
      • How to Use: Include relevant synonyms in your content to enhance query interpretation and relevance.
1269. Tokens (KnowledgeAnswersIntentQueryTokens)
      • Description: Includes a list of tokens with aggregated scores, aiding in the understanding and parsing of tokens.
      • SEO Purpose: Enhances token parsing by providing a comprehensive list of tokens with scores.
      • How to Use: Ensure your content includes well-defined tokens with relevant scores to improve parsing accuracy.
1270. Intersect Type (KnowledgeAnswersIntersectType)
      • Description: Configures a value whose type is intended to be intersected, aiding in understanding intersecting data.
      • SEO Purpose: Enhances the understanding of intersecting data types in content.
      • How to Use: Use intersect types for relevant data in your content to improve clarity and relevance.
1271. Marker (KnowledgeAnswersMarker)
      • Description: Specifies a Meaning Expression’s purpose, aiding in understanding intent functions.
      • SEO Purpose: Enhances the understanding of intent functions in content.
      • How to Use: Use markers to define the purpose of intent functions in your content to improve clarity and relevance.
1272. Marker Command (KnowledgeAnswersMarkerCommand)
      • Description: Indicates a command, instructing actions to be taken, aiding in understanding command intents.
      • SEO Purpose: Enhances the understanding of command intents in content.
      • How to Use: Use clear commands in your content to improve the interpretation and relevance of command intents.
1273. Marker Open Question (KnowledgeAnswersMarkerOpenQuestion)
      • Description: Indicates a question requesting the value of a specified slot, aiding in understanding open questions.
      • SEO Purpose: Enhances the understanding of open questions in content.
      • How to Use: Use clear and well-defined questions in your content to improve the interpretation and relevance of open questions.
1274. Marker Polar Question (KnowledgeAnswersMarkerPolarQuestion)
      • Description: Indicates a question requesting the truth-value of a state of affairs, often a yes/no question.
      • SEO Purpose: Enhances the understanding of yes/no questions in content.
      • How to Use: Use clear and well-defined yes/no questions in your content to improve the interpretation and relevance of polar questions.
1275. Marker State of Affairs (KnowledgeAnswersMarkerStateOfAffairs)
      • Description: Indicates a reference to a particular state of affairs, aiding in understanding propositions and actions.
      • SEO Purpose: Enhances the understanding of propositions and actions in content.
      • How to Use: Clearly define states of affairs in your content to improve clarity and relevance.
1276. Meaning Schema Key (KnowledgeAnswersMeaningSchemaKey)
      • Description: Represents the primary key for an intent, aiding in understanding and managing intent schemas.
      • SEO Purpose: Enhances the management and understanding of intent schemas in content.
      • How to Use: Use well-defined schema keys for intents in your content to improve organization and relevance.
1277. Meaning Schema Slot Key (KnowledgeAnswersMeaningSchemaSlotKey)
      • Description: Represents the primary key for a MeaningSchema slot, aiding in managing schema slots.
      • SEO Purpose: Enhances the management and understanding of schema slots in content.
      • How to Use: Use well-defined slot keys in your content to improve organization and relevance.
1278. Measurement Type (KnowledgeAnswersMeasurementType)
      • Description: Configures a value that consists of a measurement, aiding in understanding numeric and unit data.
      • SEO Purpose: Enhances the understanding of numeric and unit data in content.
      • How to Use: Use clear and accurate measurement types for numeric data in your content to improve clarity and relevance.
1279. Normalized String Type (KnowledgeAnswersNormalizedStringType)
      • Description: Configures a value that is one of the listed normalized values, aiding in simplifying grammar rules.
      • SEO Purpose: Enhances the understanding of normalized string values in content.
      • How to Use: Use normalized string types for relevant data in your content to improve clarity and relevance.
1280. Number Type (KnowledgeAnswersNumberType)
      • Description: Configures a value that is numeric, aiding in understanding numeric data.
      • SEO Purpose: Enhances the understanding of numeric values in content.
      • How to Use: Use clear and accurate numeric values in your content to improve clarity and relevance.
1281. Opaque Aog Type (KnowledgeAnswersOpaqueAogType)
      • Description: Custom opaque type used for actions-on-google in-dialog queries, aiding in understanding custom intents.
      • SEO Purpose: Enhances the understanding of custom intents in content.
      • How to Use: Use clear and well-defined custom intents in your content to improve interpretation and relevance.
1282. Opaque App Annotation Type (KnowledgeAnswersOpaqueAppAnnotationType)
      • Description: Captures signals for app annotations, aiding in understanding app-related queries.
      • SEO Purpose: Enhances the understanding of app-related queries in content.
      • How to Use: Include clear app annotations in your content to improve interpretation and relevance.
1283. Opaque Audio Type (KnowledgeAnswersOpaqueAudioType)
      • Description: Captures signals for audio content, aiding in understanding audio-related queries.
      • SEO Purpose: Enhances the understanding of audio-related queries in content.
      • How to Use: Ensure your audio content is well-annotated to improve interpretation and relevance.
1284. Opaque Calendar Event Type (KnowledgeAnswersOpaqueCalendarEventType)
      • Description: Captures signals for calendar events, aiding in understanding calendar-related queries.
      • SEO Purpose: Enhances the understanding of calendar-related queries in content.
      • How to Use: Ensure your calendar events are well-annotated to improve interpretation and relevance.
1285. Opaque Calendar Event Wrapper Type (KnowledgeAnswersOpaqueCalendarEventWrapperType)
      • Description: Wraps sensitive calendar events that require additional protection, aiding in secure handling.
      • SEO Purpose: Enhances the security and privacy of sensitive calendar events.
      • How to Use: Ensure sensitive calendar events are properly wrapped and securely handled in your content.
1286. Opaque Calendar Reference Type (KnowledgeAnswersOpaqueCalendarReferenceType)
      • Description: Captures signals for calendar references, aiding in understanding calendar-related queries.
      • SEO Purpose: Enhances the understanding of calendar-related queries in content.
      • How to Use: Ensure your calendar references are well-annotated to improve interpretation and relevance.
1287. Opaque Complex Queries Rewrite Type (KnowledgeAnswersOpaqueComplexQueriesRewriteType)
      • Description: Captures signals for complex query rewrites, aiding in understanding and processing complex queries.
      • SEO Purpose: Enhances the handling and interpretation of complex queries.
      • How to Use: Ensure your content includes clear and well-defined complex queries to improve processing and relevance.
1288. Opaque Component Reference Index Type (KnowledgeAnswersOpaqueComponentReferenceIndexType)
      • Description: Captures signals for component references, aiding in understanding and processing component-related queries.
      • SEO Purpose: Enhances the handling and interpretation of component-related queries.
      • How to Use: Ensure your component references are well-defined and clear to improve processing and relevance.
1289. Opaque Device ID Type (KnowledgeAnswersOpaqueDeviceIdType)
      • Description: Captures signals for device IDs, aiding in understanding and processing device-related queries.
      • SEO Purpose: Enhances the handling and interpretation of device-related queries.
      • How to Use: Ensure your device IDs are well-defined and clear to improve processing and relevance.
1290. Opaque Device Type (KnowledgeAnswersOpaqueDeviceType)
      • Description: Captures signals for device types, aiding in understanding and processing device-related queries.
      • SEO Purpose: Enhances the handling and interpretation of device-related queries.
      • How to Use: Ensure your device types are well-defined and clear to improve processing and relevance.
1291. Opaque Device User Identity Type (KnowledgeAnswersOpaqueDeviceUserIdentityType)
      • Description: Captures signals for device user identities, aiding in understanding and processing user-related queries.
      • SEO Purpose: Enhances the handling and interpretation of user-related queries.
      • How to Use: Ensure your user identities are well-defined and clear to improve processing and relevance.
1292. Opaque Home Automation Device Type (KnowledgeAnswersOpaqueHomeAutomationDeviceType)
      • Description: Captures signals for home automation devices, aiding in understanding and processing home automation-related queries.
      • SEO Purpose: Enhances the handling and interpretation of home automation-related queries.
      • How to Use: Ensure your home automation devices are well-defined and clear to improve processing and relevance.
1293. Opaque Location Type (KnowledgeAnswersOpaqueLocationType)
      • Description: Captures signals for locations, aiding in understanding and processing location-related queries.
      • SEO Purpose: Enhances the handling and interpretation of location-related queries.
      • How to Use: Ensure your locations are well-defined and clear to improve processing and relevance.
1294. Opaque Media Type (KnowledgeAnswersOpaqueMediaType)
      • Description: Captures signals for media content, aiding in understanding and processing media-related queries.
      • SEO Purpose: Enhances the handling and interpretation of media-related queries.
      • How to Use: Ensure your media content is well-defined and clear to improve processing and relevance.
1295. Opaque Message Notification Type (KnowledgeAnswersOpaqueMessageNotificationType)
      • Description: Captures signals for message notifications, aiding in understanding and processing notification-related queries.
      • SEO Purpose: Enhances the handling and interpretation of notification-related queries.
      • How to Use: Ensure your message notifications are well-defined and clear to improve processing and relevance.
1296. Opaque Money Type (KnowledgeAnswersOpaqueMoneyType)
      • Description: Captures signals for monetary values, aiding in understanding and processing money-related queries.
      • SEO Purpose: Enhances the handling and interpretation of money-related queries.
      • How to Use: Ensure your monetary values are well-defined and clear to improve processing and relevance.
1297. Opaque News Provider Type (KnowledgeAnswersOpaqueNewsProviderType)
      • Description: Captures signals for news providers, aiding in understanding and processing news-related queries.
      • SEO Purpose: Enhances the handling and interpretation of news-related queries.
      • How to Use: Ensure your news providers are well-defined and clear to improve processing and relevance.
1298. Opaque On-Device Type (KnowledgeAnswersOpaqueOnDeviceType)
      • Description: Captures signals for on-device queries, aiding in understanding and processing on-device content.
      • SEO Purpose: Enhances the handling and interpretation of on-device queries.
      • How to Use: Ensure your on-device content is well-defined and clear to improve processing and relevance.
1299. Opaque Person Type (KnowledgeAnswersOpaquePersonType)
      • Description: Captures signals for person entities, aiding in understanding and processing person-related queries.
      • SEO Purpose: Enhances the handling and interpretation of person-related queries.
      • How to Use: Ensure your person entities are well-defined and clear to improve processing and relevance.
1300. Opaque Personal Intelligence Entity Type (KnowledgeAnswersOpaquePersonalIntelligenceEntityType)
      • Description: Captures signals for personal intelligence entities, aiding in understanding and processing personal intelligence-related queries.
      • SEO Purpose: Enhances the handling and interpretation of personal intelligence-related queries.
      • How to Use: Ensure your personal intelligence entities are well-defined and clear to improve processing and relevance.
1301. Opaque Productivity List Item Type (KnowledgeAnswersOpaqueProductivityListItemType)
      • Description: Captures signals for productivity list items, aiding in understanding and processing productivity-related queries.
      • SEO Purpose: Enhances the handling and interpretation of productivity-related queries.
      • How to Use: Ensure your productivity list items are well-defined and clear to improve processing and relevance.
1302. Opaque Recurrence Type (KnowledgeAnswersOpaqueRecurrenceType)
      • Description: Captures signals for recurrence patterns, aiding in understanding and processing recurrence-related queries.
      • SEO Purpose: Enhances the handling and interpretation of recurrence-related queries.
      • How to Use: Ensure your recurrence patterns are well-defined and clear to improve processing and relevance.
1303. Opaque Reminder Type (KnowledgeAnswersOpaqueReminderType)
      • Description: Captures signals for reminders, aiding in understanding and processing reminder-related queries.
      • SEO Purpose: Enhances the handling and interpretation of reminder-related queries.
      • How to Use: Ensure your reminders are well-defined and clear to improve processing and relevance.
1304. Opaque Shopping Merchant Type (KnowledgeAnswersOpaqueShoppingMerchantType)
      • Description: Captures signals for shopping merchants, aiding in understanding and processing merchant-related queries.
      • SEO Purpose: Enhances the handling and interpretation of merchant-related queries.
      • How to Use: Ensure your shopping merchants are well-defined and clear to improve processing and relevance.
1305. Opaque Shopping Offer Type (KnowledgeAnswersOpaqueShoppingOfferType)
      • Description: Captures signals for shopping offers, aiding in understanding and processing offer-related queries.
      • SEO Purpose: Enhances the handling and interpretation of offer-related queries.
      • How to Use: Ensure your shopping offers are well-defined and clear to improve processing and relevance.
1306. Opaque Shopping Product Expression Type (KnowledgeAnswersOpaqueShoppingProductExpressionType)
      • Description: Captures signals for product expressions, aiding in understanding and processing product-related queries.
      • SEO Purpose: Enhances the handling and interpretation of product-related queries.
      • How to Use: Ensure your product expressions are well-defined and clear to improve processing and relevance.
1307. Opaque Shopping Product Type (KnowledgeAnswersOpaqueShoppingProductType)
      • Description: Captures signals for shopping products, aiding in understanding and processing product-related queries.
      • SEO Purpose: Enhances the handling and interpretation of product-related queries.
      • How to Use: Ensure your shopping products are well-defined and clear to improve processing and relevance.
1308. Opaque Shopping Store Type (KnowledgeAnswersOpaqueShoppingStoreType)
      • Description: Captures signals for shopping stores, aiding in understanding and processing store-related queries.
      • SEO Purpose: Enhances the handling and interpretation of store-related queries.
      • How to Use: Ensure your shopping stores are well-defined and clear to improve processing and relevance.
1309. Opaque Timer Type (KnowledgeAnswersOpaqueTimerType)
      • Description: Captures signals for timers, aiding in understanding and processing timer-related queries.
      • SEO Purpose: Enhances the handling and interpretation of timer-related queries.
      • How to Use: Ensure your timers are well-defined and clear to improve processing and relevance.
1310. Opaque Type (KnowledgeAnswersOpaqueType)
      • Description: Configures a value whose type is only interpretable by specific clients of the intent catalog, aiding in handling custom types.
      • SEO Purpose: Enhances the handling and interpretation of custom types in content.
      • How to Use: Ensure your custom types are well-defined and clear to improve processing and relevance.
1311. Plexity Requirement (KnowledgeAnswersPlexityRequirement)
      • Description: Plexity distinguishes between viewing an item as a single entity or a complex concept consisting of multiple parts. It is independent of grammatical number or collective interpretations.
      • SEO Purpose: Enhances content clarity by properly distinguishing between singular and complex concepts.
      • How to Use: Clearly define whether an item is a single entity or a complex concept to improve content understanding and relevance.
1312. Polar Question Type (KnowledgeAnswersPolarQuestionType)
      • Description: Represents a polar question, typically a yes/no question.
      • SEO Purpose: Improves query interpretation by correctly identifying yes/no questions.
      • How to Use: Structure questions in your content to be clear yes/no queries to enhance user engagement and query match.
1313. Range Constraint (KnowledgeAnswersRangeConstraint)
      • Description: Defines constraints on a range, including maximum and minimum values and whether endpoints are inclusive or exclusive.
      • SEO Purpose: Ensures accurate data representation and improves the precision of search results.
      • How to Use: Specify clear range constraints in your content to provide accurate data boundaries.
1314. Same Type (KnowledgeAnswersSameType)
      • Description: Ensures that values in a slot have the same type.
      • SEO Purpose: Maintains data consistency and improves search relevance.
      • How to Use: Use consistent data types in your content to enhance clarity and relevance.
1315. Semantic Type (KnowledgeAnswersSemanticType)
      • Description: Configures a value determined by another source, such as another intent or semantic frame.
      • SEO Purpose: Enhances the understanding of data relationships and improves content structure.
      • How to Use: Use semantic types to define relationships between data points in your content.
1316. Sensitivity Argument Eval Policy (KnowledgeAnswersSensitivityArgumentEvalPolicy)
      • Description: Controls evaluation at the argument level.
      • SEO Purpose: Ensures sensitive data is handled appropriately.
      • How to Use: Define clear evaluation policies for sensitive data to maintain privacy and compliance.
1317. Sensitivity Instruction (KnowledgeAnswersSensitivityInstruction)
      • Description: Provides instructions for handling sensitive intents and data.
      • SEO Purpose: Ensures sensitive data is processed correctly according to predefined guidelines.
      • How to Use: Implement sensitivity instructions to handle sensitive data properly in your content.
1318. Sensitivity Instruction Argument (KnowledgeAnswersSensitivityInstructionArgument)
      • Description: Provides instructions at the slot or argument level for handling sensitive data.
      • SEO Purpose: Enhances the precision of sensitive data handling.
      • How to Use: Use argument-level instructions to fine-tune the handling of sensitive data in your content.
1319. Sensitivity Instruction Intent (KnowledgeAnswersSensitivityInstructionIntent)
      • Description: Provides intent-level instructions for handling all arguments within an intent.
      • SEO Purpose: Ensures comprehensive handling of sensitive intents.
      • How to Use: Apply intent-level instructions to manage the handling of sensitive data holistically.
1320. Sensitivity Instruction Previous Query (KnowledgeAnswersSensitivityInstructionPreviousQuery)
      • Description: Provides instructions for handling data from previous queries.
      • SEO Purpose: Maintains consistency and compliance when using data from past interactions.
      • How to Use: Define clear instructions for managing data derived from previous queries.
1321. Sensitivity Intent Eval Policy (KnowledgeAnswersSensitivityIntentEvalPolicy)
      • Description: Controls evaluation at the intent level.
      • SEO Purpose: Ensures sensitive intents are evaluated according to predefined policies.
      • How to Use: Implement intent-level evaluation policies to ensure sensitive data is handled appropriately.
1322. Sensitivity Logging Policy (KnowledgeAnswersSensitivityLoggingPolicy)
      • Description: Controls the logging of sensitive data.
      • SEO Purpose: Ensures sensitive data is logged in compliance with privacy guidelines.
      • How to Use: Define logging policies to manage how sensitive data is recorded and stored.
1323. Sensitivity My Activity Policy (KnowledgeAnswersSensitivityMyActivityPolicy)
      • Description: Controls how sensitive data is managed within the user’s activity history.
      • SEO Purpose: Maintains user privacy by properly handling sensitive data in activity logs.
      • How to Use: Implement policies to manage sensitive data in user activity histories.
1324. Sensitivity Sensitivity (KnowledgeAnswersSensitivitySensitivity)
      • Description: Represents the sensitivity level of a query or data point.
      • SEO Purpose: Enhances data privacy by categorizing data sensitivity levels.
      • How to Use: Classify data based on sensitivity to improve privacy management.
1325. Sensitivity Serving Policy (KnowledgeAnswersSensitivityServingPolicy)
      • Description: Controls the RPC whitelist for serving sensitive data.
      • SEO Purpose: Ensures sensitive data is served only to authorized requests.
      • How to Use: Define serving policies to control access to sensitive data during requests.
1326. Sensitivity Storage Policy (KnowledgeAnswersSensitivityStoragePolicy)
      • Description: Controls the storage of sensitive data.
      • SEO Purpose: Ensures sensitive data is stored securely and in compliance with guidelines.
      • How to Use: Implement storage policies to manage how sensitive data is stored and accessed.
1327. State of Affairs Type (KnowledgeAnswersStateOfAffairsType)
      • Description: Represents a state of affairs, aiding in understanding propositions and actions.
      • SEO Purpose: Enhances the understanding of propositions and actions in content.
      • How to Use: Clearly define states of affairs in your content to improve clarity and relevance.
1328. String Type (KnowledgeAnswersStringType)
      • Description: Configures a value intended to be arbitrary text.
      • SEO Purpose: Enhances the handling and interpretation of text data.
      • How to Use: Use clear and accurate text values in your content to improve clarity and relevance.
1329. TimeZone Type (KnowledgeAnswersTimeZoneType)
      • Description: Configures a value that is a timezone.
      • SEO Purpose: Enhances the handling and interpretation of time-related data.
      • How to Use: Use clear and accurate timezone values in your content to improve clarity and relevance.
1330. Tracking Number Type (KnowledgeAnswersTrackingNumberType)
      • Description: Configures a value that is a tracking number.
      • SEO Purpose: Enhances the handling and interpretation of tracking information.
      • How to Use: Use clear and accurate tracking numbers in your content to improve clarity and relevance.
1331. Union Type (KnowledgeAnswersUnionType)
      • Description: Configures a value that can be one of several specified types.
      • SEO Purpose: Enhances the flexibility and relevance of data handling.
      • How to Use: Use union types to allow for multiple data types in your content, improving flexibility.
1332. Value Type (KnowledgeAnswersValueType)
      • Description: Specifies the allowed types that a value can have, ensuring type consistency.
      • SEO Purpose: Enhances data consistency and relevance.
      • How to Use: Define allowed value types to maintain consistency in your content.
1333. DateTime Proto (KnowledgeGraphDateTimeProto)
      • Description: Represents date and time values with detailed components such as year, month, day, hour, minute, second, and timezone offset.
      • SEO Purpose: Enhances the precision and relevance of date and time information in content.
      • How to Use: Use detailed date and time values in your content to improve accuracy and relevance.
1334. Nested Struct (KnowledgeGraphNestedStruct)
      • Description: A recursive tree structure for storing a set of triples, representing complex relationships between data points.
      • SEO Purpose: Enhances the representation of complex data relationships.
      • How to Use: Use nested structures to accurately represent complex data relationships in your content.
1335. Triple (KnowledgeGraphTriple)
      • Description: Represents data with a subject, predicate, and object, allowing for detailed relationships between data points.
      • SEO Purpose: Enhances the understanding and representation of data relationships.
      • How to Use: Use triples to define clear relationships between data points in your content.
1336. Triple Object (KnowledgeGraphTripleObj)
      • Description: Represents the object part of a triple with various possible data types, such as boolean, datetime, double, int, string, etc.
      • SEO Purpose: Enhances the precision and flexibility of data representation.
      • How to Use: Use appropriate data types for objects in your triples to improve data accuracy and relevance.
1337. Triple Provenance (KnowledgeGraphTripleProvenance)
      • Description: Contains information about the source of a triple, providing context for data relationships.
      • SEO Purpose: Enhances the trustworthiness and transparency of data.
      • How to Use: Include provenance information to provide context and improve data credibility.
1338. User Specified Location (KnowledgeVerticalsWeatherProtoUserSpecifiedLocation)
      • Description: Represents a location specified by the user, used to trigger weather or other vertical-specific information.
      • SEO Purpose: Enhances the personalization and relevance of location-based content.
      • How to Use: Use user-specified locations to tailor content based on user preferences and locations.
1339. Legal Citation (LegalCitation)
      • Description: Represents a legal citation, including country, state, court, document, and law information.
      • SEO Purpose: Enhances the accuracy and relevance of legal references in content.
      • How to Use: Use detailed legal citations to improve the credibility and precision of legal content.
1340. Court Document (LegalCitationCourtDocument)
      • Description: Contains information about a published court document, including court name, level, and opinion details.
      • SEO Purpose: Enhances the accuracy and relevance of court-related content.
      • How to Use: Include detailed court document information to improve the credibility and precision of legal content.
1341. Law (LegalCitationLaw)
      • Description: Represents a law with detailed attributes such as revision date, status, type, collection name, and levels.
      • SEO Purpose: Enhances the accuracy and relevance of legal references.
      • How to Use: Use detailed law information to improve the credibility and precision of legal content.
1342. Legal Date (LegalDate)
      • Description: Represents a legal date with components such as day, month, and year.
      • SEO Purpose: Enhances the precision and relevance of date information in legal content.
      • How to Use: Use detailed legal dates to improve the accuracy and relevance of legal content.
1343. Person (LegalPerson)
      • Description: Represents a person with attributes such as description, last name, and other names.
      • SEO Purpose: Enhances the personalization and relevance of content related to individuals.
      • How to Use: Use detailed person information to improve the accuracy and relevance of personal content.
1344. Style Aesthetics Score Signals (LensDiscoveryStyleAestheticsScoreSignals)
      • Description: Represents the aesthetics score of a style image, indicating its visual appeal.
      • SEO Purpose: Enhances the understanding and ranking of visually appealing images.
      • How to Use: Include aesthetics scores to improve the ranking of style images based on visual appeal.
1345. Bounding Box (LensDiscoveryStyleBoundingBox)
      • Description: Represents a bounding box with absolute integer coordinates, indicating the position of an element in an image.
      • SEO Purpose: Enhances the precision and relevance of image content.
      • How to Use: Use bounding boxes to accurately define the position of elements in images.
1346. Person Attributes (LensDiscoveryStylePersonAttributes)
      • Description: Represents attributes of a person detected in an image, such as visibility scores and predictions.
      • SEO Purpose: Enhances the understanding and relevance of person-related content in images.
      • How to Use: Use detailed person attributes to improve the relevance and precision of image content.
1347. Person Detection Signals (LensDiscoveryStylePersonDetectionSignals)
      • Description: Represents the bounding boxes of detected people in an image, indicating their position and attributes.
      • SEO Purpose: Enhances the precision and relevance of person-related content in images.
      • How to Use: Use person detection signals to accurately define the position and attributes of people in images.
1348. Style Image Type Signals (LensDiscoveryStyleStyleImageTypeSignals)
      • Description: Represents the predicted style image type, such as stage, stock, street, or outfits.
      • SEO Purpose: Enhances the classification and relevance of style images.
      • How to Use: Use style image type signals to accurately classify and rank style images.
1349. List Snippet Response (ListSnippetResponse)
      • Description: Represents data to generate list snippets UI, including rows of data.
      • SEO Purpose: Enhances the presentation and relevance of list-based content.
      • How to Use: Use list snippet responses to create visually appealing and relevant list-based content.
1350. Local WWW Info (LocalWWWInfo)
      • Description: Represents information related to local businesses, such as addresses, phone numbers, and opening hours.
      • SEO Purpose: Enhances the relevance and accuracy of local business content.
      • How to Use: Use detailed local business information to improve the accuracy and relevance of local content.
1351. Cluster (LocalWWWInfoCluster)
      • Description: Represents clusters of local business information, including confidence scores, hours, and relevance.
      • SEO Purpose: Enhances the accuracy and relevance of clustered local business content.
      • How to Use: Use clusters to group related local business information and improve content relevance.
1352. Opening Hours (LocalWWWInfoOpeningHours)
      • Description: Represents the opening hours of a local business.
      • SEO Purpose: Enhances the accuracy and relevance of local business content.
      • How to Use: Include detailed opening hours to improve the accuracy and relevance of local business content.
1353. Phone (LocalWWWInfoPhone)
      • Description: Represents the phone number of a local business.
      • SEO Purpose: Enhances the accuracy and relevance of contact information in local business content.
      • How to Use: Include detailed phone numbers to improve the accuracy and relevance of local business content.
1354. Wrapptor Item (LocalWWWInfoWrapptorItem)
      • Description: Represents a single WrapptorItem with business name, address, and phone number.
      • SEO Purpose: Enhances the accuracy and relevance of business contact information.
      • How to Use: Use Wrapptor items to provide detailed contact information for businesses.
1355. Chain ID (LocalsearchChainId)
      • Description: Represents the unique identification of a chain, including prominent entity ID and sitechunk.
      • SEO Purpose: Enhances the accuracy and relevance of chain-related content.
      • How to Use: Use chain IDs to accurately identify and group related business locations.
1356. Doc Info (LocalsearchDocInfo)
      • Description: Represents document information related to local search.
      • SEO Purpose: Enhances the relevance and accuracy of local search content.
      • How to Use: Include detailed document information to improve the accuracy and relevance of local search content.
1357. Food Ordering Action Metadata (LocalsearchProtoInternalFoodOrderingActionMetadata)
      • Description: Represents metadata associated with food ordering actions, including service type and availability.
      • SEO Purpose: Enhances the relevance and accuracy of food ordering content.
      • How to Use: Use detailed food ordering metadata to improve the accuracy and relevance of food ordering content.
1358. Crawler ID Proto (LogsProtoIndexingCrawlerIdCrawlerIdProto)
      • Description: Represents the Crawler-ID in Web-Search, used for identifying and applying attributes.
      • SEO Purpose: Enhances the accuracy and relevance of web search content.
      • How to Use: Use crawler IDs to accurately identify and manage web search content.
1359. Entity Link Metadata (LogsSemanticInterpretationIntentQueryEntityLinkMetadata)
      • Description: Represents metadata for entity links, used to imply QRef implications.
      • SEO Purpose: Enhances the understanding and relevance of entity relationships.
      • How to Use: Include detailed entity link metadata to improve the accuracy and relevance of entity-related content.
1360. Link Kind Flags (LogsSemanticInterpretationIntentQueryLinkKindFlags)
      • Description: Represents flags for link kinds, used to imply QRef implications.
      • SEO Purpose: Enhances the understanding and relevance of link relationships.
      • How to Use: Use link kind flags to accurately define and manage link relationships.
1361. Link Kind Info (LogsSemanticInterpretationIntentQueryLinkKindInfo)
      • Description: Represents information about link kinds, used to imply QRef implications.
      • SEO Purpose: Enhances the understanding and relevance of link relationships.
      • How to Use: Include detailed link kind information to improve the accuracy and relevance of link-related content.
1362. Support Transfer Rule (LogsSemanticInterpretationIntentQuerySupportTransferRule)
      • Description: Represents rules for support transfer, used to manage entity support in queries.
      • SEO Purpose: Enhances the understanding and relevance of support relationships.
      • How to Use: Use support transfer rules to accurately define and manage support relationships in queries.
1363. Webref Entity Relationship (LogsSemanticInterpretationIntentQueryWebrefEntityRelationship)
      • Description: Represents relationships between webref entities, used to imply QRef implications.
      • SEO Purpose: Enhances the understanding and relevance of entity relationships.
      • How to Use: Include detailed entity relationship information to improve the accuracy and relevance of content.
1364. Long Structured Snippet (LongStructuredSnippet)
      • Description: Represents a long snippet with headers and plain text paragraphs.
      • SEO Purpose: Enhances the presentation and relevance of long-form content.
      • How to Use: Use long structured snippets to create detailed and visually appealing content.
1365. Long Structured Snippet Entry (LongStructuredSnippetEntry)
      • Description: Represents an entry in a long structured snippet, indicating whether it is a header or paragraph.
      • SEO Purpose: Enhances the presentation and relevance of long-form content.
      • How to Use: Use structured snippet entries to create detailed and visually appealing content.
1366. Contact Shortcut Information (MajelContactInformationShortcutInformation)
      • Description: Indicates if a contact is related to an app shortcut.
      • SEO Purpose: Helps in understanding and optimizing the association between contacts and app shortcuts.
      • How to Use: Utilize this information to enhance app functionality and user experience by optimizing contact-related shortcuts.
1367. Special Words Flags (MapsQualitySpecialWordsFlags)
      • Description: Describes flags that provide information about special words used in maps, such as abbreviations and directional indicators.
      • SEO Purpose: Helps in canonicalizing user queries and improving the accuracy of map-related searches.
      • How to Use: Implement special words flags to optimize map data processing and improve the relevance of search results.
1368. Special Words Proto (MapsQualitySpecialWordsProto)
      • Description: Manages special words in maps to rewrite abbreviations into canonical versions and determine important tokens.
      • SEO Purpose: Enhances the precision of map searches and data indexing.
      • How to Use: Use special words proto to ensure that address components and other map elements are correctly identified and indexed.
1369. Bounding Box (MediaIndexBoundingbox)
      • Description: Stores coordinates for the dimensions of a box surrounding a region of interest in an image.
      • SEO Purpose: Improves the accuracy of image content indexing and search.
      • How to Use: Use bounding boxes to define regions of interest in images, enhancing image search and categorization.
1370. Entity Field (MediaIndexEntityField)
      • Description: Combines entity ID and score from a given source.
      • SEO Purpose: Improves entity-based search accuracy and relevance.
      • How to Use: Use entity fields to better categorize and rank content based on entity scores.
1371. Frame Identifier (MediaIndexFrameIdentifier)
      • Description: Identifies frames associated with a video.
      • SEO Purpose: Enhances video content indexing and search precision.
      • How to Use: Utilize frame identifiers to accurately segment and index video content for better search results.
1372. Preview Frame Zero Variant (MediaIndexFrameIdentifierPreviewFrameZeroVariant)
      • Description: Defines the first frame of a video’s generated preview.
      • SEO Purpose: Improves video content presentation and user engagement.
      • How to Use: Use this variant to create compelling video previews that attract user clicks.
1373. Region Metadata (MediaIndexRegion)
      • Description: Contains metadata associated with a region in an image.
      • SEO Purpose: Enhances the accuracy of image content indexing and search.
      • How to Use: Include region metadata to improve image content categorization and search relevance.
1374. Sparse Float Vector (MediaIndexSparseFloatVector)
      • Description: Represents sparse float vectors with parallel arrays of columns and values for efficient data storage and retrieval.
      • SEO Purpose: Enhances data processing efficiency and precision in search algorithms.
      • How to Use: Implement sparse float vectors to manage large datasets efficiently, improving search accuracy and performance.
1375. Video Centroid (MediaIndexVideoCentroid)
      • Description: Contains data about video behavior across different pages it is embedded in.
      • SEO Purpose: Enhances the understanding and relevance of video content based on its usage patterns.
      • How to Use: Use video centroid data to optimize video placement and improve user engagement.
1376. Video Centroid Domain Score (MediaIndexVideoCentroidDomainScore)
      • Description: Represents domain scores for video content based on its behavior across different pages.
      • SEO Purpose: Enhances video content ranking and relevance.
      • How to Use: Utilize domain scores to improve the ranking of video content based on its performance across multiple domains.
1377. Video Core Signals (MediaIndexVideoCoreSignals)
      • Description: Core signals for video content that are fetched for every query.
      • SEO Purpose: Improves the relevance and accuracy of video search results.
      • How to Use: Include core signals in video indexing to enhance search precision and user experience.
1378. Video Frame (MediaIndexVideoFrame)
      • Description: Contains data about a specific frame within a video.
      • SEO Purpose: Enhances the granularity and accuracy of video content indexing.
      • How to Use: Use frame data to accurately segment and index video content for improved search results.
1379. Video Frames (MediaIndexVideoFrames)
      • Description: Contains data about multiple frames within a video.
      • SEO Purpose: Enhances the granularity and accuracy of video content indexing.
      • How to Use: Utilize data about multiple frames to improve the precision of video content indexing and search.
1380. Xtag (MediaIndexXtag)
      • Description: Represents an Xtag with a name and value for categorizing content.
      • SEO Purpose: Enhances content categorization and search relevance.
      • How to Use: Use Xtages to tag and categorize content accurately, improving search precision and relevance.
1381. Xtag List (MediaIndexXtagList)
      • Description: A collection of Xtag instances associated with a specific piece of content.
      • SEO Purpose: Improves content categorization and search relevance.
      • How to Use: Utilize Xtag lists to manage content tags efficiently, enhancing search accuracy and relevance.
1382. Per Document Data (MobilePerDocData)
      • Description: Stores data associated with a specific document for mobile indexing.
      • SEO Purpose: Enhances mobile search relevance and accuracy.
      • How to Use: Use per document data to optimize content indexing for mobile search results.
1383. Field Presence (MultiscaleFieldPresence)
      • Description: Defines the presence of a field to distinguish between empty and non-present annotations.
      • SEO Purpose: Improves data accuracy and relevance in search algorithms.
      • How to Use: Implement field presence definitions to manage data annotations effectively, enhancing search precision.
1384. Layer Presence (MultiscaleLayerPresence)
      • Description: Defines the presence of a layer in a hierarchical structure.
      • SEO Purpose: Enhances the accuracy and relevance of layered content indexing.
      • How to Use: Use layer presence definitions to manage hierarchical data structures efficiently.
1385. Pointer Index (MultiscalePointerIndex)
      • Description: Points to a single node in a target scale, used for hierarchical indexing.
      • SEO Purpose: Enhances the precision and efficiency of hierarchical content indexing.
      • How to Use: Utilize pointer indices to accurately navigate and index hierarchical data structures.
1386. Pointer Span (MultiscalePointerSpan)
      • Description: Points to a contiguous range of nodes in a target scale.
      • SEO Purpose: Enhances the efficiency and precision of hierarchical content indexing.
      • How to Use: Use pointer spans to manage and index contiguous ranges of hierarchical data effectively.
1387. Snippet Candidate Feature (MustangReposWwwSnippetsCandidateFeature)
      • Description: Contains a pair of feature name and score for a snippet candidate.
      • SEO Purpose: Improves the ranking and relevance of snippet candidates.
      • How to Use: Use snippet candidate features to optimize snippet selection and ranking in search results.
1388. Organic List Snippet Response (MustangReposWwwSnippetsOrganicListSnippetResponse)
      • Description: Data to generate the list preview for organic list snippets.
      • SEO Purpose: Enhances the presentation and relevance of organic list snippets.
      • How to Use: Use organic list snippet response data to create visually appealing and relevant list previews.
1389. Snippet Candidate (MustangReposWwwSnippetsSnippetCandidate)
      • Description: Contains features for snippet candidates at the chooser level.
      • SEO Purpose: Improves snippet selection and ranking precision.
      • How to Use: Utilize snippet candidate features to optimize the selection and ranking of snippets in search results.
1390. Snippets Ranklab Features (MustangReposWwwSnippetsSnippetsRanklabFeatures)
      • Description: Protocol buffer to export snippet features into flatfiles for ranklab.
      • SEO Purpose: Enhances snippet ranking accuracy and relevance.
      • How to Use: Use ranklab features to optimize snippet ranking in search results.
1391. Rendered Token (MustangSnippetsRenderedToken)
      • Description: Represents a token rendered in generating snippets or titles.
      • SEO Purpose: Improves the accuracy and relevance of snippet and title generation.
      • How to Use: Use rendered tokens to create accurate and relevant snippets and titles.
1392. Versioned Item (NSRVersionedItem)
      • Description: Represents a versioned NSR score used for experimentation.
      • SEO Purpose: Enhances the precision of search result rankings through experimentation.
      • How to Use: Utilize versioned items to test and refine search ranking algorithms.
1393. Virtual Network ID (NetFabricRpcVirtualNetworkId)
      • Description: Globally unique identifier for a virtual network.
      • SEO Purpose: Improves the accuracy and relevance of network-related content.
      • How to Use: Use virtual network IDs to manage and categorize network-related content effectively.
1394. Component-Specific Contracts (NlpMeaningComponentSpecificContracts)
      • Description: Defines component-specific contracts for elements in the MeaningCatalog.
      • SEO Purpose: Enhances the precision and relevance of intent schemas and slots.
      • How to Use: Implement component-specific contracts to manage and enforce data schema conformance.
1395. Meaning Remodeling (NlpMeaningMeaningRemodeling)
      • Description: Indicates parts of a schema that are being remodeled.
      • SEO Purpose: Improves the adaptability and precision of data schemas.
      • How to Use: Use meaning remodelings to update and refine data schemas for better search relevance.
1396. Meaning Remodeling Control (NlpMeaningMeaningRemodelingControl)
      • Description: FunctionCall counterpart to the MeaningRemodelings structure for typechecking.
      • SEO Purpose: Enhances the accuracy and consistency of data schemas.
      • How to Use: Implement remodeling controls to ensure data schema consistency and accuracy.
1397. Semantic Type Name Contracts (NlpMeaningSemanticTypeNameComponentSpecificContracts)
      • Description: Defines component-specific contracts for semantic type names.
      • SEO Purpose: Enhances the precision and relevance of semantic type naming.
      • How to Use: Use semantic type name contracts to manage and enforce naming conventions for semantic types.
1398. Semantic Type Name Remodelings (NlpMeaningSemanticTypeNameMeaningRemodelings)
      • Description: Associates remodeling data with a semantic type name.
      • SEO Purpose: Improves the adaptability and relevance of semantic type names.
      • How to Use: Implement semantic type name remodelings to update and refine naming conventions.
1399. Annotated Phrase (NlpSaftAnnotatedPhrase)
      • Description: Represents a phrase in a document with a particular annotation.
      • SEO Purpose: Enhances the accuracy and relevance of document annotations.
      • How to Use: Use annotated phrases to improve document indexing and search precision.
1400. Constituency Node (NlpSaftConstituencyNode)
      • Description: Represents a node in a constituency parse tree with tokens as leaf nodes.
      • SEO Purpose: Improves the accuracy of syntactic analysis and search relevance.
      • How to Use: Implement constituency nodes to enhance syntactic parsing and document indexing.
1401. Document (NlpSaftDocument)
      • Description: Contains raw text content and analysis of a document, including tokens, entities, and mentions.
      • SEO Purpose: Enhances the accuracy and relevance of document indexing and search.
      • How to Use: Use document data to improve the precision of content indexing and retrieval.
1402. Document Topic (NlpSaftDocumentTopic)
      • Description: Represents topics associated with a document.
      • SEO Purpose: Enhances the relevance and accuracy of document categorization.
      • How to Use: Use document topics to improve content categorization and search relevance.
1403. Entity (NlpSaftEntity)
      • Description: Named entities within a document.
      • SEO Purpose: Improves entity-based search accuracy and relevance.
      • How to Use: Utilize entity data to enhance entity recognition and indexing.
1404. Entity Profile (NlpSaftEntityProfile)
      • Description: Contains a summary of information about a single unique entity.
      • SEO Purpose: Enhances entity-based search relevance and accuracy.
      • How to Use: Use entity profiles to improve the precision of entity recognition and indexing.
1405. Entity Profile Alternate (NlpSaftEntityProfileAlternate)
      • Description: Represents alternative names for an entity.
      • SEO Purpose: Improves the accuracy of entity recognition and search relevance.
      • How to Use: Implement alternate names to enhance entity recognition and indexing.
1406. Entity Profile Attribute (NlpSaftEntityProfileAttribute)
      • Description: Contains various attributes related to an entity, such as boolean values, floats, and strings.
      • SEO Purpose: Enhances the precision and relevance of entity-based search.
      • How to Use: Use entity profile attributes to enrich entity data for better search accuracy.
1407. Entity Profile Keyword (NlpSaftEntityProfileKeyword)
      • Description: Keywords and key phrases associated with an entity.
      • SEO Purpose: Improves the relevance of entity-based search results.
      • How to Use: Utilize keywords to enhance entity indexing and search relevance.
1408. Entity Profile Reference (NlpSaftEntityProfileReference)
      • Description: References to an entity within documents.
      • SEO Purpose: Enhances the accuracy and relevance of entity-based search.
      • How to Use: Use references to improve the precision of entity recognition and indexing.
1409. Entity Profile Related (NlpSaftEntityProfileRelated)
      • Description: Represents entities related to a specific entity.
      • SEO Purpose: Improves the accuracy and relevance of entity-based search.
      • How to Use: Utilize related entities to enhance entity recognition and indexing.
1410. Entity Type (NlpSaftEntityType)
      • Description: Describes a generic type for an entity.
      • SEO Purpose: Enhances entity recognition and categorization accuracy.
      • How to Use: Use entity types to categorize entities more accurately, improving search relevance.
1411. Hyperlink (NlpSaftHyperlink)
      • Description: Represents a hyperlink on an HTML page.
      • SEO Purpose: Enhances link-based content indexing and relevance.
      • How to Use: Implement hyperlinks to improve the accuracy of link-based content indexing.
1412. Identifier (NlpSaftIdentifier)
      • Description: Represents an external identifier for an object within a domain.
      • SEO Purpose: Improves the accuracy and relevance of content indexing based on identifiers.
      • How to Use: Use identifiers to enhance content categorization and indexing precision.
1413. Labeled Span (NlpSaftLabeledSpan)
      • Description: Represents a labeled span within a document, defined by byte-level or token-level boundaries.
      • SEO Purpose: Enhances the accuracy of document annotation and search relevance.
      • How to Use: Implement labeled spans to improve document indexing and search precision.
1414. Labeled Spans (NlpSaftLabeledSpans)
      • Description: Contains a list of labeled spans of the same type within a document.
      • SEO Purpose: Improves the accuracy and relevance of document annotation.
      • How to Use: Use labeled spans to enhance document indexing and search precision.
1415. Measure (NlpSaftMeasure)
      • Description: Represents measures within documents, such as time expressions and physical quantities.
      • SEO Purpose: Enhances the accuracy of content indexing and relevance.
      • How to Use: Implement measures to improve the precision of content indexing and search results.
1416. Entity Mention (NlpSaftMention)
      • Description: Refers to instances where an entity (e.g., person, place, or organization) is mentioned in a document. This factor helps identify and highlight relevant entities within the content.
      • SEO Purpose: Enhances content relevance and contextual understanding, improving how search engines match queries with content.
      • How to Use: Ensure entities are mentioned naturally and contextually within the content. Use structured data to markup entity mentions.
1417. Mention Resolution (NlpSaftMentionResolution)
      • Description: Resolves mentions by encoding the concept ID for a specific entity. It helps to disambiguate and accurately identify entities across different mentions.
      • SEO Purpose: Improves entity recognition and disambiguation, which enhances the precision of search results.
      • How to Use: Use unique identifiers (e.g., mid) for entities in your content. Consistently refer to entities by their established IDs where possible.
1418. Morphology (NlpSaftMorphology)
      • Description: Stores information about the morphology of a token, including its root form, tense, and other grammatical features. This factor aids in understanding the syntactic structure of the content.
      • SEO Purpose: Enhances natural language processing by providing detailed grammatical information, improving search engine comprehension of content.
      • How to Use: Write content with proper grammar and syntax. Use variations of key terms (e.g., plural forms, different tenses) to improve relevance.
1419. Document Phrase (NlpSaftPhrase)
      • Description: Marks a range of tokens in a document as a phrase, identifying coherent chunks of text that function together semantically.
      • SEO Purpose: Helps in understanding the context and meaning of phrases within the content, leading to better search result matching.
      • How to Use: Use clear and coherent phrases in content. Highlight key phrases using proper formatting and structure.
1420. Referent (NlpSaftReferent)
      • Description: Contains information about what a discourse context entity refers to, acting as a canonical mention of the entity.
      • SEO Purpose: Ensures that references to entities are clearly understood, improving content coherence and relevance.
      • How to Use: Maintain consistency when referring to entities. Use clear and unambiguous language to ensure accurate referent identification.
1421. Entity Relations (NlpSaftRelation)
      • Description: Identifies relationships between different entities within the document. Each relation is documented along with mentions.
      • SEO Purpose: Enhances the understanding of how entities are interconnected, which can improve the relevance of search results.
      • How to Use: Clearly describe relationships between entities in your content. Use structured data to define these relationships.
1422. Relation Mentions (NlpSaftRelationMention)
      • Description: Records mentions of relationships between entities in the document. This helps in mapping out the interactions between different entities.
      • SEO Purpose: Provides detailed context about entity relationships, improving the depth of content analysis.
      • How to Use: Explicitly mention and describe relationships between entities. Use examples and context to illustrate these relationships.
1423. Semantic Node (NlpSaftSemanticNode)
      • Description: Annotates semantic constructions in documents, representing them as a directed acyclic graph. Each node can link to entities, measures, or token spans.
      • SEO Purpose: Enhances semantic understanding of content by structuring it into meaningful nodes and relationships.
      • How to Use: Organize content logically, using clear headings and subheadings. Use structured data to annotate key semantic elements.
1424. Semantic Node Arc (NlpSaftSemanticNodeArc)
      • Description: Defines arcs between nodes in a directed acyclic graph, indicating directional relationships between different semantic nodes.
      • SEO Purpose: Clarifies the relationships and hierarchies within content, aiding in semantic search and content comprehension.
      • How to Use: Ensure logical flow and connectivity in content. Use structured data to define relationships between key concepts.
1425. Token (NlpSaftToken)
      • Description: Marks spans of bytes in the document text as tokens or words, essential for tokenizing and processing text data.
      • SEO Purpose: Facilitates natural language processing by clearly defining the smallest units of text.
      • How to Use: Write clear, well-structured content with proper spacing and punctuation. Use consistent terminology throughout the document.
1426. Article Data (NlpSciencelitArticleData)
      • Description: Contains the text of an article along with references to internal figures, external citations, datasets, and more.
      • SEO Purpose: Provides comprehensive content information, enhancing the depth and quality of the document.
      • How to Use: Include thorough and well-referenced content in articles. Use internal and external links to provide additional context and resources.
1427. Article ID (NlpSciencelitArticleId)
      • Description: Contains unique identifiers associated with an article, such as PMID, DOI, or PMC.
      • SEO Purpose: Ensures proper citation and retrieval of scientific articles, enhancing credibility and traceability.
      • How to Use: Always include accurate identifiers for scientific articles. Use proper citation formats to reference these IDs.
1428. Article Metadata (NlpSciencelitArticleMetadata)
      • Description: Stores metadata related to scientific articles, including publication details, authorship, and more.
      • SEO Purpose: Enhances the discoverability and indexing of scientific content by providing detailed metadata.
      • How to Use: Provide complete and accurate metadata for articles. Use structured data to mark up metadata fields.
1429. Author Information (NlpSciencelitAuthor)
      • Description: Captures the first and last names of authors, helping to attribute and identify the creators of the content.
      • SEO Purpose: Ensures accurate authorship information, enhancing credibility and traceability.
      • How to Use: Always include the full names of authors. Provide author bios and relevant credentials to establish authority.
1430. Citation Data (NlpSciencelitCitationData)
      • Description: Contains information about citations, including references to external works and datasets.
      • SEO Purpose: Enhances the credibility and depth of content by including relevant citations.
      • How to Use: Cite sources accurately. Use proper citation formats and include links to referenced works.
1431. Dataset Information (NlpSciencelitDataset)
      • Description: Stores details about datasets associated with the content, including metadata and associations.
      • SEO Purpose: Provides additional data resources, enhancing the comprehensiveness and utility of the content.
      • How to Use: Include detailed information about datasets used in research. Link to datasets and provide metadata for better discoverability.
1432. Mesh Heading (NlpSciencelitMeshHeading)
      • Description: Represents a full Mesh Heading containing descriptors and optional qualifiers, used for indexing and categorizing medical content.
      • SEO Purpose: Improves the categorization and discoverability of medical and scientific content through standardized headings.
      • How to Use: Use Mesh Headings to categorize medical content accurately. Ensure that headings and qualifiers are relevant to the content.
1433. Pub Date (NlpSciencelitPubDate)
      • Description: Extracts the publication date from PMC article metadata, providing a clear timeline for the content.
      • SEO Purpose: Ensures the timeliness and relevance of scientific articles by clearly indicating publication dates.
      • How to Use: Always include the publication date for articles. Ensure that dates are accurate and up-to-date.
1434. Publication Type (NlpSciencelitPublicationType)
      • Description: Describes the type of publication, such as “Journal Article,” using display names and unique identifiers.
      • SEO Purpose: Helps categorize content by publication type, enhancing its relevance and discoverability.
      • How to Use: Clearly indicate the type of publication. Use standardized terms and identifiers for different publication types.
1435. Referenced Block (NlpSciencelitReferencedBlock)
      • Description: Contains data associated with reference blocks in scientific articles, providing context and linkage to references.
      • SEO Purpose: Enhances the credibility and thoroughness of content by linking to relevant references.
      • How to Use: Include reference blocks in scientific articles. Provide clear and accurate references to support the content.
1436. Retrieval Query Debug Info (NlpSciencelitRetrievalQueryEncodingDebugInfo)
      • Description: Encodes the query used for retrieval, aiding in debugging and refining search algorithms.
      • SEO Purpose: Improves the accuracy and efficiency of search algorithms by providing detailed query information.
      • How to Use: Use query encoding to refine search algorithms. Monitor and debug search queries to enhance performance.
1437. Search Result Debug Info (NlpSciencelitRetrievalSearchResultDebugInfo)
      • Description: Provides debug information for search results returned by the Delver API, helping to analyze and improve search accuracy.
      • SEO Purpose: Enhances search result accuracy and relevance by providing detailed debug information.
      • How to Use: Use debug information to analyze and improve search results. Regularly review and refine search algorithms based on debug data.
1438. Search Result Set Debug Info (NlpSciencelitRetrievalSearchResultSetDebugInfo)
      • Description: Optionally returned by the Delver API in the response’s debug_info field, providing additional context for search result sets.
      • SEO Purpose: Provides detailed context for search result sets, aiding in the refinement and improvement of search algorithms.
      • How to Use: Review and utilize debug information for search result sets. Refine search algorithms based on insights gained from debug data.
1439. Snippet Debug Info (NlpSciencelitRetrievalSnippetDebugInfo)
      • Description: Provides debug information for snippets returned by the Delver API, helping to analyze and refine snippet generation.
      • SEO Purpose: Improves the accuracy and relevance of snippets by providing detailed debug information.
      • How to Use: Analyze snippet debug information to refine snippet generation. Ensure snippets accurately represent the content.
1440. Subject Heading (NlpSciencelitSubjectHeading)
      • Description: Represents a subject heading from MeSH, used to categorize and index content.
      • SEO Purpose: Enhances the categorization and discoverability of content through standardized subject headings.
      • How to Use: Use MeSH subject headings to categorize content accurately. Ensure that headings are relevant and properly applied.
1441. Tokenized Text (NlpSciencelitTokenizedText)
      • Description: Represents text that has been tokenized, with optional original representation preserved.
      • SEO Purpose: Facilitates natural language processing by breaking text into manageable tokens.
      • How to Use: Ensure content is well-structured and easily tokenizable. Preserve original text representation where necessary.
1442. Annotation Evaluation Data (NlpSemanticParsingAnnotationEvalData)
      • Description: Used for span-based evaluation metrics in training, aligning byte spans with token spans to save examples.
      • SEO Purpose: Enhances the accuracy of natural language processing models by providing detailed evaluation metrics.
      • How to Use: Use annotation evaluation data to train and refine NLP models. Align byte spans with token spans for accurate evaluations.
1443. App Annotation (NlpSemanticParsingAppAnnotation)
      • Description: Annotates potential app names in the parser’s input, outputting details about identified apps.
      • SEO Purpose: Improves the identification and relevance of app-related queries and content.
      • How to Use: Clearly mention app names in content. Use structured data to annotate and highlight app names.
1444. DateTime Annotation (NlpSemanticParsingDateTimeAnnotation)
      • Description: Annotates date and time expressions in content, such as “Friday” or “9am,” with corresponding date/time details.
      • SEO Purpose: Enhances the understanding and relevance of date/time-related content.
      • How to Use: Clearly state date and time expressions in content. Use structured data to annotate date and time information.
1445. Absolute DateTime (NlpSemanticParsingDatetimeAbsoluteDateTime)
      • Description: Represents resolved date/time expressions that need no further calculation, including both date and time sections.
      • SEO Purpose: Ensures the accuracy of date and time information in content, improving search relevance.
      • How to Use: Clearly specify absolute dates and times in content. Use structured data to mark up date and time information accurately.
1446. DateTime Representation (NlpSemanticParsingDatetimeDateTime)
      • Description: Top-level representation of date/time, which can include ranges, points, or recurrent expressions.
      • SEO Purpose: Enhances the understanding of complex date/time expressions, improving content relevance.
      • How to Use: Use clear and accurate date/time expressions. Utilize structured data to represent date/time ranges and points.
1447. DateTime Property (NlpSemanticParsingDatetimeDateTimeProperty)
      • Description: Contains metadata about the DateTime interpretation, providing additional context for date/time expressions.
      • SEO Purpose: Improves the understanding and relevance of date/time content by providing detailed metadata.
      • How to Use: Include relevant metadata for date/time expressions. Use structured data to mark up this information accurately.
1448. Duration (NlpSemanticParsingDatetimeDuration)
      • Description: Represents unanchored durations, indicating the length of time expressions without specific calendar references.
      • SEO Purpose: Enhances the understanding of duration-related content, improving search result accuracy.
      • How to Use: Clearly state durations in content. Use structured data to mark up duration information.
1449. Event (NlpSemanticParsingDatetimeEvent)
      • Description: Represents events that interact with date/time expressions, such as sunset or sunrise, and can be extended to include richer event information.
      • SEO Purpose: Enhances the understanding of event-related content, improving search relevance.
      • How to Use: Clearly describe events in content. Use structured data to annotate events and their interactions with date/time expressions.
1450. Fetched Relative DateTime (NlpSemanticParsingDatetimeFetchedRelativeDateTime)
      • Description: Represents relative datetime expressions fetched through operations, such as “next weekend” or “last two Mondays.”
      • SEO Purpose: Improves the understanding of relative datetime expressions, enhancing content relevance.
      • How to Use: Clearly state relative datetime expressions. Use structured data to mark up relative date/time information.
1451. Holiday (NlpSemanticParsingDatetimeHoliday)
      • Description: Lists holidays that are not fixed absolute or relative dates on the Gregorian calendar.
      • SEO Purpose: Enhances the understanding and relevance of holiday-related content.
      • How to Use: Include relevant holiday information in content. Use structured data to mark up holidays accurately.
1452. Moon Event Info (NlpSemanticParsingDatetimeMoonEventInfo)
      • Description: Contains information about moon phases and types, used for annotating lunar events.
      • SEO Purpose: Enhances the understanding of moon-related content, improving search relevance.
      • How to Use: Clearly describe lunar events in content. Use structured data to annotate moon phases and types.
1453. Non-Gregorian Date (NlpSemanticParsingDatetimeNonGregorianDate)
      • Description: Represents dates using non-Gregorian calendars, similar to AbsoluteDateTime but with different calendar systems.
      • SEO Purpose: Enhances the understanding of non-Gregorian date expressions, improving content relevance.
      • How to Use: Clearly state non-Gregorian dates in content. Use structured data to mark up non-Gregorian date information.
1454. Quantity (NlpSemanticParsingDatetimeQuantity)
      • Description: Represents quantities in date/time expressions, such as “3 days” or “5 minutes,” including modifiers and symbolic quantities.
      • SEO Purpose: Enhances the understanding of quantity-related content, improving search relevance.
      • How to Use: Clearly state quantities in date/time expressions. Use structured data to mark up quantity information accurately.
1455. DateTime Range (NlpSemanticParsingDatetimeRange)
      • Description: Represents ranges in date/time expressions, including explicit, fuzzy, and relative ranges.
      • SEO Purpose: Enhances the understanding of date/time ranges, improving content relevance.
      • How to Use: Clearly state date/time ranges in content. Use structured data to mark up range information accurately.
1456. Recurrent DateTime (NlpSemanticParsingDatetimeRecurrent)
      • Description: Represents recurrent date/time expressions, such as “every Monday” or “every morning starting from this Friday.”
      • SEO Purpose: Enhances the understanding of recurrent date/time expressions, improving search result accuracy.
      • How to Use: Clearly state recurrent date/time expressions. Use structured data to mark up recurrent date/time information.
1457. Relative DateTime (NlpSemanticParsingDatetimeRelativeDateTime)
      • Description: Provides a semi-abstract description for relative datetime expressions, such as “three days ago” or “2 days after March 1st.”
      • SEO Purpose: Improves the understanding of relative datetime expressions, enhancing content relevance.
      • How to Use: Clearly state relative datetime expressions. Use structured data to mark up relative date/time information.
1458. Resolution Properties (NlpSemanticParsingDatetimeResolutionProperties)
      • Description: Encapsulates metadata about the query span resolved, providing additional context for datetime resolutions.
      • SEO Purpose: Enhances the accuracy and relevance of datetime content by providing detailed resolution metadata.
      • How to Use: Include relevant metadata for datetime resolutions. Use structured data to mark up resolution information accurately.
1459. Shifted Relative DateTime (NlpSemanticParsingDatetimeShiftedRelativeDateTime)
      • Description: This ranking factor handles datetime expressions that are shifted relative to another datetime point. It includes details such as the base datetime, the type of base, metadata for tagging, relative base properties, shift amount, and direction (past or future).
      • SEO Purpose: Improves the accuracy and relevance of search results involving date and time expressions by correctly interpreting relative shifts.
      • How to Use: Ensure datetime expressions are clear and unambiguous. Use structured data to provide context for relative date and time references.
1460. Datetime Span (NlpSemanticParsingDatetimeSpan)
      • Description: Represents a specific byte offset and text of a span within the document, helping to identify precise sections of text.
      • SEO Purpose: Enhances the ability of search algorithms to pinpoint and highlight specific text spans, improving search precision.
      • How to Use: Clearly define and format important spans within your content. Use structured data to help search engines recognize these spans.
1461. Target to Fetch (NlpSemanticParsingDatetimeTargetToFetch)
      • Description: Identifies the target datetime that needs to be fetched, including specific details that help retrieve the correct date or time.
      • SEO Purpose: Ensures accurate retrieval of date/time information, enhancing the relevance of time-sensitive content.
      • How to Use: Specify clear and accurate datetime targets within your content. Use structured data to assist in the correct identification and retrieval of these targets.
1462. Time Zone (NlpSemanticParsingDatetimeTimeZone)
      • Description: Specifies the time zone information for datetime expressions, ensuring that the time is correctly interpreted based on geographic location.
      • SEO Purpose: Enhances the accuracy of time-sensitive search results by incorporating time zone data.
      • How to Use: Clearly indicate the time zone for datetime expressions in your content. Use structured data to markup time zone information.
1463. Entity Source Data (NlpSemanticParsingEntitySourceData)
      • Description: Provides information about the sources from which parts of an entity were retrieved, offering insight into the origin and credibility of the data.
      • SEO Purpose: Improves the trustworthiness and accuracy of entity-related content by clarifying data sources.
      • How to Use: Ensure that data sources are reliable and clearly documented. Use structured data to attribute the origins of entity information.
1464. Expression Status (NlpSemanticParsingExpressionStatus)
      • Description: Indicates whether the user has finished expressing their intended semantics during a streaming interaction. This status helps in detecting whether additional input is expected.
      • SEO Purpose: Enhances user interaction by accurately sensing when a user has completed their input, improving the handling of dynamic queries.
      • How to Use: Monitor user interactions to determine when input is complete. Use this data to optimize real-time query processing and responses.
1465. Local Amenities (NlpSemanticParsingLocalAmenities)
      • Description: Lists amenity constraints, representing various amenities that a location might offer. These constraints are combined using an implicit AND relationship.
      • SEO Purpose: Enhances local search results by specifying the amenities available at a location, improving user satisfaction.
      • How to Use: Clearly list amenities available at your location. Use structured data to annotate these amenities.
1466. Basic Location (NlpSemanticParsingLocalBasicLocation)
      • Description: Describes a single location, which can be a sequence of location elements. At least one element in the sequence must be an actual location.
      • SEO Purpose: Improves the accuracy and relevance of local search results by precisely defining locations.
      • How to Use: Provide clear and detailed descriptions of locations. Use structured data to mark up each location element.
1467. Business Type (NlpSemanticParsingLocalBusinessType)
      • Description: Categorizes business types, which can include various establishments such as hotels, restaurants, and more. Business types can match multiple categories.
      • SEO Purpose: Enhances local search results by accurately categorizing businesses, improving user discovery.
      • How to Use: Clearly categorize your business. Use structured data to mark up business types and relevant categories.
1468. Chain Member Constraint (NlpSemanticParsingLocalChainMemberConstraint)
      • Description: Provides constraints for filtering queries based on chain membership, useful for identifying locations that are part of a specific chain.
      • SEO Purpose: Enhances search precision by filtering results to include or exclude specific chains.
      • How to Use: Clearly indicate chain membership for your business. Use structured data to mark up chain-related information.
1469. Compound Location (NlpSemanticParsingLocalCompoundLocation)
      • Description: Describes locations that are combinations of two or more basic locations, connected by a joiner (e.g., “Starbucks near Central Park”).
      • SEO Purpose: Improves local search relevance by accurately representing complex location queries.
      • How to Use: Clearly describe compound locations in your content. Use structured data to mark up the components and joiners of these locations.
1470. Contact Location (NlpSemanticParsingLocalContactLocation)
      • Description: Provides contact information for a specific location, such as phone numbers or email addresses.
      • SEO Purpose: Enhances local search results by providing accurate contact details, improving user accessibility.
      • How to Use: Ensure contact information is up-to-date and clearly displayed. Use structured data to markup contact details.
1471. Cuisine Constraint (NlpSemanticParsingLocalCuisineConstraint)
      • Description: Specifies constraints for types of cuisine, such as “Chinese,” “Italian,” or “Thai.”
      • SEO Purpose: Improves search relevance for restaurant queries by specifying cuisine types.
      • How to Use: Clearly list the types of cuisine offered. Use structured data to mark up cuisine types.
1472. EV Charging Station Connector Constraint (NlpSemanticParsingLocalEvChargingStationConnectorConstraint)
      • Description: Specifies the types of connectors available at an EV charging station.
      • SEO Purpose: Enhances the relevance of search results for EV charging stations by detailing connector types.
      • How to Use: Clearly specify the types of connectors available at your EV charging station. Use structured data to mark up connector information.
1473. EV Charging Station Payment Constraint (NlpSemanticParsingLocalEvChargingStationPaymentConstraint)
      • Description: Details the payment methods accepted at an EV charging station.
      • SEO Purpose: Improves user experience by providing information on payment options for EV charging.
      • How to Use: Clearly list accepted payment methods. Use structured data to mark up payment options.
1474. EV Charging Station Speed Constraint (NlpSemanticParsingLocalEvChargingStationSpeedConstraint)
      • Description: Specifies the charging speeds available at an EV charging station.
      • SEO Purpose: Enhances search results for EV charging stations by providing detailed information on charging speeds.
      • How to Use: Clearly indicate the charging speeds offered. Use structured data to mark up charging speed information.
1475. Extent (NlpSemanticParsingLocalExtent)
      • Description: Represents the extent of a location, which can be described in units like distance or time. It can include non-specific values such as “a few.”
      • SEO Purpose: Enhances the precision of location-based queries by providing detailed extent information.
      • How to Use: Clearly specify the extent in location descriptions. Use structured data to mark up extent information.
1476. GCID Constraint (NlpSemanticParsingLocalGcidConstraint)
      • Description: Uses GCID (Google’s unique identifier for businesses) to specify constraints in search queries.
      • SEO Purpose: Improves the accuracy and relevance of search results by using unique identifiers for businesses.
      • How to Use: Ensure your business has a GCID and use it in structured data to improve search accuracy.
1477. Health Insurance Constraint (NlpSemanticParsingLocalHealthInsuranceConstraint)
      • Description: Specifies constraints related to health insurance networks for providers.
      • SEO Purpose: Enhances search results for healthcare providers by detailing accepted insurance networks.
      • How to Use: Clearly list accepted health insurance networks. Use structured data to mark up insurance information.
1478. Hotel Type (NlpSemanticParsingLocalHotelType)
      • Description: Differentiates between sub-classes of accommodations, such as hotels, motels, and guest houses.
      • SEO Purpose: Improves search relevance for accommodation queries by accurately categorizing hotel types.
      • How to Use: Clearly specify the type of accommodation. Use structured data to mark up hotel types.
1479. Hyper Reliable Data (NlpSemanticParsingLocalHyperReliableData)
      • Description: Contains information about hyper-reliable categories, used to ensure high accuracy in certain categories.
      • SEO Purpose: Enhances trust and accuracy in search results by highlighting hyper-reliable data.
      • How to Use: Ensure data accuracy and reliability in your content. Use structured data to highlight hyper-reliable information.
1480. Implicit Local Category (NlpSemanticParsingLocalImplicitLocalCategory)
      • Description: Flags indicating specific implicit intents, such as dining or travel.
      • SEO Purpose: Improves the accuracy of search results by recognizing implicit user intents.
      • How to Use: Clearly define and indicate implicit intents in your content. Use structured data to mark up these intents.
1481. Joiner (NlpSemanticParsingLocalJoiner)
      • Description: Represents the connecting text between two locations or elements in a query.
      • SEO Purpose: Enhances the understanding of complex queries by accurately interpreting joiners.
      • How to Use: Use clear and appropriate joiners in location descriptions. Use structured data to mark up joiners.
1482. Local Result ID (NlpSemanticParsingLocalLocalResultId)
      • Description: Holds information needed to look up a local result in search.
      • SEO Purpose: Ensures accurate retrieval of local search results by using specific result IDs.
      • How to Use: Include local result IDs in structured data to improve search accuracy.
1483. Location (NlpSemanticParsingLocalLocation)
      • Description: Describes various types of locations, including basic, compound, and vicinity locations.
      • SEO Purpose: Improves the accuracy and relevance of location-based search results.
      • How to Use: Provide detailed and accurate location descriptions. Use structured data to mark up different types of locations.
1484. Location Constraint (NlpSemanticParsingLocalLocationConstraint)
      • Description: Specifies constraints for locations, including compound and internal location elements.
      • SEO Purpose: Enhances search precision by applying specific location constraints.
      • How to Use: Clearly specify location constraints in your content. Use structured data to mark up these constraints.
1485. Location Element (NlpSemanticParsingLocalLocationElement)
      • Description: Represents individual elements of a location, which can be actual locations or modifiers.
      • SEO Purpose: Improves the granularity and precision of location-based search results.
      • How to Use: Clearly define and describe each location element. Use structured data to mark up these elements.
1486. Menu Item (NlpSemanticParsingLocalMenuItem)
      • Description: Specifies menu items as location constraints or standalone categorical elements.
      • SEO Purpose: Enhances search results for food-related queries by specifying menu items.
      • How to Use: Clearly list and describe menu items. Use structured data to mark up menu items.
1487. Price Constraint (NlpSemanticParsingLocalPriceConstraint)
      • Description: Represents constraints related to price, including ranges and currency codes.
      • SEO Purpose: Improves search relevance for price-sensitive queries.
      • How to Use: Clearly indicate price ranges and currency codes. Use structured data to mark up price constraints.
1488. Quality Constraint (NlpSemanticParsingLocalQualityConstraint)
      • Description: Specifies quality constraints, such as ratings and reviews.
      • SEO Purpose: Enhances search results by highlighting quality metrics.
      • How to Use: Clearly indicate quality metrics such as ratings and reviews. Use structured data to mark up quality information.
1489. Room Constraint (NlpSemanticParsingLocalRoomConstraint)
      • Description: Specifies constraints for room occupancy in hotels or vacation rentals.
      • SEO Purpose: Improves search results for accommodation queries by specifying room constraints.
      • How to Use: Clearly specify room occupancy constraints. Use structured data to mark up room information.
1490. Scalable Attribute (NlpSemanticParsingLocalScalableAttribute)
      • Description: Represents scalable attributes, which can be used as location constraints or standalone categorical elements.
      • SEO Purpose: Enhances search results by specifying scalable attributes such as “outdoor seating” or “happy hour.”
      • How to Use: Clearly list scalable attributes. Use structured data to mark up these attributes.
1491. Service Constraint (NlpSemanticParsingLocalServiceConstraint)
      • Description: Specifies constraints related to service types, such as delivery or dine-in.
      • SEO Purpose: Improves search relevance for service-related queries.
      • How to Use: Clearly indicate service types. Use structured data to mark up service constraints.
1492. Star Ratings (NlpSemanticParsingLocalStarRatings)
      • Description: Represents star rating constraints for establishments like hotels.
      • SEO Purpose: Enhances search results by specifying star ratings.
      • How to Use: Clearly indicate star ratings for your establishment. Use structured data to mark up star rating information.
1493. Vicinity Location (NlpSemanticParsingLocalVicinityLocation)
      • Description: Indicates the area around a certain location, defined by time or space.
      • SEO Purpose: Improves search precision for queries related to vicinity or proximity.
      • How to Use: Clearly specify vicinity locations. Use structured data to mark up proximity information.
1494. Visit History Constraint (NlpSemanticParsingLocalVisitHistoryConstraint)
      • Description: Specifies constraints based on whether a location has been visited before.
      • SEO Purpose: Enhances search results by considering visit history.
      • How to Use: Track and indicate visit history. Use structured data to mark up visit history constraints.
1495. Contact Type (NlpSemanticParsingModelsCommunicationPhoneType)
      • Description: Represents the type of contact, such as mobile, home, or work.
      • SEO Purpose: Improves search relevance for contact-related queries.
      • How to Use: Clearly indicate contact types. Use structured data to mark up contact information.
1496. Recipient (NlpSemanticParsingModelsCommunicationRecipient)
      • Description: Represents a recipient, which can be a person, business, email, or phone number.
      • SEO Purpose: Enhances search accuracy for queries involving specific recipients.
      • How to Use: Clearly specify recipient details. Use structured data to mark up recipient information.
1497. Relationship Argument (NlpSemanticParsingModelsCommunicationRelationshipArgument)
      • Description: Represents a relationship contact, providing context for relationship-based queries.
      • SEO Purpose: Improves search relevance for queries involving relationships.
      • How to Use: Clearly describe relationship contacts. Use structured data to mark up relationship information.
1498. Device (NlpSemanticParsingModelsDevice)
      • Description: Specifies the device for performing an action, including type and name.
      • SEO Purpose: Enhances search results by recognizing specific devices.
      • How to Use: Clearly indicate device types and names. Use structured data to mark up device information.
1499. Device Name (NlpSemanticParsingModelsDeviceName)
      • Description: Represents the name of a device, such as “Nexus 5” or “Nexus 10.”
      • SEO Purpose: Improves search relevance for device-related queries.
      • How to Use: Clearly specify device names. Use structured data to mark up device names.
1500. Dialog Referents (NlpSemanticParsingModelsDialogReferentsDialogReferents)
      • Description: Used to emit type annotations from dialog referents, helping to identify specific references in conversations.
      • SEO Purpose: Enhances search accuracy for queries involving dialog referents.
      • How to Use: Clearly indicate dialog referents. Use structured data to mark up referent information.
1501. List Selection (NlpSemanticParsingModelsDialogReferentsListSelection)
      • Description: Represents the user’s selection from a list of alternatives, providing context for choices made.
      • SEO Purpose: Improves search relevance for queries involving lists and selections.
      • How to Use: Clearly describe list selections. Use structured data to mark up selection information.
1502. Album Title (NlpSemanticParsingModelsMediaAlbumTitle)
      • Description: Represents the title of an album, enhancing the identification of music-related content.
      • SEO Purpose: Improves search accuracy for music-related queries by specifying album titles.
      • How to Use: Clearly indicate album titles. Use structured data to mark up album information.
1503. Audio (NlpSemanticParsingModelsMediaAudio)
      • Description: Represents a music recording, including details about the song and artist.
      • SEO Purpose: Enhances search results for music queries by providing detailed audio information.
      • How to Use: Clearly describe music recordings. Use structured data to mark up audio information.
1504. Audiobook Info (NlpSemanticParsingModelsMediaAudiobookInfo)
      • Description: Provides metadata for an audiobook, including title and author.
      • SEO Purpose: Improves search relevance for audiobook queries by providing detailed metadata.
      • How to Use: Clearly describe audiobooks. Use structured data to mark up audiobook information.
1505. Book (NlpSemanticParsingModelsMediaBook)
      • Description: Represents a book, including its title, such as “East of Eden.”
      • SEO Purpose: Enhances search accuracy for book-related queries by specifying titles.
      • How to Use: Clearly indicate book titles. Use structured data to mark up book information.
1506. Media Device Annotation (NlpSemanticParsingModelsMediaCastDeviceAnnotation)
      • Description: Represents a media device, such as a Chromecast or TV, used for casting media.
      • SEO Purpose: Improves search results for queries involving media devices.
      • How to Use: Clearly specify media devices. Use structured data to mark up device information.
1507. Media Cost (NlpSemanticParsingModelsMediaCost)
      • Description: Represents the localized price of media content.
      • SEO Purpose: Enhances search relevance for queries involving media costs.
      • How to Use: Clearly indicate media prices. Use structured data to mark up cost information.
1508. Deeplink Info (NlpSemanticParsingModelsMediaDeeplinkInfo)
      • Description: Provides deeplink information and associated metadata, including platform restrictions and user subscriptions.
      • SEO Purpose: Enhances user experience by providing direct links to media content.
      • How to Use: Clearly specify deeplink URLs. Use structured data to mark up deeplink information.
1509. Deeplink Info Time Window (NlpSemanticParsingModelsMediaDeeplinkInfoTimeWindow)
      • Description: Represents a time window for deeplink access, expressed as a time range.
      • SEO Purpose: Improves search relevance for time-sensitive media content.
      • How to Use: Clearly indicate time windows for deeplink access. Use structured data to mark up time window information.
1510. Media Description (NlpSemanticParsingModelsMediaDescription)
      • Description: This factor captures free-form text descriptions of media content, such as “the episode with all of the comedians.”
      • SEO Purpose: Enhances the discoverability and relevance of media content by using descriptive phrases that match user queries.
      • How to Use: Include detailed and engaging descriptions of media content. Use keywords and phrases that potential viewers might search for.
1511. Episode Constraint (NlpSemanticParsingModelsMediaEpisodeConstraint)
      • Description: Specifies constraints for media episodes, such as “latest” to indicate a specific ordinal.
      • SEO Purpose: Improves the relevance of search results by allowing users to specify particular episodes.
      • How to Use: Clearly indicate the order or specific episodes in your content. Use structured data to mark up episode details.
1512. Radio Frequency (NlpSemanticParsingModelsMediaFrequency)
      • Description: Defines the frequency for terrestrial radio stations, such as 99.1 FM or 730 AM.
      • SEO Purpose: Enhances search relevance for radio station queries by specifying exact frequencies.
      • How to Use: Clearly indicate the frequency of your radio station. Use structured data to mark up frequency information.
1513. Game (NlpSemanticParsingModelsMediaGame)
      • Description: Represents a video game, such as “Deus Ex Human Revolution.”
      • SEO Purpose: Improves search results for video game queries by specifying game titles.
      • How to Use: Clearly list video game titles in your content. Use structured data to mark up game information.
1514. Generic Music (NlpSemanticParsingModelsMediaGenericMusic)
      • Description: Represents general music queries, such as “my library” or “some music.”
      • SEO Purpose: Enhances the relevance of music-related queries by accommodating general music requests.
      • How to Use: Use general terms to describe music collections. Use structured data to mark up generic music references.
1515. Latitude/Longitude (NlpSemanticParsingModelsMediaLatLng)
      • Description: Represents a geographic location using latitude and longitude coordinates.
      • SEO Purpose: Improves the accuracy of location-based queries by providing precise geographic data.
      • How to Use: Clearly indicate geographic coordinates in your content. Use structured data to mark up location information.
1516. Media Annotation (NlpSemanticParsingModelsMediaMediaAnnotation)
      • Description: Provides annotations for media entities, helping to categorize and describe media content.
      • SEO Purpose: Enhances the categorization and discoverability of media content through detailed annotations.
      • How to Use: Use annotations to provide additional context and metadata for media content. Use structured data to mark up annotations.
1517. Media Annotation List (NlpSemanticParsingModelsMediaMediaAnnotationList)
      • Description: A list of media annotations, used to annotate spans of media content.
      • SEO Purpose: Improves the accuracy and relevance of media-related search results by using comprehensive annotation lists.
      • How to Use: Compile detailed annotation lists for media content. Use structured data to mark up these lists.
1518. Media Provider Info (NlpSemanticParsingModelsMediaMediaProviderInfo)
      • Description: Contains information about media providers and their deeplinks, abstracting multiple media-related types.
      • SEO Purpose: Enhances the discoverability and user experience by linking to media providers and their content.
      • How to Use: Clearly specify media provider details and deeplinks. Use structured data to mark up provider information.
1519. Movie (NlpSemanticParsingModelsMediaMovie)
      • Description: Represents a movie, such as “Casablanca.”
      • SEO Purpose: Improves search relevance for movie queries by specifying movie titles.
      • How to Use: Clearly list movie titles in your content. Use structured data to mark up movie information.
1520. Music Artist (NlpSemanticParsingModelsMediaMusicArtist)
      • Description: Represents a music artist, such as “The Beatles.”
      • SEO Purpose: Enhances search results for music queries by specifying artist names.
      • How to Use: Clearly list music artist names in your content. Use structured data to mark up artist information.
1521. Music Genre (NlpSemanticParsingModelsMediaMusicGenre)
      • Description: Represents a music genre, such as “British Invasion.”
      • SEO Purpose: Improves the categorization and discoverability of music content by specifying genres.
      • How to Use: Clearly indicate music genres in your content. Use structured data to mark up genre information.
1522. Music Playlist (NlpSemanticParsingModelsMediaMusicPlaylist)
      • Description: Represents a music playlist, such as “gym playlist.”
      • SEO Purpose: Enhances the relevance of search results for playlist queries by specifying playlist names.
      • How to Use: Clearly list and describe playlists. Use structured data to mark up playlist information.
1523. News Info (NlpSemanticParsingModelsMediaNewsInfo)
      • Description: Provides metadata for news articles, including docid, content type, publication time, and publisher.
      • SEO Purpose: Improves the accuracy and relevance of news-related search results by providing detailed metadata.
      • How to Use: Include detailed metadata for news articles. Use structured data to mark up news information.
1524. News Topic (NlpSemanticParsingModelsMediaNewsTopic)
      • Description: Represents a news topic, such as “Ukraine” in a query like “read me news about Ukraine.”
      • SEO Purpose: Enhances search relevance for news queries by specifying topics.
      • How to Use: Clearly indicate news topics in your content. Use structured data to mark up topic information.
1525. Paid Offer Detail (NlpSemanticParsingModelsMediaPaidOfferDetail)
      • Description: Represents details for BUY and RENT offers, including associated costs.
      • SEO Purpose: Improves the relevance of search results for purchase-related queries by providing detailed offer information.
      • How to Use: Clearly list details for paid offers. Use structured data to mark up offer information.
1526. Podcast (NlpSemanticParsingModelsMediaPodcast)
      • Description: Represents a podcast, such as “This American Life.”
      • SEO Purpose: Enhances search relevance for podcast queries by specifying podcast titles.
      • How to Use: Clearly list podcast titles in your content. Use structured data to mark up podcast information.
1527. Podcast Info (NlpSemanticParsingModelsMediaPodcastInfo)
      • Description: Provides metadata for podcasts, including cluster ID, episode GUID, feed URL, and recommendation features.
      • SEO Purpose: Improves the discoverability and relevance of podcast content by providing detailed metadata.
      • How to Use: Include detailed metadata for podcasts. Use structured data to mark up podcast information.
1528. Provider Metadata (NlpSemanticParsingModelsMediaProviderMetadata)
      • Description: Contains metadata associated with video providers.
      • SEO Purpose: Enhances the relevance and accuracy of video-related search results by providing provider metadata.
      • How to Use: Clearly specify provider metadata for videos. Use structured data to mark up this information.
1529. Purchase Info (NlpSemanticParsingModelsMediaPurchaseInfo)
      • Description: Provides details about a purchase, including order type and purchase timestamp.
      • SEO Purpose: Improves search relevance for purchase-related queries by providing detailed purchase information.
      • How to Use: Clearly indicate purchase details. Use structured data to mark up purchase information.
1530. Media Quantification (NlpSemanticParsingModelsMediaQuantification)
      • Description: Quantifies devices in a query, such as “three speakers” or “all TVs.”
      • SEO Purpose: Enhances search accuracy for queries involving multiple devices by specifying quantifications.
      • How to Use: Clearly indicate quantities of devices. Use structured data to mark up quantification information.
1531. Radio (NlpSemanticParsingModelsMediaRadio)
      • Description: Represents a radio station, such as “107.7 The Bone.”
      • SEO Purpose: Improves search relevance for radio station queries by specifying station names.
      • How to Use: Clearly list radio station names in your content. Use structured data to mark up radio information.
1532. Radio Info (NlpSemanticParsingModelsMediaRadioInfo)
      • Description: Provides metadata for radio stations, including terrestrial and internet radio.
      • SEO Purpose: Enhances the relevance and accuracy of radio-related search results by providing detailed metadata.
      • How to Use: Include detailed metadata for radio stations. Use structured data to mark up radio information.
1533. Radio Network (NlpSemanticParsingModelsMediaRadioNetwork)
      • Description: Represents a radio network, such as “NPR” or “BBC.”
      • SEO Purpose: Improves search relevance for network-related radio queries by specifying network names.
      • How to Use: Clearly indicate radio network names. Use structured data to mark up network information.
1534. Rental Info (NlpSemanticParsingModelsMediaRentalInfo)
      • Description: Provides details for media rentals, including activation and grant periods, purchase timestamp, and validity.
      • SEO Purpose: Enhances search relevance for rental-related queries by providing detailed rental information.
      • How to Use: Clearly indicate rental details. Use structured data to mark up rental information.
1535. Season Constraint (NlpSemanticParsingModelsMediaSeasonConstraint)
      • Description: Specifies constraints for TV show seasons, such as “season 2” of a series.
      • SEO Purpose: Improves search relevance for TV show queries by specifying season information.
      • How to Use: Clearly indicate season numbers for TV shows. Use structured data to mark up season information.
1536. Song (NlpSemanticParsingModelsMediaSong)
      • Description: Represents a song, such as “Hey Jude.”
      • SEO Purpose: Enhances search relevance for music queries by specifying song titles.
      • How to Use: Clearly list song titles in your content. Use structured data to mark up song information.
1537. TV Show (NlpSemanticParsingModelsMediaTVShow)
      • Description: Represents a TV show, such as “Breaking Bad.”
      • SEO Purpose: Improves search relevance for TV show queries by specifying show titles.
      • How to Use: Clearly list TV show titles in your content. Use structured data to mark up TV show information.
1538. YouTube Deeplink Info (NlpSemanticParsingModelsMediaYouTubeDeeplinkInfo)
      • Description: Provides deeplink information specific to YouTube media assets.
      • SEO Purpose: Enhances user experience by providing direct links to YouTube content.
      • How to Use: Clearly specify deeplink URLs for YouTube content. Use structured data to mark up deeplink information.
1539. YouTube Playlist Info (NlpSemanticParsingModelsMediaYouTubePlaylistInfo)
      • Description: Provides details about YouTube playlists, including the number of videos playable in WoodStock and total video count.
      • SEO Purpose: Improves the relevance of search results for YouTube playlists by providing detailed playlist information.
      • How to Use: Clearly list details for YouTube playlists. Use structured data to mark up playlist information.
1540. Currency (NlpSemanticParsingModelsMoneyCurrency)
      • Description: Represents a currency, identified by its knowledge graph identifier.
      • SEO Purpose: Enhances search relevance for queries involving currencies by providing specific identifiers.
      • How to Use: Clearly indicate currency identifiers. Use structured data to mark up currency information.
1541. Money (NlpSemanticParsingModelsMoneyMoney)
      • Description: Represents a quantity of money.
      • SEO Purpose: Improves search relevance for queries involving monetary amounts.
      • How to Use: Clearly specify monetary amounts in your content. Use structured data to mark up money information.
1542. News Provider (NlpSemanticParsingModelsNarrativeNewsNewsProvider)
      • Description: Corresponds to an entry in a curated table of news providers.
      • SEO Purpose: Enhances the credibility and relevance of news-related content by specifying news providers.
      • How to Use: Clearly indicate news provider names. Use structured data to mark up provider information.
1543. On Device (NlpSemanticParsingModelsOnDevice)
      • Description: Describes the device(s) to perform an action, useful for specifying target devices in commands.
      • SEO Purpose: Enhances the accuracy of device-specific queries by specifying target devices.
      • How to Use: Clearly indicate target devices for actions. Use structured data to mark up device information.
1544. Person (NlpSemanticParsingModelsPersonPerson)
      • Description: Represents a person, including details such as name, contact data, and alternative names.
      • SEO Purpose: Improves search relevance for queries involving people by providing detailed personal information.
      • How to Use: Clearly indicate personal details. Use structured data to mark up person information.
1545. Recurrence (NlpSemanticParsingModelsRecurrence)
      • Description: Specifies rules for date- and time-based repetition for tasks, such as daily, weekly, monthly, or yearly patterns.
      • SEO Purpose: Enhances the relevance of search results for recurring events by providing detailed recurrence information.
      • How to Use: Clearly indicate recurrence rules for events. Use structured data to mark up recurrence information.
1546. Brand Phrase (NlpSemanticParsingModelsShoppingAssistantBrandPhrase)
      • Description: Represents a brand, which can be any combination of text or knowledge graph identifier.
      • SEO Purpose: Improves search relevance for brand-related queries by specifying brand names.
      • How to Use: Clearly indicate brand names in your content. Use structured data to mark up brand information.
1547. Merchant (NlpSemanticParsingModelsShoppingAssistantMerchant)
      • Description: Represents a merchant that sells products.
      • SEO Purpose: Enhances search relevance for queries involving merchants by specifying merchant names.
      • How to Use: Clearly indicate merchant names. Use structured data to mark up merchant information.
1548. Merchant Center ID (NlpSemanticParsingModelsShoppingAssistantMerchantMerchantCenterId)
      • Description: Represents a merchant center ID, capturing multiple IDs for different purposes.
      • SEO Purpose: Improves the accuracy and relevance of search results involving merchant center IDs.
      • How to Use: Clearly indicate merchant center IDs. Use structured data to mark up ID information.
1549. Offer (NlpSemanticParsingModelsShoppingAssistantOffer)
      • Description: Represents a product for sale from a particular merchant, possibly available at a specific store.
      • SEO Purpose: Enhances search relevance for product offers by specifying offer details.
      • How to Use: Clearly indicate offer details in your content. Use structured data to mark up offer information.
1550. Phrase (NlpSemanticParsingModelsShoppingAssistantPhrase)
      • Description: Represents a phrase parsed from a user query, useful for understanding search intent.
      • SEO Purpose: Improves search accuracy by understanding the context and intent behind user queries.
      • How to Use: Clearly indicate phrases in your content. Use structured data to mark up phrase information.
1551. Product (NlpSemanticParsingModelsShoppingAssistantProduct)
      • Description: Represents a product that can be purchased.
      • SEO Purpose: Enhances search relevance for product-related queries by specifying product details.
      • How to Use: Clearly list product details in your content. Use structured data to mark up product information.
1552. Product Classification (NlpSemanticParsingModelsShoppingAssistantProductClassification)
      • Description: Classifies products into specific categories, such as “video games.”
      • SEO Purpose: Improves the categorization and discoverability of products by specifying categories.
      • How to Use: Clearly indicate product categories. Use structured data to mark up classification information.
1553. Product Expression (NlpSemanticParsingModelsShoppingAssistantProductExpression)
      • Description: Represents an expression parsed from a user query that describes a product or set of products.
      • SEO Purpose: Enhances search relevance by understanding the context and intent behind product-related queries.
      • How to Use: Clearly indicate product expressions in your content. Use structured data to mark up expression information.
1554. Media Product (NlpSemanticParsingModelsShoppingAssistantProductMediaProduct)
      • Description: Represents a media product that can be purchased, such as a book or album.
      • SEO Purpose: Improves search relevance for media product queries by specifying product details.
      • How to Use: Clearly list media product details in your content. Use structured data to mark up media product information.
1555. Media Attribute Value (NlpSemanticParsingModelsShoppingAssistantProductMediaProductMediaAttributeValue)
      • Description: Represents the knowledge graph identifier and raw text of a media attribute, such as an author.
      • SEO Purpose: Enhances search relevance for media-related queries by providing detailed attribute information.
      • How to Use: Clearly indicate media attribute values. Use structured data to mark up attribute information.
1556. Product Phrase (NlpSemanticParsingModelsShoppingAssistantProductPhrase)
      • Description: Represents a product using a combination of raw text and metadata.
      • SEO Purpose: Improves search relevance for product-related queries by specifying product phrases.
      • How to Use: Clearly indicate product phrases in your content. Use structured data to mark up phrase information.
1557. Shopping List Item Info (NlpSemanticParsingModelsShoppingAssistantShoppingListItemInfo)
      • Description: Provides details about items on a shopping list, including item ID and list ID.
      • SEO Purpose: Enhances search relevance for shopping list queries by providing detailed item information.
      • How to Use: Clearly indicate shopping list item details. Use structured data to mark up item information.
1558. Store (NlpSemanticParsingModelsShoppingAssistantStore)
      • Description: Represents a merchant’s physical store.
      • SEO Purpose: Improves search relevance for store-related queries by specifying store details.
      • How to Use: Clearly indicate store details. Use structured data to mark up store information.
1559. Unrecognized Phrase (NlpSemanticParsingModelsShoppingAssistantUnrecognizedPhrase)
      • Description: Represents a span in a user query that could not be identified as any other type of phrase.
      • SEO Purpose: Enhances the accuracy of search results by identifying unrecognized phrases.
      • How to Use: Clearly indicate unrecognized phrases in your content. Use structured data to mark up these phrases.
1560. Fraction Number (NlpSemanticParsingNumberFractionNumber)
      • Description: This ranking factor deals with fraction numbers, capturing details such as the numerator, denominator, precision (number of digits after the decimal point), and whole number for mixed fractions.
      • SEO Purpose: Enhances the precision of numeric content interpretation, ensuring fractions are correctly understood and displayed in search results.
      • How to Use: Use clear and accurate fraction representations in content. Ensure fractions are properly formatted and contextualized.
1561. Number (NlpSemanticParsingNumberNumber)
      • Description: Represents numeric values, crucial for interpreting and processing numbers in content.
      • SEO Purpose: Ensures accurate understanding and ranking of content involving numeric values.
      • How to Use: Clearly specify numeric values in content. Use structured data to mark up numbers for better search engine comprehension.
1562. Simple Number (NlpSemanticParsingNumberSimpleNumber)
      • Description: Represents simple numeric values without complex fractions or mixed numbers.
      • SEO Purpose: Enhances the relevance of search results involving straightforward numeric data.
      • How to Use: Use simple and clear numeric values in content. Ensure numbers are easily readable and properly formatted.
1563. Personal Intelligence Entity (NlpSemanticParsingPersonalIntelligenceEntity)
      • Description: Represents personal intelligence entities, wire-equivalent to the Entity proto defined in personal intelligence models.
      • SEO Purpose: Improves personalization and relevance of search results by understanding user-specific entities.
      • How to Use: Include detailed and accurate personal entity information. Use structured data to mark up personal intelligence entities.
1564. Personal Reference Annotation (NlpSemanticParsingPersonalReferenceAnnotation)
      • Description: Contains QRefAnnotations designating personal references and resolutions, used for personalized intents like “navigate to my hotel.”
      • SEO Purpose: Enhances personalization in search results by accurately interpreting personal references.
      • How to Use: Clearly specify personal references in content. Use structured data to mark up personal reference annotations.
1565. Google Actions Slot (NlpSemanticParsingProtoActionsOnGoogleAogSlot)
      • Description: Represents NLU slots that can contain multiple possible values, including complex tree structures and list parameters.
      • SEO Purpose: Improves the accuracy and functionality of Google Actions by understanding user input slots.
      • How to Use: Clearly define slot values in content. Use structured data to mark up Google Actions slots.
1566. Google Actions DateTime (NlpSemanticParsingProtoActionsOnGoogleDateTime)
      • Description: Represents datetime values, including date, time, and date-time. Tracks hours and minutes but omits seconds.
      • SEO Purpose: Enhances the relevance of search results involving datetime queries.
      • How to Use: Clearly specify date and time values in content. Use structured data to mark up datetime information.
1567. Google Actions DateTime Property (NlpSemanticParsingProtoActionsOnGoogleDateTimeProperty)
      • Description: Represents properties about matched datetime values, providing additional context for date, time, and date-time values.
      • SEO Purpose: Improves the accuracy of datetime interpretations in search results.
      • How to Use: Include detailed datetime properties in content. Use structured data to mark up datetime properties.
1568. Google Actions Slot List (NlpSemanticParsingProtoActionsOnGoogleSlotList)
      • Description: Injects a list as a possible value into a slot, used for handling lists in Google Actions.
      • SEO Purpose: Enhances the functionality of Google Actions by accurately interpreting list values.
      • How to Use: Clearly define list values in content. Use structured data to mark up slot lists.
1569. Google Actions Slot Map (NlpSemanticParsingProtoActionsOnGoogleSlotMap)
      • Description: Injects a map as a possible value into a slot, used for handling maps in Google Actions.
      • SEO Purpose: Improves the accuracy of map-based slot interpretations in Google Actions.
      • How to Use: Clearly define map values in content. Use structured data to mark up slot maps.
1570. Google Actions Slot Value (NlpSemanticParsingProtoActionsOnGoogleSlotValue)
      • Description: Contains one or more possible values for a slot, used in Google Actions.
      • SEO Purpose: Enhances the relevance and accuracy of search results involving slot values.
      • How to Use: Clearly specify slot values in content. Use structured data to mark up slot value information.
1571. Google Actions Slot Value Single (NlpSemanticParsingProtoActionsOnGoogleSlotValueSingleValue)
      • Description: Represents an actual value for a slot in Google Actions.
      • SEO Purpose: Improves the precision of slot value interpretations in Google Actions.
      • How to Use: Clearly define single slot values in content. Use structured data to mark up single slot values.
1572. Google Actions Typed Value (NlpSemanticParsingProtoActionsOnGoogleTypedValue)
      • Description: Contains information about the type of slot value returned by on-device Heron.
      • SEO Purpose: Enhances the accuracy of slot value types in Google Actions.
      • How to Use: Clearly specify typed values in content. Use structured data to mark up typed value information.
1573. QRef Annotation (NlpSemanticParsingQRefAnnotation)
      • Description: Annotates spans of input with freebase-ids and collection information.
      • SEO Purpose: Improves the relevance and accuracy of entity-related search results.
      • How to Use: Clearly annotate entities with freebase-ids. Use structured data to mark up QRef annotations.
1574. QRef Collection Membership (NlpSemanticParsingQRefAnnotationCollectionMembership)
      • Description: Indicates the collection membership of an entity, providing relevance scores.
      • SEO Purpose: Enhances the categorization and discoverability of entity-related content.
      • How to Use: Clearly specify collection memberships in content. Use structured data to mark up collection membership information.
1575. QRef Entity Relationship (NlpSemanticParsingQRefAnnotationEntityRelationship)
      • Description: Represents relationships between entities, including implied relationships and link property names.
      • SEO Purpose: Improves the understanding of entity relationships, enhancing the relevance of search results.
      • How to Use: Clearly indicate relationships between entities. Use structured data to mark up entity relationship information.
1576. Merlot Category Data (NlpSemanticParsingQRefAnnotationMerlotCategoryData)
      • Description: Contains category information derived from collection membership.
      • SEO Purpose: Enhances the categorization and discoverability of content by providing detailed category data.
      • How to Use: Clearly specify category data in content. Use structured data to mark up Merlot category information.
1577. QRef SubCluster (NlpSemanticParsingQRefAnnotationSubCluster)
      • Description: Tracks individual clusters that an entity is a member of, providing cluster-specific information.
      • SEO Purpose: Improves the accuracy and relevance of search results by understanding entity subclusters.
      • How to Use: Clearly indicate subcluster memberships in content. Use structured data to mark up subcluster information.
1578. Related Entity (NlpSemanticParsingRelatedEntity)
      • Description: Stores relationships between annotations and other entities, including types of relationships.
      • SEO Purpose: Enhances the understanding of entity relationships, improving search relevance.
      • How to Use: Clearly specify relationships between entities. Use structured data to mark up related entity information.
1579. Coreference (NlpSemanticParsingSaftCoreference)
      • Description: Identifies coreference mentions (pronouns or nominals) resolved to an entity.
      • SEO Purpose: Improves the accuracy of content interpretation by resolving coreferences.
      • How to Use: Ensure coreferences are clear and correctly resolved in content. Use structured data to mark up coreference information.
1580. Measure (NlpSemanticParsingSaftMeasure)
      • Description: Identifies measures in queries, such as weights or quantities.
      • SEO Purpose: Enhances the precision of search results involving measures by accurately interpreting quantities.
      • How to Use: Clearly specify measures in content. Use structured data to mark up measure information.
1581. Mention Annotation (NlpSemanticParsingSaftMentionAnnotation)
      • Description: Identifies sub-spans of input with semantic relevance, such as persons, locations, or measures.
      • SEO Purpose: Improves the categorization and discoverability of content by highlighting semantically relevant spans.
      • How to Use: Clearly annotate semantically relevant spans in content. Use structured data to mark up mention annotations.
1582. Span (NlpSemanticParsingSaftSpan)
      • Description: Defines a category for a sub-span of the raw text of a query.
      • SEO Purpose: Enhances the precision of content interpretation by categorizing text spans.
      • How to Use: Clearly specify and categorize spans in content. Use structured data to mark up span information.
1583. Byte (NlxDataSchemaByte)
      • Description: Represents a single byte from a UTF-8 encoded character sequence.
      • SEO Purpose: Improves the precision of content interpretation at the byte level.
      • How to Use: Ensure content is properly encoded. Use structured data to mark up byte-level information.
1584. Character (NlxDataSchemaCharacter)
      • Description: Represents a single Unicode character.
      • SEO Purpose: Enhances the accuracy of content interpretation at the character level.
      • How to Use: Ensure content uses proper Unicode characters. Use structured data to mark up character-level information.
1585. Document (NlxDataSchemaDocument)
      • Description: Represents a single document.
      • SEO Purpose: Improves the discoverability and relevance of documents by clearly defining them.
      • How to Use: Clearly define and describe documents in content. Use structured data to mark up document information.
1586. Entity (NlxDataSchemaEntity)
      • Description: Represents an entity that may occur multiple times in the text.
      • SEO Purpose: Enhances the relevance of content by accurately identifying entities.
      • How to Use: Clearly specify entities in content. Use structured data to mark up entity information.
1587. Language Span (NlxDataSchemaLanguageSpan)
      • Description: Represents a span of text written in a specified language or languages.
      • SEO Purpose: Improves the relevance of multilingual content by accurately identifying language spans.
      • How to Use: Clearly specify language spans in content. Use structured data to mark up language information.
1588. Mention (NlxDataSchemaMention)
      • Description: Represents a mention of an entity, which may occur multiple times.
      • SEO Purpose: Enhances the accuracy of entity-related content by identifying mentions.
      • How to Use: Clearly specify mentions in content. Use structured data to mark up mention information.
1589. Paragraph (NlxDataSchemaParagraph)
      • Description: Represents a single paragraph.
      • SEO Purpose: Improves the readability and structure of content by clearly defining paragraphs.
      • How to Use: Clearly format paragraphs in content. Use structured data to mark up paragraph information.
1590. Scale Set (NlxDataSchemaScaleSet)
      • Description: Represents a standard set of scales.
      • SEO Purpose: Enhances the accuracy of content interpretation by providing standard scales.
      • How to Use: Clearly specify scales in content. Use structured data to mark up scale information.
1591. Sentence (NlxDataSchemaSentence)
      • Description: Represents a single sentence or utterance.
      • SEO Purpose: Improves the readability and structure of content by clearly defining sentences.
      • How to Use: Clearly format sentences in content. Use structured data to mark up sentence information.
1592. Token (NlxDataSchemaToken)
      • Description: Represents a word, punctuation mark, or other small piece of text.
      • SEO Purpose: Enhances the precision of content interpretation by accurately identifying tokens.
      • How to Use: Clearly specify tokens in content. Use structured data to mark up token information.
1593. Token Dependency Edge (NlxDataSchemaTokenDependencyEdge)
      • Description: (Deprecated) Represents one edge of the dependency parse.
      • SEO Purpose: Previously improved the accuracy of syntactic parsing.
      • How to Use: Use current fields like dependency_head and dependency_label for dependency parsing.
1594. Woodwing Item Metadata (OceanDataDocinfoWoodwingItemMetadata)
      • Description: Provides metadata describing an ‘item’ (article) in a Woodwing file.
      • SEO Purpose: Enhances the discoverability and relevance of articles by providing detailed metadata.
      • How to Use: Include detailed metadata for articles. Use structured data to mark up Woodwing item information.
1595. Ocean Document Info (OceanDocInfo)
      • Description: Represents ocean data in docserver results for whole documents.
      • SEO Purpose: Improves the relevance of search results for documents by providing detailed ocean data.
      • How to Use: Clearly specify ocean document data in content. Use structured data to mark up document information.
1596. Ocean Document Tag (OceanDocTag)
      • Description: Represents tags for ocean documents, enhancing their categorization.
      • SEO Purpose: Improves the discoverability and relevance of tagged content.
      • How to Use: Clearly specify tags for documents. Use structured data to mark up tag information.
1597. Book Specific Tag (OceanDocTagBookSpecific)
      • Description: Contains fields specific to books.
      • SEO Purpose: Enhances the relevance of book-related content by providing specific tags.
      • How to Use: Clearly specify book-specific tags. Use structured data to mark up book information.
1598. Book Specific Numbering Range (OceanDocTagBookSpecificNumberingRange)
      • Description: Provides volume numbering information, such as “Volume 1” or “Parts A-D.”
      • SEO Purpose: Improves the organization and discoverability of serialized content by specifying numbering ranges.
      • How to Use: Clearly indicate volume and part numbers in content. Use structured data to mark up numbering information.
1599. Catalog Specific Fields (OceanDocTagCatalogSpecific)
      • Description: These fields are specific to catalogs and provide detailed information relevant to catalog items.
      • SEO Purpose: Enhances search relevance for catalog-specific queries by providing detailed metadata.
      • How to Use: Clearly specify catalog-specific information. Use structured data to mark up catalog-specific fields.
1600. Contributor Information (OceanDocTagContributor)
      • Description: Provides a composite descriptor of contributors, including authors and editors.
      • SEO Purpose: Improves the relevance of search results by accurately identifying contributors.
      • How to Use: Clearly list and describe contributors. Use structured data to mark up contributor information.
1601. Magazine Specific Fields (OceanDocTagMagazineSpecific)
      • Description: Contains fields specific to magazines, providing detailed metadata.
      • SEO Purpose: Enhances the discoverability and relevance of magazine-related content.
      • How to Use: Clearly indicate magazine-specific information. Use structured data to mark up magazine-specific fields.
1602. Newspaper Specific Fields (OceanDocTagNewspaperSpecific)
      • Description: Contains fields specific to newspapers, offering detailed metadata.
      • SEO Purpose: Improves the relevance of search results for newspaper-related queries.
      • How to Use: Clearly specify newspaper-specific information. Use structured data to mark up newspaper-specific fields.
1603. Patent Specific Fields (OceanDocTagPatentSpecific)
      • Description: Contains fields specific to patents. Currently empty but intended for future use.
      • SEO Purpose: Enhances the relevance of search results for patent-related queries.
      • How to Use: Clearly indicate patent-specific information when available. Use structured data to mark up patent-specific fields.
1604. Work Cluster Details (OceanDocTagWorkCluster)
      • Description: Provides details of the work cluster for a volume.
      • SEO Purpose: Improves the organization and relevance of content by grouping related works.
      • How to Use: Clearly specify work cluster details. Use structured data to mark up work cluster information.
1605. GE Money Container (OceanGEMoney)
      • Description: Stores price information for GE (Google Editions) sales.
      • SEO Purpose: Enhances the accuracy of search results involving price information.
      • How to Use: Clearly specify prices in content. Use structured data to mark up price information.
1606. GE Price Data (OceanGEPrice)
      • Description: Contains data related to GE sales, including pricing and sale details.
      • SEO Purpose: Improves the relevance of search results for sale-related queries.
      • How to Use: Clearly specify sale details and prices. Use structured data to mark up GE price information.
1607. GE Price Locale (OceanGEPriceLocale)
      • Description: Provides locale-specific price information, including country code and offer price.
      • SEO Purpose: Enhances the relevance of search results by providing localized pricing information.
      • How to Use: Clearly specify locale-specific prices. Use structured data to mark up price information for different locales.
1608. Image Size (OceanImageSize)
      • Description: Provides size information for images.
      • SEO Purpose: Enhances the accuracy of search results involving images by providing size details.
      • How to Use: Clearly specify image sizes in content. Use structured data to mark up image size information.
1609. Locale Viewability (OceanLocaleViewability)
      • Description: Describes how a volume may be viewed in a particular locale.
      • SEO Purpose: Improves the relevance of search results by providing viewability information for different locales.
      • How to Use: Clearly specify viewability details for different locales. Use structured data to mark up viewability information.
1610. Viewability Dates (OceanLocaleViewabilityDates)
      • Description: Provides dates related to viewability.
      • SEO Purpose: Enhances the relevance of time-sensitive content by providing viewability dates.
      • How to Use: Clearly indicate viewability dates. Use structured data to mark up date information.
1611. Viewability Source Details (OceanLocaleViewabilitySourceDetails)
      • Description: Details how viewability for a locale and volume is derived, including partner and imprint information.
      • SEO Purpose: Improves the credibility and relevance of content by providing source details.
      • How to Use: Clearly specify viewability source details. Use structured data to mark up source information.
1612. Per-Doc Data (OceanPerDocData)
      • Description: Provides per-document data in the Ocean index, detailing indexing specifics.
      • SEO Purpose: Enhances search accuracy by providing detailed indexing information.
      • How to Use: Clearly indicate per-document data. Use structured data to mark up indexing details.
1613. Volume Access Rights (OceanVolumeAccessRights)
      • Description: Specifies access rights for a volume, including download allowances, text-to-speech permissions, and viewability restrictions.
      • SEO Purpose: Improves the user experience by clearly defining access rights and restrictions.
      • How to Use: Clearly specify access rights and restrictions. Use structured data to mark up access rights information.
1614. Computed Access Rights (OceanVolumeComputedAccessRights)
      • Description: Provides computed access rights for a volume, complementing partner and book metadata.
      • SEO Purpose: Enhances the relevance of search results by providing detailed access rights information.
      • How to Use: Clearly indicate computed access rights. Use structured data to mark up computed access rights information.
1615. Display Details (OceanVolumeDisplayDetails)
      • Description: Describes display attributes for a volume, relevant for OFE and indexing.
      • SEO Purpose: Improves the discoverability and presentation of content by providing display details.
      • How to Use: Clearly specify display attributes. Use structured data to mark up display details.
1616. Volume Imprint (OceanVolumeImprint)
      • Description: Provides commercial information for a volume, detailing the imprint or publisher subdivision.
      • SEO Purpose: Enhances the relevance and discoverability of content by providing imprint details.
      • How to Use: Clearly specify imprint information. Use structured data to mark up imprint details.
1617. Volume Viewability (OceanVolumeViewability)
      • Description: Specifies viewability details for a volume, including default and locale-specific viewability.
      • SEO Purpose: Improves the relevance of search results by providing detailed viewability information.
      • How to Use: Clearly indicate viewability details. Use structured data to mark up viewability information.
1618. Volume Viewability Locale (OceanVolumeViewabilityLocale)
      • Description: Provides locale-specific viewability details for a volume.
      • SEO Purpose: Enhances the relevance of search results by specifying viewability for different locales.
      • How to Use: Clearly specify locale-specific viewability details. Use structured data to mark up viewability information for different locales.
1619. Photo Bounding Box (OcrPhotoBoundingBox)
      • Description: Defines the bounding box for a patch containing a line, word, or symbol in a photo.
      • SEO Purpose: Enhances the accuracy of image-related search results by providing bounding box details.
      • How to Use: Clearly specify bounding boxes for text in images. Use structured data to mark up bounding box information.
1620. Photo Curve (OcrPhotoCurve)
      • Description: Provides details about the curve of a bounding box for OCR in photos.
      • SEO Purpose: Improves the accuracy of OCR results by understanding text curves in images.
      • How to Use: Clearly indicate curve details for text in images. Use structured data to mark up curve information.
1621. Curve Point (OcrPhotoCurvePoint)
      • Description: Represents a point in a curve for OCR, specifying x and y coordinates.
      • SEO Purpose: Enhances the precision of OCR results by providing detailed curve point information.
      • How to Use: Clearly specify curve points for text in images. Use structured data to mark up curve point information.
1622. Curved Bounding Box (OcrPhotoCurvedBoundingBox)
      • Description: Defines a curved bounding box for OCR, including midline curve and thickness.
      • SEO Purpose: Improves the accuracy of OCR results by providing detailed curved bounding box information.
      • How to Use: Clearly specify curved bounding boxes for text in images. Use structured data to mark up curved bounding box information.
1623. Text Box (OcrPhotoTextBox)
      • Description: Represents text with a bounding box in an image.
      • SEO Purpose: Enhances the accuracy of text-related search results in images.
      • How to Use: Clearly specify text boxes in images. Use structured data to mark up text box information.
1624. Official Key (OfficialPagesOfficialKey)
      • Description: Used as the key for official pages data, containing normalized queries.
      • SEO Purpose: Improves the relevance and accuracy of search results for official pages.
      • How to Use: Clearly specify normalized queries for official pages. Use structured data to mark up official key information.
1625. Official Query Set (OfficialPagesQuerySet)
      • Description: Contains a set of official queries and their country-language fingerprints.
      • SEO Purpose: Enhances the relevance of search results by providing detailed query sets for official pages.
      • How to Use: Clearly specify official queries and their fingerprints. Use structured data to mark up query set information.
1626. Document Entities (OrionDocEntitiesProto)
      • Description: Represents entities within a document, including document ID and encoded entities.
      • SEO Purpose: Improves the relevance of search results by accurately identifying document entities.
      • How to Use: Clearly specify entities within documents. Use structured data to mark up entity information.
1627. Pairwise Scoring Data (PairwiseQScoringData)
      • Description: Provides scoring data for pairwise comparisons, including confidence values.
      • SEO Purpose: Enhances the accuracy of search result rankings by providing detailed scoring data.
      • How to Use: Clearly specify scoring data for pairwise comparisons. Use structured data to mark up scoring information.
1628. Versioned Pairwise Item (PairwiseQVersionedItem)
      • Description: Represents a versioned item for pairwise Q scores used in experimentation.
      • SEO Purpose: Improves the relevance of search result rankings by using versioned scoring data.
      • How to Use: Clearly specify versioned pairwise items. Use structured data to mark up versioned scoring information.
1629. Internal/External Flexorgs (PeoplestackFlexorgsProtoInternalExternal)
      • Description: Describes internal and external flexorgs within an application context.
      • SEO Purpose: Enhances the relevance of search results by accurately identifying internal and external organizations.
      • How to Use: Clearly specify flexorg information. Use structured data to mark up internal/external flexorg details.
1630. Flexorg State Status (PeoplestackFlexorgsProtoInternalExternalStateStatus)
      • Description: Represents the state status of internal and external flexorgs within a given context.
      • SEO Purpose: Improves the accuracy of search results by providing detailed state status information.
      • How to Use: Clearly specify state status for flexorgs. Use structured data to mark up state status information.
1631. Per-Doc Debug Event (PerDocDebugEvent)
      • Description: Contains free-form debug information from various components.
      • SEO Purpose: Enhances the transparency and troubleshooting capabilities of search indexing.
      • How to Use: Clearly specify debug information. Use structured data to mark up debug event information.
1632. Alias ID (PersonalizationMapsAliasAliasId)
      • Description: Provides a unique association of an alias type and a number to identify the alias.
      • SEO Purpose: Improves the relevance of personalized search results by accurately identifying aliases.
      • How to Use: Clearly specify alias IDs. Use structured data to mark up alias information.
1633. Alias Icon (PersonalizationMapsAliasIcon)
      • Description: Represents an alias icon used in search and maps to quickly display icons.
      • SEO Purpose: Enhances the visual relevance of search results by providing quick display icons.
      • How to Use: Clearly specify alias icons. Use structured data to mark up icon information.
1634. Local Discovery Settings Metadata (PersonalizationSettingsApiProtoLocalDiscoveryLocalDiscoverySettingsMetadata)
      • Description: Contains metadata related to local discovery settings, such as dietary restrictions and cuisine preferences.
      • SEO Purpose: Improves the personalization and relevance of local discovery search results.
      • How to Use: Clearly specify local discovery settings metadata. Use structured data to mark up settings information.
1635. OPA Recipes Context (PersonalizationSettingsApiProtoLocalDiscoveryOpaRecipesContext)
      • Description: Represents user preferences regarding recipes, such as disliked cuisines.
      • SEO Purpose: Enhances the personalization of search results for recipe queries.
      • How to Use: Clearly specify user preferences for recipes. Use structured data to mark up recipes context information.
1636. Phil Per-Doc Data (PhilPerDocData)
      • Description: Provides data specific to Phil, including versioning.
      • SEO Purpose: Enhances the relevance of search results by providing detailed per-doc data.
      • How to Use: Clearly specify Phil-specific data. Use structured data to mark up per-doc information.
1637. Animation Metadata (PhotosAnimationMetadata)
      • Description: Contains metadata about animations or movies, including duration, loop count, and number of frames.
      • SEO Purpose: Enhances the relevance of search results by providing detailed animation metadata.
      • How to Use: Clearly specify animation details such as duration and loop count. Use structured data to mark up animation metadata.
1638. Dynamic Depth Metadata (PhotosDynamicDepthMetadata)
      • Description: Indicates the presence of dynamic depth in images.
      • SEO Purpose: Improves the accuracy of search results by identifying images with dynamic depth.
      • How to Use: Clearly indicate the presence of dynamic depth in images. Use structured data to mark up dynamic depth metadata.
1639. FourC Metadata (PhotosFourCMetadata)
      • Description: Contains metadata such as captions, copyright information, creators, and credit for images.
      • SEO Purpose: Enhances the relevance and credibility of image-related content by providing detailed metadata.
      • How to Use: Clearly specify captions, copyright information, and creator details. Use structured data to mark up FourC metadata.
1640. GDepth Metadata (PhotosGDepthMetadata)
      • Description: Metadata related to the GDepth XMP block, detailing depth information in images.
      • SEO Purpose: Improves the accuracy of search results involving depth-related image content.
      • How to Use: Clearly specify GDepth metadata. Use structured data to mark up depth information.
1641. HDR Metadata (PhotosHdrMetadata)
      • Description: Describes how an image expresses high dynamic range (HDR) information, including gainmap or specialized color space.
      • SEO Purpose: Enhances the visual relevance of HDR images in search results.
      • How to Use: Clearly specify HDR details such as gainmap and color space. Use structured data to mark up HDR metadata.
1642. Gainmap HDR Metadata (PhotosHdrMetadataGainmap)
      • Description: Provides details about gainmap-based HDR formats, allowing images to adhere to multiple gainmap specifications.
      • SEO Purpose: Improves the visual relevance and discoverability of gainmap HDR images.
      • How to Use: Clearly specify gainmap details for HDR images. Use structured data to mark up gainmap HDR metadata.
1643. Image Metadata (PhotosImageMetadata)
      • Description: Contains comprehensive metadata for images.
      • SEO Purpose: Enhances the relevance and accuracy of image-related search results by providing detailed metadata.
      • How to Use: Clearly specify all relevant image metadata. Use structured data to mark up image details.
1644. Panorama Metadata (PhotosPanoramaMetadata)
      • Description: Provides metadata for panoramic images, including whether they are spherical or VR180.
      • SEO Purpose: Improves the relevance of search results involving panoramic images.
      • How to Use: Clearly specify panoramic details such as spherical or VR180 status. Use structured data to mark up panorama metadata.
1645. Normalized Bounding Box (PhotosVisionGroundtruthdbNormalizedBoundingBox)
      • Description: Defines bounding box coordinates relative to the width and height of the image.
      • SEO Purpose: Enhances the accuracy of object detection in images by providing bounding box details.
      • How to Use: Clearly specify bounding box coordinates. Use structured data to mark up bounding box information.
1646. Object Recognition Feature Vector (PhotosVisionObjectrecFeatureVector)
      • Description: Contains feature vector data for object recognition, using single precision floating point data.
      • SEO Purpose: Improves the accuracy of object recognition in images by providing detailed feature vectors.
      • How to Use: Clearly specify feature vector details. Use structured data to mark up object recognition feature vectors.
1647. Geo-Location (PhotosVisionObjectrecGeoLocation)
      • Description: Provides the geo-location of a single point or the “center” of a group of points in an image.
      • SEO Purpose: Enhances the relevance of geographically tagged images in search results.
      • How to Use: Clearly specify geo-location details. Use structured data to mark up geo-location information.
1648. Global Feature (PhotosVisionObjectrecGlobalFeature)
      • Description: Represents global features for the image.
      • SEO Purpose: Improves the relevance and accuracy of image-related search results by providing global feature data.
      • How to Use: Clearly specify global features. Use structured data to mark up global feature information.
1649. Image Template (PhotosVisionObjectrecImageTemplate)
      • Description: Contains local and/or global features generated from an image, used for object recognition.
      • SEO Purpose: Enhances the accuracy of object recognition in images by providing comprehensive feature templates.
      • How to Use: Clearly specify image template details. Use structured data to mark up image template information.
1650. Image Template SubSet (PhotosVisionObjectrecImageTemplateSubSet)
      • Description: Contains local descriptors of a specific type, indicating the algorithm used for generation.
      • SEO Purpose: Improves the accuracy of image recognition by providing detailed local descriptor information.
      • How to Use: Clearly specify local descriptor types. Use structured data to mark up image template subsets.
1651. Local Descriptor (PhotosVisionObjectrecLocalDescriptor)
      • Description: Holds interest point data and an optional local descriptor vector for object recognition.
      • SEO Purpose: Enhances the precision of object recognition in images by providing detailed local descriptors.
      • How to Use: Clearly specify local descriptors. Use structured data to mark up local descriptor information.
1652. Matrix 2D (PhotosVisionObjectrecMatrix2D)
      • Description: Represents a 2×2 float matrix.
      • SEO Purpose: Improves the accuracy of image transformations and object recognition.
      • How to Use: Clearly specify 2×2 float matrix data. Use structured data to mark up matrix information.
1653. Quantized Feature Vector (PhotosVisionObjectrecQuantizedFeatureVector)
      • Description: Contains quantized/compressed feature vector data, with 8 bits per value.
      • SEO Purpose: Enhances the efficiency and accuracy of image recognition by providing compressed feature vectors.
      • How to Use: Clearly specify quantized feature vector details. Use structured data to mark up quantized feature information.
1654. Region of Interest (PhotosVisionObjectrecROI)
      • Description: Defines a region of interest in an image.
      • SEO Purpose: Improves the accuracy of search results involving specific regions within images.
      • How to Use: Clearly specify regions of interest. Use structured data to mark up region of interest information.
1655. Porn Flag Data (PornFlagData)
      • Description: Stores data for URLs flagged as pornographic, including referer and optional image scores.
      • SEO Purpose: Enhances content moderation and filtering in search results by identifying flagged URLs.
      • How to Use: Clearly specify flagged URLs and related data. Use structured data to mark up porn flag information.
1656. Postal Address (PostalAddress)
      • Description: Represents postal address information.
      • SEO Purpose: Improves the relevance and accuracy of search results involving location data.
      • How to Use: Clearly specify postal addresses. Use structured data to mark up address information.
1657. Precomputed Restricts (PrecomputedRestricts)
      • Description: Contains restricts computed before building a search index.
      • SEO Purpose: Enhances search efficiency by precomputing restricts.
      • How to Use: Clearly specify precomputed restricts. Use structured data to mark up restrict information.
1658. Premium Per-Doc Data (PremiumPerDocData)
      • Description: Provides per-document data for premium documents in the Google index.
      • SEO Purpose: Enhances the relevance and discoverability of premium content.
      • How to Use: Clearly specify premium document details. Use structured data to mark up per-doc data for premium content.
1659. Proto2 Bridge Message Set (Proto2BridgeMessageSet)
      • Description: Proto2’s version of MessageSet, used for compatibility and data transfer.
      • SEO Purpose: Ensures compatibility and data integrity across different protocol buffer versions.
      • How to Use: Clearly specify message set details. Use structured data to mark up message set information.
1660. Pseudo Video Data (PseudoVideoData)
      • Description: Contains data for pseudo videos, used in indexing and search.
      • SEO Purpose: Enhances the relevance of search results for pseudo video content.
      • How to Use: Clearly specify pseudo video details. Use structured data to mark up pseudo video information.
1661. Pseudo Video Data Transcript (PseudoVideoDataTranscript)
      • Description: Provides a time-coded transcription of a document’s audio track.
      • SEO Purpose: Improves the relevance of search results for audio and video content by providing transcriptions.
      • How to Use: Clearly specify transcriptions for audio and video content. Use structured data to mark up transcript information.
1662. Transcript Timestamp (PseudoVideoDataTranscriptTimestamp)
      • Description: Maps time/character correspondences, used to link snippets to their corresponding time and thumbnail.
      • SEO Purpose: Enhances the user experience by accurately linking transcriptions to timestamps.
      • How to Use: Clearly specify timestamp mappings. Use structured data to mark up transcript timestamp information.
1663. PToken (PtokenPToken)
      • Description: Expresses policy-relevant properties of data objects processed and stored in Google’s systems.
      • SEO Purpose: Enhances data security and compliance by specifying policy-relevant properties.
      • How to Use: Clearly specify policy-related properties. Use structured data to mark up PToken information.
1664. App Info (QualityActionsAppInfo)
      • Description: Provides information about apps, including name, package name, and confidence levels.
      • SEO Purpose: Enhances the relevance of search results involving apps by providing detailed app information.
      • How to Use: Clearly specify app details. Use structured data to mark up app information.
1665. App Info Source Data (QualityActionsAppInfoSourceData)
      • Description: Contains source data for app information, including confidence and source type.
      • SEO Purpose: Improves the accuracy of app-related search results by providing detailed source data.
      • How to Use: Clearly specify source data for apps. Use structured data to mark up app source information.
1666. App Info Source Data Allow List (QualityActionsAppInfoSourceDataAllowListSourceData)
      • Description: Provides additional signals for apps from allow lists.
      • SEO Purpose: Enhances the relevance of app-related search results by using allow list signals.
      • How to Use: Clearly specify allow list source data. Use structured data to mark up allow list information.
1667. App Info Source Data Media Provider (QualityActionsAppInfoSourceDataMediaProviderSourceData)
      • Description: Specifies information about media content served by the app.
      • SEO Purpose: Improves the relevance of media-related app content in search results.
      • How to Use: Clearly specify media provider source data. Use structured data to mark up media provider information.
1668. App Understanding Category (QualityActionsAppUnderstandingCategory)
      • Description: Categorizes apps into specific categories based on their function.
      • SEO Purpose: Enhances the relevance of app-related search results by categorizing apps accurately.
      • How to Use: Clearly specify app categories. Use structured data to mark up app category information.
1669. Customized Notification (QualityActionsCustomizedNotification)
      • Description: Deprecated. Previously used for customized notifications in apps.
      • SEO Purpose: Ensured relevance and personalization in app notifications.
      • How to Use: Use current methods for handling notifications in apps.
1670. Customized Notification Button (QualityActionsCustomizedNotificationButton)
      • Description: Deprecated. Previously used for buttons in customized notifications.
      • SEO Purpose: Enhanced user interaction with app notifications.
      • How to Use: Use current methods for adding interactive elements to notifications.
1671. Customized Notification Payload (QualityActionsCustomizedNotificationPayload)
      • Description: Deprecated. Previously used for the payload in customized notifications.
      • SEO Purpose: Enhanced the relevance and personalization of notification content.
      • How to Use: Use current methods for handling notification payloads.
1672. News Provider Annotation Data (QualityActionsNewsProviderAnnotationData)
      • Description: Contains annotation data for news providers, used in search indexing.
      • SEO Purpose: Improves the relevance of news-related search results by providing detailed provider annotations.
      • How to Use: Clearly specify news provider annotations. Use structured data to mark up news provider information.
1673. News Provider Annotation Data Provider (QualityActionsNewsProviderAnnotationDataProvider)
      • Description: Contains provider-specific annotation data for news content.
      • SEO Purpose: Enhances the relevance and accuracy of news-related search results.
      • How to Use: Clearly specify provider-specific data. Use structured data to mark up news provider information.
1674. Reminder (QualityActionsReminder)
      • Description: Represents a reminder, including details such as recurrence, location, and person.
      • SEO Purpose: Improves the relevance of reminder-related search results by providing detailed reminder information.
      • How to Use: Clearly specify reminder details. Use structured data to mark up reminder information.
1675. Reminder Document (QualityActionsReminderDocument)
      • Description: Represents a document associated with a reminder, such as Google Docs, Sheets, or Slides.
      • SEO Purpose: Enhances the relevance of search results for reminders linked to documents.
      • How to Use: Clearly specify document details for reminders. Use structured data to mark up reminder document information.
1676. Reminder Dynamite Group (QualityActionsReminderDynamiteGroup)
      • Description: Represents a Google Chat space associated with a reminder.
      • SEO Purpose: Improves the relevance of reminder-related search results involving Google Chat spaces.
      • How to Use: Clearly specify Google Chat space details for reminders. Use structured data to mark up reminder group information.
1677. Reminder Location (QualityActionsReminderLocation)
      • Description: Represents locations that trigger reminders, including specific locations, groups, or personal aliases.
      • SEO Purpose: Enhances the relevance of location-based reminders in search results.
      • How to Use: Clearly specify reminder-triggering locations. Use structured data to mark up location information.
1678. Reminder Location Category Info (QualityActionsReminderLocationCategoryInfo)
      • Description: Provides information about location categories for reminders, such as grocery stores or restaurants.
      • SEO Purpose: Improves the relevance of category-based reminders in search results.
      • How to Use: Clearly specify location category information. Use structured data to mark up category details.
1679. Reminder Location Chain Info (QualityActionsReminderLocationChainInfo)
      • Description: Provides information about chains associated with reminder locations.
      • SEO Purpose: Enhances the relevance of chain-based reminders in search results.
      • How to Use: Clearly specify chain information for reminder locations. Use structured data to mark up chain details.
1680. Reminder Person (QualityActionsReminderPerson)
      • Description: Represents a person associated with a reminder, either as the creator or recipient.
      • SEO Purpose: Improves the relevance of person-based reminders in search results.
      • How to Use: Clearly specify person details for reminders. Use structured data to mark up person information.
1681. Reminder Recurrence Info (QualityActionsReminderRecurrenceInfo)
      • Description: Provides recurrence rules for time-based repeating reminders.
      • SEO Purpose: Enhances the relevance of recurring reminders in search results.
      • How to Use: Clearly specify recurrence rules for reminders. Use structured data to mark up recurrence information.
1682. Ringtone (QualityActionsRingtone)
      • Description: Contains information about ringtones used for notifications, such as timers and alarms.
      • SEO Purpose: Improves the relevance of search results involving notification ringtones.
      • How to Use: Clearly specify ringtone details. Use structured data to mark up ringtone information.
1683. Room (QualityActionsRoom)
      • Description: Represents the room where an alarm or timer is set.
      • SEO Purpose: Enhances the relevance of room-based notifications in search results.
      • How to Use: Clearly specify room details for alarms and timers. Use structured data to mark up room information.
1684. Timer (QualityActionsTimer)
      • Description: Represents a timer, including its duration and expiration time.
      • SEO Purpose: Improves the relevance of timer-related search results.
      • How to Use: Clearly specify timer details. Use structured data to mark up timer information.
1685. Topic Embeddings Versioned Item (QualityAuthorityTopicEmbeddingsVersionedItem)
      • Description: Stores versioned topic embedding scores, used in search ranking.
      • SEO Purpose: Enhances the relevance of search results by providing topic embedding data.
      • How to Use: Clearly specify topic embedding scores. Use structured data to mark up embedding information.
1686. App Link (QualityCalypsoAppsLink)
      • Description: Contains application IDs linked to specific content.
      • SEO Purpose: Improves the relevance of app-linked content in search results.
      • How to Use: Clearly specify application IDs. Use structured data to mark up app link information.
1687. Live Op Detail (QualityCalypsoAppsUniversalAuLiveOpDetail)
      • Description: Provides information for serving a single LiveOp/LiveEvent.
      • SEO Purpose: Enhances the relevance of live operation events in search results.
      • How to Use: Clearly specify live operation details. Use structured data to mark up LiveOp information.
1688. Live Op Event (QualityCalypsoAppsUniversalAuLiveOpEvent)
      • Description: Contains the schedule for a single live operation event.
      • SEO Purpose: Improves the relevance of scheduled live events in search results.
      • How to Use: Clearly specify event schedules. Use structured data to mark up live event information.
1689. Live Op Format (QualityCalypsoAppsUniversalAuLiveOpFormat)
      • Description: Provides format information for a single LiveOp/LiveEvent.
      • SEO Purpose: Enhances the relevance of live operation formats in search results.
      • How to Use: Clearly specify format details. Use structured data to mark up LiveOp format information.
1690. Live Ops Detail Info (QualityCalypsoAppsUniversalAuLiveOpsDetailInfo)
      • Description: Stores all possible LiveOps/LiveEvents eligible to be shown for an app.
      • SEO Purpose: Improves the relevance of app-related live events in search results.
      • How to Use: Clearly specify eligible LiveOps/LiveEvents. Use structured data to mark up live event details.
1691. Universal Image (QualityCalypsoAppsUniversalImage)
      • Description: Contains image details, including URL, height, and width.
      • SEO Purpose: Enhances the visual relevance of image-related search results.
      • How to Use: Clearly specify image details. Use structured data to mark up image information.
1692. Universal Image Data (QualityCalypsoAppsUniversalImageData)
      • Description: Provides data for enhanced images, including cover images and screenshots.
      • SEO Purpose: Improves the relevance of image-related app content in search results.
      • How to Use: Clearly specify enhanced image data. Use structured data to mark up image details.
1693. Firefly Site Signal (QualityCopiaFireflySiteSignal)
      • Description: Contains site-level signals for the search stack.
      • SEO Purpose: Enhances the relevance of site-specific content in search results.
      • How to Use: Clearly specify site signals. Use structured data to mark up site-level signal information.
1694. External IDs (QualityDialogManagerExternalIds)
      • Description: Maps various external IDs to local results, including IDs from Google systems and third-party systems.
      • SEO Purpose: Improves the relevance of local results by mapping external identifiers.
      • How to Use: Clearly specify external IDs. Use structured data to mark up ID information.
1695. Local Intent Options (QualityDialogManagerLocalIntentOptions)
      • Description: Represents intent options for local results.
      • SEO Purpose: Enhances the relevance of local intent-based search results.
      • How to Use: Clearly specify local intent options. Use structured data to mark up intent information.
1696. Local Result (QualityDialogManagerLocalResult)
      • Description: Represents a local result returned by a backend.
      • SEO Purpose: Improves the relevance of local search results by providing detailed result information.
      • How to Use: Clearly specify local result details. Use structured data to mark up local result information.
1697. Reminder Client Type (QualityDialogManagerReminderClientType)
      • Description: Defines types of clients for reminders, used for UX customization, metrics, and visibility control.
      • SEO Purpose: Enhances the user experience and relevance of reminder-related search results.
      • How to Use: Clearly specify client types for reminders. Use structured data to mark up client type information.
1698. Preview Restrictions (QualityDniDocPreviewRestrictions)
      • Description: Sets per-document markup restrictions based on EUCD and global preview compliance.
      • SEO Purpose: Ensures compliance with legal requirements and enhances the relevance of preview content in search results.
      • How to Use: Clearly specify preview restrictions. Use structured data to mark up restriction information.
1699. Extended News Previews (QualityDniExtendedNewsPreviews)
      • Description: Provides extended preview data for news content.
      • SEO Purpose: Improves the relevance of news-related search results by providing detailed preview information.
      • How to Use: Clearly specify news preview details. Use structured data to mark up preview information.
1700. Fringe Query Prior Per-Doc Data (QualityFringeFringeQueryPriorPerDocData)
      • Description: Contains per-document data for fringe queries, used for classification.
      • SEO Purpose: Enhances the relevance of search results for fringe queries.
      • How to Use: Clearly specify fringe query data. Use structured data to mark up fringe query information.
1701. Complex Queries Output Rewrite (QualityGenieComplexQueriesComplexQueriesOutputRewrite)
      • Description: This factor involves the rewriting of complex queries to enhance search precision. It uses entities and textual rewrites to interpret and rephrase user queries more effectively.
      • SEO Purpose: By accurately rewriting complex queries, this factor helps ensure that search results are more relevant to the user’s intent, improving the overall search experience and increasing the likelihood of content discovery.
      • How to Use: Implement structured data to identify key entities within content. Ensure your content is clear and comprehensive to aid in accurate query rewriting.
1702. Output Rewrite Entity (QualityGenieComplexQueriesComplexQueriesOutputRewriteEntity)
      • Description: This factor identifies specific entities within a rewritten query. Entities are unique identifiers such as names or IDs that provide context to the query.
      • SEO Purpose: Enhancing the identification of entities helps improve the relevance and accuracy of search results, ensuring that users find exactly what they are looking for.
      • How to Use: Use schema markup to tag entities within your content, making it easier for algorithms to recognize and use them in query rewriting.
1703. Brainloc Attachment (QualityGeoBrainlocBrainlocAttachment)
      • Description: This factor involves attaching Brainloc annotations to documents, providing detailed geographic and locational context.
      • SEO Purpose: Geographic context can significantly improve the relevance of search results, especially for location-based queries.
      • How to Use: Include clear and detailed geographic information in your content. Use location-based keywords and metadata to enhance geographic relevance.
1704. Google Label Data (QualityLabelsGoogleLabelData)
      • Description: This factor involves applying labels to data for categorization and improved search indexing. Labels include confidence levels and provider information.
      • SEO Purpose: Proper labeling helps in the categorization and retrieval of content, making it easier for search engines to understand and present relevant results.
      • How to Use: Ensure your content is well-organized and labeled with appropriate metadata. Use structured data to provide additional context and categorization.
1705. Label Data Label (QualityLabelsGoogleLabelDataLabel)
      • Description: This factor provides detailed label information, including confidence scores and identifiers, to help categorize content accurately.
      • SEO Purpose: Accurate labeling enhances the search engine’s ability to classify and rank content correctly, improving visibility and discoverability.
      • How to Use: Use structured data to tag your content with relevant labels. Include confidence scores and identifiers where applicable to improve content categorization.
1706. Click Signals (QualityNavboostCrapsCrapsClickSignals)
      • Description: This factor involves collecting click and impression signals to understand user interactions with search results.
      • SEO Purpose: Analyzing click signals helps improve the ranking algorithm by understanding user preferences and behavior, leading to more relevant search results.
      • How to Use: Monitor and analyze user interactions on your website. Optimize your content and layout based on user behavior to improve click-through rates.
1707. Craps Data (QualityNavboostCrapsCrapsData)
      • Description: This factor involves aggregating data related to clicks and impressions across different devices, countries, and languages.
      • SEO Purpose: Aggregating this data helps in understanding user behavior patterns, which can be used to refine and improve search algorithms.
      • How to Use: Ensure your website is optimized for various devices and languages. Use analytics to gather and understand user interaction data.
1708. Craps Device (QualityNavboostCrapsCrapsDevice)
      • Description: This factor provides information about the device used for search queries, including interface type and operating system.
      • SEO Purpose: Device-specific data helps tailor search results to the user’s device, enhancing the user experience.
      • How to Use: Optimize your website for different devices and operating systems. Use responsive design to ensure a seamless experience across all devices.
1709. Feature Craps Data (QualityNavboostCrapsFeatureCrapsData)
      • Description: This factor involves aggregating click signals by country, device, language, and location to provide detailed insights into user behavior.
      • SEO Purpose: Detailed aggregation helps in fine-tuning search algorithms to cater to specific user segments, improving relevance and personalization.
      • How to Use: Use structured data to provide detailed information about the country, device, and language of your content. Analyze user behavior to tailor content accordingly.
1710. Stats with Weights (QualityNavboostCrapsStatsWithWeightsProto)
      • Description: This factor involves statistical analysis of click and impression data, including means, medians, variances, and standard deviations.
      • SEO Purpose: Statistical analysis helps in understanding the distribution and variability of user interactions, which can be used to improve ranking algorithms.
      • How to Use: Use analytics tools to perform statistical analysis on user interaction data. Optimize content based on insights gained from the analysis.
1711. Voter Token Bitmap (QualityNavboostGlueVoterTokenBitmapMessage)
      • Description: This factor involves using voter token bitmaps to aggregate unique query tokens, ensuring privacy-related filtering.
      • SEO Purpose: Ensuring privacy in data aggregation helps build user trust and compliance with data protection regulations.
      • How to Use: Implement privacy-compliant data collection practices. Use aggregation methods that protect user privacy while providing valuable insights.
1712. Experimental NSR Team Data (QualityNsrExperimentalNsrTeamData)
      • Description: This factor involves collecting versioned signals for live experiments, helping to test and refine search algorithms.
      • SEO Purpose: Experimentation allows for continuous improvement of search algorithms, leading to more relevant and accurate search results.
      • How to Use: Conduct regular experiments to test changes in your content strategy. Use versioned signals to track the impact of these changes.
1713. NSR Team Scoring Signal (QualityNsrExperimentalNsrTeamScoringSignal)
      • Description: This factor provides versioned signals used for scoring in experimental data.
      • SEO Purpose: Accurate scoring signals help refine the relevance and ranking of search results.
      • How to Use: Use structured data to provide clear scoring criteria for your content. Regularly update and test scoring signals.
1714. WSJ Data Wrapper (QualityNsrExperimentalNsrTeamWSJData)
      • Description: This factor is a wrapper for WSJ data, used for injecting experimental data and keys.
      • SEO Purpose: Ensures comprehensive data integration for experiments, improving the accuracy of search results.
      • How to Use: Use structured data to integrate external data sources into your content strategy. Ensure data is accurately represented and updated.
1715. Keto Versioned Data (QualityNsrKetoKetoVersionedData)
      • Description: This factor involves populating data to NSR and propagating it to various indexing and scoring systems.
      • SEO Purpose: Consistent data propagation helps maintain the accuracy and relevance of search results across different systems.
      • How to Use: Ensure your content is consistently updated and propagated across all relevant platforms. Use structured data to facilitate accurate indexing and scoring.
1716. NSR Versioned Data (QualityNsrNSRVersionedData)
      • Description: This factor involves versioned NSR score data used in search ranking.
      • SEO Purpose: Versioned data helps in tracking changes and improvements in search algorithms, ensuring continuous optimization.
      • How to Use: Regularly update and test versioned data in your content strategy. Use structured data to provide clear versioning information.
1717. NSR Chunks Proto (QualityNsrNsrChunksProto)
      • Description: This factor corresponds to the NSRChunks class, storing data for indexing and scoring.
      • SEO Purpose: Proper data storage ensures accurate and efficient indexing and scoring, improving search result relevance.
      • How to Use: Use structured data to store and manage content information. Ensure data is accurately indexed and scored.
1718. NSR Chunks with Source Info (QualityNsrNsrChunksWithSourceInfo)
      • Description: This factor includes NSR chunks with annotated source information.
      • SEO Purpose: Source information helps improve the accuracy and relevance of indexed content.
      • How to Use: Provide clear source information for your content. Use structured data to annotate and manage source details.
1719. NSR Data (QualityNsrNsrData)
      • Description: This factor involves NSR data used for indexing and ranking content.
      • SEO Purpose: Accurate NSR data helps improve the relevance and ranking of search results.
      • How to Use: Use structured data to provide detailed NSR information for your content. Ensure data is accurately indexed and ranked.
1720. NSR Data Cluster Uplift (QualityNsrNsrDataClusterUplift)
      • Description: This factor involves uplift values for clusters used in ranking algorithms.
      • SEO Purpose: Uplift values help improve the accuracy and relevance of clustered search results.
      • How to Use: Use clustering techniques to organize your content. Provide clear uplift values to improve ranking accuracy.
1721. NSR Data Embedding (QualityNsrNsrDataEmbedding)
      • Description: This factor involves embedding data for NSR, including version information and vectors.
      • SEO Purpose: Embedding data helps improve the relevance and contextual understanding of search results.
      • How to Use: Use embedding techniques to provide contextual information for your content. Ensure embedding data is accurate and up-to-date.
1722. NSR Data Encoded Embedding (QualityNsrNsrDataEncodedEmbedding)
      • Description: This factor involves encoded embedding data for NSR, including version information and encoded vectors.
      • SEO Purpose: Encoded embedding data helps improve the efficiency and accuracy of search result processing.
      • How to Use: Use encoding techniques to optimize embedding data. Ensure data is accurately encoded and versioned.
1723. NSR Data Metadata (QualityNsrNsrDataMetadata)
      • Description: This factor involves metadata for NSR data, providing additional context and information.
      • SEO Purpose: Metadata helps improve the accuracy and relevance of search results by providing additional context.
      • How to Use: Use structured data to provide detailed metadata for your content. Ensure metadata is accurate and comprehensive.
1724. NSR PQ Data (QualityNsrPQData)
      • Description: This factor involves data used to compute PQ scores for NSR, including subchunk data.
      • SEO Purpose: PQ data helps improve the accuracy and relevance of search results by providing detailed scoring information.
      • How to Use: Use structured data to provide detailed PQ data for your content. Ensure data is accurately computed and scored.
1725. NSR Versioned Float Signal (QualityNsrVersionedFloatSignal)
      • Description: This factor involves versioned float signals used for scoring in NSR.
      • SEO Purpose: Accurate float signals help improve the relevance and accuracy of search result rankings.
      • How to Use: Use structured data to provide clear float signals for your content. Regularly update and test signals for accuracy.
1726. NSR Versioned Int Signal (QualityNsrVersionedIntSignal)
      • Description: This factor involves versioned int signals used for scoring in NSR.
      • SEO Purpose: Accurate int signals help improve the relevance and accuracy of search result rankings.
      • How to Use: Use structured data to provide clear int signals for your content. Regularly update and test signals for accuracy.
1727. Document Intent Scores (QualityOrbitAsteroidBeltDocumentIntentScores)
      • Description: This factor involves scoring document intents for relevance in search results.
      • SEO Purpose: Accurate intent scoring helps improve the relevance of document-based search results.
      • How to Use: Use intent-based keywords and phrases in your content. Ensure content aligns with user search intents.
1728. Image Intent Scores (QualityOrbitAsteroidBeltImageIntentScores)
      • Description: This factor involves scoring image intents in the context of a landing page.
      • SEO Purpose: Accurate image intent scoring helps improve the relevance of image-based search results.
      • How to Use: Use intent-based keywords and phrases in image descriptions and alt text. Ensure images align with user search intents.
1729. Orbit Image Intent (QualityOrbitOrbitImageIntent)
      • Description: This factor involves storing information for a single image-only orbit intent.
      • SEO Purpose: Accurate image intent storage helps improve the relevance and accuracy of image-based search results.
      • How to Use: Use structured data to provide clear image intent information. Ensure images are tagged with relevant intents.
1730. Orbit Image Intents (QualityOrbitOrbitImageIntents)
      • Description: This factor involves managing multiple image-only orbit intents.
      • SEO Purpose: Proper management of image intents helps improve the relevance and accuracy of image-based search results.
      • How to Use: Use structured data to manage and tag multiple image intents. Ensure images are accurately categorized.
1731. Chosen Snippet Info (QualityPreviewChosenSnippetInfo)
      • Description: This factor involves providing information for chosen snippets in search results.
      • SEO Purpose: Accurate snippet information helps improve the relevance and quality of featured snippets.
      • How to Use: Use structured data to provide detailed snippet information. Ensure content is optimized for snippet selection.
1732. Chosen Snippet Tidbit Info (QualityPreviewChosenSnippetInfoTidbitInfo)
      • Description: This factor involves identifying and providing information for snippet tidbits.
      • SEO Purpose: Accurate tidbit information helps improve the relevance and quality of featured snippets.
      • How to Use: Use structured data to tag and identify snippet tidbits. Ensure content is optimized for snippet selection.
1733. Ranklab Snippet (QualityPreviewRanklabSnippet)
      • Description: This factor involves providing candidate snippet information and signal scores.
      • SEO Purpose: Accurate snippet scoring helps improve the relevance and quality of featured snippets.
      • How to Use: Use structured data to provide detailed snippet information and signal scores. Ensure content is optimized for snippet selection.
1734. Ranklab Title (QualityPreviewRanklabTitle)
      • Description: This factor involves providing data corresponding to a single title candidate for scoring and selection.
      • SEO Purpose: Accurate title scoring helps improve the relevance and quality of title-based search results.
      • How to Use: Use structured data to provide detailed title information and signal scores. Ensure titles are optimized for search relevance.
1735. Snippet Brain Features (QualityPreviewSnippetBrainFeatures)
      • Description: This factor involves providing brain scores for snippets to aid in selection and ranking.
      • SEO Purpose: Accurate brain scores help improve the relevance and quality of featured snippets.
      • How to Use: Use structured data to provide detailed brain score information for snippets. Ensure content is optimized for snippet selection.
1736. Snippet Document Features (QualityPreviewSnippetDocumentFeatures)
      • Description: This factor involves providing document-related features for snippet scoring.
      • SEO Purpose: Accurate document features help improve the relevance and quality of featured snippets.
      • How to Use: Use structured data to provide detailed document features for snippets. Ensure content is optimized for snippet selection.
1737. Snippet Experimental Features (QualityPreviewSnippetExperimentalFeatures)
      • Description: This factor involves providing experimental features for snippet scoring and selection.
      • SEO Purpose: Testing and implementing experimental features help improve the relevance and quality of featured snippets.
      • How to Use: Use structured data to tag experimental features for snippets. Regularly test and optimize content based on experimental results.
1738. Snippet Quality Features (QualityPreviewSnippetQualityFeatures)
      • Description: This factor involves quality-related features used in the scoring of snippets. These features help determine the relevance and usefulness of a snippet for a given query.
      • SEO Purpose: Ensuring high-quality snippets appear in search results helps improve user engagement and satisfaction, leading to better click-through rates and potential conversions.
      • How to Use: Optimize content to provide clear, concise, and high-quality information that directly answers common user queries. Use structured data to highlight key points that could be featured as snippets.
1739. Snippet Query Features (QualityPreviewSnippetQueryFeatures)
      • Description: This factor involves query-related features used in the scoring of snippets. These features assess how well the snippet matches the user’s query.
      • SEO Purpose: Matching snippets accurately to user queries improves the relevance of search results, enhancing user experience and trust in the search engine.
      • How to Use: Ensure content includes relevant keywords and phrases that match user search queries. Use natural language and focus on answering potential questions users might have.
1740. Snippet Query Term Coverage Features (QualityPreviewSnippetQueryTermCoverageFeatures)
      • Description: This factor evaluates the coverage of query terms within the snippet. It assesses how many of the query terms are present in the snippet.
      • SEO Purpose: High term coverage in snippets improves relevance and ensures that the snippets are addressing the user’s search intent comprehensively.
      • How to Use: Include important query terms within your content and ensure that these terms are naturally integrated into the main points or headings that could be featured as snippets.
1741. Radish Features (QualityPreviewSnippetRadishFeatures)
      • Description: This factor involves features like answer scores, passage coverage, and similarity scores between the query and the snippet. It uses advanced methods to assess how well a snippet matches the query.
      • SEO Purpose: Advanced assessment of snippet relevance ensures that the most accurate and helpful snippets are shown, enhancing user satisfaction.
      • How to Use: Use comprehensive content that covers various aspects of a topic in detail. Include sections that directly answer common questions with clear, concise answers.
1742. Product Site Data (QualityProductProductSiteData)
      • Description: This factor involves data related to product sites, stored as signal data in document joins. It includes detailed information about products for better search indexing.
      • SEO Purpose: Detailed product site data helps search engines understand product offerings better, improving the visibility of product pages in search results.
      • How to Use: Ensure product pages are well-structured with detailed product descriptions, specifications, and relevant metadata. Use schema markup to provide additional context.
1743. Product Site Data Locale (QualityProductProductSiteDataLocaleData)
      • Description: This factor involves product site data specific to a particular locale. It ensures that product information is tailored to different regions.
      • SEO Purpose: Localized product data improves relevance for users in different regions, enhancing the user experience and potentially boosting local search rankings.
      • How to Use: Tailor product descriptions and metadata to different locales. Include localized keywords and ensure compliance with local regulations and standards.
1744. Custom Search Engine URL Info (QualityProseCSEUrlInfo)
      • Description: This factor involves data related to custom search engines, including IDs and scores that help categorize and rank search results.
      • SEO Purpose: Accurate categorization and ranking of URLs within custom search engines improve the relevance and usefulness of search results for specific queries.
      • How to Use: Use custom search engines effectively by ensuring URLs are correctly categorized and scored. Regularly update and refine search engine settings to maintain relevance.
1745. Account Provenance (QualityQrewriteAccountProvenance)
      • Description: This factor involves annotating the source of cross-account personal data, providing context for data coming from different accounts.
      • SEO Purpose: Understanding the provenance of personal data helps improve the personalization and accuracy of search results, enhancing user experience.
      • How to Use: Ensure personal data used in content is well-documented and its source is clearly identified. Use structured data to annotate the provenance of personal information.
1746. Google Account Provenance (QualityQrewriteAccountProvenanceGoogleAccount)
      • Description: This factor involves annotating personal data from Google accounts, ensuring accurate identification and context.
      • SEO Purpose: Accurate annotation of Google account data helps personalize search results, improving relevance and user satisfaction.
      • How to Use: Encourage users to link their Google accounts for personalized experiences. Use structured data to annotate and manage account-related information.
1747. Third-Party Account Provenance (QualityQrewriteAccountProvenanceThirdPartyAccount)
      • Description: This factor involves annotating personal data from third-party accounts, providing context and improving data integration.
      • SEO Purpose: Integrating third-party account data helps enhance the personalization of search results, making them more relevant to the user.
      • How to Use: Ensure third-party data is accurately annotated and integrated into your systems. Use structured data to manage and provide context for third-party account information.
1748. Alternative Name Info (QualityQrewriteAlternativeNameInfo)
      • Description: This factor involves alternative names and their sources, helping recognize different names or spellings for the same entity.
      • SEO Purpose: Recognizing alternative names improves the accuracy and relevance of search results, especially for queries with multiple possible spellings or variations.
      • How to Use: Include alternative names and common misspellings in your content. Use structured data to provide information on alternative names.
1749. Calendar Reference (QualityQrewriteCalendarReference)
      • Description: This factor involves calendar references, including aliases and contact calendar names, to provide context for calendar-related queries.
      • SEO Purpose: Accurate calendar references help improve the relevance of search results for calendar-related queries, enhancing user experience.
      • How to Use: Use structured data to provide clear calendar references and aliases. Ensure calendar-related information is up-to-date and accurately annotated.
1750. Contact Calendar Name (QualityQrewriteContactCalendarName)
      • Description: This factor involves the names of contacts’ calendars, helping to provide context and relevance for calendar-related queries.
      • SEO Purpose: Including contact calendar names improves the personalization and accuracy of search results for calendar-related queries.
      • How to Use: Ensure contact calendar names are accurately annotated and integrated into your systems. Use structured data to manage and provide context for contact calendar information.
1751. Family Calendar Alias (QualityQrewriteFamilyCalendarAlias)
      • Description: This factor involves aliases for family calendars, helping to provide context and relevance for family-related calendar queries.
      • SEO Purpose: Accurate family calendar aliases help improve the relevance and personalization of search results for family-related queries.
      • How to Use: Use structured data to provide clear aliases for family calendars. Ensure family calendar-related information is up-to-date and accurately annotated.
1752. Personal Contact Data (QualityQrewritePersonalContactData)
      • Description: This factor involves metadata related to personal contacts, helping to provide context and relevance for contact-related queries.
      • SEO Purpose: Accurate personal contact data improves the relevance and personalization of search results for contact-related queries.
      • How to Use: Ensure personal contact data is accurately annotated and integrated into your systems. Use structured data to manage and provide context for personal contact information.
1753. Primary Calendar Alias (QualityQrewritePrimaryCalendarAlias)
      • Description: This factor involves aliases for primary calendars, helping to provide context and relevance for primary calendar-related queries.
      • SEO Purpose: Accurate primary calendar aliases help improve the relevance and personalization of search results for primary calendar-related queries.
      • How to Use: Use structured data to provide clear aliases for primary calendars. Ensure primary calendar-related information is up-to-date and accurately annotated.
1754. Account-Aware Calendar Alias (QualityQrewriteQRewriteAccountAwareCalendarAliasWrapper)
      • Description: This factor involves a wrapper for account-aware calendar aliases, used for query annotation and providing context for calendar-related queries.
      • SEO Purpose: Accurate account-aware calendar aliases help improve the relevance and personalization of search results for calendar-related queries.
      • How to Use: Use structured data to provide clear aliases for account-aware calendars. Ensure calendar-related information is up-to-date and accurately annotated.
1755. Relationship Memory Data (QualityQrewriteRelationshipMemoryData)
      • Description: This factor involves relationship-to-contact data provided by Assistant Memory, helping to provide context and relevance for relationship-related queries.
      • SEO Purpose: Accurate relationship memory data improves the personalization and relevance of search results for relationship-related queries.
      • How to Use: Ensure relationship memory data is accurately annotated and integrated into your systems. Use structured data to manage and provide context for relationship-related information.
1756. Mustang Rank Embed Info (QualityRankembedMustangMustangRankEmbedInfo)
      • Description: This factor involves embedding information used in Mustang ranking algorithms, providing context and improving ranking accuracy.
      • SEO Purpose: Accurate embedding information helps improve the relevance and accuracy of search result rankings.
      • How to Use: Use structured data to provide detailed embedding information for your content. Regularly update and test embedding data for accuracy.
1757. Mustang Rank Embed Info Compressed Embedding (QualityRankembedMustangMustangRankEmbedInfoCompressedEmbedding)
      • Description: This factor involves compressed embedding information used in Mustang ranking algorithms, optimizing storage and processing.
      • SEO Purpose: Compressed embedding information helps improve the efficiency and accuracy of search result rankings.
      • How to Use: Use efficient compression techniques to optimize embedding data. Ensure data is accurately compressed and stored.
1758. Launch App Info Per Doc Data (QualityRichsnippetsAppsProtosLaunchAppInfoPerDocData)
      • Description: This factor involves data related to launchable apps stored in document data, helping identify documents containing app links.
      • SEO Purpose: Accurate app information helps improve the relevance and usefulness of search results containing app links.
      • How to Use: Ensure app-related data is accurately annotated and integrated into your content. Use structured data to highlight app links and related information.
1759. Launchable App Per Doc Data (QualityRichsnippetsAppsProtosLaunchableAppPerDocData)
      • Description: This factor involves a subset of launchable application data stored in document data, used to identify app links at serving time.
      • SEO Purpose: Accurate launchable app data helps improve the relevance and usefulness of search results containing app links.
      • How to Use: Ensure launchable app data is accurately annotated and integrated into your content. Use structured data to highlight app links and related information.
1760. Salient Country (QualitySalientCountriesSalientCountry)
      • Description: This factor measures how salient a country is for the document, providing context for country-specific relevance.
      • SEO Purpose: Understanding the salience of a country helps improve the relevance of search results for users in that country.
      • How to Use: Include country-specific information and keywords in your content. Use structured data to provide context for the relevance of different countries.
1761. Salient Country Set (QualitySalientCountriesSalientCountrySet)
      • Description: This factor involves a set of salient countries for a document, providing context for country-specific relevance.
      • SEO Purpose: Understanding the salience of multiple countries helps improve the relevance of search results for users in different countries.
      • How to Use: Include country-specific information and keywords for multiple regions in your content. Use structured data to provide context for the relevance of different countries.
1762. Salient Terms Doc Data (QualitySalientTermsDocData)
      • Description: This factor involves additional salient-term-set-level information for a document, complementing salient term sets.
      • SEO Purpose: Detailed salient term data helps improve the relevance and accuracy of search results.
      • How to Use: Include relevant terms and keywords in your content. Use structured data to provide additional context for salient terms.
1763. Salient Term (QualitySalientTermsSalientTerm)
      • Description: This factor involves normalized terms and weights, providing important term-level data for search relevance.
      • SEO Purpose: Recognizing salient terms helps improve the accuracy and relevance of search results.
      • How to Use: Include relevant terms and keywords in your content. Use structured data to provide weights and context for salient terms.
1764. Salient Term Set (QualitySalientTermsSalientTermSet)
      • Description: This factor involves a collection of terms with associated weights that describe something, known as the salient terms.
      • SEO Purpose: Using salient terms helps improve the relevance and accuracy of search results.
      • How to Use: Include relevant terms and keywords in your content. Use structured data to provide context and weights for salient terms.
1765. Salient Terms Signal Data (QualitySalientTermsSignalData)
      • Description: This factor involves signal-specific salient-term-set-level information, storing internal data for populators.
      • SEO Purpose: Detailed signal data helps improve the relevance and accuracy of search results.
      • How to Use: Use structured data to provide detailed signal information for your content. Ensure data is accurately populated and maintained.
1766. Salient Terms Signal Term Data (QualitySalientTermsSignalTermData)
      • Description: This factor involves signal-specific term-level information, storing internal data for populators.
      • SEO Purpose: Detailed signal term data helps improve the relevance and accuracy of search results.
      • How to Use: Use structured data to provide detailed term-level information for your content. Ensure data is accurately populated and maintained.
1767. Sherlock Knex Annotation (QualitySherlockKnexAnnotation)
      • Description: This factor involves annotations for Sherlock Knex, providing detailed item-level data for search relevance.
      • SEO Purpose: Detailed annotations help improve the relevance and accuracy of search results.
      • How to Use: Use structured data to provide detailed annotations for your content. Ensure annotations are accurate and comprehensive.
1768. Sherlock Knex Annotation Item (QualitySherlockKnexAnnotationItem)
      • Description: This factor involves item-level data for Sherlock Knex annotations, including scores and equivalent IDs.
      • SEO Purpose: Accurate item-level data helps improve the relevance and accuracy of search results.
      • How to Use: Use structured data to provide detailed item-level information for your content. Ensure data is accurate and comprehensive.
1769. Shopping Attachment (QualityShoppingShoppingAttachment)
      • Description: This factor involves data related to shopping attachments, used for scoring and previewing shopping results.
      • SEO Purpose: Accurate shopping data helps improve the relevance and usefulness of shopping search results.
      • How to Use: Ensure shopping-related data is accurately annotated and integrated into your content. Use structured data to highlight shopping links and related information.
1770. Shopping Attachment Locale (QualityShoppingShoppingAttachmentLocale)
      • Description: This factor involves locale-specific data for shopping attachments, helping tailor shopping results to different regions.
      • SEO Purpose: Localized shopping data improves relevance for users in different regions, enhancing user experience and potentially boosting local search rankings.
      • How to Use: Tailor shopping descriptions and metadata to different locales. Include localized keywords and ensure compliance with local regulations and standards.
1771. Shopping Attachment Moka Facet Value (QualityShoppingShoppingAttachmentMokaFacetValue)
      • Description: This factor involves Moka product attribute facets, providing detailed attribute information for products.
      • SEO Purpose: Accurate attribute information helps improve the relevance and usefulness of shopping search results.
      • How to Use: Use structured data to provide detailed attribute information for your products. Ensure attributes are accurately tagged and categorized.
1772. Shopping Attachment Offer (QualityShoppingShoppingAttachmentOffer)
      • Description: This factor involves offer-related data for shopping attachments, including conditions, images, and merchant information.
      • SEO Purpose: Detailed offer information helps improve the relevance and attractiveness of shopping search results.
      • How to Use: Ensure offer-related data is accurately annotated and integrated into your content. Use structured data to highlight offers and related information.
1773. Shopping Attachment PBlock (QualityShoppingShoppingAttachmentPBlock)
      • Description: This factor involves PBlock data for shopping attachments, used for structuring product information.
      • SEO Purpose: Properly structured product information helps improve the relevance and clarity of shopping search results.
      • How to Use: Use structured data to provide detailed PBlock information for your products. Ensure data is accurately organized and presented.
1774. Shopping Attachment PBlock Image Info (QualityShoppingShoppingAttachmentPBlockImageInfo)
      • Description: This factor involves image-related data for PBlock in shopping attachments, including dimensions and URLs.
      • SEO Purpose: Accurate image data helps improve the visual appeal and relevance of shopping search results.
      • How to Use: Use high-quality images with accurate dimensions and URLs. Ensure images are well-optimized for search engines.
1775. Shopping Attachment Product (QualityShoppingShoppingAttachmentProduct)
      • Description: This factor involves product-related data for shopping attachments, including ratings, brand information, and images.
      • SEO Purpose: Detailed product information helps improve the relevance and attractiveness of shopping search results.
      • How to Use: Ensure product-related data is accurately annotated and integrated into your content. Use structured data to highlight product details and related information.
1776. Sitemap Breadcrumb Target (QualitySitemapBreadcrumbTarget)
      • Description: This factor involves sitelink candidates generated from breadcrumbs, providing context for navigation links.
      • SEO Purpose: Accurate breadcrumb data helps improve the user experience and relevance of navigation links in search results.
      • How to Use: Use structured data to provide detailed breadcrumb information. Ensure breadcrumbs are accurately tagged and categorized.
1777. Sitemap Breadcrumb Target Doc (QualitySitemapBreadcrumbTargetDoc)
      • Description: This factor involves document-level data for breadcrumb targets, including URL and title information.
      • SEO Purpose: Detailed document-level breadcrumb data helps improve the relevance and accuracy of navigation links in search results.
      • How to Use: Ensure breadcrumb-related data is accurately annotated and integrated into your content. Use structured data to highlight breadcrumb links and related information.
1778. Co-Click Target (QualitySitemapCoClickTarget)
      • Description: This factor involves data related to co-click targets, helping to identify commonly clicked links.
      • SEO Purpose: Understanding co-click patterns helps improve the relevance and usefulness of navigation links in search results.
      • How to Use: Analyze co-click patterns and optimize your navigation links accordingly. Use structured data to provide context for commonly clicked links.
1779. Co-Click Target Doc (QualitySitemapCoClickTargetDoc)
      • Description: This factor involves document-level data for co-click targets, including URLs and click patterns.
      • SEO Purpose: Detailed document-level co-click data helps improve the relevance and accuracy of navigation links in search results.
      • How to Use: Ensure co-click-related data is accurately annotated and integrated into your content. Use structured data to highlight commonly clicked links and related information.
1780. Co-Click Target Doc Co-Click by Locale (QualitySitemapCoClickTargetDocCoClickByLocale)
      • Description: This factor involves locale-specific data for co-click targets, helping tailor navigation links to different regions.
      • SEO Purpose: Localized co-click data improves relevance for users in different regions, enhancing user experience and potentially boosting local search rankings.
      • How to Use: Tailor navigation links and metadata to different locales. Include localized keywords and ensure compliance with local regulations and standards.
1781. Scoring Signals (QualitySitemapScoringSignals)
      • Description: This factor involves scoring signals used for computing the sitelink score, helping to determine the relevance of navigation links.
      • SEO Purpose: Accurate scoring signals help improve the relevance and usefulness of navigation links in search results.
      • How to Use: Use structured data to provide detailed scoring signals for your navigation links. Ensure data is accurately calculated and presented.
1782. Sporc Signals (QualitySitemapSporcSignals)
      • Description: Sporc Signals provide additional scoring data for a URL, specifically during online/serving time.
      • SEO Purpose: These signals help enhance the relevance and ranking of URLs by incorporating real-time data during the serving process.
      • How to Use: Ensure your website provides up-to-date and relevant content that can be dynamically scored during serving to improve search rankings.
1783. Subresult (QualitySitemapSubresult)
      • Description: Subresult information includes details about a single sub-result within a larger set of search results.
      • SEO Purpose: Detailed sub-result data can improve the understanding of individual result components, enhancing overall relevance.
      • How to Use: Optimize individual components of your content to ensure each sub-result is relevant and well-structured.
1784. Subresult List (QualitySitemapSubresultList)
      • Description: A container that encapsulates a list of sub-results.
      • SEO Purpose: Organizing sub-results into a comprehensive list helps improve the structure and presentation of search results.
      • How to Use: Ensure your content is well-organized, making it easier for search engines to compile and present relevant sub-results.
1785. Sitelink Target (QualitySitemapTarget)
      • Description: Represents a single sitelink target, including basic display information and potential dynamic ranking adjustments.
      • SEO Purpose: Proper sitelink targets improve navigation and enhance the user’s search experience.
      • How to Use: Use structured data to specify sitelink targets, ensuring URLs and titles are accurate and relevant.
1786. Sitelink Target Group (QualitySitemapTargetGroup)
      • Description: Represents a set of sitelink targets with an optional label to uniquely identify the group.
      • SEO Purpose: Grouping sitelink targets enhances the organization and relevance of search results.
      • How to Use: Organize sitelinks into logical groups and use labels to clearly define each group’s purpose.
1787. Third-Party Carousels List Item Metadata (QualitySitemapThirdPartyCarouselsListItemMuppetMetadata)
      • Description: Metadata about a list item in a third-party carousel, passed on to Muppet from indexing.
      • SEO Purpose: Enhances the relevance and presentation of third-party carousel items in search results.
      • How to Use: Ensure carousel items are accurately annotated with relevant metadata.
1788. Top URL (QualitySitemapTopURL)
      • Description: Contains the score and URL of a top-performing webpage.
      • SEO Purpose: Highlighting top URLs helps improve visibility and click-through rates.
      • How to Use: Optimize key pages to become top URLs by focusing on high-quality content and relevant keywords.
1789. Two-Level Target (QualitySitemapTwoLevelTarget)
      • Description: Represents a two-level sitelink target, including both first and second-level targets.
      • SEO Purpose: Enhances navigation by providing multiple levels of relevant sitelinks.
      • How to Use: Implement two-level sitelinks to improve site navigation and user experience.
1790. Snippet Bolded Range (QualitySnippetsTruncationSnippetBoldedRange)
      • Description: Indicates bolded ranges within printed snippet lines to highlight key information.
      • SEO Purpose: Emphasizes important parts of snippets, making them more noticeable and relevant to users.
      • How to Use: Ensure key information in your content is highlighted and likely to be bolded in search snippets.
1791. Snippet Bolded Range Position (QualitySnippetsTruncationSnippetBoldedRangePosition)
      • Description: Provides the byte offset and index of bolded ranges in snippets.
      • SEO Purpose: Accurate positioning of bolded ranges helps improve snippet relevance and user engagement.
      • How to Use: Optimize content structure to ensure important information is correctly positioned for bolding.
1792. Date Unreliability (QualityTimebasedDateUnreliability)
      • Description: Signals indicating unreliable dates for a URL.
      • SEO Purpose: Helps filter out content with unreliable dates, improving the accuracy and relevance of search results.
      • How to Use: Ensure date information on your site is accurate and reliable to avoid negative impacts on search rankings.
1793. Last Significant Update (QualityTimebasedLastSignificantUpdate)
      • Description: Details the last significant update date of a document, including adjustment info and source.
      • SEO Purpose: Recent and significant updates can boost the relevance of your content in search results.
      • How to Use: Regularly update your content with significant changes to maintain its relevance and improve search rankings.
1794. Last Significant Update Adjustments (QualityTimebasedLastSignificantUpdateAdjustments)
      • Description: Information about adjustments made to the last significant update date.
      • SEO Purpose: Accurate adjustment data helps improve the precision of update-related ranking signals.
      • How to Use: Document and manage significant content updates to ensure accurate reflection in search rankings.
1795. Page Type (QualityTimebasedPageType)
      • Description: Indicates the type of page, such as forum or Q&A page.
      • SEO Purpose: Page type classification helps search engines better understand and rank different types of content.
      • How to Use: Clearly define the type of content on your pages using structured data to improve relevance and rankings.
1796. Petacat Date Unreliability (QualityTimebasedPetacatDateUnreliability)
      • Description: Unreliable date signals for a specific domain and petacat.
      • SEO Purpose: Helps identify and filter out content with unreliable dates in specific categories.
      • How to Use: Ensure category-specific content has accurate and reliable date information.
1797. Syntactic Date (QualityTimebasedSyntacticDate)
      • Description: Stores syntactic date information for a document.
      • SEO Purpose: Accurate date information helps improve the relevance and timeliness of search results.
      • How to Use: Use structured data to provide precise date information for your content.
1798. Syntactic Date Date Range (QualityTimebasedSyntacticDateDateRange)
      • Description: Stores a date range if a single date is insufficient.
      • SEO Purpose: Helps provide more precise date information, improving the relevance of search results.
      • How to Use: Use date ranges where applicable to provide better context for your content.
1799. Syntactic Date Position (QualityTimebasedSyntacticDatePosition)
      • Description: Provides byte offset positions for dates within a document.
      • SEO Purpose: Accurate positioning of dates helps improve the relevance and user experience of search results.
      • How to Use: Ensure dates are accurately positioned within your content using structured data.
1800. Good Sites Data (QualityTravelGoodSitesData)
      • Description: Data related to good travel sites, stored as signals in docjoins.
      • SEO Purpose: Identifies high-quality travel sites to improve the relevance of travel-related search results.
      • How to Use: Ensure your travel site provides high-quality content and is accurately categorized.
1801. Good Sites Data I18n (QualityTravelGoodSitesDataI18n)
      • Description: Locale-specific data for good travel sites.
      • SEO Purpose: Localized data improves relevance for users in different regions.
      • How to Use: Provide localized content and metadata for your travel site to improve its relevance in different regions.
1802. Good Sites Data Signal (QualityTravelGoodSitesDataSignal)
      • Description: Raw signals used to determine the site quality score.
      • SEO Purpose: High-quality signals improve the relevance and ranking of travel sites.
      • How to Use: Ensure your site has strong quality signals, such as good reviews and user engagement.
1803. Video Language (QualityVidyaVideoLanguageVideoLanguage)
      • Description: Audio-based language information for a Watch Page.
      • SEO Purpose: Accurate language information improves the relevance of video search results.
      • How to Use: Provide accurate language metadata for your videos to improve their relevance in search results.
1804. Cluster Info (QualityViewsExtractionClusterInfo)
      • Description: Stores cluster scoring information for an entity.
      • SEO Purpose: Detailed cluster information improves the accuracy and relevance of entity-related search results.
      • How to Use: Ensure your content accurately represents entities and their relationships to improve cluster scoring.
1805. Transcript Annotations (QualityWebanswersTranscriptAnnotations)
      • Description: Wraps other annotations for auto-generated video captions.
      • SEO Purpose: Enhances the relevance and accuracy of video captions in search results.
      • How to Use: Ensure video captions are accurately annotated with relevant information.
1806. Video Transcript Annotations (QualityWebanswersVideoTranscriptAnnotations)
      • Description: Annotations for video transcripts, including language and timing information.
      • SEO Purpose: Accurate transcript annotations improve the relevance and accuracy of video search results.
      • How to Use: Provide detailed and accurate annotations for your video transcripts.
1807. YouTube Caption Timing Info Annotations (QualityWebanswersVideoYouTubeCaptionTimingInfoAnnotations)
      • Description: Timing information for YouTube captions, mapping sentence boundaries to timing offsets.
      • SEO Purpose: Accurate timing information improves the relevance and usability of video captions.
      • How to Use: Ensure YouTube captions have precise timing information to improve their relevance in search results.
1808. YouTube Caption Timing Info Annotations Instance (QualityWebanswersVideoYouTubeCaptionTimingInfoAnnotationsInstance)
      • Description: Byte-offset and timing information for YouTube captions.
      • SEO Purpose: Enhances the accuracy and relevance of YouTube captions in search results.
      • How to Use: Provide accurate byte-offset and timing information for your YouTube captions.
1809. Registration Info (RegistrationInfo)
      • Description: Domain registration information for a document.
      • SEO Purpose: Accurate registration information helps verify the legitimacy and relevance of a domain.
      • How to Use: Ensure your domain registration information is accurate and up-to-date.
1810. Embedding (ReneEmbedding)
      • Description: Represents an embedding vector with clusters.
      • SEO Purpose: Embedding vectors help improve the relevance of search results by understanding content relationships.
      • How to Use: Use embeddings to represent content relationships and improve search result relevance.
1811. Embedding Cluster (ReneEmbeddingCluster)
      • Description: Represents a cluster within the embedding space.
      • SEO Purpose: Clusters help identify and group related content, improving search result relevance.
      • How to Use: Ensure content is accurately represented within embedding clusters to improve its relevance in search results.
1812. Embedding Cluster List (ReneEmbeddingClusterList)
      • Description: Represents a list of clusters within the embedding space.
      • SEO Purpose: Grouping related content into clusters improves the organization and relevance of search results.
      • How to Use: Organize content into logical clusters within the embedding space.
1813. Geo Topic (RepositoryAnnotationsGeoTopic)
      • Description: Represents a geo-topic, including its normalized scores.
      • SEO Purpose: Geo-topics help improve the relevance of location-specific search results.
      • How to Use: Ensure content is accurately tagged with relevant geo-topics.
1814. Geo Topicality (RepositoryAnnotationsGeoTopicality)
      • Description: A set of geo-topics ordered by normalized scores.
      • SEO Purpose: Ordered geo-topics improve the relevance and accuracy of location-specific search results.
      • How to Use: Ensure geo-topics are accurately ordered and relevant to the content.
1815. Geo Topicality Score (RepositoryAnnotationsGeoTopicalityScore)
      • Description: Represents the raw score and type of a geo-topicality.
      • SEO Purpose: Accurate geo-topicality scores help improve the relevance of location-specific search results.
      • How to Use: Ensure geo-topicality scores are accurate and relevant to the content.
1816. Sentiment Snippet Annotations (RepositoryAnnotationsMustangSentimentSnippetAnnotations)
      • Description: Stores sentiment snippet information for content.
      • SEO Purpose: Sentiment snippets help improve the relevance and user engagement of search results.
      • How to Use: Ensure content includes sentiment annotations to improve snippet relevance.
1817. Breadcrumbs (RepositoryAnnotationsRdfaBreadcrumbs)
      • Description: Represents breadcrumb information extracted from a document.
      • SEO Purpose: Breadcrumbs improve site navigation and enhance the user’s search experience.
      • How to Use: Implement breadcrumb navigation on your site to improve search result relevance.
1818. Breadcrumb Crumb (RepositoryAnnotationsRdfaCrumb)
      • Description: Represents a single link in a breadcrumb trail.
      • SEO Purpose: Individual breadcrumb links help improve navigation and relevance.
      • How to Use: Ensure breadcrumb links are accurately represented and relevant to the content.
1819. Rich Snippets Application (RepositoryAnnotationsRdfaRdfaRichSnippetsApplication)
      • Description: Holds application information for rich snippets.
      • SEO Purpose: Rich snippets enhance the presentation and relevance of search results.
      • How to Use: Implement structured data for rich snippets to improve search result relevance.
1820. Application App Type Data (RepositoryAnnotationsRdfaRdfaRichSnippetsApplicationAppTypeData)
      • Description: Top-level app category type, such as game or application.
      • SEO Purpose: Accurate app type data helps improve the relevance of app-related search results.
      • How to Use: Ensure app category data is accurately represented in structured data.
1821. Application Country Price (RepositoryAnnotationsRdfaRdfaRichSnippetsApplicationCountryPrice)
      • Description: Represents the country-specific price of an application.
      • SEO Purpose: Country-specific pricing information improves the relevance of app-related search results.
      • How to Use: Provide accurate country-specific pricing data for your applications.
1822. Application Localized Trusted Genome (RepositoryAnnotationsRdfaRdfaRichSnippetsApplicationLocalizedTrustedGenome)
      • Description: Represents localized trusted genome tags matching the document’s locale.
      • SEO Purpose: Localized trusted genome data enhances the relevance and trustworthiness of app-related search results.
      • How to Use: Ensure trusted genome data is localized and accurately represented.
1823. Application Rank (RepositoryAnnotationsRdfaRdfaRichSnippetsApplicationRank)
      • Description: Represents the rank of an application, including app store link and category.
      • SEO Purpose: Accurate app ranking information improves the visibility and relevance of app-related search results.
      • How to Use: Provide accurate ranking data for your applications to improve their search result relevance.
1824. Application Rank Data (RepositoryAnnotationsRdfaRdfaRichSnippetsApplicationRankData)
      • Description: Represents ranking data for applications, including category IDs and ranks.
      • SEO Purpose: Detailed ranking data improves the relevance and visibility of app-related search results.
      • How to Use: Ensure application ranking data is accurately represented in structured data.
1825. Aggregated Entity Name Scores (RepositoryWebrefAggregatedEntityNameScores)
      • Description: Represents aggregated scores of entities for a given name across all sources.
      • SEO Purpose: Aggregated entity scores improve the relevance and accuracy of entity-related search results.
      • How to Use: Ensure entity names and scores are accurately aggregated and represented.
1826. Anchor Indices (RepositoryWebrefAnchorIndices)
      • Description: Identifies a set of anchors in a document, treated as equivalent by the annotator.
      • SEO Purpose: Accurate anchor indices improve the relevance of search results by identifying key content.
      • How to Use: Ensure anchor points in your content are accurately identified and annotated.
1827. Category Annotation (RepositoryWebrefCategoryAnnotation)
      • Description: High-level category annotations for documents and queries.
      • SEO Purpose: Category annotations improve the relevance and organization of search results.
      • How to Use: Use structured data to accurately categorize your content.
1828. Entity Annotations (RepositoryWebrefEntityAnnotations)
      • Description: Represents all annotations for a given concept in one document collection.
      • SEO Purpose: Comprehensive entity annotations improve the relevance and accuracy of search results.
      • How to Use: Ensure concepts in your content are accurately annotated and relevant.
1829. Entity Debug Info (RepositoryWebrefEntityDebugInfo)
      • Description: Provides debug information for entities, used for engineering and model training.
      • SEO Purpose: Debug info helps improve the accuracy and relevance of entity-related search results.
      • How to Use: Ensure debug information is accurately represented for entities in your content.
1830. Entity Link Metadata (RepositoryWebrefEntityLinkMetadata)
      • Description: Metadata about the nature of entity links.
      • SEO Purpose: Detailed link metadata improves the understanding and relevance of entity relationships.
      • How to Use: Ensure entity links are accurately represented and relevant.
1831. Entity Name Ratings (RepositoryWebrefEntityNameRatings)
      • Description: Stores all human ratings collected for a given entity name.
      • SEO Purpose: Human ratings improve the relevance and trustworthiness of entity-related search results.
      • How to Use: Collect and represent human ratings for entity names accurately.
1832. Entity Mention (NlpSaftMention)
      • Description: Refers to instances where an entity (e.g., person, place, or organization) is mentioned in a document. This factor helps identify and highlight relevant entities within the content.
      • SEO Purpose: Enhances content relevance and contextual understanding, improving how search engines match queries with content.
      • How to Use: Ensure entities are mentioned naturally and contextually within the content. Use structured data to markup entity mentions.
1833. Mention Resolution (NlpSaftMentionResolution)
      • Description: Resolves mentions by encoding the concept ID for a specific entity. It helps to disambiguate and accurately identify entities across different mentions.
      • SEO Purpose: Improves entity recognition and disambiguation, which enhances the precision of search results.
      • How to Use: Use unique identifiers (e.g., mid) for entities in your content. Consistently refer to entities by their established IDs where possible.
1834. Morphology (NlpSaftMorphology)
      • Description: Stores information about the morphology of a token, including its root form, tense, and other grammatical features. This factor aids in understanding the syntactic structure of the content.
      • SEO Purpose: Enhances natural language processing by providing detailed grammatical information, improving search engine comprehension of content.
      • How to Use: Write content with proper grammar and syntax. Use variations of key terms (e.g., plural forms, different tenses) to improve relevance.
1835. Document Phrase (NlpSaftPhrase)
      • Description: Marks a range of tokens in a document as a phrase, identifying coherent chunks of text that function together semantically.
      • SEO Purpose: Helps in understanding the context and meaning of phrases within the content, leading to better search result matching.
      • How to Use: Use clear and coherent phrases in content. Highlight key phrases using proper formatting and structure.
1836. Referent (NlpSaftReferent)
      • Description: Contains information about what a discourse context entity refers to, acting as a canonical mention of the entity.
      • SEO Purpose: Ensures that references to entities are clearly understood, improving content coherence and relevance.
      • How to Use: Maintain consistency when referring to entities. Use clear and unambiguous language to ensure accurate referent identification.
1837. Entity Relations (NlpSaftRelation)
      • Description: Identifies relationships between different entities within the document. Each relation is documented along with mentions.
      • SEO Purpose: Enhances the understanding of how entities are interconnected, which can improve the relevance of search results.
      • How to Use: Clearly describe relationships between entities in your content. Use structured data to define these relationships.
1838. Relation Mentions (NlpSaftRelationMention)
      • Description: Records mentions of relationships between entities in the document. This helps in mapping out the interactions between different entities.
      • SEO Purpose: Provides detailed context about entity relationships, improving the depth of content analysis.
      • How to Use: Explicitly mention and describe relationships between entities. Use examples and context to illustrate these relationships.
1839. Semantic Node (NlpSaftSemanticNode)
      • Description: Annotates semantic constructions in documents, representing them as a directed acyclic graph. Each node can link to entities, measures, or token spans.
      • SEO Purpose: Enhances semantic understanding of content by structuring it into meaningful nodes and relationships.
      • How to Use: Organize content logically, using clear headings and subheadings. Use structured data to annotate key semantic elements.
1840. Semantic Node Arc (NlpSaftSemanticNodeArc)
      • Description: Defines arcs between nodes in a directed acyclic graph, indicating directional relationships between different semantic nodes.
      • SEO Purpose: Clarifies the relationships and hierarchies within content, aiding in semantic search and content comprehension.
      • How to Use: Ensure logical flow and connectivity in content. Use structured data to define relationships between key concepts.
1841. Token (NlpSaftToken)
      • Description: Marks spans of bytes in the document text as tokens or words, essential for tokenizing and processing text data.
      • SEO Purpose: Facilitates natural language processing by clearly defining the smallest units of text.
      • How to Use: Write clear, well-structured content with proper spacing and punctuation. Use consistent terminology throughout the document.
1842. Article Data (NlpSciencelitArticleData)
      • Description: Contains the text of an article along with references to internal figures, external citations, datasets, and more.
      • SEO Purpose: Provides comprehensive content information, enhancing the depth and quality of the document.
      • How to Use: Include thorough and well-referenced content in articles. Use internal and external links to provide additional context and resources.
1843. Article ID (NlpSciencelitArticleId)
      • Description: Contains unique identifiers associated with an article, such as PMID, DOI, or PMC.
      • SEO Purpose: Ensures proper citation and retrieval of scientific articles, enhancing credibility and traceability.
      • How to Use: Always include accurate identifiers for scientific articles. Use proper citation formats to reference these IDs.
1844. Article Metadata (NlpSciencelitArticleMetadata)
      • Description: Stores metadata related to scientific articles, including publication details, authorship, and more.
      • SEO Purpose: Enhances the discoverability and indexing of scientific content by providing detailed metadata.
      • How to Use: Provide complete and accurate metadata for articles. Use structured data to mark up metadata fields.
1845. Author Information (NlpSciencelitAuthor)
      • Description: Captures the first and last names of authors, helping to attribute and identify the creators of the content.
      • SEO Purpose: Ensures accurate authorship information, enhancing credibility and traceability.
      • How to Use: Always include the full names of authors. Provide author bios and relevant credentials to establish authority.
1846. Citation Data (NlpSciencelitCitationData)
      • Description: Contains information about citations, including references to external works and datasets.
      • SEO Purpose: Enhances the credibility and depth of content by including relevant citations.
      • How to Use: Cite sources accurately. Use proper citation formats and include links to referenced works.
1847. Dataset Information (NlpSciencelitDataset)
      • Description: Stores details about datasets associated with the content, including metadata and associations.
      • SEO Purpose: Provides additional data resources, enhancing the comprehensiveness and utility of the content.
      • How to Use: Include detailed information about datasets used in research. Link to datasets and provide metadata for better discoverability.
1848. Mesh Heading (NlpSciencelitMeshHeading)
      • Description: Represents a full Mesh Heading containing descriptors and optional qualifiers, used for indexing and categorizing medical content.
      • SEO Purpose: Improves the categorization and discoverability of medical and scientific content through standardized headings.
      • How to Use: Use Mesh Headings to categorize medical content accurately. Ensure that headings and qualifiers are relevant to the content.
1849. Pub Date (NlpSciencelitPubDate)
      • Description: Extracts the publication date from PMC article metadata, providing a clear timeline for the content.
      • SEO Purpose: Ensures the timeliness and relevance of scientific articles by clearly indicating publication dates.
      • How to Use: Always include the publication date for articles. Ensure that dates are accurate and up-to-date.
1850. Publication Type (NlpSciencelitPublicationType)
      • Description: Describes the type of publication, such as “Journal Article,” using display names and unique identifiers.
      • SEO Purpose: Helps categorize content by publication type, enhancing its relevance and discoverability.
      • How to Use: Clearly indicate the type of publication. Use standardized terms and identifiers for different publication types.
1851. Referenced Block (NlpSciencelitReferencedBlock)
      • Description: Contains data associated with reference blocks in scientific articles, providing context and linkage to references.
      • SEO Purpose: Enhances the credibility and thoroughness of content by linking to relevant references.
      • How to Use: Include reference blocks in scientific articles. Provide clear and accurate references to support the content.
1852. Retrieval Query Debug Info (NlpSciencelitRetrievalQueryEncodingDebugInfo)
      • Description: Encodes the query used for retrieval, aiding in debugging and refining search algorithms.
      • SEO Purpose: Improves the accuracy and efficiency of search algorithms by providing detailed query information.
      • How to Use: Use query encoding to refine search algorithms. Monitor and debug search queries to enhance performance.
1853. Search Result Debug Info (NlpSciencelitRetrievalSearchResultDebugInfo)
      • Description: Provides debug information for search results returned by the Delver API, helping to analyze and improve search accuracy.
      • SEO Purpose: Enhances search result accuracy and relevance by providing detailed debug information.
      • How to Use: Use debug information to analyze and improve search results. Regularly review and refine search algorithms based on debug data.
1854. Search Result Set Debug Info (NlpSciencelitRetrievalSearchResultSetDebugInfo)
      • Description: Optionally returned by the Delver API in the response’s debug_info field, providing additional context for search result sets.
      • SEO Purpose: Provides detailed context for search result sets, aiding in the refinement and improvement of search algorithms.
      • How to Use: Review and utilize debug information for search result sets. Refine search algorithms based on insights gained from debug data.
1855. Snippet Debug Info (NlpSciencelitRetrievalSnippetDebugInfo)
      • Description: Provides debug information for snippets returned by the Delver API, helping to analyze and refine snippet generation.
      • SEO Purpose: Improves the accuracy and relevance of snippets by providing detailed debug information.
      • How to Use: Analyze snippet debug information to refine snippet generation. Ensure snippets accurately represent the content.
1856. Subject Heading (NlpSciencelitSubjectHeading)
      • Description: Represents a subject heading from MeSH, used to categorize and index content.
      • SEO Purpose: Enhances the categorization and discoverability of content through standardized subject headings.
      • How to Use: Use MeSH subject headings to categorize content accurately. Ensure that headings are relevant and properly applied.
1857. Tokenized Text (NlpSciencelitTokenizedText)
      • Description: Represents text that has been tokenized, with optional original representation preserved.
      • SEO Purpose: Facilitates natural language processing by breaking text into manageable tokens.
      • How to Use: Ensure content is well-structured and easily tokenizable. Preserve original text representation where necessary.
1858. Annotation Evaluation Data (NlpSemanticParsingAnnotationEvalData)
      • Description: Used for span-based evaluation metrics in training, aligning byte spans with token spans to save examples.
      • SEO Purpose: Enhances the accuracy of natural language processing models by providing detailed evaluation metrics.
      • How to Use: Use annotation evaluation data to train and refine NLP models. Align byte spans with token spans for accurate evaluations.
1859. App Annotation (NlpSemanticParsingAppAnnotation)
      • Description: Annotates potential app names in the parser’s input, outputting details about identified apps.
      • SEO Purpose: Improves the identification and relevance of app-related queries and content.
      • How to Use: Clearly mention app names in content. Use structured data to annotate and highlight app names.
1860. DateTime Annotation (NlpSemanticParsingDateTimeAnnotation)
      • Description: Annotates date and time expressions in content, such as “Friday” or “9am,” with corresponding date/time details.
      • SEO Purpose: Enhances the understanding and relevance of date/time-related content.
      • How to Use: Clearly state date and time expressions in content. Use structured data to annotate date and time information.
1861. Absolute DateTime (NlpSemanticParsingDatetimeAbsoluteDateTime)
      • Description: Represents resolved date/time expressions that need no further calculation, including both date and time sections.
      • SEO Purpose: Ensures the accuracy of date and time information in content, improving search relevance.
      • How to Use: Clearly specify absolute dates and times in content. Use structured data to mark up date and time information accurately.
1862. DateTime Representation (NlpSemanticParsingDatetimeDateTime)
      • Description: Top-level representation of date/time, which can include ranges, points, or recurrent expressions.
      • SEO Purpose: Enhances the understanding of complex date/time expressions, improving content relevance.
      • How to Use: Use clear and accurate date/time expressions. Utilize structured data to represent date/time ranges and points.
1863. DateTime Property (NlpSemanticParsingDatetimeDateTimeProperty)
      • Description: Contains metadata about the DateTime interpretation, providing additional context for date/time expressions.
      • SEO Purpose: Improves the understanding and relevance of date/time content by providing detailed metadata.
      • How to Use: Include relevant metadata for date/time expressions. Use structured data to mark up this information accurately.
1864. Duration (NlpSemanticParsingDatetimeDuration)
      • Description: Represents unanchored durations, indicating the length of time expressions without specific calendar references.
      • SEO Purpose: Enhances the understanding of duration-related content, improving search result accuracy.
      • How to Use: Clearly state durations in content. Use structured data to mark up duration information.
1865. Event (NlpSemanticParsingDatetimeEvent)
      • Description: Represents events that interact with date/time expressions, such as sunset or sunrise, and can be extended to include richer event information.
      • SEO Purpose: Enhances the understanding of event-related content, improving search relevance.
      • How to Use: Clearly describe events in content. Use structured data to annotate events and their interactions with date/time expressions.
1866. Fetched Relative DateTime (NlpSemanticParsingDatetimeFetchedRelativeDateTime)
      • Description: Represents relative datetime expressions fetched through operations, such as “next weekend” or “last two Mondays.”
      • SEO Purpose: Improves the understanding of relative datetime expressions, enhancing content relevance.
      • How to Use: Clearly state relative datetime expressions. Use structured data to mark up relative date/time information.
1867. Holiday (NlpSemanticParsingDatetimeHoliday)
      • Description: Lists holidays that are not fixed absolute or relative dates on the Gregorian calendar.
      • SEO Purpose: Enhances the understanding and relevance of holiday-related content.
      • How to Use: Include relevant holiday information in content. Use structured data to mark up holidays accurately.
1868. Moon Event Info (NlpSemanticParsingDatetimeMoonEventInfo)
      • Description: Contains information about moon phases and types, used for annotating lunar events.
      • SEO Purpose: Enhances the understanding of moon-related content, improving search relevance.
      • How to Use: Clearly describe lunar events in content. Use structured data to annotate moon phases and types.
1869. Non-Gregorian Date (NlpSemanticParsingDatetimeNonGregorianDate)
      • Description: Represents dates using non-Gregorian calendars, similar to AbsoluteDateTime but with different calendar systems.
      • SEO Purpose: Enhances the understanding of non-Gregorian date expressions, improving content relevance.
      • How to Use: Clearly state non-Gregorian dates in content. Use structured data to mark up non-Gregorian date information.
1870. Quantity (NlpSemanticParsingDatetimeQuantity)
      • Description: Represents quantities in date/time expressions, such as “3 days” or “5 minutes,” including modifiers and symbolic quantities.
      • SEO Purpose: Enhances the understanding of quantity-related content, improving search relevance.
      • How to Use: Clearly state quantities in date/time expressions. Use structured data to mark up quantity information accurately.
1871. DateTime Range (NlpSemanticParsingDatetimeRange)
      • Description: Represents ranges in date/time expressions, including explicit, fuzzy, and relative ranges.
      • SEO Purpose: Enhances the understanding of date/time ranges, improving content relevance.
      • How to Use: Clearly state date/time ranges in content. Use structured data to mark up range information accurately.
1872. Recurrent DateTime (NlpSemanticParsingDatetimeRecurrent)
      • Description: Represents recurrent date/time expressions, such as “every Monday” or “every morning starting from this Friday.”
      • SEO Purpose: Enhances the understanding of recurrent date/time expressions, improving search result accuracy.
      • How to Use: Clearly state recurrent date/time expressions. Use structured data to mark up recurrent date/time information.
1873. Relative DateTime (NlpSemanticParsingDatetimeRelativeDateTime)
      • Description: Provides a semi-abstract description for relative datetime expressions, such as “three days ago” or “2 days after March 1st.”
      • SEO Purpose: Improves the understanding of relative datetime expressions, enhancing content relevance.
      • How to Use: Clearly state relative datetime expressions. Use structured data to mark up relative date/time information.
1874. Resolution Properties (NlpSemanticParsingDatetimeResolutionProperties)
      • Description: Encapsulates metadata about the query span resolved, providing additional context for datetime resolutions.
      • SEO Purpose: Enhances the accuracy and relevance of datetime content by providing detailed resolution metadata.
      • How to Use: Include relevant metadata for datetime resolutions. Use structured data to mark up resolution information accurately.
1875. Shifted Relative DateTime (NlpSemanticParsingDatetimeShiftedRelativeDateTime)
      • Description: This ranking factor handles datetime expressions that are shifted relative to another datetime point. It includes details such as the base datetime, the type of base, metadata for tagging, relative base properties, shift amount, and direction (past or future).
      • SEO Purpose: Improves the accuracy and relevance of search results involving date and time expressions by correctly interpreting relative shifts.
      • How to Use: Ensure datetime expressions are clear and unambiguous. Use structured data to provide context for relative date and time references.
1876. Datetime Span (NlpSemanticParsingDatetimeSpan)
      • Description: Represents a specific byte offset and text of a span within the document, helping to identify precise sections of text.
      • SEO Purpose: Enhances the ability of search algorithms to pinpoint and highlight specific text spans, improving search precision.
      • How to Use: Clearly define and format important spans within your content. Use structured data to help search engines recognize these spans.
1877. Target to Fetch (NlpSemanticParsingDatetimeTargetToFetch)
      • Description: Identifies the target datetime that needs to be fetched, including specific details that help retrieve the correct date or time.
      • SEO Purpose: Ensures accurate retrieval of date/time information, enhancing the relevance of time-sensitive content.
      • How to Use: Specify clear and accurate datetime targets within your content. Use structured data to assist in the correct identification and retrieval of these targets.
1878. Time Zone (NlpSemanticParsingDatetimeTimeZone)
      • Description: Specifies the time zone information for datetime expressions, ensuring that the time is correctly interpreted based on geographic location.
      • SEO Purpose: Enhances the accuracy of time-sensitive search results by incorporating time zone data.
      • How to Use: Clearly indicate the time zone for datetime expressions in your content. Use structured data to markup time zone information.
1879. Entity Source Data (NlpSemanticParsingEntitySourceData)
      • Description: Provides information about the sources from which parts of an entity were retrieved, offering insight into the origin and credibility of the data.
      • SEO Purpose: Improves the trustworthiness and accuracy of entity-related content by clarifying data sources.
      • How to Use: Ensure that data sources are reliable and clearly documented. Use structured data to attribute the origins of entity information.
1880. Expression Status (NlpSemanticParsingExpressionStatus)
      • Description: Indicates whether the user has finished expressing their intended semantics during a streaming interaction. This status helps in detecting whether additional input is expected.
      • SEO Purpose: Enhances user interaction by accurately sensing when a user has completed their input, improving the handling of dynamic queries.
      • How to Use: Monitor user interactions to determine when input is complete. Use this data to optimize real-time query processing and responses.
1881. Local Amenities (NlpSemanticParsingLocalAmenities)
      • Description: Lists amenity constraints, representing various amenities that a location might offer. These constraints are combined using an implicit AND relationship.
      • SEO Purpose: Enhances local search results by specifying the amenities available at a location, improving user satisfaction.
      • How to Use: Clearly list amenities available at your location. Use structured data to annotate these amenities.
1882. Basic Location (NlpSemanticParsingLocalBasicLocation)
      • Description: Describes a single location, which can be a sequence of location elements. At least one element in the sequence must be an actual location.
      • SEO Purpose: Improves the accuracy and relevance of local search results by precisely defining locations.
      • How to Use: Provide clear and detailed descriptions of locations. Use structured data to mark up each location element.
1883. Business Type (NlpSemanticParsingLocalBusinessType)
      • Description: Categorizes business types, which can include various establishments such as hotels, restaurants, and more. Business types can match multiple categories.
      • SEO Purpose: Enhances local search results by accurately categorizing businesses, improving user discovery.
      • How to Use: Clearly categorize your business. Use structured data to mark up business types and relevant categories.
1884. Chain Member Constraint (NlpSemanticParsingLocalChainMemberConstraint)
      • Description: Provides constraints for filtering queries based on chain membership, useful for identifying locations that are part of a specific chain.
      • SEO Purpose: Enhances search precision by filtering results to include or exclude specific chains.
      • How to Use: Clearly indicate chain membership for your business. Use structured data to mark up chain-related information.
1885. Compound Location (NlpSemanticParsingLocalCompoundLocation)
      • Description: Describes locations that are combinations of two or more basic locations, connected by a joiner (e.g., “Starbucks near Central Park”).
      • SEO Purpose: Improves local search relevance by accurately representing complex location queries.
      • How to Use: Clearly describe compound locations in your content. Use structured data to mark up the components and joiners of these locations.
1886. Contact Location (NlpSemanticParsingLocalContactLocation)
      • Description: Provides contact information for a specific location, such as phone numbers or email addresses.
      • SEO Purpose: Enhances local search results by providing accurate contact details, improving user accessibility.
      • How to Use: Ensure contact information is up-to-date and clearly displayed. Use structured data to markup contact details.
1887. Cuisine Constraint (NlpSemanticParsingLocalCuisineConstraint)
      • Description: Specifies constraints for types of cuisine, such as “Chinese,” “Italian,” or “Thai.”
      • SEO Purpose: Improves search relevance for restaurant queries by specifying cuisine types.
      • How to Use: Clearly list the types of cuisine offered. Use structured data to mark up cuisine types.
1888. EV Charging Station Connector Constraint (NlpSemanticParsingLocalEvChargingStationConnectorConstraint)
      • Description: Specifies the types of connectors available at an EV charging station.
      • SEO Purpose: Enhances the relevance of search results for EV charging stations by detailing connector types.
      • How to Use: Clearly specify the types of connectors available at your EV charging station. Use structured data to mark up connector information.
1889. EV Charging Station Payment Constraint (NlpSemanticParsingLocalEvChargingStationPaymentConstraint)
      • Description: Details the payment methods accepted at an EV charging station.
      • SEO Purpose: Improves user experience by providing information on payment options for EV charging.
      • How to Use: Clearly list accepted payment methods. Use structured data to mark up payment options.
1890. EV Charging Station Speed Constraint (NlpSemanticParsingLocalEvChargingStationSpeedConstraint)
      • Description: Specifies the charging speeds available at an EV charging station.
      • SEO Purpose: Enhances search results for EV charging stations by providing detailed information on charging speeds.
      • How to Use: Clearly indicate the charging speeds offered. Use structured data to mark up charging speed information.
1891. Extent (NlpSemanticParsingLocalExtent)
      • Description: Represents the extent of a location, which can be described in units like distance or time. It can include non-specific values such as “a few.”
      • SEO Purpose: Enhances the precision of location-based queries by providing detailed extent information.
      • How to Use: Clearly specify the extent in location descriptions. Use structured data to mark up extent information.
1892. GCID Constraint (NlpSemanticParsingLocalGcidConstraint)
      • Description: Uses GCID (Google’s unique identifier for businesses) to specify constraints in search queries.
      • SEO Purpose: Improves the accuracy and relevance of search results by using unique identifiers for businesses.
      • How to Use: Ensure your business has a GCID and use it in structured data to improve search accuracy.
1893. Health Insurance Constraint (NlpSemanticParsingLocalHealthInsuranceConstraint)
      • Description: Specifies constraints related to health insurance networks for providers.
      • SEO Purpose: Enhances search results for healthcare providers by detailing accepted insurance networks.
      • How to Use: Clearly list accepted health insurance networks. Use structured data to mark up insurance information.
1894. Hotel Type (NlpSemanticParsingLocalHotelType)
      • Description: Differentiates between sub-classes of accommodations, such as hotels, motels, and guest houses.
      • SEO Purpose: Improves search relevance for accommodation queries by accurately categorizing hotel types.
      • How to Use: Clearly specify the type of accommodation. Use structured data to mark up hotel types.
1895. Hyper Reliable Data (NlpSemanticParsingLocalHyperReliableData)
      • Description: Contains information about hyper-reliable categories, used to ensure high accuracy in certain categories.
      • SEO Purpose: Enhances trust and accuracy in search results by highlighting hyper-reliable data.
      • How to Use: Ensure data accuracy and reliability in your content. Use structured data to highlight hyper-reliable information.
1896. Implicit Local Category (NlpSemanticParsingLocalImplicitLocalCategory)
      • Description: Flags indicating specific implicit intents, such as dining or travel.
      • SEO Purpose: Improves the accuracy of search results by recognizing implicit user intents.
      • How to Use: Clearly define and indicate implicit intents in your content. Use structured data to mark up these intents.
1897. Joiner (NlpSemanticParsingLocalJoiner)
      • Description: Represents the connecting text between two locations or elements in a query.
      • SEO Purpose: Enhances the understanding of complex queries by accurately interpreting joiners.
      • How to Use: Use clear and appropriate joiners in location descriptions. Use structured data to mark up joiners.
1898. Local Result ID (NlpSemanticParsingLocalLocalResultId)
      • Description: Holds information needed to look up a local result in search.
      • SEO Purpose: Ensures accurate retrieval of local search results by using specific result IDs.
      • How to Use: Include local result IDs in structured data to improve search accuracy.
1899. Location (NlpSemanticParsingLocalLocation)
      • Description: Describes various types of locations, including basic, compound, and vicinity locations.
      • SEO Purpose: Improves the accuracy and relevance of location-based search results.
      • How to Use: Provide detailed and accurate location descriptions. Use structured data to mark up different types of locations.
1900. Location Constraint (NlpSemanticParsingLocalLocationConstraint)
      • Description: Specifies constraints for locations, including compound and internal location elements.
      • SEO Purpose: Enhances search precision by applying specific location constraints.
      • How to Use: Clearly specify location constraints in your content. Use structured data to mark up these constraints.
1901. Location Element (NlpSemanticParsingLocalLocationElement)
      • Description: Represents individual elements of a location, which can be actual locations or modifiers.
      • SEO Purpose: Improves the granularity and precision of location-based search results.
      • How to Use: Clearly define and describe each location element. Use structured data to mark up these elements.
1902. Menu Item (NlpSemanticParsingLocalMenuItem)
      • Description: Specifies menu items as location constraints or standalone categorical elements.
      • SEO Purpose: Enhances search results for food-related queries by specifying menu items.
      • How to Use: Clearly list and describe menu items. Use structured data to mark up menu items.
1903. Price Constraint (NlpSemanticParsingLocalPriceConstraint)
      • Description: Represents constraints related to price, including ranges and currency codes.
      • SEO Purpose: Improves search relevance for price-sensitive queries.
      • How to Use: Clearly indicate price ranges and currency codes. Use structured data to mark up price constraints.
1904. Quality Constraint (NlpSemanticParsingLocalQualityConstraint)
      • Description: Specifies quality constraints, such as ratings and reviews.
      • SEO Purpose: Enhances search results by highlighting quality metrics.
      • How to Use: Clearly indicate quality metrics such as ratings and reviews. Use structured data to mark up quality information.
1905. Room Constraint (NlpSemanticParsingLocalRoomConstraint)
      • Description: Specifies constraints for room occupancy in hotels or vacation rentals.
      • SEO Purpose: Improves search results for accommodation queries by specifying room constraints.
      • How to Use: Clearly specify room occupancy constraints. Use structured data to mark up room information.
1906. Scalable Attribute (NlpSemanticParsingLocalScalableAttribute)
      • Description: Represents scalable attributes, which can be used as location constraints or standalone categorical elements.
      • SEO Purpose: Enhances search results by specifying scalable attributes such as “outdoor seating” or “happy hour.”
      • How to Use: Clearly list scalable attributes. Use structured data to mark up these attributes.
1907. Service Constraint (NlpSemanticParsingLocalServiceConstraint)
      • Description: Specifies constraints related to service types, such as delivery or dine-in.
      • SEO Purpose: Improves search relevance for service-related queries.
      • How to Use: Clearly indicate service types. Use structured data to mark up service constraints.
1908. Star Ratings (NlpSemanticParsingLocalStarRatings)
      • Description: Represents star rating constraints for establishments like hotels.
      • SEO Purpose: Enhances search results by specifying star ratings.
      • How to Use: Clearly indicate star ratings for your establishment. Use structured data to mark up star rating information.
1909. Vicinity Location (NlpSemanticParsingLocalVicinityLocation)
      • Description: Indicates the area around a certain location, defined by time or space.
      • SEO Purpose: Improves search precision for queries related to vicinity or proximity.
      • How to Use: Clearly specify vicinity locations. Use structured data to mark up proximity information.
1910. Visit History Constraint (NlpSemanticParsingLocalVisitHistoryConstraint)
      • Description: Specifies constraints based on whether a location has been visited before.
      • SEO Purpose: Enhances search results by considering visit history.
      • How to Use: Track and indicate visit history. Use structured data to mark up visit history constraints.
1911. Contact Type (NlpSemanticParsingModelsCommunicationPhoneType)
      • Description: Represents the type of contact, such as mobile, home, or work.
      • SEO Purpose: Improves search relevance for contact-related queries.
      • How to Use: Clearly indicate contact types. Use structured data to mark up contact information.
1912. Recipient (NlpSemanticParsingModelsCommunicationRecipient)
      • Description: Represents a recipient, which can be a person, business, email, or phone number.
      • SEO Purpose: Enhances search accuracy for queries involving specific recipients.
      • How to Use: Clearly specify recipient details. Use structured data to mark up recipient information.
1913. Relationship Argument (NlpSemanticParsingModelsCommunicationRelationshipArgument)
      • Description: Represents a relationship contact, providing context for relationship-based queries.
      • SEO Purpose: Improves search relevance for queries involving relationships.
      • How to Use: Clearly describe relationship contacts. Use structured data to mark up relationship information.
1914. Device (NlpSemanticParsingModelsDevice)
      • Description: Specifies the device for performing an action, including type and name.
      • SEO Purpose: Enhances search results by recognizing specific devices.
      • How to Use: Clearly indicate device types and names. Use structured data to mark up device information.
1915. Device Name (NlpSemanticParsingModelsDeviceName)
      • Description: Represents the name of a device, such as “Nexus 5” or “Nexus 10.”
      • SEO Purpose: Improves search relevance for device-related queries.
      • How to Use: Clearly specify device names. Use structured data to mark up device names.
1916. Dialog Referents (NlpSemanticParsingModelsDialogReferentsDialogReferents)
      • Description: Used to emit type annotations from dialog referents, helping to identify specific references in conversations.
      • SEO Purpose: Enhances search accuracy for queries involving dialog referents.
      • How to Use: Clearly indicate dialog referents. Use structured data to mark up referent information.
1917. List Selection (NlpSemanticParsingModelsDialogReferentsListSelection)
      • Description: Represents the user’s selection from a list of alternatives, providing context for choices made.
      • SEO Purpose: Improves search relevance for queries involving lists and selections.
      • How to Use: Clearly describe list selections. Use structured data to mark up selection information.
1918. Album Title (NlpSemanticParsingModelsMediaAlbumTitle)
      • Description: Represents the title of an album, enhancing the identification of music-related content.
      • SEO Purpose: Improves search accuracy for music-related queries by specifying album titles.
      • How to Use: Clearly indicate album titles. Use structured data to mark up album information.
1919. Audio (NlpSemanticParsingModelsMediaAudio)
      • Description: Represents a music recording, including details about the song and artist.
      • SEO Purpose: Enhances search results for music queries by providing detailed audio information.
      • How to Use: Clearly describe music recordings. Use structured data to mark up audio information.
1920. Audiobook Info (NlpSemanticParsingModelsMediaAudiobookInfo)
      • Description: Provides metadata for an audiobook, including title and author.
      • SEO Purpose: Improves search relevance for audiobook queries by providing detailed metadata.
      • How to Use: Clearly describe audiobooks. Use structured data to mark up audiobook information.
1921. Book (NlpSemanticParsingModelsMediaBook)
      • Description: Represents a book, including its title, such as “East of Eden.”
      • SEO Purpose: Enhances search accuracy for book-related queries by specifying titles.
      • How to Use: Clearly indicate book titles. Use structured data to mark up book information.
1922. Media Device Annotation (NlpSemanticParsingModelsMediaCastDeviceAnnotation)
      • Description: Represents a media device, such as a Chromecast or TV, used for casting media.
      • SEO Purpose: Improves search results for queries involving media devices.
      • How to Use: Clearly specify media devices. Use structured data to mark up device information.
1923. Media Cost (NlpSemanticParsingModelsMediaCost)
      • Description: Represents the localized price of media content.
      • SEO Purpose: Enhances search relevance for queries involving media costs.
      • How to Use: Clearly indicate media prices. Use structured data to mark up cost information.
1924. Deeplink Info (NlpSemanticParsingModelsMediaDeeplinkInfo)
      • Description: Provides deeplink information and associated metadata, including platform restrictions and user subscriptions.
      • SEO Purpose: Enhances user experience by providing direct links to media content.
      • How to Use: Clearly specify deeplink URLs. Use structured data to mark up deeplink information.
1925. Deeplink Info Time Window (NlpSemanticParsingModelsMediaDeeplinkInfoTimeWindow)
      • Description: Represents a time window for deeplink access, expressed as a time range.
      • SEO Purpose: Improves search relevance for time-sensitive media content.
      • How to Use: Clearly indicate time windows for deeplink access. Use structured data to mark up time window information.
1926. Media Description (NlpSemanticParsingModelsMediaDescription)
      • Description: This factor captures free-form text descriptions of media content, such as “the episode with all of the comedians.”
      • SEO Purpose: Enhances the discoverability and relevance of media content by using descriptive phrases that match user queries.
      • How to Use: Include detailed and engaging descriptions of media content. Use keywords and phrases that potential viewers might search for.
1927. Episode Constraint (NlpSemanticParsingModelsMediaEpisodeConstraint)
      • Description: Specifies constraints for media episodes, such as “latest” to indicate a specific ordinal.
      • SEO Purpose: Improves the relevance of search results by allowing users to specify particular episodes.
      • How to Use: Clearly indicate the order or specific episodes in your content. Use structured data to mark up episode details.
1928. Radio Frequency (NlpSemanticParsingModelsMediaFrequency)
      • Description: Defines the frequency for terrestrial radio stations, such as 99.1 FM or 730 AM.
      • SEO Purpose: Enhances search relevance for radio station queries by specifying exact frequencies.
      • How to Use: Clearly indicate the frequency of your radio station. Use structured data to mark up frequency information.
1929. Game (NlpSemanticParsingModelsMediaGame)
      • Description: Represents a video game, such as “Deus Ex Human Revolution.”
      • SEO Purpose: Improves search results for video game queries by specifying game titles.
      • How to Use: Clearly list video game titles in your content. Use structured data to mark up game information.
1930. Generic Music (NlpSemanticParsingModelsMediaGenericMusic)
      • Description: Represents general music queries, such as “my library” or “some music.”
      • SEO Purpose: Enhances the relevance of music-related queries by accommodating general music requests.
      • How to Use: Use general terms to describe music collections. Use structured data to mark up generic music references.
1931. Latitude/Longitude (NlpSemanticParsingModelsMediaLatLng)
      • Description: Represents a geographic location using latitude and longitude coordinates.
      • SEO Purpose: Improves the accuracy of location-based queries by providing precise geographic data.
      • How to Use: Clearly indicate geographic coordinates in your content. Use structured data to mark up location information.
1932. Media Annotation (NlpSemanticParsingModelsMediaMediaAnnotation)
      • Description: Provides annotations for media entities, helping to categorize and describe media content.
      • SEO Purpose: Enhances the categorization and discoverability of media content through detailed annotations.
      • How to Use: Use annotations to provide additional context and metadata for media content. Use structured data to mark up annotations.
1933. Media Annotation List (NlpSemanticParsingModelsMediaMediaAnnotationList)
      • Description: A list of media annotations, used to annotate spans of media content.
      • SEO Purpose: Improves the accuracy and relevance of media-related search results by using comprehensive annotation lists.
      • How to Use: Compile detailed annotation lists for media content. Use structured data to mark up these lists.
1934. Media Provider Info (NlpSemanticParsingModelsMediaMediaProviderInfo)
      • Description: Contains information about media providers and their deeplinks, abstracting multiple media-related types.
      • SEO Purpose: Enhances the discoverability and user experience by linking to media providers and their content.
      • How to Use: Clearly specify media provider details and deeplinks. Use structured data to mark up provider information.
1935. Movie (NlpSemanticParsingModelsMediaMovie)
      • Description: Represents a movie, such as “Casablanca.”
      • SEO Purpose: Improves search relevance for movie queries by specifying movie titles.
      • How to Use: Clearly list movie titles in your content. Use structured data to mark up movie information.
1936. Music Artist (NlpSemanticParsingModelsMediaMusicArtist)
      • Description: Represents a music artist, such as “The Beatles.”
      • SEO Purpose: Enhances search results for music queries by specifying artist names.
      • How to Use: Clearly list music artist names in your content. Use structured data to mark up artist information.
1937. Music Genre (NlpSemanticParsingModelsMediaMusicGenre)
      • Description: Represents a music genre, such as “British Invasion.”
      • SEO Purpose: Improves the categorization and discoverability of music content by specifying genres.
      • How to Use: Clearly indicate music genres in your content. Use structured data to mark up genre information.
1938. Music Playlist (NlpSemanticParsingModelsMediaMusicPlaylist)
      • Description: Represents a music playlist, such as “gym playlist.”
      • SEO Purpose: Enhances the relevance of search results for playlist queries by specifying playlist names.
      • How to Use: Clearly list and describe playlists. Use structured data to mark up playlist information.
1939. News Info (NlpSemanticParsingModelsMediaNewsInfo)
      • Description: Provides metadata for news articles, including docid, content type, publication time, and publisher.
      • SEO Purpose: Improves the accuracy and relevance of news-related search results by providing detailed metadata.
      • How to Use: Include detailed metadata for news articles. Use structured data to mark up news information.
1940. News Topic (NlpSemanticParsingModelsMediaNewsTopic)
      • Description: Represents a news topic, such as “Ukraine” in a query like “read me news about Ukraine.”
      • SEO Purpose: Enhances search relevance for news queries by specifying topics.
      • How to Use: Clearly indicate news topics in your content. Use structured data to mark up topic information.
1941. Paid Offer Detail (NlpSemanticParsingModelsMediaPaidOfferDetail)
      • Description: Represents details for BUY and RENT offers, including associated costs.
      • SEO Purpose: Improves the relevance of search results for purchase-related queries by providing detailed offer information.
      • How to Use: Clearly list details for paid offers. Use structured data to mark up offer information.
1942. Podcast (NlpSemanticParsingModelsMediaPodcast)
      • Description: Represents a podcast, such as “This American Life.”
      • SEO Purpose: Enhances search relevance for podcast queries by specifying podcast titles.
      • How to Use: Clearly list podcast titles in your content. Use structured data to mark up podcast information.
1943. Podcast Info (NlpSemanticParsingModelsMediaPodcastInfo)
      • Description: Provides metadata for podcasts, including cluster ID, episode GUID, feed URL, and recommendation features.
      • SEO Purpose: Improves the discoverability and relevance of podcast content by providing detailed metadata.
      • How to Use: Include detailed metadata for podcasts. Use structured data to mark up podcast information.
1944. Provider Metadata (NlpSemanticParsingModelsMediaProviderMetadata)
      • Description: Contains metadata associated with video providers.
      • SEO Purpose: Enhances the relevance and accuracy of video-related search results by providing provider metadata.
      • How to Use: Clearly specify provider metadata for videos. Use structured data to mark up this information.
1945. Purchase Info (NlpSemanticParsingModelsMediaPurchaseInfo)
      • Description: Provides details about a purchase, including order type and purchase timestamp.
      • SEO Purpose: Improves search relevance for purchase-related queries by providing detailed purchase information.
      • How to Use: Clearly indicate purchase details. Use structured data to mark up purchase information.
1946. Media Quantification (NlpSemanticParsingModelsMediaQuantification)
      • Description: Quantifies devices in a query, such as “three speakers” or “all TVs.”
      • SEO Purpose: Enhances search accuracy for queries involving multiple devices by specifying quantifications.
      • How to Use: Clearly indicate quantities of devices. Use structured data to mark up quantification information.
1947. Radio (NlpSemanticParsingModelsMediaRadio)
      • Description: Represents a radio station, such as “107.7 The Bone.”
      • SEO Purpose: Improves search relevance for radio station queries by specifying station names.
      • How to Use: Clearly list radio station names in your content. Use structured data to mark up radio information.
1948. Radio Info (NlpSemanticParsingModelsMediaRadioInfo)
      • Description: Provides metadata for radio stations, including terrestrial and internet radio.
      • SEO Purpose: Enhances the relevance and accuracy of radio-related search results by providing detailed metadata.
      • How to Use: Include detailed metadata for radio stations. Use structured data to mark up radio information.
1949. Radio Network (NlpSemanticParsingModelsMediaRadioNetwork)
      • Description: Represents a radio network, such as “NPR” or “BBC.”
      • SEO Purpose: Improves search relevance for network-related radio queries by specifying network names.
      • How to Use: Clearly indicate radio network names. Use structured data to mark up network information.
1950. Rental Info (NlpSemanticParsingModelsMediaRentalInfo)
      • Description: Provides details for media rentals, including activation and grant periods, purchase timestamp, and validity.
      • SEO Purpose: Enhances search relevance for rental-related queries by providing detailed rental information.
      • How to Use: Clearly indicate rental details. Use structured data to mark up rental information.
1951. Season Constraint (NlpSemanticParsingModelsMediaSeasonConstraint)
      • Description: Specifies constraints for TV show seasons, such as “season 2” of a series.
      • SEO Purpose: Improves search relevance for TV show queries by specifying season information.
      • How to Use: Clearly indicate season numbers for TV shows. Use structured data to mark up season information.
1952. Song (NlpSemanticParsingModelsMediaSong)
      • Description: Represents a song, such as “Hey Jude.”
      • SEO Purpose: Enhances search relevance for music queries by specifying song titles.
      • How to Use: Clearly list song titles in your content. Use structured data to mark up song information.
1953. TV Show (NlpSemanticParsingModelsMediaTVShow)
      • Description: Represents a TV show, such as “Breaking Bad.”
      • SEO Purpose: Improves search relevance for TV show queries by specifying show titles.
      • How to Use: Clearly list TV show titles in your content. Use structured data to mark up TV show information.
1954. YouTube Deeplink Info (NlpSemanticParsingModelsMediaYouTubeDeeplinkInfo)
      • Description: Provides deeplink information specific to YouTube media assets.
      • SEO Purpose: Enhances user experience by providing direct links to YouTube content.
      • How to Use: Clearly specify deeplink URLs for YouTube content. Use structured data to mark up deeplink information.
1955. YouTube Playlist Info (NlpSemanticParsingModelsMediaYouTubePlaylistInfo)
      • Description: Provides details about YouTube playlists, including the number of videos playable in WoodStock and total video count.
      • SEO Purpose: Improves the relevance of search results for YouTube playlists by providing detailed playlist information.
      • How to Use: Clearly list details for YouTube playlists. Use structured data to mark up playlist information.
1956. Currency (NlpSemanticParsingModelsMoneyCurrency)
      • Description: Represents a currency, identified by its knowledge graph identifier.
      • SEO Purpose: Enhances search relevance for queries involving currencies by providing specific identifiers.
      • How to Use: Clearly indicate currency identifiers. Use structured data to mark up currency information.
1957. Money (NlpSemanticParsingModelsMoneyMoney)
      • Description: Represents a quantity of money.
      • SEO Purpose: Improves search relevance for queries involving monetary amounts.
      • How to Use: Clearly specify monetary amounts in your content. Use structured data to mark up money information.
1958. News Provider (NlpSemanticParsingModelsNarrativeNewsNewsProvider)
      • Description: Corresponds to an entry in a curated table of news providers.
      • SEO Purpose: Enhances the credibility and relevance of news-related content by specifying news providers.
      • How to Use: Clearly indicate news provider names. Use structured data to mark up provider information.
1959. On Device (NlpSemanticParsingModelsOnDevice)
      • Description: Describes the device(s) to perform an action, useful for specifying target devices in commands.
      • SEO Purpose: Enhances the accuracy of device-specific queries by specifying target devices.
      • How to Use: Clearly indicate target devices for actions. Use structured data to mark up device information.
1960. Person (NlpSemanticParsingModelsPersonPerson)
      • Description: Represents a person, including details such as name, contact data, and alternative names.
      • SEO Purpose: Improves search relevance for queries involving people by providing detailed personal information.
      • How to Use: Clearly indicate personal details. Use structured data to mark up person information.
1961. Recurrence (NlpSemanticParsingModelsRecurrence)
      • Description: Specifies rules for date- and time-based repetition for tasks, such as daily, weekly, monthly, or yearly patterns.
      • SEO Purpose: Enhances the relevance of search results for recurring events by providing detailed recurrence information.
      • How to Use: Clearly indicate recurrence rules for events. Use structured data to mark up recurrence information.
1962. Brand Phrase (NlpSemanticParsingModelsShoppingAssistantBrandPhrase)
      • Description: Represents a brand, which can be any combination of text or knowledge graph identifier.
      • SEO Purpose: Improves search relevance for brand-related queries by specifying brand names.
      • How to Use: Clearly indicate brand names in your content. Use structured data to mark up brand information.
1963. Merchant (NlpSemanticParsingModelsShoppingAssistantMerchant)
      • Description: Represents a merchant that sells products.
      • SEO Purpose: Enhances search relevance for queries involving merchants by specifying merchant names.
      • How to Use: Clearly indicate merchant names. Use structured data to mark up merchant information.
1964. Merchant Center ID (NlpSemanticParsingModelsShoppingAssistantMerchantMerchantCenterId)
      • Description: Represents a merchant center ID, capturing multiple IDs for different purposes.
      • SEO Purpose: Improves the accuracy and relevance of search results involving merchant center IDs.
      • How to Use: Clearly indicate merchant center IDs. Use structured data to mark up ID information.
1965. Offer (NlpSemanticParsingModelsShoppingAssistantOffer)
      • Description: Represents a product for sale from a particular merchant, possibly available at a specific store.
      • SEO Purpose: Enhances search relevance for product offers by specifying offer details.
      • How to Use: Clearly indicate offer details in your content. Use structured data to mark up offer information.
1966. Phrase (NlpSemanticParsingModelsShoppingAssistantPhrase)
      • Description: Represents a phrase parsed from a user query, useful for understanding search intent.
      • SEO Purpose: Improves search accuracy by understanding the context and intent behind user queries.
      • How to Use: Clearly indicate phrases in your content. Use structured data to mark up phrase information.
1967. Product (NlpSemanticParsingModelsShoppingAssistantProduct)
      • Description: Represents a product that can be purchased.
      • SEO Purpose: Enhances search relevance for product-related queries by specifying product details.
      • How to Use: Clearly list product details in your content. Use structured data to mark up product information.
1968. Product Classification (NlpSemanticParsingModelsShoppingAssistantProductClassification)
      • Description: Classifies products into specific categories, such as “video games.”
      • SEO Purpose: Improves the categorization and discoverability of products by specifying categories.
      • How to Use: Clearly indicate product categories. Use structured data to mark up classification information.
1969. Product Expression (NlpSemanticParsingModelsShoppingAssistantProductExpression)
      • Description: Represents an expression parsed from a user query that describes a product or set of products.
      • SEO Purpose: Enhances search relevance by understanding the context and intent behind product-related queries.
      • How to Use: Clearly indicate product expressions in your content. Use structured data to mark up expression information.
1970. Media Product (NlpSemanticParsingModelsShoppingAssistantProductMediaProduct)
      • Description: Represents a media product that can be purchased, such as a book or album.
      • SEO Purpose: Improves search relevance for media product queries by specifying product details.
      • How to Use: Clearly list media product details in your content. Use structured data to mark up media product information.
1971. Media Attribute Value (NlpSemanticParsingModelsShoppingAssistantProductMediaProductMediaAttributeValue)
      • Description: Represents the knowledge graph identifier and raw text of a media attribute, such as an author.
      • SEO Purpose: Enhances search relevance for media-related queries by providing detailed attribute information.
      • How to Use: Clearly indicate media attribute values. Use structured data to mark up attribute information.
1972. Product Phrase (NlpSemanticParsingModelsShoppingAssistantProductPhrase)
      • Description: Represents a product using a combination of raw text and metadata.
      • SEO Purpose: Improves search relevance for product-related queries by specifying product phrases.
      • How to Use: Clearly indicate product phrases in your content. Use structured data to mark up phrase information.
1973. Shopping List Item Info (NlpSemanticParsingModelsShoppingAssistantShoppingListItemInfo)
      • Description: Provides details about items on a shopping list, including item ID and list ID.
      • SEO Purpose: Enhances search relevance for shopping list queries by providing detailed item information.
      • How to Use: Clearly indicate shopping list item details. Use structured data to mark up item information.
1974. Store (NlpSemanticParsingModelsShoppingAssistantStore)
      • Description: Represents a merchant’s physical store.
      • SEO Purpose: Improves search relevance for store-related queries by specifying store details.
      • How to Use: Clearly indicate store details. Use structured data to mark up store information.
1975. Unrecognized Phrase (NlpSemanticParsingModelsShoppingAssistantUnrecognizedPhrase)
      • Description: Represents a span in a user query that could not be identified as any other type of phrase.
      • SEO Purpose: Enhances the accuracy of search results by identifying unrecognized phrases.
      • How to Use: Clearly indicate unrecognized phrases in your content. Use structured data to mark up these phrases.
1976. Fraction Number (NlpSemanticParsingNumberFractionNumber)
      • Description: This ranking factor deals with fraction numbers, capturing details such as the numerator, denominator, precision (number of digits after the decimal point), and whole number for mixed fractions.
      • SEO Purpose: Enhances the precision of numeric content interpretation, ensuring fractions are correctly understood and displayed in search results.
      • How to Use: Use clear and accurate fraction representations in content. Ensure fractions are properly formatted and contextualized.
1977. Number (NlpSemanticParsingNumberNumber)
      • Description: Represents numeric values, crucial for interpreting and processing numbers in content.
      • SEO Purpose: Ensures accurate understanding and ranking of content involving numeric values.
      • How to Use: Clearly specify numeric values in content. Use structured data to mark up numbers for better search engine comprehension.
1978. Simple Number (NlpSemanticParsingNumberSimpleNumber)
      • Description: Represents simple numeric values without complex fractions or mixed numbers.
      • SEO Purpose: Enhances the relevance of search results involving straightforward numeric data.
      • How to Use: Use simple and clear numeric values in content. Ensure numbers are easily readable and properly formatted.
1979. Personal Intelligence Entity (NlpSemanticParsingPersonalIntelligenceEntity)
      • Description: Represents personal intelligence entities, wire-equivalent to the Entity proto defined in personal intelligence models.
      • SEO Purpose: Improves personalization and relevance of search results by understanding user-specific entities.
      • How to Use: Include detailed and accurate personal entity information. Use structured data to mark up personal intelligence entities.
1980. Personal Reference Annotation (NlpSemanticParsingPersonalReferenceAnnotation)
      • Description: Contains QRefAnnotations designating personal references and resolutions, used for personalized intents like “navigate to my hotel.”
      • SEO Purpose: Enhances personalization in search results by accurately interpreting personal references.
      • How to Use: Clearly specify personal references in content. Use structured data to mark up personal reference annotations.
1981. Google Actions Slot (NlpSemanticParsingProtoActionsOnGoogleAogSlot)
      • Description: Represents NLU slots that can contain multiple possible values, including complex tree structures and list parameters.
      • SEO Purpose: Improves the accuracy and functionality of Google Actions by understanding user input slots.
      • How to Use: Clearly define slot values in content. Use structured data to mark up Google Actions slots.
1982. Google Actions DateTime (NlpSemanticParsingProtoActionsOnGoogleDateTime)
      • Description: Represents datetime values, including date, time, and date-time. Tracks hours and minutes but omits seconds.
      • SEO Purpose: Enhances the relevance of search results involving datetime queries.
      • How to Use: Clearly specify date and time values in content. Use structured data to mark up datetime information.
1983. Google Actions DateTime Property (NlpSemanticParsingProtoActionsOnGoogleDateTimeProperty)
      • Description: Represents properties about matched datetime values, providing additional context for date, time, and date-time values.
      • SEO Purpose: Improves the accuracy of datetime interpretations in search results.
      • How to Use: Include detailed datetime properties in content. Use structured data to mark up datetime properties.
1984. Google Actions Slot List (NlpSemanticParsingProtoActionsOnGoogleSlotList)
      • Description: Injects a list as a possible value into a slot, used for handling lists in Google Actions.
      • SEO Purpose: Enhances the functionality of Google Actions by accurately interpreting list values.
      • How to Use: Clearly define list values in content. Use structured data to mark up slot lists.
1985. Google Actions Slot Map (NlpSemanticParsingProtoActionsOnGoogleSlotMap)
      • Description: Injects a map as a possible value into a slot, used for handling maps in Google Actions.
      • SEO Purpose: Improves the accuracy of map-based slot interpretations in Google Actions.
      • How to Use: Clearly define map values in content. Use structured data to mark up slot maps.
1986. Google Actions Slot Value (NlpSemanticParsingProtoActionsOnGoogleSlotValue)
      • Description: Contains one or more possible values for a slot, used in Google Actions.
      • SEO Purpose: Enhances the relevance and accuracy of search results involving slot values.
      • How to Use: Clearly specify slot values in content. Use structured data to mark up slot value information.
1987. Google Actions Slot Value Single (NlpSemanticParsingProtoActionsOnGoogleSlotValueSingleValue)
      • Description: Represents an actual value for a slot in Google Actions.
      • SEO Purpose: Improves the precision of slot value interpretations in Google Actions.
      • How to Use: Clearly define single slot values in content. Use structured data to mark up single slot values.
1988. Google Actions Typed Value (NlpSemanticParsingProtoActionsOnGoogleTypedValue)
      • Description: Contains information about the type of slot value returned by on-device Heron.
      • SEO Purpose: Enhances the accuracy of slot value types in Google Actions.
      • How to Use: Clearly specify typed values in content. Use structured data to mark up typed value information.
1989. QRef Annotation (NlpSemanticParsingQRefAnnotation)
      • Description: Annotates spans of input with freebase-ids and collection information.
      • SEO Purpose: Improves the relevance and accuracy of entity-related search results.
      • How to Use: Clearly annotate entities with freebase-ids. Use structured data to mark up QRef annotations.
1990. QRef Collection Membership (NlpSemanticParsingQRefAnnotationCollectionMembership)
      • Description: Indicates the collection membership of an entity, providing relevance scores.
      • SEO Purpose: Enhances the categorization and discoverability of entity-related content.
      • How to Use: Clearly specify collection memberships in content. Use structured data to mark up collection membership information.
1991. QRef Entity Relationship (NlpSemanticParsingQRefAnnotationEntityRelationship)
      • Description: Represents relationships between entities, including implied relationships and link property names.
      • SEO Purpose: Improves the understanding of entity relationships, enhancing the relevance of search results.
      • How to Use: Clearly indicate relationships between entities. Use structured data to mark up entity relationship information.
1992. Merlot Category Data (NlpSemanticParsingQRefAnnotationMerlotCategoryData)
      • Description: Contains category information derived from collection membership.
      • SEO Purpose: Enhances the categorization and discoverability of content by providing detailed category data.
      • How to Use: Clearly specify category data in content. Use structured data to mark up Merlot category information.
1993. QRef SubCluster (NlpSemanticParsingQRefAnnotationSubCluster)
      • Description: Tracks individual clusters that an entity is a member of, providing cluster-specific information.
      • SEO Purpose: Improves the accuracy and relevance of search results by understanding entity subclusters.
      • How to Use: Clearly indicate subcluster memberships in content. Use structured data to mark up subcluster information.
1994. Related Entity (NlpSemanticParsingRelatedEntity)
      • Description: Stores relationships between annotations and other entities, including types of relationships.
      • SEO Purpose: Enhances the understanding of entity relationships, improving search relevance.
      • How to Use: Clearly specify relationships between entities. Use structured data to mark up related entity information.
1995. Coreference (NlpSemanticParsingSaftCoreference)
      • Description: Identifies coreference mentions (pronouns or nominals) resolved to an entity.
      • SEO Purpose: Improves the accuracy of content interpretation by resolving coreferences.
      • How to Use: Ensure coreferences are clear and correctly resolved in content. Use structured data to mark up coreference information.
1996. Measure (NlpSemanticParsingSaftMeasure)
      • Description: Identifies measures in queries, such as weights or quantities.
      • SEO Purpose: Enhances the precision of search results involving measures by accurately interpreting quantities.
      • How to Use: Clearly specify measures in content. Use structured data to mark up measure information.
1997. Mention Annotation (NlpSemanticParsingSaftMentionAnnotation)
      • Description: Identifies sub-spans of input with semantic relevance, such as persons, locations, or measures.
      • SEO Purpose: Improves the categorization and discoverability of content by highlighting semantically relevant spans.
      • How to Use: Clearly annotate semantically relevant spans in content. Use structured data to mark up mention annotations.
1998. Span (NlpSemanticParsingSaftSpan)
      • Description: Defines a category for a sub-span of the raw text of a query.
      • SEO Purpose: Enhances the precision of content interpretation by categorizing text spans.
      • How to Use: Clearly specify and categorize spans in content. Use structured data to mark up span information.
1999. Byte (NlxDataSchemaByte)
      • Description: Represents a single byte from a UTF-8 encoded character sequence.
      • SEO Purpose: Improves the precision of content interpretation at the byte level.
      • How to Use: Ensure content is properly encoded. Use structured data to mark up byte-level information.
2000. Character (NlxDataSchemaCharacter)
      • Description: Represents a single Unicode character.
      • SEO Purpose: Enhances the accuracy of content interpretation at the character level.
      • How to Use: Ensure content uses proper Unicode characters. Use structured data to mark up character-level information.
2001. Document (NlxDataSchemaDocument)
      • Description: Represents a single document.
      • SEO Purpose: Improves the discoverability and relevance of documents by clearly defining them.
      • How to Use: Clearly define and describe documents in content. Use structured data to mark up document information.
2002. Entity (NlxDataSchemaEntity)
      • Description: Represents an entity that may occur multiple times in the text.
      • SEO Purpose: Enhances the relevance of content by accurately identifying entities.
      • How to Use: Clearly specify entities in content. Use structured data to mark up entity information.
2003. Language Span (NlxDataSchemaLanguageSpan)
      • Description: Represents a span of text written in a specified language or languages.
      • SEO Purpose: Improves the relevance of multilingual content by accurately identifying language spans.
      • How to Use: Clearly specify language spans in content. Use structured data to mark up language information.
2004. Mention (NlxDataSchemaMention)
      • Description: Represents a mention of an entity, which may occur multiple times.
      • SEO Purpose: Enhances the accuracy of entity-related content by identifying mentions.
      • How to Use: Clearly specify mentions in content. Use structured data to mark up mention information.
2005. Paragraph (NlxDataSchemaParagraph)
      • Description: Represents a single paragraph.
      • SEO Purpose: Improves the readability and structure of content by clearly defining paragraphs.
      • How to Use: Clearly format paragraphs in content. Use structured data to mark up paragraph information.
2006. Scale Set (NlxDataSchemaScaleSet)
      • Description: Represents a standard set of scales.
      • SEO Purpose: Enhances the accuracy of content interpretation by providing standard scales.
      • How to Use: Clearly specify scales in content. Use structured data to mark up scale information.
2007. Sentence (NlxDataSchemaSentence)
      • Description: Represents a single sentence or utterance.
      • SEO Purpose: Improves the readability and structure of content by clearly defining sentences.
      • How to Use: Clearly format sentences in content. Use structured data to mark up sentence information.
2008. Token (NlxDataSchemaToken)
      • Description: Represents a word, punctuation mark, or other small piece of text.
      • SEO Purpose: Enhances the precision of content interpretation by accurately identifying tokens.
      • How to Use: Clearly specify tokens in content. Use structured data to mark up token information.
2009. Token Dependency Edge (NlxDataSchemaTokenDependencyEdge)
      • Description: (Deprecated) Represents one edge of the dependency parse.
      • SEO Purpose: Previously improved the accuracy of syntactic parsing.
      • How to Use: Use current fields like dependency_head and dependency_label for dependency parsing.
2010. Woodwing Item Metadata (OceanDataDocinfoWoodwingItemMetadata)
      • Description: Provides metadata describing an ‘item’ (article) in a Woodwing file.
      • SEO Purpose: Enhances the discoverability and relevance of articles by providing detailed metadata.
      • How to Use: Include detailed metadata for articles. Use structured data to mark up Woodwing item information.
2011. Ocean Document Info (OceanDocInfo)
      • Description: Represents ocean data in docserver results for whole documents.
      • SEO Purpose: Improves the relevance of search results for documents by providing detailed ocean data.
      • How to Use: Clearly specify ocean document data in content. Use structured data to mark up document information.
2012. Ocean Document Tag (OceanDocTag)
      • Description: Represents tags for ocean documents, enhancing their categorization.
      • SEO Purpose: Improves the discoverability and relevance of tagged content.
      • How to Use: Clearly specify tags for documents. Use structured data to mark up tag information.
2013. Book Specific Tag (OceanDocTagBookSpecific)
      • Description: Contains fields specific to books.
      • SEO Purpose: Enhances the relevance of book-related content by providing specific tags.
      • How to Use: Clearly specify book-specific tags. Use structured data to mark up book information.
2014. Book Specific Numbering Range (OceanDocTagBookSpecificNumberingRange)
      • Description: Provides volume numbering information, such as “Volume 1” or “Parts A-D.”
      • SEO Purpose: Improves the organization and discoverability of serialized content by specifying numbering ranges.
      • How to Use: Clearly indicate volume and part numbers in content. Use structured data to mark up numbering information.
2015. Catalog Specific Fields (OceanDocTagCatalogSpecific)
      • Description: These fields are specific to catalogs and provide detailed information relevant to catalog items.
      • SEO Purpose: Enhances search relevance for catalog-specific queries by providing detailed metadata.
      • How to Use: Clearly specify catalog-specific information. Use structured data to mark up catalog-specific fields.
2016. Contributor Information (OceanDocTagContributor)
      • Description: Provides a composite descriptor of contributors, including authors and editors.
      • SEO Purpose: Improves the relevance of search results by accurately identifying contributors.
      • How to Use: Clearly list and describe contributors. Use structured data to mark up contributor information.
2017. Magazine Specific Fields (OceanDocTagMagazineSpecific)
      • Description: Contains fields specific to magazines, providing detailed metadata.
      • SEO Purpose: Enhances the discoverability and relevance of magazine-related content.
      • How to Use: Clearly indicate magazine-specific information. Use structured data to mark up magazine-specific fields.
2018. Newspaper Specific Fields (OceanDocTagNewspaperSpecific)
      • Description: Contains fields specific to newspapers, offering detailed metadata.
      • SEO Purpose: Improves the relevance of search results for newspaper-related queries.
      • How to Use: Clearly specify newspaper-specific information. Use structured data to mark up newspaper-specific fields.
2019. Patent Specific Fields (OceanDocTagPatentSpecific)
      • Description: Contains fields specific to patents. Currently empty but intended for future use.
      • SEO Purpose: Enhances the relevance of search results for patent-related queries.
      • How to Use: Clearly indicate patent-specific information when available. Use structured data to mark up patent-specific fields.
2020. Work Cluster Details (OceanDocTagWorkCluster)
      • Description: Provides details of the work cluster for a volume.
      • SEO Purpose: Improves the organization and relevance of content by grouping related works.
      • How to Use: Clearly specify work cluster details. Use structured data to mark up work cluster information.
2021. GE Money Container (OceanGEMoney)
      • Description: Stores price information for GE (Google Editions) sales.
      • SEO Purpose: Enhances the accuracy of search results involving price information.
      • How to Use: Clearly specify prices in content. Use structured data to mark up price information.
2022. GE Price Data (OceanGEPrice)
      • Description: Contains data related to GE sales, including pricing and sale details.
      • SEO Purpose: Improves the relevance of search results for sale-related queries.
      • How to Use: Clearly specify sale details and prices. Use structured data to mark up GE price information.
2023. GE Price Locale (OceanGEPriceLocale)
      • Description: Provides locale-specific price information, including country code and offer price.
      • SEO Purpose: Enhances the relevance of search results by providing localized pricing information.
      • How to Use: Clearly specify locale-specific prices. Use structured data to mark up price information for different locales.
2024. Image Size (OceanImageSize)
      • Description: Provides size information for images.
      • SEO Purpose: Enhances the accuracy of search results involving images by providing size details.
      • How to Use: Clearly specify image sizes in content. Use structured data to mark up image size information.
2025. Locale Viewability (OceanLocaleViewability)
      • Description: Describes how a volume may be viewed in a particular locale.
      • SEO Purpose: Improves the relevance of search results by providing viewability information for different locales.
      • How to Use: Clearly specify viewability details for different locales. Use structured data to mark up viewability information.
2026. Viewability Dates (OceanLocaleViewabilityDates)
      • Description: Provides dates related to viewability.
      • SEO Purpose: Enhances the relevance of time-sensitive content by providing viewability dates.
      • How to Use: Clearly indicate viewability dates. Use structured data to mark up date information.
2027. Viewability Source Details (OceanLocaleViewabilitySourceDetails)
      • Description: Details how viewability for a locale and volume is derived, including partner and imprint information.
      • SEO Purpose: Improves the credibility and relevance of content by providing source details.
      • How to Use: Clearly specify viewability source details. Use structured data to mark up source information.
2028. Per-Doc Data (OceanPerDocData)
      • Description: Provides per-document data in the Ocean index, detailing indexing specifics.
      • SEO Purpose: Enhances search accuracy by providing detailed indexing information.
      • How to Use: Clearly indicate per-document data. Use structured data to mark up indexing details.
2029. Volume Access Rights (OceanVolumeAccessRights)
      • Description: Specifies access rights for a volume, including download allowances, text-to-speech permissions, and viewability restrictions.
      • SEO Purpose: Improves the user experience by clearly defining access rights and restrictions.
      • How to Use: Clearly specify access rights and restrictions. Use structured data to mark up access rights information.
2030. Computed Access Rights (OceanVolumeComputedAccessRights)
      • Description: Provides computed access rights for a volume, complementing partner and book metadata.
      • SEO Purpose: Enhances the relevance of search results by providing detailed access rights information.
      • How to Use: Clearly indicate computed access rights. Use structured data to mark up computed access rights information.
2031. Display Details (OceanVolumeDisplayDetails)
      • Description: Describes display attributes for a volume, relevant for OFE and indexing.
      • SEO Purpose: Improves the discoverability and presentation of content by providing display details.
      • How to Use: Clearly specify display attributes. Use structured data to mark up display details.
2032. Volume Imprint (OceanVolumeImprint)
      • Description: Provides commercial information for a volume, detailing the imprint or publisher subdivision.
      • SEO Purpose: Enhances the relevance and discoverability of content by providing imprint details.
      • How to Use: Clearly specify imprint information. Use structured data to mark up imprint details.
2033. Volume Viewability (OceanVolumeViewability)
      • Description: Specifies viewability details for a volume, including default and locale-specific viewability.
      • SEO Purpose: Improves the relevance of search results by providing detailed viewability information.
      • How to Use: Clearly indicate viewability details. Use structured data to mark up viewability information.
2034. Volume Viewability Locale (OceanVolumeViewabilityLocale)
      • Description: Provides locale-specific viewability details for a volume.
      • SEO Purpose: Enhances the relevance of search results by specifying viewability for different locales.
      • How to Use: Clearly specify locale-specific viewability details. Use structured data to mark up viewability information for different locales.
2035. Photo Bounding Box (OcrPhotoBoundingBox)
      • Description: Defines the bounding box for a patch containing a line, word, or symbol in a photo.
      • SEO Purpose: Enhances the accuracy of image-related search results by providing bounding box details.
      • How to Use: Clearly specify bounding boxes for text in images. Use structured data to mark up bounding box information.
2036. Photo Curve (OcrPhotoCurve)
      • Description: Provides details about the curve of a bounding box for OCR in photos.
      • SEO Purpose: Improves the accuracy of OCR results by understanding text curves in images.
      • How to Use: Clearly indicate curve details for text in images. Use structured data to mark up curve information.
2037. Curve Point (OcrPhotoCurvePoint)
      • Description: Represents a point in a curve for OCR, specifying x and y coordinates.
      • SEO Purpose: Enhances the precision of OCR results by providing detailed curve point information.
      • How to Use: Clearly specify curve points for text in images. Use structured data to mark up curve point information.
2038. Curved Bounding Box (OcrPhotoCurvedBoundingBox)
      • Description: Defines a curved bounding box for OCR, including midline curve and thickness.
      • SEO Purpose: Improves the accuracy of OCR results by providing detailed curved bounding box information.
      • How to Use: Clearly specify curved bounding boxes for text in images. Use structured data to mark up curved bounding box information.
2039. Text Box (OcrPhotoTextBox)
      • Description: Represents text with a bounding box in an image.
      • SEO Purpose: Enhances the accuracy of text-related search results in images.
      • How to Use: Clearly specify text boxes in images. Use structured data to mark up text box information.
2040. Official Key (OfficialPagesOfficialKey)
      • Description: Used as the key for official pages data, containing normalized queries.
      • SEO Purpose: Improves the relevance and accuracy of search results for official pages.
      • How to Use: Clearly specify normalized queries for official pages. Use structured data to mark up official key information.
2041. Official Query Set (OfficialPagesQuerySet)
      • Description: Contains a set of official queries and their country-language fingerprints.
      • SEO Purpose: Enhances the relevance of search results by providing detailed query sets for official pages.
      • How to Use: Clearly specify official queries and their fingerprints. Use structured data to mark up query set information.
2042. Document Entities (OrionDocEntitiesProto)
      • Description: Represents entities within a document, including document ID and encoded entities.
      • SEO Purpose: Improves the relevance of search results by accurately identifying document entities.
      • How to Use: Clearly specify entities within documents. Use structured data to mark up entity information.
2043. Pairwise Scoring Data (PairwiseQScoringData)
      • Description: Provides scoring data for pairwise comparisons, including confidence values.
      • SEO Purpose: Enhances the accuracy of search result rankings by providing detailed scoring data.
      • How to Use: Clearly specify scoring data for pairwise comparisons. Use structured data to mark up scoring information.
2044. Versioned Pairwise Item (PairwiseQVersionedItem)
      • Description: Represents a versioned item for pairwise Q scores used in experimentation.
      • SEO Purpose: Improves the relevance of search result rankings by using versioned scoring data.
      • How to Use: Clearly specify versioned pairwise items. Use structured data to mark up versioned scoring information.
2045. Internal/External Flexorgs (PeoplestackFlexorgsProtoInternalExternal)
      • Description: Describes internal and external flexorgs within an application context.
      • SEO Purpose: Enhances the relevance of search results by accurately identifying internal and external organizations.
      • How to Use: Clearly specify flexorg information. Use structured data to mark up internal/external flexorg details.
2046. Flexorg State Status (PeoplestackFlexorgsProtoInternalExternalStateStatus)
      • Description: Represents the state status of internal and external flexorgs within a given context.
      • SEO Purpose: Improves the accuracy of search results by providing detailed state status information.
      • How to Use: Clearly specify state status for flexorgs. Use structured data to mark up state status information.
2047. Per-Doc Debug Event (PerDocDebugEvent)
      • Description: Contains free-form debug information from various components.
      • SEO Purpose: Enhances the transparency and troubleshooting capabilities of search indexing.
      • How to Use: Clearly specify debug information. Use structured data to mark up debug event information.
2048. Alias ID (PersonalizationMapsAliasAliasId)
      • Description: Provides a unique association of an alias type and a number to identify the alias.
      • SEO Purpose: Improves the relevance of personalized search results by accurately identifying aliases.
      • How to Use: Clearly specify alias IDs. Use structured data to mark up alias information.
2049. Alias Icon (PersonalizationMapsAliasIcon)
      • Description: Represents an alias icon used in search and maps to quickly display icons.
      • SEO Purpose: Enhances the visual relevance of search results by providing quick display icons.
      • How to Use: Clearly specify alias icons. Use structured data to mark up icon information.
2050. Local Discovery Settings Metadata (PersonalizationSettingsApiProtoLocalDiscoveryLocalDiscoverySettingsMetadata)
      • Description: Contains metadata related to local discovery settings, such as dietary restrictions and cuisine preferences.
      • SEO Purpose: Improves the personalization and relevance of local discovery search results.
      • How to Use: Clearly specify local discovery settings metadata. Use structured data to mark up settings information.
2051. OPA Recipes Context (PersonalizationSettingsApiProtoLocalDiscoveryOpaRecipesContext)
      • Description: Represents user preferences regarding recipes, such as disliked cuisines.
      • SEO Purpose: Enhances the personalization of search results for recipe queries.
      • How to Use: Clearly specify user preferences for recipes. Use structured data to mark up recipes context information.
2052. Phil Per-Doc Data (PhilPerDocData)
      • Description: Provides data specific to Phil, including versioning.
      • SEO Purpose: Enhances the relevance of search results by providing detailed per-doc data.
      • How to Use: Clearly specify Phil-specific data. Use structured data to mark up per-doc information.
2053. Animation Metadata (PhotosAnimationMetadata)
      • Description: Contains metadata about animations or movies, including duration, loop count, and number of frames.
      • SEO Purpose: Enhances the relevance of search results by providing detailed animation metadata.
      • How to Use: Clearly specify animation details such as duration and loop count. Use structured data to mark up animation metadata.
2054. Dynamic Depth Metadata (PhotosDynamicDepthMetadata)
      • Description: Indicates the presence of dynamic depth in images.
      • SEO Purpose: Improves the accuracy of search results by identifying images with dynamic depth.
      • How to Use: Clearly indicate the presence of dynamic depth in images. Use structured data to mark up dynamic depth metadata.
2055. FourC Metadata (PhotosFourCMetadata)
      • Description: Contains metadata such as captions, copyright information, creators, and credit for images.
      • SEO Purpose: Enhances the relevance and credibility of image-related content by providing detailed metadata.
      • How to Use: Clearly specify captions, copyright information, and creator details. Use structured data to mark up FourC metadata.
2056. GDepth Metadata (PhotosGDepthMetadata)
      • Description: Metadata related to the GDepth XMP block, detailing depth information in images.
      • SEO Purpose: Improves the accuracy of search results involving depth-related image content.
      • How to Use: Clearly specify GDepth metadata. Use structured data to mark up depth information.
2057. HDR Metadata (PhotosHdrMetadata)
      • Description: Describes how an image expresses high dynamic range (HDR) information, including gainmap or specialized color space.
      • SEO Purpose: Enhances the visual relevance of HDR images in search results.
      • How to Use: Clearly specify HDR details such as gainmap and color space. Use structured data to mark up HDR metadata.
2058. Gainmap HDR Metadata (PhotosHdrMetadataGainmap)
      • Description: Provides details about gainmap-based HDR formats, allowing images to adhere to multiple gainmap specifications.
      • SEO Purpose: Improves the visual relevance and discoverability of gainmap HDR images.
      • How to Use: Clearly specify gainmap details for HDR images. Use structured data to mark up gainmap HDR metadata.
2059. Image Metadata (PhotosImageMetadata)
      • Description: Contains comprehensive metadata for images.
      • SEO Purpose: Enhances the relevance and accuracy of image-related search results by providing detailed metadata.
      • How to Use: Clearly specify all relevant image metadata. Use structured data to mark up image details.
2060. Panorama Metadata (PhotosPanoramaMetadata)
      • Description: Provides metadata for panoramic images, including whether they are spherical or VR180.
      • SEO Purpose: Improves the relevance of search results involving panoramic images.
      • How to Use: Clearly specify panoramic details such as spherical or VR180 status. Use structured data to mark up panorama metadata.
2061. Normalized Bounding Box (PhotosVisionGroundtruthdbNormalizedBoundingBox)
      • Description: Defines bounding box coordinates relative to the width and height of the image.
      • SEO Purpose: Enhances the accuracy of object detection in images by providing bounding box details.
      • How to Use: Clearly specify bounding box coordinates. Use structured data to mark up bounding box information.
2062. Object Recognition Feature Vector (PhotosVisionObjectrecFeatureVector)
      • Description: Contains feature vector data for object recognition, using single precision floating point data.
      • SEO Purpose: Improves the accuracy of object recognition in images by providing detailed feature vectors.
      • How to Use: Clearly specify feature vector details. Use structured data to mark up object recognition feature vectors.
2063. Geo-Location (PhotosVisionObjectrecGeoLocation)
      • Description: Provides the geo-location of a single point or the “center” of a group of points in an image.
      • SEO Purpose: Enhances the relevance of geographically tagged images in search results.
      • How to Use: Clearly specify geo-location details. Use structured data to mark up geo-location information.
2064. Global Feature (PhotosVisionObjectrecGlobalFeature)
      • Description: Represents global features for the image.
      • SEO Purpose: Improves the relevance and accuracy of image-related search results by providing global feature data.
      • How to Use: Clearly specify global features. Use structured data to mark up global feature information.
2065. Image Template (PhotosVisionObjectrecImageTemplate)
      • Description: Contains local and/or global features generated from an image, used for object recognition.
      • SEO Purpose: Enhances the accuracy of object recognition in images by providing comprehensive feature templates.
      • How to Use: Clearly specify image template details. Use structured data to mark up image template information.
2066. Image Template SubSet (PhotosVisionObjectrecImageTemplateSubSet)
      • Description: Contains local descriptors of a specific type, indicating the algorithm used for generation.
      • SEO Purpose: Improves the accuracy of image recognition by providing detailed local descriptor information.
      • How to Use: Clearly specify local descriptor types. Use structured data to mark up image template subsets.
2067. Local Descriptor (PhotosVisionObjectrecLocalDescriptor)
      • Description: Holds interest point data and an optional local descriptor vector for object recognition.
      • SEO Purpose: Enhances the precision of object recognition in images by providing detailed local descriptors.
      • How to Use: Clearly specify local descriptors. Use structured data to mark up local descriptor information.
2068. Matrix 2D (PhotosVisionObjectrecMatrix2D)
      • Description: Represents a 2×2 float matrix.
      • SEO Purpose: Improves the accuracy of image transformations and object recognition.
      • How to Use: Clearly specify 2×2 float matrix data. Use structured data to mark up matrix information.
2069. Quantized Feature Vector (PhotosVisionObjectrecQuantizedFeatureVector)
      • Description: Contains quantized/compressed feature vector data, with 8 bits per value.
      • SEO Purpose: Enhances the efficiency and accuracy of image recognition by providing compressed feature vectors.
      • How to Use: Clearly specify quantized feature vector details. Use structured data to mark up quantized feature information.
2070. Region of Interest (PhotosVisionObjectrecROI)
      • Description: Defines a region of interest in an image.
      • SEO Purpose: Improves the accuracy of search results involving specific regions within images.
      • How to Use: Clearly specify regions of interest. Use structured data to mark up region of interest information.
2071. Porn Flag Data (PornFlagData)
      • Description: Stores data for URLs flagged as pornographic, including referer and optional image scores.
      • SEO Purpose: Enhances content moderation and filtering in search results by identifying flagged URLs.
      • How to Use: Clearly specify flagged URLs and related data. Use structured data to mark up porn flag information.
2072. Postal Address (PostalAddress)
      • Description: Represents postal address information.
      • SEO Purpose: Improves the relevance and accuracy of search results involving location data.
      • How to Use: Clearly specify postal addresses. Use structured data to mark up address information.
2073. Precomputed Restricts (PrecomputedRestricts)
      • Description: Contains restricts computed before building a search index.
      • SEO Purpose: Enhances search efficiency by precomputing restricts.
      • How to Use: Clearly specify precomputed restricts. Use structured data to mark up restrict information.
2074. Premium Per-Doc Data (PremiumPerDocData)
      • Description: Provides per-document data for premium documents in the Google index.
      • SEO Purpose: Enhances the relevance and discoverability of premium content.
      • How to Use: Clearly specify premium document details. Use structured data to mark up per-doc data for premium content.
2075. Proto2 Bridge Message Set (Proto2BridgeMessageSet)
      • Description: Proto2’s version of MessageSet, used for compatibility and data transfer.
      • SEO Purpose: Ensures compatibility and data integrity across different protocol buffer versions.
      • How to Use: Clearly specify message set details. Use structured data to mark up message set information.
2076. Pseudo Video Data (PseudoVideoData)
      • Description: Contains data for pseudo videos, used in indexing and search.
      • SEO Purpose: Enhances the relevance of search results for pseudo video content.
      • How to Use: Clearly specify pseudo video details. Use structured data to mark up pseudo video information.
2077. Pseudo Video Data Transcript (PseudoVideoDataTranscript)
      • Description: Provides a time-coded transcription of a document’s audio track.
      • SEO Purpose: Improves the relevance of search results for audio and video content by providing transcriptions.
      • How to Use: Clearly specify transcriptions for audio and video content. Use structured data to mark up transcript information.
2078. Transcript Timestamp (PseudoVideoDataTranscriptTimestamp)
      • Description: Maps time/character correspondences, used to link snippets to their corresponding time and thumbnail.
      • SEO Purpose: Enhances the user experience by accurately linking transcriptions to timestamps.
      • How to Use: Clearly specify timestamp mappings. Use structured data to mark up transcript timestamp information.
2079. PToken (PtokenPToken)
      • Description: Expresses policy-relevant properties of data objects processed and stored in Google’s systems.
      • SEO Purpose: Enhances data security and compliance by specifying policy-relevant properties.
      • How to Use: Clearly specify policy-related properties. Use structured data to mark up PToken information.
2080. App Info (QualityActionsAppInfo)
      • Description: Provides information about apps, including name, package name, and confidence levels.
      • SEO Purpose: Enhances the relevance of search results involving apps by providing detailed app information.
      • How to Use: Clearly specify app details. Use structured data to mark up app information.
2081. App Info Source Data (QualityActionsAppInfoSourceData)
      • Description: Contains source data for app information, including confidence and source type.
      • SEO Purpose: Improves the accuracy of app-related search results by providing detailed source data.
      • How to Use: Clearly specify source data for apps. Use structured data to mark up app source information.
2082. App Info Source Data Allow List (QualityActionsAppInfoSourceDataAllowListSourceData)
      • Description: Provides additional signals for apps from allow lists.
      • SEO Purpose: Enhances the relevance of app-related search results by using allow list signals.
      • How to Use: Clearly specify allow list source data. Use structured data to mark up allow list information.
2083. App Info Source Data Media Provider (QualityActionsAppInfoSourceDataMediaProviderSourceData)
      • Description: Specifies information about media content served by the app.
      • SEO Purpose: Improves the relevance of media-related app content in search results.
      • How to Use: Clearly specify media provider source data. Use structured data to mark up media provider information.
2084. App Understanding Category (QualityActionsAppUnderstandingCategory)
      • Description: Categorizes apps into specific categories based on their function.
      • SEO Purpose: Enhances the relevance of app-related search results by categorizing apps accurately.
      • How to Use: Clearly specify app categories. Use structured data to mark up app category information.
2085. Customized Notification (QualityActionsCustomizedNotification)
      • Description: Deprecated. Previously used for customized notifications in apps.
      • SEO Purpose: Ensured relevance and personalization in app notifications.
      • How to Use: Use current methods for handling notifications in apps.
2086. Customized Notification Button (QualityActionsCustomizedNotificationButton)
      • Description: Deprecated. Previously used for buttons in customized notifications.
      • SEO Purpose: Enhanced user interaction with app notifications.
      • How to Use: Use current methods for adding interactive elements to notifications.
2087. Customized Notification Payload (QualityActionsCustomizedNotificationPayload)
      • Description: Deprecated. Previously used for the payload in customized notifications.
      • SEO Purpose: Enhanced the relevance and personalization of notification content.
      • How to Use: Use current methods for handling notification payloads.
2088. News Provider Annotation Data (QualityActionsNewsProviderAnnotationData)
      • Description: Contains annotation data for news providers, used in search indexing.
      • SEO Purpose: Improves the relevance of news-related search results by providing detailed provider annotations.
      • How to Use: Clearly specify news provider annotations. Use structured data to mark up news provider information.
2089. News Provider Annotation Data Provider (QualityActionsNewsProviderAnnotationDataProvider)
      • Description: Contains provider-specific annotation data for news content.
      • SEO Purpose: Enhances the relevance and accuracy of news-related search results.
      • How to Use: Clearly specify provider-specific data. Use structured data to mark up news provider information.
2090. Reminder (QualityActionsReminder)
      • Description: Represents a reminder, including details such as recurrence, location, and person.
      • SEO Purpose: Improves the relevance of reminder-related search results by providing detailed reminder information.
      • How to Use: Clearly specify reminder details. Use structured data to mark up reminder information.
2091. Reminder Document (QualityActionsReminderDocument)
      • Description: Represents a document associated with a reminder, such as Google Docs, Sheets, or Slides.
      • SEO Purpose: Enhances the relevance of search results for reminders linked to documents.
      • How to Use: Clearly specify document details for reminders. Use structured data to mark up reminder document information.
2092. Reminder Dynamite Group (QualityActionsReminderDynamiteGroup)
      • Description: Represents a Google Chat space associated with a reminder.
      • SEO Purpose: Improves the relevance of reminder-related search results involving Google Chat spaces.
      • How to Use: Clearly specify Google Chat space details for reminders. Use structured data to mark up reminder group information.
2093. Reminder Location (QualityActionsReminderLocation)
      • Description: Represents locations that trigger reminders, including specific locations, groups, or personal aliases.
      • SEO Purpose: Enhances the relevance of location-based reminders in search results.
      • How to Use: Clearly specify reminder-triggering locations. Use structured data to mark up location information.
2094. Reminder Location Category Info (QualityActionsReminderLocationCategoryInfo)
      • Description: Provides information about location categories for reminders, such as grocery stores or restaurants.
      • SEO Purpose: Improves the relevance of category-based reminders in search results.
      • How to Use: Clearly specify location category information. Use structured data to mark up category details.
2095. Reminder Location Chain Info (QualityActionsReminderLocationChainInfo)
      • Description: Provides information about chains associated with reminder locations.
      • SEO Purpose: Enhances the relevance of chain-based reminders in search results.
      • How to Use: Clearly specify chain information for reminder locations. Use structured data to mark up chain details.
2096. Reminder Person (QualityActionsReminderPerson)
      • Description: Represents a person associated with a reminder, either as the creator or recipient.
      • SEO Purpose: Improves the relevance of person-based reminders in search results.
      • How to Use: Clearly specify person details for reminders. Use structured data to mark up person information.
2097. Reminder Recurrence Info (QualityActionsReminderRecurrenceInfo)
      • Description: Provides recurrence rules for time-based repeating reminders.
      • SEO Purpose: Enhances the relevance of recurring reminders in search results.
      • How to Use: Clearly specify recurrence rules for reminders. Use structured data to mark up recurrence information.
2098. Ringtone (QualityActionsRingtone)
      • Description: Contains information about ringtones used for notifications, such as timers and alarms.
      • SEO Purpose: Improves the relevance of search results involving notification ringtones.
      • How to Use: Clearly specify ringtone details. Use structured data to mark up ringtone information.
2099. Room (QualityActionsRoom)
      • Description: Represents the room where an alarm or timer is set.
      • SEO Purpose: Enhances the relevance of room-based notifications in search results.
      • How to Use: Clearly specify room details for alarms and timers. Use structured data to mark up room information.
2100. Timer (QualityActionsTimer)
      • Description: Represents a timer, including its duration and expiration time.
      • SEO Purpose: Improves the relevance of timer-related search results.
      • How to Use: Clearly specify timer details. Use structured data to mark up timer information.
2101. Topic Embeddings Versioned Item (QualityAuthorityTopicEmbeddingsVersionedItem)
      • Description: Stores versioned topic embedding scores, used in search ranking.
      • SEO Purpose: Enhances the relevance of search results by providing topic embedding data.
      • How to Use: Clearly specify topic embedding scores. Use structured data to mark up embedding information.
2102. App Link (QualityCalypsoAppsLink)
      • Description: Contains application IDs linked to specific content.
      • SEO Purpose: Improves the relevance of app-linked content in search results.
      • How to Use: Clearly specify application IDs. Use structured data to mark up app link information.
2103. Live Op Detail (QualityCalypsoAppsUniversalAuLiveOpDetail)
      • Description: Provides information for serving a single LiveOp/LiveEvent.
      • SEO Purpose: Enhances the relevance of live operation events in search results.
      • How to Use: Clearly specify live operation details. Use structured data to mark up LiveOp information.
2104. Live Op Event (QualityCalypsoAppsUniversalAuLiveOpEvent)
      • Description: Contains the schedule for a single live operation event.
      • SEO Purpose: Improves the relevance of scheduled live events in search results.
      • How to Use: Clearly specify event schedules. Use structured data to mark up live event information.
2105. Live Op Format (QualityCalypsoAppsUniversalAuLiveOpFormat)
      • Description: Provides format information for a single LiveOp/LiveEvent.
      • SEO Purpose: Enhances the relevance of live operation formats in search results.
      • How to Use: Clearly specify format details. Use structured data to mark up LiveOp format information.
2106. Live Ops Detail Info (QualityCalypsoAppsUniversalAuLiveOpsDetailInfo)
      • Description: Stores all possible LiveOps/LiveEvents eligible to be shown for an app.
      • SEO Purpose: Improves the relevance of app-related live events in search results.
      • How to Use: Clearly specify eligible LiveOps/LiveEvents. Use structured data to mark up live event details.
2107. Universal Image (QualityCalypsoAppsUniversalImage)
      • Description: Contains image details, including URL, height, and width.
      • SEO Purpose: Enhances the visual relevance of image-related search results.
      • How to Use: Clearly specify image details. Use structured data to mark up image information.
2108. Universal Image Data (QualityCalypsoAppsUniversalImageData)
      • Description: Provides data for enhanced images, including cover images and screenshots.
      • SEO Purpose: Improves the relevance of image-related app content in search results.
      • How to Use: Clearly specify enhanced image data. Use structured data to mark up image details.
2109. Firefly Site Signal (QualityCopiaFireflySiteSignal)
      • Description: Contains site-level signals for the search stack.
      • SEO Purpose: Enhances the relevance of site-specific content in search results.
      • How to Use: Clearly specify site signals. Use structured data to mark up site-level signal information.
2110. External IDs (QualityDialogManagerExternalIds)
      • Description: Maps various external IDs to local results, including IDs from Google systems and third-party systems.
      • SEO Purpose: Improves the relevance of local results by mapping external identifiers.
      • How to Use: Clearly specify external IDs. Use structured data to mark up ID information.
2111. Local Intent Options (QualityDialogManagerLocalIntentOptions)
      • Description: Represents intent options for local results.
      • SEO Purpose: Enhances the relevance of local intent-based search results.
      • How to Use: Clearly specify local intent options. Use structured data to mark up intent information.
2112. Local Result (QualityDialogManagerLocalResult)
      • Description: Represents a local result returned by a backend.
      • SEO Purpose: Improves the relevance of local search results by providing detailed result information.
      • How to Use: Clearly specify local result details. Use structured data to mark up local result information.
2113. Reminder Client Type (QualityDialogManagerReminderClientType)
      • Description: Defines types of clients for reminders, used for UX customization, metrics, and visibility control.
      • SEO Purpose: Enhances the user experience and relevance of reminder-related search results.
      • How to Use: Clearly specify client types for reminders. Use structured data to mark up client type information.
2114. Preview Restrictions (QualityDniDocPreviewRestrictions)
      • Description: Sets per-document markup restrictions based on EUCD and global preview compliance.
      • SEO Purpose: Ensures compliance with legal requirements and enhances the relevance of preview content in search results.
      • How to Use: Clearly specify preview restrictions. Use structured data to mark up restriction information.
2115. Extended News Previews (QualityDniExtendedNewsPreviews)
      • Description: Provides extended preview data for news content.
      • SEO Purpose: Improves the relevance of news-related search results by providing detailed preview information.
      • How to Use: Clearly specify news preview details. Use structured data to mark up preview information.
2116. Fringe Query Prior Per-Doc Data (QualityFringeFringeQueryPriorPerDocData)
      • Description: Contains per-document data for fringe queries, used for classification.
      • SEO Purpose: Enhances the relevance of search results for fringe queries.
      • How to Use: Clearly specify fringe query data. Use structured data to mark up fringe query information.
2117. Complex Queries Output Rewrite (QualityGenieComplexQueriesComplexQueriesOutputRewrite)
      • Description: This factor involves the rewriting of complex queries to enhance search precision. It uses entities and textual rewrites to interpret and rephrase user queries more effectively.
      • SEO Purpose: By accurately rewriting complex queries, this factor helps ensure that search results are more relevant to the user’s intent, improving the overall search experience and increasing the likelihood of content discovery.
      • How to Use: Implement structured data to identify key entities within content. Ensure your content is clear and comprehensive to aid in accurate query rewriting.
2118. Output Rewrite Entity (QualityGenieComplexQueriesComplexQueriesOutputRewriteEntity)
      • Description: This factor identifies specific entities within a rewritten query. Entities are unique identifiers such as names or IDs that provide context to the query.
      • SEO Purpose: Enhancing the identification of entities helps improve the relevance and accuracy of search results, ensuring that users find exactly what they are looking for.
      • How to Use: Use schema markup to tag entities within your content, making it easier for algorithms to recognize and use them in query rewriting.
2119. Brainloc Attachment (QualityGeoBrainlocBrainlocAttachment)
      • Description: This factor involves attaching Brainloc annotations to documents, providing detailed geographic and locational context.
      • SEO Purpose: Geographic context can significantly improve the relevance of search results, especially for location-based queries.
      • How to Use: Include clear and detailed geographic information in your content. Use location-based keywords and metadata to enhance geographic relevance.
2120. Google Label Data (QualityLabelsGoogleLabelData)
      • Description: This factor involves applying labels to data for categorization and improved search indexing. Labels include confidence levels and provider information.
      • SEO Purpose: Proper labeling helps in the categorization and retrieval of content, making it easier for search engines to understand and present relevant results.
      • How to Use: Ensure your content is well-organized and labeled with appropriate metadata. Use structured data to provide additional context and categorization.
2121. Label Data Label (QualityLabelsGoogleLabelDataLabel)
      • Description: This factor provides detailed label information, including confidence scores and identifiers, to help categorize content accurately.
      • SEO Purpose: Accurate labeling enhances the search engine’s ability to classify and rank content correctly, improving visibility and discoverability.
      • How to Use: Use structured data to tag your content with relevant labels. Include confidence scores and identifiers where applicable to improve content categorization.
2122. Click Signals (QualityNavboostCrapsCrapsClickSignals)
      • Description: This factor involves collecting click and impression signals to understand user interactions with search results.
      • SEO Purpose: Analyzing click signals helps improve the ranking algorithm by understanding user preferences and behavior, leading to more relevant search results.
      • How to Use: Monitor and analyze user interactions on your website. Optimize your content and layout based on user behavior to improve click-through rates.
2123. Craps Data (QualityNavboostCrapsCrapsData)
      • Description: This factor involves aggregating data related to clicks and impressions across different devices, countries, and languages.
      • SEO Purpose: Aggregating this data helps in understanding user behavior patterns, which can be used to refine and improve search algorithms.
      • How to Use: Ensure your website is optimized for various devices and languages. Use analytics to gather and understand user interaction data.
2124. Craps Device (QualityNavboostCrapsCrapsDevice)
      • Description: This factor provides information about the device used for search queries, including interface type and operating system.
      • SEO Purpose: Device-specific data helps tailor search results to the user’s device, enhancing the user experience.
      • How to Use: Optimize your website for different devices and operating systems. Use responsive design to ensure a seamless experience across all devices.
2125. Feature Craps Data (QualityNavboostCrapsFeatureCrapsData)
      • Description: This factor involves aggregating click signals by country, device, language, and location to provide detailed insights into user behavior.
      • SEO Purpose: Detailed aggregation helps in fine-tuning search algorithms to cater to specific user segments, improving relevance and personalization.
      • How to Use: Use structured data to provide detailed information about the country, device, and language of your content. Analyze user behavior to tailor content accordingly.
2126. Stats with Weights (QualityNavboostCrapsStatsWithWeightsProto)
      • Description: This factor involves statistical analysis of click and impression data, including means, medians, variances, and standard deviations.
      • SEO Purpose: Statistical analysis helps in understanding the distribution and variability of user interactions, which can be used to improve ranking algorithms.
      • How to Use: Use analytics tools to perform statistical analysis on user interaction data. Optimize content based on insights gained from the analysis.
2127. Voter Token Bitmap (QualityNavboostGlueVoterTokenBitmapMessage)
      • Description: This factor involves using voter token bitmaps to aggregate unique query tokens, ensuring privacy-related filtering.
      • SEO Purpose: Ensuring privacy in data aggregation helps build user trust and compliance with data protection regulations.
      • How to Use: Implement privacy-compliant data collection practices. Use aggregation methods that protect user privacy while providing valuable insights.
2128. Experimental NSR Team Data (QualityNsrExperimentalNsrTeamData)
      • Description: This factor involves collecting versioned signals for live experiments, helping to test and refine search algorithms.
      • SEO Purpose: Experimentation allows for continuous improvement of search algorithms, leading to more relevant and accurate search results.
      • How to Use: Conduct regular experiments to test changes in your content strategy. Use versioned signals to track the impact of these changes.
2129. NSR Team Scoring Signal (QualityNsrExperimentalNsrTeamScoringSignal)
      • Description: This factor provides versioned signals used for scoring in experimental data.
      • SEO Purpose: Accurate scoring signals help refine the relevance and ranking of search results.
      • How to Use: Use structured data to provide clear scoring criteria for your content. Regularly update and test scoring signals.
2130. WSJ Data Wrapper (QualityNsrExperimentalNsrTeamWSJData)
      • Description: This factor is a wrapper for WSJ data, used for injecting experimental data and keys.
      • SEO Purpose: Ensures comprehensive data integration for experiments, improving the accuracy of search results.
      • How to Use: Use structured data to integrate external data sources into your content strategy. Ensure data is accurately represented and updated.
2131. Keto Versioned Data (QualityNsrKetoKetoVersionedData)
      • Description: This factor involves populating data to NSR and propagating it to various indexing and scoring systems.
      • SEO Purpose: Consistent data propagation helps maintain the accuracy and relevance of search results across different systems.
      • How to Use: Ensure your content is consistently updated and propagated across all relevant platforms. Use structured data to facilitate accurate indexing and scoring.
2132. NSR Versioned Data (QualityNsrNSRVersionedData)
      • Description: This factor involves versioned NSR score data used in search ranking.
      • SEO Purpose: Versioned data helps in tracking changes and improvements in search algorithms, ensuring continuous optimization.
      • How to Use: Regularly update and test versioned data in your content strategy. Use structured data to provide clear versioning information.
2133. NSR Chunks Proto (QualityNsrNsrChunksProto)
      • Description: This factor corresponds to the NSRChunks class, storing data for indexing and scoring.
      • SEO Purpose: Proper data storage ensures accurate and efficient indexing and scoring, improving search result relevance.
      • How to Use: Use structured data to store and manage content information. Ensure data is accurately indexed and scored.
2134. NSR Chunks with Source Info (QualityNsrNsrChunksWithSourceInfo)
      • Description: This factor includes NSR chunks with annotated source information.
      • SEO Purpose: Source information helps improve the accuracy and relevance of indexed content.
      • How to Use: Provide clear source information for your content. Use structured data to annotate and manage source details.
2135. NSR Data (QualityNsrNsrData)
      • Description: This factor involves NSR data used for indexing and ranking content.
      • SEO Purpose: Accurate NSR data helps improve the relevance and ranking of search results.
      • How to Use: Use structured data to provide detailed NSR information for your content. Ensure data is accurately indexed and ranked.
2136. NSR Data Cluster Uplift (QualityNsrNsrDataClusterUplift)
      • Description: This factor involves uplift values for clusters used in ranking algorithms.
      • SEO Purpose: Uplift values help improve the accuracy and relevance of clustered search results.
      • How to Use: Use clustering techniques to organize your content. Provide clear uplift values to improve ranking accuracy.
2137. NSR Data Embedding (QualityNsrNsrDataEmbedding)
      • Description: This factor involves embedding data for NSR, including version information and vectors.
      • SEO Purpose: Embedding data helps improve the relevance and contextual understanding of search results.
      • How to Use: Use embedding techniques to provide contextual information for your content. Ensure embedding data is accurate and up-to-date.
2138. NSR Data Encoded Embedding (QualityNsrNsrDataEncodedEmbedding)
      • Description: This factor involves encoded embedding data for NSR, including version information and encoded vectors.
      • SEO Purpose: Encoded embedding data helps improve the efficiency and accuracy of search result processing.
      • How to Use: Use encoding techniques to optimize embedding data. Ensure data is accurately encoded and versioned.
2139. NSR Data Metadata (QualityNsrNsrDataMetadata)
      • Description: This factor involves metadata for NSR data, providing additional context and information.
      • SEO Purpose: Metadata helps improve the accuracy and relevance of search results by providing additional context.
      • How to Use: Use structured data to provide detailed metadata for your content. Ensure metadata is accurate and comprehensive.
2140. NSR PQ Data (QualityNsrPQData)
      • Description: This factor involves data used to compute PQ scores for NSR, including subchunk data.
      • SEO Purpose: PQ data helps improve the accuracy and relevance of search results by providing detailed scoring information.
      • How to Use: Use structured data to provide detailed PQ data for your content. Ensure data is accurately computed and scored.
2141. NSR Versioned Float Signal (QualityNsrVersionedFloatSignal)
      • Description: This factor involves versioned float signals used for scoring in NSR.
      • SEO Purpose: Accurate float signals help improve the relevance and accuracy of search result rankings.
      • How to Use: Use structured data to provide clear float signals for your content. Regularly update and test signals for accuracy.
2142. NSR Versioned Int Signal (QualityNsrVersionedIntSignal)
      • Description: This factor involves versioned int signals used for scoring in NSR.
      • SEO Purpose: Accurate int signals help improve the relevance and accuracy of search result rankings.
      • How to Use: Use structured data to provide clear int signals for your content. Regularly update and test signals for accuracy.
2143. Document Intent Scores (QualityOrbitAsteroidBeltDocumentIntentScores)
      • Description: This factor involves scoring document intents for relevance in search results.
      • SEO Purpose: Accurate intent scoring helps improve the relevance of document-based search results.
      • How to Use: Use intent-based keywords and phrases in your content. Ensure content aligns with user search intents.
2144. Image Intent Scores (QualityOrbitAsteroidBeltImageIntentScores)
      • Description: This factor involves scoring image intents in the context of a landing page.
      • SEO Purpose: Accurate image intent scoring helps improve the relevance of image-based search results.
      • How to Use: Use intent-based keywords and phrases in image descriptions and alt text. Ensure images align with user search intents.
2145. Orbit Image Intent (QualityOrbitOrbitImageIntent)
      • Description: This factor involves storing information for a single image-only orbit intent.
      • SEO Purpose: Accurate image intent storage helps improve the relevance and accuracy of image-based search results.
      • How to Use: Use structured data to provide clear image intent information. Ensure images are tagged with relevant intents.
2146. Orbit Image Intents (QualityOrbitOrbitImageIntents)
      • Description: This factor involves managing multiple image-only orbit intents.
      • SEO Purpose: Proper management of image intents helps improve the relevance and accuracy of image-based search results.
      • How to Use: Use structured data to manage and tag multiple image intents. Ensure images are accurately categorized.
2147. Chosen Snippet Info (QualityPreviewChosenSnippetInfo)
      • Description: This factor involves providing information for chosen snippets in search results.
      • SEO Purpose: Accurate snippet information helps improve the relevance and quality of featured snippets.
      • How to Use: Use structured data to provide detailed snippet information. Ensure content is optimized for snippet selection.
2148. Chosen Snippet Tidbit Info (QualityPreviewChosenSnippetInfoTidbitInfo)
      • Description: This factor involves identifying and providing information for snippet tidbits.
      • SEO Purpose: Accurate tidbit information helps improve the relevance and quality of featured snippets.
      • How to Use: Use structured data to tag and identify snippet tidbits. Ensure content is optimized for snippet selection.
2149. Ranklab Snippet (QualityPreviewRanklabSnippet)
      • Description: This factor involves providing candidate snippet information and signal scores.
      • SEO Purpose: Accurate snippet scoring helps improve the relevance and quality of featured snippets.
      • How to Use: Use structured data to provide detailed snippet information and signal scores. Ensure content is optimized for snippet selection.
2150. Ranklab Title (QualityPreviewRanklabTitle)
      • Description: This factor involves providing data corresponding to a single title candidate for scoring and selection.
      • SEO Purpose: Accurate title scoring helps improve the relevance and quality of title-based search results.
      • How to Use: Use structured data to provide detailed title information and signal scores. Ensure titles are optimized for search relevance.
2151. Snippet Brain Features (QualityPreviewSnippetBrainFeatures)
      • Description: This factor involves providing brain scores for snippets to aid in selection and ranking.
      • SEO Purpose: Accurate brain scores help improve the relevance and quality of featured snippets.
      • How to Use: Use structured data to provide detailed brain score information for snippets. Ensure content is optimized for snippet selection.
2152. Snippet Document Features (QualityPreviewSnippetDocumentFeatures)
      • Description: This factor involves providing document-related features for snippet scoring.
      • SEO Purpose: Accurate document features help improve the relevance and quality of featured snippets.
      • How to Use: Use structured data to provide detailed document features for snippets. Ensure content is optimized for snippet selection.
2153. Snippet Experimental Features (QualityPreviewSnippetExperimentalFeatures)
      • Description: This factor involves providing experimental features for snippet scoring and selection.
      • SEO Purpose: Testing and implementing experimental features help improve the relevance and quality of featured snippets.
      • How to Use: Use structured data to tag experimental features for snippets. Regularly test and optimize content based on experimental results.
2154. Snippet Quality Features (QualityPreviewSnippetQualityFeatures)
      • Description: This factor involves quality-related features used in the scoring of snippets. These features help determine the relevance and usefulness of a snippet for a given query.
      • SEO Purpose: Ensuring high-quality snippets appear in search results helps improve user engagement and satisfaction, leading to better click-through rates and potential conversions.
      • How to Use: Optimize content to provide clear, concise, and high-quality information that directly answers common user queries. Use structured data to highlight key points that could be featured as snippets.
2155. Snippet Query Features (QualityPreviewSnippetQueryFeatures)
      • Description: This factor involves query-related features used in the scoring of snippets. These features assess how well the snippet matches the user’s query.
      • SEO Purpose: Matching snippets accurately to user queries improves the relevance of search results, enhancing user experience and trust in the search engine.
      • How to Use: Ensure content includes relevant keywords and phrases that match user search queries. Use natural language and focus on answering potential questions users might have.
2156. Snippet Query Term Coverage Features (QualityPreviewSnippetQueryTermCoverageFeatures)
      • Description: This factor evaluates the coverage of query terms within the snippet. It assesses how many of the query terms are present in the snippet.
      • SEO Purpose: High term coverage in snippets improves relevance and ensures that the snippets are addressing the user’s search intent comprehensively.
      • How to Use: Include important query terms within your content and ensure that these terms are naturally integrated into the main points or headings that could be featured as snippets.
2157. Radish Features (QualityPreviewSnippetRadishFeatures)
      • Description: This factor involves features like answer scores, passage coverage, and similarity scores between the query and the snippet. It uses advanced methods to assess how well a snippet matches the query.
      • SEO Purpose: Advanced assessment of snippet relevance ensures that the most accurate and helpful snippets are shown, enhancing user satisfaction.
      • How to Use: Use comprehensive content that covers various aspects of a topic in detail. Include sections that directly answer common questions with clear, concise answers.
2158. Product Site Data (QualityProductProductSiteData)
      • Description: This factor involves data related to product sites, stored as signal data in document joins. It includes detailed information about products for better search indexing.
      • SEO Purpose: Detailed product site data helps search engines understand product offerings better, improving the visibility of product pages in search results.
      • How to Use: Ensure product pages are well-structured with detailed product descriptions, specifications, and relevant metadata. Use schema markup to provide additional context.
2159. Product Site Data Locale (QualityProductProductSiteDataLocaleData)
      • Description: This factor involves product site data specific to a particular locale. It ensures that product information is tailored to different regions.
      • SEO Purpose: Localized product data improves relevance for users in different regions, enhancing the user experience and potentially boosting local search rankings.
      • How to Use: Tailor product descriptions and metadata to different locales. Include localized keywords and ensure compliance with local regulations and standards.
2160. Custom Search Engine URL Info (QualityProseCSEUrlInfo)
      • Description: This factor involves data related to custom search engines, including IDs and scores that help categorize and rank search results.
      • SEO Purpose: Accurate categorization and ranking of URLs within custom search engines improve the relevance and usefulness of search results for specific queries.
      • How to Use: Use custom search engines effectively by ensuring URLs are correctly categorized and scored. Regularly update and refine search engine settings to maintain relevance.
2161. Account Provenance (QualityQrewriteAccountProvenance)
      • Description: This factor involves annotating the source of cross-account personal data, providing context for data coming from different accounts.
      • SEO Purpose: Understanding the provenance of personal data helps improve the personalization and accuracy of search results, enhancing user experience.
      • How to Use: Ensure personal data used in content is well-documented and its source is clearly identified. Use structured data to annotate the provenance of personal information.
2162. Google Account Provenance (QualityQrewriteAccountProvenanceGoogleAccount)
      • Description: This factor involves annotating personal data from Google accounts, ensuring accurate identification and context.
      • SEO Purpose: Accurate annotation of Google account data helps personalize search results, improving relevance and user satisfaction.
      • How to Use: Encourage users to link their Google accounts for personalized experiences. Use structured data to annotate and manage account-related information.
2163. Third-Party Account Provenance (QualityQrewriteAccountProvenanceThirdPartyAccount)
      • Description: This factor involves annotating personal data from third-party accounts, providing context and improving data integration.
      • SEO Purpose: Integrating third-party account data helps enhance the personalization of search results, making them more relevant to the user.
      • How to Use: Ensure third-party data is accurately annotated and integrated into your systems. Use structured data to manage and provide context for third-party account information.
2164. Alternative Name Info (QualityQrewriteAlternativeNameInfo)
      • Description: This factor involves alternative names and their sources, helping recognize different names or spellings for the same entity.
      • SEO Purpose: Recognizing alternative names improves the accuracy and relevance of search results, especially for queries with multiple possible spellings or variations.
      • How to Use: Include alternative names and common misspellings in your content. Use structured data to provide information on alternative names.
2165. Calendar Reference (QualityQrewriteCalendarReference)
      • Description: This factor involves calendar references, including aliases and contact calendar names, to provide context for calendar-related queries.
      • SEO Purpose: Accurate calendar references help improve the relevance of search results for calendar-related queries, enhancing user experience.
      • How to Use: Use structured data to provide clear calendar references and aliases. Ensure calendar-related information is up-to-date and accurately annotated.
2166. Contact Calendar Name (QualityQrewriteContactCalendarName)
      • Description: This factor involves the names of contacts’ calendars, helping to provide context and relevance for calendar-related queries.
      • SEO Purpose: Including contact calendar names improves the personalization and accuracy of search results for calendar-related queries.
      • How to Use: Ensure contact calendar names are accurately annotated and integrated into your systems. Use structured data to manage and provide context for contact calendar information.
2167. Family Calendar Alias (QualityQrewriteFamilyCalendarAlias)
      • Description: This factor involves aliases for family calendars, helping to provide context and relevance for family-related calendar queries.
      • SEO Purpose: Accurate family calendar aliases help improve the relevance and personalization of search results for family-related queries.
      • How to Use: Use structured data to provide clear aliases for family calendars. Ensure family calendar-related information is up-to-date and accurately annotated.
2168. Personal Contact Data (QualityQrewritePersonalContactData)
      • Description: This factor involves metadata related to personal contacts, helping to provide context and relevance for contact-related queries.
      • SEO Purpose: Accurate personal contact data improves the relevance and personalization of search results for contact-related queries.
      • How to Use: Ensure personal contact data is accurately annotated and integrated into your systems. Use structured data to manage and provide context for personal contact information.
2169. Primary Calendar Alias (QualityQrewritePrimaryCalendarAlias)
      • Description: This factor involves aliases for primary calendars, helping to provide context and relevance for primary calendar-related queries.
      • SEO Purpose: Accurate primary calendar aliases help improve the relevance and personalization of search results for primary calendar-related queries.
      • How to Use: Use structured data to provide clear aliases for primary calendars. Ensure primary calendar-related information is up-to-date and accurately annotated.
2170. Account-Aware Calendar Alias (QualityQrewriteQRewriteAccountAwareCalendarAliasWrapper)
      • Description: This factor involves a wrapper for account-aware calendar aliases, used for query annotation and providing context for calendar-related queries.
      • SEO Purpose: Accurate account-aware calendar aliases help improve the relevance and personalization of search results for calendar-related queries.
      • How to Use: Use structured data to provide clear aliases for account-aware calendars. Ensure calendar-related information is up-to-date and accurately annotated.
2171. Relationship Memory Data (QualityQrewriteRelationshipMemoryData)
      • Description: This factor involves relationship-to-contact data provided by Assistant Memory, helping to provide context and relevance for relationship-related queries.
      • SEO Purpose: Accurate relationship memory data improves the personalization and relevance of search results for relationship-related queries.
      • How to Use: Ensure relationship memory data is accurately annotated and integrated into your systems. Use structured data to manage and provide context for relationship-related information.
2172. Mustang Rank Embed Info (QualityRankembedMustangMustangRankEmbedInfo)
      • Description: This factor involves embedding information used in Mustang ranking algorithms, providing context and improving ranking accuracy.
      • SEO Purpose: Accurate embedding information helps improve the relevance and accuracy of search result rankings.
      • How to Use: Use structured data to provide detailed embedding information for your content. Regularly update and test embedding data for accuracy.
2173. Mustang Rank Embed Info Compressed Embedding (QualityRankembedMustangMustangRankEmbedInfoCompressedEmbedding)
      • Description: This factor involves compressed embedding information used in Mustang ranking algorithms, optimizing storage and processing.
      • SEO Purpose: Compressed embedding information helps improve the efficiency and accuracy of search result rankings.
      • How to Use: Use efficient compression techniques to optimize embedding data. Ensure data is accurately compressed and stored.
2174. Launch App Info Per Doc Data (QualityRichsnippetsAppsProtosLaunchAppInfoPerDocData)
      • Description: This factor involves data related to launchable apps stored in document data, helping identify documents containing app links.
      • SEO Purpose: Accurate app information helps improve the relevance and usefulness of search results containing app links.
      • How to Use: Ensure app-related data is accurately annotated and integrated into your content. Use structured data to highlight app links and related information.
2175. Launchable App Per Doc Data (QualityRichsnippetsAppsProtosLaunchableAppPerDocData)
      • Description: This factor involves a subset of launchable application data stored in document data, used to identify app links at serving time.
      • SEO Purpose: Accurate launchable app data helps improve the relevance and usefulness of search results containing app links.
      • How to Use: Ensure launchable app data is accurately annotated and integrated into your content. Use structured data to highlight app links and related information.
2176. Salient Country (QualitySalientCountriesSalientCountry)
      • Description: This factor measures how salient a country is for the document, providing context for country-specific relevance.
      • SEO Purpose: Understanding the salience of a country helps improve the relevance of search results for users in that country.
      • How to Use: Include country-specific information and keywords in your content. Use structured data to provide context for the relevance of different countries.
2177. Salient Country Set (QualitySalientCountriesSalientCountrySet)
      • Description: This factor involves a set of salient countries for a document, providing context for country-specific relevance.
      • SEO Purpose: Understanding the salience of multiple countries helps improve the relevance of search results for users in different countries.
      • How to Use: Include country-specific information and keywords for multiple regions in your content. Use structured data to provide context for the relevance of different countries.
2178. Salient Terms Doc Data (QualitySalientTermsDocData)
      • Description: This factor involves additional salient-term-set-level information for a document, complementing salient term sets.
      • SEO Purpose: Detailed salient term data helps improve the relevance and accuracy of search results.
      • How to Use: Include relevant terms and keywords in your content. Use structured data to provide additional context for salient terms.
2179. Salient Term (QualitySalientTermsSalientTerm)
      • Description: This factor involves normalized terms and weights, providing important term-level data for search relevance.
      • SEO Purpose: Recognizing salient terms helps improve the accuracy and relevance of search results.
      • How to Use: Include relevant terms and keywords in your content. Use structured data to provide weights and context for salient terms.
2180. Salient Term Set (QualitySalientTermsSalientTermSet)
      • Description: This factor involves a collection of terms with associated weights that describe something, known as the salient terms.
      • SEO Purpose: Using salient terms helps improve the relevance and accuracy of search results.
      • How to Use: Include relevant terms and keywords in your content. Use structured data to provide context and weights for salient terms.
2181. Salient Terms Signal Data (QualitySalientTermsSignalData)
      • Description: This factor involves signal-specific salient-term-set-level information, storing internal data for populators.
      • SEO Purpose: Detailed signal data helps improve the relevance and accuracy of search results.
      • How to Use: Use structured data to provide detailed signal information for your content. Ensure data is accurately populated and maintained.
2182. Salient Terms Signal Term Data (QualitySalientTermsSignalTermData)
      • Description: This factor involves signal-specific term-level information, storing internal data for populators.
      • SEO Purpose: Detailed signal term data helps improve the relevance and accuracy of search results.
      • How to Use: Use structured data to provide detailed term-level information for your content. Ensure data is accurately populated and maintained.
2183. Sherlock Knex Annotation (QualitySherlockKnexAnnotation)
      • Description: This factor involves annotations for Sherlock Knex, providing detailed item-level data for search relevance.
      • SEO Purpose: Detailed annotations help improve the relevance and accuracy of search results.
      • How to Use: Use structured data to provide detailed annotations for your content. Ensure annotations are accurate and comprehensive.
2184. Sherlock Knex Annotation Item (QualitySherlockKnexAnnotationItem)
      • Description: This factor involves item-level data for Sherlock Knex annotations, including scores and equivalent IDs.
      • SEO Purpose: Accurate item-level data helps improve the relevance and accuracy of search results.
      • How to Use: Use structured data to provide detailed item-level information for your content. Ensure data is accurate and comprehensive.
2185. Shopping Attachment (QualityShoppingShoppingAttachment)
      • Description: This factor involves data related to shopping attachments, used for scoring and previewing shopping results.
      • SEO Purpose: Accurate shopping data helps improve the relevance and usefulness of shopping search results.
      • How to Use: Ensure shopping-related data is accurately annotated and integrated into your content. Use structured data to highlight shopping links and related information.
2186. Shopping Attachment Locale (QualityShoppingShoppingAttachmentLocale)
      • Description: This factor involves locale-specific data for shopping attachments, helping tailor shopping results to different regions.
      • SEO Purpose: Localized shopping data improves relevance for users in different regions, enhancing user experience and potentially boosting local search rankings.
      • How to Use: Tailor shopping descriptions and metadata to different locales. Include localized keywords and ensure compliance with local regulations and standards.
2187. Shopping Attachment Moka Facet Value (QualityShoppingShoppingAttachmentMokaFacetValue)
      • Description: This factor involves Moka product attribute facets, providing detailed attribute information for products.
      • SEO Purpose: Accurate attribute information helps improve the relevance and usefulness of shopping search results.
      • How to Use: Use structured data to provide detailed attribute information for your products. Ensure attributes are accurately tagged and categorized.
2188. Shopping Attachment Offer (QualityShoppingShoppingAttachmentOffer)
      • Description: This factor involves offer-related data for shopping attachments, including conditions, images, and merchant information.
      • SEO Purpose: Detailed offer information helps improve the relevance and attractiveness of shopping search results.
      • How to Use: Ensure offer-related data is accurately annotated and integrated into your content. Use structured data to highlight offers and related information.
2189. Shopping Attachment PBlock (QualityShoppingShoppingAttachmentPBlock)
      • Description: This factor involves PBlock data for shopping attachments, used for structuring product information.
      • SEO Purpose: Properly structured product information helps improve the relevance and clarity of shopping search results.
      • How to Use: Use structured data to provide detailed PBlock information for your products. Ensure data is accurately organized and presented.
2190. Shopping Attachment PBlock Image Info (QualityShoppingShoppingAttachmentPBlockImageInfo)
      • Description: This factor involves image-related data for PBlock in shopping attachments, including dimensions and URLs.
      • SEO Purpose: Accurate image data helps improve the visual appeal and relevance of shopping search results.
      • How to Use: Use high-quality images with accurate dimensions and URLs. Ensure images are well-optimized for search engines.
2191. Shopping Attachment Product (QualityShoppingShoppingAttachmentProduct)
      • Description: This factor involves product-related data for shopping attachments, including ratings, brand information, and images.
      • SEO Purpose: Detailed product information helps improve the relevance and attractiveness of shopping search results.
      • How to Use: Ensure product-related data is accurately annotated and integrated into your content. Use structured data to highlight product details and related information.
2192. Sitemap Breadcrumb Target (QualitySitemapBreadcrumbTarget)
      • Description: This factor involves sitelink candidates generated from breadcrumbs, providing context for navigation links.
      • SEO Purpose: Accurate breadcrumb data helps improve the user experience and relevance of navigation links in search results.
      • How to Use: Use structured data to provide detailed breadcrumb information. Ensure breadcrumbs are accurately tagged and categorized.
2193. Sitemap Breadcrumb Target Doc (QualitySitemapBreadcrumbTargetDoc)
      • Description: This factor involves document-level data for breadcrumb targets, including URL and title information.
      • SEO Purpose: Detailed document-level breadcrumb data helps improve the relevance and accuracy of navigation links in search results.
      • How to Use: Ensure breadcrumb-related data is accurately annotated and integrated into your content. Use structured data to highlight breadcrumb links and related information.
2194. Co-Click Target (QualitySitemapCoClickTarget)
      • Description: This factor involves data related to co-click targets, helping to identify commonly clicked links.
      • SEO Purpose: Understanding co-click patterns helps improve the relevance and usefulness of navigation links in search results.
      • How to Use: Analyze co-click patterns and optimize your navigation links accordingly. Use structured data to provide context for commonly clicked links.
2195. Co-Click Target Doc (QualitySitemapCoClickTargetDoc)
      • Description: This factor involves document-level data for co-click targets, including URLs and click patterns.
      • SEO Purpose: Detailed document-level co-click data helps improve the relevance and accuracy of navigation links in search results.
      • How to Use: Ensure co-click-related data is accurately annotated and integrated into your content. Use structured data to highlight commonly clicked links and related information.
2196. Co-Click Target Doc Co-Click by Locale (QualitySitemapCoClickTargetDocCoClickByLocale)
      • Description: This factor involves locale-specific data for co-click targets, helping tailor navigation links to different regions.
      • SEO Purpose: Localized co-click data improves relevance for users in different regions, enhancing user experience and potentially boosting local search rankings.
      • How to Use: Tailor navigation links and metadata to different locales. Include localized keywords and ensure compliance with local regulations and standards.
2197. Scoring Signals (QualitySitemapScoringSignals)
      • Description: This factor involves scoring signals used for computing the sitelink score, helping to determine the relevance of navigation links.
      • SEO Purpose: Accurate scoring signals help improve the relevance and usefulness of navigation links in search results.
      • How to Use: Use structured data to provide detailed scoring signals for your navigation links. Ensure data is accurately calculated and presented.
2198. Sporc Signals (QualitySitemapSporcSignals)
      • Description: Sporc Signals provide additional scoring data for a URL, specifically during online/serving time.
      • SEO Purpose: These signals help enhance the relevance and ranking of URLs by incorporating real-time data during the serving process.
      • How to Use: Ensure your website provides up-to-date and relevant content that can be dynamically scored during serving to improve search rankings.
2199. Subresult (QualitySitemapSubresult)
      • Description: Subresult information includes details about a single sub-result within a larger set of search results.
      • SEO Purpose: Detailed sub-result data can improve the understanding of individual result components, enhancing overall relevance.
      • How to Use: Optimize individual components of your content to ensure each sub-result is relevant and well-structured.
2200. Subresult List (QualitySitemapSubresultList)
      • Description: A container that encapsulates a list of sub-results.
      • SEO Purpose: Organizing sub-results into a comprehensive list helps improve the structure and presentation of search results.
      • How to Use: Ensure your content is well-organized, making it easier for search engines to compile and present relevant sub-results.
2201. Sitelink Target (QualitySitemapTarget)
      • Description: Represents a single sitelink target, including basic display information and potential dynamic ranking adjustments.
      • SEO Purpose: Proper sitelink targets improve navigation and enhance the user’s search experience.
      • How to Use: Use structured data to specify sitelink targets, ensuring URLs and titles are accurate and relevant.
2202. Sitelink Target Group (QualitySitemapTargetGroup)
      • Description: Represents a set of sitelink targets with an optional label to uniquely identify the group.
      • SEO Purpose: Grouping sitelink targets enhances the organization and relevance of search results.
      • How to Use: Organize sitelinks into logical groups and use labels to clearly define each group’s purpose.
2203. Third-Party Carousels List Item Metadata (QualitySitemapThirdPartyCarouselsListItemMuppetMetadata)
      • Description: Metadata about a list item in a third-party carousel, passed on to Muppet from indexing.
      • SEO Purpose: Enhances the relevance and presentation of third-party carousel items in search results.
      • How to Use: Ensure carousel items are accurately annotated with relevant metadata.
2204. Top URL (QualitySitemapTopURL)
      • Description: Contains the score and URL of a top-performing webpage.
      • SEO Purpose: Highlighting top URLs helps improve visibility and click-through rates.
      • How to Use: Optimize key pages to become top URLs by focusing on high-quality content and relevant keywords.
2205. Two-Level Target (QualitySitemapTwoLevelTarget)
      • Description: Represents a two-level sitelink target, including both first and second-level targets.
      • SEO Purpose: Enhances navigation by providing multiple levels of relevant sitelinks.
      • How to Use: Implement two-level sitelinks to improve site navigation and user experience.
2206. Snippet Bolded Range (QualitySnippetsTruncationSnippetBoldedRange)
      • Description: Indicates bolded ranges within printed snippet lines to highlight key information.
      • SEO Purpose: Emphasizes important parts of snippets, making them more noticeable and relevant to users.
      • How to Use: Ensure key information in your content is highlighted and likely to be bolded in search snippets.
2207. Snippet Bolded Range Position (QualitySnippetsTruncationSnippetBoldedRangePosition)
      • Description: Provides the byte offset and index of bolded ranges in snippets.
      • SEO Purpose: Accurate positioning of bolded ranges helps improve snippet relevance and user engagement.
      • How to Use: Optimize content structure to ensure important information is correctly positioned for bolding.
2208. Date Unreliability (QualityTimebasedDateUnreliability)
      • Description: Signals indicating unreliable dates for a URL.
      • SEO Purpose: Helps filter out content with unreliable dates, improving the accuracy and relevance of search results.
      • How to Use: Ensure date information on your site is accurate and reliable to avoid negative impacts on search rankings.
2209. Last Significant Update (QualityTimebasedLastSignificantUpdate)
      • Description: Details the last significant update date of a document, including adjustment info and source.
      • SEO Purpose: Recent and significant updates can boost the relevance of your content in search results.
      • How to Use: Regularly update your content with significant changes to maintain its relevance and improve search rankings.
2210. Last Significant Update Adjustments (QualityTimebasedLastSignificantUpdateAdjustments)
      • Description: Information about adjustments made to the last significant update date.
      • SEO Purpose: Accurate adjustment data helps improve the precision of update-related ranking signals.
      • How to Use: Document and manage significant content updates to ensure accurate reflection in search rankings.
2211. Page Type (QualityTimebasedPageType)
      • Description: Indicates the type of page, such as forum or Q&A page.
      • SEO Purpose: Page type classification helps search engines better understand and rank different types of content.
      • How to Use: Clearly define the type of content on your pages using structured data to improve relevance and rankings.
2212. Petacat Date Unreliability (QualityTimebasedPetacatDateUnreliability)
      • Description: Unreliable date signals for a specific domain and petacat.
      • SEO Purpose: Helps identify and filter out content with unreliable dates in specific categories.
      • How to Use: Ensure category-specific content has accurate and reliable date information.
2213. Syntactic Date (QualityTimebasedSyntacticDate)
      • Description: Stores syntactic date information for a document.
      • SEO Purpose: Accurate date information helps improve the relevance and timeliness of search results.
      • How to Use: Use structured data to provide precise date information for your content.
2214. Syntactic Date Date Range (QualityTimebasedSyntacticDateDateRange)
      • Description: Stores a date range if a single date is insufficient.
      • SEO Purpose: Helps provide more precise date information, improving the relevance of search results.
      • How to Use: Use date ranges where applicable to provide better context for your content.
2215. Syntactic Date Position (QualityTimebasedSyntacticDatePosition)
      • Description: Provides byte offset positions for dates within a document.
      • SEO Purpose: Accurate positioning of dates helps improve the relevance and user experience of search results.
      • How to Use: Ensure dates are accurately positioned within your content using structured data.
2216. Good Sites Data (QualityTravelGoodSitesData)
      • Description: Data related to good travel sites, stored as signals in docjoins.
      • SEO Purpose: Identifies high-quality travel sites to improve the relevance of travel-related search results.
      • How to Use: Ensure your travel site provides high-quality content and is accurately categorized.
2217. Good Sites Data I18n (QualityTravelGoodSitesDataI18n)
      • Description: Locale-specific data for good travel sites.
      • SEO Purpose: Localized data improves relevance for users in different regions.
      • How to Use: Provide localized content and metadata for your travel site to improve its relevance in different regions.
2218. Good Sites Data Signal (QualityTravelGoodSitesDataSignal)
      • Description: Raw signals used to determine the site quality score.
      • SEO Purpose: High-quality signals improve the relevance and ranking of travel sites.
      • How to Use: Ensure your site has strong quality signals, such as good reviews and user engagement.
2219. Video Language (QualityVidyaVideoLanguageVideoLanguage)
      • Description: Audio-based language information for a Watch Page.
      • SEO Purpose: Accurate language information improves the relevance of video search results.
      • How to Use: Provide accurate language metadata for your videos to improve their relevance in search results.
2220. Cluster Info (QualityViewsExtractionClusterInfo)
      • Description: Stores cluster scoring information for an entity.
      • SEO Purpose: Detailed cluster information improves the accuracy and relevance of entity-related search results.
      • How to Use: Ensure your content accurately represents entities and their relationships to improve cluster scoring.
2221. Transcript Annotations (QualityWebanswersTranscriptAnnotations)
      • Description: Wraps other annotations for auto-generated video captions.
      • SEO Purpose: Enhances the relevance and accuracy of video captions in search results.
      • How to Use: Ensure video captions are accurately annotated with relevant information.
2222. Video Transcript Annotations (QualityWebanswersVideoTranscriptAnnotations)
      • Description: Annotations for video transcripts, including language and timing information.
      • SEO Purpose: Accurate transcript annotations improve the relevance and accuracy of video search results.
      • How to Use: Provide detailed and accurate annotations for your video transcripts.
2223. YouTube Caption Timing Info Annotations (QualityWebanswersVideoYouTubeCaptionTimingInfoAnnotations)
      • Description: Timing information for YouTube captions, mapping sentence boundaries to timing offsets.
      • SEO Purpose: Accurate timing information improves the relevance and usability of video captions.
      • How to Use: Ensure YouTube captions have precise timing information to improve their relevance in search results.
2224. YouTube Caption Timing Info Annotations Instance (QualityWebanswersVideoYouTubeCaptionTimingInfoAnnotationsInstance)
      • Description: Byte-offset and timing information for YouTube captions.
      • SEO Purpose: Enhances the accuracy and relevance of YouTube captions in search results.
      • How to Use: Provide accurate byte-offset and timing information for your YouTube captions.
2225. Registration Info (RegistrationInfo)
      • Description: Domain registration information for a document.
      • SEO Purpose: Accurate registration information helps verify the legitimacy and relevance of a domain.
      • How to Use: Ensure your domain registration information is accurate and up-to-date.
2226. Embedding (ReneEmbedding)
      • Description: Represents an embedding vector with clusters.
      • SEO Purpose: Embedding vectors help improve the relevance of search results by understanding content relationships.
      • How to Use: Use embeddings to represent content relationships and improve search result relevance.
2227. Embedding Cluster (ReneEmbeddingCluster)
      • Description: Represents a cluster within the embedding space.
      • SEO Purpose: Clusters help identify and group related content, improving search result relevance.
      • How to Use: Ensure content is accurately represented within embedding clusters to improve its relevance in search results.
2228. Embedding Cluster List (ReneEmbeddingClusterList)
      • Description: Represents a list of clusters within the embedding space.
      • SEO Purpose: Grouping related content into clusters improves the organization and relevance of search results.
      • How to Use: Organize content into logical clusters within the embedding space.
2229. Geo Topic (RepositoryAnnotationsGeoTopic)
      • Description: Represents a geo-topic, including its normalized scores.
      • SEO Purpose: Geo-topics help improve the relevance of location-specific search results.
      • How to Use: Ensure content is accurately tagged with relevant geo-topics.
2230. Geo Topicality (RepositoryAnnotationsGeoTopicality)
      • Description: A set of geo-topics ordered by normalized scores.
      • SEO Purpose: Ordered geo-topics improve the relevance and accuracy of location-specific search results.
      • How to Use: Ensure geo-topics are accurately ordered and relevant to the content.
2231. Geo Topicality Score (RepositoryAnnotationsGeoTopicalityScore)
      • Description: Represents the raw score and type of a geo-topicality.
      • SEO Purpose: Accurate geo-topicality scores help improve the relevance of location-specific search results.
      • How to Use: Ensure geo-topicality scores are accurate and relevant to the content.
2232. Sentiment Snippet Annotations (RepositoryAnnotationsMustangSentimentSnippetAnnotations)
      • Description: Stores sentiment snippet information for content.
      • SEO Purpose: Sentiment snippets help improve the relevance and user engagement of search results.
      • How to Use: Ensure content includes sentiment annotations to improve snippet relevance.
2233. Breadcrumbs (RepositoryAnnotationsRdfaBreadcrumbs)
      • Description: Represents breadcrumb information extracted from a document.
      • SEO Purpose: Breadcrumbs improve site navigation and enhance the user’s search experience.
      • How to Use: Implement breadcrumb navigation on your site to improve search result relevance.
2234. Breadcrumb Crumb (RepositoryAnnotationsRdfaCrumb)
      • Description: Represents a single link in a breadcrumb trail.
      • SEO Purpose: Individual breadcrumb links help improve navigation and relevance.
      • How to Use: Ensure breadcrumb links are accurately represented and relevant to the content.
2235. Rich Snippets Application (RepositoryAnnotationsRdfaRdfaRichSnippetsApplication)
      • Description: Holds application information for rich snippets.
      • SEO Purpose: Rich snippets enhance the presentation and relevance of search results.
      • How to Use: Implement structured data for rich snippets to improve search result relevance.
2236. Application App Type Data (RepositoryAnnotationsRdfaRdfaRichSnippetsApplicationAppTypeData)
      • Description: Top-level app category type, such as game or application.
      • SEO Purpose: Accurate app type data helps improve the relevance of app-related search results.
      • How to Use: Ensure app category data is accurately represented in structured data.
2237. Application Country Price (RepositoryAnnotationsRdfaRdfaRichSnippetsApplicationCountryPrice)
      • Description: Represents the country-specific price of an application.
      • SEO Purpose: Country-specific pricing information improves the relevance of app-related search results.
      • How to Use: Provide accurate country-specific pricing data for your applications.
2238. Application Localized Trusted Genome (RepositoryAnnotationsRdfaRdfaRichSnippetsApplicationLocalizedTrustedGenome)
      • Description: Represents localized trusted genome tags matching the document’s locale.
      • SEO Purpose: Localized trusted genome data enhances the relevance and trustworthiness of app-related search results.
      • How to Use: Ensure trusted genome data is localized and accurately represented.
2239. Application Rank (RepositoryAnnotationsRdfaRdfaRichSnippetsApplicationRank)
      • Description: Represents the rank of an application, including app store link and category.
      • SEO Purpose: Accurate app ranking information improves the visibility and relevance of app-related search results.
      • How to Use: Provide accurate ranking data for your applications to improve their search result relevance.
2240. Application Rank Data (RepositoryAnnotationsRdfaRdfaRichSnippetsApplicationRankData)
      • Description: Represents ranking data for applications, including category IDs and ranks.
      • SEO Purpose: Detailed ranking data improves the relevance and visibility of app-related search results.
      • How to Use: Ensure application ranking data is accurately represented in structured data.
2241. Aggregated Entity Name Scores (RepositoryWebrefAggregatedEntityNameScores)
      • Description: Represents aggregated scores of entities for a given name across all sources.
      • SEO Purpose: Aggregated entity scores improve the relevance and accuracy of entity-related search results.
      • How to Use: Ensure entity names and scores are accurately aggregated and represented.
2242. Anchor Indices (RepositoryWebrefAnchorIndices)
      • Description: Identifies a set of anchors in a document, treated as equivalent by the annotator.
      • SEO Purpose: Accurate anchor indices improve the relevance of search results by identifying key content.
      • How to Use: Ensure anchor points in your content are accurately identified and annotated.
2243. Category Annotation (RepositoryWebrefCategoryAnnotation)
      • Description: High-level category annotations for documents and queries.
      • SEO Purpose: Category annotations improve the relevance and organization of search results.
      • How to Use: Use structured data to accurately categorize your content.
2244. Entity Annotations (RepositoryWebrefEntityAnnotations)
      • Description: Represents all annotations for a given concept in one document collection.
      • SEO Purpose: Comprehensive entity annotations improve the relevance and accuracy of search results.
      • How to Use: Ensure concepts in your content are accurately annotated and relevant.
2245. Entity Debug Info (RepositoryWebrefEntityDebugInfo)
      • Description: Provides debug information for entities, used for engineering and model training.
      • SEO Purpose: Debug info helps improve the accuracy and relevance of entity-related search results.
      • How to Use: Ensure debug information is accurately represented for entities in your content.
2246. Entity Link Metadata (RepositoryWebrefEntityLinkMetadata)
      • Description: Metadata about the nature of entity links.
      • SEO Purpose: Detailed link metadata improves the understanding and relevance of entity relationships.
      • How to Use: Ensure entity links are accurately represented and relevant.
2247. Entity Name Ratings (RepositoryWebrefEntityNameRatings)
      • Description: Stores all human ratings collected for a given entity name.
      • SEO Purpose: Human ratings improve the relevance and trustworthiness of entity-related search results.
      • How to Use: Collect and represent human ratings for entity names accurately.
2248. Entity Name Rating (RepositoryWebrefEntityNameRatingsEntityNameRating)
      • Description: This rating includes a comment justifying the decision, a label, and the source of the rating.
      • SEO Purpose: Ratings help evaluate the relevance and accuracy of entity names, impacting search result quality.
      • How to Use: Encourage positive user interactions and feedback to improve ratings of entity names associated with your content.
2249. Entity Score (RepositoryWebrefEntityNameScore)
      • Description: Represents a score assigned to an entity, reflecting its relevance and importance.
      • SEO Purpose: Entity scores impact the visibility and ranking of entities in search results.
      • How to Use: Optimize content to be highly relevant and authoritative to improve entity scores.
2250. Entity Name Source (RepositoryWebrefEntityNameSource)
      • Description: Represents data from various sources, including entity scores and multipliers.
      • SEO Purpose: Ensures comprehensive evaluation by aggregating scores from multiple sources.
      • How to Use: Source high-quality data from trusted entities to enhance your entity’s credibility.
2251. Entity Scores (RepositoryWebrefEntityScores)
      • Description: Contains a set of scores evaluating different aspects of an entity.
      • SEO Purpose: These scores influence the overall ranking and visibility of entities in search results.
      • How to Use: Ensure your content is comprehensive and of high quality to achieve better scores.
2252. Explained Range Info (RepositoryWebrefExplainedRangeInfo)
      • Description: Provides information about ranges in a document explained by an entity or related entities.
      • SEO Purpose: Enhances the understanding and relevance of entity annotations in search queries.
      • How to Use: Clearly define and annotate entities within your content to improve their explained ranges.
2253. Explained Range (RepositoryWebrefExplainedRangeInfoExplainedRange)
      • Description: A specific range in a document explained by an entity.
      • SEO Purpose: Detailed ranges help improve the accuracy of entity annotations in search results.
      • How to Use: Ensure that entities are clearly and accurately defined within specific ranges in your content.
2254. Extended Entity Name Score (RepositoryWebrefExtendedEntityNameScore)
      • Description: Stores region-specific score ratios for an entity.
      • SEO Purpose: Improves the relevance of entities in region-specific searches.
      • How to Use: Localize your content to improve its relevance in different regions.
2255. Extra Metadata (RepositoryWebrefExtraMetadata)
      • Description: Contains additional metadata about an entity derived from various data sources.
      • SEO Purpose: Enriches the entity data, improving its accuracy and relevance in search results.
      • How to Use: Provide comprehensive metadata to enhance the understanding and relevance of your entities.
2256. Fatcat Category (RepositoryWebrefFatcatCategory)
      • Description: Represents a category ID and its relative weight within a distribution.
      • SEO Purpose: Accurate categorization helps improve the relevance and ranking of content.
      • How to Use: Ensure your content is accurately categorized to improve its visibility in search results.
2257. Forwarding URLs (RepositoryWebrefForwardingUrls)
      • Description: Contains forwarding URLs within document metadata.
      • SEO Purpose: Helps manage and redirect traffic, maintaining link equity and relevance.
      • How to Use: Implement proper URL forwarding to ensure users and search engines can follow redirects accurately.
2258. Fprint Modifier Proto (RepositoryWebrefFprintModifierProto)
      • Description: Defines available modifier options as enums.
      • SEO Purpose: Helps in fine-tuning the fingerprints of entities to improve their relevance in search results.
      • How to Use: Utilize modifiers to adjust and refine entity fingerprints for better search performance.
2259. Freebase Type (RepositoryWebrefFreebaseType)
      • Description: Contains type information from Freebase.
      • SEO Purpose: Type information helps in categorizing and understanding entities better.
      • How to Use: Ensure accurate type information is provided for entities to improve their classification.
2260. Generic Indices (RepositoryWebrefGenericIndices)
      • Description: Identifies segment indices for various Webref SegmentTypes.
      • SEO Purpose: Helps in accurately indexing different segments of a document.
      • How to Use: Ensure your content is well-segmented and indexed to improve its search visibility.
2261. Geo Metadata Proto (RepositoryWebrefGeoMetadataProto)
      • Description: Contains geo-specific information about an entity.
      • SEO Purpose: Enhances the relevance of entities in location-specific searches.
      • How to Use: Provide accurate geo-metadata to improve the local search relevance of your content.
2262. Geo Metadata Proto Address Synonym (RepositoryWebrefGeoMetadataProtoAddressSynonym)
      • Description: Stores terms from AddressComponent that can be used as address synonyms.
      • SEO Purpose: Improves address recognition and relevance in geo-specific searches.
      • How to Use: Use accurate address components and synonyms to enhance local search relevance.
2263. Global Link Info (RepositoryWebrefGlobalLinkInfo)
      • Description: Groups together LinkInfo for all locales.
      • SEO Purpose: Ensures comprehensive link information across different regions.
      • How to Use: Provide complete and accurate link information for all relevant locales.
2264. Global Name Info (RepositoryWebrefGlobalNameInfo)
      • Description: Groups together NameInfo for all variants of a given name.
      • SEO Purpose: Ensures accurate representation and disambiguation of entity names.
      • How to Use: Ensure all name variants are accurately represented to improve search relevance.
2265. Human Ratings (RepositoryWebrefHumanRatings)
      • Description: Contains human ratings for various annotations.
      • SEO Purpose: Human ratings help validate the relevance and accuracy of search results.
      • How to Use: Encourage positive human interactions and feedback to improve ratings.
2266. Image Mention (RepositoryWebrefImageMention)
      • Description: Represents mentions of images, including confidence scores and image IDs.
      • SEO Purpose: Enhances the relevance of images in search results.
      • How to Use: Ensure images are accurately tagged and described to improve their search relevance.
2267. Image Query Indices (RepositoryWebrefImageQueryIndices)
      • Description: Identifies Image NavBoost queries within a document.
      • SEO Purpose: Helps improve the relevance of image search results.
      • How to Use: Optimize image queries and ensure they are accurately indexed.
2268. Juggernaut Indices (RepositoryWebrefJuggernautIndices)
      • Description: Identifies the source of Spore segments in a document.
      • SEO Purpose: Helps in accurately indexing and ranking content segments.
      • How to Use: Ensure content segments are accurately identified and indexed.
2269. KC Attribute Metadata (RepositoryWebrefKCAttributeMetadata)
      • Description: Metadata related to KC attributes and Q&A triggering.
      • SEO Purpose: Enhances the relevance of content in question and answer searches.
      • How to Use: Provide accurate KC attribute metadata to improve Q&A search relevance.
2270. KG Collection (RepositoryWebrefKGCollection)
      • Description: Represents a collection of knowledge graph entities.
      • SEO Purpose: Improves the understanding and relevance of interconnected entities.
      • How to Use: Ensure knowledge graph entities are accurately represented and interconnected.
2271. Latent Entities (RepositoryWebrefLatentEntities)
      • Description: Lists entities that are latent or related to a given entity.
      • SEO Purpose: Enhances the relevance of content by understanding related entities.
      • How to Use: Identify and connect related entities to improve content relevance.
2272. Latent Entity (RepositoryWebrefLatentEntity)
      • Description: Metadata about a latent entity and its relationship to a given entity.
      • SEO Purpose: Helps in understanding and ranking related entities.
      • How to Use: Ensure relationships between entities are accurately represented.
2273. Lexical Annotation (RepositoryWebrefLexicalAnnotation)
      • Description: Exposes lexical information from WordGraph features and LWT annotations.
      • SEO Purpose: Improves the understanding and relevance of lexical information in content.
      • How to Use: Provide accurate lexical annotations to enhance search relevance.
2274. Lexical Range (RepositoryWebrefLexicalRange)
      • Description: Defines a lexical range within a document.
      • SEO Purpose: Helps improve the accuracy and relevance of lexical annotations.
      • How to Use: Ensure lexical ranges are accurately defined and relevant to the content.
2275. Lightweight Token (RepositoryWebrefLightweightTokensMatchedLightweightToken)
      • Description: Contains information about lightweight token patterns for entity retrieval.
      • SEO Purpose: Enhances the relevance of content by identifying key lexical patterns.
      • How to Use: Use lightweight tokens to improve the accuracy of entity retrieval.
2276. Per Mention Lightweight Token (RepositoryWebrefLightweightTokensPerMentionLightweightToken)
      • Description: Collects lightweight token patterns for each mention.
      • SEO Purpose: Improves the relevance of mentions by identifying key patterns.
      • How to Use: Ensure mentions are accurately annotated with relevant token patterns.
2277. Per Name Lightweight Token (RepositoryWebrefLightweightTokensPerNameLightweightToken)
      • Description: Collects lightweight token patterns for each name.
      • SEO Purpose: Enhances the understanding and relevance of names by identifying key patterns.
      • How to Use: Use lightweight tokens to improve the accuracy of name annotations.
2278. Link Info (RepositoryWebrefLinkInfo)
      • Description: Represents all information about a specific/localized link.
      • SEO Purpose: Comprehensive link information helps improve the relevance and accuracy of search results.
      • How to Use: Ensure link information is complete and accurately localized.
2279. Link Kind Flags (RepositoryWebrefLinkKindFlags)
      • Description: A bitmap of boolean values associated with a link kind.
      • SEO Purpose: Helps in categorizing and understanding link types.
      • How to Use: Use link kind flags to accurately categorize and understand links.
2280. Link Kind Info (RepositoryWebrefLinkKindInfo)
      • Description: Information about the types of linked entities.
      • SEO Purpose: Detailed link type information improves the relevance of linked entities.
      • How to Use: Ensure link types are accurately represented and relevant.
2281. Localized String (RepositoryWebrefLocalizedString)
      • Description: Represents a localized string.
      • SEO Purpose: Localized strings improve the relevance of content in different regions.
      • How to Use: Provide accurate localized strings for different regions to improve search relevance.
2282. MDVC Metadata (RepositoryWebrefMdvcMetadata)
      • Description: Contains metadata about MDVC (multi-domain vertical classification).
      • SEO Purpose: Enhances the relevance of content across multiple domains and verticals.
      • How to Use: Ensure content is accurately classified across different domains and verticals.
2283. MDVC Metadata Per Vertical (RepositoryWebrefMdvcMetadataPerVertical)
      • Description: Per-vertical metadata for MDVC.
      • SEO Purpose: Improves the relevance of content within specific verticals.
      • How to Use: Provide accurate per-vertical metadata to enhance vertical-specific search relevance.
2284. Mention (RepositoryWebrefMention)
      • Description: Describes a single mention of an entity in a document or query.
      • SEO Purpose: Accurate mentions improve the relevance and understanding of entities in search results.
      • How to Use: Ensure entities are accurately mentioned and annotated in your content.
2285. Mention Additional Explained Range (RepositoryWebrefMentionAdditionalExplainedRange)
      • Description: Additional ranges covered by a mention.
      • SEO Purpose: Detailed mention ranges enhance the understanding and relevance of entity mentions.
      • How to Use: Provide comprehensive ranges for entity mentions to improve their relevance.
2286. Mention Component (RepositoryWebrefMentionComponent)
      • Description: Reference to a component of a compound mention.
      • SEO Purpose: Helps in accurately identifying and understanding compound mentions.
      • How to Use: Ensure compound mentions are accurately defined and referenced.
2287. Compound Mention (RepositoryWebrefMentionCompoundMention)
      • Description: Represents a single compound mention.
      • SEO Purpose: Accurate compound mentions improve the relevance and understanding of complex entities.
      • How to Use: Provide detailed annotations for compound mentions to enhance their relevance.
2288. Mention Debug Info (RepositoryWebrefMentionDebugInfo)
      • Description: Contains debug information for mentions, including clean text, snippets, and original text.
      • SEO Purpose: Debug info helps improve the accuracy and quality of entity mentions.
      • How to Use: Ensure debug information is accurately represented for mentions to aid in quality control.
2289. Mention Eval Info (RepositoryWebrefMentionEvalInfo)
      • Description: Evaluation information for mentions, including weight and rating.
      • SEO Purpose: Evaluation info helps assess the accuracy and relevance of entity mentions.
      • How to Use: Provide accurate evaluation information to improve the quality of entity mentions.
2290. Mention Ratings (RepositoryWebrefMentionRatings)
      • Description: Contains ratings for mentions in a document.
      • SEO Purpose: Mention ratings help validate the accuracy and relevance of entity mentions.
      • How to Use: Collect and represent ratings for mentions to improve their quality.
2291. Mention Ratings Single Mention Rating (RepositoryWebrefMentionRatingsSingleMentionRating)
      • Description: Represents a single mention rating.
      • SEO Purpose: Individual mention ratings help improve the accuracy of entity mentions.
      • How to Use: Ensure single mention ratings are accurately represented to aid in quality control.
2292. Meta Tag Indices (RepositoryWebrefMetaTagIndices)
      • Description: Identifies the source of Meta Content Tag segments in a document.
      • SEO Purpose: Accurate meta tags improve the relevance and indexing of content.
      • How to Use: Implement proper meta tags to enhance the visibility and relevance of your content.
2293. Name Debug Info (RepositoryWebrefNameDebugInfo)
      • Description: Collects signals from a query used for prior learning.
      • SEO Purpose: Debug info helps improve the accuracy and relevance of entity names.
      • How to Use: Ensure debug information is accurately represented for entity names.
2294. Name Debug Info Candidate Info (RepositoryWebrefNameDebugInfoCandidateInfo)
      • Description: Collects signals from a query and candidate.
      • SEO Purpose: Candidate info helps improve the understanding and relevance of entity names.
      • How to Use: Provide accurate candidate information to enhance entity name relevance.
2295. Name Info (RepositoryWebrefNameInfo)
      • Description: Represents all information about a specific/localized name.
      • SEO Purpose: Comprehensive name information improves the accuracy and relevance of entity names.
      • How to Use: Ensure all relevant information is provided for entity names.
2296. Name Scores (RepositoryWebrefNameScores)
      • Description: Represents scores for names, independent of associated entities.
      • SEO Purpose: Accurate name scores help improve the relevance of entity names in search results.
      • How to Use: Optimize names to achieve higher scores and improve search visibility.
2297. Ngram Context (RepositoryWebrefNgramContext)
      • Description: Represents an N-gram context encountered in a document.
      • SEO Purpose: N-gram contexts help improve the understanding and relevance of content.
      • How to Use: Ensure N-gram contexts are accurately represented to enhance content relevance.
2298. N-gram Mention (RepositoryWebrefNgramMention)
      • Description: Represents a mention of an entity within a specific N-gram context or a substring of it.
      • SEO Purpose: Helps in understanding the relevance of keywords within a document, impacting search rankings based on keyword mentions.
      • How to Use: Optimize content by including relevant N-grams to ensure the entity mentions are contextually accurate and meaningful.
2299. Oyster Type (RepositoryWebrefOysterType)
      • Description: Provides information about the type of an Oyster entity.
      • SEO Purpose: Helps classify and understand the nature of the entity, improving the accuracy of search results.
      • How to Use: Ensure that the type information for entities is accurately specified to improve classification and search relevance.
2300. Per Document Relevance Rating (RepositoryWebrefPerDocRelevanceRating)
      • Description: Represents relevance ratings for individual documents.
      • SEO Purpose: Influences how relevant a document is considered for specific queries, affecting its ranking.
      • How to Use: Optimize content to meet the relevance criteria to achieve higher ratings and better search rankings.
2301. Aggregated Document Ratings (RepositoryWebrefPerDocRelevanceRatings)
      • Description: Aggregates relevance ratings for URLs or document fingerprints.
      • SEO Purpose: Provides an overall assessment of a document’s relevance across different queries.
      • How to Use: Ensure comprehensive and high-quality content to achieve better aggregated ratings and improve overall search performance.
2302. Personalization Context Output (RepositoryWebrefPersonalizationContextOutput)
      • Description: Stores values associated with a personalization type in a key-value format.
      • SEO Purpose: Enhances personalized search results by using context-specific information.
      • How to Use: Utilize personalization data to tailor content to specific user preferences and improve search relevance.
2303. Personalization Context Outputs (RepositoryWebrefPersonalizationContextOutputs)
      • Description: Contains details about personalization and contextual scoring decisions from Personalized Query Understanding.
      • SEO Purpose: Helps fine-tune ranking or triggering logic based on personalized data.
      • How to Use: Leverage personalization insights to adjust content and improve its alignment with user intents and preferences.
2304. Name Entity Metadata (RepositoryWebrefPreprocessingNameEntityMetadata)
      • Description: Metadata about names, used for readability and decoding speed.
      • SEO Purpose: Provides detailed information about entity names, improving search accuracy.
      • How to Use: Ensure metadata for names is comprehensive and accurate to enhance entity recognition and relevance in search results.
2305. Name Entity Scores (RepositoryWebrefPreprocessingNameEntityScores)
      • Description: Abstract, source-independent scores for name entities.
      • SEO Purpose: Evaluates the quality and relevance of names, impacting search performance.
      • How to Use: Optimize entity names to achieve higher scores and improve their search visibility.
2306. Name Variant Signals (RepositoryWebrefPreprocessingNameVariantSignals)
      • Description: Contains signals for different name variants.
      • SEO Purpose: Helps understand and rank various name variants accurately.
      • How to Use: Ensure name variants are well-represented and relevant to improve their ranking in search results.
2307. Original Names (RepositoryWebrefPreprocessingOriginalNames)
      • Description: Represents the total number of original names and their versions from different sources.
      • SEO Purpose: Ensures comprehensive evaluation of name versions, improving accuracy.
      • How to Use: Provide accurate and complete original names to enhance their recognition and relevance.
2308. Original Name Details (RepositoryWebrefPreprocessingOriginalNamesOriginalName)
      • Description: Contains details about the original name, including its score, sources, and text.
      • SEO Purpose: Evaluates the quality of original names, influencing their relevance in search.
      • How to Use: Ensure original name details are accurate and well-documented to improve their relevance.
2309. URL Matching Metadata (RepositoryWebrefPreprocessingUrlMatchingMetadata)
      • Description: Metadata related to why a particular document was selected for entity joins.
      • SEO Purpose: Enhances the accuracy of URL matching in search results.
      • How to Use: Provide detailed metadata for URLs to ensure accurate matching and improve search relevance.
2310. URL Source Information (RepositoryWebrefPreprocessingUrlSourceInfo)
      • Description: Information about the source of a URL.
      • SEO Purpose: Helps understand the origin and credibility of URLs, impacting their ranking.
      • How to Use: Ensure URL source information is accurate and trustworthy to improve search rankings.
2311. Processor Counter (RepositoryWebrefProcessorCounter)
      • Description: Stores a single processor counter as a pair of name and value.
      • SEO Purpose: Helps track and measure processing activities, aiding in optimization.
      • How to Use: Utilize processor counters to monitor and optimize processing activities.
2312. Processor Timing (RepositoryWebrefProcessorTiming)
      • Description: Represents processor timings as produced by performance counters.
      • SEO Purpose: Helps measure and improve the efficiency of processing tasks.
      • How to Use: Analyze processor timings to identify and optimize performance bottlenecks.
2313. Product Metadata (RepositoryWebrefProductMetadata)
      • Description: Product-specific information about an entity, available in QrefMetadata output.
      • SEO Purpose: Enhances the relevance of product-related search results.
      • How to Use: Provide detailed product metadata to improve the accuracy and relevance of product searches.
2314. Query Indices (RepositoryWebrefQueryIndices)
      • Description: Identifies a set of NavBoost queries in a document, treated as equivalent by the annotator.
      • SEO Purpose: Helps understand and rank queries accurately.
      • How to Use: Ensure query indices are accurately represented to improve their relevance in search results.
2315. Range Annotations (RepositoryWebrefRangeAnnotations)
      • Description: Holds “non-entity” annotations of text.
      • SEO Purpose: Improves the understanding of text segments, enhancing search accuracy.
      • How to Use: Provide comprehensive range annotations to improve the understanding and relevance of text segments.
2316. Range Metadata (RepositoryWebrefRangeMetadata)
      • Description: Keeps metadata for an annotated range of a segment.
      • SEO Purpose: Enhances the understanding of annotated ranges, improving search relevance.
      • How to Use: Ensure range metadata is accurately represented to enhance the relevance of annotated segments.
2317. Document Mention Spans (RepositoryWebrefRefconDocumentMentionSpans)
      • Description: Encapsulates textual mention spans extracted from a document, split per token.
      • SEO Purpose: Helps in accurately identifying and understanding mention spans, impacting search relevance.
      • How to Use: Ensure mention spans are accurately represented to improve their relevance.
2318. Mention Spans (RepositoryWebrefRefconMentionSpans)
      • Description: Describes a mention annotated by Webref in a document.
      • SEO Purpose: Accurate mention spans enhance the understanding of entity mentions.
      • How to Use: Provide detailed mention spans to improve the accuracy and relevance of entity mentions.
2319. Query Statistics (RepositoryWebrefRefconQueryStats)
      • Description: Contains high-level search query statistics of a document.
      • SEO Purpose: Helps analyze the performance and relevance of queries, improving search accuracy.
      • How to Use: Utilize query statistics to optimize content and improve query performance.
2320. Document Metadata (RepositoryWebrefRefconRefconDocumentMetadata)
      • Description: Encapsulates additional metadata needed by Refcon for a document.
      • SEO Purpose: Enhances the understanding and relevance of document metadata.
      • How to Use: Provide comprehensive document metadata to improve search relevance.
2321. Refcon Name Info (RepositoryWebrefRefconRefconNameInfo)
      • Description: Represents Refcon name information in split concepts.
      • SEO Purpose: Helps accurately represent and rank names in search results.
      • How to Use: Ensure Refcon name information is accurately represented to improve name relevance.
2322. Reference Page Scores (RepositoryWebrefReferencePageScores)
      • Description: Signals used for identifying new reference pages, set by the reference-page-scorer processor.
      • SEO Purpose: Improves the identification and ranking of reference pages.
      • How to Use: Optimize content to be recognized as high-quality reference pages.
2323. Segment Mention (RepositoryWebrefSegmentMention)
      • Description: Represents a single mention within a document segment.
      • SEO Purpose: Accurate segment mentions improve the relevance and understanding of content.
      • How to Use: Ensure mentions within segments are accurately defined to enhance their relevance.
2324. Segment Mentions (RepositoryWebrefSegmentMentions)
      • Description: Annotations for a single document segment, containing all mentions for that segment.
      • SEO Purpose: Comprehensive segment annotations improve the accuracy of content segmentation.
      • How to Use: Provide detailed annotations for document segments to enhance their relevance.
2325. Semantic Date Range (RepositoryWebrefSemanticDateRange)
      • Description: Represents a date range for an entity, such as the lifespan of a person or the release date of a movie.
      • SEO Purpose: Accurate date ranges enhance the temporal relevance of entities in search results.
      • How to Use: Ensure date ranges are accurately defined and relevant to the entity.
2326. Simplified Anchor (RepositoryWebrefSimplifiedAnchor)
      • Description: A compact representation of anchor data from docjoins, which can separate onsite and off-domain anchors.
      • SEO Purpose: Helps in understanding and scoring anchor text accurately.
      • How to Use: Provide accurate anchor data to improve link relevance and ranking.
2327. Simplified Anchors (RepositoryWebrefSimplifiedAnchors)
      • Description: A collection of simplified anchors.
      • SEO Purpose: Enhances the understanding and relevance of anchor text in search results.
      • How to Use: Ensure anchor collections are accurately represented to improve link relevance and ranking.
2328. Simplified Composite Document (RepositoryWebrefSimplifiedCompositeDoc)
      • Description: Represents information close to a composite document but compresses anchor representation to save space.
      • SEO Purpose: Improves the efficiency and relevance of composite document data.
      • How to Use: Optimize composite document data for space and relevance efficiency.
2329. Forwarding Duplicate URL (RepositoryWebrefSimplifiedForwardingDup)
      • Description: Stores the URL of a forwarding duplicate.
      • SEO Purpose: Identifies and manages duplicate URLs to ensure that search engines recognize the canonical URL, improving page ranking and avoiding duplicate content penalties.
      • How to Use: Ensure correct canonical tags and manage URL redirects to point to the preferred URL, helping consolidate SEO value.
2330. Sub-Segment Index (RepositoryWebrefSubSegmentIndex)
      • Description: Contains information to identify sub-segments within a document, such as specific queries, query features, or anchors.
      • SEO Purpose: Enhances search engines’ understanding of specific parts of a document, improving the relevance of search results for particular queries.
      • How to Use: Optimize key sections of your content, ensuring important sub-segments are clearly defined and relevant to targeted keywords.
2331. Support Transfer Rule (RepositoryWebrefSupportTransferRule)
      • Description: Represents rules for transferring support between entities based on context, helping to address cases where annotations do not match user intent.
      • SEO Purpose: Ensures more accurate entity annotations in search results, improving user satisfaction with the relevance of the returned results.
      • How to Use: Ensure contextually relevant content and entity mentions to align with user intent, leveraging support transfer rules.
2332. Task Data (RepositoryWebrefTaskData)
      • Description: Contains information about the quality and readability of data shown to raters, including project and task details.
      • SEO Purpose: Helps improve the accuracy and quality of content evaluations, impacting the ranking and presentation of content in search results.
      • How to Use: Focus on high-quality, readable content to ensure positive evaluations from raters, enhancing overall search visibility.
2333. Task Details (RepositoryWebrefTaskDetails)
      • Description: Provides information about how raters interact with and perceive the presented tasks.
      • SEO Purpose: Improves understanding of rater interactions and feedback, guiding adjustments to content for better rankings.
      • How to Use: Analyze task details to understand rater behavior and preferences, optimizing content accordingly for improved user engagement and SEO performance.
2334. Triple Annotation (RepositoryWebrefTripleAnnotation)
      • Description: Annotates triples (subject-predicate-object) within a document, including confidence scores and verification status.
      • SEO Purpose: Enhances the semantic understanding of content, improving relevance and accuracy in search results.
      • How to Use: Ensure clear and accurate annotations of key information in your content to enhance its semantic value and search performance.
2335. Triple Annotations (RepositoryWebrefTripleAnnotations)
      • Description: Represents a collection of triples annotated by Webref/Webit, included in WebrefEntities.
      • SEO Purpose: Aggregates semantic information, aiding in the accurate interpretation and ranking of content.
      • How to Use: Maintain comprehensive and precise annotations of triples to ensure high-quality semantic data for search engines.
2336. Triple Mention (RepositoryWebrefTripleMention)
      • Description: Details mentions of triples within a document, including scope and specific mentions of subjects, predicates, and values.
      • SEO Purpose: Provides context and specificity to semantic data, improving search result relevance.
      • How to Use: Accurately annotate and highlight key triples within your content to provide clear semantic cues for search engines.
2337. Universal N-gram Data (RepositoryWebrefUniversalNgramData)
      • Description: Contains n-gram data used during model building.
      • SEO Purpose: Enhances the understanding of keyword patterns and relationships within content.
      • How to Use: Optimize content with relevant n-grams to align with search engine models and improve keyword relevance.
2338. Annotation Statistics (RepositoryWebrefWebrefAnnotationStats)
      • Description: Provides detailed statistics about annotations within a document, such as the number of entities matched and mention counts.
      • SEO Purpose: Helps tune scoring functions based on annotation data, influencing search rankings.
      • How to Use: Regularly review and optimize annotations to ensure comprehensive coverage and relevance, enhancing search performance.
2339. Annotation Metadata (RepositoryWebrefWebrefAttachmentMetadata)
      • Description: Metadata for individual entity annotations.
      • SEO Purpose: Provides additional context and information about entity annotations, improving their accuracy and impact.
      • How to Use: Ensure metadata is thorough and accurate to support robust entity annotations, enhancing search relevance.
2340. Document Information (RepositoryWebrefWebrefDocumentInfo)
      • Description: Contains information that applies globally to the document.
      • SEO Purpose: Provides an overarching context for the document, aiding in accurate content categorization and ranking.
      • How to Use: Maintain detailed and accurate global document information to support overall content relevance and SEO performance.
2341. Entity Collection (RepositoryWebrefWebrefEntities)
      • Description: Represents a collection of entities returned by the WebRef service.
      • SEO Purpose: Aggregates entity data for improved semantic understanding and relevance in search results.
      • How to Use: Ensure entity collections are comprehensive and accurately represented to enhance semantic search performance.
2342. Entity Information (RepositoryWebrefWebrefEntity)
      • Description: Contains all available information about a single entity within WebRef.
      • SEO Purpose: Provides detailed entity data to improve search result relevance and accuracy.
      • How to Use: Ensure entity information is detailed and accurate to support high-quality search results.
2343. Entity Relationships (RepositoryWebrefWebrefEntityRelationship)
      • Description: Information regarding links between annotated entities.
      • SEO Purpose: Enhances the understanding of relationships between entities, improving contextual relevance in search results.
      • How to Use: Accurately define and document relationships between entities to support improved contextual search relevance.
2344. Mustang Attachment (RepositoryWebrefWebrefMustangAttachment)
      • Description: Deprecated attachment for storing WebRef entities and IQL expressions in Mustang/TG.
      • SEO Purpose: Provides a legacy method for storing and accessing entity data.
      • How to Use: Migrate to the recommended UDR system for improved features and support.
2345. Outlink Information (RepositoryWebrefWebrefOutlinkInfo)
      • Description: Information about outlinks for a specific target URL from an annotated document.
      • SEO Purpose: Helps understand and manage outbound links, improving link structure and SEO.
      • How to Use: Ensure outlinks are relevant and appropriately documented to support link strategy and SEO.
2346. Outlink Information List (RepositoryWebrefWebrefOutlinkInfos)
      • Description: Aggregated information about outlinks from an annotated document.
      • SEO Purpose: Provides a comprehensive view of outbound links, aiding in link strategy and SEO optimization.
      • How to Use: Regularly review and manage outbound links to ensure they are relevant and beneficial to your SEO strategy.
2347. Webref Status (RepositoryWebrefWebrefStatus)
      • Description: Contains status information such as data epoch and version number of the annotator.
      • SEO Purpose: Provides insights into the status and versioning of annotation data, aiding in debugging and optimization.
      • How to Use: Monitor and update annotation status information to ensure data accuracy and alignment with the latest models.
2348. Wikipedia Category Information (RepositoryWebrefWikipediaCategory)
      • Description: Information about a Wikipedia category, typically found at the bottom of a page.
      • SEO Purpose: Helps categorize and understand the relevance of content within specific categories.
      • How to Use: Ensure accurate categorization of content to improve its relevance and alignment with user queries.
2349. Wikipedia Geocode (RepositoryWebrefWikipediaGeocode)
      • Description: Geocodes extracted from Wikipedia joins.
      • SEO Purpose: Enhances the geographical understanding of content, improving location-based search relevance.
      • How to Use: Provide accurate geocodes to support location-based searches and improve content relevance for geographical queries.
2350. Conjunction (ResearchScamCoscamConjunction)
      • Description: Represents an AND clause containing multiple OR clauses (disjunctions).
      • SEO Purpose: Helps in refining and optimizing search queries by combining multiple conditions to filter results.
      • How to Use: Use conjunctions to narrow down search results by combining multiple relevant disjunctions, ensuring more precise search outputs.
2351. Disjunction (ResearchScamCoscamDisjunction)
      • Description: Represents an OR clause that contains multiple group

        tuples.

      • SEO Purpose: Broadens search criteria by including multiple possible matches within a single clause.
      • How to Use: Use disjunctions to expand search results by including several related terms or groups, capturing a wider range of relevant content.
2352. Easy Conjunction (ResearchScamCoscamEasyConjunction)
      • Description: Represents an AND-of-ORs block, simplifying complex query logic.
      • SEO Purpose: Enhances query efficiency by organizing complex conditions in a structured manner.
      • How to Use: Utilize easy conjunctions to simplify the management of complex queries, improving search performance and relevance.
2353. Easy Disjunction (ResearchScamCoscamEasyDisjunction)
      • Description: Represents one OR clause within a simplified conjunction.
      • SEO Purpose: Allows for the inclusion of multiple potential matches in search queries.
      • How to Use: Apply easy disjunctions to add flexibility to your search criteria, enabling a broader scope of relevant results.
2354. Easy Restrict Definition (ResearchScamCoscamEasyRestrictDefinition)
      • Description: Represents an OR-of-ANDs-of-ORs block, defining complex restriction criteria.
      • SEO Purpose: Helps in defining detailed search restrictions, improving the precision of search results.
      • How to Use: Use easy restrict definitions to create intricate search filters that narrow down results based on specific criteria.
2355. Restrict Definition (ResearchScamCoscamRestrictDefinition)
      • Description: Defines a single OR-of-ANDs-of-ORs restrict definition using multiple conjunctions and disjunctions.
      • SEO Purpose: Allows for detailed and specific search restrictions, enhancing the accuracy of search results.
      • How to Use: Implement restrict definitions to apply comprehensive filters to search queries, ensuring highly relevant search outputs.
2356. Restrict Tokens V2 (ResearchScamCoscamRestrictTokensV2)
      • Description: A set of group

        tuples collated by group for use in restricted searches.

      • SEO Purpose: Filters search results based on predefined token groups, improving relevance.
      • How to Use: Use restrict tokens to limit search results to those matching specific token groups, enhancing search accuracy.
2357. Token Group (ResearchScamCoscamTokenGroup)
      • Description: Defines a group of tokens with a name and optional human-readable strings for debugging.
      • SEO Purpose: Organizes tokens into manageable groups for more efficient search filtering.
      • How to Use: Create token groups to categorize related terms, making it easier to apply targeted search restrictions.
2358. Custom Restrict Evaluation Stats (ResearchScamCustomRestrictEvaluationStats)
      • Description: Contains evaluation statistics for custom restricts.
      • SEO Purpose: Provides insights into the effectiveness of custom search restrictions.
      • How to Use: Analyze evaluation stats to refine custom restricts, improving search accuracy and relevance.
2359. Custom Restrict Namespace (ResearchScamCustomRestrictNamespace)
      • Description: Defines a custom restrict namespace, which may not be symmetric and can vary between queries and database points.
      • SEO Purpose: Allows for the creation of tailored search restricts, enhancing the precision of search results.
      • How to Use: Define custom namespaces to apply specific restrictions to search queries, ensuring more relevant results.
2360. Generic Feature Vector (ResearchScamGenericFeatureVector)
      • Description: Represents a collection of features used in search and matching algorithms.
      • SEO Purpose: Provides a structured way to represent and process search features.
      • How to Use: Utilize generic feature vectors to incorporate multiple features into search algorithms, improving the relevance of results.
2361. Generic Feature Vector Crowding (ResearchScamGenericFeatureVectorCrowding)
      • Description: Contains configuration for crowding, limiting the number of similar neighbors in search results.
      • SEO Purpose: Prevents search results from being dominated by similar items, enhancing result diversity.
      • How to Use: Configure crowding settings to ensure diverse and representative search results.
2362. Generic Feature Vector Fixed Point Metadata (ResearchScamGenericFeatureVectorFixedPointMetadata)
      • Description: Metadata for feature vectors transformed from floating-point to fixed-point representation.
      • SEO Purpose: Improves the performance and efficiency of search algorithms.
      • How to Use: Use fixed-point metadata to optimize the processing of feature vectors, enhancing search performance.
2363. Generic Feature Vector Restrict Tokens (ResearchScamGenericFeatureVectorRestrictTokens)
      • Description: Tokens used to perform restricted searches based on boolean rules.
      • SEO Purpose: Enhances the precision of search results by applying specific restrictions.
      • How to Use: Apply restrict tokens to filter search results according to defined boolean rules, improving search accuracy.
2364. Nearest Neighbors (ResearchScamNearestNeighbors)
      • Description: Represents all nearest neighbors for a given data point in a search query.
      • SEO Purpose: Identifies closely related items, improving the relevance of search results.
      • How to Use: Use nearest neighbors to find and display related content, enhancing the user’s search experience.
2365. Neighbor (ResearchScamNearestNeighborsNeighbor)
      • Description: Represents a single nearest neighbor, including distance and metadata.
      • SEO Purpose: Provides detailed information about related items in search results.
      • How to Use: Analyze neighbor data to enhance the relevance and context of search results.
2366. Neighbor Selection Override (ResearchScamNeighborSelectionOverride)
      • Description: Allows for the customization of neighbor selection in search results.
      • SEO Purpose: Provides flexibility in defining which neighbors are included in search results.
      • How to Use: Use selection overrides to refine neighbor selection criteria, ensuring more accurate search outputs.
2367. Numeric Restrict Namespace (ResearchScamNumericRestrictNamespace)
      • Description: Defines a namespace for numeric restricts, including operations and values.
      • SEO Purpose: Allows for numerical filtering of search results, improving precision.
      • How to Use: Implement numeric restrict namespaces to filter search results based on numerical criteria, enhancing relevance.
2368. Online Search Latency Stats (ResearchScamOnlineSearchLatencyStats)
      • Description: Records response times for search nodes.
      • SEO Purpose: Helps monitor and optimize the performance of search queries.
      • How to Use: Analyze latency stats to identify and address performance bottlenecks, improving search speed and efficiency.
2369. Query Metadata (ResearchScamQueryMetadata)
      • Description: Encodes query-specific information, such as tokenization and neighbor selection overrides.
      • SEO Purpose: Enhances the customization and optimization of search queries.
      • How to Use: Utilize query metadata to fine-tune search queries, ensuring more precise and relevant results.
2370. Query Response (ResearchScamQueryResponse)
      • Description: Contains the results of a search query, including nearest neighbors and optional debugging information.
      • SEO Purpose: Provides detailed search results and insights for optimization.
      • How to Use: Review query responses to evaluate and improve the effectiveness of search queries.
2371. Restrict Evaluation Info (ResearchScamRestrictEvaluationInfo)
      • Description: Holds detailed information for evaluating search restricts for a given query and dataset.
      • SEO Purpose: Assesses the effectiveness of restricts, aiding in their optimization.
      • How to Use: Analyze restrict evaluation info to refine and enhance search restricts, ensuring better search results.
2372. Restrict Evaluation Info Apply Token Stats (ResearchScamRestrictEvaluationInfoApplyTokenStats)
      • Description: Aggregates statistics for token namespace restricts.
      • SEO Purpose: Provides insights into the application and impact of token restricts.
      • How to Use: Use token stats to understand and optimize the use of token restricts in search queries.
2373. Restrict Evaluation Info Direct Lookup Stats (ResearchScamRestrictEvaluationInfoDirectLookupStats)
      • Description: Contains stats for direct lookup restricts, providing detailed evaluation information.
      • SEO Purpose: Assists in evaluating the effectiveness of direct lookup restricts.
      • How to Use: Analyze direct lookup stats to refine search restricts, ensuring more accurate and relevant results.
2374. Restrict Stats (ResearchScamRestrictStats)
      • Description: Holds the number of active and total datapoints for a given dataset.
      • SEO Purpose: Provides a snapshot of restrict application, aiding in the evaluation of search restricts.
      • How to Use: Use restrict stats to monitor the impact of search restricts on the dataset, optimizing search performance.
2375. Scoring Extension Metadata (ResearchScamScoringExtensionMetadata)
      • Description: Adjusts the configuration for scoring extensions in search algorithms.
      • SEO Purpose: Enhances the customization and accuracy of search result scoring.
      • How to Use: Configure scoring extensions to fine-tune search result rankings, improving relevance and precision.
2376. Token Namespace (ResearchScamTokenNamespace)
      • Description: Defines a namespace for tokens, including blacklist and whitelist tokens.
      • SEO Purpose: Organizes tokens for precise search filtering and restrictions.
      • How to Use: Implement token namespaces to categorize and manage tokens, enhancing the effectiveness of search filters.
2377. V3 Restrict (ResearchScamV3Restrict)
      • Description: Defines advanced restricts for search queries, supporting complex filtering across multiple namespaces and types.
      • SEO Purpose: Provides robust filtering options to enhance the precision of search results.
      • How to Use: Utilize V3 restricts to implement detailed and comprehensive search filters, ensuring highly relevant results.
2378. Science Search Catalog (ResearchScienceSearchCatalog)
      • Description: Information about the catalog from which a dataset originates.
      • SEO Purpose: Provides context and metadata about the source of datasets, aiding in data management and search relevance.
      • How to Use: Include catalog information to enhance the discoverability and context of datasets, improving search accuracy.
2379. Science Search Citation (ResearchScienceSearchCitation)
      • Description: References to citations in Google Scholar.
      • SEO Purpose: Enhances the credibility and context of scholarly content by linking to citations.
      • How to Use: Include citation references to support the authority and relevance of scholarly content, improving search rankings.
2380. Science Search Data Download (ResearchScienceSearchDataDownload)
      • Description: Provides downloadable dataset entries in various file formats.
      • SEO Purpose: Enhances user accessibility to datasets by offering multiple download options.
      • How to Use: Ensure datasets are available in multiple formats to accommodate user needs, improving accessibility and usability.
2381. Science Search Data Size (ResearchScienceSearchDataSize)
      • Description: Information about the size of a dataset, including numeric value and unit.
      • SEO Purpose: Provides users with an understanding of dataset size, aiding in data management decisions.
      • How to Use: Clearly specify data size to help users assess the scope and relevance of datasets, enhancing search utility.
2382. Science Search Date (ResearchScienceSearchDate)
      • Description: Represents dates associated with datasets, formatted in ISO 8601 or as unformatted strings.
      • SEO Purpose: Ensures accurate date representation for datasets, aiding in search relevance and filtering.
      • How to Use: Use standardized date formats to improve the accuracy and consistency of date-related search filters.
2383. Science Search Field of Study Info (ResearchScienceSearchFieldOfStudyInfo)
      • Description: Stores classification information for fields of study labels.
      • SEO Purpose: Enhances the categorization and discoverability of scholarly content by field of study.
      • How to Use: Properly classify content by field of study to improve its visibility and relevance in specialized searches.
2384. Science Search License (ResearchScienceSearchLicense)
      • Description: Information about the distribution license for datasets.
      • SEO Purpose: Provides users with licensing details, ensuring proper use and compliance.
      • How to Use: Clearly specify licensing information to guide users on the permissible use of datasets, enhancing transparency and trust.
2385. Science Search Location (ResearchScienceSearchLocation)
      • Description: Describes spatial information about dataset values.
      • SEO Purpose: Enhances the geographical context of datasets, improving location-based searches.
      • How to Use: Include accurate location information to support location-based search filters, improving relevance for geographically specific queries.
2386. Science Search Navboost Query Info (ResearchScienceSearchNavboostQueryInfo)
      • Description: Represents navigation boost queries for the dataset source URL.
      • SEO Purpose: Improves the ranking and relevance of datasets in search results by using navigation boosts.
      • How to Use: Implement navboost query info to enhance the visibility and ranking of datasets, ensuring they appear prominently in relevant searches.
2387. Science Search Organization (ResearchScienceSearchOrganization)
      • Description: Information about organizations, such as dataset sources or funders.
      • SEO Purpose: Provides context and credibility to datasets by linking them to reputable organizations.
      • How to Use: Include organization details to enhance the authority and relevance of datasets, improving their search visibility.
2388. Science Search Reconciled Metadata (ResearchScienceSearchReconciledMetadata)
      • Description: Stores inferred and reconciled metadata for Science Search.
      • SEO Purpose: Ensures comprehensive and accurate metadata, enhancing the discoverability and relevance of datasets.
      • How to Use: Maintain detailed reconciled metadata to support accurate search results and improved dataset visibility.
2389. Science Search Replica (ResearchScienceSearchReplica)
      • Description: Information about dataset replicas.
      • SEO Purpose: Provides users with access to dataset copies, ensuring data availability and redundancy.
      • How to Use: Clearly document replica information to enhance dataset accessibility and reliability, improving user experience.
2390. Science Search Scholarly Article (ResearchScienceSearchScholarlyArticle)
      • Description: Data and metadata for scholarly articles, including associated PDFs.
      • SEO Purpose: Enhances the visibility and credibility of scholarly articles by providing detailed metadata.
      • How to Use: Ensure comprehensive metadata for scholarly articles to improve their discoverability and relevance in academic searches.
2391. Science Search Source URL Docjoin Info (ResearchScienceSearchSourceUrlDocjoinInfo)
      • Description: Information extracted from docjoin for the dataset source URL.
      • SEO Purpose: Provides detailed context and metadata for datasets, improving search relevance.
      • How to Use: Include comprehensive docjoin information to support the accuracy and relevance of dataset search results.
2392. Science Search Source URL Docjoin Info Webref Entity Info (ResearchScienceSearchSourceUrlDocjoinInfoWebrefEntityInfo)
      • Description: The MID and description of a WebRef entity associated with the source URL.
      • SEO Purpose: Enhances the semantic understanding of datasets by linking them to WebRef entities.
      • How to Use: Include WebRef entity information to improve the semantic context and relevance of datasets in search results.
2393. Science Search Version Cluster Info (ResearchScienceSearchVersionClusterInfo)
      • Description: Information about clusters of dataset versions.
      • SEO Purpose: Provides users with a comprehensive view of dataset versions, aiding in data management.
      • How to Use: Clearly document version cluster information to support the organization and accessibility of dataset versions.
2394. Data Object (RichsnippetsDataObject)
      • Description: Represents a structured data object for rich snippets.
      • SEO Purpose: Enhances search result visibility and click-through rates by displaying rich snippets.
      • How to Use: Implement structured data objects to generate rich snippets, improving the attractiveness and relevance of search results.
2395. Data Object Attribute (RichsnippetsDataObjectAttribute)
      • Description: Additional attributes for rich snippet data objects.
      • SEO Purpose: Provides detailed information for rich snippets, enhancing their utility and relevance.
      • How to Use: Include comprehensive attributes in data objects to generate detailed and useful rich snippets, improving user engagement.
2396. Page Map (RichsnippetsPageMap)
      • Description: Contains data objects and templates for rich snippets.
      • SEO Purpose: Organizes structured data to generate rich snippets, improving search result presentation.
      • How to Use: Implement page maps to structure data effectively for rich snippets, enhancing search result visibility and user experience.
2397. Page Map Template Type (RichsnippetsPageMapTemplateType)
      • Description: Defines templates for rich snippet data objects.
      • SEO Purpose: Provides a consistent structure for rich snippets, improving their utility and relevance.
      • How to Use: Use template types to standardize rich snippets, ensuring consistency and quality in search result presentation.
2398. Audio Language (S3AudioLanguageS3AudioLanguage)
      • Description: Provides audio language information for watch pages.
      • SEO Purpose: Enhances the accessibility and relevance of audio content by specifying language information.
      • How to Use: Include accurate audio language metadata to improve the discoverability and user experience of audio content.
2399. Offensive Image Annotation (SafesearchImageOffensiveAnnotation)
      • Description: Scores for detecting offensive content in images.
      • SEO Purpose: Ensures safe search results by filtering out offensive content.
      • How to Use: Apply offensive image annotations to manage and filter content, ensuring compliance with safe search guidelines.
2400. Internal Image Signals (SafesearchInternalImageSignals)
      • Description: Stores internal signals for SafeSearch that are not exported to clients.
      • SEO Purpose: Enhances SafeSearch capabilities by utilizing internal image signals.
      • How to Use: Utilize internal signals to improve SafeSearch accuracy and reliability, ensuring safe and appropriate search results.
2401. Video Classifier Output (SafesearchVideoClassifierOutput)
      • Description: Flexible classification output for videos, with extensions for different verticals.
      • SEO Purpose: Enhances SafeSearch for video content by classifying based on multiple criteria.
      • How to Use: Implement video classifier outputs to filter and manage video content, ensuring safe and relevant search results.
2402. Video Content Signals (SafesearchVideoContentSignals)
      • Description: Classification scores for video content based on specific features.
      • SEO Purpose: Improves SafeSearch for videos by scoring content based on predefined features.
      • How to Use: Use video content signals to assess and manage video content, enhancing SafeSearch effectiveness.
2403. Multi-Label Classification Info (SafesearchVideoContentSignalsMultiLabelClassificationInfo)
      • Description: Information about multi-label classification results for video content.
      • SEO Purpose: Enhances SafeSearch by providing detailed classification information for videos.
      • How to Use: Apply multi-label classification info to improve the precision and relevance of video content filtering.
2404. Multi-Label Output (SafesearchVideoContentSignalsMultiLabelOutput)
      • Description: Output of the multi-label video classifier.
      • SEO Purpose: Provides comprehensive classification for video content, enhancing SafeSearch.
      • How to Use: Implement multi-label outputs to manage and filter video content effectively, ensuring safe search results.
2405. Science Citation (ScienceCitation)
      • Description: Metadata and references for scholarly citations, including patents and publications.
      • SEO Purpose: Enhances the credibility and context of scholarly content by linking to citations.
      • How to Use: Include detailed citation information to support the authority and relevance of scholarly content, improving search rankings.
2406. Access URL (ScienceCitationAccessURL)
      • Description: Provides user-defined URLs and their last access dates for citation management.
      • SEO Purpose: Ensures proper citation management and access tracking for scholarly content.
      • How to Use: Use this information to maintain up-to-date URLs for citations, improving the reliability and relevance of linked resources.
2407. Alternate Abstract (ScienceCitationAlternateAbstract)
      • Description: Contains alternate abstract fields that match those used for primary abstracts.
      • SEO Purpose: Provides additional abstract information for improved indexing and search relevance.
      • How to Use: Include alternate abstracts to enhance the searchability and context of scholarly articles.
2408. Alternate Title (ScienceCitationAlternateTitle)
      • Description: Stores alternate titles, including available language information.
      • SEO Purpose: Improves content discoverability by including various title versions.
      • How to Use: Use alternate titles to capture different language versions and enhance global search relevance.
2409. Citation Anchor (ScienceCitationAnchor)
      • Description: Holds content relevant to a citation, such as text before or after the citation.
      • SEO Purpose: Enhances citation context, making it easier to understand and search.
      • How to Use: Include citation anchors to provide context and improve the credibility and relevance of citations.
2410. Citation Author (ScienceCitationAuthor)
      • Description: Stores author names in the order specified in the paper.
      • SEO Purpose: Ensures accurate attribution and enhances author-based searches.
      • How to Use: Maintain the correct order of authors to improve the accuracy of author searches and citation credibility.
2411. Citation Category (ScienceCitationCategory)
      • Description: Classifies citations into categories based on a predefined ontology.
      • SEO Purpose: Enhances searchability and relevance by categorizing citations.
      • How to Use: Categorize citations accurately to improve search results and content organization.
2412. Download URL (ScienceCitationDownloadURL)
      • Description: Contains URLs for downloading citation-related documents.
      • SEO Purpose: Improves access to downloadable content, enhancing user experience.
      • How to Use: Provide download URLs to ensure easy access to citation documents, improving content usability.
2413. Funding Information (ScienceCitationFunding)
      • Description: Contains details about the funding agency, grant numbers, recipients, and source text for funding acknowledgements.
      • SEO Purpose: Adds credibility and context by linking research to its funding sources.
      • How to Use: Include comprehensive funding information to enhance the authority and relevance of research content.
2414. Funding Extraction Info (ScienceCitationFundingExtractionInfo)
      • Description: Holds details about the source of funding entries.
      • SEO Purpose: Improves the transparency and reliability of funding information.
      • How to Use: Document the source of funding entries to maintain accuracy and enhance trustworthiness.
2415. Reference Discussion (ScienceCitationReferenceDiscussion)
      • Description: Details the levels of discussion for references cited in the document.
      • SEO Purpose: Enhances the contextual understanding and relevance of citations.
      • How to Use: Include reference discussion details to provide deeper insights into citation contexts, improving search relevance.
2416. Subject Classification (ScienceCitationSubject)
      • Description: Classifies the subject of the citation.
      • SEO Purpose: Improves search relevance and discoverability by categorizing content.
      • How to Use: Use subject classifications to accurately categorize content, enhancing search results.
2417. Translated Author (ScienceCitationTranslatedAuthor)
      • Description: Stores translated author names, usually for non-English papers.
      • SEO Purpose: Enhances global searchability and relevance by including translated author names.
      • How to Use: Include translated author names to improve the discoverability of non-English papers.
2418. Union Catalog (ScienceCitationUnionCatalog)
      • Description: Groups book-level information for citations.
      • SEO Purpose: Enhances the organization and discoverability of book-related citations.
      • How to Use: Use union catalogs to provide comprehensive book information, improving search relevance and organization.
2419. Index Signal (ScienceIndexSignal)
      • Description: Contains various signals for indexing, including title fingerprints, selection scores, and author information.
      • SEO Purpose: Enhances indexing accuracy and search relevance.
      • How to Use: Utilize index signals to improve the precision and relevance of search results.
2420. Index Signal Author (ScienceIndexSignalAuthor)
      • Description: Stores the last names and other names of authors for indexing purposes.
      • SEO Purpose: Ensures accurate author attribution and enhances author-based searches.
      • How to Use: Maintain accurate author information to improve author searches and citation credibility.
2421. Ocean View (ScienceOceanView)
      • Description: Describes the viewability of ocean content.
      • SEO Purpose: Enhances content accessibility and relevance based on viewability.
      • How to Use: Document viewability details to improve content accessibility and search relevance.
2422. Ocean View Country (ScienceOceanViewCountryView)
      • Description: Contains country-specific viewability information for ocean content.
      • SEO Purpose: Enhances regional content relevance and accessibility.
      • How to Use: Include country-specific viewability details to improve regional search relevance and user experience.
2423. Embedding (SdrEmbedding)
      • Description: Contains compressed embeddings and other values for ranking purposes.
      • SEO Purpose: Enhances search ranking accuracy using advanced embedding techniques.
      • How to Use: Use embeddings to improve the relevance and precision of search results.
2424. Page Anchors Doc Info (SdrPageAnchorsDocInfo)
      • Description: Contains information about page anchors, including articleness, qscore, and text richness.
      • SEO Purpose: Improves the relevance and ranking of search results based on page anchor details.
      • How to Use: Include page anchor information to enhance search result relevance and user engagement.
2425. Page Anchor (SdrPageAnchorsSitelink)
      • Description: Contains details about page anchors, such as embeddings, scores, and text.
      • SEO Purpose: Enhances the discoverability and relevance of specific page sections.
      • How to Use: Use page anchor details to improve the visibility and relevance of specific content sections in search results.
2426. Page Anchor Wrapper (SdrPageAnchorsSitelinkWrapper)
      • Description: Wraps additional information for generating embeddings.
      • SEO Purpose: Supports advanced embedding generation for improved search relevance.
      • How to Use: Utilize the wrapper to include additional data for embedding generation, enhancing search accuracy.
2427. Scroll To (SdrScrollTo)
      • Description: Provides data to construct scroll-to text fragments.
      • SEO Purpose: Enhances user navigation and search result usability.
      • How to Use: Implement scroll-to fragments to improve user navigation and search result engagement.
2428. Scroll To On Page Matches (SdrScrollToOnPageMatches)
      • Description: Contains match counts for scroll-to text fragments.
      • SEO Purpose: Improves the precision and relevance of scroll-to functionality.
      • How to Use: Use match count data to enhance scroll-to functionality, ensuring accurate and relevant user navigation.
2429. Rankable Sensitivity (SearchPolicyRankableSensitivity)
      • Description: Encapsulates sensitivity mode and metadata used for ranking.
      • SEO Purpose: Enhances ranking precision based on sensitivity settings.
      • How to Use: Implement rankable sensitivity settings to fine-tune search result rankings for improved relevance.
2430. Sensitivity Attentional Entity (SearchPolicyRankableSensitivityAttentionalEntity)
      • Description: Marks attentional entities for sensitivity in search ranking.
      • SEO Purpose: Improves search relevance by considering attentional entities.
      • How to Use: Use attentional entity sensitivity to enhance the precision and relevance of search results.
2431. Sensitivity Follow On (SearchPolicyRankableSensitivityFollowOn)
      • Description: Marks sensitivity based on follow-on context.
      • SEO Purpose: Enhances search relevance by considering follow-on interactions.
      • How to Use: Implement follow-on sensitivity to improve the contextual relevance of search results.
2432. Sensitivity Fulfillment (SearchPolicyRankableSensitivityFulfillment)
      • Description: Marks sensitivity from fulfillment.
      • SEO Purpose: Ensures search results are relevant based on fulfillment context.
      • How to Use: Use fulfillment sensitivity to enhance the accuracy and relevance of search results.
2433. Sensitivity Grounding Provider (SearchPolicyRankableSensitivityGroundingProvider)
      • Description: Marks sensitivity from a grounding provider.
      • SEO Purpose: Improves search relevance by considering grounding provider inputs.
      • How to Use: Include grounding provider sensitivity to enhance the precision and relevance of search results.
2434. Sensitivity Query Understanding (SearchPolicyRankableSensitivityQueryUnderstanding)
      • Description: Marks sensitivity based on query understanding.
      • SEO Purpose: Enhances search relevance by incorporating query understanding.
      • How to Use: Use query understanding sensitivity to improve the contextual relevance of search results.
2435. Sensitivity Synthetic Intent (SearchPolicyRankableSensitivitySyntheticIntent)
      • Description: Marks sensitivity from a synthetic intent.
      • SEO Purpose: Ensures search results are relevant based on synthetic intent.
      • How to Use: Implement synthetic intent sensitivity to enhance the accuracy and relevance of search results.
2436. Authenticated Users (SecurityCredentialsAllAuthenticatedUsersProto)
      • Description: Represents authenticated users for access control.
      • SEO Purpose: Improves security and accountability by recognizing authenticated users.
      • How to Use: Use authenticated user data to manage access control and enhance security.
2437. Cap Token Holder (SecurityCredentialsCapTokenHolderProto)
      • Description: Represents a principal with a specific secret string for access control.
      • SEO Purpose: Enhances security by managing access through capability tokens.
      • How to Use: Use cap token holders to enforce secure access control policies.
2438. Chat Principal (SecurityCredentialsChatProto)
      • Description: Represents users associated with a chat for access control.
      • SEO Purpose: Manages chat-related access control and permissions.
      • How to Use: Implement chat principal data to manage and secure chat-related access.
2439. Circle Principal (SecurityCredentialsCircleProto)
      • Description: Represents a Google+ Circle for access control.
      • SEO Purpose: Manages access control based on social circles.
      • How to Use: Use circle principal data to manage access control within social circles.
2440. Cloud Principal (SecurityCredentialsCloudPrincipalProto)
      • Description: Represents a cloud principal for access control.
      • SEO Purpose: Enhances cloud security by recognizing cloud principals.
      • How to Use: Implement cloud principal data to manage and secure cloud access.
2441. Contact Group (SecurityCredentialsContactGroupProto)
      • Description: Represents a group of contacts for access control.
      • SEO Purpose: Manages access control based on contact groups.
      • How to Use: Use contact group data to manage and secure access control within contact groups.
2442. Email Owner (SecurityCredentialsEmailOwnerProto)
      • Description: Represents a verified owner of an email address.
      • SEO Purpose: Ensures accurate identification and accountability of email owners.
      • How to Use: Implement email owner data to manage and secure email-based access control.
2443. Event Principal (SecurityCredentialsEventProto)
      • Description: Represents users associated with a Google+ Event for access control.
      • SEO Purpose: Manages event-related access control and permissions.
      • How to Use: Use event principal data to manage and secure event-related access.
2444. Gaia Group (SecurityCredentialsGaiaGroupProto)
      • Description: Represents a Gaia group for access control.
      • SEO Purpose: Manages access control based on Gaia groups.
      • How to Use: Use Gaia group data to manage and secure group-based access control.
2445. Gaia User (SecurityCredentialsGaiaUserProto)
      • Description: Represents a Gaia account for access control.
      • SEO Purpose: Ensures secure access control for Gaia accounts.
      • How to Use: Implement Gaia user data to manage and secure access control for Gaia accounts.
2446. Host Principal (SecurityCredentialsHostProto)
      • Description: Represents a single host for access control.
      • SEO Purpose: Manages access control based on host information.
      • How to Use: Use host principal data to manage and secure access control for hosts.
2447. LDAP Group (SecurityCredentialsLdapGroupProto)
      • Description: Represents an LDAP group for access control.
      • SEO Purpose: Manages access control based on LDAP groups.
      • How to Use: Use LDAP group data to manage and secure group-based access control.
2448. LDAP User (SecurityCredentialsLdapUserProto)
      • Description: Represents an LDAP user for access control.
      • SEO Purpose: Ensures secure access control for LDAP users.
      • How to Use: Implement LDAP user data to manage and secure access control for LDAP users.
2449. MDB Group (SecurityCredentialsMdbGroupProto)
      • Description: Represents an MDB group for access control.
      • SEO Purpose: Manages access control based on MDB groups.
      • How to Use: Use MDB group data to manage and secure group-based access control.
2450. MDB User (SecurityCredentialsMdbUserProto)
      • Description: Represents an MDB user for access control.
      • SEO Purpose: Ensures secure access control for MDB users.
      • How to Use: Implement MDB user data to manage and secure access control for MDB users.
2451. OAuth Consumer (SecurityCredentialsOAuthConsumerProto)
      • Description: Represents an OAuth consumer for access control.
      • SEO Purpose: Enhances security by managing OAuth consumer access.
      • How to Use: Use OAuth consumer data to manage and secure OAuth-based access control.
2452. Postini User (SecurityCredentialsPostiniUserProto)
      • Description: Represents a Postini user for access control.
      • SEO Purpose: Ensures secure access control for Postini users.
      • How to Use: Implement Postini user data to manage and secure access control for Postini users.
2453. Principal (SecurityCredentialsPrincipalProto)
      • Description: Represents a principal for access control, typically a user or group.
      • SEO Purpose: Manages access control based on principal data.
      • How to Use: Use principal data to manage and secure access control for users and groups.
2454. RBAC Role (SecurityCredentialsRbacRoleProto)
      • Description: Represents a role for Role-Based Access Control (RBAC).
      • SEO Purpose: Enhances security by managing role-based access.
      • How to Use: Implement RBAC role data to manage and secure role-based access control.
2455. RBAC Subject (SecurityCredentialsRbacSubjectProto)
      • Description: Represents a subject for Role-Based Access Control (RBAC).
      • SEO Purpose: Manages access control based on RBAC subjects.
      • How to Use: Use RBAC subject data to manage and secure subject-based access control.
2456. Resource Role (SecurityCredentialsResourceRoleProto)
      • Description: Represents a resource role for access control.
      • SEO Purpose: Manages access control based on resource roles.
      • How to Use: Use resource role data to manage and secure access control for specific resources.
2457. Signing Key Possessor (SecurityCredentialsSigningKeyPossessorProto)
      • Description: Represents a principal with a signing key for access control.
      • SEO Purpose: Enhances security by managing signing key-based access.
      • How to Use: Implement signing key possessor data to enforce secure access control policies.
2458. Simple Secret Holder (SecurityCredentialsSimpleSecretHolderProto)
      • Description: Represents a principal with a secret string for access control.
      • SEO Purpose: Enhances security by managing secret-based access.
      • How to Use: Use simple secret holder data to enforce secure access control policies.
2459. Simple Secret Label (SecurityCredentialsSimpleSecretLabelProto)
      • Description: Identifies a particular secret used for access control without revealing the actual secret. This ensures that secrets are unguessable and securely used for authorization.
      • SEO Purpose: Enhances security measures by managing secret-based access control, thereby protecting sensitive content from unauthorized access.
      • How to Use: Implement simple secret labels to manage secure access control for specific objects or resources within your application, ensuring that only authorized users can access them.
2460. Social Graph Node (SecurityCredentialsSocialGraphNodeProto)
      • Description: Represents a user pseudonym linked to accounts on Google and third-party services like YouTube or Twitter. This helps in managing identities across various platforms.
      • SEO Purpose: Improves identity management and user experience by integrating social account information.
      • How to Use: Use social graph nodes to manage user identities and interactions across multiple platforms, enhancing personalized content delivery and user engagement.
2461. Google+ Square (SecurityCredentialsSquareProto)
      • Description: Represents the set of members in a Google+ Square, used for access control. This helps in managing group interactions and permissions.
      • SEO Purpose: Manages access control and group interactions, enhancing user engagement and security.
      • How to Use: Implement Google+ Square data to manage group-based access control and interactions, improving community management and content delivery.
2462. YouTube User (SecurityCredentialsYoutubeUserProto)
      • Description: Represents a YouTube user, identified by their YouTube user ID. This helps in managing permissions and interactions specific to YouTube.
      • SEO Purpose: Enhances security and user management for YouTube-related content.
      • How to Use: Use YouTube user data to manage permissions and interactions for YouTube content, improving security and personalized content delivery.
2463. Zwieback Session (SecurityCredentialsZwiebackSessionProto)
      • Description: Represents a session based on Zwieback, used for authentication and tracking. This helps in managing user sessions securely.
      • SEO Purpose: Improves security and session management for authenticated users.
      • How to Use: Implement Zwieback sessions to securely manage user authentication and session tracking, enhancing security and user experience.
2464. Sentence Boundary Annotations (SentenceBoundaryAnnotations)
      • Description: Identifies sentence boundaries within text. This helps in processing and analyzing text for better understanding and segmentation.
      • SEO Purpose: Enhances text processing and content analysis for better search engine understanding.
      • How to Use: Use sentence boundary annotations to improve text segmentation and analysis, enhancing content readability and SEO performance.
2465. Sentiment (SentimentSentiment)
      • Description: Contains the sentiment and emotions exhibited by the user at the time of the query. This helps in understanding user intent and providing relevant responses.
      • SEO Purpose: Enhances user experience by tailoring responses based on user sentiment and emotions.
      • How to Use: Implement sentiment analysis to understand user emotions and provide personalized responses, improving engagement and satisfaction.
2466. Sentiment Behaviors (SentimentSentimentBehaviors)
      • Description: Represents the behavior signals expressed by the user, detected through sentiment analysis. This helps in determining appropriate response behaviors.
      • SEO Purpose: Improves response accuracy and relevance by considering user behaviors.
      • How to Use: Use behavior signals from sentiment analysis to tailor responses and interactions, enhancing user engagement and satisfaction.
2467. Sentiment Emotions (SentimentSentimentEmotions)
      • Description: Identifies basic emotions expressed by the user. This helps in understanding user feelings and tailoring responses accordingly.
      • SEO Purpose: Enhances user experience by providing emotionally intelligent responses.
      • How to Use: Implement emotion detection to understand user feelings and provide empathetic responses, improving engagement and satisfaction.
2468. Shingle Info Per Doc Data (ShingleInfoPerDocData)
      • Description: Represents shingle-related information extracted from a document. This helps in understanding content structure and relevance.
      • SEO Purpose: Enhances content analysis and relevance by using shingle information.
      • How to Use: Use shingle info to analyze content structure and improve search relevance, enhancing SEO performance.
2469. Shingle Source (ShingleSource)
      • Description: Represents the source of shingles used in content analysis. This helps in understanding content composition and relevance.
      • SEO Purpose: Improves content analysis by identifying the sources of shingles.
      • How to Use: Implement shingle sources to analyze content composition and improve search relevance, enhancing SEO performance.
2470. Shopping Inferred Image (ShoppingWebentityShoppingAnnotationInferredImage)
      • Description: Contains images inferred from context, used when no offers are available. This helps in providing visual content for products.
      • SEO Purpose: Enhances product visibility and engagement by providing contextual images.
      • How to Use: Use inferred images to display visual content for products, improving user engagement and product visibility.
2471. Offer Availability Info (ShoppingWebentityShoppingAnnotationOfferAvailabilityInfo)
      • Description: Provides information about the availability of a product offer. This helps in informing users about product stock status.
      • SEO Purpose: Improves user experience by providing accurate product availability information.
      • How to Use: Implement offer availability info to keep users informed about product stock status, enhancing trust and user experience.
2472. Product Image (ShoppingWebentityShoppingAnnotationProductImage)
      • Description: Contains images at the product level, used when no offers are available. This helps in providing visual content for products.
      • SEO Purpose: Enhances product visibility and engagement by providing high-quality images.
      • How to Use: Use product images to display visual content for products, improving user engagement and product visibility.
2473. Product Rating (ShoppingWebentityShoppingAnnotationProductRating)
      • Description: Provides information about product ratings, including aggregated ratings if available. This helps in informing users about product quality.
      • SEO Purpose: Enhances product credibility and user trust by providing rating information.
      • How to Use: Display product ratings to inform users about product quality, improving credibility and user engagement.
2474. Sitemap Target (SitemapDEPRECATED_Target)
      • Description: Contains deprecated fields related to sitemap targets, such as URLs and scores. This helps in managing and updating sitemap data.
      • SEO Purpose: Manages sitemap data to ensure accurate indexing and content discovery.
      • How to Use: Update and maintain sitemap target data to improve content indexing and search engine visibility.
2475. Smartphone Per Doc Data (SmartphonePerDocData)
      • Description: Stores information related to smartphones, similar to MobilePerDocData but for higher-end mobile devices.
      • SEO Purpose: Enhances mobile SEO by providing detailed smartphone-related content analysis.
      • How to Use: Use smartphone per doc data to optimize content for high-end mobile devices, improving mobile search performance.
2476. Web Landing Page Entry (SmearedWebLandingPageEntry)
      • Description: Contains information about web landing pages, used for legacy purposes. This helps in understanding landing page composition and performance.
      • SEO Purpose: Enhances landing page analysis and optimization.
      • How to Use: Use landing page entry data to analyze and optimize web landing pages, improving user engagement and search performance.
2477. Snapshot Box (SnapshotBox)
      • Description: Represents a simple 2D box with coordinates, width, and height. This helps in understanding the layout of web content.
      • SEO Purpose: Enhances content layout analysis and optimization.
      • How to Use: Use snapshot boxes to analyze and optimize content layout, improving user experience and search performance.
2478. Snapshot Image Node (SnapshotImageNode)
      • Description: Contains information about images in a snapshot, including bounding boxes and URLs. This helps in understanding image placement and relevance.
      • SEO Purpose: Enhances image analysis and optimization for search engines.
      • How to Use: Use snapshot image node data to analyze and optimize image placement, improving search relevance and user engagement.
2479. Snapshot Document (SnapshotSnapshotDocument)
      • Description: Represents a snapshot of a document, including images, text nodes, and metadata. This helps in capturing the content and layout of a webpage.
      • SEO Purpose: Enhances content capture and analysis for search engines.
      • How to Use: Use snapshot documents to capture and analyze web content, improving indexing and search performance.
2480. Snapshot Metadata (SnapshotSnapshotMetadata)
      • Description: Contains metadata about a snapshot, such as resource count, crawl timestamp, and content size. This helps in understanding the composition and quality of web content.
      • SEO Purpose: Enhances content quality analysis and optimization.
      • How to Use: Use snapshot metadata to analyze content quality and composition, improving user experience and search performance.
2481. Snapshot Text Node (SnapshotTextNode)
      • Description: Represents a text node in a snapshot, including text content, bounding boxes, and font sizes. This helps in understanding the textual composition of web content.
      • SEO Purpose: Enhances text analysis and optimization for search engines.
      • How to Use: Use snapshot text node data to analyze and optimize textual content, improving readability and search relevance.
2482. Snippet Extra Info (SnippetExtraInfo)
      • Description: Contains additional information about snippets, such as candidate info, user quotes, and scoring information. This helps in understanding and optimizing snippet generation.
      • SEO Purpose: Enhances snippet optimization for better search engine results.
      • How to Use: Use snippet extra info to optimize snippets for search engines, improving click-through rates and search visibility.
2483. Snippet Candidate Info (SnippetExtraInfoSnippetCandidateInfo)
      • Description: Provides detailed information about snippet candidates, including extended versions and scoring info. This helps in selecting the best snippet candidates.
      • SEO Purpose: Enhances snippet selection and optimization for search engines.
      • How to Use: Use snippet candidate info to select and optimize the best snippet candidates, improving search relevance and user engagement.
2484. Snippet Scoring Info (SnippetExtraInfoSnippetScoringInfo)
      • Description: Contains scoring information for snippets, used to determine the most relevant snippets. This helps in optimizing snippet selection.
      • SEO Purpose: Enhances snippet scoring and selection for better search engine results.
      • How to Use: Use snippet scoring info to optimize snippet selection based on relevance and scoring, improving search visibility and click-through rates.
2485. Snippets Brain Model Info (SnippetExtraInfoSnippetsBrainModelInfo)
      • Description: Provides information about the model used to generate snippet scores, including model name and input processor. This helps in understanding snippet scoring mechanisms.
      • SEO Purpose: Enhances understanding and optimization of snippet scoring models.
      • How to Use: Use snippets brain model info to understand and optimize snippet scoring models, improving search relevance and performance.
2486. Leading Text Annotation (SnippetsLeadingtextLeadingTextAnnotation)
      • Description: Represents leading text annotations, consisting of multiple text pieces. This helps in understanding the leading text of documents.
      • SEO Purpose: Enhances content analysis and optimization for leading text.
      • How to Use: Use leading text annotations to analyze and optimize leading text, improving content readability and search relevance.
2487. Leading Text Info (SnippetsLeadingtextLeadingTextInfo)
      • Description: Contains detailed information about leading text, including start positions and text content. This helps in understanding and optimizing the leading text of documents.
      • SEO Purpose: Enhances content analysis and optimization for leading text.
      • How to Use: Use leading text info to analyze and optimize the leading text of documents, improving content readability and search relevance.
2488. Social Content Attachment (SocialCommonAttachmentAttachment)
      • Description: Represents a linked entity associated with social content, such as an attachment or embed. This helps in managing and displaying linked content in social posts.
      • SEO Purpose: Enhances social content management and display.
      • How to Use: Use social content attachments to manage and display linked entities in social posts, improving user engagement and content richness.
2489. Social Formatting (SocialCommonFormatting)
      • Description: Contains formatting information for social content segments, such as bold or italics. This helps in rendering social content with appropriate formatting.
      • SEO Purpose: Enhances the display and readability of social content.
      • How to Use: Use social formatting to apply appropriate formatting to social content, improving display and user experience.
2490. Hashtag Data (SocialCommonHashtagData)
      • Description: Contains metadata for hashtags, including display and search text. This helps in managing and indexing hashtags for social content.
      • SEO Purpose: Enhances hashtag management and searchability.
      • How to Use: Use hashtag data to manage and index hashtags for social content, improving searchability and user engagement.
2491. Link Data (SocialCommonLinkData)
      • Description: Contains metadata for links in social content, including anchor text. This helps in managing and displaying links in social posts.
      • SEO Purpose: Enhances link management and display in social content.
      • How to Use: Use link data to manage and display links in social posts, improving user engagement and content richness.
2492. Search Link Data (SocialCommonSearchLinkData)
      • Description: Contains metadata for search links in social content. This helps in managing and displaying search links in social posts.
      • SEO Purpose: Enhances search link management and display in social content.
      • How to Use: Use search link data to manage and display search links in social posts, improving user engagement and search relevance.
2493. Social Segment (SocialCommonSegment)
      • Description: Represents a segment of social content, including text, formatting, and metadata. This helps in managing and displaying structured social content.
      • SEO Purpose: Enhances the management and display of structured social content.
      • How to Use: Use social segments to manage and display structured social content, improving user engagement and content richness.
2494. Social Segments (SocialCommonSegments)
      • Description: Represents structured social content, such as posts or chat messages, which consist of various types of content like text, hashtags, and links. Each segment is treated as a distinct unit with specific qualifiers.
      • SEO Purpose: Enhances content structuring and indexing by breaking down complex social content into manageable segments, improving search relevance.
      • How to Use: Use segments to structure social content effectively, ensuring each type of content (text, links, hashtags) is appropriately tagged and indexed for better search visibility.
2495. User Mention Data (SocialCommonUserMentionData)
      • Description: Contains metadata for user mentions in social content, including user ID, email, or other identifiers. This helps in identifying and linking mentioned users within the content.
      • SEO Purpose: Improves the recognition and indexing of user mentions in social content, enhancing searchability and user engagement.
      • How to Use: Ensure user mention data is included in social content to improve the accuracy of user identification and linking, enhancing the content’s searchability and relevance.
2496. External Entity Key (SocialDiscoveryExternalEntityKey)
      • Description: Represents an obfuscated entity key that can be used externally, typically for user identification across platforms.
      • SEO Purpose: Enhances user privacy and security while enabling cross-platform user identification and engagement.
      • How to Use: Implement external entity keys to securely manage user identification across different platforms, improving privacy and seamless user experiences.
2497. App Contact Data (SocialGraphApiAppContactData)
      • Description: Contains contact data supported by third-party apps, including app-specific endpoints and identifiers for actions like messaging or calling.
      • SEO Purpose: Enhances integration with third-party apps, improving user interaction and content relevance.
      • How to Use: Use app contact data to enable seamless interactions with third-party apps, enhancing user experience and engagement through integrated functionalities.
2498. Android Device Info (SocialGraphApiProtoAndroidDeviceInfo)
      • Description: Provides information about the device, such as make and model, which is useful for understanding user device context.
      • SEO Purpose: Improves content personalization and targeting based on the user’s device.
      • How to Use: Use device info to tailor content and interactions based on the user’s device, improving personalization and engagement.
2499. Birthday Decoration (SocialGraphApiProtoBirthdayDecoration)
      • Description: Manages visibility settings for birthday decorations within the user’s profile.
      • SEO Purpose: Enhances user experience by allowing personalized and controlled display of birthday information.
      • How to Use: Implement birthday decoration settings to provide personalized and celebratory content, improving user engagement and satisfaction.
2500. Contact Create Context (SocialGraphApiProtoContactCreateContext)
      • Description: Encapsulates data related to the creation of a contact, including the source and timestamp of the creation action.
      • SEO Purpose: Enhances contact management and tracking, improving the accuracy of contact-related interactions.
      • How to Use: Use contact create context data to track and manage contact creation events, improving the organization and reliability of contact information.
2501. Contact Deletion Context (SocialGraphApiProtoContactDeletionContext)
      • Description: Encapsulates data related to the deletion of a contact, including specific details needed for deletion.
      • SEO Purpose: Improves contact management by providing detailed context for deletion actions, ensuring accurate and secure contact removal.
      • How to Use: Implement contact deletion context data to manage and track contact deletion events, enhancing data accuracy and security.
2502. Contact Edit Context (SocialGraphApiProtoContactEditContext)
      • Description: Encapsulates data related to the editing of a contact, including the source and timestamp of the edit action.
      • SEO Purpose: Enhances contact management by providing detailed context for contact edits, improving the accuracy of contact information.
      • How to Use: Use contact edit context data to track and manage contact edits, ensuring up-to-date and accurate contact information.
2503. Contact Mutation Context (SocialGraphApiProtoContactMutationContext)
      • Description: Provides generic mutation data shared between create, update, and delete actions for contacts, including source of change and metadata.
      • SEO Purpose: Enhances contact management by providing a unified context for all contact mutations, improving data consistency.
      • How to Use: Use contact mutation context data to manage and track all types of contact mutations, ensuring data consistency and accuracy.
2504. Contact Prompt Settings (SocialGraphApiProtoContactPromptSettings)
      • Description: Manages settings for contact prompts, including reminders and active states for contacts.
      • SEO Purpose: Improves user engagement by managing reminders and prompts for contact interactions.
      • How to Use: Implement contact prompt settings to provide timely reminders and prompts, enhancing user engagement and interaction.
2505. Contact State (SocialGraphApiProtoContactState)
      • Description: Provides metadata related to the state of a contact, such as whether it is active or trashed.
      • SEO Purpose: Enhances contact management by tracking the state of contacts, improving data organization and retrieval.
      • How to Use: Use contact state data to manage and track the status of contacts, ensuring accurate data organization and retrieval.
2506. Daily Recurrence (SocialGraphApiProtoDailyRecurrence)
      • Description: Defines a pattern for daily or every N day recurrence of events or notifications.
      • SEO Purpose: Enhances event and notification management by providing flexible recurrence patterns.
      • How to Use: Implement daily recurrence patterns to manage and schedule regular events or notifications, improving user engagement and organization.
2507. Decoration Overlay (SocialGraphApiProtoDecorationOverlay)
      • Description: Manages settings for displaying decoration overlays, such as visual elements on user profiles.
      • SEO Purpose: Enhances user experience by providing customizable visual decorations for profiles.
      • How to Use: Use decoration overlay settings to personalize and enhance visual elements on user profiles, improving user engagement and satisfaction.
2508. Delegated Group ID (SocialGraphApiProtoDelegatedGroupId)
      • Description: Represents a group ID for groups that are owned by another user but accessible to the current user.
      • SEO Purpose: Enhances group management by allowing access to delegated groups, improving collaboration and interaction.
      • How to Use: Implement delegated group IDs to manage and provide access to groups owned by other users, enhancing collaboration and user engagement.
2509. Display Name Source (SocialGraphApiProtoDisplayNameSource)
      • Description: Indicates the source of a user’s display name, providing context for name selection.
      • SEO Purpose: Improves user identification and personalization by tracking the source of display names.
      • How to Use: Use display name source data to manage and personalize user display names, enhancing identification and user experience.
2510. Host App Info (SocialGraphApiProtoHostAppInfo)
      • Description: Provides information about the host application, such as the app name, for contextual understanding.
      • SEO Purpose: Enhances integration and user experience by providing context about the host application.
      • How to Use: Use host app info to provide contextual information about the application, improving integration and user experience.
2511. Image Reference (SocialGraphApiProtoImageReference)
      • Description: Represents a reference to a photo stored in Photos Backend or SGI storage, used for managing and displaying images.
      • SEO Purpose: Enhances image management and display by providing structured references to images.
      • How to Use: Implement image references to manage and display photos within applications, improving visual content and user engagement.
2512. Limited Profile Name Settings (SocialGraphApiProtoLimitedProfileNameSettings)
      • Description: Manages settings for limited profile names, including options for name shortening and verbatim full names.
      • SEO Purpose: Enhances user privacy and personalization by managing limited profile name settings.
      • How to Use: Use limited profile name settings to provide users with options for managing their display names, enhancing privacy and personalization.
2513. Limited Profile Picture Settings (SocialGraphApiProtoLimitedProfilePictureSettings)
      • Description: Manages settings for limited profile pictures, allowing users to control how their profile pictures are displayed.
      • SEO Purpose: Enhances user privacy and personalization by managing profile picture settings.
      • How to Use: Implement limited profile picture settings to provide users with control over their profile pictures, improving privacy and personalization.
2514. Limited Profile Settings (SocialGraphApiProtoLimitedProfileSettings)
      • Description: Manages overall settings for limited profiles, including name and picture settings.
      • SEO Purpose: Enhances user privacy and personalization by providing comprehensive management of limited profiles.
      • How to Use: Use limited profile settings to manage user privacy and personalization options, improving user control and satisfaction.
2515. Monthly Day Recurrence (SocialGraphApiProtoMonthlyDayRecurrence)
      • Description: Defines a pattern for monthly recurrence based on specific days of the month.
      • SEO Purpose: Enhances event scheduling and management by providing flexible monthly recurrence patterns.
      • How to Use: Implement monthly day recurrence patterns to manage and schedule monthly events, improving organization and user engagement.
2516. Monthly Recurrence (SocialGraphApiProtoMonthlyRecurrence)
      • Description: Defines a pattern for monthly recurrence, supporting both specific days and weekdays.
      • SEO Purpose: Enhances event scheduling and management by providing versatile monthly recurrence options.
      • How to Use: Use monthly recurrence patterns to manage and schedule regular monthly events, improving organization and user engagement.
2517. Monthly Weekday Recurrence (SocialGraphApiProtoMonthlyWeekdayRecurrence)
      • Description: Defines a pattern for monthly recurrence based on specific weekdays, such as the third Wednesday of the month.
      • SEO Purpose: Enhances event scheduling and management by providing flexible weekday-based monthly recurrence options.
      • How to Use: Implement monthly weekday recurrence patterns to manage and schedule events based on specific weekdays, improving organization and user engagement.
2518. Name Pronunciation Audio Metadata (SocialGraphApiProtoNamePronunciationAudioMetadata)
      • Description: Provides metadata for audio recordings of name pronunciations, helping in accurate pronunciation representation.
      • SEO Purpose: Enhances user experience by providing accurate name pronunciation metadata.
      • How to Use: Use name pronunciation audio metadata to manage and display accurate name pronunciations, improving user interaction and satisfaction.
2519. Notification Trigger (SocialGraphApiProtoNotificationTrigger)
      • Description: Defines triggers for notifications, used for scheduling and managing event notifications.
      • SEO Purpose: Enhances user engagement by providing timely notifications based on defined triggers.
      • How to Use: Implement notification triggers to schedule and manage notifications, improving user engagement and interaction.
2520. Partial Name Options (SocialGraphApiProtoPartialNameOptions)
      • Description: Provides options for name shortening and formatting, allowing users to control how their names are displayed.
      • SEO Purpose: Enhances user personalization and privacy by providing flexible name formatting options.
      • How to Use: Use partial name options to manage and display user names according to their preferences, improving personalization and user satisfaction.
2521. Partial Name Options Name Part Spec (SocialGraphApiProtoPartialNameOptionsNamePartSpec)
      • Description: Specifies how each part of a name should be handled, including given and family names.
      • SEO Purpose: Enhances name management by providing detailed control over name parts.
      • How to Use: Implement name part specifications to manage and display user names accurately, improving personalization and user experience.
2522. Partial Name Options Parsed Display Name Spec (SocialGraphApiProtoPartialNameOptionsParsedDisplayNameSpec)
      • Description: Uses sophisticated logic to parse and format user names, considering various name structures and conventions.
      • SEO Purpose: Enhances name parsing and formatting for accurate display and indexing.
      • How to Use: Use parsed display name specifications to manage and display user names accurately, improving personalization and user experience.
2523. Partial Name Options Two Part Name Spec (SocialGraphApiProtoPartialNameOptionsTwoPartNameSpec)
      • Description: Provides specifications for managing two-part names, such as given and family names.
      • SEO Purpose: Enhances name management by providing detailed control over two-part names.
      • How to Use: Implement two-part name specifications to manage and display user names accurately, improving personalization and user experience.
2524. Photo Overlay (SocialGraphApiProtoPhotoOverlay)
      • Description: Manages settings for photo overlays, controlling how visual elements are displayed on photos.
      • SEO Purpose: Enhances visual content by providing customizable photo overlays.
      • How to Use: Use photo overlay settings to personalize and enhance visual elements on photos, improving user engagement and satisfaction.
2525. Prompt (SocialGraphApiProtoPrompt)
      • Description: Represents a prompt used in various contexts, such as reminders or notifications.
      • SEO Purpose: Enhances user engagement by providing timely and relevant prompts.
      • How to Use: Implement prompts to schedule and manage reminders and notifications, improving user engagement and interaction.
2526. Prompt Content (SocialGraphApiProtoPromptContent)
      • Description: Provides content for prompts, used to display messages or reminders to users.
      • SEO Purpose: Enhances user engagement by providing clear and relevant prompt content.
      • How to Use: Use prompt content to create and display effective reminders and notifications, improving user engagement and interaction.
2527. Pronoun Data (SocialGraphApiProtoPronounData)
      • Description: Represents a user’s preferred pronouns, including type and value.
      • SEO Purpose: Enhances personalization and inclusivity by providing accurate pronoun data.
      • How to Use: Use pronoun data to manage and display user pronouns, improving personalization and inclusivity.
2528. Pronoun Entry (SocialGraphApiProtoPronounEntry)
      • Description: Provides detailed information about a user’s pronoun entry, including language and type.
      • SEO Purpose: Enhances personalization and inclusivity by providing detailed pronoun information.
      • How to Use: Implement pronoun entry data to manage and display user pronouns accurately, improving personalization and inclusivity.
2529. Pronunciation (SocialGraphApiProtoPronunciation)
      • Description: This attribute stores the phonetic representation of a word or text, which helps in accurately understanding and processing user queries that involve specific names or terms.
      • SEO Purpose: Proper pronunciation data enhances voice search accuracy, ensuring that user queries are matched with the correct content, improving user experience and search rankings.
      • How to Use: For websites with content that includes names, brands, or terms that might be pronounced in various ways, provide phonetic information to improve voice search recognition.
2530. Recurrence (SocialGraphApiProtoRecurrence)
      • Description: This attribute defines the recurrence pattern of events or actions, such as weekly meetings, yearly anniversaries, or specific dates for one-time events.
      • SEO Purpose: Accurate recurrence information ensures that time-sensitive content, such as event announcements, is correctly indexed and displayed in search results, improving visibility and relevance.
      • How to Use: Use structured data to mark up recurring events on your website. Specify the recurrence rules clearly to help search engines understand and display the events correctly in search results.
2531. Relative Position (SocialGraphApiProtoRelativePosition)
      • Description: This attribute determines the position of an element relative to a user’s avatar, indicating whether it is above, below, to the left, or to the right.
      • SEO Purpose: Understanding the relative positioning can enhance the layout and navigation of web content, contributing to a better user experience.
      • How to Use: Optimize the layout of interactive elements on your site based on user interactions and preferences, ensuring important content is easily accessible.
2532. Relative Scale (SocialGraphApiProtoRelativeScale)
      • Description: This attribute indicates the scale of an element relative to a user’s avatar, ranging from exclusive 0 to inclusive 1.
      • SEO Purpose: Proper scaling ensures that visual elements are appropriately sized for user interactions, enhancing usability and user engagement.
      • How to Use: Design scalable elements on your website that adapt to different screen sizes and user preferences, ensuring a consistent user experience across devices.
2533. Search Profile Data (SocialGraphApiProtoSearchProfileData)
      • Description: Contains comprehensive data included in every search profile, which can encompass user attributes, preferences, and activity history.
      • SEO Purpose: Detailed search profile data helps personalize search results, making them more relevant to individual users, which can improve click-through rates and user satisfaction.
      • How to Use: Ensure your website content is optimized for personalization by using metadata and structured data to make it easier for search engines to match content with user profiles.
2534. Educational Background (SocialGraphApiProtoSearchProfileEducation)
      • Description: This attribute encapsulates information about a user’s educational history, including institutions attended and degrees obtained.
      • SEO Purpose: Highlighting educational background in profiles can improve search relevance for users looking for experts or professionals with specific qualifications.
      • How to Use: Include detailed and accurate educational information in professional profiles on your website. Use schema markup to enhance visibility in search results.
2535. Location Information (SocialGraphApiProtoSearchProfileLocationInfo)
      • Description: Wraps information about a user’s geographic location, including latitude, longitude, and radius of the area.
      • SEO Purpose: Accurate location data enhances local search results, ensuring users find geographically relevant content.
      • How to Use: Implement location-based metadata and structured data for local SEO. Ensure your business location information is consistent across all platforms and directories.
2536. Social Links (SocialGraphApiProtoSearchProfileSocialLink)
      • Description: Contains information about a user’s social media profiles and links to their social presence.
      • SEO Purpose: Social links help search engines verify the authenticity and social reach of a profile, contributing to credibility and authority.
      • How to Use: Include social media links in user profiles and use structured data to help search engines associate social accounts with website content.
2537. Profile State (SocialGraphApiProtoSearchProfileState)
      • Description: Describes the current state of a user’s profile, including timestamps for when the state was changed and when it should be displayed.
      • SEO Purpose: Managing profile state data helps keep user profiles up-to-date and relevant, improving the accuracy and reliability of search results.
      • How to Use: Regularly update user profile states and use timestamps to ensure changes are reflected accurately in search results.
2538. Workplace Information (SocialGraphApiProtoSearchProfileWorkplace)
      • Description: Contains details about a user’s current and past workplaces, including positions held and duration of employment.
      • SEO Purpose: Highlighting workplace information can improve search relevance for users seeking professionals with specific work experience.
      • How to Use: Ensure workplace information is detailed and current in professional profiles. Use schema markup to enhance visibility in search results.
2539. Single Recurrence (SocialGraphApiProtoSingleRecurrence)
      • Description: Defines a one-time occurrence of an event, such as a specific date for a graduation or a reminder to connect with someone.
      • SEO Purpose: Accurate one-time event information helps ensure such events are correctly indexed and displayed in search results, improving visibility and relevance.
      • How to Use: Use structured data to mark up single events on your website, specifying the date and details to help search engines display them accurately.
2540. Third-Party Information (SocialGraphWireProtoPeopleapiExtensionThirdPartyInfo)
      • Description: Contains data about third-party applications interacting with a user’s profile, including client names and project numbers.
      • SEO Purpose: Understanding third-party interactions can help manage data privacy and improve the transparency of app integrations.
      • How to Use: Monitor third-party access to user data and ensure compliance with privacy policies. Display relevant third-party information clearly to users.
2541. Usage Information (SocialGraphApiProtoUsageInfo)
      • Description: Provides data on how a user’s profile or content is being used, including device interactions and activity patterns.
      • SEO Purpose: Usage data helps optimize content for user engagement and interaction, improving overall user experience and search performance.
      • How to Use: Analyze usage patterns to tailor content and improve engagement. Use this data to refine SEO strategies based on user behavior insights.
2542. Weekly Recurrence (SocialGraphApiProtoWeeklyRecurrence)
      • Description: Defines patterns for weekly recurring events, specifying the days of the week and intervals between occurrences.
      • SEO Purpose: Accurate weekly event information ensures recurring events are correctly indexed and displayed, enhancing visibility in search results.
      • How to Use: Use structured data to mark up weekly events on your website, specifying recurrence rules to help search engines display them accurately.
2543. Yearly Recurrence (SocialGraphApiProtoYearlyRecurrence)
      • Description: Specifies patterns for yearly recurring events, including monthly patterns and specific days within those months.
      • SEO Purpose: Correct yearly event information helps ensure such events are accurately indexed and displayed, improving relevance and visibility in search results.
      • How to Use: Mark up yearly events with structured data, clearly defining recurrence rules to aid search engines in displaying the events correctly.
2544. Affinity Metadata (SocialGraphWireProtoPeopleapiAffinityMetadata)
      • Description: Contains additional ranking information based on affinity data, helping filter and rank suggestions for users.
      • SEO Purpose: Affinity metadata helps personalize search results and suggestions, making them more relevant to individual user preferences and interactions.
      • How to Use: Use affinity data to customize content recommendations and improve user engagement by providing personalized search results.
2545. Client Interaction Information (SocialGraphWireProtoPeopleapiAffinityMetadataClientInteractionInfo)
      • Description: Indicates whether a suggestion is based on direct client interactions, such as shared photos or messages.
      • SEO Purpose: Highlighting direct interactions improves the accuracy and relevance of personalized content and suggestions in search results.
      • How to Use: Track and utilize direct user interactions to refine content recommendations and personalize user experiences.
2546. Device Data Information (SocialGraphWireProtoPeopleapiAffinityMetadataCloudDeviceDataInfo)
      • Description: Provides partial affinity scores and indicates whether device data about a candidate was available in the cloud.
      • SEO Purpose: Using device data helps improve the accuracy of affinity-based recommendations and search results, enhancing user satisfaction.
      • How to Use: Integrate device data to refine content suggestions and improve personalization, ensuring a better match with user preferences.
2547. Legal Request Metadata (StorageGraphBfgLegalRequestMetadata)
      • Description: Contains metadata about legal requests, including associated bug IDs for tracking purposes.
      • SEO Purpose: Managing legal request data ensures compliance with legal requirements and helps maintain transparency and trust with users.
      • How to Use: Track and respond to legal requests efficiently, maintaining detailed records to ensure compliance and transparency.
2548. Livegraph Provenance Metadata (StorageGraphBfgLivegraphProvenanceMetadata)
      • Description: This metadata provides additional context on source assertions, influencing how the Livegraph system processes data. It is designed for internal use within Google’s knowledge graph infrastructure.
      • SEO Purpose: Understanding data provenance ensures that the information presented is accurate and trustworthy, which can enhance the credibility of the content and improve its ranking in search results.
      • How to Use: Ensure that your data sources are credible and accurately cited. Use consistent metadata to improve the reliability and transparency of your content.
2549. LLM Policy Metadata (StorageGraphBfgLlmPolicyMetadata)
      • Description: Contains metadata fields related to the usage restrictions of Large Language Models (LLM). This ensures compliance with data usage policies.
      • SEO Purpose: Adhering to data usage policies maintains the integrity of your content, helping to avoid penalties and ensuring compliance with legal standards, which can positively impact search rankings.
      • How to Use: Familiarize yourself with LLM data usage restrictions and incorporate them into your data handling practices to ensure compliance.
2550. LMS Policy Metadata (StorageGraphBfgLmsPolicyMetadata)
      • Description: Includes metadata fields specific to Learning Management Systems (LMS) and their data usage restrictions.
      • SEO Purpose: Ensuring compliance with LMS data policies helps maintain the credibility and legality of your educational content, which can improve search visibility and user trust.
      • How to Use: Implement LMS policy guidelines in your content management practices, and ensure your content adheres to these restrictions.
2551. Data Governance Policy Metadata (StorageGraphBfgPolicyMetadata)
      • Description: This metadata pertains to data governance policies, including details about data availability and expiration.
      • SEO Purpose: Proper data governance ensures that your content is managed according to best practices, enhancing its reliability and trustworthiness, which can positively affect search rankings.
      • How to Use: Follow data governance policies to manage your content lifecycle effectively, ensuring data is accurate and up-to-date.
2552. Public Information Metadata (StorageGraphBfgPublicInformationMetadata)
      • Description: Contains publicly visible URLs and the date when they were last verified, ensuring the accuracy and currency of public information.
      • SEO Purpose: Verifiable and up-to-date public information enhances the credibility of your content, improving its search engine ranking.
      • How to Use: Regularly verify and update publicly visible URLs to maintain their accuracy and relevance.
2553. Real World Journey Policy Metadata (StorageGraphBfgRwjPolicyMetadata)
      • Description: This metadata field pertains to the Real World Journey data governance policies, ensuring data handling aligns with specific regulations.
      • SEO Purpose: Compliance with Real World Journey policies enhances the trustworthiness of your content, positively influencing search engine rankings.
      • How to Use: Ensure your data practices align with Real World Journey policies to maintain compliance and improve data credibility.
2554. SPII Certification (StorageGraphBfgSpiiCertification)
      • Description: Indicates whether sensitive personal information (SPII) meets certification requirements, ensuring data is handled appropriately.
      • SEO Purpose: Proper handling and certification of sensitive information enhance the security and trustworthiness of your site, which can improve search rankings.
      • How to Use: Certify that all sensitive personal information on your site meets specific requirements and policies to ensure compliance and trust.
2555. Triple Provenance (StorageGraphBfgTripleProvenance)
      • Description: Contains information about the source of data triples, detailing the creator and the attribution chain.
      • SEO Purpose: Accurate provenance information ensures the credibility and traceability of data, which can positively affect your site’s search rankings.
      • How to Use: Include detailed provenance information for all data sources to improve transparency and credibility.
2556. UMP Policy Metadata (StorageGraphBfgUmpPolicyMetadata)
      • Description: Metadata fields for Universal Music Publishing (UMP) policies, ensuring data access aligns with allowed regions and timeframes.
      • SEO Purpose: Compliance with UMP policies helps ensure that content is legally distributed, which can enhance your site’s reputation and search ranking.
      • How to Use: Adhere to UMP policy guidelines to manage content distribution effectively and legally.
2557. Podcast Recommendations Features (SuperrootPodcastsRecommendationsPodcastRecsFeatures)
      • Description: Contains features related to podcast recommendations, including user language preferences and scores.
      • SEO Purpose: Tailoring podcast recommendations based on user preferences can enhance user engagement and improve your site’s relevance in search results.
      • How to Use: Utilize user language and preference data to provide personalized podcast recommendations, improving user satisfaction and engagement.
2558. Telephone Number Information (TelephoneNumber)
      • Description: This attribute includes comprehensive details about telephone numbers, such as area codes, country codes, extensions, and formatted numbers.
      • SEO Purpose: Accurate and properly formatted contact information improves user trust and local SEO performance.
      • How to Use: Ensure all telephone numbers on your site are correctly formatted and include necessary details to enhance local search visibility and user trust.
2559. Airline Contact Information (TravelFlightsAirlineConfigContactInfo)
      • Description: Contains formatted phone numbers and types of contact information for airlines, grouped by country or language.
      • SEO Purpose: Providing accurate contact information enhances the user experience and trust, improving search engine rankings for travel-related queries.
      • How to Use: Maintain up-to-date and correctly formatted contact information for airlines to ensure it is easily accessible and trustworthy.
2560. Green Fares Information (TravelFlightsAirlineConfigGreenFaresInfo)
      • Description: Details about green fare programs, including bonus miles and contribution framing, to promote eco-friendly travel options.
      • SEO Purpose: Highlighting green travel options can attract environmentally conscious users and improve the relevance of your travel content in search results.
      • How to Use: Promote green fare programs and provide clear information about bonus miles and contributions to attract eco-conscious travelers.
2561. Name Catalog Entry (TravelFlightsNameCatalogEntry)
      • Description: Contains information about catalog entries for names, including language and text.
      • SEO Purpose: Accurate name catalog entries ensure proper indexing and retrieval of names in search queries, enhancing the relevance and accuracy of search results.
      • How to Use: Maintain an accurate and comprehensive name catalog to improve the retrieval and relevance of names in search queries.
2562. Fetch Body Data (TrawlerFetchBodyData)
      • Description: Includes details about fetched content, such as compression type, content data, and uncompressed size.
      • SEO Purpose: Efficient data fetching and handling ensure fast load times and a better user experience, positively impacting search rankings.
      • How to Use: Optimize content fetching processes to ensure efficient data handling and fast load times, improving user experience and search performance.
2563. Fetch Reply Data (TrawlerFetchReplyData)
      • Description: Metadata for fetch replies, including protocol responses, delivery reports, and fetch statistics.
      • SEO Purpose: Detailed fetch reply data helps optimize content delivery and improve the efficiency of web crawlers, enhancing search engine indexing and ranking.
      • How to Use: Analyze fetch reply data to optimize content delivery and improve the performance of web crawlers, ensuring efficient indexing and higher search rankings.
2564. Fetch Status (TrawlerFetchStatus)
      • Description: Provides information about the status of a fetch request, including reasons for failures or errors.
      • SEO Purpose: Understanding fetch statuses helps identify and resolve issues that might affect content indexing and search rankings.
      • How to Use: Monitor fetch statuses regularly to identify and address issues affecting content fetching and indexing, ensuring optimal search performance.
2565. Content Range Info (TrawlerContentRangeInfo)
      • Description: Parsed version of HTTP Content-Range fields, indicating the range of bytes returned in a fetch request.
      • SEO Purpose: Proper handling of content range data ensures efficient data fetching and delivery, improving user experience and search performance.
      • How to Use: Implement content range handling to optimize data fetching processes and ensure efficient content delivery.
2566. Event Logging (TrawlerEvent)
      • Description: Logs significant events during URL fetches, such as fetch start, URL rejection, and fetch completion.
      • SEO Purpose: Event logging helps identify and troubleshoot issues in the fetch process, ensuring smooth content delivery and indexing.
      • How to Use: Regularly review event logs to identify and resolve issues in the fetch process, ensuring efficient content delivery and indexing.
2567. Client Service Info (TrawlerClientServiceInfo)
      • Description: Stores specific data for clients using Trawler/Harpoon services, such as client names and fetch statistics.
      • SEO Purpose: Understanding client service data helps optimize fetch processes and improve content delivery, enhancing search engine indexing and ranking.
      • How to Use: Utilize client service data to optimize fetch processes and ensure efficient content delivery and indexing.
2568. Partial Response Handling (TrawlerFetchReplyDataPartialResponse)
      • Description: Manages streaming responses in large file fetches, linking multiple fetch replies to a single request.
      • SEO Purpose: Efficient partial response handling ensures smooth content delivery and improved user experience, positively impacting search rankings.
      • How to Use: Implement partial response handling for large file fetches to ensure smooth content delivery and enhance user experience.
2569. TCP/IP Information (TrawlerTCPIPInfo)
      • Description: Tracks fetch connection endpoints, providing detailed information about source and destination IP addresses.
      • SEO Purpose: Accurate tracking of connection endpoints helps optimize fetch processes and improve the efficiency of web crawlers, enhancing search engine indexing and ranking.
      • How to Use: Utilize TCP/IP information to optimize fetch processes and ensure efficient content delivery and indexing.
2570. Throttle Client Data (TrawlerThrottleClientData)
      • Description: Contains information about bandwidth throttling for fetch clients, including maximum allowed rates.
      • SEO Purpose: Effective throttling ensures fair use of bandwidth and prevents server overload, improving content delivery and user experience.
      • How to Use: Implement throttling measures to manage bandwidth usage effectively and ensure smooth content delivery.
2571. Universal Search Knowledge Result Support (UniversalsearchNewPackerKnowledgeResultSupport)
      • Description: Provides information about support for knowledge results in universal search, ensuring accurate and relevant search results.
      • SEO Purpose: Accurate knowledge result support enhances the relevance and credibility of search results, improving user engagement and satisfaction.
      • How to Use: Ensure your content is optimized for universal search knowledge results to improve its relevance and visibility in search results.
2572. URL Poisoning Data (UrlPoisoningData)
      • Description: Contains information about URL poisoning, including the number of spam siblings detected.
      • SEO Purpose: Identifying and mitigating URL poisoning helps maintain the integrity of your site, preventing it from being associated with spam and improving its search ranking.
      • How to Use: Regularly check for and address URL poisoning issues to maintain the integrity and trustworthiness of your site.
2573. Trusted Genome Annotation (VendingConsumerProtoTrustedGenomeAnnotation)
      • Description: Includes trusted genome entities associated with an app, enhancing the credibility and accuracy of app-related content.
      • SEO Purpose: Trusted genome annotations improve the credibility and relevance of app content, positively affecting search rankings.
      • How to Use: Ensure that app-related content includes accurate and trustworthy genome annotations to enhance its credibility and search performance.
2574. Ambisonics Metadata (VideoAmbisonicsAmbisonicsMetadata)
      • Description: Provides metadata for ambisonic audio, including channel maps, ordering, and normalization.
      • SEO Purpose: Proper ambisonics metadata ensures high-quality audio content, enhancing user experience and engagement.
      • How to Use: Include detailed ambisonics metadata for audio content to ensure high-quality playback and user experience.
2575. Video ID (VideoAssetsVenomVideoId)
      • Description: Unique identifier for a video, ensuring that each video can be distinctly referenced and tracked.
      • SEO Purpose: Unique video IDs improve content management and tracking, enhancing the organization and indexing of video content.
      • How to Use: Assign unique IDs to all video content to ensure efficient management and tracking.
2576. Video Audio Stream (VideoAudioStream)
      • Description: Contains information about video audio streams, ensuring that audio content is accurately processed and delivered.
      • SEO Purpose: Proper handling of video audio streams enhances the quality of multimedia content, improving user engagement and search performance.
      • How to Use: Ensure accurate metadata for video audio streams to improve the quality and delivery of multimedia content.
2577. Closed Captions (VideoClosedCaptions)
      • Description: Indicates whether a video has closed captions, enhancing accessibility for users with hearing impairments.
      • SEO Purpose: Including closed captions improves accessibility and user engagement, positively impacting search rankings.
      • How to Use: Add closed captions to video content to enhance accessibility and improve user experience and search performance.
2578. Thumbnail Information (VideoContentSearchAnchorThumbnailInfo)
      • Description: Provides details about thumbnail images for video anchors, including color entropy and safety classifications.
      • SEO Purpose: High-quality and safe thumbnail images improve user engagement and click-through rates, enhancing search performance.
      • How to Use: Ensure thumbnails are high-quality, accurately represent the content, and are safe for all audiences to improve engagement and search performance.
2579. Aspect Information (VideoContentSearchAspect)
      • Description: Contains information about product aspects, ensuring that various features and qualities of a product are accurately represented.
      • SEO Purpose: Detailed aspect information enhances the accuracy and relevance of product content, improving its visibility in search results.
      • How to Use: Include comprehensive aspect information for products to improve their relevance and visibility in search results.
2580. Caption Entity Information (VideoContentSearchCaptionEntityDocInfo)
      • Description: Provides information about document appearances of an entity within video captions, ensuring accurate indexing and retrieval.
      • SEO Purpose: Accurate caption entity information improves the relevance and accuracy of search results for video content.
      • How to Use: Ensure entity information within captions is detailed and accurate to enhance search relevance and accuracy.
2581. Span Anchor Features (VideoContentSearchCaptionSpanAnchorFeatures)
      • Description: Contains features and scores for caption span anchors, including embedding distances and confidence stats.
      • SEO Purpose: Detailed span anchor features enhance the precision and relevance of video search results, improving user engagement.
      • How to Use: Utilize span anchor features to improve the precision and relevance of video search results, enhancing user engagement and satisfaction.
2582. Caption Span Anchor Set Features (VideoContentSearchCaptionSpanAnchorSetFeatures)
      • Description: This attribute summarizes the dolphin scores across a set of caption span anchors. It evaluates how well the spans are recognized and scored within the set.
      • SEO Purpose: Ensuring high-quality caption spans improves the accuracy of video content indexing and retrieval, leading to better search performance.
      • How to Use: Optimize video captions by ensuring they are clear and relevant, and use tools to verify their accuracy. This helps search engines better understand and index your video content.
2583. Comment Anchor Set Features (VideoContentSearchCommentAnchorSetFeatures)
      • Description: Contains set-level features for comment anchors, summarizing comments retrieved from various sources, including YouTube’s Data API.
      • SEO Purpose: Analyzing and optimizing comment data can enhance user engagement and interaction, positively affecting video rankings.
      • How to Use: Monitor and manage video comments to ensure they are relevant and engaging. Respond to user comments to foster interaction and improve the overall content quality.
2584. Description Anchor Features (VideoContentSearchDescriptionAnchorFeatures)
      • Description: This attribute evaluates description anchors by their entity text coverage, presence in ASR (Automatic Speech Recognition), and alignment with the description timing.
      • SEO Purpose: High-quality descriptions help improve video indexing and retrieval, enhancing search visibility and user engagement.
      • How to Use: Craft detailed and accurate descriptions for your videos. Ensure descriptions align with spoken content and include relevant keywords to improve search engine indexing.
2585. Description Anchor Set Features (VideoContentSearchDescriptionAnchorSetFeatures)
      • Description: Summarizes the performance of description anchors in relation to ASR matches, including anchor counts and unique matches.
      • SEO Purpose: Effective description anchors enhance the discoverability of video content, improving search rankings and user engagement.
      • How to Use: Regularly review and optimize your video descriptions to ensure they are effectively matched to captions and improve search performance.
2586. Description Span Info (VideoContentSearchDescriptionSpanInfo)
      • Description: Metadata about description spans, providing context and additional details about the anchor source.
      • SEO Purpose: Properly annotated description spans aid in accurate content indexing and retrieval, boosting search visibility.
      • How to Use: Ensure your video descriptions are well-structured and accurately reflect the content to improve search engine indexing and user engagement.
2587. Dolphin Ensemble Score (VideoContentSearchDolphinEnsembleScore)
      • Description: Provides scores from individual dolphin ensemble models, which are used to evaluate video anchors.
      • SEO Purpose: Accurate scoring of video anchors enhances content ranking and retrieval, leading to better visibility and engagement.
      • How to Use: Use advanced scoring models to evaluate and optimize your video content, ensuring it meets high-quality standards and improves search rankings.
2588. Dolphin Features (VideoContentSearchDolphinFeatures)
      • Description: Includes various features used to build Dolphin examples, such as alternative queries, answers, timestamps, and URLs.
      • SEO Purpose: Optimizing these features helps improve the accuracy of video content recommendations and search results.
      • How to Use: Ensure your video content includes clear and relevant metadata, such as accurate titles and timestamps, to improve search engine understanding and indexing.
2589. Dolphin Scoring Config (VideoContentSearchDolphinScoringConfig)
      • Description: Contains configuration settings for Dolphin scoring models, including model names, inference methods, and output keys.
      • SEO Purpose: Proper configuration of scoring models ensures accurate evaluation of video content, enhancing search rankings and visibility.
      • How to Use: Regularly update and optimize your scoring models to ensure they are configured correctly and provide accurate evaluations of your video content.
2590. Entity Annotations (VideoContentSearchEntityAnnotations)
      • Description: Annotations for entities representing anchor labels or query text, aiding in the accurate identification and indexing of video content.
      • SEO Purpose: Detailed entity annotations improve the relevance and accuracy of search results, enhancing user engagement and content visibility.
      • How to Use: Include comprehensive annotations for key entities in your video content to improve search engine indexing and retrieval.
2591. Entity Group Info (VideoContentSearchEntityGroupInfo)
      • Description: Contains information about groups of entities, including collection IDs and labels.
      • SEO Purpose: Grouping entities accurately helps improve content categorization and retrieval, leading to better search performance.
      • How to Use: Organize related entities into groups with clear labels to enhance the discoverability and relevance of your video content.
2592. Frame Similarity Interval (VideoContentSearchFrameSimilarityInterval)
      • Description: Provides information on frame-level similarities within a specific interval of frames for each topic.
      • SEO Purpose: Identifying frame similarities helps improve content indexing and retrieval, enhancing search accuracy and user engagement.
      • How to Use: Analyze frame-level similarities to optimize video content for better indexing and retrieval by search engines.
2593. Frame Starburst Data (VideoContentSearchFrameStarburstData)
      • Description: Contains dense data for frame-level starburst features, aiding in the detailed analysis of video frames.
      • SEO Purpose: Detailed frame data improves the precision of video content indexing and retrieval, leading to better search visibility.
      • How to Use: Utilize frame-level starburst data to enhance the quality and accuracy of video indexing and search results.
2594. Generative Prediction Features (VideoContentSearchGenerativePredictionFeatures)
      • Description: Includes features for inferences from generative models, such as passages, predictions, and targets.
      • SEO Purpose: Leveraging generative prediction features enhances the relevance and accuracy of video content recommendations and search results.
      • How to Use: Incorporate generative model predictions to improve the contextual relevance and accuracy of your video content.
2595. Generative Topic Prediction Features (VideoContentSearchGenerativeTopicPredictionFeatures)
      • Description: Provides features from the prediction service that generates topics for video content.
      • SEO Purpose: Accurate topic predictions help improve the categorization and discoverability of video content, enhancing search rankings.
      • How to Use: Use generative topic predictions to optimize the categorization and tagging of your video content for better search engine indexing.
2596. Instruction Anchor Features (VideoContentSearchInstructionAnchorFeatures)
      • Description: Contains metadata about instruction anchors, detailing their role and context within the video.
      • SEO Purpose: Properly annotated instruction anchors improve the indexing and retrieval of instructional content, enhancing user engagement and search performance.
      • How to Use: Clearly define and annotate instructional content within your videos to improve its discoverability and relevance in search results.
2597. Instruction Training Data Anchor Features (VideoContentSearchInstructionTrainingDataAnchorFeatures)
      • Description: Provides metadata about instructional anchors used for training data, including multiple steps and description anchors.
      • SEO Purpose: High-quality training data enhances the accuracy of instructional content indexing and recommendations.
      • How to Use: Develop comprehensive training data for instructional anchors to improve the relevance and accuracy of search results for educational content.
2598. List Anchor Features (VideoContentSearchListAnchorFeatures)
      • Description: Metadata about list description anchors, aiding in the detailed analysis and indexing of list-based content.
      • SEO Purpose: Properly annotated list anchors improve the discoverability and relevance of list-based video content, enhancing search performance.
      • How to Use: Ensure your list-based content is clearly structured and annotated to improve its indexing and retrieval by search engines.
2599. List Anchor Set Features (VideoContentSearchListAnchorSetFeatures)
      • Description: Cluster-level metadata about list anchors, summarizing their performance and relevance.
      • SEO Purpose: Accurate clustering of list anchors enhances content categorization and search visibility.
      • How to Use: Organize list anchors into relevant clusters to improve their categorization and discoverability in search results.
2600. List Training Data Anchor Features (VideoContentSearchListTrainingDataAnchorFeatures)
      • Description: Metadata about list description anchors used to build training data, ensuring the quality and accuracy of list-based content.
      • SEO Purpose: High-quality training data for list anchors improves the relevance and accuracy of list-based content recommendations.
      • How to Use: Develop comprehensive training data for list anchors to enhance the relevance and accuracy of search results for list-based content.
2601. List Training Data Set Features (VideoContentSearchListTrainingDataSetFeatures)
      • Description: Cluster-level metadata about list description anchors used to build training data, summarizing their performance and relevance.
      • SEO Purpose: Properly clustered training data enhances the accuracy and relevance of list-based content recommendations and search results.
      • How to Use: Organize list training data into relevant clusters to improve their categorization and discoverability in search results.
2602. Match Scores (VideoContentSearchMatchScores)
      • Description: Provides information about match scores for video content, including methods used and similarity scores.
      • SEO Purpose: Accurate match scoring enhances the relevance and accuracy of video content recommendations and search results.
      • How to Use: Utilize match scores to evaluate and optimize your video content, ensuring it meets high-quality standards and improves search rankings.
2603. Metric Stats (VideoContentSearchMetricStats)
      • Description: Summarizes median, mean, and standard deviation of feature values, providing a statistical overview of video content features.
      • SEO Purpose: Detailed metric stats help evaluate and optimize video content, enhancing its quality and search performance.
      • How to Use: Regularly analyze metric stats to identify areas for improvement and optimize your video content for better search rankings.
2604. Multimodal Topic Features (VideoContentSearchMultimodalTopicFeatures)
      • Description: Provides multimodal features for generated topics, aiding in the detailed analysis and categorization of video content.
      • SEO Purpose: Leveraging multimodal features improves the accuracy and relevance of topic-based video content recommendations.
      • How to Use: Incorporate multimodal features to enhance the categorization and tagging of your video content for better search engine indexing.
2605. Named Entity (VideoContentSearchNamedEntity)
      • Description: Represents named entities within video content, aiding in their accurate identification and indexing.
      • SEO Purpose: Detailed named entity annotations improve the relevance and accuracy of video content search results.
      • How to Use: Include comprehensive annotations for named entities in your video content to improve search engine indexing and retrieval.
2606. Navboost Anchor Features (VideoContentSearchNavboostAnchorFeatures)
      • Description: Features for queries generated using document navboost data with timed anchors, enhancing the relevance of search results.
      • SEO Purpose: Optimizing navboost anchor features improves the precision and relevance of video content recommendations.
      • How to Use: Utilize navboost data to optimize your video content for better search engine indexing and improved relevance in search results.
2607. OCR Text (VideoContentSearchOCRText)
      • Description: Contains OCR text, its start time, and additional details about position and fonts, aiding in accurate content analysis.
      • SEO Purpose: Properly processed OCR text enhances the indexing and retrieval of video content, improving search visibility.
      • How to Use: Ensure OCR text in your video content is accurately processed and annotated to improve its discoverability and relevance in search results.
2608. OCR/ASR Feature (VideoContentSearchOcrAsrFeature)
      • Description: Provides features that compare OCR text with ASR text, including edit distances, word overlaps, and scores.
      • SEO Purpose: Accurate OCR and ASR comparisons enhance the relevance and accuracy of video content indexing and retrieval.
      • How to Use: Regularly compare and optimize OCR and ASR text to ensure high-quality indexing and improved search performance.
2609. OCR/ASR Set Feature (VideoContentSearchOcrAsrSetFeature)
      • Description: Summarizes word overlap scores between OCR and ASR text for anchor clusters, enhancing content analysis.
      • SEO Purpose: Effective OCR and ASR set features improve the precision and relevance of video content recommendations.
      • How to Use: Analyze word overlap scores to optimize your video content for better indexing and retrieval by search engines.
2610. OCR Description Training Data Anchor Features (VideoContentSearchOcrDescriptionTrainingDataAnchorFeatures)
      • Description: Metadata about the join of description anchors and OCR data used to build training data, enhancing content quality.
      • SEO Purpose: High-quality training data improves the relevance and accuracy of OCR-based video content recommendations.
      • How to Use: Develop comprehensive training data that joins description anchors and OCR data to enhance the relevance and accuracy of search results.
2611. OCR Description Training Data Set Features (VideoContentSearchOcrDescriptionTrainingDataSetFeatures)
      • Description: Metadata about the join of description anchors and OCR data for a set of description anchors, summarizing their performance.
      • SEO Purpose: Properly joined training data enhances the accuracy and relevance of OCR-based video content recommendations.
      • How to Use: Organize description anchors and OCR data into relevant sets to improve their categorization and discoverability in search results.
2612. OCR Video Features (VideoContentSearchOcrVideoFeature)
      • Description: These features are extracted from OCR (Optical Character Recognition) data at the video level, providing detailed information about the text content present in video frames.
      • SEO Purpose: Enhances the indexing and retrieval of videos by recognizing and processing text within video frames, making content more searchable and accessible.
      • How to Use: Ensure high-quality, readable text in your video content. Use clear and consistent fonts and avoid cluttered backgrounds to improve OCR accuracy and enhance search engine indexing.
2613. On-Screen Text Cluster Features (VideoContentSearchOnScreenTextClusterFeature)
      • Description: These features describe the properties and attributes of clusters of on-screen text within a video.
      • SEO Purpose: Improves the understanding of grouped text elements in videos, aiding in the accurate categorization and indexing of video content.
      • How to Use: Organize on-screen text in a logical and visually clear manner. Group related text elements together to improve content retrieval and user engagement.
2614. On-Screen Text Features (VideoContentSearchOnScreenTextFeature)
      • Description: Features that help filter and identify titles and labels from on-screen text in video content.
      • SEO Purpose: Facilitates the extraction and categorization of key text elements, improving the accuracy of video content indexing.
      • How to Use: Clearly label and title your video content on-screen. Ensure text is easily readable and positioned consistently to enhance content discovery and search performance.
2615. QBST Terms Overlap Features (VideoContentSearchQbstTermsOverlapFeatures)
      • Description: Features that measure the overlap of QBST (Query by Semantic Text) terms with candidate queries, helping assess the relevance of video content.
      • SEO Purpose: Enhances the relevance of video content in response to specific queries, improving search accuracy and user satisfaction.
      • How to Use: Optimize your video metadata and descriptions to align with common search queries, improving the semantic relevance of your content.
2616. Q&A Anchor Features (VideoContentSearchQnaAnchorFeatures)
      • Description: Features specific to individual Q&A anchors within video content, aiding in the identification and categorization of Q&A segments.
      • SEO Purpose: Improves the discoverability of Q&A segments in videos, making it easier for users to find relevant information.
      • How to Use: Clearly structure and label Q&A segments within your videos. Use consistent formatting and metadata to enhance indexing and retrieval.
2617. Q&A Anchor Set Features (VideoContentSearchQnaAnchorSetFeatures)
      • Description: Debugging information for sets of Q&A anchors, providing insights into the performance and relevance of grouped Q&A segments.
      • SEO Purpose: Enhances the overall quality and relevance of Q&A content in videos, improving user engagement and search performance.
      • How to Use: Regularly review and optimize your Q&A anchor sets. Ensure they are logically grouped and clearly labeled to improve discoverability.
2618. Rank Embed Nearest Neighbors Features (VideoContentSearchRankEmbedNearestNeighborsFeatures)
      • Description: Features that identify the nearest neighbor relationships for candidate queries based on rank embedding, aiding in the assessment of query relevance.
      • SEO Purpose: Improves the accuracy and relevance of search results by understanding the contextual relationships between queries and content.
      • How to Use: Optimize your video content and metadata to reflect relevant keywords and topics. Ensure your content is contextually aligned with common search queries.
2619. SAFT Entity Info (VideoContentSearchSaftEntityInfo)
      • Description: Information about SAFT (Semantic Analysis Framework for Text) named entities related to a given topic within video content.
      • SEO Purpose: Enhances the semantic understanding and indexing of video content, improving search relevance and user engagement.
      • How to Use: Include detailed and accurate entity information in your video content. Use structured data to enhance the semantic understanding of your content.
2620. Shopping Opinions Anchor Features (VideoContentSearchShoppingOpinionsAnchorFeatures)
      • Description: Features specific to individual shopping opinions anchors, used to identify and categorize user reviews and opinions in video content.
      • SEO Purpose: Improves the discoverability and relevance of user-generated content and reviews, enhancing search performance for shopping-related queries.
      • How to Use: Clearly highlight and label user reviews and opinions within your videos. Use consistent formatting and metadata to enhance indexing and retrieval.
2621. Similarity Match Info (VideoContentSearchSimilarityMatchInfo)
      • Description: Provides detailed information about the similarity matching of text segments within video content, including scores and matching methods.
      • SEO Purpose: Enhances the accuracy of content matching and retrieval, improving the relevance of search results.
      • How to Use: Optimize your video content by ensuring text segments are clear and contextually relevant. Use similarity matching to refine content alignment with search queries.
2622. Span Dolphin Features (VideoContentSearchSpanDolphinFeatures)
      • Description: Features extracted from text passages using Dolphin models, including titles and timestamps, aiding in the detailed analysis of video content.
      • SEO Purpose: Improves the precision of video content analysis and indexing, enhancing search relevance and user engagement.
      • How to Use: Ensure your video content includes detailed and accurate titles and timestamps. Use Dolphin models to analyze and optimize text passages for better indexing.
2623. Span Dolphin Scores (VideoContentSearchSpanDolphinScores)
      • Description: Scores for text spans derived from Dolphin models, including token-score pairs and span candidates, used to evaluate the relevance of video segments.
      • SEO Purpose: Enhances the precision and relevance of video content recommendations and search results.
      • How to Use: Utilize Dolphin model scores to evaluate and optimize text spans in your video content. Ensure spans are contextually relevant and accurately labeled.
2624. Sports Key Moments Anchor Set Features (VideoContentSearchSportsKeyMomentsAnchorSetFeatures)
      • Description: Features for sets of Sports Key Moments (SKM) anchors, aiding in the identification and categorization of key moments in sports videos.
      • SEO Purpose: Improves the discoverability of important sports moments, enhancing user engagement and search performance for sports-related content.
      • How to Use: Clearly identify and label key moments in sports videos. Use consistent formatting and metadata to enhance indexing and retrieval of these moments.
2625. Text Match Info (VideoContentSearchTextMatchInfo)
      • Description: Provides detailed information about text matching within video content, including similarity scores, matched ASR text, and timestamps.
      • SEO Purpose: Enhances the accuracy of text matching and retrieval, improving the relevance of video content in search results.
      • How to Use: Optimize your video content by ensuring text is clear and contextually relevant. Use text matching to refine content alignment with search queries.
2626. Text Similarity Features (VideoContentSearchTextSimilarityFeatures)
      • Description: Features that measure text similarity between hypothesis and reference texts within video content, including token match counts and similarity scores.
      • SEO Purpose: Improves the semantic relevance of video content, enhancing search accuracy and user engagement.
      • How to Use: Regularly analyze and optimize text similarity features in your video content. Ensure text segments are contextually aligned with common search queries.
2627. Token Alignment (VideoContentSearchTokenAlignment)
      • Description: Maps tokens between hypothesis and reference texts, providing a detailed analysis of text alignment within video content.
      • SEO Purpose: Enhances the accuracy of text alignment and retrieval, improving the relevance of video content in search results.
      • How to Use: Ensure your video content includes well-aligned text segments. Use token alignment to refine content and improve its relevance in search results.
2628. Token Timing Info (VideoContentSearchTokenTimingInfo)
      • Description: Provides timing information for tokens in ASR spans, aiding in the detailed analysis of video content.
      • SEO Purpose: Enhances the precision of video content indexing and retrieval by understanding the timing of spoken words.
      • How to Use: Ensure your video content includes accurate timing information for spoken words. Use token timing info to improve content alignment with search queries.
2629. Video Actions (VideoContentSearchVideoActions)
      • Description: Contains information about video actions, such as skip patterns defined by schema.org, aiding in the detailed analysis of user interactions.
      • SEO Purpose: Improves the understanding of user interactions with video content, enhancing engagement and search performance.
      • How to Use: Clearly define and label interactive elements in your videos. Use video action data to optimize content for better user engagement and search performance.
2630. Video Anchor (VideoContentSearchVideoAnchor)
      • Description: Represents anchors within video content, aiding in the identification and categorization of key segments.
      • SEO Purpose: Enhances the discoverability of important video segments, improving search relevance and user engagement.
      • How to Use: Clearly identify and label key segments within your videos. Use consistent formatting and metadata to enhance indexing and retrieval of these segments.
2631. Video Anchor Rating Score (VideoContentSearchVideoAnchorRatingScore)
      • Description: Aggregated rating score for video anchors, used in training pipelines to evaluate the relevance of key segments.
      • SEO Purpose: Improves the accuracy of video content recommendations and search results by using aggregated rating scores.
      • How to Use: Regularly review and optimize the rating scores of video anchors. Ensure key segments are relevant and accurately labeled to enhance search performance.
2632. Video Anchor Score Information (VideoContentSearchVideoAnchorScoreInfo)
      • Description: This attribute contains scoring and debugging information related to video anchors, including details not directly used in the final video anchor data.
      • SEO Purpose: By analyzing and understanding anchor scores, you can improve the quality and relevance of key video segments, enhancing search engine ranking.
      • How to Use: Regularly review and optimize the scoring details of your video anchors to ensure they are relevant and provide valuable insights into your content.
2633. Video Anchor Score Information Label Transformation (VideoContentSearchVideoAnchorScoreInfoLabelTransformation)
      • Description: Stores the label before any cleaning or transformation processes. It tracks the changes that labels undergo during different transformation stages.
      • SEO Purpose: Maintaining the integrity of labels throughout transformations ensures consistent and accurate indexing, which improves search engine visibility.
      • How to Use: Monitor and document label transformations to maintain clarity and accuracy, ensuring the labels correctly represent the video content.
2634. Video Anchor Set Rating Score (VideoContentSearchVideoAnchorSetRatingScore)
      • Description: Aggregated rating scores for sets of video anchors, used primarily in training pipelines to evaluate the relevance of video segments.
      • SEO Purpose: Helps in refining video content by identifying high and low-performing segments, which can be crucial for optimizing video SEO.
      • How to Use: Analyze rating scores to identify which video segments perform well and which need improvement. Use this data to enhance the overall quality of your video content.
2635. Video Anchor Sets (VideoContentSearchVideoAnchorSets)
      • Description: Represents multiple types of text anchors within a video. A single video can have various anchors like list anchors and OCR anchors.
      • SEO Purpose: Facilitates comprehensive indexing of all text-related elements within a video, improving the discoverability of specific content segments.
      • How to Use: Implement diverse anchor types in your videos to cover all relevant textual content, ensuring thorough indexing and better search performance.
2636. Video Anchors (VideoContentSearchVideoAnchors)
      • Description: A video can have a list of text anchors with different types, aiding in the detailed analysis and indexing of video content.
      • SEO Purpose: Enhances the granular indexing of video content, making specific segments more discoverable and improving overall search visibility.
      • How to Use: Clearly define and utilize different types of anchors within your videos. Ensure each anchor is accurately labeled and contextually relevant.
2637. Video Anchors Score Information (VideoContentSearchVideoAnchorsScoreInfo)
      • Description: Contains scoring and debugging information specific to video anchors, providing insights into their performance and relevance.
      • SEO Purpose: Detailed scoring information helps in fine-tuning video content for better relevance and performance in search results.
      • How to Use: Regularly assess the scoring details of your video anchors. Use this information to optimize and refine your content.
2638. Video Common Features (VideoContentSearchVideoCommonFeatures)
      • Description: Contains common features at the video level that apply to all anchor types, aiding in the overall analysis of video content.
      • SEO Purpose: Common features provide a baseline for evaluating video content, improving consistency in indexing and search relevance.
      • How to Use: Ensure your video content includes all necessary common features. Regularly review these features to maintain consistency and improve search engine performance.
2639. Video Generated Query Features (VideoContentSearchVideoGeneratedQueryFeatures)
      • Description: Features applied at the video level for queries generated, aiding in the relevance and accuracy of search results.
      • SEO Purpose: Enhances the ability to generate relevant queries based on video content, improving search accuracy and user engagement.
      • How to Use: Optimize your video metadata and descriptions to align with potential search queries, ensuring better search performance and relevance.
2640. Video Information (VideoContentSearchVideoInfo)
      • Description: Holds metadata and signals of a video, typically used for debugging data in offline pipelines related to video anchors.
      • SEO Purpose: Accurate metadata and signals improve the indexing and retrieval of video content, enhancing its discoverability in search results.
      • How to Use: Ensure all relevant metadata and signals are accurately included in your video content. Use this data to improve indexing and search performance.
2641. Video Introduction (VideoContentSearchVideoIntroduction)
      • Description: Specifies whether a video has an introduction part that can be safely skipped without impacting the user’s understanding of the content.
      • SEO Purpose: Allows users to skip non-essential parts of the video, improving user experience and engagement, which can positively impact search rankings.
      • How to Use: Clearly define and label the introduction part of your videos. Provide options for users to skip the introduction to improve engagement.
2642. Video Multimodal Topic Features (VideoContentSearchVideoMultimodalTopicFeatures)
      • Description: Multimodal features at the video level for generated topics, aiding in the comprehensive analysis and categorization of video content.
      • SEO Purpose: Enhances the understanding and indexing of video content across multiple modalities, improving search relevance and accuracy.
      • How to Use: Incorporate multimodal features into your video content. Ensure these features are accurately captured and labeled to improve indexing and retrieval.
2643. Video Score Information (VideoContentSearchVideoScoreInfo)
      • Description: Provides scoring information at the video level, aiding in the evaluation of overall video performance and relevance.
      • SEO Purpose: Detailed scoring information helps in optimizing video content for better search performance and user engagement.
      • How to Use: Regularly review and optimize the scoring details of your videos. Use this data to improve content relevance and search performance.
2644. Visual Features (VideoContentSearchVisualFeatures)
      • Description: Contains visual tokens or features, such as starburst visual elements, aiding in the detailed analysis of video content.
      • SEO Purpose: Enhances the visual indexing of video content, improving the relevance and discoverability of visually rich segments.
      • How to Use: Ensure your video content includes visually distinctive elements. Use visual features to improve the indexing and retrieval of visually appealing content.
2645. Inline Playback Metadata (VideoCrawlVideoInlinePlaybackMetadata)
      • Description: Stores information about inline playback in the video web attachment portion of the web search index.
      • SEO Purpose: Improves the indexing and playback experience of video content directly within search results, enhancing user engagement.
      • How to Use: Include detailed metadata for inline playback in your video content. Ensure playback features are optimized for seamless integration into search results.
2646. Dolby Vision Decoder Configuration (VideoDoViDecoderConfiguration)
      • Description: Configuration for decoding Dolby Vision content encoded by any codec, providing details about profiles and levels.
      • SEO Purpose: Ensures high-quality playback of Dolby Vision content, enhancing the viewing experience and user engagement.
      • How to Use: Ensure your video content includes proper Dolby Vision configurations. Optimize video settings to support high-quality playback.
2647. Video Color Information (VideoFileColorInfo)
      • Description: Holds all color information about a signal, including color primaries, transfer characteristics, matrix coefficients, and color range.
      • SEO Purpose: Accurate color information ensures high-quality visual representation, improving user engagement and content attractiveness.
      • How to Use: Ensure your video content includes detailed and accurate color information. Use this data to optimize visual quality and enhance user experience.
2648. Content Light Level (VideoFileContentLightLevel)
      • Description: Provides coarse statistics on the luminance levels in video content, used as a hint by algorithms and displays for tone mapping.
      • SEO Purpose: Accurate light level information helps in optimizing video playback quality, enhancing the viewing experience and user satisfaction.
      • How to Use: Include detailed light level information in your video content. Use this data to ensure optimal tone mapping and visual quality.
2649. Frame Packing Arrangement (VideoFileFramePackingArrangement)
      • Description: Information on the arrangement of frames in a video, aiding in the detailed analysis and playback configuration.
      • SEO Purpose: Proper frame packing ensures high-quality video playback, improving user engagement and content attractiveness.
      • How to Use: Ensure your video content includes detailed frame packing information. Use this data to optimize playback settings and enhance visual quality.
2650. HDR10+ Stats (VideoFileHDR10PlusStats)
      • Description: Provides statistics on HDR10+ video frames, aiding in the detailed analysis and optimization of high dynamic range content.
      • SEO Purpose: Enhances the playback quality of HDR10+ content, improving the viewing experience and user satisfaction.
      • How to Use: Include detailed HDR10+ statistics in your video content. Use this data to optimize high dynamic range settings and enhance visual quality.
2651. Mastering Display Metadata (VideoFileMasteringDisplayMetadata)
      • Description: Information about the mastering display color volume, used for tone mapping HDR signals to different displays.
      • SEO Purpose: Ensures consistent and high-quality playback across different displays, enhancing user experience and content attractiveness.
      • How to Use: Include detailed mastering display metadata in your video content. Use this data to optimize tone mapping and ensure consistent visual quality across devices.
2652. Color Coordinate (VideoFileMasteringDisplayMetadataCIE1931Coordinate)
      • Description: Represents a color coordinate in the CIE1931 color space, which is a standard for color representation used in video processing.
      • SEO Purpose: Accurate color representation ensures high-quality video playback, which can improve user engagement and retention.
      • How to Use: Ensure that your video content is color-accurate by using CIE1931 coordinates, leading to better visual quality and user satisfaction.
2653. Spherical Metadata (VideoFileSphericalMetadata)
      • Description: Contains globally allowed spherical metadata, providing details about the spherical nature of the video content.
      • SEO Purpose: Spherical metadata helps in the correct rendering and navigation of 360-degree videos, enhancing user experience.
      • How to Use: Include spherical metadata to ensure that 360-degree videos are properly indexed and displayed, improving engagement for immersive content.
2654. Spherical Metadata Cropped Area (VideoFileSphericalMetadataCroppedArea)
      • Description: Specifies the cropping coordinates in pixels for spherical video content.
      • SEO Purpose: Accurate cropping metadata ensures the correct display of 360-degree videos, enhancing the viewer’s experience.
      • How to Use: Provide precise cropping coordinates for spherical videos to ensure they are displayed correctly across all devices.
2655. Spherical Metadata Cubemap Projection (VideoFileSphericalMetadataCubemapProjection)
      • Description: Specifies the usage of cubemap projection for spherical video content, detailing how the video is projected onto a cube.
      • SEO Purpose: Proper cubemap projection metadata improves the quality and user experience of 360-degree videos.
      • How to Use: Use cubemap projection for high-quality rendering of 360-degree videos, ensuring a seamless and immersive experience.
2656. Spherical Metadata Equirectangular Projection (VideoFileSphericalMetadataEquirectProjection)
      • Description: Specifies the usage of equirectangular projection, detailing the proportions of the video frame not covered by the projection.
      • SEO Purpose: Ensures accurate rendering and navigation of equirectangular projected 360-degree videos.
      • How to Use: Include equirectangular projection metadata for correct display of 360-degree videos, enhancing user experience and engagement.
2657. Spherical Metadata FOV Bounds (VideoFileSphericalMetadataFOVBounds)
      • Description: Provides field of view (FOV) boundaries in degrees for spherical video content, specifying tilt and yaw angles.
      • SEO Purpose: Accurate FOV metadata enhances the viewer’s navigation and interaction with 360-degree videos.
      • How to Use: Ensure that your 360-degree videos include detailed FOV boundaries to improve the user experience and engagement.
2658. Spherical Metadata Mesh Projection (VideoFileSphericalMetadataMeshProjection)
      • Description: Specifies the usage of mesh projection, including details about vertices and coordinates for spherical video content.
      • SEO Purpose: Mesh projection metadata ensures high-quality rendering and navigation of 360-degree videos.
      • How to Use: Use mesh projection for detailed and accurate rendering of spherical videos, enhancing the immersive experience.
2659. Spherical Metadata Pose (VideoFileSphericalMetadataPose)
      • Description: Specifies the compass heading, pitch, and roll for the origin of the projection, ensuring accurate orientation of spherical video content.
      • SEO Purpose: Accurate pose metadata improves the viewer’s interaction and navigation within 360-degree videos.
      • How to Use: Include detailed pose metadata to ensure that your spherical videos are correctly oriented and easily navigable.
2660. Spherical Metadata View Direction (VideoFileSphericalMetadataViewDirection)
      • Description: Provides view direction metadata, including heading, pitch, and roll degrees, for spherical video content.
      • SEO Purpose: Enhances the accuracy and quality of the viewing experience for 360-degree videos.
      • How to Use: Ensure your spherical videos include precise view direction metadata to enhance user engagement and experience.
2661. YouTube Video Clip Info (VideoGoogleVideoClipInfo)
      • Description: Contains meta information extracted from video files used in YouTube apps.
      • SEO Purpose: Accurate clip information ensures better indexing and retrieval of video content on YouTube.
      • How to Use: Include detailed metadata for your YouTube videos to improve their discoverability and relevance in search results.
2662. Legos Annotations Set (VideoLegosLegosAnnotationsSet)
      • Description: Contains a set of annotations and features for a specific video, aiding in detailed analysis and categorization.
      • SEO Purpose: Detailed annotations improve the indexing and relevance of video content in search results.
      • How to Use: Regularly update and maintain detailed annotations for your video content to enhance search engine indexing and retrieval.
2663. Legos Annotations Sets (VideoLegosLegosAnnotationsSets)
      • Description: Contains multiple sets of annotations for a video, each with different feature sets.
      • SEO Purpose: Multiple annotation sets provide a comprehensive understanding of video content, improving search relevance.
      • How to Use: Use various annotation sets to cover all aspects of your video content, ensuring thorough indexing and better search performance.
2664. Video Media Information (VideoMediaInfo)
      • Description: Contains detailed media information for video content, aiding in its analysis and categorization.
      • SEO Purpose: Accurate media information improves the indexing and retrieval of video content, enhancing its discoverability.
      • How to Use: Ensure all relevant media information is included in your video content to improve its search engine visibility and relevance.
2665. Video Media Overview (VideoMediaOverview)
      • Description: Provides an overview of media streams, including audio, video, and data streams, with no personally identifiable information (PII).
      • SEO Purpose: A comprehensive media overview ensures better indexing and retrieval of video content.
      • How to Use: Include a detailed media overview for your videos to improve indexing and enhance search engine performance.
2666. Per-Doc Data (VideoPerDocData)
      • Description: Contains core signals and frames data for video content, aiding in detailed analysis and categorization.
      • SEO Purpose: Detailed per-doc data improves the accuracy and relevance of video content indexing.
      • How to Use: Ensure your video content includes comprehensive per-doc data to enhance its search engine visibility and relevance.
2667. Thumbnailer Column Data (VideoPipelineViperThumbnailerColumnData)
      • Description: Contains data related to video thumbnails, including frame references and generation details.
      • SEO Purpose: Accurate thumbnail data improves the visual representation and click-through rates of video content in search results.
      • How to Use: Ensure high-quality thumbnails are generated for your videos and include detailed metadata to enhance search visibility and user engagement.
2668. VSI Column Data (VideoPipelineViperVSIColumnData)
      • Description: Contains data related to video stream information (VSI), including read time and VSI statistics.
      • SEO Purpose: Detailed VSI data improves the analysis and indexing of video content, enhancing its relevance in search results.
      • How to Use: Include comprehensive VSI data for your video content to improve its indexing and search engine performance.
2669. Rational Data (VideoRational32)
      • Description: Represents rational numbers using a numerator and denominator, aiding in precise video data calculations.
      • SEO Purpose: Precise numerical data ensures accurate analysis and representation of video content.
      • How to Use: Use rational data to provide accurate numerical information for your videos, enhancing their analysis and indexing.
2670. SEI Message (VideoSEIMessage)
      • Description: Contains information about SEI messages, including payload type and size, used for video data analysis.
      • SEO Purpose: Accurate SEI data improves the quality and relevance of video content analysis.
      • How to Use: Include detailed SEI messages in your video content to enhance its analysis and indexing.
2671. Loudness Data (VideoStorageLoudnessData)
      • Description: Provides measurements of loudness in video content, aiding in audio analysis and optimization.
      • SEO Purpose: Accurate loudness data ensures high-quality audio playback, improving user experience and engagement.
      • How to Use: Ensure your videos include detailed loudness data to optimize audio quality and enhance user satisfaction.
2672. Frame File (VideoThumbnailsFrameFile)
      • Description: Contains individual video frames saved as image files, used for thumbnail generation and analysis.
      • SEO Purpose: High-quality frame files improve the visual representation of video content, enhancing click-through rates and engagement.
      • How to Use: Generate and include high-quality frame files for your video thumbnails to improve their visual appeal and search engine visibility.
2673. Frame File List (VideoThumbnailsFrameFileList)
      • Description: Lists individual video frames, each saved as an image file, aiding in comprehensive thumbnail generation.
      • SEO Purpose: A detailed list of frame files ensures better thumbnail generation and visual representation of video content.
      • How to Use: Maintain a comprehensive list of frame files for your videos to ensure high-quality thumbnail generation and improved search performance.
2674. Thumbnail Score (VideoThumbnailsThumbnailScore)
      • Description: Contains scores calculated from video thumbnails, aiding in the evaluation of their quality and relevance.
      • SEO Purpose: High thumbnail scores improve the visual appeal and click-through rates of video content in search results.
      • How to Use: Regularly evaluate and optimize the scores of your video thumbnails to enhance their visual quality and search engine performance.
2675. Timed Text Results (VideoTimedtextS4ALIResults)
      • Description: Provides results for automatic language identification (ALI) in timed text streams, including language scores and speech classification.
      • SEO Purpose: Accurate ALI results ensure better indexing and retrieval of video content based on language.
      • How to Use: Include detailed ALI results for your timed text streams to improve language-based indexing and search performance.
2676. Language Score (VideoTimedtextS4LangScore)
      • Description: Contains scores for identified languages in video content, aiding in language analysis and optimization.
      • SEO Purpose: Accurate language scores improve the relevance and indexing of video content based on language.
      • How to Use: Ensure your videos include detailed language scores to enhance their indexing and retrieval based on language.
2677. Registered ITU-T T.35 User Data (VideoUserDataRegisteredItuTT35)
      • Description: Contains user data registered under the ITU-T T.35 standard, used for video data analysis.
      • SEO Purpose: Accurate user data registration ensures better analysis and representation of video content.
      • How to Use: Include detailed ITU-T T.35 user data in your videos to enhance their analysis and indexing.
2678. Unregistered User Data (VideoUserDataUnregistered)
      • Description: Contains unregistered user data identified by a UUID, aiding in detailed video data analysis.
      • SEO Purpose: Detailed unregistered user data improves the analysis and representation of video content.
      • How to Use: Ensure your videos include comprehensive unregistered user data to enhance their analysis and indexing.
2679. Video Clip Info (VideoVideoClipInfo)
      • Description: Contains meta information extracted from video files, aiding in detailed analysis and categorization.
      • SEO Purpose: Accurate video clip information improves the indexing and retrieval of video content.
      • How to Use: Include detailed meta information for your video clips to enhance their search engine visibility and relevance.
2680. Video Geo-Location (VideoVideoGeoLocation)
      • Description: Contains generic geo-location information for video content, aiding in location-based indexing and retrieval.
      • SEO Purpose: Accurate geo-location data improves the relevance and discoverability of video content based on location.
      • How to Use: Include detailed geo-location information for your videos to enhance their location-based indexing and search performance.
2681. Video Stream (VideoVideoStream)
      • Description: Provides detailed information about video streams, including bitrate, codec, FPS, dimensions, and more.
      • SEO Purpose: Comprehensive video stream data ensures better indexing and retrieval of video content based on technical specifications.
      • How to Use: Ensure your videos include detailed stream information to enhance their indexing and improve search engine performance.
2682. Video Stream Information (VideoVideoStreamInfo)
      • Description: Provides detailed information about video streams, including lengths, frame rates (FPS), and other attributes. This information reflects the source video but may not match transcode details if the source information is incomplete or incorrect.
      • SEO Purpose: Ensures accurate indexing and playback quality of video content by providing detailed technical data about the video stream.
      • How to Use: Include comprehensive video stream information to enhance the accuracy and quality of video content indexing, leading to better search engine performance and user experience.
2683. Audio Stream Information (VideoVideoStreamInfoAudioStream)
      • Description: Provides detailed information about audio streams within the video, including codec and bitrate details.
      • SEO Purpose: Enhances the indexing and quality assessment of video content based on its audio attributes.
      • How to Use: Ensure that your video metadata includes detailed audio stream information to improve search engine indexing and playback quality.
2684. Data Stream Information (VideoVideoStreamInfoDataStream)
      • Description: Refers to additional data streams separate from audio and video streams, such as camera motion metadata.
      • SEO Purpose: Allows for the inclusion of supplementary data that can enhance the indexing and usability of video content.
      • How to Use: Incorporate data stream information to provide a complete picture of the video content, aiding in better indexing and user experience.
2685. Metadata (VideoVideoStreamInfoMetadata)
      • Description: Contains metadata for the video stream, including lookup tables (LUTs) and frame packing arrangement.
      • SEO Purpose: Provides essential technical details that can improve video processing and display quality.
      • How to Use: Include detailed metadata to enhance the quality and accuracy of video content representation in search results.
2686. Timed Text Stream (VideoVideoStreamInfoTimedTextStream)
      • Description: Refers to streams of text that are separate from audio and video, such as closed captions not embedded in the video stream.
      • SEO Purpose: Improves accessibility and usability of video content by providing text streams for indexing.
      • How to Use: Ensure your video content includes timed text streams to enhance accessibility and improve indexing for search engines.
2687. Video Stream Clean Aperture (VideoVideoStreamInfoVideoStreamCleanAperture)
      • Description: Provides details about the clean aperture of the video stream, including height, width, and horizontal and vertical offsets.
      • SEO Purpose: Ensures accurate cropping and display of video content, improving visual quality.
      • How to Use: Include clean aperture details in your video metadata to ensure proper cropping and high-quality display.
2688. Video Stream Statistics (VideoVideoStreamInfoVideoStreamStatistics)
      • Description: Provides statistical data about the video stream, including maximum, mean, and minimum values for various attributes.
      • SEO Purpose: Offers detailed insights into video quality and performance, aiding in better indexing and quality assessment.
      • How to Use: Incorporate video stream statistics to provide a comprehensive view of video quality, enhancing search engine indexing and user experience.
2689. Smart Suggestion (VideoYoutubeCommentsClassificationProtoSmartSuggestion)
      • Description: Contains smart reply suggestions for YouTube comments, including diversification thresholds, bias weights, reply content, and model scores.
      • SEO Purpose: Enhances user engagement and interaction by providing relevant and high-quality comment suggestions.
      • How to Use: Implement smart suggestion data to improve the relevance and quality of automated comment replies, boosting user engagement and satisfaction.
2690. Smart Reply (VideoYoutubeCommentsClassificationProtoYouTubeCommentSmartReply)
      • Description: Provides smart reply suggestions for YouTube comments.
      • SEO Purpose: Improves user interaction and engagement by offering relevant and timely reply suggestions.
      • How to Use: Utilize smart reply suggestions to enhance user interaction in the comment section, increasing engagement and satisfaction.
2691. Comment Ranking Metrics (VideoYoutubeCommentsRankingCTRMetrics)
      • Description: Contains metrics for ranking comments based on click-through rates (CTR).
      • SEO Purpose: Helps in prioritizing comments that are more likely to engage users, improving user interaction.
      • How to Use: Use CTR metrics to rank comments effectively, enhancing user engagement and the overall commenting experience.
2692. Per-Document Information (WWWDocInfo)
      • Description: Contains specific information returned for all document info requests.
      • SEO Purpose: Provides detailed per-document data that aids in accurate indexing and retrieval.
      • How to Use: Include comprehensive per-document information to improve the accuracy and relevance of search engine indexing.
2693. Related Images (WWWDocInfoRelatedImages)
      • Description: Returns related images for the document.
      • SEO Purpose: Enhances visual search results and user engagement by providing relevant images.
      • How to Use: Ensure that related images are included in your content to improve visual search indexing and engagement.
2694. Thumbnail Information (WWWDocInfoThumbnail)
      • Description: Contains details about document thumbnails, including expiration timestamp, dimensions, and type.
      • SEO Purpose: Enhances the visual representation and click-through rates of content in search results.
      • How to Use: Include detailed thumbnail information to improve the visual appeal and click-through rates of your content in search results.
2695. Meta Tags (WWWMetaTag)
      • Description: Returns content attributes for some or all meta tags in a document.
      • SEO Purpose: Improves search engine indexing and relevance by providing detailed meta tag information.
      • How to Use: Ensure that all relevant meta tags are included and detailed to enhance search engine indexing and relevance.
2696. Sub Image Document Information (WWWResultInfoSubImageDocInfo)
      • Description: Contains information about sub image documents, used for boosting web image search results.
      • SEO Purpose: Enhances the relevance and quality of image search results by providing detailed sub image information.
      • How to Use: Include sub image document information to improve the relevance and quality of image search results.
2697. Snippet Response (WWWSnippetResponse)
      • Description: Provides a per-document response for a document info request, including encoded bitmap information.
      • SEO Purpose: Improves search result snippets’ relevance and visual quality, enhancing user engagement.
      • How to Use: Ensure detailed snippet responses are included for each document to improve search result relevance and engagement.
2698. Watch Page Language Predictions (WatchpageLanguageWatchPageLanguageModelPredictions)
      • Description: Contains language model predictions for watch pages, including language scores.
      • SEO Purpose: Enhances the accuracy of language detection and indexing, improving search relevance.
      • How to Use: Include detailed language predictions to ensure accurate language detection and indexing, improving search relevance.
2699. Live Result Document Boost (WeboftrustLiveResultDocBoostData)
      • Description: Indicates that a document has a reliable live result feed that warrants potential ranking boosts.
      • SEO Purpose: Improves the visibility and ranking of documents with reliable live result feeds.
      • How to Use: Ensure that live result feeds are reliable to boost document ranking and visibility in search results.
2700. Live Result Provider Attachment (WeboftrustLiveResultProviderDocAttachment)
      • Description: Identifies pages for which live result triggering should appear based on provider-specific criteria.
      • SEO Purpose: Enhances the relevance and accuracy of live result triggers, improving user experience.
      • How to Use: Attach provider-specific criteria to documents to ensure accurate and relevant live result triggers.
2701. Time Range (WeboftrustTimeRange)
      • Description: Specifies the time range during which a live result is considered “hot” and potentially boosts document rank.
      • SEO Purpose: Improves the timeliness and relevance of live results, enhancing user engagement.
      • How to Use: Include accurate time ranges for live results to ensure timely and relevant document boosting, improving user engagement.
2702. Safe HTML (WebutilHtmlTypesSafeHtmlProto)
      • Description: Contains HTML content that is safe to display, preventing the inclusion of potentially harmful scripts.
      • SEO Purpose: Ensures the safety and integrity of displayed HTML content, improving user trust.
      • How to Use: Use safe HTML content to prevent security risks and enhance user trust and experience.
2703. Fetch Metadata (WirelessTranscoderFetchFetchMetadata)
      • Description: Contains metadata about the fetch request, including name and value pairs.
      • SEO Purpose: Provides detailed information about fetch requests, aiding in better indexing and retrieval.
      • How to Use: Include detailed fetch metadata to improve the accuracy and efficiency of fetch request indexing and retrieval.
2704. Fetch Source Information (WirelessTranscoderFetchFetchSourceInfo)
      • Description: Tags which fetcher satisfied the fetch request with optional details.
      • SEO Purpose: Enhances the traceability and accountability of fetch requests, improving reliability.
      • How to Use: Include detailed fetch source information to improve the traceability and reliability of fetch requests.
2705. Super VOD Comment Information (YoutubeBackstageSuperVodCommentInfo)
      • Description: Contains information about comments posted through Super Thanks purchases on YouTube.
      • SEO Purpose: Enhances the engagement and monetization of video content through Super Thanks comments.
      • How to Use: Include Super VOD comment information to leverage Super Thanks purchases, boosting engagement and monetization.
2706. Comment Enforcement Status (YoutubeCommentsApiCommentEnforcementStatus)
      • Description: Encapsulates the possible enforcement states of a comment, influencing the viewer experience.
      • SEO Purpose: Ensures appropriate moderation and display of comments, improving user experience and community standards.
      • How to Use: Implement comment enforcement statuses to manage and moderate comments effectively, enhancing user experience.
2707. Comment Moderated Restriction (YoutubeCommentsApiCommentModeratedRestriction)
      • Description: Represents a comment moderated restriction, hiding the comment from viewers except the author.
      • SEO Purpose: Ensures effective moderation of comments, maintaining community standards and user experience.
      • How to Use: Apply moderated restrictions to manage inappropriate comments, improving community standards and user experience.
2708. Smart Suggestion for Comments (YoutubeCommentsClusteringMiniStanza)
      • Description: Provides smart suggestions for comments to enhance interaction and engagement.
      • SEO Purpose: Boosts user engagement by providing relevant and high-quality comment suggestions.
      • How to Use: Implement smart suggestions for comments to improve user interaction and engagement on your platform.
2709. Comment Text Embedding (YoutubeCommentsRankingYouTubeCommentTextEmbedding)
      • Description: Contains text embedding for comments to analyze and rank comment quality.
      • SEO Purpose: Enhances the relevance and quality assessment of comments, improving user engagement.
      • How to Use: Include comment text embeddings to analyze and rank comments effectively, boosting user engagement.
2710. Text Quality Annotation (YoutubeCommentsRankingYouTubeCommentTextQualityAnnotation)
      • Description: Provides text quality scores for individual comments, aiding in quality assessment and ranking.
      • SEO Purpose: Ensures high-quality comments are highlighted, improving the overall quality of interactions.
      • How to Use: Use text quality annotations to rank and highlight high-quality comments, enhancing user engagement.
2711. Sentiment Analysis (YoutubeCommentsSentimentSentiment)
      • Description: Extracts sentiment information from annotated content, providing sentiment analysis for comments.
      • SEO Purpose: Enhances understanding of user sentiment, improving content and community management.
      • How to Use: Implement sentiment analysis to understand user sentiment and manage content effectively, improving user experience.
2712. Entity Sentiment Annotation (YoutubeCommentsSentimentSentimentEntitySentimentAnnotation)
      • Description: Aggregates sentiment values for all mentions of an entity within a comment. This annotation helps understand the overall sentiment expressed towards specific entities.
      • SEO Purpose: Enhances sentiment analysis by providing aggregated sentiment data for entities, allowing for better understanding of user emotions and improving content relevance.
      • How to Use: Use entity sentiment annotations to gauge overall sentiment towards specific entities in comments, aiding in content and user engagement strategies.
2713. Mention Sentiment Annotation (YoutubeCommentsSentimentSentimentEntitySentimentAnnotationMentionSentimentAnnotation)
      • Description: Provides sentiment values for individual mentions of an entity within a comment. This helps in understanding the sentiment of each mention.
      • SEO Purpose: Improves sentiment analysis by offering detailed sentiment data for each entity mention, leading to more precise content evaluation.
      • How to Use: Utilize mention sentiment annotations to analyze individual mentions of entities in comments, helping to refine sentiment analysis and content strategy.
2714. Document Annotation (YoutubeDiscoveryLegosLegosAnnotation)
      • Description: Annotates a document based on a given entity and relationship type. This provides contextual information about the document’s content.
      • SEO Purpose: Enhances content relevance and discoverability by providing detailed annotations, aiding in better indexing and search results.
      • How to Use: Include document annotations to provide search engines with contextual information about your content, improving its relevance and visibility.
2715. Collection of Annotations (YoutubeDiscoveryLegosLegosAnnotations)
      • Description: A collection of annotations for a document, returned by Legos. This consolidates multiple annotations, providing comprehensive data about the document.
      • SEO Purpose: Boosts content relevance and search engine performance by offering a complete set of annotations, improving indexing accuracy.
      • How to Use: Use collections of annotations to provide a thorough context for your content, enhancing its indexing and search result rankings.
2716. Knowledge Graph Entity (YoutubeDiscoveryLegosLegosEntity)
      • Description: Identifies a Knowledge Graph (KG) entity within Legos, linking the document to a known entity.
      • SEO Purpose: Increases content authority and relevance by associating it with recognized entities in the Knowledge Graph.
      • How to Use: Ensure your content is linked to relevant Knowledge Graph entities to improve its authority and relevance in search results.
2717. Format Relationship Annotation (YoutubeDiscoveryLegosLegosFormatRelationship)
      • Description: Describes the relationship format of a Legos annotation, providing information on how the entity relates to the document.
      • SEO Purpose: Enhances content structure and understanding by detailing the relationship format, aiding in better search engine comprehension.
      • How to Use: Implement format relationship annotations to clarify how entities relate to your content, improving search engine understanding and indexing.
2718. Present Relationship Annotation (YoutubeDiscoveryLegosLegosPresentRelationship)
      • Description: Describes a present relationship annotation in Legos, detailing the current state of the entity’s relation to the document.
      • SEO Purpose: Improves content relevance and indexing by providing up-to-date relationship information.
      • How to Use: Use present relationship annotations to offer current context about entity relationships in your content, enhancing its relevance and search visibility.
2719. Semantic Relationship Annotation (YoutubeDiscoveryLegosLegosSemanticRelationship)
      • Description: Describes a semantic relationship annotation in Legos, providing detailed semantic context about the entity’s relation to the document.
      • SEO Purpose: Boosts content relevance and understanding by offering semantic context, aiding in better indexing and search results.
      • How to Use: Include semantic relationship annotations to provide detailed semantic context about entities in your content, improving its relevance and search engine performance.
2720. Semantic Relationship Context (YoutubeDiscoveryLegosLegosSemanticRelationshipContext)
      • Description: Provides extra context about how the entity relates to the document, often including vertical-specific details.
      • SEO Purpose: Enhances the relevance and depth of content by offering additional context about entity relationships.
      • How to Use: Use semantic relationship context to provide in-depth details about entity relationships in your content, improving its depth and relevance.
2721. Taxonomic Relationship Annotation (YoutubeDiscoveryLegosLegosTaxonomicRelationship)
      • Description: Describes a taxonomic relationship annotation in Legos, detailing hierarchical relationships between entities and the document.
      • SEO Purpose: Improves content organization and relevance by detailing taxonomic relationships, aiding in better indexing and search results.
      • How to Use: Implement taxonomic relationship annotations to clarify hierarchical relationships in your content, enhancing its organization and search engine performance.