Dynamic page information and metadata
On this page
StoreConnect generates the metadata in the <head> of every storefront page for you: the page title, the description and keywords, the canonical URL, and the Open Graph tags that social platforms and search engines read. Use this topic to work out which record supplies those values on a given page, and which field to fill in to change them.
You do not add these tags to your theme. They are generated on every page render.
How StoreConnect chooses the source record
Metadata comes from the most specific record on the page. StoreConnect checks in this order and uses the first match:
- Product
- Product Category
- Article
- Article Category
- Page (any page other than the home page)
- The home Page
- Location
- Location Group
- Search results
- Store
The Store supplies the metadata only when none of the others are present, so store-level values act as the fallback for the whole site.
What is generated
| Tag | Value |
|---|---|
<title> |
The title for the source record |
<meta name="keywords"> |
The keywords for the source record |
<meta name="description"> |
The description for the source record |
<meta property="og:type"> |
article on an article, page on a page, location, or location group, otherwise website |
<meta property="og:title"> |
Same value as <title> |
<meta property="og:description"> |
Same value as the description |
<meta property="og:url"> |
The canonical URL of the current request |
<meta property="og:locale"> |
The store’s locale |
<meta property="og:image"> |
The social image for the source record, at huge size (1024px). Omitted when there is no image. |
<meta property="og:price:amount"> |
The product price. Products only, omitted elsewhere. |
<meta property="og:price:currency"> |
The store’s currency code. Products only. |
<meta name="sc-path"> |
The store’s path |
<meta name="sc-type"> |
The search type. Search result pages only. |
<link rel="canonical"> |
The canonical URL of the current request |
On page 2 and beyond of a paginated listing, the page number is appended to the title through the pagination.paged_title translation key.
Where each value comes from
Each value follows a fallback chain, so a blank Meta Title does not produce an empty tag. The first field with a value wins.
| Source record | Title | Keywords | Description |
|---|---|---|---|
| Product | Meta Title, then Display Name, then Name, then the store title | Meta Keywords, then the words of Meta Title | Meta Description, then Search Description, then Summary, then brand plus product name |
| Product Category | Meta Title, then Display Name, then Title, then the store title | Meta Keywords, then the words of the title | Meta Description, then Introduction, then Information, then the store description |
| Article | Meta Title, then Title, then Name, then the store title | Meta Keywords, then the words of the title, then the store keywords | Meta Description, then Intro, then Summary, then the store description |
| Article Category | Meta Title, then Display Name, then Name, then the store title | Meta Keywords, then the words of the title | Meta Description, then the store description |
| Store | Meta Title, then Name | Meta Keywords, then the words of Meta Title | Meta Description |
Where a description falls back to a markdown field, the markdown is stripped to plain text first.
The Social Image field supplies og:image. When it is blank, StoreConnect falls back to the record’s own image: the product image, the category image, the article hero image, or the store logo.
Set the metadata for a record
- Open the record whose metadata you want to change, such as a Product or a Page.
- Set Meta Title, Meta Description, and Meta Keywords.
- Set Social Image if you want a specific image for social shares rather than the record’s default image.
- Click Save.
To bulk-edit metadata across many records, the fields are s_c__Meta_Title__c, s_c__Meta_Description__c, and s_c__Meta_Keywords__c on Product (Product2), Product Category (s_c__Product_Category__c), Article (s_c__Article__c), Page (s_c__Page__c), and Store (s_c__Store__c), all editable through Data Loader or the API.
Verify the metadata on a page
Open the page on your storefront and view the page source. The <title>, <link rel="canonical">, and og: tags in the <head> show the values from the record you edited. If they show store-level values instead, the more specific record has no value in that field and the chain has fallen through to the Store.
Was this article helpful?
Thanks for your feedback! It helps us improve our docs.