Forum Moderators: Robert Charlton & goodroi
ABC.asp?Id=1
ABC.asp?Id=4234
ABC.asp?Id=99203
site:www.site.com -inurl:www.site.com inurl:ABC
I get almost 1K supplemental results for this page, and I am pretty sure the problem is that all of these pages have the SAME description meta tag. Has anyone else seen this as well?
The issue is that those urls might all represent unique content, so search engines will look at each issue. If this goes on to an extreme degree, you may lose your regular listings, too. Can you programtically add a meta robots noindex tag to the head section if there is a query string?
ABC.asp is counted as supplemental for each instance.
eg.
ABC.asp?Id=126
ABC.asp?Id=23432
ABC.asp?Id=33
If I change the description tag so that it is unique, will G remove these pages from the supplemental index? Do I have to email them to do this?
I am also in the process of finishing a project that rewrites the ABC.asp page from:
ABC.asp?Id=126 into ABC_126.asp
ABC.asp?Id=23432 into ABC_23432.asp
ABC.asp?Id=33 into ABC_33.asp
and the old ABC.asp?Id=someNumber will return a 302 Object moved status. What do you think? I can programatically change the META description tag so all pages have a different tag.
This page does not have a lot of content (limit of 500 characters for the main section of the page). Do you think this is moreso the problem than the duplicate META description tag across all instances of this page (regardless of the Id parameter in the querystring)?
500 characters is not a lot of on page content, but if it is, say 70% to 80% unique, that can still be enough. In that situation a unique meta description can often fix the problem.
If ABC.asp page is rewritten as the following, would this be better or should I only change the meta description tag and leave the rewrite for later?
ABC.asp?Id=126 into ABC_126.asp
ABC.asp?Id=23432 into ABC_23432.asp
ABC.asp?Id=33 into ABC_33.asp
and the old ABC.asp?Id=someNumber returns a 302 Object moved status.
That is exactly what you want to happen.
A 302 does not enable that to happen. Use only the 301 redirect. Check that it really is a 301 by using a HTTP header checker.
Oh, and make sure that all of your new URLs are entirely in lower case. You really do not want to have duplicate content issues where a page is indexed multiple times with mixed case URLs. Don't even go there.
[edited by: g1smd at 10:09 pm (utc) on June 23, 2006]
check out this thread for more on what 301 permanent redirects are, how to implement them, and what they mean to search engines:
[webmasterworld.com...]
basic implementation: [webconfs.com...]
Jonathan