Let's use a Wix example site (not a client, just a sample from their page) as my example. Say you wanted to check:

http://www.kingskolacheny.com/#!press/crr2

In the source code I see the escaped fragment URL.  This is the one you can find a cache for:

http://www.kingskolacheny.com/?escaped_fragment=press/crr2

That leads me to: http://webcache.googleusercontent.com/search?q=cache:http://www.kingskolacheny.com/?escaped_fragment=press/crr2

If your #! URLs are not setup this way, you will struggle to see it. One page websites are ... one page. But if you have escaped fragment URLs setup, you should be able to submit those and go from there.

The easiest way I know to find these is Screaming Frog, Ajax tab, Ugly URL field - try that one.

While I do agree it's possible for them to affect you, I want you to think about an example.

Take the keyword "blog."  By itself, it's very, very competitive.

Somehow Wordpress.com ranks #3 for blog.

They do not rank for "create a free website" which is in their homepage title but they do rank for "create a free blog" #1.

Their results are all over the place. They have a huge number of spammy, low quality subdomains. Are the inconsistencies because of the difficulty of these terms? Maybe. The spammy subdomains? Maybe.

But I can't see Wordpress.com ranking for "blog" if the subdomains could pull you down.

Take this for example (Just one LITTLE piece of the spammy pie):

http://bit.ly/1O5AzDr

I assume you mean an "official" change of address in Search Console?  Yes, if this is an official, permanent move then you should do the official change of address in WMT.

Use the change of address tool

If you've moved your site to a new domain or subdomain, use the Change of address tool in Search Console. A change of address notification helps you manage the transition needed by Google to index your new URLs at the new address, while minimizing impact to your current ranking in Google Search results.

https://support.google.com/webmasters/answer/83106?hl=en

It depends on the setup of your site, to be honest.

If you have a Wordpress, Joomla, etc. with really easy access header sections that you can put the code in once and it's done forevermore no matter what pages are added, that's the simplest way.

If your dev can script it to add to each page through the sitemap, that's also a one & done way.

The only thing you really don't want to do is have to add a hreflang tag to every new page you add to the site. As long as you can avoid that, you should be right. We had a client add it to their sitemap but the sitemap wasn't auto-generating the tag so each time they updated they had to re-implement the tags. That was a frustrating time ... now we've got it automatically updating so it's much easier to maintain.

247pinger.com

bulkping.com

Those two usually do the job. Google (and thus a number of SEOs) suggests pinging isn't necessary but we test & test some more and this works. We've sped up the process many times using this tactic.

Haha I read this question earlier, saw the post come across feedly and knew what I needed to do with it. Just a matter of minutes. You're right though - I would've probably said remove earlier as well. It's a toss up but usually when they clarify, I try to follow. (Sometimes they talk nonsense of course, but you just have to filter that out.)

I know this question is answered already but my 2c based on what we've changed about our onsites.

If your brand name includes a main keyphrase, we typically don't include it on every page. You basically end up "competing" with yourself for that keyphrase. There's no point having:

Syracuse Wedding Photographers | MyCompany Photography

and using that brand bit on every single page. You're over-telling Google that the page is photo related. (Photographers in general have this issue but it applies to MyCompany Plumbing and MyCompany Iphone Repair too.)

No, you don't need to worry. If you've implemented hreflang into the sitemap properly, it will work and you don't have to worry about the Moz reading. Moz tries to cover off the main things that affect you and give you an indication of what Google may like & dislike on your site but by no means are the implementations of everything exactly the same. So yes, Google will understand your 'duplicate' page titles are not.

@Patrick - you can definitely implement hreflang in sitemap. I was surprised when I saw that the first time, too, but I've tried it for a few clients lately and it works well.

We're all students of the game. I hope I never stop learning about marketing.

I had read about the sitemap implementation but never tried it. Then I ran into an enterprise client who has over 40,000 indexed pages & 20 separate languages.

One of the languages didn't have a subfolder but all the rest did. Instead of coding it in, I figured my way through sitemaps & thought it was SO much easier in the end. I've used it a few times since and it's great.

Well ... I gave this as thorough a check as I possibly can. Guess what?

It's happening because your www.us.allsaints.com homepage is NOT INDEXED.

• site:fr.allsaints.com (1st result)
• site:es.allsaints.com (1st result)
• site:www.allsaints.com (1st result)

site:www.us.allsaints.com  - Nope. You have subpages indexed but not the homepage.

Now, whether that's duplicate content or the massive amount of IP-related spam links to the site is hard to say. But your homepage has been deindexed and because it's not indexed, doesn't show up in the cache.

If you have the site claimed in Search Console, check for penalties. Check that you haven't removed the URL through Google Index > Remove URLs. Check that you haven't done a site move on https://www.google.com/webmasters/tools/change-address?hl=en&siteUrl=www.us.allsaints.com

Once the homepage gets indexed, you should be good to go.

A link can't be direct to your site, then refer back to shareasale, then redirect back to your site unless you've set it up that way somehow.

So if someone builds a shareasale link like:

Link to your product

This is going to shareasale. If you quit shareasale and they said it would still go directly to you, they're just not planting their tracking cookie on the intermediate step. Everything else would remain the same.

If the link is something like:

Link to product and somehow that goes from your site, to shareasale, back to your site - well that's definitely not helping you very much for SEO and if you quit, yes that would then go directly to your site - but only if you reconfigured how the links were working since this type of linking would require a lot of special work to make it happen. It's more likely it's the 1st example.

In any case, they both pass through Shareasale and, per Matt Cutts, Google is attempting to not give you credit for that link. Whether or not they do, I can't say - but they're attempting not to. I'm not sure which part of my previous answer may not be "completely true."

If your site is only in English you don't need to use hreflang tags at all.

If it were my site, I would move the UK site to .com/UK, then have .com/DE and .com/US.

Then I would 301 redirect all the UK links back to their counterparts on the new site, keeping as much authority as possible. Point the main homepage at .com/UK and all the inner links as they currently are.

Doing this now will definitely help your expansion in the future as well.

I would do all this after you've rebuilt the site, though, because you don't want to do 301s to 301s. Figure out what the new site will be, do the 301s to that one directly. No intermediate jumps ... it's a longer time to implement but you're better off in the long run.

You said you don't like the idea of redirecting the root domain to a sub dir - but why? It's passing the full value of the UK site to the new location of the UK site. Makes perfect sense in my head. I would definitely do so.

I would only recommend the /US version because of the hreflangs. You can do it the other way, it's just a bit more technical to build the hreflang tags. You can use this example I've used before, though:

" hreflang="x-default" />
" hreflang="en-uk" />
" hreflang="en-de" />

This will do the trick, I believe. Then will display that in the header of every page and the request URL will grab the URL you're on so you'll end up with hreflangs for the two URL structures.

You said you could migrate .co.uk to .com/UK asap - do it as soon as you can, as long as the URL structure won't change. If you're moving from say .co.uk/about.html to .com/UK/about-us/  then you can't do it until those URLs exist. I wouldn't move the existing site over now if the URLs are going to change. This is what I was saying above - you don't want to go from .co.uk/about.html to .com/UK/about.html (and then in August) to .com/UK/about-us/

Make sense?