Personally I would just setup the 301 correctly and not worry about logging the change in WMT.  However If you click into your site, hit the gear icon in the upper right hand side of the page, then hit "change site address" you can specifiy a new address.  You could also setup the https domain as a new site in WMT and delete the old WMT account, but again if it was me I would just leave things as is and let google pick up the change through your 301

the way I read the information from Google is that if you have all your pages "site wide" redirect too SSL they will factor that into rankings.  If you only enable the SSL on sensitive shopping cart pages you will not get credit in Google's eyes.

Its an interesting move, and in general the only "negative" aspect of doing this is site speed. The SSL "handshake" slows down site loading times, but it should be a very small amount.  I'm guessing that in the future google will provide some kind of "reward" for sites that do this... possibly a small badge or emblem on the serp page saying something like "secure site".

That is strange, looks like a mobile result for sure.  Best guess is you fooled google with a mobile emulator and they served a mobile results page too you.

the screenshot is also showing your location history, do you sync your chrome browser across your phone/table/desktop?  I do this and sometimes run into a situation where my phone will pull a recent search I did on my desktop computer.  Maybe your desktop chrome browser was pulling a recent search you did on your phone and displaying the mobile results..... regardless this looks to just be a random fluke.

Hi Tanveer-

I think you will find your experience posting in Q&A very positive and I suspect Moz does things the way they do to possibly foster some of that community involvement.  I've found that almost any question I had related to Moz I could reach out to the community and get great answers (usually with responses in 10-15 mins on a question).  The community at Moz is very large, very active, and very helpful.

This might be overly simplistic but why not just have a "translation" or some other similar type of link accompany each blog post.  Something along the lines of:

Post title:

post content

want more information about your region visit our "UK" "french" "us" website for more content in your area.

An alternative route would be to go with subfolders instead of subdomains.  Each regional version could be in a corresponding subfolder of your website, instead of subdomain and that way your link equity would be shared without the need for any additional linking as everything would be under one top level domain.

That XML sitemap you linked too is formatted in an odd way. I noticed the site you are generating the xml sitemap for is based in wordpress.  There is a really solid sitemap plugin you could use to generate your XML and submit to google instead of the current plugin you are using: http://wordpress.org/plugins/google-sitemap-generator/

I've used that plugnin numerous times and submitted sitemaps to google with no errors. Hopefully that helps you out.

closed

Dan-

Yep you are right on, if you added the above type code below all of the specific page redirects then that would "catch" all the remaining URL's with random parameters in the URL and redirect them to the home page.  And its very similar code for the windows server, I'm confident your Dev should know this, if for some reason they don't I can message you the code snippets you would need for the windows server.

Also Everett Sizemore brought up a great point below.  If you are redirecting all 404 pages to this 1 custom "404 landing page" that is incorrect.  That is called a "soft 404" error.  These will actually show up in your WMT account as well as under a section called "soft 404's".

To help figure out what is causing the 404 errors do the following in webmaster tools:

-login to your websites profile, then on the left hand side navigation hit crawl > crawl errors > not found.  Under not found review the list of URL's for clues (you can also click on an individual link to see where the 404 page was linked from).  Depending on how large your site is, if the 747 not found URL's is a large percentage of your total page count, you could be experiencing a temporary rankings drop that will disappear one you fix your error pages.  If you could add a link to a few of the 404 error pages we could help you figure out what is wrong with your site code or server setup.

No problem Dan.

There is definitely no harm in ticking off the errors as "fixed" and then seeing which ones return. If they return I'm betting 1 of 2 things.  1.) That you still have a live link somewhere on the new site pointing to the page.  The easiest way to test this is click on one of the pages in WMT and hit the "linked from" button. That shows you where google is getting sent to the page from. The second option is that the pages have an "external" link pointing too them.  If that's the case you want to be double sure to redirect it so you get the link credit!

I'm not 100% positive on why MOZ is not showing the errors as quickly, but MOZ does a "deep" crawl of the web and then does a lot of computing. WMT is literally just crawling your site, and spitting out anything it finds to your account.  A much easier job for WMT, hence it is pretty quick to report site errors too you.  The errors in your MOZ account will most likely update when MOZ pushes their next mozscape index update (this will also be useful for you because MOZ will have better data about "external" links than WMT)

From the error you sent me it looks like you are going through a move of a site from .aspx to .php or .html.  When you change languages like this you can end up with a lot of gnarly 404 pages, especially from search pages that have variables in the URL. If you have a large amount of these errors, so many that you feel you are getting a temporary "penalty" for too many site errors you can write a quick snippet of code in the .httpdconf file on your apache server to fix these old useless pages. (if your not on an apache server this can still be achieved, the code would just be different.)

make sure to put this snippet below all of your other individual page redirects

#redirect all old dead .aspx pages to the new homepage
RedirectMatch 301 /(.*).aspx /

You should still make your best effort to redirect each old page to its corresponding "new" page. However at a certain point if you have thousands to redirect, and many are just pages with with search parameters in the URL... there comes a point where you want to just hit all the remaining pages in 1 fell swoop.

I'm not certain on how long it would take the 301 to fully "pass" page rank in Google's eyes. I think it is safe to assume that once the old page no longer has a 404 link, and it is not showing up any longer in Google searches then the PR has been passed.  MOZ page authority should reflect it once MOZ pics up the change, but MOZ authority is just very "similar" to PR. Its not an exact science, MOZ should pic up the change easily though, it will just take them a little longer time.

Dan-

It sounds like you have already spot checked a few of the pages and they are still returning errors. In my experience WMT is very quick to re-crawl pages you have marked as fixed to see if they truly are fixed.  For example if you mark 100 pages as fixed, then 24 hours later 95 of the pages come back, its always been the case for me that the 95 pages still had an issue and were not "fixed".

I would pull up the error report in WMT again, spot check a few of the examples and see if the pages still error out.  If they do I would export that list from WMT, send it to your Dev and ask him to fix all redirection errors.

Dana your thought was right on.  Also you don't even really need to worry about changing anything on the "old" page per se. You could just open up the .htaccess file on your server and redirect the old page to the new. For example:

Redirect old file path to new file path Redirect

/olddirectory/oldfile.html  http://example.com/newdirectory/newfile.html

I just want to make sure I fully understand the question, so you have several hundred domain names all of which just have a generic Godaddy (or registrar) parked page?  If that is the case 1.) that is confusing why you would have so many domain names! and 2.) It sounds like your company is possibly trying to re-sell the domain names so I would think at a minimum you would want to create a custom parked page that had your contact info and an easy way someone could get in touch with you about bidding on the domain.

If you do really just have several hundred domain names your not currently using redirecting them back to your site will have next to no "SEO" value, unless as Richard Mentioned some of them have backlinks.  If non of them have backlinks then redirecting them all to your main page is essentially the same as going: 0 + 0 = 0.  If I were you I would keep and redirect possibly a few domains that have close mis-spellings of your main website.  Then I would tell your boss that you didn't want to renew the remaining 100+ "useless" domains, take that money saved and better invest it somewhere else (a Pro Moz membership, attend a conference ect...)

Did the language of your website change, meaning did you move from .aspx to  .php or .html?  If so we have experienced a similar situation where thousands of old pages were indexed by Google, once the site was moved to a new language we were penalized until we redirected all of the old pages.

We just went through this exact process with a website.  We agonized over whether to do the move since the .html pages were ranking and converting well. In the end the client wanted it so we decided to make the switch, this is what we did:

1.) Took all well ranking .html pages and 301 to their new version in apache .htaccess file, example code

Redirect 301 domain-name/old-page.html domain-name/new-page/

2.) Installed the SEO plugin by Yoast and made sure to tune all title/meta info for each page

3.) Made the change and stayed patient. We saw a traffic drop for 9 days following the move.  Then on the 10th day we got close to pre-move levels, and 2 full weeks later we were back at pre-move levels with improved average site time, bounce rate and conversions.

*we are almost 2 months into the move now and traffic is higher than ever.

This is a neat idea and like Oleg said should be straightforward for you to do if you just cookie all visitors.  You could then check  what cookie they have, and show the defined images (or pull several images from your DB).  I don't know of any "pre-made" tool that will do this for you, dynamic remarketing through Google adwords is somewhat similar but that is showing a set of images to users who are no longer on your site (user goes to x product page, and are shown x product later when they are watching video on youtube  ect...)

So our question is should we handle page redirection/rewriting in php or in .htaccess (with a specific problem we are running into outlined below).

We have an ecommerce store in a subfolder of our site (example.com/store/).  In the next folder down we have a group of widgets(www.example.com/store/widget-group1).  Recently we put a .htaccess redirect in the top level folder (example.com/store/.htaccess), in order to re-write some URL’s and also 301 a page to another page.  This seems to be negatively affecting our /widgets-group1/ subfolder however (organic traffic to example.com/store/widget-group1) took a nose dive 3 days after putting the .htaccess redirect in place on the /store/ folder and it has not recovered 8 days later).

*Nothing appears outwardly wrong with the current setup to the eye when viewing the pages or requesting as googlebot (the only issue being the nose dive in organic traffic lol)

*both subfolders are setup in apache config file to allow local overrides of .htaccess as follows:

<directory store="" widget-group1="">Options -Indexes FollowSymLinks -MultiViews
AllowOverride All
Order allow,deny
allow from all</directory>

<directory store="">Options -Indexes FollowSymLinks -MultiViews
AllowOverride All
Order allow,deny
allow from all</directory>

have you tried to "disallow" google from crawling your images directory in your robots.txt file?  If you get a lot of traffic from google image search you would probably not want to do this, but if the current problem you posted about is your #1 priority to fix, not allowing google to crawl your image directory should fix your problem.

Question 1:

1.) The impression/actions screen is actually very inaccurate (even according to google, they are "working" on it). We do a lot of paid advertising and therefor have access to a few different representatives @ google and have asked about this on multiple occasions.  Their best answer was to check webmaster tools ranking performance data to get a good idea of what you are ranking for "locally" and to get an idea of the traffic.  I know that is a pretty lame answer, but its the one we have gotten from google on 2 or 3 different occasions.

2.) It can take 2-3 weeks for changes you make to places pages to appear (crazy right!).  But if it's only been 2 weeks I would just give it a little more time.  One quick note though, if you already had photos on the account and just added 1 or 2 more, those will show up and the end and might not be showing up on the main page view.  In order to organize the photos exactly how you want to you have to upload them in the exact order you want them to display. Another thing to consider is getting a Google trusted photographer to come out and shoot  photos/a virtual tour.  It typically cost's ~300-400 dollars, but they upload the virtual tour and photos for you and will make sure everything loads exactly how you want it too.  *if you do the virtual tour a cool idea we have done for a couple clients is to hide small items in the store, and then run social promotions using your virtual tour, so you could say for example hide an envelope in your store and then later on Facebook say "the first person to find the envelope of 2 football tickets in our store gets them"

The wordpress hacking was almost surely due to having outdated version of WP, or having a vulnerable plugin installed.  There are a few helpful plugins you can use to secure your WP site, plugins like (http://wordpress.org/plugins/better-wp-security/).

also a couple things to note, you should also take basic measures to project the site by changing the default table prefixes of your DB from _wp,  create a new admin user and delete the default "admin" accoun & limit access to your wp-admin section in your .htaccess file.... these security plugins will give you a whole checklist of items to "secure".