Old 302 Hijack now supplemental? Forward-slash-dot on domain ending?

Very weird site problems with Google causing poor rankings but no ban?

[pieman fellis]

Prob 1:

An old (fixed) 302 Hijack now shows as supplemetial result. This this does not appear when using "site:mydomain.com" only for specific searches to include both domain names.

The story was I bought a domain and used the domain company control panel to forward the domain to my website - they were still using the old 302 redirect which caused me to hijack myself! I then changed this a few days after the problem to a 301 redirect. Shall I stop this 301 also, could this still be hurting me?

Prob 2:

I have also found a forward slash dot problem "/." e.g. "www.mydomain.com/." - what is the /. all about, this result appeared on Web Position Gold 3 when I was doing some research.

Could this be the reason why my website is supressed in Google, it used to rank well?

[tedster]

I would wait just a bit. The 301 is correct, but recently something went whacky at Google and some old historical 302 domains started showing up again. I think it's their bug ad I expect it to be fixed next week or so.

If the 301 is sending you any backlink happiness at all, you wouldn't lightly drop the 301. But if the SERP hijack continues, then you have a judgement call to make, based on your total picture.

The slash dot thing sounds like a typo somewhere. Does your server respond to that?

[jd01]

I think Tedster is right to say, 'just wait'.

If you run into real problems, you might remove the 301 from the index only and put some short text, with a 10 sec. meta-refresh and link to the target domain.

(I recommend 'noindexing' the index page of the domain currently being redirected if you go this route.)

Something like:

RewriteCond %{REQUEST_URI} !^/(index\.html)?$
RewriteRule (.*) http://www.target-domain.com/$1 [R=301,L]

Will redirect everything, except requests for / OR /index.html to the target domain, but will allow the index page to be loaded.

Justin