Both. The free TranslatePress plugin includes trp_translate, the trp_dictionary tables, and the visual editor needed for the integration. Pro features like SEO Pack and Browse as Other Roles continue to work alongside SleekPixel without conflict, since SleekPixel only consumes the public translation helpers, not internal Pro APIs.

For requests that bypass the front end like REST endpoints and CLI runs, SleekPixel reads the locale from the queried URL prefix or from the explicit locale parameter on the WP-CLI command. For standard front end requests it uses the TRP_Settings global state, which TranslatePress sets early in the request lifecycle.

Yes. Per page settings let you skip per-locale rendering for specific pages, useful for legal disclaimers or third party embed pages where a translated card would be inappropriate. The skipped pages fall back to the source language card, which still serves all locales until you flip them on.

Yes. Automatic translation writes into the same trp_dictionary tables that human edits write to, so the SleekPixel render path treats automatic and human translations identically. Cards regenerate after automatic translation batches finish through the same dictionary write hooks that handle manual edits in the visual editor.

trp_translate returns the original source string when no translation row exists, which means the card renders with the source language headline rather than failing or showing an empty slot. This is the safest fallback, since it keeps the share preview functional while you backfill missing translations through the visual editor.

Yes. The corner mark slot accepts either the raw locale code or a human readable language name. WordPress core ships a locale to language name mapping that SleekPixel can use, or you can override per locale with a custom string in the template settings, useful when marketing prefers a friendlier label.

Yes. SleekPixel writes og:image and twitter:image meta tags, which sit outside the hreflang and canonical URL concerns that multilingual SEO plugins manage. Yoast, Rank Math, and SEOPress all coexist without conflict because their multilingual modules focus on link tags rather than image meta tags on translated URLs.

trp_translate is heavily cached in TranslatePress itself, hitting the database only on initial dictionary load per request. The card render adds a single dictionary lookup per slot, which is negligible compared to the PNG generation cost. Once the card is cached as a PNG, the translation cost disappears for subsequent requests entirely.