---
schema_version: "1"
id: 426ad4267ec063b48bc81e4234f5ffabe7aca65c4b36a3eca87d21860109dce1
title: Set Up Your Experience Builder Site for SEO
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/experience/264-0-0/networks_seo_setup.md
canonical_url: https://help.salesforce.com/s/articleView?id=experience.networks_seo_setup.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 32de878b866f4fa729b1385a30647e4e54a0c352c4a763f9dc6db1417dcbbbe6
description: Setting up SEO for your Experience Builder site includes a series of tasks that you perform in Salesforce and in the site. From identifying your preferred domain to determining which objects to make public, we’ve got you covered.
products:
  - Experiences
release: "264"
---
# Set Up Your Experience Builder Site for SEO

Setting up SEO for your Experience Builder site includes a series of tasks that you perform in Salesforce and in the site. From identifying your preferred domain to determining which objects to make public, we’ve got you covered.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong> Editions</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Applies to: <a href="https://help.salesforce.com/s/articleView?id=experience.exp_cloud_basics_glossary.htm&amp;release=264.0.0&amp;type=5">LWR and Aura sites</a></td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d98951e76">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d98951e76 ">To customize or publish an Experience Cloud site:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d98951e76 ">
              <ul>
                <li>Create and Set Up Experiences AND View Setup and Configuration AND be a member
                  of the site<p>OR</p>
                </li>

                <li>View Setup and Configuration AND be a member of the site AND have appropriate
                  <a href="https://help.salesforce.com/s/articleView?id=experience.networks_access_control_overview.htm&amp;language=en_US" target="_blank">role-based site access</a>
                </li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

Here’s an overview of the main steps to set up SEO for your site on a production org.

1. If you have multiple domains, [identify your preferred domain](https://help.salesforce.com/s/articleView?id=experience.networks_seo_preferred_domain.htm&release=264.0.0&type=5 "By default, your site is available on the *.my.site.com or *.force.com domain, but you can add a custom domain so that your site URLs reflect your company brand. However, multiple domains for the same site, meaning *.my.site.com, *.force.com, and custom domains, can dilute search engine results and lower page ranking. If you have multiple domains, identify which domain to use for crawling and indexing your site’s pages.").
    
    For an enhanced LWR site or for an Aura or LWR site without an identified preferred domain, the site’s first custom domain alphabetically is the preferred domain.
    
    ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/images/icon_tip.png)
    
    Tip Identify your preferred domain before you make your site public. If the site is made public without a preferred domain, the \*.force.com or \*.my.site.com URLs are also indexed, and removing them from search results can take time.
2. [Make your site public](https://help.salesforce.com/s/articleView?id=platform.community_builder_page_access_settings.htm&type=5&language=en_US).
    
    The SEO settings tab in Experience Builder is available only if your site is public.
    
    When you make your site or specific pages public, search engines can then index those public pages. However, if you don’t want unauthenticated visitors or search engines accessing certain pages, you can make those pages private. Also, more granular indexing control is available at the object and field levels.
3. To improve search results, [specify the SEO properties for individual pages](https://help.salesforce.com/s/articleView?id=experience.networks_seo_tags.htm&release=264.0.0&type=5 "Set the title, description, and head properties for your Experience Builder site pages to improve search results.").
    
    These SEO properties are for the title and description that appear in the search results of indexed pages, and to prevent a page from being indexed.
4. Optionally, for a rules-based approach, [create a custom robots.txt file](https://help.salesforce.com/s/articleView?id=experience.networks_seo_configure.htm&release=264.0.0&type=5 "The robots.txt file for your site is automatically generated. It allows search engines to crawl your entire site. However, if you want to tell search engines not to crawl certain pages of your public site, you can create a custom robots.txt file.") to control the indexing of specific areas of your site.
5. If you want the information stored in objects accessible to search engines, [make objects and their associated fields readable](https://help.salesforce.com/s/articleView?id=experience.networks_seo_object_access.htm&release=264.0.0&type=5 "When you make your site public, search engines can index the pages of your Experience Builder site. However, to ensure that you don't expose sensitive data, the data displayed by objects on those pages aren’t public. Instead, you must specifically make those objects and their associated fields publicly available for indexing by search engines.").
6. Optionally, [enable generative engine optimization (GEO)](https://help.salesforce.com/s/articleView?id=experience.networks_seo_geo.htm&release=264.0.0&type=5 "To make public site pages more discoverable by AI-powered search engines and enhance the precision of generated answers, enable generative engine optimization (GEO) in Experience Builder. When you enable GEO, AI bots can request content snapshots of your site’s pages to generate answers more effectively.") to make pages more discoverable by AI-powered search engines.
    
    When you enable GEO, AI bots can request content snapshots of your site’s pages to generate answers more effectively.
7. [Activate your site](https://help.salesforce.com/s/articleView?id=experience.networks_publish.htm&release=264.0.0&type=5 "Activate your site to make it accessible to members. The result of activation differs depending on whether you have a Salesforce Tabs + Visualforce site or a Lightning site.") to successfully implement SEO.
    
    Before activating your site, check the guest user profile to ensure that the correct objects have read access. This best practice controls the scope of your sitemap.xml file and keeps your site secure.
8. To make your changes live, publish your site.
9. If you’re setting up SEO for the first time, or as needed, [generate a manual sitemap refresh](https://help.salesforce.com/s/articleView?id=experience.networks_manual_SEO_sitemap.htm&release=264.0.0&type=5 "When you go live with a new Experience Builder site or make significant updates to an existing one, you can generate a manual sitemap one time every 24 hours outside of the weekly automatic sitemap refresh.").
    
    The sitemap is automatically regenerated every Sunday. An automatic partial sitemap refresh that picks up incremental changes occurs every 24 hours. You can also generate a manual sitemap refresh one time every 24 hours if needed.
10. If necessary, [provide search engines with fresh content snapshots](https://help.salesforce.com/s/articleView?id=experience.networks_seo_snapshot.htm&release=264.0.0&type=5 "Experience Builder sites in your production org use the Content Snapshot service to generate SEO optimized HTML for web crawlers such as Googlebot, and content sharing platforms such as Facebook. The concept is common to single-page application frameworks known as dynamic rendering. Salesforce takes a snapshot when you make changes to your site’s publicly available content. This functionality works well for most updates. But let’s say you update a page with time-sensitive information, such as price changes for a flash sale. Instead of waiting, you can take a manual snapshot once every 24 hours to refresh the page content served to search engines.").
    
    Salesforce takes a snapshot when you make changes to your site’s publicly available content. This functionality works well for most updates. But if you update a page with time-sensitive content and don’t see your changes in search results right away, you can take a manual snapshot one time every 24 hours. When you take a manual snapshot, you refresh the page content served to search engines.