Populating widget input fields

An SEO widget has no visual presentation. The widget populates the following elements in the HEAD tag of its host page:

title tag.
description parameter of a meta tag.
keywords parameter of a meta tag.

When you create or configure a SEO widget, you need to supply values for title, description, keywords. You can enter one variable or a list of variables in each field. For variables, see ???.

The rest of this topic describes the use of variables through examples.

Anatomy of a variable

All dynamic or variable content must meet the following requirements:

They must begin and end with two curly brackets. Any content outside them is published as entered in the field.
A period must separate all the elements of the variable.

The following example shows a commonly used variable, namely the variable for category meta_description, and a table describing its elements.

RequestResponse

{{$rfk.context.category[0].meta_description}}

Element	Description
`$rfk`	Discover
`context`	Context
`category[0]`	First item from a list of categories
`meta_description`	The value for the `meta_description` attribute

Phrase or list of variables

This section includes a list of variables, and a table describing its content.

RequestResponse

Shop {{$rfk.context.genders,}} {{$rfk.context.category_sport,}} {{$rfk.context.technology_feature_name,}} | Store name goes here

Note

The comma beside the variable is not part of the variable. It is not connected to the variable by a period. It appears when variable has a value, and gives the SEO text a phrase like appearance.

Element	Description
`Shop`	Static text (not surrounded by curly brackets)
`$rfk.context.genders`	Value of an attribute called `genders`
`$rfk.context.category_sport`	Value of an attribute called `category_sport`
`$rfk.context.technology_feature_name`	Value of an attribute called `technology_feature_name`
`\| Store name goes here`	Static text (not surrounded by curly brackets)

Variables and actual values

At the time of publishing a page associated with a particular URL, some variables might not have actual values. Discover ignores everything between the curly brackets if the variable does not have a value.

For the page shown at URL store.com/women/tennis, the content is not driven by technology_feature_name and its variable has no value. The variable is ignored if the following is added as description:

RequestResponse

Shop {{$rfk.context.genders,}} {{$rfk.context.category_sport,}} {{$rfk.context.technology_feature_name,}} | Store name goes here

There is no limit to how many variables you enter in the fields. However, we recommend that you restrict yourself to those that are in line with your merchandising strategy.

Do you have some feedback for us?

If you have suggestions for improving this article,