subject: serverside delievery of appropriate language-sense pageversion worsened searchengine ranking

Sun, 21 May 2017 18:18:59 +0200 last edited: Fri, 29 Sep 2017 08:42:22 +0200

FYI: Use of one url for two or more languages with serverside delievery of appropriate language-sense pageversion worsened searchengine ranking. S. also "Make sure each language version is easily discoverable" - https://support.google.com/webmasters/answer/182192?hl=en

Keep the content for each language on separate URLs. Don’t use cookies to show translated versions of the page. Consider cross-linking each language version of a page. That way, a French user who lands on the German version of your page can get to the right language version with a single click.

Avoid automatic redirection based on the user’s perceived language. These redirections could prevent users (and search engines) from viewing all the versions of your site.

@Andrew Manning @Hubzilla Development+ @Hubzilla Support Forum+ #switch #browsersniffing #BrowserDetection #Browserweiche #sniffing #languagesensitive #serverside #seo #search #searchengine #sumo

show all 14 comments

Andrew

Sun, 21 May 2017 19:42:47 +0200

Perhaps you could make a little dropdown menu that integrates into the Hubzilla project page nav bar (use for example the icon http://fontawesome.io/icon/language/) so that people can select another language other than the auto-detected one that was served to them.

neue medienordnung plus

Sun, 21 May 2017 19:53:25 +0200 last edited: Mon, 22 May 2017 05:08:20 +0200

@Andrew Manning Thank you for nav bar suggest, but what mean you to multilingual url for multilingual pages -suggest from Google? I even believe that it would be helpful for Hubzilla-Ranking in #SERP, when each laanguage-Pages get one separate URL. For example how in my suggest data model for multilingual website hubzilla.org proposed.

neue medienordnung plus

Sun, 21 May 2017 22:35:00 +0200 last edited: Mon, 22 May 2017 06:51:06 +0200

@Andrew Manning For tests use I several Firefox-language profils. But remember that with one multilingual webpage with comanche-lang-switch can searchengines badly how one human visitor access to the page content in the required language.

Mike Macgirvin

Mon, 22 May 2017 11:26:11 +0200

Might want to just make language a supported function of the page module (and wiki module) just like it is for the help system. It's a content decision, not a presentation decision. Comanche is a presentation platform. Bonus points for adding language preference to blocks and menus. Don't get me wrong, I love the 'switch' mechanism, but there's no reason why language awareness couldn't be a built-in platform capability.

neue medienordnung plus

Tue, 23 May 2017 05:35:26 +0200

@Mike Macgirvin

Edit - just added this to webpages in red and it works well.

Mean you, that you have implement in redmatrix the language-sensitive help pages?

Mike Macgirvin

Tue, 23 May 2017 11:30:51 +0200

Looks like there's some confusion. No I implemented language-sensitive *webpages* in 'red' which is basically next generation technology (Zot 5.x) but is not being developed for public use. Hubzilla is basically Zot 4.x. Redmatrix is an abandoned project fork (Zot 2.x) that appears to have usurped/stolen by Thomas as his private workspace and personal path to fortune and glory - and I guess I'm ok with that. That code is pretty awful - and we've completely rebuilt the codebase since then.

A lot of 'red' technology has found its way into Hubzilla. This feature may eventually be backported, but that isn't my decision. I do stuff in red that many of you are going to hate me for, so I'm not choosing what features get backported to hubzilla. If somebody likes a feature they can port it. If they don't, oh well. Likewise if Hubzilla does something I hate, I probably won't port it to red. Cuts both ways.

neue medienordnung plus

Wed, 24 May 2017 06:01:11 +0200 last edited: Wed, 24 May 2017 06:09:56 +0200

@Mike Macgirvin

No I implemented language-sensitive *webpages* in 'red' which is basically next generation technology (Zot 5.x)

Apropos *webpages* vs. *help pages* .

Wich important features differences help pages from webpages for you in this kontext?
Why is it for you important, help pages from webpages to difference?
Maybe are it only context-values, the make differences between *webpages* and *help pages*? Such context-values, how *user role* or *Hubzilla mobile agent (HMA)* role (s. to HMA bottom). I suggest for example these definition for one context "Hubzilla grid: homepage, hub, help documentation"
One *Hubzilla help page* is one web page with comanche features, where help for *logged in Hubzilla user* to learn about HUbzilla

I think, the answers to these questions will help one good concept and good solution for this idea Hubzilla mobile agent Heliza

Mike's definiton for observer-object inspired me for the idea embodiment for observer-objekt as one agent, assistant, butler, intermediary, broker between the Hubzilla Community, Hubzilla knowledge base, Hubzilla engine and other fellow human. Now that in Hubzilla can more and more events to analyse with "switch" or "if" instructions, can Hubzilla ...

[ more ... ]

to design.

neue medienordnung plus

Wed, 24 May 2017 07:08:21 +0200

@Mike Macgirvin

I implemented language-sensitive *webpages* in 'red' which is basically next generation technology (Zot 5.x)

Can you describe, what you mean withlanguage-sensitive *webpages* in this context? Can you say:

for wich scenarios are these language-sensitive *webpages* designed?
what contains your implementation of language-sensitive *webpages* concept?

Mike Macgirvin

Wed, 24 May 2017 22:41:43 +0200

This was ported to hubzilla (dev branch) yesterday. So if you're running that branch you can use it now.

If you want to translate a webpage 'foo' into German you just create a page called 'de/foo' and translate the page. And you're done. Same as you would do for help pages or wiki pages. You don't have to learn Comanche or modify templates or anything else to do this. Visit the page 'foo' with a German browser preference and you'll get the German version. If you want a French version, name it 'fr/foo'. Any language that isn't recognised will load the original page 'foo' (and see the page in whatever the default language is).

If you want to specifically load the default page and over-ride the browser setting, you can visit '-/foo' and it will load the original page 'foo' regardless of browser language. This currently works for webpages and wikis but should probably be backported to the help pages for consistency.

Using this to implement a multi-lingual web project is now pretty easy, and if you want to address the bullet points in the top level post you can still do that, but it would involve a bit of extra effort. It would be extra effort no matter how you do it so nothing has changed in that regard. Basically to make it search engine friendly, you would provide a list of languages on the top page linking to the URLs of the top page for those languages and allow people to over-ride the automatic language selection by accessing those translations directly.

neue medienordnung plus

Thu, 25 May 2017 08:14:57 +0200

@Andrew Manning When can I test thelanguage-sensitive *webpages* feature on https://dev.hubzilla.org/ ?

@Mike Macgirvin

If you want to translate a webpage 'foo' into German you just create a page called 'de/foo' and translate the page. And you're done.

The requirement is, that I have an account at the website, correct?

Andrew

Thu, 25 May 2017 16:48:08 +0200

I will pull these updates on dev.hubzilla.org when I get a chance and let you know so you can begin playing with them.

By the way, you can run a dev hub in a local virtual machine, which makes it easy to tinker with stuff like this that doesn't require your hub to be accessible on the grid.

Andrew

Fri, 26 May 2017 00:59:22 +0200

dev.hubzilla.org is now at dev branch commit 31d9208.

Here's an example of what changed for the Page module:



diff --git a/Zotlabs/Module/Page.php b/Zotlabs/Module/Page.php
index 6ef285d..7bc90c0 100644
--- a/Zotlabs/Module/Page.php
+++ b/Zotlabs/Module/Page.php
@@ -43,11 +43,31 @@ class Page extends \Zotlabs\Web\Controller {
     
         $channel_address = argv(1);
     
+        // Always look first for the page name prefixed by the observer language; for instance page/nickname/de/foo
+        // followed by page/nickname/foo if that is not found.
+        // If your browser language is de and you want to access the default in this case, 
+        // use page/nickname/-/foo to over-ride the language and access only the page with pagelink of 'foo'
+
+        $page_name = '';
+        $ignore_language = false;
+
+        for($x = 2; $x < argc(); $x ++) {
+            if($page_name === '' && argv($x) === '-') {
+                $ignore_language = true;
+                continue;
+            }
+            if($page_name)
+                $page_name .= '/';
+            $page_name .= argv($x);
+        }
+
+
         // The page link title was stored in a urlencoded format
         // php or the browser may/will have decoded it, so re-encode it for our search
     
-        $page_id = urlencode(argv(2));
-    
+        $page_id = urlencode($page_name);
+        $lang_page_id = urlencode(\App::$language . '/' . $page_name);
+
         $u = q("select channel_id from channel where channel_address = '%s' limit 1",
             dbesc($channel_address)
         );
@@ -64,16 +84,31 @@ class Page extends \Zotlabs\Web\Controller {
     
         require_once('include/security.php');
         $sql_options = item_permissions_sql($u[0]['channel_id']);
-    
-        $r = q("select item.* from item left join iconfig on item.id = iconfig.iid
-            where item.uid = %d and iconfig.cat = 'system' and iconfig.v = '%s' and item.item_delayed = 0 
-            and (( iconfig.k = 'WEBPAGE' and item_type = %d ) 
-            OR ( iconfig.k = 'PDL' AND item_type = %d )) $sql_options $revision limit 1",
-            intval($u[0]['channel_id']),
-            dbesc($page_id),
-            intval(ITEM_TYPE_WEBPAGE),
-            intval(ITEM_TYPE_PDL)
-        );
+
+        $r = null;    
+
+        if(! $ignore_language) {
+            $r = q("select item.* from item left join iconfig on item.id = iconfig.iid
+                where item.uid = %d and iconfig.cat = 'system' and iconfig.v = '%s' and item.item_delayed = 0 
+                and (( iconfig.k = 'WEBPAGE' and item_type = %d ) 
+                OR ( iconfig.k = 'PDL' AND item_type = %d )) $sql_options $revision limit 1",
+                intval($u[0]['channel_id']),
+                dbesc($lang_page_id),
+                intval(ITEM_TYPE_WEBPAGE),
+                intval(ITEM_TYPE_PDL)
+            );
+        }
+        if(! $r) {
+            $r = q("select item.* from item left join iconfig on item.id = iconfig.iid
+                where item.uid = %d and iconfig.cat = 'system' and iconfig.v = '%s' and item.item_delayed = 0 
+                and (( iconfig.k = 'WEBPAGE' and item_type = %d ) 
+                OR ( iconfig.k = 'PDL' AND item_type = %d )) $sql_options $revision limit 1",
+                intval($u[0]['channel_id']),
+                dbesc($page_id),
+                intval(ITEM_TYPE_WEBPAGE),
+                intval(ITEM_TYPE_PDL)
+            );
+        }
         if(! $r) {
     
             // Check again with no permissions clause to see if it is a permissions issue

neue medienordnung plus

Fri, 26 May 2017 09:57:04 +0200 last edited: Fri, 26 May 2017 10:04:37 +0200

@Mike Macgirvin

If you want to translate a webpage 'foo' into German you just create a page called 'de/foo' and translate the page.

I mean, for search friendly, SEO-optimized URL's is it inpossible for all languages same address foo to use. URL-value, keywords in URL's are important for pageranking - s.

Therefore is it important, that URL contains keywords, suitably for respective language in each page.

neue medienordnung plus

Fri, 26 May 2017 10:09:01 +0200

I included the solution "Support for publishing of search engine friendly multilinguage content" in my speech/ presentation Hubzilla - introduction, possibilities, Hubzilla community - in three languages

http://hub2.sprechrun.de/page/hucope/hubzilla_tools_page_en