The largest channel for discovering content for the Experience Cloud is organic search from external search engines, primarily Google. To help improve content discovery for customers, content presented on pages requires optimizing for the indexers to easily catalog what a page is about.
Initially this is a straighforward process, giving basic information, but can become more nuanced the more specifically you want to tune pages.
External search engines require several elements to be available for good quality indexing.
SCCM automatically takes care of page syntax, sitemaps, and structure. As writers, the SCCM process relies on you adding the information to this structure.
Our internal search engine does not create a full-page index at this time. Instead, our internal search indexes the following:
description metadata is especially important to improve internal search. Try to include likely search terms and synonyms in your descriptions.
Our internal search also indexes the following metadata that allows users to filter their search results:
For more information which values to specify for these search filters, see Metadata.
SCCM stores metadata in 3 places.
metadata.md file located at the root of your content guide is much like a birth certificate, with basic information that is applied to all pages in the material set. You will set this up with the SCCM when you create a new content set. You shouldn’t need to edit this again.
TOC.md file. This provides every page with metadata about which solution or sub solution this content relates to, as well as audience type etc. This is generally only changed if a solution name changes.
On your content pages. The content pages need only these fields completed:
Please note we are deprecating the
seo-description fields. We included these fields in the migration to be in line with chl-author (helpx). You can remove or ignore the
seo-description fields. Google uses the regular
Useful tips about tuning your pages for search.
description metadata on your page. (Note that
seo-description are deprecated. )
Google pays attention to title, description, and keyword metadata. You’ll get even better results if the metadata closely matches words on the page.
Add the solution name to your metadata, especially for articles that could apply to different products from different companies.
Include previous product names (
SiteCatalyst) in your description if relevant. Many of our customers still use previous product names when searching and it’s useful to match them up.
Google has the ability to change the title of a page in the results and construct it from meta, page content and titles, if it thinks it is a closer/more helpful result. So we may see some results change, and have no match to any one field. The more accurate we are, the less that should happen, but it’s possible. We have seen a few examples where we can’t explain where a title word came from. That is Google ‘adjusting a title for accuracy’.
If search entries match content in the title or first paragraph, the page will likely appear much higher in the list of search results. Use key search terms early and as often as possible (without being contrived or repetitious) in these places:
Sample first paragraph in an overview:
Audiences are collections of visitors (a list of visitor IDs). Adobe's audience service manages the translation of visitor data into audience segmentation. As such, creating and managing audiences is similar to creating and using segments, with the added ability to share the audience segment to the Experience Cloud.
Sample first paragraph in a task:
Create the customer attribute source (CSV and FIN files) and upload the data. You can activate the data source when you are ready. After the data source is active, share the attribute data to Analytics and Target.