kimitri
Forum Replies Created
-
Thanks, @cybr!
Unfortunately, we’re still experiencing issues with sitemaps. It seems that sitemap language can now be set using the
langGET parameter but the “normal” language selection (path prefix in our case) does not work.The original site I gave as an example in the original report is not yet using the updated version of the plugin but we tested updating the plugin on another site that was suffering from the same issue. Here are links to the site:
- https://www.portofhelsinki.fi/sitemap.xml (works, provides the sitemap for the main language)
- https://www.portofhelsinki.fi/sitemap.xml?lang=en (works, provides the sitemap for the given language)
- https://www.portofhelsinki.fi/en/sitemap.xml (does not work, worked before updating TSF from 4.x to 5.x)
Is there anything I can do to assist you in debugging this?
Hi Sybre,
Sorry for the delay! Naturally, we’d prefer to use the optimized sitemaps so I think going ahead with the debugging option is the way to go. Just give us the code you use to debug and we’ll provide you with the dump.
Thanks!
Hi Sybre!
Unfortunately, this problem is not resolved. The problem is that after updating The SEO Framework plugin from 4.x to 5.x sitemap is generated only for the main language – all other language versions now return a 404.
This poses a problem for a lot of our websites as there are big differences in the amount fo content for each language. Just relying on providing hreflang-links is not enough as some of the content may not exist for the main language.