This guide will help you configure the Magento Tweakwise Attribute Landing Page Extension.
Important
The Attribute Landing Page module is part of Tweakwise level Medium or higher
Introduction
For marketing campaigns, it is great to introduce URLs behind which a search-engine optimised product overview page becomes visible. Think of special pages for brands or a specific group of products such as round tables.
- Improve the SEO of your webshop with unique URLs and metadata.
- Use flexible conditions for adding products to the page.
- Display custom CMS blocks above or below the product selection.
- Add landing pages to the sitemap for better visibility
- Create overview pages such as a page that links to all brands.
- Create as many landing pages as desired.
Prerequisites
Please note that for this extension to work properly, it is important that both extensions are installed:
- Hyvä: Magento2TweakwiseHyva
- Default theme: Magento2Tweakwise
- The Tweakwise Export extension must be installed, Enabled and Layered Navigation must be enabled.
Managing attribute landing pages takes place in the following modules:
- Content > Attribute landing pages > Manage pages
- Content > Attribute landing pages > Manage overview pages
Creating an Attribute Landing Page
Go to Content > Attribute landing pages > Manage pages and choose to create a new page.
General settings
The key feature of an attribute landing page is that you get a pretty URL to a special category page where certain filter values are selected.
When configuring an attribute, in the ‘Attribute’ column, enter the ‘attribute code’ known in Tweakwise. In the ‘Value’ column, enter the value for the filter to be selected. Only select the filter values that are on the filter template in Tweakwise. The attribute and value text must exactly match the known data.
The attribute code can be found in Tweakwise app on the specific attribute listed under ‘URL name’.
Setting | Value | Description |
---|---|---|
Active | Yes/No | Enable/disable the landing page |
Category | Select | Setting to indicate which category this landing page should be limited to. Make sure you select a category that contains products. |
Name | Text | Internal name of the landing page, it is not used on the front-end. |
URL path | Text | Specify on which url path this landing page should trigger. Important: do not include domain. |
Filter attributes | Text | Specify which filter values should be applied to the landingpage. Note: only select filters that are on the filter template in Tweakwise. |
Hide selected filters | Yes/No | Yes: do not display the selected filters in the front-end. This prevents the visitor from deselecting the filter or clicking more options. Note: if you use the root category under Category, this option must be set to ‘Yes’. |
Tweakwise Filter Template | Dropdown | This setting determines which filter template is used on the page. If you choose ‘Default template’, the template linked to the selected category will be used. |
Tweakwise Merchandising template | Dropdown | This setting determines which merchandising (sorting) template is used on the page. If you choose ‘Default template’, the template linked to the selected category will be used. |
Tweakwise Builder template | Dropdown | This setting determines which builder template is used on the page. If you choose ‘Default template’, the template linked to the selected category will be used |
Active stores | List | Using this setting, you determine which storeview this landing page works for. You can easily select the right storeview from the tree structure. Multiple select is possible. |
Allow link in faceted search | Yes/No | Enables cross-linking to the landing page from facets. Yes: you have created a landing page for blue jeans and the category jeans is filtered on blue then the visitor is automatically directed to the landing page. |
Notes:
- If the values do not match exactly or if you have used attributes here that are not present on the filter template, the set-up values will be ignored.
- Names & values are case-sensitive.
- Next to feed properties (recommended), you can also use derived properties for this functionality. Using the derived properties, you can also select a subset of products from Tweakwise.
Content & SEO
In the content section, you give the landing page additional information. You can give the page a special header and add content above and below the product selection. For example SEO content, products or other possibilities offered by Magento's Page editor.
The SEO section allows you to make specific SEO setups for the landing page created. Commons SEO fields like canonical and meta fields can be configured.
Overview page
It is possible to present this landing page on an overview page. An overview page is a page that links to several landing pages. You can give the page an image with image, which is displayed on the overview page.
Creating an overview page
An overview page allows you to easily collect all kinds of attribute landing pages on one page. Such a page can again be made visible behind an SEO-friendly, self-determined URL. Think, for example, of an overview page for brands.
Go to the module manage overview pages and choose ‘add new page’.
General settings
Setting | Value | Description |
---|---|---|
Active | Yes/No | Enable/disable the landing page |
Name | Text | Internal name of the landing page, it is not used on the front-end. |
URL path | Text | Specify on which url path this landing page should trigger. Important: do not include domain. |
Active stores | List | Using this setting, you determine which storeview this landing page overview is for. You can easily select the right storeview from the tree structure. Multiple select is possible. |
Content & SEO
In the content section, you give the page additional information. You can give the page a special header and add content above and below the product selection. Think of text, products and all the other possibilities offered by Magento's Page editor.
The SEO section allows you to make specific SEO setups for the landing page created. Commons SEO fields like canonical and meta fields can be configured.