duplicate url error

I was looking at web master tools sitemap and it said that i have an error in my sitemap and that i should remove it. It tells me that i have dublicate url for my forum.

Am i getting the error because i have the url in extra-urls.txt also?

I was not getting this error before.

Hello ,

It looks like Google implemented a new warning. We are currently investigating what can cause this.

I removed the url from extra-urls.txt and regenerated the sitemaps. I'm hoping if that works.

Thanks Mert,

I also had warnings for duplication of urls in my sitemap. Webmaster was telling me the poll.php urls were being duplicated so i removed poll.php from the sitemap and resubmitted, it seems to be fine but ill check back later.

I only have the sitemap generator plugin installed from vbulletin.org but i dont have vbseo.

i got same issue with tags , i removed tags from sitemap and resubmitted now no error but i dont think removing tags is a good idea :(

Tags can be good to have. However, it all depends on what your users are actually using FOR the tag itself. I personally do NOT include tags in my sitemaps, and still, many tag pages are indexed in the SERPs.

Originally Posted by Julio

It tells me that i have dublicate url for my forum.


I was not getting this error before.

i have the same problem

any updates ??

Duplicate URL's in my sitemap to. How can I remove Tags from my sitemap?

Admincp - vBSEO Sitemap generator settings - include Tags pages choose no and then save your settings
and remove all .gz files located in your data folder and then re-generate your sitemap manually

How do I re-generate my sitemap manually?

1) Remove files ending in .gz from your vbseo_sitemap/data folder
2) Login to your vbseo_sitemap, and generate sitemap.

Originally Posted by Michael Biddle

1) Remove files ending in .gz from your vbseo_sitemap/data folder
2) Login to your vbseo_sitemap, and generate sitemap.

I did that but I still keep getting an error saying that there is a Duplicate URL and I disabled Tags

Google has changed a few things and is throwing this error. We are currently looking into this.

So will there be no links being indexed to google because of this until you guys find a fix?