Overview
Back to topMany Magento®2 stores translate content on the product and category pages into different languages in order to cater to customers from different parts of the world. With the Alternate Hreflang Tags extension, which is commonly known as rel="alternate" hreflang="language code", each page's language is made known to Google so that it will match the user's searching in that language to pages which are in the same language. The Hreflang enhances your SEO without you having to code it yourself.
With this extension, you can Group the right language store views together so the Href Lang tags will be generated to tell Search Engines if there are any alternative languages available for the product, category, or Homepage.
Features
- Turnkey Alternate Href Lang Tag Solution
- Easy and Fast configuration
- Build by the latest Google Standards
- Comes with complete Documentation
- Works with the latest versions of Magento 2
Technical Product Features
- Made according to the latest Google standards
- Specially designed for Magento
- Easy to set configuration
- Easy installation
- Positive SEO effect
Examples
In this way, the group with Href Lang Tags will look like:
- < link rel= ”alternate” hreflang=”nl” href=”http://www.yourmagentostore.nl” > Tell's Google that the specific product or category is also available in Dutch.
- < link rel= ”alternate” hreflang=”nl-be” href=”http://www.yourmagentostore.be/” > Tell's Google that the specific product or category is also available in dutch but for the country Belgium.
- < link rel= ”alternate” hreflang=”fr” href=”http://www.yourmagentostore.fr/ > Tell's Google that the specific product or category is also available in French.
New
Alternate HrefLang Tags for CMS Pages: The HrefLang Tag Extension can recognize the different URLs for the products and categories based on the different store-views, but for CMS pages it's made up of a different data structure. With the new CMS categorize functionality, it's now possible to categorize them to connect them with categories to connect them with the half long tags. Every CMS page with the same connected category tag will be will be identified as alternate pages.
For example, there can be three store-views with three distinct "contact us" pages:
- [storeview] magmodules.eu - identifier: contact-us
- [storeview] magmodules.nl - identifier: neem-contactop
- [storeview] magmodules.de - identifier: Kontakt
By giving each of the three CMS pages the category "contact us", the three pages will be linked as related and the hreflang tag will be added automatically.
What Is Hreflang?
What is the rel=”alternate” hreflang=”Language code”? Introduced in 2011, the Hreflang attribute indicates the page language and makes the relationship between content pages of different languages known to search engines such as Google. This is handy for Magento®2 shops which have multiple storefronts in varying languages catered towards a variety of consumers while selling the same products. If different storefronts selling the same product are linked with the Hreflang attribute, search engines will know which page to direct the customer to. A product page with both a Spanish and an English version will be tagged as "Español" by using hreflang="es”.
A customer with an IP address from a Spanish country will be directed from the Google search result to the Spanish page version instead of the English one. By ensuring that your target consumers are directed to the most relevant page in their language, your bounce rate will decrease and your conversions will increase.
Instead of targeting consumers based on their language, we are also able to target consumers based on their country. For instance, a Belgium storefront using a Dutch language pack. Using two different stores, a Dutch storefront and a Belgium storefront, we are able to target different consumers with different product pages: a Dutch one (hreflang="nl-nl") and a Belgium one (hreflang="nl-be"). This is especially handy when it comes to geo-targeting consumers for changes in currency, shipping costs, seasonality, and culture.
Technical Specifications
Back to topSeller profile
Seller contact
Current Version
1.5.0
Adobe Commerce platform compatibility
Adobe Commerce (cloud): 2.4 (current), 2.3 (obsolete)
Adobe Commerce (on-prem): 2.4 (current), 2.3 (obsolete)
Magento Open Source: 2.4 (current), 2.0 (obsolete), 2.1 (obsolete), 2.2 (obsolete), 2.3 (obsolete)
Type
Stable Build
Updated
06 February, 2024
Categories
Extensions, Marketing, SEO/SEM
Quality Report
Back to topAll tests were conducted on the latest versions of Adobe Commerce that existed for the compatible release lines at the moment of the extension submission. Latest versions of all other software were used, as applicable.
Release Notes
Back to top1.5.0:
- Compatible with Adobe Commerce (cloud) : 2.3 2.4
- Compatible with Adobe Commerce (on-prem) : 2.3 2.4
- Compatible with Magento Open Source : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
Changes:
* Added support for Firebear Improved Configurable Product
1.4.0:
- Compatible with Adobe Commerce (cloud) : 2.3 2.4
- Compatible with Adobe Commerce (on-prem) : 2.3 2.4
- Compatible with Magento Open Source : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
Changes:
* Revamped admin config
* Remove alternate urls for stores that are disabled
1.3.8:
- Compatible with Adobe Commerce (cloud) : 2.3 2.4
- Compatible with Adobe Commerce (on-prem) : 2.3 2.4
- Compatible with Magento Open Source : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Small code cleanup.
1.3.7:
- Compatible with Adobe Commerce (cloud) : 2.3 2.4
- Compatible with Adobe Commerce (on-prem) : 2.3 2.4
- Compatible with Magento Open Source : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Fixed general enable flag
1.3.6:
- Compatible with Adobe Commerce (cloud) : 2.3 2.4
- Compatible with Adobe Commerce (on-prem) : 2.3 2.4
- Compatible with Magento Open Source : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Make Logger component compatible with Monolog 2.0
* Replaced deprecated _redirect method
* Declared visibility on all constants
1.3.5:
- Compatible with Adobe Commerce (cloud) : 2.3 2.4
- Compatible with Adobe Commerce (on-prem) : 2.3 2.4
- Compatible with Magento Open Source : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Refactored header template file for cleaner output without extra line endings / indents
1.3.4:
- Compatible with Adobe Commerce (cloud) : 2.3 2.4
- Compatible with Adobe Commerce (on-prem) : 2.3 2.4
- Compatible with Magento Open Source : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Get category url from UrlRewrite for better performance when using lots of storeviews
* Fixed ACL rights
1.3.2:
- Compatible with Magento Open Source : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Added fallback on getting product url by store id for faulty records in url_rewrite table
1.3.0:
- Compatible with Magento Open Source : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Added compatibility for Amasty Shop By Brand
* Moved all config options to config repository interface
* Coding styles and check on exclusive canonicals
1.2.0:
- Compatible with Magento Open Source : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
New: Refactoring of code
New: Added extensive self-test function
New: Added extensive error log function
New: Added extensive debug log function
New: Added compatibility for Magento 2.4
1.1.7:
- Compatible with Magento Open Source : 2.2 2.3
- Stability: Stable Build
-
Description:
* Fixed; check if product is linked to store
* Added; support for Magento 2.3.x
1.1.2:
- Compatible with Magento Open Source : 2.1 2.2
- Stability: Stable Build
-
Description:
* Fixed product alternate check
1.1.1:
- Compatible with Magento Open Source : 2.1 2.2
- Stability: Stable Build
-
Description:
* Improved debug output messages
* Small bug fixes
1.1.0:
- Compatible with Magento Open Source : 2.1 2.2
- Stability: Stable Build
-
Description:
* Added CMS Pages Href Lang Tag compatibility
1.0.5:
- Compatible with Magento Open Source : 2.1 2.2
- Stability: Stable Build
-
Description:
* Added compatibility for Magento 2.2
1.0.4:
- Compatible with Magento Open Source : 2.0 2.1
- Stability: Stable Build
-
Description:
* Extended groups
1.0.2:
- Compatible with Magento Open Source : 2.0 2.1
- Stability: Stable Build
-
Description:
- Small fixes
1.0.1:
- Compatible with Magento Open Source : 2.1
- Stability: Stable Build
-
Description:
* Small bugfixes (compilation)
1.0.0:
- Compatible with Magento Open Source : 2.1
- Stability: Stable Build
-
Description:
Initial Release
Support
Back to topThe best place to start if you need help with a specific extension is to contact the developer. All Adobe Commerce developers have both a contact email and a support email listed.
Contact Vendor