Getting Started

Welcome to the Advanced SEO Suite Documentation. Here you will find everything you need to set up your Advanced Search Engine Optimization Suite (SEO) and tune-up organic (non-paid) search engine results for your store, along with technical elements, which can improve rankings, drive traffic, and boost overall brand awareness on the Internet.

Our solution has a very convenient backend interface to set up optimization options, and a transparent frontend interface which displays optimization results on each page. Whether you are new or an advanced user, you can find some useful information here.

Go ahead, dive in!

Firstly, please, find our extension in the My Downloadable Products section of our store. Learn how to install extension, and proceed with Quick Start, which will guide you when setting up your SEO policy.

How to install the extension

  1. Back up your store's database and web directory.
  2. Log in to the SSH console on your server and navigate to the root directory of the Magento 2 store.
  3. Copy installation instructions from the page My Downloadable Products to the SSH console and press ENTER.

  4. Run the command php -f bin/magento module:enable -f Mirasvit_Core Mirasvit_Seo Mirasvit_SeoAutolink Mirasvit_SeoSitemap Mirasvit_SeoContent Mirasvit_SeoMarkup Mirasvit_SeoToolbar to enable the extension. If you are using native Magento Layered Navigation and there are no third-party Layered Navigation extensions installed on your store, you can also enable Mirasvit SeoFilter: php -f bin/magento module:enable Mirasvit_SeoFilter
  5. Run the command php -f bin/magento setup:upgrade to install the extension.
  6. Run the command php -f bin/magento cache:clean to clean the cache.
  7. Deploy static view files

    rm -rf pub/static/frontend/*; rm -rf pub/static/backend/*; rm -rf var/view_preprocessed/*; php -f bin/magento setup:static-content:deploy

  8. Setup a cron job for Magento.

    You can skip this step if you have already configured cron jobs for Magento 2 store, or you can check out this link for Magento documentation instructions on this regard.

Quick Start

Our Advanced Search Engine Optimization Suite (SEO) extension is a powerful tool which allows you to perfectly tune up your store for maximum search indexing performance. After instlling the extension, we recommend to consider following steps:

  1. Check out SEO Templates to configure the headings and meta-information of your pages. Templates are very flexible and can fit your policy using a complex condition subsystem. Meta-tags can also be overridden by Rewrites. Unlike Templates described above, rewrites act on top of all other templates used on your page. Rewrite is a powerful tool for precise metadata policy. The main part can be implemented as Templates, since one template can handle multiple pages. Individual (or exceptional - promotional, for example, or some action-related) pages can be then additionally optimized using Rewrite. The ability to use wildcards allows you to alter metadata even on search results and other dynamic pages.

  2. Google allows you to display information about products and stores, and where they are sold on search result pages (SERP). To use this capability, you need to provide the web crawler with additional pieces of information known as snippets. Add these snippets to your pages, and Google crawler can utilize them. This functions in the the same way that you can provide additional information for Facebook sharing.

  3. Our Redirects allows you to create special redirects from one page to another (point to point), and flexibly manage 404 pages, directing customers to different sections of the store. These redirects can be generated separately, and imported to our extension as a CSV file.

  4. The advanced cross link functionality for Magento 2 helps you build solid site-linking architecture in order to interlink all thematically relevant pages, so it's also definitely worth checking out, and is 100% search engine-friendly. This can be done via our Autolinks.

  5. After fine-tuning meta-information using the tools above, you can manage and improve your sitemap with our Extended Sitemap functionality.

This should get you off to a good start!

Please refer to appropriate sections of our manual to get more info.

SEO General Configuration

All SEO settings are located at Marketing -> Advanced SEO Suite > Settings -> SEO and are broken down into the following sections:

General Settings

  • Add Canonical URL Meta Header - If this option is enabled, the tag <link rel="canonical" href="http://store.com/" /> will be added to the META-tags of your store.
  • Use longest product URL as canonical - If the category path is used in products URLs and certain products reside in several sub-categories - the deepest category tree path will be used for canonical meta tag. Require the enabled option "Use Categories Path for Product URLs" from the Configuration > Catalog > Catalog > Search Engine Optimization.
  • Associated Products Canonical Tag for Configurable Products - if set to "Parent Product": if a Simple Product has a Configurable Product as a Parent Product, then for the simple Product, the Canonical URL will be a Configurable Product URL.
  • Associated Products Canonical Tag for Grouped Products - if set to "Parent Product": if a Simple Product has a Grouped Product as a Parent Product, then for the simple Product, the Canonical URL will be a Grouped Product URL.
  • Associated Products Canonical Tag for Bundle Products - if set to "Parent Product": if a Simple Product has a Bundle Product as a Parent Product, then for the simple Product, the Canonical URL will be a Bundle Product URL.
  • Canonical to store without store code - provides the possibility of cutting the store code from the canonical URL if the option "Configuration->GENERAL->Web->Add Store Code to Urls" is enabled
  • Cross Domain Canonical URL - sets the default cross-domain canonical URL for a multistore configuration. For more information, see Cross-domain Canonical URL.
  • Prefer https for Cross Domain Canonical URL - Use the https url for Cross Domain Canonical.
  • Add '?p=' to paginated content - if set to "Yes", the canonical link will include information about the current page; otherwise the canonical on paginated content will point to the category URL.
  • Don't use canonical URLs on pages - the list of pages where the Canonical Meta tags will not be added. This can be a full action name or a request path. Examples:

    Example

    *cell-phones* - exclude URLs which contain the phrase 'cell-phones'
    *cell-phones/nokia-2610-phone.html -  exclude URLs which have end path: 'cell-phones/nokia-2610-phone.html'
    catalogsearch_result_index
    catalogsearch_advanced_index
    catalogsearch_advanced_result
    checkout_cart_index
    checkout_onepage_index
    cms_index_noroute
    
    Wildcards are allowed:
    customer_account_*
    customer/account/*

  • Robots Meta Header - allows you to instruct robots not to index the content of a page, and/or not to scan it for links to follow. The URL pattern can be a full action name or a request path. Wildcards are allowed. Examples:

    Example

    *cell-phones*                           INDEX, NOFOLLOW
    *cell-phones/nokia-2610-phone.html      NOINDEX, NOFOLLOW
    customer_account_*                      NOINDEX, NOFOLLOW
    /customer/account/*                     NOINDEX, FOLLOW
    *?mode=list                             INDEX, NOFOLLOW
    
    Examples for layered navigation:
    filterattribute_(manufacturer)          INDEX, NOFOLLOW
    filterattribute_(1level)                NOINDEX, NOFOLLOW
    

    Read more about Robots.txt.

  • Robots Meta Header for HTTPS - allows you to add headers like "NOINDEX, FOLLOW", "INDEX, NOFOLLOW", "NOINDEX, NOFOLLOW" only for https store.

  • Enable Link Rel="next/prev" - adds pagination <link rel="next/prev" .. > to the head of your products list pages. This feature is highly recommended by Google.

    Note

    Please note that if AJAX technology is used on some of your pages (for example on categories), a human user may need to refresh (reload) the page to check actual canonicals, alternates and hreflang tags in the source code of a page (since they are not altered by AJAX). However, as Google crawlers always load page anew when they follow any URL, the search engine's bots will always see the correct meta data on your page (meta data is designed for search engines rather than for human visitors).
  • Enable Link Rel="alternate" and hreflang - sets "alternate" and "hreflang" tags for multilingual stores. More detailed information:

    If you have a multilingual store, you need to configure a second "hreflang" parameter ("language" from country/language pair) for those store views who need this. To set the appropriate language for the store view, go to Stores > Configuration > General and select the required store view. At the tab Locale Options, select the appropriate locale for this store view and save it. This selected locale code will be the first code of the hreflang parameter. To set the alternate and hreflang tags, go to SEO > Settings and select the appropriate Store View where you use another language. Untick the Use Website on the line Enable Link Rel="alternate" and hreflang and select the value Add for everywebsite from the drop down list. After this action, a new field will appear: Hreflang locale code (not necessary) where you can additionally set the language code which will be added to the alternate URL as a second parameter.

    Alternatively, you may set the "Enable Link Rel="alternate" and hreflang" option to "Configure manually". This way, you can manually determine which store views are alternative versions of each other by setting them in the same store group, individually determining the HrefLang part of an alternate meta link for each store. All configuration in this case takes place on the "Default Config" scope in the admin panel.

    Note

    This is an optional setting that is meant for adjusting alternate links combination if you are not happy with the automatic generation of those links. If you are unsure what to enter in those fields - using "Add for every website" setting of "Enable Link Rel="alternate" and hreflang" is recommended.

    Note

    Google does not recommend using the URLs with a parameter for the multilingual stores ?, such as: http://store.com/yourpage.html?___store=french. To get more information about Google multilingual URLs requirements, you can read this article: Multi-regional and multilingual sites

    How to set "alternate" and "hreflang" tags for CMS pages

    To tell the Magento system that some of CMS pages are "alternates", you need to add these page in one Alternate group. Alternate group - is an additional parameter which is added by our module (it can be used by any word in this field). CMS page will have alternate links of pages with the same Alternate Group name.

  • Cut category additional data for alternate URL - if the store uses different attributes, the name will be added after using the SEO filter

  • Use meta tags from categories if they are not empty - if the option is enabled, Meta Title, Meta Description and Meta Keywords from the General Information tab will be applied to the child categories (only if they are not empty). If this option is enabled, the SEO values from the category General Information tab will prevail over the category SEO tab. To apply H1 to the current category, add H1 text to the Page Header in the General Information tab. If meta tags from the parent category are empty, the child categories and products will only use their own meta tags.

  • Use meta tags from products if they are not empty - if the option is enabled, Meta Title, Meta Description and Meta Keywords from the product Meta Information tab will be applied to the products (only if they are not empty). If the option is enabled, the SEO's values for the product's Meta Information tab will prevail over the category's SEO tab.

Extended Settings

Option Description
Page Number for Meta Title Adds Page Number to the Meta Title. Example: Page 2 | Meta Title Text.
Page Number for Meta Description Adds the Page Number to the Meta Description. Example: Page 2 | Meta Description Text
Allow for use of HTML symbols in meta tags Allow for use of HTML symbols like &, < etc. in meta tags.
Max Length for Meta Title Set the maximum length of the Meta Title. If the actual Meta Title is longer, it will be automatically cropped. If a value of less than 25 was set, the default value of 55 characters will be used instead.
Max Length for Meta Description Set the maximum length of Meta Description. If the actual Meta Description is longer, it will be automatically cropped. If a value of less than 25 was set, the default value of 150 characters will be used instead.
Max Length for Product Name Set the maximum length for the Product Name. If the actual Name is longer, it will be automatically cropped. If a value of less than 10 was specified, default value of 25 characters will be used instead.
Max Length for Product Short Description Set the maximum length for the Product Description. If the actual Description is longer, it will be automatically cropped. If a value of less than 25 was specified, the default value of 90 characters will be used instead.
Redirect urls to lowercase If set to Yes, this allows you to automatically redirect all URLs typed in mixed case to the same URL, but in lower case.

SEO-friendly URLs Settings

Option Description
Remove the Parent Category Path for Category URLs If enabled, removes parent category path for category URLs.
Product URL Key Template Allows you to set the URL key template for store pages. Leave the field empty to disable it.

Note

In the template, you can use any product attributes as variables in the format [product_attribute](e.g. [product_name], [product_brand]).

To activate a new Product URL Key Template, click the button Save config to apply changes. After that, run the ssh command: php bin/magento mirasvit:seo:product-url-template --apply to activate URL template
Trailing Slash Manage trailing slash “/” at the end of each store URL. See possible options below.

Note

There are 3 options for the Trailing Slash parameter:

  • Disabled
  • Redirect to same page with Trailing Slash - if a certain URL does not fit to the settings of the trailing slash, the user will be redirected to the same URL, but with a proper trailing slash.
  • Redirect to same page without Trailing Slash - the user will be redirected to the same page, but without trailing slash.

Images

Note

After making changes in this section, clear cache at Stores -> Tools -> Cache Management to apply those changes. These options are store-dependent, so you can have a different URL policy on different stores.
Option Description
Enable SEO-friendly URLs for Product Images If enabled, the extension will replace the URLs of product images with more SEO-friendly ones according to the template. This option impacts product images on product view, product list pages, and in the Google sitemap.
Template for URL key of Product Images Defines the template which will be used for the generation of Product Images URLs.
Enable generation of Product Images Alt and Title If enabled, the extension will automatically insert the Alt HTML attribute to all product images. This option impacts product images on product view, product list pages, and in the Google sitemap.
Template for Product Images Alt and Title Defines the template which will be used for the generation of Product Alt and Titles.

Note

In templates, you can use variables like: [product_name] [product_sku] [by {product_manufacturer}] [color {product_color}].

Example:

  • Template for URL key of Product Images: [product_name]
  • Actual URL: http://www.example.com/pub/media/catalog/product/m/b/mb04-black-0.jpg
  • Rewritten URL: http://www.example.com/pub/media/product/28fb/strive-shoulder-pack.jpg

The same will be done for Alt and Title attributes.

Info (visible in the frontend, will not work if FPC or Varnish is enabled)

This section governs the special SEO Toolbar block that can be displayed on the frontend, as shown on the screenshot below:

seo_toolbar.png

Option Description
Show Info Enable SEO Toolbar. It will become visible in the frontend of the store. Has three modes: Disabled, Enabled and Enabled if Cookie Exists (see note below for more info).
SEO Toolbar position Allows you to select where to display the Info block: Left or Right.
Show info only for Defines a list of IPs (comma separated), visitors which can see the SEO Toolbar. Leave it empty for access from any location.

Note

You can restrict the SEO Toolbar display by creating a special bind to your workstation (very useful for developers with dynamic IP).

For this, you need to log in to backend from your workstation, set Show Info to Enabled if Cookie Exists, and then press Add Cookie button, that will appear. This will create on your browser a cookie that will act as an access password.

You can remove this cookie at any time by pressing the Delete Cookie button.

SEO Templates Management

The SEO Templates option is a powerful and flexible tool for managing the meta information on your store pages according to defined rules.

seo_templates

Note

Meta tags are defined in SEO Templates and can be overwritten by the same tags filled in the SEO Rewrite Manager.

Go to Marketing > Advanced SEO Suite > SEO Templates. Here you can find all information about existing templates, edit them and create new SEO templates.

Create a SEO Template

To add a new SEO Template, go to Marketing > Advanced SEO Suite > Templates and click Add SEO Template.

General Information tab

Fill in the following General Information tab fields:

  • Internal Name - give the template a name.
  • Rule Type - determine the pages that the SEO Template will be applied to. It will determine the pages that the SEO Template will be applied to. You may choose one of three types:
    • Product - to apply the template to product pages.
    • Category - to apply the template to category pages.
    • Results of layered navigation - to apply the template to the filtered Layered Navigation pages.
  • Meta title - allows you to rewrite the meta title tag of the targeted pages.
  • Meta keywords - allows you to rewrite the meta keywords tag of the targeted pages.
  • Meta description - allows you to rewrite meta description tags of the targeted pages.
  • Title (H1) - allows you to change the header of the targeted pages.
  • SEO description - allows you to add additional SEO information about a rewritten store page. More detailed information:

    This field is not required, but can increase Google indexation. A SEO description block will be added in a position which you can configure in "SEO description position" setting. seo_description_template_after

  • SEO description position - allows you to determine where SEO Description blocks will be displayed on the page. More detailed information:

    You can choose from one of these predefined options: Bottom of the page, Under Short Description, Under Full Description, Don't add automatically or select the option "Under custom template", which will provide an additional field "Template for adding SEO description", where you can fill in the desired template path, for example: < magento_root_folder >/app/code/Magento/Catalog/view/frontend/templates/product/view/additional.phtml . You may determine the necessary template path by temporarily enabling "Template Path hints for StoreFront" from Stores > Settings > Configuration > Advanced > Developer > Debug Admin Panel section. seo_description_template_after_front

  • Product short description - allows you to rewrite a short desctiption on the product page. Only available for templates based on product rule types.
  • Product description - allows you to rewrite the description on the product page. Only available for templates based on product rule types.
  • Status - indicates whether the template is enabled or disabled.
  • Apply for the Store View - you can select the store views where the template will be added
  • Sort Order - you may define the importance of the template. If more than one SEO Template is assigned to a single page, it will be applied to the template with the highest value of sort order parameter.

Conditions tab

On the Condition tab section of the SEO Template configuration page, you may define conditions that will trigger the template. The Template condition consists of two parts: a combining condition, and one or several sub-conditions. The sub-conditions are tied together by a combining condition. You can change ANY to ALL and TRUE to FALSE. Thus, a combining condition can have one of these four forms:

Example

  • If ALL of these conditions are TRUE
  • If ALL of these conditions are FALSE
  • If ANY of these conditions are TRUE
  • If ANY of these conditions are FALSE

You can set multiple sub-conditions by clicking the round + button. This will open a drop-down list with product attributes. However, not every attribute can be used to generate template conditions. First of all, the attribute property Use for Promo Rule Conditions must be set to Yes. To set this option to active, go to Stores > Attributes > Product, open the edit page of the required attribute and click on the Storefront Properties tab. At this section, you can change the Use for Promo Rule Conditions setting.

used_in_promo

You can create multiple-levels of sub-conditions by using a combining condition. Select “Condition combination” in the drop-down list and you will get a combining setting similar to the one at the top level. Under it, you can add a new branch of attribute-based sub-conditions.

Sub-conditions come in the form of “attribute name” + “operator” + “value”.
The “operator” depends on the attribute type and can be:

  • is / is not - used for single entity (for example: SKU)
  • equals or greater than / equals or less than
  • greater than / less than
  • is one of / is not one of - used for multiple entities (for example: selected categories)
  • contains / does not contain

rules

Note

Stop Further Rules Processing - If enabled, the template will be applied to the page even if another rule with a higher sort order value is applicable.
Apply to child categories - If the category is set in Conditions, the template will also be applied to all child categories.

Rich Snippets and Opengraph

Rich Snippets allows you to display additional information about your site's pages in the search results. To set up SEO Rich Snippets, go to Marketing > Advanced SEO Suite > Settings > SEO - SEO Rich Snippets and Opengraph.

Note

Structured data markup for Google Rich Snippets added by our extension is implemented via JSON-LD (JavaScript Object Notation for Linked Data). This method is recommended by Google Guidelines and is preferable to Microdata or RDFa usage(https://developers.google.com/search/docs/guides/intro-structured-data).

Snippets

Set up Rich Snippets for the following data types:

  • Product Rich Snippets - allows you to show product rating stars, prices, descriptions and other parameters in Google search results.

    • Enable Rich Snippet - Enables and disables adding Product Rich Snippets meta information to the product pages
    • Delete wrong snippets automatically - the current configuration will automatically cut incorrect snippets that were added in html
    • Item Description - allows you to add snippets of product Description or Meta Description.
    • Item image - add snippets of a Product image.
    • Item Availability - add snippets of a Product stock status.
    • Payment Methods - add snippets of preferred payment methods.
    • Delivery Methods - add snippets of delivery(shipping) methods.
    • Product Category - add snippets of Product Categories.
    • Manufacture part number - add the Manufacturer part number of products to the snippets
    • Brand Attribute - allows you to add an attribute code of the brand. If you want to add multiple attributes, use a comma separator. For example: country_of_manufacture, manufacturer
    • Model Attribute - allows you to add an Attribute Code of the model. If you want to add several attributes, use a comma separator. For example: model, car_model
    • Color Attribute - add an attribute code of the color. If you want to add multiple attributes, use a comma separator. For example: color, car_color.
    • Weight - allows you to add weight snippets. You can set it to use Grams, Kilograms or Pounds.
    • Dimensions - if enabled, snippets with dimensions will be added (height, width or depth have to be configured). If the option is enabled, the following additional fields will appear:
      • Unit - if you use a numeric value for the dimension, you can set a dimensional unit. For example: cm, mm, inch.
      • Height Attribute - add an attribute code of the height.
      • Width Attribute - add an attribute code of the width.
      • Depth Attribute - add an attribute code of the depth.
    • Product Condition - if enabled, snippets with a product condition will be added (Condition Attribute, New Condition Value, Used Condition Value and Refurbished Condition Value have to be configured). If the option is enabled, the following additional fields will appear:
      • Condition Attribute - add an attribute code of the product's condition.
      • New Attribute Value - add the value of the new product's condition. Get the value from the attribute of the condition.
      • Used Attribute Value - add the value of a used product's condition. Get the value from the attribute of the condition.
      • Refurbished Attribute Value - add the value of a refurbished product's condition. Get the value from the attribute of the condition.
      • Damaged Attribute Value - add the value of a damaged product's condition. Get the value from the attribute of the condition.

    Note

    https://mirasvit.com store uses product snippets added by Mirasvit SEO Suite, so you can freely view some examples.

    Note

    If you've marked up your site's content, test your markup using the Structured Data Testing Tool, and check the common issues above, remember that it takes some time for rich snippets to appear in the search. Product and Category Rich Snippets will appear only after Google indexation.
  • Category Rich Snippets - allows you to add Rich snippets to the category's pages. Snippets are created using the schema.org markup schema and microdata format. There are these options available to select:

    • Delete wrong snippets automatically - Current configuration will automatically cut incorrect snippets added in html
    • Enable Rich Snippet - Enable and disable adding Product Rich Snippets meta information to category pages
    • Product Offers - add enabled in stock product offers on the category pages.
      • For current page - information about the products will only be added from the current page.
      • For current category - all information about all the products from the current category will be added.
  • CMS Page snippets - allows you to add snippets to CMS pages.

  • Organization snippets - allows you to add store information snippets.

    Enable Organization snippets - allows you to enable or disable adding Organization snippets. If this option is enabled, the following additional fields will appear:

    • Name of Organization - sets the store name.
      • Add Name from Store Information - if the option is selected, the store name will be set from Stores > Configuration > General > General > Store Information > Store Name.
      • Add Name manually - allows you to add a name manually in the field Name Text for Organization Rich Snippet.
    • Country Address - sets the country address.
      • Add Country Address from Store Information - if the option is selected, the country address will be set from Stores > Configuration > General > General > Store Information > Country.
      • Add Country Address manually - allows you to set the country address manually. For example, USA.
    • Locality Address - sets the locality, allows you to set the Locality Address manually. For example, Mountain View.
    • Postal Code - sets the postal code.

      • Add Postalcode from Store Information - if the option selected, the postal code will be set from Stores > Configuration > General > General > Store Information > ZIP/Postal Code.
      • Add Postal Code Manually. For example, 94043.
    • Street Address - sets the street address.

      • Add Street Address from Store Information - if the option is selected, the street address will be set from Stores > Configuration > General > General > Store Information > Street Address.
      • Add Street Address manually - allows you to set the street address manually. For example, 1600 Amphitheatre Pkwy.
    • Telephone Number - sets the store telephone number.
      • Add Telephone Number from Store Information - if the option is selected, the telephone number will be added from Stores > Configuration > General > General > Store Information > Telephone Number.
      • Add Telephone Number manually - allows you to set the telephone number manually.
    • Fax Number - sets the fax number.
    • Email - sets the store email.
      • Add Email from Store Email Addresses - if the option is selected, the email will be set from Stores > Configuration > General > Store Email Addresses > General Contact > Sender Email.
      • Add Email manually - allows you to set the email manually.
  • Rich Snippets Breadcrumbs - allows you to add Breadcrumbs to rich snippets. With this setting, you have several options:

    • Disabled - Rich Snippets structured data won't be added to the breadcrumbs block.

    • Breadcrumb - structured data will be added, as shown on the image below:

    breadcrumb

    • BreadcrumbList - structured data will be added, as shown on the image below:

    breadcrumblist

    Note

    Please note that structured data is added only to links in the breadcrumbs block. Structured data is not added to a text category or product name, if it is not presented with a link.

Open Graph

  • Facebook Opengraph allows Facebook to display information about your pages in a more attractive way when users share links to the pages of your store. To use this option, you need to add the Facebook button with another extension. You can test this option here: Open Graph Debugger.

    There are these options to select:

    • Category Opengraph - if the option is enabled, Facebook Opengraph tags will be added to the store category pages.
    • Enable Cms Opengraph - allows you to add Opengraph tags to the store CMS pages.

Twitter

  • Add Twitter Summary Card allows Twitter to display information about your pages in a more attractive way when users share links to the pages of your store. To use this option, you need to add the Tweet button with another extension. You can test this option here: Card Validator.

    You can choose one of two card variations:

    • Summary Card - is designed to give the reader a preview of the content before clicking through to your website.
    • Summary Card with Large Image - is designed to give the reader a rich photo experience, and clicking on the image brings the user to your website.
  • Twitter username - @username for the website used in the card footer.

Cross-domain Canonical URL

The extension allows you to manage the cross-domain canonical URLs for a multistore configuration.

To manage the cross-domain canonical URLs, go to Marketing > Advanced SEO Suite > Settings > SEO.
Set up the following field:

  • Cross Domain Canonical URL - sets the default cross-domain canonical URL for multistore configurations.

Example

For Example, you have the following stores:

http://example.com/
http://mystore.com/
http://site.com/


  1. If you select the option, Default Store URL from the Cross Domain Canonical URL list, all the stores will have their own canonical URLs:
    for http://example.com/ canonical URL will be http://example.com/product/
    for http://mystore.com/ canonical URL will be http://mystore.com/product/
    for http://site.com/ canonical URL will be http://site.com/product/
  2. If you select the store http://mystore.com/ as your Cross Domain Canonical URL, all stores will have canonical URLs with the domain http://mystore.com/:
    for http://example.com/ canonical URL will be http://mystore.com/.../
    for http://mystore.com/ canonical URL will be http://mystore.com/.../
    for http://site.com/ canonical URL will be http://mystore.com/.../

Canonical Rewrite

Note

Mirasvit SEO Suite extension provides you with a mechanism to set a canonical link automatically for all relevant pages on your store, but if you need an exception for certain pages, you can configure canonicals for them manually by using canonical rewrite as described below.

Go to Marketing > Advanced SEO Suite > Canonical Rewrite and click the button Add Canonical Rewrite. In the opened window, enter these settings:

  • Is Active - indicates whether rewrite is active or disabled.
  • Canonical URL - enter the full URL that the canonical should point to.
  • Visible in Store View - Select the store views where the rewrite will be applied.
  • Conditions - in this section, you can specify which page(s) should have a canonical link set in the "Canonical URL" field using either Rule conditions or Regular expression variants
  • Additional - in this section, you have the option of defining additional parameters like Sort Order, which is used for determining which canonical should be applied if the page matches several rules at once (the canonical with the higher "Sort Order" will be used) and Comments for internal use to distinguish one rewrite from others or store-related information.

canonical_rewrite

Redirects management

Redirect rule creation

Note

With this option you can manage mass redirects in your site more efficiently.
To create a custom redirect rule, you need to go to Marketing > Advanced SEO Suite > Redirects. Click the Add Redirect button. In order to redirect the rule, you must define:

  • Request URL - redirect if the user opens this URL. You can use wildcards.
  • Target URL - redirect to this URL from the Request URL.
  • Redirect Type - choose the HTTP response status code that will be used when redirecting.

    Available options:

    • 301 Moved Permanently - This and all future requests should be directed to the given URI.
    • 302 Object Moved - The response to the request can be found under another URI using the GET method.
    • 307 Temporary Redirect - The request should be repeated with another URI, however, future requests should still use the original URI. For example, a POST request should be repeated using another POST request.
  • Redirect only if the request URL can't be found (404) - the redirect will only be triggered if the request URL corresponds with the 404 Not Found status. This is extremely useful when dealing with 404 Not Found issues in Google Webmaster Tools.
  • Comments - you may leave them to be visible in the admin panel so that other authorized backend users can easily understand the purpose of the redirect rule.
  • Status - indicates whether the redirect rule is enabled or disabled.
  • Visible in Store View - you may select store views in which redirects will be added.

Example

For example, with this option you may set up redirects for all pages that return a "404 Not Found" error to the Homepage of your site.

redirect_create

Note

This implementation is an extremely effective means of dealing with lots of 404 errors found in the Google Webmaster Tools due to
previous URL generation misconfiguration or if pages that do not exist anymore on your site are still present in the Google cache.
Also, the extension allows you to make Import of URLs for Redirect

Import/Export Redirects

This extension allows you to import and export redirect rules via the CSV file.

Go to Marketing > Advanced SEO Suite > Redirects. At the right upper buttons list, click the Import/Export Redirects button.

import_export_redirects

Click on the Example of CSV file to download an example import template. If you open the example, you will see these columns on the first line: url_from, url_to, is_redirect_only_error_page, comments, is_active.

redirect_import_file

Strarting with the second line, fill in the values according to the header. All of these headers correspond to the fields in which you can see if you have created a new redirect rule.

redirect_create

If you have already correctly created a CSV file, click on the button Browse and select the file. To apply redirects, click the Save button.

Note

To be interpreted correctly, the CSV file needs to be created using UTF-8 encoding and a comma as a field delimiter.

Rewrites Management

Rewrites Management allows you to configure meta tags, H1 headers, and SEO descriptions for any store URLs.

Note

All SEO meta tags and descriptions of the rewrited pages are applied only to the current rewrite page URL, and aren't applied to other store pages (child categories, another layered navigation product URL, etc).

Go to Marketing > Advanced SEO Suite > SEO Rewrites. To add a new rewrite, press the button Add Rewrite. Fill in the following fields:

  • Pattern of URL or Action name - pattern of the URL of the page on which you want to change the SEO values. Can be a full action name or a request path; wildcards are allowed. Examples:

    /customer/account/login/
    /customer/account/*
    customer_account_*
    *?mode=list
    */electronics/cell-phones/
    *cell-phones/nokia-2610-phone.html
  • Title - title of the rewritten store page.

  • SEO description - allows you to add the additional SEO information about a rewritten store page. More detailed information:

    This field is not required, but it can increase Google indexation. A SEO description block will be added in a position where you can configure in "SEO description position" setting. image

  • SEO description position - allows you to determine where the SEO Description block will be displayed on the page. More detailed information:

    You can select one of the below defined options: Buttom of the page, Under Short Description, Under Full Description, or choose the option "Under custom template", that will provide the additional field "Template for adding SEO description", where you can fill in desired template path, for example: < magento_root_folder >/app/code/Magento/Catalog/view/frontend/templates/product/view/additional.phtml . You can determine the necessary template path by temporarily enabling "Template Path hints for StoreFront" from the Stores > Settings > Configuration > Advanced > Developer > Debug Admin Panel section. image

  • Meta Title - meta title of the rewritten store page.
  • Meta Keywords - meta keywords of the rewritten store page.
  • Meta Description - meta description of the rewritten store page.
  • Is Active - indicates whether the rewrite is active or disabled.
  • Visible In - sets the store views for where the SEO Rewrite will be applied.

Click the button Save Rewrite.

You can use variables for all SEO meta tags and descriptions from the list of variables. See List of variables that can be used in templates

Note

Information defined in the SEO Rewrite rule will prevail over meta tags defined in the SEO Templates.

seo_rewrite_create

SEO Filters

SEO Filters allows for a replacement of layered navigation links (i.e. with interchangeable parameters like size and colors) with SEO-friendly links with more intuitive and human-readable paths.

The corresponding subsystem of Mirasvit SEO Suite is located at Marketing > Advanced SEO Suite > Settings > SEO Filters.

The only options available at this time are:

  • Enabled - enables and disables the SEO Filters feature
  • Separator between words in complex filter name - if the attribute name consists of several words, this option will define their concatenating to a single name with a delimiter. These are the following options:
    • Do not use separator - words are not separated at all.
    • Use "_" as separator - words will be separated with an underscore.
    • Use capital letter as separator - each word in the attribute name will be capitalized.

Note

Important Note

SEO Filters should only be enabled if you are using native Magento Layered Navigation or Mirasvit Layered Navigation and there are no third-party Layered Navigation extensions installed on your store.

Otherwise, turning on this option can cause unchecked errors and unexpected crashes.

SEO Filters Example

Consider links which are generated for different subcategories at the Tops category page, and displayed as layered navigation sidebar.

Layered Navigation Sidebar

Subcategories, displayed above, are constructed dynamically from parameters that are defined in configurable products, and have the following form. For example, let's consider a link for a top of XS size and of orange color.

    http://www.example.com/women/tops-women.html?size=167
    http://www.example.com/women/tops-women.html?color=56

As you can see, the link has a dynamic part which takes the form parameter=ID, which is not optimal for web indexing.

However, if we set Marketing > Advanced SEO Suite > Settings > SEO Filters -> Enable to Yes, the links will change into:

    http://www.example.com/women/tops-women/xs.html
    http://www.example.com/women/tops-women/orange.html

These links are far more SEO-friendly.

Note

Important Note

You should purge ALL cache after enabling/disabling SEO filters, otherwise the links will not change.

List of variables that can be used in templates

This extension allows you to use variables for the category, product and layered navigation pages.

Note

The extension will hide any variable in the rule if it is not set for the proper template. If you would like to hide some particular text around the variable, just do the following: [some text {variable} other text].

Permitted variables for the following pages:

Category pages

  • [category_name] - name of the category
  • [category_description] - category description
  • [category_url] - category URL
  • [category_parent_name] - name of the category parent
  • [category_parent_url] - URL of the category parent
  • [category_parent_parent_name] - name of the parent of category parent
  • [category_page_title] or [category_meta_title] - title of the category
  • [store_name] - name of the current store
  • [store_url] - URL of the current store
  • [store_address] - address of the current store
  • [store_phone] - phone number of the current store

Product pages

  • [product_{attribute_code}] - where {attribute_code} is any attribute which can be found in Catalog > Attributes > Manage attributes. For example, for an attribute with the Attribute Label Decor Type and Attribute Code decor_type a corresponding template variable would be [product_decor_type]. The same goes for [product_brand], [product_size], etc
  • [product_name] - product's name
  • [product_sku] - product's SKU
  • [product_price] - product's regular price
  • [product_special_price] - product's special price
  • [product_final_price] - product's final price
  • [product_final_price_minimal] - product's final price (for bundle, configurable and grouped products will return minimal price)
  • [product_final_price_range] - product's final price (for bundle, configurable and grouped products will return price range)
  • [product_brand] - product's brand
  • [product_url] - product's URL
  • [product_entity_id] - product's ID
  • [category_name] - name of the category
  • [category_description] - category description
  • [category_url] - category URL
  • [category_parent_name] - name of the category parent
  • [category_parent_url] - URL of the category parent
  • [store_name] - name of the current store
  • [store_url] - URL of the current store
  • [store_address] - address of the current store
  • [store_phone] - phone number of the current store

CMS Page Data

  • [cmsPage_title] - title of the CMS Page
  • [cmsPage_meta_keywords] - keywords of the CMS Page
  • [cmsPage_meta_description] - meta description of the CMS Page
  • [cmsPage_content_heading] - content heading of the CMS Page
  • [cmsPage_content] - content of the CMS Page
  • [cmsPage_meta_title] - meta title of the CMS Page

Layered Navigation pages

  • [filter_selected_options] - will return the values of the chosen attributes in the layered navigation. Format: <selected options of attribute1>, <selected options of attribute2>. For example, "Asus, Red, Black Intel Core I5".
  • [filter_named_selected_options] - will return you names with values of the chosen attributes in the layered navigation. Format: <name of attribute1>: <selected options of attribute1>, <name of attribute2>: <selected options of attribute2>. For example, "Brand: Asus, Color: Red, Black CPU: Intel Core I5".
  • [category_name] - name of the category
  • [category_description] - category description
  • [category_url] - category URL
  • [category_parent_name] - name of the category parent
  • [category_parent_url] - URL of the category parent
  • [store_name] - name of the current store
  • [store_url] - URL of the current store
  • [store_address] - address of the current store
  • [store_phone] - phone number of the current store

Example

Example

[filter_selected_options] [category_name] ★★★★★ good prices, favorable terms of delivery and payment - [store_name] [| Call us {store_phone}]

Command Line Interface

Usage: php -f ./bin/magento [options]

  • mirasvit:seositemap:generate --info - provides an information message with the available sitemap generation command options
  • mirasvit:seositemap:generate --all - generates all available sitemaps
  • mirasvit:seositemap:generate --sitemap_id - generates individual sitemaps through their sitemap id.
    The id of the necessary sitemap can be taken from the Admin Panel grid in Marketing > Advanced SEO Suite > Site Map. For example, to generate sitemap with the id 8 issue command:
    php -f ./bin/magento mirasvit:seositemap:generate -- sitemap_id 8

  • mirasvit:seo:product-url-template --apply --dry-run - This will simulate the applying
  • mirasvit:seo:product-url-template --restore --dry-run - This will simulate the restoring of original values
  • mirasvit:seo:product-url-template --apply - Apply the product url key template
  • mirasvit:seo:product-url-template --restore - Restore the product url key template using [product_name]
  • mirasvit:seo:product-url-template --regenerate - Regenerate the urls in table url_rewrite. Useful if database has been corrupted

Extended Sitemap Configuration

Our extension greatly expands the possibilities of sitemap generation. It can alter standard Magento procedures, and add crucial information there that can boost indexing of the store by web crawlers. It can also help you to manage multiple sitemaps, which you can create with different parameters and for different purposes.

Sitemap Example

Sitemap is a special XML file which is typically located at the root of your store and contains important data on crawlable links for your store that you would like Google to become aware of as soon as possible. You can see its location in Marketing > Advanced SEO Suite > Site Map, in columns Path and Link for Google. There are two different ways to make your sitemap available to Google: submit it to Google using the Search Console Sitemaps tool (preferable), or insert the corresponding link anywhere in your robots.txt. More information in sitemaps is available here.

A typical sitemap is a simple, human-readable file, which contain an array of XML records including URL, lastmod, changefreq, priority, image, etc. Sitemaps feature a number of optional elements that can be read by Google crawler. A sitemap.xml file, generated by a native Magento mechanism, can look like this:

Example

<urlset>
    <url>
        <loc>http://www.example.com/gear.html</loc>
        <lastmod>2017-12-10T10:29:50+00:00</lastmod>
        <changefreq>daily</changefreq>
        <priority>0.5</priority>
    </url>
    <url>
        <loc>http://www.example.com/strive-shoulder-pack.html</loc>
        <lastmod>2017-12-10T10:29:52+00:00</lastmod>
        <changefreq>daily</changefreq>
        <priority>1.0</priority>
        <image:image>
            <image:loc>http://www.example.com/pub/media/catalog/product/m/b/mb04-black-0.jpg</image:loc>
            <image:title>Strive Shoulder Pack</image:title>
            <image:caption>Image</image:caption>
        </image:image>
        '<PageMap xmlns="http://www.google.com/schemas/sitemap-pagemap/1.0">
            <DataObject type="thumbnail">
                <Attribute name="name" value="Strive Shoulder Pack"/>
                <Attribute name="src" value="http://www.example.com/pub/media/catalog/product/m/b/mb04-black-0.jpg"/>
            </DataObject>
        </PageMap>'
    </url>
</urlset>

Our extension provides capabilities for additionally tweaking your sitemap.xml, making it more managable and SEO-friendly. These include:

  • making product images' URLs SEO-friendly according to the template (if the corresponding option of SEO Suite extension is enabled for frontend images)
  • adding product images' "title" and "caption" tags according to the template (if the corresponding option of SEO Suite extension is enabled for frontend images)
  • removing particular links from both HTML and XML sitemaps
  • adding custom links to both variants of a sitemap if needed

You can turn the example above in something like this:

Example

<urlset>
    <url>
        <loc>http://www.example.com/gear.html</loc>
        <lastmod>2017-12-10T10:29:50+00:00</lastmod>
        <changefreq>daily</changefreq>
        <priority>0.5</priority>
    </url>
    <url>
        <loc>http://www.example.com/strive-shoulder-pack.html</loc>
        <lastmod>2017-12-10T10:29:52+00:00</lastmod>
        <changefreq>daily</changefreq>
        <priority>1.0</priority>
        <image:image>
            <image:loc>http://www.example.com/pub/media/product/28fb/strive-shoulder-pack.jpg</image:loc>
            <image:title>The best Strive Shoulder Pack on the market</image:title>
            <image:caption>Image</image:caption>
        </image:image>
        <PageMap xmlns="http://www.google.com/schemas/sitemap-pagemap/1.0">
            <DataObject type="thumbnail">
                <Attribute name="name" value="Strive Shoulder Pack"/>
                <Attribute name="src" value="http://www.example.com/pub/media/product/28fb/strive-shoulder-pack.jpg"/>
            </DataObject>
        </PageMap>
    </url>
</urlset>

How to Generate Google Sitemap

  1. Tune-up your sitemap settings in Marketing > Advanced SEO Suite > Settings > Extended Site Map, and refer here for more information.

  2. Go to Marketing > Advanced SEO Suite > Site Map, and press the Add Sitemap button.

  3. Sitemap generation pages consists of two fields:

    • Filename - defines the name, under which the sitemap will be saved. If you wish to regenerate a standard sitemap, use sitemap.xml.
    • Path - defines the path where the sitemap should be placed. If you wish to regenerate a standard sitemap, use /.
  4. Manually edit robots.txt to include a generated sitemap to the web indexing process. Useful information, and how to do it, can be found here.

Note

Important Note

If you use one of the following extensions, generating a Google sitemap using Mirasvit extension will provide stability benefits as we have a compatibility patch to correctly process their pages pages:

  • Mirasvit Knowledge Base
  • Mirasvit Blog
  • AheadWorks Blog

Note

From version 2.0.37 on, you can also generate sitemap XML files using CLI commands described here

Frontend Sitemap Settings

Settings for Sitemap Generation are located at Marketing > Advanced SEO Suite > Settings > Extended Site Map, Frontend Sitemap Settings subsection:

  • Base URL Path To Frontend Sitemap - Base path to the frontend sitemap page.
  • Meta Title - allows you to add a meta title to the sitemap page.
  • Meta Keywords - allows you to add a keyword section to the sitemap page.
  • Meta Description - allows you to add a meta description of the sitemap page.
  • H1 Header - allows you to add a special header to the sitemap page (useful for multiple sitemap instances).
  • Show Products - if enabled, a list of all active catalog products will be displayed in the frontend sitemap.
  • Show Non-salable Products - if enabled, will be exported all products. Disable this option if you want to hide disabled products.
  • Show CMS Pages - if enabled, a list of CMS pages will be displayed in the frontend sitemap.
  • Ignore CMS Pages - defines a list of CMS pages which will not be displayed in the frontend sitemap.
  • Show Stores - if enabled, a list of Store Views will be displayed in the frontend sitemap.
  • Additional links - defines a comma-separated list of pages which should be added to the frontend sitemap. For example, you can add links Our Promotions and Customer Account to the sitemap:

    /promotions/, Our Promotions
    /customer/account/, Customer Account
  • Exclude by pattern - defines a list of patterns for links that will be excluded from the frontend sitemap.
  • Limit the number of links on one page - if not empty, the whole sitemap will be turned into a sequence of lesser sitemaps.

sitemap_settings

General Configuration

The auto links function allows you to create a set of links and keywords. For example, you have a page http://example.com/laptops and you wish to promote it by using the keyword "laptop". After you create an autolink connecting this keyword to every occurrence of the word "laptop" on your store CMS pages, the Products or Category descriptions will be added to the link http://example.com/laptops. This way, you are able to build internal crosslinks automatically.

Go to Marketing > Advanced SEO Suite > Settings > Auto Links. You will see the following fields:

  • Add links on - Select the content types where you would like the autolinks to be applied.
  • Don't add links inside tags - Ignore matching keywords enclosed in selected tags.

    Note

    To flexibly skip autolinks for one part but add to another part of the same block or template, you can define a custom tag like <skip_links> or <skip_seo>, wrap the necessay output in the template with a new tag like this: <p><skip_seo><?php echo $description_text; ?></skip_seo></p> and add this tag as skip_seo or skip_links to the Don't add links inside tags field.

    Correct format: one tag without brackets per one line image

  • Skip auto links for a page - Select the pages on which auto links should not be placed.
  • Paths of templates to add links inside - you may use this option to add auto links to the necessary blocks. To determine a necessary template file's paths to put into the field of this configuration option - please set to the "Yes" option "Enabled Template Path Hints for Storefront" in Stores > Configuration > Advanced > Developer > Debug to see it on the frontend.
  • Links limit per page - global limit of links that should be added on any given page. Leave this field empty to disable this limit.

Next steps:

Auto Links Management

Go to Marketing > Advanced SEO Suite > Autolinks and click the button Add New Link. In the opened window, enter the following settings:

  • Keyword - word which will be replaced by the link.
  • URL - target URL of the link
  • URL Target - specifies where the link should open (in the current window or in the new one)
  • URL Title - sets
  • Nofollow - if enabled, the Nofollow attribute will be added to the link
  • Number of substitutions - specifies the maximum number of keyword replacements in the content of the page. If this number is equal to 0, then the number of replacements is unlimited.
  • Occurence - specifies the direction of the search for keyword replacements.
  • Status - indicates whether the link is active or disabled.
  • Visible in Store View - Choose the store views where the links will be added.

Note

You may choose All Store Views OR individual views like English,French. Please do not select both All Store Views along with individual views.

import_link_admin

Next step:

Import Auto Links

This extension allows you to import Auto Links via CSV files.

Go to Marketing > Advanced SEO Suite > Autolinks and click the button, Import Links.

import_links

Click on the Example of CSV file to download an example of the template. If you open the example, you will see the following columns on the first line: keyword, url, url_title, url_target, is_nofollow, max_replacements, sort_order, occurence, is_active, store_id.

import_autolink_file

Each of these headers are responses for the fields in which you can see if you have created a new auto link or opened an existing one.

import_link_admin

Starting with the second line, fill in the values according to the header.

Note

The column keyword is a required field to fill in. Otherwise, CSV files will not be accepted.

If you have already correctly created a CSV file, click on the button Browse and select the file. To apply auto links, click the Save button.

Note

To have a correct autolink import, the CSV file should be created using UTF-8 encoding.

How to upgrade the extension

To upgrade the extension, take the following steps:

  1. Back up your store's database and web directory.
  2. Log in to the SSH console of your server and navigate to the root directory of the Magento 2 store.
  3. Run the command composer require mirasvit/module-seo:* --update-with-dependencies to update the current extension with all dependencies.

    Note

    In some cases, the command above is not applicable, it's not possible to update just the current module, and you need to upgrade all Mirasvit modules in a bundle. In this case, the command above will have no effect.

    Instead, run the composer update mirasvit/* command. It will update all Mirasvit modules installed on your store.

  4. Run the command php -f bin/magento module:enable -f Mirasvit_Core Mirasvit_Seo Mirasvit_SeoAutolink Mirasvit_SeoSitemap Mirasvit_SeoContent Mirasvit_SeoMarkup Mirasvit_SeoToolbar to enable new modules.
  5. Run the command php -f bin/magento setup:upgrade to install updates.
  6. Run the command php -f bin/magento cache:clean to clean the cache.
  7. Deploy static view files

    rm -rf pub/static/frontend/*; rm -rf pub/static/backend/*; rm -rf var/view_preprocessed/*; php -f bin/magento setup:static-content:deploy

Disabling the Extension

Temporarily Disable

To temporarily disable the extension, please follow these steps:

  1. Log in to the SSH console on your server and navigate to the root directory of the Magento 2 store.
  2. Run the command php -f bin/magento module:disable Mirasvit_Seo Mirasvit_SeoFilter Mirasvit_SeoAutolink Mirasvit_SeoSitemap Mirasvit_SeoContent Mirasvit_SeoMarkup Mirasvit_SeoToolbar to disable the extension.
  3. Log in to the Magento backend and refresh the store's cache (if enabled).

Extension Removing

To uninstall the extension, please follow these steps:

  1. Log in to the SSH console on your server and navigate to the root directory of the Magento 2 store.
  2. Run the command composer remove mirasvit/module-Seo to remove the extension.
  3. Log in to the Magento backend and refresh the store cache (if enabled).

Troubleshoot

This section describes the most common problems that customers report and how they can be resolved:

Meta tags were not changed after applyng the SEO template.

You probably have enabled the option "Use meta tags from categories\products if they are not empty".
This means that our extension will not overwrite meta tags if they are defined.

Wrong templates have been used for products.

When you have several templates which are applied to the same product,
you can adjust the priority of the templates by definition of Sort Order in the template settings.
Also, you can use our toolbar to find out exactly which template has been applied to the current page.: image image

In the picture, we can see that only the SEO Template with id1 has been used for this product and only a meta template has been rewritten.

Some products have URLs like "example.com/catalog/product/view/id/2046/category/34"

This happens when you don't have an appropriate rewriting in the URL rewrites table for some products in the native Magento. Check to see if you have rewrites for this product in the Marketing > SEO & Search > URL Rewrites.
In case some rewrites were missed, you can try to regenerate them with the usage of some 3rd party extension for regenerating URL rewrites.

Warnings regarding Reviews and AggregateRating attribute can occur when your product
doesn't have an approved review. Warnings with Brand or GTIN attributes can occur when you have not defined any attribute code for that particular attribute in the settings of the Advanced SEO Suite extension. You can define those settings in Stores > Configuration > Mirasvit Extension > SEO > SEO Rich Snippets & OpenGraph > Product Page: image

Change Log

2.0.186

(2020-10-21)

Feature

  • Disabling categories on pages of HTML Sitemap

Fixed

  • Trailing slash call Unique constraint violation

2.0.185

(2020-10-15)

Fixed

  • Creating rewrites with trailing slashes when such option disabled.

2.0.184

(2020-10-08)

Fixed

  • Trailing slash apply issue
  • Append toolbar to 3rd party layered navigation issue
  • Adding trailing slashes after prefixes such as html, htm, txt etc.
  • Process sitemap category load exceptions
  • Fixed issue with incorrect alt attribute value
  • Sitemap contains categories and products from another storeview

2.0.183

(2020-09-10)

Improvements

  • Added search for frontend sitemap

Fixed

  • Error on Mirasvit Blog Post page when Post assigned to all the storeviews

2.0.182

(2020-08-28)

Fixed

  • Non applied SEO Friendly Image URLs and ALT Tags templates
  • Invalid header value detected with Magesolution Pagebuilder

2.0.181

(2020-08-18)

Fixed

  • Hide service pages from the frontend sitemap
  • Critical error in LoginAsCustomer module caused by CheckUrlObserver
  • Access to robots.txt with seo toolbar enabled
  • Seo toolbar breaks Codazon MegaMenu binding

Improvements

  • Improve clickable rows for SEO Templates and SEO Rewrites

2.0.180

(2020-08-11)

Improvements

  • Support of GraphQL

2.0.179

(2020-08-04)

Improvements

  • Compatibility with Magento 2.4

2.0.177

(2020-07-20)

Improvement

  • Possibility to define separate usernames in the TwitterCard depended on storeview.
  • New frontend sitemap

Fixed

  • Issue with H1 tags when it defined also in Magento Native SEO
  • Set store specific noindex option
  • Not exported availability with all out of stock childs
  • Empty noindex pages issue
  • Empty offers issue for configurable products when all child products are out of stock or disabled
  • Ignore CMS Pages option missing pages
  • Navigation template was applied everywhere if filter by product
  • Issue with adding SeoToolbar to the download actions
  • Issue with missed attributes in category RS
  • Apply URL key template at the product creation moment
  • Permanent export image friendly URL from the main store when sitemap generates through CLI
  • Duplicating of Product & Category providers on frontend sitemap
  • Issue with unworkable Image SEO Friendly URLs with product flat
  • Added protocol to the og:url attribute
  • Changed parse_url to the strtok for building url of the twitter card
  • Navigation template was applied everywhere if filter by product attribute was applied
  • uasort() expects parameter 1 to be array string given during execution bin/magento app:config:import
  • Show KB articles in sitemap

2.0.176

(2020-05-14)

Fixed

  • Escape alternate tags

2.0.175

(2020-04-17)

Fixed

  • Sitemap issue on multistores when sitemap generates trough cli with argument --all

2.0.174

(2020-03-30)

Fixed

  • Visible placeholder when excluded tags defined
  • Fixed issue with importing posts URL to the Advanced SEO Sitemap

2.0.173

(2020-03-18)

Fixed

  • Product description from seo template wasn't export into rich snippets
  • Duplicated baseUrls in the sitemap item links

2.0.172

(2020-03-04)

Fixed

  • Limits for frontend sitemap
  • Invalid argument supplied for foreach() on Blog Pages with single store installation
  • Performance issue on category pages with enabled Rich Snippet's product offers
  • Category description block wasn't shown in SEO templates

2.0.171

(2020-02-11)

Fixed

  • Missing redirect type
  • Unable to apply images friendly URLs after Template for URL key of Product Images change
  • Use default canonical for navigation pages

2.0.170

(2020-02-04)

Improvement

  • Export of Mirasvit Brand pages into sitemap

Fixed

  • Issue when custom seo template field was empty
  • Module brand alternate URLs when brand was disabled in the one of the storeviews
  • Incorrect URLs of posts from Magefan Blog extension

2.0.169

(2020-01-21)

Improvement

  • Searchbox in Rich Snippets

Fixed

  • Issue with SEO templates conditions
  • Issue with alternate tags when category disabled for one of storeviews

2.0.168

(2020-01-02)

Fixed

  • Sitemap path
  • Invalid argument supplied for foreach()

2.0.167

(2019-12-25)

Improvements

  • Sitemap compatibility with Magefan Blog

Fixed

  • Possible XSS from the backend

2.0.166

(2019-12-23)

Fixed:

  • Unable to apply conditions for SEO templates
  • Don't add links inside tags functionality
  • Product seo template apply child categories issue
  • Duplicate domain in the sitemap URLs

2.0.165

(2019-12-10)

Fixed

  • Undefined variable socialLinks

2.0.164

(2019-12-10)

Fixed

  • Issue with alternate tags on pages Mageplaza Blog

Improvements

  • Social links in Rich Snippets

2.0.163

(2019-12-09)

Fixed

  • Rich snippets incorrect prices round
  • Apply templates for product image url and alt for
  • Hide alternate url for non-visible product
  • Issue with non-well formed numeric price

Improvements

  • Use SEO templates description in rich snippets

2.0.162

(2019-11-18)

Improvements

  • Template Syntax Editor

2.0.161

(2019-11-13)

Fixed

  • Issue when image:caption tag empty
  • Mirasvit blog alternate urls processing
  • Rich Snippets warnings

2.0.160

(2019-11-05)

Fixed

  • Issue with Mageplaza blog URLs (XML Sitemap)
  • Disable Rich Snippet markup for ROOT category (case of Shop by Brand)

2.0.159

(2019-10-31)

Improvements

  • SEO Templates for CMS Pages
  • Autolinks refactoring

Fixed

  • error when trying to add canonical rewrite
  • incorrect minPrice\maxPrice values

2.0.158

(2019-10-15)

Fix

  • Frontend sitemap pager issue
  • Sitemap path issue on Magento EE

2.0.157

(2019-10-07)

Improvements

  • Rich Snippets Reviews for current storeview only.
  • SEO Sitemap refactoring.
  • SEO Sitemap integration with Mageplaza Blog.

2.0.156

(2019-10-04)

Fixed

  • Non well formed numeric value issue with final price

2.0.155

(2019-10-02)

Fixed

  • Missing special price on product rich snippet
  • Alternate urls missing on category page

2.0.154

(2019-09-26)

Fixed

  • Issue with attribute option labels during CLI url generation

2.0.153

(2019-08-27)

Improvements

  • Enable/Disable option for the Rich Snippets on the product pages.

Fixed

  • Pattern [parent_url] exports category name instead of URL.
  • Rich Snippets performance issue on category pages.

2.0.152

(2019-08-15)

Improvements

  • Auto-links setup refactoring

Fixed

  • Issue with custom og:image
  • Serialization issue

2.0.151

(2019-08-08)

Fixed

  • Issue with non applied templates for image URLs

2.0.150

(2019-08-02)

Fixed

  • Issue with AWBlog posts in sitemap
  • Issue with missed image urls in sitemap
  • Issue with trailing slashes in the alt tags
  • Undefined property $moduleManager

2.0.149

(2019-07-24)

Fixed

  • Knowledge Base's alternate tags

2.0.148

(2019-07-12)

Fixed

  • AggregateRating for category pages

2.0.147

(2019-07-11)

Improvements

  • Show / hide disabled and out of stock products in SEO Sitemap
  • Add aggregateRating for category pages (average rating for existing products)

Fixed

  • added low price and hign price for grouped and bundle products
  • Can't apply "is one of" rule
  • Add separate configuration for category rich snippets deletion
  • Missing interface after compilation

2.0.146

(2019-06-05)

Fixed

  • issue with filterattribute_(Nlevel) in Robots Meta Header when SeoFilter enabled

2.0.145

(2019-05-27)

Improvements

  • Set default value for RS priceValidUntil

Fixed

  • Added escape for canonical urls
  • Image SEO friendly urls
  • SEO template can`t set meta title

2.0.144

(2019-05-10)

Improvements

  • SEO Toolbar IPS

Fixed

  • URL generation CLI
  • SEO templates compatibility with Manadev LayeredNavigation

2.0.143

(2019-04-25)

Fixed

  • Canonical Rewrites by conditions
  • Empty seo sitemap link in the footer

2.0.142

(2019-04-16)

Improvements

  • SEO Toolbar

Fixed

  • Canonical Rewrites for products

2.0.141

(2019-04-12)

Fixed

  • Area code issue with n98-magerun2.phar sys:url:list

2.0.140

(2019-04-11)

Fixed

  • Improved performance for some extreme cases
  • Use canonical url for sitemap
  • Issue with disapear rules in Meta Templates
  • SEO Template - Product Rules

Improvements

  • Mirasvit Blog posts sitemap integration
  • Fishpig WordPress blog posts sitemap integration
  • Added Rich Snippets to Mirasvit LayeredNavigation Brand page

2.0.139

(2019-04-01)

Improvements

  • Add seo friendly urls for images of sitemap ([#178]())

2.0.138

(2019-03-29)

Improvements

  • "debug" query param for dispaly toolbar

Fixed

  • Issue with redirect during paypal checkout (if option redirect to lowercase URL is enabled)

2.0.137

(2019-03-22)

Improvements

  • Ability to disable/enable native Meta Title Prefix/Suffix for custom Meta Titles (manually entered or using SEO Templates)
  • Refactoring of cross-links (auto-links) algorithm

Fixed

  • Auto-links add wrong symbols in some configurations

2.0.136

(2019-03-18)

Features

  • Allow to add autolinks to Mageplaza blog posts

Fixed

  • Autolinks are not applied if keyword has a dash (-)

2.0.134

(2019-03-14)

Fixed

  • Autolinks for CMS Static Blocks

Improvements

  • Added autolinks debugger to SEO Toolbar

2.0.133

(2019-03-11)

Fixed

  • Issue with Closure

2.0.132

(2019-03-07)

Fixed

  • Use Current Currency for RS Offer
  • Set main image when SEO-friendly URLs for Product Images enabled
  • Cross-links for Short Description (from content template)

2.0.131

(2019-02-26)

Improvements

  • Added H1 Title to category edit form

Fixed

  • Issue with applying magento variables in seo content
  • Possible array issue with filters

2.0.130

(2019-02-11)

Improvements

  • Refactoring

2.0.129

(2019-02-07)

Improvements

  • Ability to use short description in product rich snippets

Fixed

  • Return OutOfStock, if price is not available
  • Auto links are not applied in some cases

2.0.128

(2019-02-01)

Improvements

  • Breadcrumbs rich snippet: Deepest path, if current path is empty

Fixed

  • Issue with adding rel=next/prev on category page

2.0.127

(2019-01-30)

Improvements

  • Ability to use Template Rules for Layered Navigation selected filters

Fixed

  • Issue with canonical rewrite filters
  • Issue with secret key

2.0.126

(2019-01-23)

Improvements

  • AggregateOffer Rich Snippet for Configurable products

Fixed

  • Rich Snippet final price for simple products (tax)
  • Wrong price in Rich Snippets (if price > 10000)
  • Issue with Z/W chars in seo templates
  • XML sitemap does not include .html suffix for Mirasvit KB URLs

2.0.125

(2019-01-11)

Fixed

  • Issue with item condition

2.0.124

(2019-01-10)

Fixed

  • Possible issue with sitemap generation (Class Mirasvit\Seo\Api\Config\ImageConfigServiceInterface does not exist)
  • Aggregate rating

2.0.123

(2019-01-08)

Improvements

  • Image friendly urls and alts (Magento 2.3)
  • Changed aggregated rating calculation logic (Rich Snippets)

Fixed

  • Issue with apply templates for child categories
  • Possible M2.1 issue: Cannot instantiate interface Magento\Catalog\Model\Product\Media\ConfigInterface
  • Possible issue during update from old versions using manual installtion

2.0.121

(2018-12-19)

Improvements

  • Moved Reviews Snippets to product markup

Fixed

  • Issue with empty description for product rich snippet (if use meta description option)

2.0.119

(2018-12-18)

Fixed

  • Issue with Rich Snippets removing on product page

2.0.118

(2018-12-17)

Fixed

  • Issue with duplication product RS

2.0.117

(2018-12-14)

Fixed

  • SEO alt tags didn't use storeview settings
  • Possible issue with AJAX requests of 3rd party plugins

2.0.116

(2018-12-14)

Fixed

  • Issue with special price in Rich Snippet
  • Changed twitter meta key "property" to "name"

2.0.114

(2018-12-13)

Fixed

  • Issue with page config

2.0.113

(2018-12-12)

Fixed

  • Removing native rich snippets with enabled Page Cache

2.0.112

(2018-12-08)

Fixed

  • Issue with multi-store frontend sitemap

2.0.111

(2018-12-07)

Improvements

  • Leave pagination meta if length limiters are enabled

Fixed

  • Issue with duplication Pagination meta

2.0.110

(2018-12-07)

Features

  • Added option "Don't add automatically" for SEO description

Fixes

  • In some cases, don't show two times CatalogOffer Rich Snippet

2.0.109

(2018-12-06)

Features

  • Add SEO description widget

Improvements

  • Rich Snippets for Category/Product Listing (OfferCatalog)
  • Breadcrumbs Rich Snippet

2.0.106

(2018-12-03)

Fixed

  • Issue with applying product urls for different store views (label option for select)

2.0.105

(2018-11-29)

Fixed

  • Compatibility with Magento 2.3

2.0.104

(2018-11-23)

Fixed

  • Empty attribute

2.0.103

(2018-11-22)

Fixed

  • Issue with H1 Title logic
  • Solved possible issues with AJAX requests of 3rd-party plugins
  • Issue with reviews pagination

2.0.102

(2018-11-20)

Fixed

  • Category Description

2.0.101

(2018-11-19)

Improvements

  • Meta Title

Fixed

  • Issue with Default Category Description

2.0.100

(2018-11-16)

Fixed

  • Sm_ShopBy first page issue

2.0.98

(2018-11-15)

Fixed

  • Prefix&Suffix in title

2.0.97

(2018-11-14)

Fixed

  • Issue with rule validation on product page

2.0.96

(2018-11-12)

Fixed

  • Added Template for SEO description to product rules

2.0.95

(2018-11-09)

Fixed

  • Issue with saving Store View for Templates
  • Areacode issue during CLI sitemap generation

2.0.94

(2018-11-08)

Fixed

  • Migration for template rules
  • Issue with "select" product attributes in meta templates
  • Issue with applying [category_parent_name]
  • Incorrect 'hreflang x-default' for some cases

2.0.93

(2018-11-06)

Improvements

  • Toolbar Information

Fixed

  • Issue with redirect or error on non-native checkout (affected versions since 2.0.86)
  • Reviews are not loaded on product page (affected versions since 2.0.86)
  • Undefined offset in TemplateEngine (affected versions since 2.0.86)

2.0.92

(2018-10-31)

Fixed

  • Issue with Varnish urls

2.0.91

(2018-10-30)

Fixed

  • Issue with category rich snippet

2.0.90

(2018-10-28)

Fixed

  • Issue with pagination meta title
  • Solved issue Argument 2 passed to Magento\Theme\Controller\Result\MessagePlugin::afterRenderResult() must implement interface Magento\Framework\Controller\ResultInterface
  • Refactoring

2.0.87

(2018-10-25)

Improvements

  • Added description position for SEO Rewrites

Fixed

  • Autolinks for SEO description
  • Issue with rewrite url pattern

2.0.86

(2018-10-22)

Fixed

  • Custom template position
  • Minor error during saving of not-valid cms page
  • Issue with Blog sitemap

2.0.85

(2018-08-30)

Fixed

  • Issue with less compile (SM theme)

2.0.84

(2018-08-23)

Fixed

  • Fixed an issue with pub in images urls

2.0.83

(2018-08-20)

Fixed

  • Fixed an issue with mass action for redirects
  • Fixed an absence of home page in xml sitemap (for Magento 2.2.4 and 2.2.5)

2.0.82

(2018-08-20)

Fixed

  • Fixed ability set product urls if Product URL Key Template enabled (for some stores)

2.0.81

(2018-08-08)

Fixed

  • Fixed impossibility use Canonical Rewrite->Regular expression for some pages
  • Issue with Blog sitemap

2.0.80

(2018-08-06)

Fixed

  • Fixed an error "Fatal error: Uncaught Error: Call to undefined method Magento\Catalog\Model\ResourceModel\Category\Collection::getAllAttributeValues() in..." if in Canonical Rewrite use product attribute

2.0.79

(2018-08-02)

Fixed

  • Fixed SEO description position (if set Under Product List)
  • Fixed an issue with redirect for customer_address_form action

2.0.78

(2018-07-30)

Fixed

  • Fixed hreflang x-default (if configured manually)

Features

  • Ability to change category description and category image via SEO templates
  • Ability use redirect chain

2.0.77

(2018-07-20)

Fixed

  • Fixed an issue with tags like {{store url=""}}

2.0.76

(2018-07-19)

Fixed

  • Fixed meta title for not category pages

2.0.75

(2018-07-17)

Fixed

  • Fixed an error: "SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '9-Search Engine Optimization' for key 'EAV_ATTRIBUTE_GROUP_ATTRIBUTE_SET_ID_ATTRIBUTE_GROUP_NAME', query was: INSERT INTO eav_attribute_group (attribute_set_id, attribute_group_name, sort_order, attribute_group_code) VALUES (?, ?, ?, ?)"

2.0.74

(2018-07-02)

Improvements

  • addressRegion snippets
  • Gtin snippets

2.0.73

(2018-06-23)

Fixed

  • Fixed incorrect snippets image url (for some stores)

2.0.72

(2018-06-23)

Fixed

  • bug: Fixed "Wrong Hreflang locale code value" info

2.0.71

(2018-06-21)

Fixed

  • Fixed frontend sitemap error (for big categories)

2.0.70

(2018-06-14)

Fixed

  • bug: Fixed setup:di:compile error

2.0.69

(2018-06-13)

Fixed

  • Fixed frontend sitemap (for some stores)

2.0.68

(2018-06-12)

Fixed

  • Fixed category Open Graph image (if "Category Opengraph" set to "Use first product image")
  • Fixed incorrect snippets

2.0.67

(2018-06-11)

Fixed

  • Fixed redirect loop for home page (if index.php always in REQUEST_URI)
  • Fixed incorrect frontend sitemap redirect loop (for some stores)
  • Compatibility with Mgs/unero theme

2.0.66

(2018-06-01)

Fixed

  • Fixed an issue with redirect for all 404

2.0.65

(2018-05-29)

Fixed

  • Fixed security if "Allow use HTML symbols in meta tags" is enabled

2.0.64

(2018-05-24)

Fixed

  • Fixed incorrect meta description if "Allow use HTML symbols in meta tags" is enabled and symbol '"' exist in meta description

2.0.63

(2018-05-23)

Fixed

  • Fixed description template (for some stores)

2.0.62

(2018-05-03)

Improvements

  • Snippets for Amasty page

Fixed

  • Fixed "pub" in sitemap for images (for some stores)

2.0.61

(2018-04-26)

Fixed

  • Fixed incorrect sitemap image urls for multistores (Magento 2.2.*)

2.0.60

(2018-04-25)

Fixed

  • Fixed incorrect sitemap image urls for multistores with different CDN (Magento 2.1.*)

2.0.59

(2018-04-24)

Fixed

  • Fixed incorrect menu text for multistores if Alternate configured (for some stores)
  • Fixed incorrect images if "Enable SEO-friendly URLs for Product Images" is enabled (for some stores)

2.0.58

(2018-04-24)

Fixed

  • Fixed an error "Fatal error: Uncaught Error: Call to a member function setCurPage() on boolean"

2.0.57

(2018-04-24)

Improvements

  • Additional info for template page

Fixed

  • Fixed Product Short description templates for category page
  • Fixed incorrect H1 tags count in SEO toolbar
  • Fixed sitemap generation error: "Column not found: 1054 Unknown column 't2_thumbnail.value' in 'field list', ..."

2.0.56

(2018-04-18)

Improvements

  • Ability use widget in short and full description template
  • Ability change product short description for categories
  • Ability delete wrong snippets from home page

Fixed

  • Fixed incorrect canonical url for home page if "Add Store Code To Urls" is enabled
  • Fixed Breadcrumbs Rich Snippets for category

2.0.55

(2018-04-17)

Improvements

  • Ability add open graph image for every cms page
  • Ability use widget in SEO description

Fixed

  • Fixed an error: 'Class Aheadworks\Blog\Helper\Sitemap does not exist'
  • Fixed error when "Enable Link Rel="next/prev" is enabled (for some stores)
  • Fixed incorrect Open Graph when "Allow use HTML symbols in meta tags" is enabled
  • Fixed twitter card when cache enabled

Documentation

  • Documentation update

2.0.54

(2018-04-11)

Improvements

  • Allow use HTML symbols in meta tags

2.0.53

(2018-04-06)

Fixed

  • Fixed update error "PHP Fatal error: require(): Failed opening required '...vendor/composer/../mirasvit/module-seo/src/SeoFilter/registration.php' ..."

2.0.52

(2018-04-05)

Fixed

  • Compatibility SeoFilter with manual installation

2.0.51

(2018-04-05)

Fixed

  • Fixed an error "Requested product doesn't exist .../vendor/mirasvit/module-seo/src/Seo/Observer/Canonical.php(249)"

2.0.50

(2018-04-03)

Improvements

  • SeoFilter as additional extension

Fixed

  • Fixed an error "JSON-LD Missing ',' or '}' in object declaration."
  • Fixed an error "Notice: Undefined index: src in .../vendor/mirasvit/module-seo/src/Seo/Helper/Analyzer.php on line 261"

2.0.49

(2018-04-02)

Improvements

  • Friendly image additional check

2.0.48

(2018-03-29)

Fixed

  • Fixed an error "Fatal error: Method Magento\Ui\TemplateEngine\Xhtml\Result::__toString() must not throw an exception, caught Error: Call to a member function getId() on null in .../vendor/magento/module-ui/Component/Wrapper/UiComponent.php on line 0"

2.0.47

(2018-03-28)

Fixed

  • Fixed incorrect symbols for rich snippets
  • Fixed incorrect sitemap path when sitemap is splitted and generated by cron
  • Fixed incorrect redirect

2.0.46

(2018-03-28)

Fixed

  • Fixed incorrect symbols for rich snippets
  • Fixed incorrect sitemap path when sitemap is splitted and generated by cron
  • Fixed incorrect redirect

2.0.45

(2018-03-23)

Improvements

  • Ability use store_mp_brand variable for Mageplaza Shopbybrand brand page

2.0.44

(2018-03-20)

Improvements

  • SEO Rewrites sort order
  • Redirect uppercase to lowercase
  • Ability add custom canonical for product

Fixed

  • Fixed an incorrect product order if 'Enable Link Rel="next/prev"' set to 'Yes'
  • Fixed "SEO description" for "SEO Rewrite"

2.0.43

(2018-03-13)

Fixed

  • Fixed double data register for breadcrumbs
  • Delete invisible symbols during import

2.0.42

(2018-03-09)

Improvements

  • Canonical to store without store code

Fixed

  • Mageplaza Shop By Brand compatibility

2.0.41

(2018-03-05)

Improvements

  • Show website in visibility field
  • Delete wrong snippets automatically

Fixed

  • Fixed "Additional links" config for store
  • Fixed sitemap url if use pub folder

2.0.40

(2018-03-01)

Improvements

  • Prefer https for Cross Domain Canonical URL

2.0.39

(2018-02-19)

Features

  • Ability to add snippets to individual product reviews

2.0.38

(2018-02-14)

Documentation

  • Added information on new features usage to extension's documentation and interface help hints

fixed

  • Compilation error "Incorrect dependency in class Mirasvit\Seo\Observer\Canonical"(for some stores, affected versions 2.0.30 - 2.0.37)

2.0.37

(2018-02-14)

Improvements

  • Different redirect codes for Redirect Management subsystem(301, 302, 307) are now available

2.0.36

(2018-02-13)

Features

  • CLI commands to generate Google sitemap files (php bin/magento mirasvit:seositemap:generate --info | --all | --sitemap_id)

2.0.35

(2018-02-09)

Improvements

  • Twitter Card information can be added to any store frontend page

2.0.34

(2018-02-07)

Features

  • Add Twitter Summary Cards on store product pages

2.0.33

(2018-02-06)

Fixed

  • Checkout page does not load correctly when "Trailing Slash" option is enabled(for some stores)

2.0.32

(2018-02-05)

Fixed

  • Images not displayed when added using WYSIWYG editor on "Edit Product" Admin Panel page and displayed via Product SEO Templates using [product_description] and [product_short_descripption] template variables.

2.0.31

(2018-02-05)

Fixed

  • 'Unique constraint violation found' Exception fixed if SEO Filters enabled(for some stores)

2.0.30

(2018-02-02)

Fixed

  • Fixed canonical link for Home Page on multilingual stores when Web > URI Options > "Add Store Code to URLs" is set to "Yes" and Marketing > Advanced SEO Suite > Settings > "Trailing Slash" is set to "Redirect to the same page without trailing slash"

2.0.29

(2018-01-31)

  • ChangeLog alterations

2.0.28

(2018-01-31)

  • ChangeLog alterations

2.0.27

(2018-01-30)

Fixed

  • Fixed "Requested country is not available." exception for some cases when "Organization snippets" enabled.
  • Fixed Ajax failing with Exception #0 (RuntimeException): Catalog Layer has been already created
  • Fixed "Exception #0 (Zend_Db_Statement_Exception): SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails" for some stores when SEO Filters enabled
  • Fixed empty meta description on category pages(for some stores due to theme specifics or customizations)

Improvements

  • [category_brand_name] variable is added to be used for meta information templates on "Shop By Brand" pages

2.0.26

(2018-01-09)

Fixed

  • Fixed 404 NOT FOUND error if store don't use suffix and SEO Filters enabled
  • XML Google Sitemap links are now generated according to "Trailing Slash" option of Mirasvit Seo(if enabled)

2.0.25

(2018-01-04)

Fixed

  • Fixed compilation error (for magento 2.1.10) After run php bin/magento setup:di:compile you will see following [ReflectionException] Class Magento\Catalog\Model\View\Asset\ImageFactory does not exist

2.0.24

(2017-12-28)

Fixed

  • Fixed generation of Product Images Alt and Title for category page (for magento 2.1.6)
  • Fixed minor issue with mass status changes for SEO rewrite in admin panel
  • Fixed redirecting from URLs with URL parameters

2.0.22

(2017-12-14)

Fixed

  • Fixed error with friendly URLs for Product Images (for magento 2.1.6)

2.0.21

(2017-12-11)

Fixed

  • "Notice: Undefined variable: formattedMinPrice" fixed for category snippets on some stores

2.0.20

(2017-12-11)

Documentation

  • Documentation for new functionality added

2.0.19

(2017-12-07)

Fixed

  • Product rich snippets fixed

2.0.18

(2017-12-07)

Fixed

  • Stability adjustments introduced
  • Fixed "Uncaught Error: Call to a member function getAttribute() on null" for vendor attribute on some stores

2.0.17

(2017-11-27)

Fixed

  • Fixed admin load time issue.

2.0.16

(2017-11-20)

Fixed

  • Fixed the long page load if too much html tags

2.0.15

(2017-11-16)

Fixed

  • Fixed incorrect votes snippets (from 2.0.14)

2.0.14

(2017-11-14)

Features

  • Snippets using JSON-LD

2.0.13

(2017-11-14)

Improvements

  • Added "ratingCount"

2.0.12

(2017-11-07)

Fixed

  • Compatibility with helpdesk

2.0.11

(2017-10-31)

Fixed

  • Fixed compilation error.

2.0.10

(2017-10-19)

Features

  • SEO-friendly URLs for Product Images

2.0.9

(2017-10-17)

Fixed

  • Fix setup:di:compile error

2.0.8

(2017-10-17)

Fixed

  • Template rule compatibility (magento 2.2)

2.0.7

(2017-10-13)

Fixed

  • Fixed setup:di:compile error
  • Fixed an error with serializer (magento 2.2)
  • Fixed an error if rule enabled

2.0.6

(2017-10-10)

Fixed

  • Fixed an error:"Unknown module(s): 'Mirasvit_SeoFilter'"

2.0.5

(2017-10-09)

Features

  • Seo filters
  • Canonical rewrite

Fixed

  • Patch to prevent "Exception: Warning: Invalid argument supplied for foreach()" for some stores
  • Fixed an error if use setup::install

Documentation

  • Documentation improvement

2.0.4

(2017-09-29)

Fixed

  • Fixed an error with rules (magento 2.2)

2.0.3

(2017-09-27)

Fixed

  • Magento 2.2 compatibility

2.0.2

(2017-09-25)

Fixed

  • Disable command

2.0.1

(2017-09-18)

Improvements

  • Manual links

Fixed

  • Fixed Mirasvit Blog sitemap for multistores
  • Fixed Mirasvit Kb sitemap for multistores
  • Fixed sitemap generation by cron
  • Fix alternate tags issue
  • Compatibility with Codazon Fastest theme

2.0.0

(2017-08-30)

Improvements

  • Refactoring

1.0.80

(2017-08-30)

Improvements

  • Refactoring

1.0.79

(2017-08-30)

Improvements

  • Refactoring

1.0.78

(2017-08-29)

Fixed

  • Fixed incorrect canonical if Trailing slash enabled
  • Fixed an error (for Magento 2.0.x)

1.0.77

(2017-08-15)

Fixed

  • Fixed sitemap folder

Documentation

  • Online manual enhancement

1.0.76

(2017-08-14)

Improvements

  • User interface minor improvement

Fixed

  • Fixed alternate tags bug

1.0.75

(2017-08-03)

Fixed

  • Minor Mirasvit Knowledge Base compatibility

1.0.74

(2017-08-01)

Improvements

  • Added ability to define unique Organization snippets information for different store views
  • Added ability to define SEO Toolbar position

1.0.73

(2017-07-28)

Improvements

  • Mirasvit Knowledge Base sitemap

Fixed

  • fixed missing Opengraph tags for Home page
  • Fixed missing Rich Snippets Breadcrumbs of BreadcrumbList type on product pages
  • Fixed an issue of duplicating Hreflang locale code on product pages(for some stores)

1.0.72

(2017-07-27)

Fixed

  • Fixed incorrect meta tags for layered navigation

1.0.71

(2017-07-24)

Improvements

  • User Interface adjustments

Documentation

  • Online User Manual updated

1.0.70

(2017-07-21)

Improvements

  • compatibility with Page Cache Warmer version 1.0.33

1.0.69

(2017-07-13)

Improvements

  • Canonical for Magefan_Blog

Fixed

  • Fixed sitemap issue
  • Fixed an issue with incorrect links limit per page

1.0.68

(2017-06-23)

Fixed

  • Fixed an issue with incorrect links limit per page

1.0.67

(2017-06-23)

Fixed

Message product key already exists for the following product on mirasvit:seo --apply-product-url-key-template execution now does not stop command from applying URL-key template for other matching products in a row


1.0.66

(2017-06-22)

Fixed

  • Fixed caching issue

1.0.65

(2017-06-20)

Documentation

  • Online User Manual updated

1.0.64

(2017-06-16)

Fixed

  • "The filter must be an object. Please set a correct filter" error fixed(for some stores)
  • Performance issue fixed for attributes block on product view page

1.0.63

(2017-05-31)

Improvements

  • Rich Snippets accuracy and price formatting improved

Fixed

  • Incorrect Robots meta header tags config data (magento 2.2.0-dev)

1.0.62

(2017-05-24)

Fixed

  • Incorrect alternate tags config data (magento 2.2.0-dev)

1.0.61

(2017-05-23)

Features

  • Ability to define product images alt, title and caption tags for frontend and Google sitemap

1.0.60

(2017-05-22)

Features

  • Ability add alternate tags for any stores combinations

Fixed

  • Fixed child category sitemap
  • Fixed cms alternate group issue
  • Fixed an error with circular dependency

1.0.59

(2017-05-04)

Improvements

  • Auto Links documentation and example CSV file actualized

Fixed

  • Fixed breadcrumbs design issue when SM Himarket extension installed

Documentation

  • General user manual adjustments made

1.0.58

(2017-04-24)

Improvements

  • "Apply to child categories" setting added to make SEO Templates management more flexible

1.0.57

(2017-04-10)

Features

  • Ability add seo description in any template

Improvements

  • Сompatibility with Magefan_Blog

Fixed

  • Fixed alternate tags for Amasty Xlanding page

1.0.56

(2017-03-30)

Fixed

  • Fixed issue with ability download Import Links example

1.0.55

(2017-03-30)

Fixed

  • Fixed issue with ability download Import Links example

1.0.53

(2017-03-28)

Fixed

  • Fixed Open Graph issue

1.0.52

(2017-03-27)

Features

  • Ability use paths of templates to add links inside

Fixed

  • Fixed an error if can't get image url
  • Fixed sitemap error if blog haven't category

1.0.51

(2017-03-23)

Improvements

  • Amasty_Xlanding compatibility
  • Cut category additional data for alternate url
  • Delete 'home' for home page in sitemap
  • Paginated canonical
  • Manufacturer part number snippets
  • Trailing slash
  • AW Blog sitemap

Fixed

  • Fixed mysql error "Unknown column 't2_name.value'"
  • Fixed an issue with Product URL Key Template

1.0.50

(2017-02-14)

Improvements

  • Ability set Max Length for Product Name and Max Length for Product Short Description

1.0.49

(2017-02-13)

Fixed

  • Fixed an issue with paypal "Skip Order Review Step"

1.0.48

(2017-02-13)

Fixed

  • Fixed an issue with paypal "Skip Order Review Step"

1.0.47

(2017-02-10)

Fixed

  • Fixed redirect issue
  • Fixed ad issue with incorrect meta tags on brand page

1.0.46

(2017-01-30)

Improvements

  • Added ability use x-default alternate tag
  • Ability use different positions for SEO Description

Fixed

  • Fixed an issue with incorrect snippets for an empty category
  • Fixed an issue with double slash in canonical (forsome stores)
  • Fixed an issue with HTML5 validation

1.0.45

(2017-01-25)

Improvements

  • Store template improvement
  • Toolbar overflow

Fixed

  • Fixed an issue with adding robots tags (for some pages)
  • Fixed issue with broken html on product page (if snippets enabled)
  • Fixed an issue with incorrect title

1.0.44

(2017-01-16)

Fixed

  • Fixed seo rewrite issue for contact page
  • Fixed redirect for account/create page

1.0.43

(2017-01-10)

Improvements

  • Ability show seo toolbar depending from cookie

Fixed

  • Fixed an issue with store template

1.0.42

(2016-12-29)

Improvements

  • Ability set new condition snippet for all products

1.0.41

(2016-12-27)

Fixed

  • Fixed notice

1.0.40

(2016-12-26)

Fixed

  • Fixed an issue with check url observer (sql query throw error)

1.0.39

(2016-12-23)

Fixed

  • Fixed an issue with displaying seo description block

1.0.38

(2016-12-09)

Improvements

  • Compatibility with M2.2

1.0.36

(2016-12-08)

Fixed

  • Fixed division by zero error

1.0.35

(2016-12-07)

Features

  • BreadcrumbList snippets

1.0.34

(2016-11-24)

Fixed

  • Fixed an issue with incorrect rich snippets

1.0.33

(2016-11-21)

Features

  • Ability export redirects

1.0.32

(2016-11-11)

Fixed

  • Fixed an issue with incorrect alternate tags (for some stores)
  • Fixed error if slash exist in autolink keyword

1.0.31

(2016-11-08)

Fixed

  • Fixed an issue with page load delay (if large number of redirects with *)

1.0.30

(2016-11-07)

Improvements

  • Compatibility with extension Mirasvit CacheWarmer version 1.0.1

1.0.29

(2016-10-27)

Fixed

  • Fixed an issue with SEO template error

1.0.28

(2016-10-24)

Fixed

  • Fixed an issue with users roles

1.0.27

(2016-10-18)

Fixed

  • Fix compilation error

1.0.26

(2016-10-18)

Fixed

  • Fixed an issue with FPC performance

1.0.25

(2016-10-12)

Fixed

  • Fixed an issue with redirect error

1.0.24

(2016-10-12)

Improvements

  • Use the same font-awesome.min.css for all extensions

1.0.23

(2016-10-10)

Improvements

  • Ability set store id in import file

Fixed

  • Fixed an error if get parent category data

1.0.22

(2016-10-06)

Fixed

  • Fix notice
  • Fixed an issue with broken design (for some stores)
  • Fixed an issue with incorrect store code in URL for Autolinks
  • Fixed an issue with Cross Domain Canonical
  • Fixed an issue with attribute error

1.0.21

(2016-09-28)

Fixed

  • Fix compilation error

1.0.20

(2016-09-27)

Fixed

  • Fix undefined index notice
  • Fixed an issue with attribute error

1.0.19

(2016-09-26)

Fixed

  • Fixed an issue with snippets comma in price

1.0.18

(2016-09-22)

Fixed

  • Fixed an issue with filter attributes for robots tags

1.0.17

(2016-09-22)

Fixed

  • Fixed an issue with robots tags for search pages

1.0.16

(2016-09-20)

Fixed

  • Fixed notice

1.0.15

(2016-09-19)

Features

  • Ability change product url key by template

1.0.14

(2016-09-12)

Fixed

  • Fixed breadcrumbs issue for venustheme

1.0.13

(2016-09-07)

Fixed

  • Fixed an issue with excluding pages from XML sitemap

1.0.12

(2016-08-23)

Fixed

  • Fixed an issue with wrong title on home page

1.0.11

(2016-08-22)

Features

  • Added ability to use a longest product url as canonical

Fixed

  • Fixed an issue with incorrect aggregate rating value

1.0.10

(2016-08-08)

Fixed

  • Fixed an error if Category Opengraph set as Use first product image

1.0.9

(2016-08-05)

Fixed

  • Fixed an issue with error if run setup:di:compile (affects from 1.0.8)

1.0.8

(2016-08-04)

Features

  • Added ability to remove parent category path for category urls

1.0.7

(2016-07-19)

Fixed

  • Fixed links for "Example of CSV file" for Redirects and Autolinks

1.0.6

(2016-07-12)

Documentation

  • Fix My Downloadable Products link

1.0.5

(2016-06-30)

Fixed

  • Fixed an issue with configuration Robots Meta Header in admin panel
  • Fixed an issue with error if get parent category data

1.0.4

(2016-06-24)

Improvements

  • Support of Magento 2.1.0

1.0.3

(2016-05-17)

Fixed

  • Issue with wrong case of some filenames

1.0.2

(2016-05-12)

Improvements

  • Ability to autolink product attributes too
  • Backend menu
  • Improved SEO Toolbar

Fixed

  • Fixed an issue with saving configuration in magento 2.0.5
  • Fixed an issue with saving new customer address

1.0.1

(2016-04-01)

  • Added breadcrumbs depending on CMS Page Settings
  • Added breadcrums on sitemap page

1.0.0

(2016-02-29)

  • Initial release