When I check the Who's online page on the backend of my OSCommerce site the following IP address will sometimes be appearing 60+ times:
[url removed, login to view]
I believe it is a googlebot.
At the present time I can only see one instance of it. However it is on the page:
/[url removed, login to view]¤cy=BRL
I don't even know how it is finding such long url strings. Clearly I don't want it to be indexing such long strings. It should only index
/[url removed, login to view] and
/[url removed, login to view] (just an example of a filter id number)
I have also noticed it here:
/[url removed, login to view]
It shouldn't find urls in this format because I use the SEO URLS contribution. There should not be any links on our site to the urls in this format! I also use a contribution that sets up canonical links (something like 'sam's canonical link contribution').
All these problems seem to have arisen after installing the loginradius contribution (which allows customers to login via facebook/gmail etc). However, because this module was directing customers (and I believe the googlebots) to [url removed, login to view] I uninstalled it.
In the past week many of our pages (listed on our google sitemap) have dropped out of the google index. This seems to be because google was seeing [url removed, login to view] for many of our pages, and is now trying to index pages with long query strings attached and penalising for duplicate content.
I have prevent spider sessions set to true, and force cookie use on.
...so the job is to sort this out so that google spiders and indexes our site normally again. We would like someone with experience because SEO is very important to our business.
EDIT: I would like the winner of the bid to be able to keep me up to date with what they intend to do, and what they have done!
5 freelance ont fait une offre moyenne de 213 £ pour ce travail
Dear Sir, We have already fixed lot of problems like this. We are interested and ready to start straight away. Please let us know if you need any more information. Thanks
Hello, I have extensive experience with resolving issues of this nature on several CMS platforms. Please see your inbox for further details and a plan of action.