PDA

View Full Version : Solved Translated links without URL Tracking



cadaver
01-07-13, 08:20
Hi there,

I would like you ask for your help / suggestion:

On our forum we have setting "URL tracking" => "NO" - then to see translated content, users always have to click language link + language part ( for example /fr/, /de/ ) is not added to links - but links on their own are translated.

Example:
1. English page (forumdisplay):
{domain_name}/hello-welcome

link to thread on that page:
{domain_name}/12345-thread-title-here.html
title:
Thread Title here

2. German page:
{domain_name}/de/hello-welcome

link to thread:
{domain_name}/12345-thread-titel-hier.html
title:
Thread Titel hier


But link: {domain_name}/12345-thread-titel-hier.html redirects back to {domain_name}/12345-thread-title-here.html - because there is no language parameter ( due to settings for "URL tracking" => "NO" ).


I have 2 questions:
a) Is there any chance - with setting "URL tracking" => "NO" - dont translate actual links - just text?

b) Isnt this how it should be correct "seowise" ?

Thanks for help.

Marcin Kalak
01-07-13, 13:26
Link is generated from the current topic. If the topic is translated the link it is translated. You can disable translation of certain topics using [langtitle = nt] (http://www.vbenterprisetranslator.com/forum/vbet4-general-discussions/3168-how-make-some-text-not-translated.html).
Translated links are better for SEO.

cadaver
02-07-13, 11:19
Translated links are better for SEO.
But these links dont work - and they are redirected into original thread link

See this:
Translated link: {domain_name}/12345-thread-titel-hier.html
redirects back to
Original link: {domain_name}/12345-thread-title-here.html
- because there is no language parameter ( due to settings for "URL tracking" => "NO" ).

How that can be good for SEO? (seems more like cheating + duplicated content issues)

cadaver
02-07-13, 11:23
Link is generated from the current topic. If the topic is translated the link it is translated. You can disable translation of certain topics using [langtitle = nt] .

This is fine, but we dont want translated links on any transalated page:


See this:
2. German page:
{domain_name}/de/hello-welcome

link to thread:
{domain_name}/12345-thread-titel-hier.html

as these links redirect back to original.

Adding parameter as suggested in that thread is simply no way to go - and that's why I'm asking, if there is any way do it quicker by changing settings (havent found) OR by modifying code. (As I believe, with "URL tracking" => "NO" links shouldnt translate)

Thanks for your help.

Marcin Kalak
02-07-13, 17:07
OK, I see the issues. We propose currently turn on url tracking, it will be better for the users. We fix bug of course.

Marcin Kalak
09-07-13, 13:21
This issue is a question of vBSEO. vBSEO generated for link there is no distinction between verification correctness and content. Through it can not be done so that the links have been translated in the URL the browser, and not not be translated on the page. So now you can turn on url_tracking, it is recommended and very good for the users. You can also stay with url_tracking disabled and delete integration with vBSEO, but then you will not translated links, which is not recommended. You can also stay with the current situation, which is also not recommended, because it's not user-friendly and causes unnecessary redirects.
This issue is a limitation vBSEO and not our fault and we are not able to change that, despite intentions.
We apologize for the late reply, but we worked on it trying to make changes, but unfortunately, we came across vBSEO limitation that thwarted such a change.

AfrikaansAlbanianArabicBelarusianBulgarianCatalanChineseCroatianCzechDanishDutchEnglishEstonianFilipinoFinnishFrenchGalicianGermanGreekHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalianJapaneseKoreanLatvianLithuanianMacedonianMalayMalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishTaiwaneseThaiTurkishUkrainianVietnameseWelshYiddish
Translations supported by vBET 4.10.1