Understanding HREFLang Builder Error Codes
July 30, 2018
Set Country and Language Syntax
July 31, 2018

Read Me – Selecting your Country/Language Syntax

Attention:  This is one of the most critical steps to successfully use HREF Builder.  It is from this setting that we can effectively match your URL’s to each other to create the XML files.  Currently, we have been able to account for 88 of over 100 different URL structures that sites use for their global content.

You will have a variety of options to choose from so please review the following considerations for setting this element.  Note: if you do not see a version that matches your site it will require a custom regex which you can learn more about on our Developing a Custom Regex FAQ page.  If you have a question about any of the options that are not clear review our URL Structure Overview Table. 

Many sites follow a standard Country Code/Language Code Syntax where the country and language folders are easily identified.  Such as the UK site is managed under www.mydomain.com/en/uk/ or uk/en type structure and this is uniform across the counties. This can also work for those that use /en-uk/ and en_uk structures.  To use this one simply find the one that matches and select it.

Question:  How are the MAJORITY of my country language sites set up. 

Currently, the default option of the tool is a single format setting. We are working on allowing a user to combine multiple versions but for now, we have to develop a custom regex filter to handle these variations.  If your country and language deviate format in any way or you have special considerations read below.

Special Consideration:

Regional Language Versions – while we know there is no country called LATAM or APAC many sites do this for their regional Spanish or English sites. These are often mapped as /latam/ or /apac/en/ so this makes it hard to map these. We have built-in detectors for you to find URL’s with /apac and then assign them to a single or multiple countries in the region.  For more information please review Using HREFLang for Regional Sites.

Non-Standard Folders and Country Codes –  we have encountered a number of multinationals that have the business unit or product folders before the country and language designators.  For example www.bigglobalco.com/business_unit/us/en.  For this syntax, we have developed a “Regex” element that allows you to tell the too where your country and language elements are located.

Language or Country Parameters –  unfortunately, if you are using a top-level domain and language or country parameters to designate the pages for each country or language we may not be able to build an HREF for these pages as they most likely are not unique pages.  A number of sites use Java plugins that “replace” local language elements but use the same base URL.  If you use country and/or language parameters please contact us at help@hrefbuilder,com and we can review the site.

Default Language  –  If you have a global site that is not associated with any country or language or if you use IP detection you can set any version of the site to be the default version.  Setting x-default language option we can tell the search engines this is the version to show when there is not a designated local version.

Country Code but Non-Local Language – Do you have a site for Norway but the content is in English? Most tools would assign /no/no/ to these URL’s but it actually needs to be created as /no/en – our tool allows you to map a unique country site but set the language to English.  If you have the URL structure as en-no or no-en then we can map that without variation.

Global Language Version – this is the case where you do not use country designators but have common languages.  For example, if you use a /es version for “any” Spanish speaking countries then we can set it as “Global Spanish.”  You can do this by selecting the global language related to the site.

Post Import Considerations:  

If your “View Files” screen has rows of red highlights these are imported source files that we could not be understood by the import tool.  In this example below the user set their import to equal www.mysite.com/uk/ when in fact they were using a format of www.mysite.com/en/uk so we could not understand the locations of the actual pages.  You can fix this by clicking edit and assigning these files to a specific country and language combination or reimport them selecting the correct option.