Just the plugin. The Weglot WordPress plugin already holds the API key in wp_options.weglot_options and exposes translation helpers through PHP functions like weglot_translate and weglot_get_current_language. SleekPixel calls those helpers, never the Weglot API directly, so the API key remains scoped to the official integration.

Translation calls from the helper are cached by Weglot itself in its own option storage. If a fresh translation cannot be fetched in time, SleekPixel falls back to the source language title for that slot rather than blocking the card render. The next request after the rate limit clears regenerates the card with the proper translation.

Yes. The template setting lets you opt locales in or out per template. Skipping the source language is common when the source already has a hand-tuned OG image from another SleekPixel template, leaving the Weglot template responsible only for the locales that Weglot itself adds dynamically over its API.

Yes. Weglot supports both example.com/de and de.example.com style routing. SleekPixel reads the active locale through the Weglot helper regardless of routing mode, so the rendered card matches the locale of the request whether it arrived through a subdirectory or a fully separate subdomain at the DNS layer.

Yes. Edits made through Weglot's visual editor in the dashboard trigger the weglot_translations_updated webhook on save, which SleekPixel listens for. The plugin walks every cached PNG matching the affected locale and post pair, deleting them. Next request regenerates the card with the updated copy from translation memory.

Yes. Add a sleekpixel_exclude_locales custom field on the page with a comma separated list of locale codes to skip. Useful for legal pages where a translated card might be inappropriate or for pages still under review where you want to ship the source language card across all locales until translation is finalised.

Weglot's SEO module rewrites meta tags through its own filter chain, including the og:image tag where applicable. SleekPixel registers its og:image filter at a priority that runs after Weglot's rewrites, so the per-locale PNG URL is the final value emitted, which is what crawlers actually pick up at the wire level.

Yes. Weglot's media translation feature swaps images per locale in the page body, but SleekPixel's role is the share preview meta tag specifically. The template can also consume a media translation URL as the background or hero image source for a locale variant, giving fully localised art direction on each per-locale card.