Search in Aura and LWR sites
What site search returns and how to configure it: site-scoped, sharing-aware results; Global Search Box and Global Search Results tabs on Aura sites; guest autocomplete; header versus hero search; LWR Search Bar and Results Layout with CMS content and CRM object sources and index rebuilds; and why internal global search misses site users.
Explain the capabilities of Search within an Experience.
~7 min read · 9 practice questions ·
What the exam expects
- Explain what site search returns: results from the current site only, limited to what is shared with the member in the site context.
- Add an object, including an external object, as a result tab in an Aura site's Global Search Results component.
- Turn on autocomplete suggestions for guest users, and remove a duplicate search box when a prebuilt theme's hero has search.
- Set up LWR search with the Search Bar and Results Layout components, choose CMS Content or CRM Object as the source, and rebuild the index after publishing content.
- Explain why search configuration never limits guest record access, and why internal global search misses some site users.
Key terms: Global Search Results (the Aura component on the Search page that sets which objects appear as result tabs); autocomplete (suggestions shown while typing, which guests get only for object types marked Publicly available); Results Layout (the LWR component that shows results on a standard Search page); results source (CMS Content or CRM Object for Results Layout); network ID (the unique ID each site has, assigned to users created from a contact).
Key facts
- Detail
- Results come only from the current site
- Detail
- Members see data explicitly shared with them in the site context
- Detail
- Global Search Results on the Search page, Add an item per object
- Detail
- Can be a result tab; autocomplete isn't supported
- Detail
- Autocomplete section, object, Publicly available
- Detail
- Not limited to the objects configured in search components
- Detail
- Deselect header search to avoid two boxes
- Detail
- Results Layout only on a standard Search page
- Detail
- Rebuild Index in Settings, Search after publishing fresh content
- Detail
- Search Manager query configuration, LWR Experience Sites
- Detail
- Network ID of the site keeps them out of internal results
Sources for this section (8)
- Configure Search Functionalityhelp.salesforce.com (opens in a new tab)
- Enable the Objecthelp.salesforce.com (opens in a new tab)
- Guest Autocompletehelp.salesforce.com (opens in a new tab)
- Search Best Practices for Guest Usershelp.salesforce.com (opens in a new tab)
- Theme Guidance: Search Componenthelp.salesforce.com (opens in a new tab)
- Allow Users to Search LWR Siteshelp.salesforce.com (opens in a new tab)
- CMS Content Searchhelp.salesforce.com (opens in a new tab)
- Customize Search in Experience Cloud Siteshelp.salesforce.com (opens in a new tab)
- Why doesn't hiding objects from Global Search Results protect them from guests?
- When must a site manager click Rebuild Index on an LWR site?
- Why can't an internal admin find a site user created from a contact with global search?
- Which page must exist before Results Layout can show results?
- What should you change when a prebuilt theme shows search in both the hero and the header?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Experience Cloud Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 37 lessons of the Experience Cloud Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams