SEO gone mad...
al-nginx at none.at
Tue Oct 13 20:46:56 UTC 2015
Am 13-10-2015 21:39, schrieb steve:
> Thanks for all the replies - I've not been ignoring you, I'm just in a
> different timezone!
> On 10/14/2015 03:16 AM, Patrick Nommensen wrote:
>> On Tue, Oct 13, 2015 at 6:09 AM, Andrew Hutchings
>> <ahutchings at nginx.com> wrote:
>>> On Tuesday 13 October 2015 08:59:02 steve wrote:
>>>> Hi folks,
>>>> I have a requirement from a customer that the terminal slash be
>>>> rewritten when accessing the homepage - eg example.com/  is a
>>> 301 to
>>>> example.com 
>>>> I've tried a simple rewrite of ^/$ but that just loops.
>>>> Any ideas?
>>> As you have seen in other answers this will be pretty much
>>> impossible to get
>>> instead? Something like this:
>>> At least then (in theory) you can have the illusion of hiding the
>>> slash without risking breaking browser support for the site.
>> You can set a canonical URL if your intention is for SEO. This is the
>> standard practice.
>>> Kind Regards
>>> Andrew Hutchings (LinuxJedi)
>>> Senior Developer Advocate, NGINX Inc.
> As can be seen from the google article, it's apparently a bad thing(tm)
> to duplicate content for example.com/ and example.com. Apparently some
> .htaccess tweak can do a 301 redirect from one to the other, but
> absolutely nothing that has been suggested ( or others that allegedly
> work - like redirecting ^/(.*)/ ) does actually work with nginx, which
> is exactly what I expected to happen.
> The CMS ( it's Magento but that doesn't really make a difference )
> rewrites the URL to the value stored in the database anyway, but the
> 'problem' is that it doesn't redirect.
> As has been suggested, this is a complete non-event, as every page
> contains a canonical header entry anyway! Have suggested that client
> engages other SEO 'consultants'.
Good suggestion ;-)
> Now need to wash the snake oil out of my head (:
> Thanks for your help.
> Steve Holdoway BSc(Hons) MIITP
> Linkedin: http://www.linkedin.com/in/steveholdoway
> Skype: sholdowa
>  http://example.com/
>  http://example.com
> nginx mailing list
> nginx at nginx.org
More information about the nginx