Last post 52 min ago

Posts last week 81

Average response time last week 4 hours 29 min

All time posts 67944

All time tickets 10505

All time avg. posts per day 20

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#8579 – How to handle a multilanguage website

Posted in ‘4SEO’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Thursday, 10 March 2022 15:18 UTC

olliek

Hi,

I would like ask you how to handle a multilanguage website?
Does it make sense to analyse all language versions seperately ( /en, /fr, /es ...) and generate seperate sitemaps in each language for Google Search Console?

Thank you and best regards
Oliver

Thursday, 10 March 2022 15:42 UTC

wb_weeblr

Does it make sense to analyse all language versions seperately ( /en, /fr, /es ...)

There's nothing special about a multilingual site, all pages are just regular pages. 4SEO analyzes all pages on a site, so it will analyze all languages.

generate seperate sitemaps in each language for Google Search Console?

All pages are already analyzed and those useful are included in the sitemap (sitemap-4seo.xml). This sitemap itself is broken down into separate smaller sitemaps: per language and with a maximum of 1000 pages per sub-file. But this is internally managed and you do not have to do anything.

There's only one single sitemap (sitemap-4seo.xml) and it's actually automatically submitted to Google and Bing (unless you disabled that feature).

Best regards

Yannick Gaultier

weeblr.com / @weeblr

Sunday, 10 April 2022 05:34 UTC

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.