PDA

View Full Version : Accepted VBseo Sitemap Problems



wowglider.de
03-05-11, 15:26
Hello,
im happy to see that you are now finally translating urls.

(e.g. per Handy oder Telefon bezahlen? (http://wow.glider-forum.de/neuigkeiten/33870-per-handy-oder-telefon-bezahlen.html)
->
pay by mobile phone or telephone? (http://wow.glider-forum.de/en/neuigkeiten/33870-pay-by-mobile-phone-or-telephone.html))

But it seems the VBSEO Sitemap is not using them, so i get many many errors in google webmaster tools.

(like "Please use direct links in your sitemap and fix your 301 redirections")

Is it possible to fix this?

Thanks

kamilkurczak
03-05-11, 16:50
this is full message from google? if not - please paste here a full one, will be helpful. Thanks

vBET
03-05-11, 21:13
Hi. Please note that this is not a bug - this is known feature. We do not translate links for sitemap integration because of performance issues. Otherwise generating sitemap will require much more resources. We already described it several times in thread for sitemap translation.

Also please note that 301 is not error - this is appropriate way to tell Google that real link is somewhere else. Google prefers to have direct link (for performance of his robots), but not direct is harmless and will appropriately (still with 2 requests) bring robot to your page.

At this moment we have lot of plans for new vBET functionalities, that is why we do not give high priority to improve sitemap generator integration. Actual one is not perfect, but working and also this is not necessary. You can use vBET without this integration - Google will still index your translated sites, because links will be found on your pages, maybe solver, but will. This is why it do not have big priority, but we are aware about this need.

I will move this thread to feature requests.

wowglider.de
03-05-11, 22:32
I dont understand the problem. You are already translating all the URLs, it just needs to be correct included in the sitemaps.xml. I dont mind how much resources this needs, the sitemap is only created one time a day or less... so this would be affordable.

The right error message is:
Not referring URLs
In the Review of some of the URLs from your Sitemap, we have found that some of the URLs refer to other sites. We recommend that your Sitemap contains URLs to the final destination (the Redirect target) refer instead to a different URL to refer to it.
HTTP error: 301
URL:
http://wow.glider-forum.de/be/bugs-and-probleme/32451-probleme-priester.html
Problem detected on: 28.04.2011
-
Not referring URLs
In the Review of some of the URLs from your Sitemap, we have found that some of the URLs refer to other sites. We recommend that your Sitemap contains URLs to the final destination (the Redirect target) refer instead to a different URL to refer to it.
HTTP error: 301
URL:
http://wow.glider-forum.de/be/bugs-and-probleme/32261-gather-funktion.html
Problem detected on: 23.04.2011
-
Not referring URLs
In the Review of some of the URLs from your Sitemap, we have found that some of the URLs refer to other sites. We recommend that your Sitemap contains URLs to the final destination (the Redirect target) refer instead to a different URL to refer to it.
HTTP error: 301
URL:
http://wow.glider-forum.de/no/bugs-and-probleme/32888-instanz-problem.html
Problem detected on: 17.04.2011

vBET
04-05-11, 12:16
Yes you have right - this is done only once per day and we are already translating URLs. Still there are several issues:
- for large forum adding even not translated URLs to sitemap causes issue with mysql sever gone away and requires mysql configuration changes, because of long generation time
- at this moment vBET API do not provide function which allows to ask for all translations to one sentence. And this will be obligatory, otherwise generation of sitemap can cause to much little queries to Google and be considered as attack. And even if not it will drastically extend generation time because Google punishes for such behavior by extending time for next responses or even temporary ban (in such case it is left after contact with Google - any of our client didn’t have it in months and we like our clients to feel safe :)).

Please note that we have in plan to make such functionality, because we want make configurable to generate flags with final URL also (now requires 1 redirect when someone clicks it for translated URL). And when we will add this functionality we will describe how to integrate sitemap generator having already translated URLs.

So at this moment we recommend to wait until it will be provided. If you want to made own modification in sitemap generator integration code using vBET API please be aware about possibility of ban in case of too many little queries to Google in short time. Also please be aware about vBET optimization mechanism which delays URL translations - in early versions we made the mistake and send separate query for each URL, so we really know what we are writing here about. Right now we delay URL translations and ask for it in separate stage having al little requests to Google as possible (limited by maximum URL length for Google translation request). But you cannot use this mechanism - it translates URLs from one page so it made translations to one language. You need to translate one sentence to all languages.

I'm changing status of this request to accepted. Still please keep in mind that it has low priority, because it is for 3rd party integration which is not necessary (if you will not integrate you will have exactly same vBET functionality, and in actual integration you have only warnings with Google recommendation - recommended means that other one is still appropriate, just not best possible).

If you need any additional explanation or just want to give additional hints, comments, ideas - please feel free to write :) We always appreciate our users input :)

AfrikaansAlbanianArabicBelarusianBulgarianCatalanChineseCroatianCzechDanishDutchEnglishEstonianFilipinoFinnishFrenchGalicianGermanGreekHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalianJapaneseKoreanLatvianLithuanianMacedonianMalayMalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishTaiwaneseThaiTurkishUkrainianVietnameseWelshYiddish
Languages translations made by vBET 4.9.2