@MontseCano @seoconspiracy @schachin @robinlmay @RemcoTensen @OmiSido @GrowMap @gramm_football @simmonet @micahfk @searchrook @moniscope @rhyswynne @zigojacko @googleadviseur @rustybrick @AndyBeard @bhartzer @DavidAmerland @essentialskill @jennyhalasz @dergal @anton_shulke @laurentbourelly @LordManley @searchmartin @RebBerbel @_PaulLovell @JohnMu @JudithLewis @ChrisSimmance @StockbridgeT @KellyStanze @PeterHatherley @eYordanov @SEOJoBlogs @boggles @robwatts @RafaelMontob @JeffreyJDavis @CrystalontheWeb @witczyk @chrisgreenseo @linda_tweet @Sugarsteroni @SERanking @YumEarth @DominiqueCardon As in, based on the visitor IP Address?
This is usual done for Language, and sometimes for Business (availability, restrictions etc.).
The only "legitimate" and "sensible" use case is sensitive content (products/services/topics that are illegal in the visitors country).

@MontseCano @seoconspiracy @schachin @robinlmay @RemcoTensen @OmiSido @GrowMap @gramm_football @simmonet @micahfk @searchrook @moniscope @rhyswynne @zigojacko @googleadviseur @rustybrick @AndyBeard @bhartzer @DavidAmerland @essentialskill @jennyhalasz @dergal @anton_shulke @laurentbourelly @LordManley @searchmartin @RebBerbel @_PaulLovell @JohnMu @JudithLewis @ChrisSimmance @StockbridgeT @KellyStanze @PeterHatherley @eYordanov @SEOJoBlogs @boggles @robwatts @RafaelMontob @JeffreyJDavis @CrystalontheWeb @witczyk @chrisgreenseo @linda_tweet @Sugarsteroni @SERanking @YumEarth @DominiqueCardon The problem is, it's often done (naively) as a UX thing,
to put the content in a visitors language,
(blindly assuming people visiting from Germany speak German, and not Lang-X),
and fail to check (or ignore) a.lang headers etc.
Which upsets a % of visitors, and can screw SEO.

@MontseCano @seoconspiracy @schachin @robinlmay @RemcoTensen @OmiSido @GrowMap @gramm_football @simmonet @micahfk @searchrook @moniscope @rhyswynne @zigojacko @googleadviseur @rustybrick @AndyBeard @bhartzer @DavidAmerland @essentialskill @jennyhalasz @dergal @anton_shulke @laurentbourelly @LordManley @searchmartin @RebBerbel @_PaulLovell @JohnMu @JudithLewis @ChrisSimmance @StockbridgeT @KellyStanze @PeterHatherley @eYordanov @SEOJoBlogs @boggles @robwatts @RafaelMontob @JeffreyJDavis @CrystalontheWeb @witczyk @chrisgreenseo @linda_tweet @Sugarsteroni @SERanking @YumEarth @DominiqueCardon The more acceptable method is:
1) Ensure all content is served with Lang headers
2) Utilise hreflang (properly)
3) Check the UA, IP and A.Lang header
4a) If an SE Bot, leave alone
4b) If not, fire off a modal popup (or inject an in-content block) stating Lang X, link to Lang Y.

@MontseCano @seoconspiracy @schachin @robinlmay @RemcoTensen @OmiSido @GrowMap @gramm_football @simmonet @micahfk @searchrook @moniscope @rhyswynne @zigojacko @googleadviseur @rustybrick @AndyBeard @bhartzer @DavidAmerland @essentialskill @jennyhalasz @dergal @anton_shulke @laurentbourelly @LordManley @searchmartin @RebBerbel @_PaulLovell @JohnMu @JudithLewis @ChrisSimmance @StockbridgeT @KellyStanze @PeterHatherley @eYordanov @SEOJoBlogs @boggles @robwatts @RafaelMontob @JeffreyJDavis @CrystalontheWeb @witczyk @chrisgreenseo @linda_tweet @Sugarsteroni @SERanking @YumEarth @DominiqueCardon >>>
5) If permitted, set a cookie (or use local storage) to remember their language preference.
In the case of "requirements",
replace (4b) with an interstitial (full sized locked modal/page) - explaining that X is not available/they aren't permitted to show it to the visitor