Jump to content


Photo

www resolve


  • Please log in to reply
1 reply to this topic

#1 TimW

TimW

    Dedicated Member

  • Members
  • PipPip
  • 235 posts
  • Gender:Male
  • Location:West Country
  • Experience:Intermediate
  • Area of Expertise:Nothing

Posted 11 August 2017 - 01:38 PM

I was fiddling with htaccess today and not really knowing what I was doing. Am I right in thinking that requests for pages with/without www should all return pages from one, not the other, but it doesn't matter which?  so here for example I key in 
http://webdesignerforum.co.uk/

and my browser shows 
http://www.webdesignerforum.co.uk/

 

Hasn't google worked out that they are the same site and not duplicate content yet? Couldn't they just fix it at their end?



#2 Jack

Jack

    NaN

  • Moderators
  • PipPipPipPipPip
  • 3,144 posts
  • Gender:Male
  • Location:Jersey Channel Islands
  • Experience:Advanced
  • Area of Expertise:Web Designer

Posted 11 August 2017 - 02:20 PM

It depends what your primary domain is set to, usually you just use a CNAME to redirect to the non-www or www version. I don't think you will get duplicate content issues if you have a redirect in place, Google should be smart enough to know that it's the same URL, but this won't work for subdomains. You can also inform Google of your primary domain through Webmaster Tools, or you can setup canonical URL's if you start seeing duplicate content warnings.

 

I would avoid using htaccess if it's avoidable, in this case it is, because you can manage the domain redirect through your DNS provider. Htaccess can cause sites to slow down because every request causes a look-up of the htaccess file, if I remember the process is something like this:

  • Look up the root htaccess file
  • Look for any other htaccess files in other directories
  • Batch the files together
  • Reconfigure the server with the new settings

Only then will you get a file sent down the wire, and it happens for every single request and can't be cached. If you've ever seen warnings about a lengthy time to first byte, this is sometimes the cause.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users