Hello Antti, The requirement is that the page-properties would allow to override the URL-part for the specific page, say we'd like to have: Locale URL Base locale, default language www.mywebsite.com/article.html German www.mywebsite.com/de/artikel.html French www.mywebsite.com/fr/article.html Spanish www.mywebsite.com/es/article.html
actually, the language part is currently passed as a GET-parameter and a Cookie, we will probably re-add the prefix for making the link SEO and to avoid confusion if multiple languages define the same in different languages. So, a special i18n-content support could be the solution I suppose, respecting a localized node-data (friendly_URL[_language-code]), probably also using a URLized Page-title by default. We then will have to find the page somehow on a custom JCR query for finding the page in the tree, generate the hierarichical URL, cache the URL mapping somewhere probably in a virtual (redirect) page to gain performance. The requirement is somehow complex in my opinion, so I don't expext Magnolia to support this OOTB. We have to work out a detailed spec about the way it must work exactly. Best regards Marco -- 15 Years of Excellence - http://netcetera.com Marco Glur | [email protected] T +41 44 247 79 20 Netcetera AG | 8040 Zurich | Switzerland | http://netcetera.com From: [email protected] [mailto:[email protected]] On Behalf Of Antti Hietala Sent: Mittwoch, 29. Juni 2011 09:10 To: Magnolia User-List Subject: Re: [magnolia-user] SEO localized URLs Hi Marco, Can you describe how you want to localize your URLs? What should they look like? Magnolia's i18n support allows you to append a locale identifier to the URL. The example use case is on pp. 23-25 in the SEO Tech Brief. http://www.magnolia-cms.com/dms/products/tech-briefs/seo/Magnolia-T ech-Brief-SEO.pdf Locale URL Base locale, default language www.mywebsite.com/article.html German www.mywebsite.com/de/article.html French www.mywebsite.com/fr/article.html Spanish www.mywebsite.com/es/article.html You can store localized content in a single hierarchy or separate trees (Will's choice). http://documentation.magnolia-cms.com/technical-guide/i18n.html#C ontent Yet another option is to create virtual localized URIs and map them to language or geo-specific content. This may work if you don't plan to translate/localize the entire site but only a representative "landing page" for each locale. For example, create a Spanish landing page at /landing/es.html and map a virtual URI such as www.example.com/es to that page. http://documentation.magnolia-cms.com/technical-guide/virtual-uri-ma pping.html ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
