Welcome to the Q&A Forum

Hi Mike,

This is an interesting question. Depending on the nature of the content, you might want to try to get user generated content on those pages to make them more unique and valuable.

Best regards,
Guillaume Voyer.

Hi Candida,

I would suggest that you shouldn't use 302 redirects because they won't pass any link juice, but not only because of this.

Instead of automaticaly redirecting the users without their consent, you should let them decide in what language they want to see the website.

For example, I'm french, but my browser's language is set to english.  If I click a french result in the SERPs, I wouldn't want to be redirected to the english version.

Also, by automaticaly redirecting the users to their browser's language, this mean you will automaticaly redirect GoogleBot to your english website and prevent him from indexing your spanish website.

Best regards,
Guillaume Voyer.

Hey Sean,

I looked at the cached version of the YouTube channel of BMW ( http://webcache.googleusercontent.com/search?q=cache:www.youtube.com/bmw&hl=fr&lr=&sa=G&strip=1 ) and it doesn't seem to have any kind of redirect on this one.

You might have seen a redirect because you were logged into your account and looking at your own channel, like when you can edit it, so probably by logging out or by looking at the cached version by Google you should see that it is a plain juice flowing link.

Regards,
Guillaume Voyer.

P.S. Look at http://webcache.googleusercontent.com/search?q=cache:www.youtube.com/user/PretavoirUK&hl=fr&lr=&sa=G&strip=1

Hi Supriya,

Matt Cutts just released a video about that on YouTube :

http://www.youtube.com/watch?v=rAWFv43qubI&feature=youtube_gdata

Enjoy!

Best regards,
Guillaume Voyer.

Hi Mike,

Here's an other question on the same topic with an answer from Rand :
http://www.seomoz.org/q/is-the-size-of-a-website-a-ranking-factor

Personally, I think it can help, as long as it is quality content that will gather links and that you keep a good site architecture.

I also seen small websites (<100 pages) outrank wikipedia on generic single word queries with a small amount of links.

So, of course, there's no magic formula, it's not all about the number of pages, domain authority, page authority, on-page stuff, external links anchor text or something else.  It's all about having a little (or a lot) of everything to look authentic.

Best regards,
Guillaume Voyer.

Hi Blaine,

If the CMS allow to modify title of the page, meta description, page content, anchor text, url structure, etc. then there nothing to worry about.

As long as you can set those as you wish and that the source code is clean and readable by search engines, then it there shouldn't be any problem.

Search engine spiders doesn't care what CMS you use, they look at the source code of the page and gather the information they need.

So, as long as the pages can be parsed by spiders and that you can modify the important stuff on it, it can be optimized.

Best regards,
Guillaume Voyer.

Hi AzGuy,

Aaron Wall just did a great review of it on his blog : http://www.seobook.com/complete-review-wordtrackers-link-builder

I did not try it yet, but I'll definitely take the free trial and I think you should also see for yourself, it's the best way to know if it fits your needs.

Best regards,
Guillaume Voyer.

Hey,

I don't think there is any SEO benefits and the video your are referring to is somehow outdated and ironic as Matt Cutts doesn't display any file extension on his blog neither.

On a usability stand point, it is better for users if the URL doesn't have any extension so they doesn't have to remember if the URL was ending with either .htm, .html, .php, .aspx, .asp, .jsp, etc.

The shorter, the better. A shorter URL will be easier to share (ex: on twitter), tell on the phone, quicker to type, look better in SERPs, etc.

Best regards,
Guillaume Voyer.

Hi Tyler,

It's a good thing to use the HTTPS version of the badge on your HTTPS pages because otherwise, the page would be reported as unsecure by the browser to the user.

On the other hand, displaying HTTPS ressources on a HTTP page matters. Downloading and decrypting the secured ressources will use more bandwidth and CPU on the server and client side. In other words, HTTPS is slimply slower than HTTP so it will be detrimental to the user experience.

The difference might not be signigicant, but it's always good to keep that in mind. So, I simply suggest you match the protocol of the ressources with the one of the requested URL. HTTPS with HTTPS and HTTP with HTTP.

Best regards,
Guillaume Voyer.