Hi James.

It sounds like you've got a fairly interesting language setup to start with given the non-standard languages (e.g. es-GB) and the extra segment used to identify the locale (e.g. /gb/es rather than /gb-es). Are the languages set up as separate language branches in the CMS or do those languages exist as separate nodes within the site tree?

Hey Paul

Indeed this is an interesting one. We know it's slightly against best practice but it stems from some old SEO practices that we must temporarily inherit into a new website build to keep our SEO ranking intact for now.

For some reason the forums aren't allowing me to attach images at this moment in time, so to explain the CMS tree, we've got the root page followed by a "Country Home Page" representing each of the countries (or "markets)"

CMS Root
  - BE
    - About
    - Services
    - ... etc
   - GB
    - About
    - Services
    - ...etc
  - NL
  - FR
  - ES

So by default, we'd access these country pages like so:

example.com/be

example.com/be/about

example.com/be/services

example.com/nl/

... etc

But then these country pages can have multilingual variants. And as soon as this is switched on, as you know, the language segment comes into play in the URL, by default:

example.com/en/be/about

..and as you suggest, this isn't good practice. It really should be example.com/be/en/about

So this is where it's getting a bit confusing - I'm trying to get some programmatic exposure over the language segment in the URL, so that I can apply some rules to it.

Firstly, to change the location of language segment so instead of example.com/en/be - we can bring it more inline with best practice SEO which would be example.com/be/en 

And secondly to ditch the language segment completely when only one language is available.