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.

 

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.