I'm actually not using vbseo due to the impact it has on my server and I was pretty happy with the way search engines were indexing my website untill now.
I only tested vbseo for 2 or 3 days but that was months ago.
This is a discussion on Google - Sitemap have the same priority within the General Discussion forums, part of the vBSEO Google/Yahoo Sitemap category; I'm actually not using vbseo due to the impact it has on my server and I was pretty happy with ...
I'm actually not using vbseo due to the impact it has on my server and I was pretty happy with the way search engines were indexing my website untill now.
I only tested vbseo for 2 or 3 days but that was months ago.
I strongly advise you to reconsider trying vBSEO again. As the current version is not encoded and it is not hard on servers. You can also consider applying the optimization tips mentioned at : vBSEO Optimization Tips
Mert Gökçeimam / Crawlability Inc.
vBSEO 3.6.0 Alpha Önizlemesi - Including Like Tree
Unveiling the NEW vBSEO Sitemap Generator 3.0 - available NOW for vBSEO Customers!
Twitter:@Depkac
Personal Blog : Mert Gökçeimam
Already tried it but my load goes trough the roof.. really need a little bit more horsepower to run vbseo. And I do want to use it in the future but first I need my adsense earnings to go up to pay for a new server :-P
I will have a look at the optimization tips..
i still have warnings in 3 sitemaps after editing!
Top Web Hosting List
I'm getting the same problem. Dropped down from 8950 to 619 indexed URLs.
I now have three site map pages flagging up errors. Tried changing to smart priority of pages, dropping pages down from 1.0 to 0.9.
I'm going to kill off the site map pages and regenerate them today to see if that makes any difference
Regarding the original problem with warnings, is there any other suggestions? Because clearly the fix does not work in the long run.
The latest sitemap includes a fix, but if the messages are still occurring, we will continue to monitor it to find a new solution.
As far as I've noticed, this problem only started to occur after the upgrade to 2.2
The issue was first reported a few weeks ago, prior the 2.2 version of the sitemap getting released.
You should re-apply the fix.
Oleg Ignatiuk / Crawlability Inc.
Security vbulletin - Patch Level for all supported versions released!
Unveiling the NEW vBSEO Sitemap Generator 3.0. - available NOW for vBSEO Customers!
That's the problem, I even uninstalled the sitemap plugin, and upgraded then applied the fix as well.
What is the sitemap URL that gets warnings? Did you regenerate and resubmit sitemap after applying the fix?
Oleg Ignatiuk / Crawlability Inc.
Security vbulletin - Patch Level for all supported versions released!
Unveiling the NEW vBSEO Sitemap Generator 3.0. - available NOW for vBSEO Customers!