seopagedesc input file
Use a seopagedesc input file to load the following language-specific search engine optimization (SEO) properties for a content page: page title, meta description, and meta keyword.This input file supports loading the SEO properties in a single language or multiple languages. Include each language in a separate row. Tip: We can use the <seo:StoreName/> and <seo:StoreDescription/> substitution variables in the SEO property values. For more information, see Substitution parameters for Search Engine Optimization (SEO). For samples that demonstrate how to use this input file in different load scenarios, see:
- Sample: Loading Commerce Composer page SEO information in multiple languages
- Sample: Loading Commerce Composer pages
We can extract SEO descriptive information for pages with the Data Extract utility to create a seopage.csv file that we can load with the Data Load utility. For example, to copy or move Commerce Composer pages between stores or instances, such as for creating one or more test environments. The sample configuration files provided for you to use with the Data Extract utility, extract page SEO descriptive information data from the following database tables:
For more information about extracting Commerce Composer data, see:
- Extracting Commerce Composer data with the Data Extract utility
- Sample: Extracting Commerce Composer pages
Definitions
- PageGroup
- (String) The page group that the page belongs to. The page group for the page is defined in the page input file. Use the value Content.
Maps to: PLPAGE.PAGELAYOUTTYPE_ID
- PageUniqueID
- (Integer) The internal reference number for the content page, for example, 60001. In Delete mode, either this field or the PageAdminName field (see next column) is required.
Note: The sample CSV file does not include this column; the sample demonstrates the use of the PageAdminName to uniquely identify the page.
Maps to: PLPAGE.PLPAGE_ID
- PageAdminName
- (String) The name of the content page, for example, HomePage or HelpPage. ThePageAdminName is defined in the page input file. This name is displayed in the Commerce Composer tool to help business users identify the page. In Insert or Replace mode, this field cannot be null and the name must be unique. In Delete mode, either this field or the PageUniqueID field (see previous column) is required.
Maps to: PLPAGE.ADMINNAME
- PageTitle
- (String) The language-specific descriptive name for the page, for example, Help at Aurora or Help at <seo:StoreName/>. This name displays in the browser title bar. In the page HTML, this content is inserted in the <title> tag.
Maps to: SEOPAGEDEFDESC.TITLE
- MetaDescription
- (String) The language-specific meta description for the page. The meta description is a short, human-readable description of the page to help search engines and our customers understand the page content. Some search engines display the meta description in search results. In the page HTML, this content is inserted in the meta description tag.
Maps to: SEOPAGEDEFDESC.META_DESC
- MetaKeyword
- (String) The language-specific meta keywords that describe the contents of the web page. Some Internet search engines use these keywords to determine whether your page satisfies a search query. Separate each keyword with a comma and a space.
Maps to: SEOPAGEDEFDESC.META_KEYWORD
- LanguageId
- (Integer) The language ID for the language-specific fields in this input file. If omitted, defaults to the language specified in the business context of the environment configuration file. Examples of valid values:
- -1 (for English)
- -2 (for French)
We can look up language ID values in the LANGUAGE table. Maps to:
- SEOURLKEYWORD.LANGUAGE_ID
- SEOPAGEDEFDESC.LANGUAGE_ID
- Delete
- (String) A flag that indicates whether to delete the SEO properties for a page. Specify 1 to delete the row.
Related concepts
Pages and page creation
Search engine optimization (SEO) title and meta description (TMD) data for store web pages
Related tasks
Extracting Commerce Composer data with the Data Extract utility
Related reference
Commerce Composer samples
Sample: Extracting Commerce Composer pages
Sample: Extracting Commerce Composer data
Commerce Composer object input file definitions