Re: HTACCESS 301 - how do you point, when current URL has //
Posted: Thu Apr 09, 2015 11:38 am
I think I have.
We have URLs that have somehow been posted to the system (ie. in forums or even bad old links) that have blanks between the //.
The expected behaviour is that my HTACCESS line of code takes that said URL thru to another page.
On some of them, it DOES seem to work, and goes to /selectpage, which is a custom page we run that is more useful to the customer. However Google thing it isn't, and says "Googlebot couldn't crawl this URL because it points to a non-existent page. Generally, 404s don't harm your site's performance in search, but you can use them to help improve the user experience".
For privacy reasons I've been asked not to provide all HTACCESS details here. Sorry.
I don't understand why some the // are going to my error page, but Google sees that as NOT correct.
I've jsut checked a few at random, and they all go to my custom page. So rather than some 404 black and white page, it goes to an internal page. But Google doesn't see it like that, and I don't know why.
We have URLs that have somehow been posted to the system (ie. in forums or even bad old links) that have blanks between the //.
The expected behaviour is that my HTACCESS line of code takes that said URL thru to another page.
On some of them, it DOES seem to work, and goes to /selectpage, which is a custom page we run that is more useful to the customer. However Google thing it isn't, and says "Googlebot couldn't crawl this URL because it points to a non-existent page. Generally, 404s don't harm your site's performance in search, but you can use them to help improve the user experience".
For privacy reasons I've been asked not to provide all HTACCESS details here. Sorry.
I don't understand why some the // are going to my error page, but Google sees that as NOT correct.
I've jsut checked a few at random, and they all go to my custom page. So rather than some 404 black and white page, it goes to an internal page. But Google doesn't see it like that, and I don't know why.