Welcome to the Q&A Forum

a) I would load up several awesome articles from the get go. that way if a person visits your blog when you first start dripping, there is other content than just the 1-2 posts for them to view. b) i do recommend dripping the posts... I don't believe staggering has any SEO effect. just think your potential readers and the ideal schedule for them to return to your site and convert.

The Google webmaster blog published an updated guide four days ago [link: http://googlewebmastercentral.blogspot.com/].  I'd recommend following it to the letter. Another thing to watch out for when changing hosts is to make sure your DNS settings are ready to go on your new host before you cancel your old one.  These days this is usually fast, but I've seen sites go down for ~48 hours because they didn't take this precaution.  I'm not sure what your level of computer savvy is, so here's an explainer on DNS and why it's important [ink: http://www.howtogeek.com/122845/htg-explains-what-is-dns/].  Basically it's how your browser translates a URL into a form that it can understand and provide a page back to you.  Most hosts provide this free, and it's something you never think about until something goes wrong with it.

Hi Paul, Bing is much less confused, and we'll sit tight - but many thanks for the change of address tool suggestion - we had missed that! Best, Richard

is there any idea ?

Stackoverflow is always your best friend: http://stackoverflow.com/questions/2345038/iis-404-custom-error-url-return-response-code-200-instead

When you say external cdn, is it a cdn that you control or a public repository? If you control the cdn and you are just using it to open more channels for the browser download I would recommend setting the link in the header. From there you can set the canonical tag of the resource in the header. Here is a screenshot of the http request of my logo on my site, http://screencast.com/t/rQoiVIo8deZ5  It is getting the file from the cdn, but it is also telling search engines that the canonical location of the file is on my domain. This is something Google has supported for a while now, http://googlewebmastercentral.blogspot.com/2011/06/supporting-relcanonical-http-headers.html If you are using a public repository, you do not have control over the header, so I would not worry too much about it.

One we were watching, the Official site for Jehovah's Witnesses went from watchtower.org to jw.org with a major site redesign. What makes it an interesting case study is that it was a multi language site as well.

Technically the disavow acts like a nofollow, so unless you think they might turn into "followed" at some point, you do not need to disavow them. It can take 6+ months for a disavow to take effect too. So if it was submitted only recently, it might need some more time.

I would not use a .eu domain if I were you (or probably anyone else). It's too big and generic of a target when Europe is full of so many countries and languages. I'd recommend it only for a site such as Eurovision. Now, there are three ways to do it. **1. Separate root domains.**This would be creating and using example.be and example.nl. 2. Separate subdirectories/subfolders. Take your main website at example.com and configure its targeting (in the meta data and Google Webmaster Tools) to either Belgium or the Netherlands. Then, create a subdirectory/subfolder for the other country (example.com/nl/ or example.com/be/) and configure its targeting as well. 3. Separate subdomains. This would be creating nl.example.com and be.example.com SEOs and digital marketers will argue forever over which one is best. I'll point out some general differences and points since I don't know your specific situation. Separate root domains and subdomains are essentially entirely-separate sites in Google's eyes. This is good to use when you have a lot of specialized content for each domain's target audience/country/topic. It's also usually easier to use different design templates on different domains and subdomains. The bad side is that links pointing to one domain or subdomain will probably not "benefit" the other one. Keeping everything on one domain in a second subdirectory/subfolder can be a lot more simple to manage. Plus, all links to everywhere on the domain generally "help" everything on the domain. However, you will often be limited to using the same overall design template. Since you cannot create country-specific content, I'd create one website and use a secondary subdirector/subfolder (number two in the main list at the top). Google says the duplicate content is not a problem as long as it is clear that the two versions are each targeting a different location. As to why your current .nl website is not performing, it's impossible to say without taking a look at it. First, review this page of introductory guidelines and the related links. Some more detail from Google. A Webmaster Support question. For more information on international strategy, I'd suggest this post by Moz Associate Aleyda Solís. Good luck!

Hi there It sounds like you've got all the basis covered.  To avoid any form of duplication, it is important to redirect the old version to the new URL as soon as possible, preferably simultaneously when the new blog is published.  That will ensure the two won't be indexed together, plus it makes sense that an updated would be redirected. There are other methods as well - you could simply remove the old blog post page and return a 404 (which isn't a bad thing), update the canonicals like you say or add a robots instruction to prevent the page from being indexed.  But I think a 301 redirect here would be best, as it would pass on any link equity (no matter how small) the previous page did earn, it's one of the quickest methods to remove old pages from the Google index and for continuity's sake I think it makes sense too. The fact that you're changing the old post in a substantial way might mean that you could potentially keep both versions on your site, but only you'll be the judge of how unique it is.  I think, to remove any doubt, you should use the 301. Hope this helps.

As mentioned earlier, you can create a comprehensive Sitemap.xml file and resubmit to Google. Give me your email address, I will create one for you and send it Best regards, Devanur Rafi

Great responses so far! I would like to add that Domain Authority is a metric created by Moz, and not a metric created or used by Google. There is likely a correlation that a higher DA will help you do better in search engines, but it's not a metric we're getting from Google or sending to them.

Hi Andrew, Welcome to the SEO world and as Devanur mentions in his response below, you need to change focus from looking for followed / nofollowed links to building great content which will automatically attract links coming through to you. Alternatively, though, you can still focus on the traditional linking methods by joining industry associations in your field and being listed on their websites as verified members which will get you links back to your site (follow / nofollow really depends on each site in this instance). Good luck and stick to white hat techniques!

You are correct, adding code to a page to 'adjust' the bounce rate can effect your 'average time per visitor' statistic. This is because of how google measures the time spent on a page... Normally, if a user opens one page, then does not visit any more pages on your site, it will count as a bounce (even if the user had remained on that page browsing for 10 minutes).  This is because there is only one call made to google analytics when the page is opened.  There is no call made to google analytics when the page is closed. So normally, the 'time on page' is calculated by taking the time stamp of when the current page is opened, and comparing it to when the next page on your site is opened.  The difference between the two is your 'time on (previous) page'. So what happens when a user only opens one page on your site and leaves (bounces)?  This will be counted as a 0 second visit (even if the user was on the site for 10 minutes).  Thus bringing down the average visit time for all visits. What happens when you add the 'adjusted bounce rate' code to your page, is that a 2nd call is made after x seconds to the google server.... Allowing google to know that the user has in fact remained on the page for an extended period of time.  So now a whole bunch of these '0' second (bounced) sessions will be converted to longer sessions based on the time between the 2 time stamps. The more 'one page only' visits you have to your site, the more this has the potential to skew your average session time. On a side note, this will also effect the last page visited of multi-page sessions, as normally google would not know how much time was spent on the last page of the site as well.

I agree with the rel="canonical" that is the definitive way to solve the issue. The urls are not actually two different urls, they are using a query string. If you put a redirect into place, you might lose the functionality of the query string. Also, GA uses query strings for tracking, so you would also lose any GA tracking you are using on the main site page. Most people use rel="canonical" to solve this issue. I know when I blog and I link to a site I normally put a query string in the url I link to just to give them an idea of where the traffic is coming from and to make it easier to track.

Hi Tiffany, This looks like you're debating between two approaches to me. approach 1 - is it ok to delete a sitemap file and submit a new one once a month with product updates. approach 2 - Is it ok to resubmit the same existing sitemap with the updates included. also once a month. As Eric mentions below, stick to having your current sitemap file and just updating it rather than having to delete and submit a fresh one each time. Part 2 - Is updating once a month too much? no. Once a month updates are fine and you can still get away with more than just once a month depending on how much content you have available to update.

Awesome, thanks so much for taking the time to provide some feedback, greatly appreciated Pete! There are no site-wide footer links that I know of, so I think we're good. Martin

" Domain Authority measures the predictive ranking strength of entire domains or subdomains, Page Authority measures the strength of individual page. " According tot he data moz has on your web site they think your homepage has better chance of ranking as opposed to other pages on the domain. I would not be too worried about it, you can mitigate it by building quality links to some of your other top internal pages http://moz.com/learn/seo/page-authority http://moz.com/learn/seo/domain-authority