Hi Khashayar,
TranslatePress does not store translated pages in the database conventionally, so we can’t retrieve these when generating a sitemap. This also means we cannot store metadata for it conveniently — if at all.
TSF can read the pages queried and provide automated SEO for those out of the box. TranslatePress, in turn, provides hreflang meta-links to your pages and correctly updates the permalinks. So, the translated versions will be found and indexed by search engines in the actual language.
The sitemap is a redundant tool anyway: It only helps to speed up indexing, but actual crawling is done by following internal links. If you search for your English site on Google, you can find they have already found and indexed the English pages.
Let me know if you have any more questions. Cheers!
Hi Sybre and thanks for the response.
I understood, I just thought it would look good and off course be 1% advantage and be beneficial, if I had them listed in my sitemap.
One question though, what do You mean when You say
“TSF can read the pages queried and provide automated SEO for those out of the box.”
Especially with “out of the box” ?
Best regards
Howdy!
“Out of the box” is a saying that means “without any input or configuration required” or “it just works.”
You probably found that, if you look at the page’s source, the metadata of TSF are translated with the page.
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.
Hi @kimitri,
What translation plugin are you using? TranslatePress, Polylang, WPML?
TSF was never able to support TranslatePress due to how their translation works.
If Polylang or WPML, please see if adding ?lang=en, ?lang=es, etc. works for the sitemaps (more info here). We found that some configurations of Polylang loaded language support too late for the upgraded sitemaps, but setting the language flag mitigates this.
If that doesn’t work, could you please open a new topic and explain the details? https://tsf.fyi/support/tsf/new-topic
Thanks!
