Support » Plugin: The SEO Framework – Fast, Automated, Effortless. » Compatibility with TranslatePress

  • Hi dev,

    On Knowledge Base TranslatePress is mentioned as “compatible”, but I can’t find any specific info.

    I make some check on my site, and understood that TSF simply leave TranslatePress doing its job without any interference, but there is no integration at all. I mean:
    – no translated pages added to sitemap;
    – no translated pages meta descriptions (which have to be done on TranslatePress)

    Is that right?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Sybre Waaijer


    Howdy! Sorry for my delayed reply.

    That is right.

    TranslatePress does not store translated pages into the database conventionally, which means we can’t retrieve those for generating a sitemap. This also means we cannot store metadata for it conveniently — if at all feasible.

    TSF can read the pages queried and provide automated SEO for those out of the box. TranslatePress, in turn, correctly provides hreflang meta links to your pages, so the translated versions will be found by search engines and have attributed automatically languages for indexing.

    Thread Starter masvil


    I appreciate your detailed response. You make very clear most sites don’t really need a sitemap. Anyway I’m working on a new one, and I need it to be indexed quickly.

    1. Is there a way to add URLs to the TSF’s standard sitemap?

    2. Don’t hate me for this: why other SEO plugins support TranslatePress or the other way around?

    3. Unrelated: is there a Focus extension demo I can try? I can’t even find a video on YT.

    Plugin Author Sybre Waaijer



    Indexing quickly won’t help with ranking. We also found that new sites are struggling with indexing lately, only explainable by algorithm changes out of our control.

    To answer your questions right away:

    1. This requires using code. You can append any string to the sitemap using the_seo_framework_sitemap_extend, or provide a map of URLs via the_seo_framework_sitemap_additional_urls. I advise against doing this and spend time improving the user-facing part of the site instead.
    2. They don’t. TranslatePress added support, not vice versa. TSF didn’t require a patch, and I have yet to see data proving that expanding the sitemap is useful.
    3. Unfortunately, we have yet to realize this. We do offer a 30-day no-questions-asked refund policy.

    I hope this helps! Cheers 🙂

    Thread Starter masvil


    While quick indexing doesn’t help with ranking, I’m dealing with an edge case. I’m working to a new website for a client in a very, very small niche with small competition. They think the indexing itself will give them some visibility.

    1. Good to know it can be done. I hope in the future you will add this feature to the GUI. I understand you’re confident on the uselessness of the “expanded” sitemap, and I guess you debated on this topic countless times.

    2. It’s surprising to realize that SEO plugins claiming to “support” TranslatePress actually are just supported by it. Thanks for sharing!

    3. That’s great, I will take this opportunity. Just first I would like to know if it is possible to restrict the access to certain categories of users on backend. Asking in advance so I get ready.

    Plugin Author Sybre Waaijer


    I understand what you wish for, but by the time we find a proper workaround, Google’d have processed all pages already without any help. But, if you must, you can request indexing via Google Search Console; see

    1. Yup.

    2. No problem )

    3. Yes, that’s possible. Let me know what you’re looking for specifically.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Compatibility with TranslatePress’ is closed to new replies.