Welcome to the Q&A Forum

You're not going to get a massive benefit from a dedicated server on a low amount of visitors. You'll get a bigger benefit for speed by making sure you've got caching/images optimised and lazy loaded + using a CDN for assets. Have a look at Cloudflare and their free plan.

Honestly, to get a proper answer people would need to know the site in question to do an audit themselves.

Would you be able to send me a dm with a copy of that email? I'm interested in larger sized automatic sites and trying to figure out where the limit is (and how yours isn't allowed when others are)

Ok, this one may be interesting, if it's none of these options below I'd love to take a deeper look, send me a dm on twitter: https://twitter.com/thomasharvey_me

So, I see that you're on Cloudflare, are you still being crawled by Google?

Have you looked in the old search console? Have you or anyone you work with done anything in the "remove urls" section?

Have you seen any change in crawl stats recently?

Any recent changes to the site that may have caused this?

In my opinion, it would be a business decision that's then implemented by the SEO. So ask your bosses these questions and what experience they want for their customers.

can anyone think of any other reasons why the images wouldn't get indexed.

Only thing I can think of is perhaps if your subdomain is serving wrong status codes for your images, unlikely but possible.

My guess, is that Google is picking up this line in your code: class='testimonial-date'>Written on May 19, 2018

Which looks to be when people are leaving reviews for you?

You would use hreflang tags: https://moz.com/learn/seo/hreflang-tag

1. You can use any version you want as the x-default, it is merely the version that will be shown if none of the other languages are relevant.

2. Yes

3. I'm guessing you forgot to change the url, so here's the correct structure:

Hope this helps you!

When you say country targeting, do you mean ip redirects?

I'm even more awake than the last time I checked too!

Looking at the source of say: https://au.pacapod.com/collections/classic-plain-changing-bags

You have the following code:

Whereas on https://www.pacapod.com/collections/classic-plain-changing-bags you have:

and https://us.pacapod.com/collections/classic-plain-changing-bags being:

In short, looks like your AU site is setup incorrectly to just reference the homepage.

Hi  Eddie,

Sorry, hadn't woken up when I looked this morning!

If possible, try moving your hreflang toward the top of the head. You've also got two canonicals in the head too.

Having a look at the hreflang code though, I don't see any mistakes in it, so perhaps it's just placement.

Tom

Hi Eddie,

I've had a check of your sitemaps, I can't see any hreflang? https://www.pacapod.com/sitemap.xml

Tom

What's the redirect issue?

Personally, I am redirecting and forcing all users to use https. Https isn't going anywhere and http has no benefits over https, so trying to support both and not doing redirects is just not worth the effort. Keep it simple and just force all users to use https.

I've been using them for the past few months and their offering is from what I can see is very good value. I've had a few issues with setting up and learning their platform (as well as actual bugs) however chatting to them on their live chat the issues have been resolved and also they've given credits to make up for their mistakes. So I'm a pretty happy customer of theirs.

When you put the redirect in place for migrating to the new site, why not just do a redirect http/https (old site) -> https (new site) and this sorts the redirect chain issue.

Try using this extension, it's quite handy for highlighting issues.

https://chrome.google.com/webstore/detail/link-redirect-trace/nnpljppamoaalgkieeciijbcccohlpoh

Also, are you getting any issues highlighted in Search Console?

If I'm correct, you're no longer using the old domain and just redirecting to the new site?

If that's correct, why keep it with Shopify at all, you could instead point it to a different server (or to Cloudflare which'll be able to handle to redirects through page rules without you having to do any code).

The best course of action is to 301 redirect the site to the new site, then on the new site (after checking for issues) submit sitemaps/fetch as google. To speed up this process slightly you can also submit a sitemap for the old site, Google will see the redirect when they try to crawl any page.

Have a look at your site through http://web.archive.org/. You'll be able to see what the directories were used for.

However, if there's no use for them on the current site then what's the purpose of keeping these disallows in the robots.txt?