Localized Directory and URL Mapping

In talking to multinational site owners, one of the main reasons many global sites do not use HREFLang elements is their inability to map localized URLs.

HREFLang Builder automatically maps all URL’s that are the same despite the number of languages.  For example, If you have 10 English language URL structures that are the same across markets, then they will all be mapped by default.  If the URL’s are localized or the structure changes  across countries, the user will need to use one of the options below to map them to each other.

  • Method 1 – Matching Localized Directories/Sub Directories – the user selects one or multiple local directory names from URLs and assigns them to a master classification. This works well if only a category or subcategory directory has been localized. We can show these on the screen and the user can select them and map them.   Alternatively, you can upload a mapping file of the different version and dynamically map them.

 

  • Method 2 – Matching Localized URL’s – the user selects one or multiple local directory names from URLs and assigns them to a master classification. This works well if only a category or subcategory directory has been localized. We can show these on the screen and the user can select them and map them.   Alternatively, you can upload a mapping file of the different version and dynamically map them.

 

  • Method 2 – Matching Product Code or Parameter in URL – Sites that use a unique product parameter in the URL representing an SKU or a category can map each variable across languages to all equivalent pages. We just need to upload a master list of the product SKU’s and the system will match them no matter the language of the URL.

 

  • Method 3 – Local/Global ID Meta Tag Mapping – A number of eCommerce systems use productID or other unique identification tags on their pages. Once we tell our system where to look for that tag we can import it during the diagnostic process and map all pages that have the same tag.  The ID’s are mapped and parsed out into HREFLang alternate blocks in the XML site maps. This spans different URL structures, CMS and languages very efficiently.

 

  • Method 4 – Local/Global ID Mapping – Similar to the previous method of using a unique product ID in this case we take that ID from the client’s ERP system and map the pages in a database and import the matching table into HREFLang Builder. For a few larger sites with complex structures and product ID’s we have been able to leverage this successfully with customized mapping and management.

 

We have built a few other custom mapping solutions for clients that have very unique requirements.   If you have a site that the above solutions do not match please contact us to see if we can develop something custom.