Forum Moderators: Robert Charlton & goodroi

Message Too Old, No Replies

site-operator returns a 302 at the top of the serps

         

efendi

4:41 pm on Mar 20, 2009 (gmt 0)

10+ Year Member



hello,
i have a short question (and excuse me for my bad english).

if i take search with the site-operator like this:

site:www.domain.com -site:www.domain.com/*

and

-site:www.domain.com/* site:www.domain.com

google returns:

302 Found
Found. The document has moved here. Apache Server at www.domain.com Port 443.
www.domain.com:443/ - 1k

at the top of the serps.
can this issue hurts my ranking?

thanks a lot
efendi

[edited by: tedster at 7:04 pm (utc) on Mar. 20, 2009]

tedster

7:17 pm on Mar 20, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



If it's already indexed (and it is) your rankings are already showing any effects. This is certainly the kind of url that Google would make supplemental, and that's a good thing.

I'm surprised that this shows up at all - normally Google would index the content of the 302 redirect target page. Do you have a chain of 302 redirects in place?

g1smd

8:39 pm on Mar 20, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



The Port 443 reference bothers me. Is this a redirect to an equivalent HTTPS URL?

What's the full chain of URLs and the HTTP status for each one when this is clicked?

efendi

9:57 am on Mar 27, 2009 (gmt 0)

10+ Year Member



Sorry for my late reply.

g1smd, you helped me in this thread:
[webmasterworld.com...]
and this htaccess i use actually

This is a abstract from my .htaccess und apache conf-file

conf:

<VirtualHost 192.168.1.1 (example!):443>

RewriteEngine On
RewriteCond %{HTTP_HOST} !^192.168.1.1 (example!)
RewriteCond %{HTTP_HOST} !^www.domain.com
RewriteRule ^/(.*) [domain.com...] [L,R]

htaccess:

RewriteCond %{HTTP_HOST} !^192.168.1.1$
RewriteCond %{HTTP_HOST} !^(www\.domain\.com)?$
RewriteCond %{SERVER_PORT}s ^(443(s)¦[0-9]+s)$
RewriteRule (.*) http%2://www.domain.com/$1 [R=301,L]

i'm not so familiar in this zone. so my question: is this correct? do you need more information?

efendi

Receptional Andy

11:37 am on Mar 27, 2009 (gmt 0)



I'd be pretty sure the page returns a 200 OK HTTP status instead of a 302.

Incidentally, does the destination for the "here" link point at something like error/HTTP_BAD_REQUEST.html.var?