The Dirk answer points to some potential answers.

Said that, when I click on your SERP's link, I see others sitelinks (just two):

• the first >>> Robes
• the second >>> Вся распродажа.

As Dirk pointed out, your site has detected my IP (quite surely, but maybe it is user agent), and when I click on the second sitelink I see this url: http://www.revolveclothing.es/r/Brands.jsp?aliasURL=sale/all-sale-items/br/54cc7b&&n=s&s=d&c=All+Sale+Items.

The biggest problem, when it comes to IP redirections, is that they are a big problem in terms both of SEO and usability:

1. SEO, because googlebot (and others bots) will mostly be redirected to the USA version due to their IPs, even though Google crawls site also from datacenters present in other country (but much less);
2. Users, because you are making impossible, for instance, to a Spanish user to see the Spanish site whenever they are not in Spain. And that really sucks and pisses off users.

There's a solution:

1. making the IP redirection just the first time someone click on a link to your site and if that link is not corresponding to the version of the country from were users and bots are clicking;

2. presenting the links to the others country versions of your site, so that:

3. bots will follow those links and discover those versions (but not being redirected again);

4. users are free to go to the version of your site they really need (but not being redirected again if coming from those country selector links).

Said that, it would be better using a system like the one Amazon uses, which consists not forcing a redirection because of IP, but detecting it and launching an alert on-screen, something like: "We see that you are visiting us from [Country X]. Maybe you will prefer visiting [url to user's country site]".

Then, i just checked the hreflang implementation, and it seems it was implemented correctly (at least after a very fast review with Flang).

I tried to search for "Resolve clothing" in Spain incognito and not personalized search, and it shows me the Spanish website and Spanish sitelinks correctly;

I tried the same search from Spain but letting Google consider my user-agent (setup for English in search), and I saw the .com version and English sitelinks (which is fine).

Remember, sitelinks are decided by Goggle and we can only demote them.

To conclude, I think the real reason has to be searched not in a real international SEO issue (but check out the IP redirection), but to a possible and more general indexation problem.

HI!

As the previous answer says, you must always present all the countries and languages (or just languages) related hreflang annotations as many are the multicountry/multilingual version of your site.

So your own first question (My question is, do both of these tags need to be on both the Spanish and English version of the page?) is the correct answer.

Using the hard coded hreflang or the sitemap option is indifferent.

Regarding why Google is caching the .be flemish version of your website, instead of the .nl one, I sincerely have no answer to give you, but - with the few information I have about it right now - what I would look is at the CMS you are using, in the case you have a centralized CMS that then distributes the content along the domains.

Your case is weird, because that something I usually experience with hacked sites.

I put this in discussion, and ask others to give their answer.

Hi  Alan!

yes, I was saying exactly that. If you're going for an international multi-country SEO and you have to deal with countries that share language, like in the case of Ireland and Uk, it is better to target them with two different "sites" (being a site in a ccTld or subfolder or sibdomain, depending on business convenience).

if you're doing multi-cointry SEO and one of your targeted counties has 2+ official languages, then the ideal solution is having a ccTld for that country and creating as many subfolder translated versions as are the official languages of that country.

For instance:

www.domain.be, with the French version appended from the root,

www.domain.be/nl/, with the Flemish translated version.

As alternatives be you can redirect 302 via user agent from domain.com to /fr/ or /nl/, while always letting users to eventually choose the alternate version via language selector.

Hi Alan and Matt,

I am sorry to tell you that if you set up the hreflang for "Europe" as hreflang="en-GB", that won't work.

That annotation, in fact, tells Google to show the URLs having it only to users searching in English from Great Britain.

It would be better to use only "en" in European website.

Said that, this is not the best solution either, because it is telling Google: "show this to users searching in English globally (but not if they are in the USA).

If the European web site is meant to reach users who not necessarily are using English as default language (eg: Spanish, French, Italians, Germans et al), than a solution could be tagging the European website with the "x-default" hreflang.

Note, though, that this a quite extreme use of the x-default.

The big mistake, anyway, is creating an European website itself:

1. Google does not consider political regions like European Community nor continents and geographical areas like "Asia", "Middle East", "Europe";
2. Because of 1, you cannot geotarget a website but for Political States (Spain, UK, Russia...)
3. To think that not-English speaking users will use English for searching something it is not realistic, therefore it is correct what Matt says in his answer re: translated versions served in whatever format (ccTld, sudomain, subfolder) better fits your business needs.

Finally, personally I would not suggest to a ccTld for targeting European users, because that ccTld would geotarget the site to its country (eg: .es to Spain). Better a generic domain name (.net or even .eu, which is a generic domain name and does not have any geotargeting power), or even a subfolder/subdomain.

Finally, when creating the different country sites, I remind you that in certain countries is spoken the same language. For instance Ireland and UK share English, but they have different currencies, obviously different postal system and phone numbers and, especially, a different culture, so that you should not think in having an European EN version serving all the English speaking countries, but localizing each one of them.

To not talk, and I really end my answer, countries like Switzerland (French, German, Italian and Romance), Spain (Spanish and Catalan), Belgium (French and Flemish), Ukraine (Russian and Ukranian).

Hi Pieter,

can you answer to this question?

I checked you .nl website with flang by Dejan SEO, and it is not showing me any hreflang annotation... I check directly looked into the code and confirmed that was not a Flang mistake.

So... are you using hreflang in your sitemaps.xml file?

I see that you already decided to stick with the .com domain.

It's fine, albeit a conservative choice, even though I would have started considering more seriously the idea of migrating to a .com.au domain name if - as you say - you're struggling vs those ccTlds domains, which outrank you even if objective factors (link profile, DA, PA) are better in your case.

I say it because of the lift effect a ccTld may mean: given parity of pondered factor, one ranking signal improved can provide you a big positive change.

However, I agree with you that migrating your domain may be a risk because of all the things that can go wrong during a migration.

Therefore, look at others geotargeting signals. For instance, look at from where your backlinks are coming. You say you have clients from all over the world, therefore I suspect that you target the global market also when creating the link profile of your site, and considered less important earning links from local websites or sites targeting your region.

Maybe you should start targeting more also those sites, so to give a clear geotargeting sitgnal to Google.

Obviously, this is a generic suggestion, as I don't know that much about your site and niche, but remember: international SEO is not just about domain terminations and geo-targeting in Search Console, but also many others signals, being the origin of inbound links one of the most relevant ones.

Likes are not a ranking factor :D... so thinking they are the reason your UK Facebook page is outranking the German one in google.de is not a correct assumption.

I would look to more classic reason, as the backlinks your UK Facebook page may have and the DE one not.

Try to build links pointing to your German FB page from German webistes. This should be enough for making understand Google to present your DE FB page to German users instead of the UK one.

Finally, the hreflang annotations (presence or not) do not have any influence of how your Facebook pages rank or not.

If they are contextual links, then you should not have any problem and can maintain them as they are.

No need "to hide" them to Google.

The use of the hreflang can be useful anyway, especially from Brand searches (aka: "name of the brand" as search term), because in that case you can see your "local country" web site outranked by your most powerful one despite of the geotargeting you have set up in GWT.

There are two good ways to do interlinking between different country sites:

1. The first one is offering somehow similar to the one you described, but not making it sitewide (as saying, not having the footer links always linking to the home pages), but contextual linking, which means that domain.com/page-a will link in the footer to domain.co.uk/page-a, domain.it/pagina-a, domain.es/pagina-a et al.

2. Doing like Apple does. Having in the footer a link to a country selector page, where you can find all the link to all the different websites. This option is conservative, in the sense that you have just one page linking to all the international sites, hence you don't have to fear Google deciding to penalize sitewide interlinking.