Moz uses Google + and Facebook as their baselines so having images that are scaled to the reqs in those two would be the quickest solution. With Google you can bulk upload images in the dimensional range of 1000x1000 to 3000x3000 "We recommend adding photos that are larger than 1000 x 1000 pixels and smaller than 3000 x 3000 pixels." (https://support.google.com/business/answer/6031953) and then select what you want as a cover photo within Google+. See this guideline: https://support.google.com/business/answer/4791112.

And for Facebook a profile photo containing your company's logo must measure at least 180 by 180 pixels to meet Facebook's upload requirements. Once uploaded, the photo is resized to 160 by 160 pixels and placed within a 170 by 170 field, providing a small border between your profile photo and cover photo. Photos larger than 180 by 180 pixels are scaled down to fit within the profile template. (from: http://smallbusiness.chron.com/size-facebook-business-logos-57290.html)

Were these bolded terms relevant to the search query?

For the other languages, it's going to be a conditional redirect, which is best handled by 302. Here it is from Google: http://googlewebmastercentral.blogspot.com/2014/05/creating-right-homepage-for-your.html :

A third scenario would be to automatically serve the appropriate HTML content to your users depending on their location and language settings. You will either do that by using server-side 302 redirects or by dynamically serving the right HTML content.

Remember to use x-default rel-alternate-hreflang annotation on the homepage / generic page even if the latter is a redirect page that is not accessible directly for users.

Note: Think about redirecting users for whom you do not have a specific version. For instance, French-speaking users on a website that has English, Spanish and Chinese versions. Show them the content that you consider the most appropriate.

Cheers!

Hi Andy. There are quite a few settings you can adjust to make the server load less while the crawl is running. These can be found with descriptions here: http://www.screamingfrog.co.uk/seo-spider/user-guide/configuration/

For example, by not checking Images, CSS, SWF, and Javascript you'll be able to lessen load substantially, or if you'd like to crawl just a portion of the site you can set it to not check links outside of the start folder.

To have even more control over the crawl, you can use regular expressions to exclude certain pages, or sections that match a given pattern. The page above is fairly robust, so it should help you dial back the crawler to be friendlier to your server.  Cheers!

Hi Angelos. I agree. Having a 301 redirect that's always in place for going to /en is a bit redundant. If /en is the default option the default should be the root.

Other redirection should be handled via 302 to the various languages with all the proper href-lang and alternate attributes. Per Google, "For language/country selectors or auto-redirecting homepages, you should add an annotation for the hreflang value "x-default" as well: "  Cheers!

Hi Eric. I'd recommend using folders as being navigational and/or site-section specific. As such, they can be shorter--like the two letter abbreviation for states--and create less worries about URL length that way. A ton of other signals are going to be contributing to a page being recognized as being about a resort in Florida than FL vs Florida in the URL alone.

Once you have your structure figured out, using hyphenated URLs that often mimic the title tag of the page is generally a best practice as this gives the user the best idea of what a link is about while also containing keywords when someone links to the page solely via URL.  The Moz blog has plenty of examples such as: http://moz.com/blog/how-to-stop-spam-bots-from-ruining-your-analytics-referral-data.. Short domain, short folder name, then the content. Each bit is readable and understandable as to why it's there.

See: http://moz.com/learn/seo/url for more.  Cheers!

Yup. And the title of that page is that it's unusual activity from your network, and Moz isn't your network, so that one is easy to eliminate.  It's likely some other trigger as I and others mention.

Hi Ash. I've used Moz for years and this has never happened (due to Moz). The machines they use to check rankings are separate from the machine you're using, so here's what could be going on...

1. You're checking rankings so much in Google, repetitively running the same searches over and over, that Google is limiting your machine's access.
2. You're on a VPN that is shared by others and they're doing similar to #1.
3. You're on an office network that is doing similar to #1 and it's causing the captcha to appear.

As an experiment, launch a fresh browser instance--preferably one you never use, like Opera, or a fresh Firefox install--load up a VPN to change your location to some other country, and then run your search in that country's local version of Google. I doubt you'll see the captcha then.  Cheers!

In addition to using rel=canonical for the lowercase version of your URLs you should also consider implementing redirection from uppercase to lowercase.  A regex expert should be able to write the redirect script you'll need to add to your .htaccess file in order to change upper to lowercase. Cheers!