SEO Best Practices and Considerations for Guest Users

Experience Builder Sites

You identify the standard and custom, but not chatter, objects available for SEO using the Experience Builder guest user profile. Objects and associated fields assigned read access are added to the sitemap.

• To control the scope of your sitemap and help keep your site secure, regularly review which objects are public and the number of records exposed for each object. From Experience Builder, go to Settings | SEO | Object Access list. It can take up to 24 hours for the Object Access list to be refreshed and include object pages and records newly made public.
  
• Even though an object and its fields are public, Salesforce security settings still determine guest user access to this data. To ensure that object data is available to search engines, review the sharing rules, field-level security (FLS), and permission sets assigned to that object.
• Make sure that all sensitive objects are private, even the objects used in private pages not included in the sitemap. All public pages and public objects are discoverable because search engines use the sitemap only as a starting point to identify which site content is available for crawling.
• If you enable guest user access for an object that has existing records, manually trigger the full sitemap generation. Otherwise, the sitemap doesn’t include the object’s records until the next automatic sitemap regeneration, which can be up to a week later.

Salesforce Tabs + Visualforce Sites

• In your sitemap, include only publicly accessible Visualforce pages and objects that you want discoverable by search engines.
• Use robots.txt for more control over which data is available for search engines to index when they crawl your site.
• Submit your sitemap to search engines, such as Google Search Console, only after completing the previous steps.