Welcome to the Q&A Forum

You can block Wayback Machine from crawling and creating a record of your site by adding the following to your Robots.txt file: User-agent: ia_archiver Disallow: / This will not only stop new records from being created but also stop people viewing what had previously been indexed by Wayback Machine. More information about this can be found here: https://archive.org/about/exclude.php

Ha, it happens. Every once in awhile I do a full audit on our thousands of clients. I find the strangest things - meta robots blocked, robots.txt blocked, client releases new site, doesn't tel us, no onsite done at all, homepage titles set to "Home."  It happens - things get lost in the mix. Plus, most people deal with robots.txt and meta robots (at least more frequently). The simplest thing for future reference is just to drop it in Screaming Frog (even the trial) and just see what you see.

As far as I understand this, to your browser and to Google, they're the same page (this really seems to only apply to the homepage, other pages "/" really matters a lot). I would not worry about changing the canonical, in fact it's technically the 'right" location of the page. When it comes to the HTTP docs, a request to the root needs "/". All modern web browsers add it back in for you even if it's not there. This is I believe why the canonical is set as it is there in yoast. I covered this in a blog as someone asked this at Pubcon this year in a keynote. http://www.winstondigitalmarketing.com/yoast-homepage-canonical-correct-include-trailing-slash/

A) Generally yes, but hard to say for certain. There are correlations suggesting that maybe some of them do pass influence in some way. B) Probably, but again, likely based on engagement, i.e. if a social link gets very little engagement, it probably won't do much to influence search rankings, but if it gets a lot, it often seems to have at least some positive impact.

Thanks Amelia!

No problem, glad I could help!

I think that your "hub" pages can be category pages and more. Imagine a hub page for widgets with.... "how to do it" articles down the left column, "widget reviews" down the center column, and tips on "how to enjoy widgets" down the right column. These could look like your sample page or look like the homepage of Slate.com... or any other news site's homepage or category pages if you have enough content.

No problem - what was you reason for going to HTTPs? If it is for a ranking boost you may find this an interesting read - http://blog.searchmetrics.com/us/2014/08/29/https-vs-http-analysis-do-secure-sites-get-higher-rankings/ I moved one site to https and saw no siginificant ranking boost from this change. I have seen people implement this and cause there site to slow down which has had the opposite effect. In my opinion another big clue is the fact that sites like Moz and Search Engine Land haven't gone to https

Hi Kevin, I'm reviewing the questions assigned to me as Associate, and I was wondering if you consider this yours as answered. If it is so, I kindly ask you to set it up as answered. Thank you.

As long as you submit the URL to your sitemap there it will pick up any changes.

Sorry don't think I replied directly to your comment... the previous site defaulted to English so every page on mysite.com was in English. The other languages were accessible via top navigation and those were/are found under mysite.com/jp/ mysite.com/aus/ The only change now is instead of having English pages on mysite.com/some-page/ they've decided to add the English subdirectory /en/ so you get mysite.com/en/ mysite.com/en/some-page/ The homepage was never a language select page because English is the most commonly requested language. I'm just wondering if adding /en/ to each page will have a negative impact to the site. A large chunk of our links were pointing to the old homepage www.mysite.com but now our homepage is www.mysite.com/en/ (keep in mind we have thousands of linking root domains pointing to all different parts of our site and we are considered an authority) Hope I explained that ok. Thanks.

Thank you Ray-pp, This is very helpful.

It does.  I was sceptical when I was told that it had something to do with Moz Local.  I'll take a look at the video - thanks for the suggestion!

Ray did a great job explaining what and how linking c-blocks do to affect your domain authority. Generally speaking it is better to have unique linking c-blocks as it means a variety of sources are linking to your domain. If all come from the same c-block it may look spammy or fake according to search engines.

I don't know any specific to the auto sales industry, but I have worked with a lot of people in similar scenarios (ie: vacuum parts - lots of sku's, items, inventory) - and they have been pretty happy with Magento. You're probably familiar with it already though

You can find the 35 temporary redirects that Moz reports using the Screaming Frog tool. You'll see the redirects for individual links under the "Response Codes" tab. Look for the "Redirect URI" column. The fastest way to find all of the redirects is to go to "Reports" > "Redirect Chains." This will show all the redirects on the site. I think you have to purchase a license for this feature. If you are trying to find redirects that have been set up for incoming links from external sites, you'll have to access the .htaccess file. I also do a site:domain.com search in Google just to see if there are old links still in the index. Then keep an eye on 404 errors in Google Webmaster Tools after the site launches.

Given they were tags and not something more powerful like an , I'm not sure how detrimental it would've been, however, I think your SEO agency is right to change the HTML element to something else. How the tags were being used was outside their initial design (page hierarchy and design), as davebuts pointed out above.