Proxylang: AI Translation & Multilingual SEO compatibility with REEID Translate

Plugin capabilities

• Generates per-language URL paths (e.g., `/{language}/…`) intended to be indexable by search engines, with hreflang annotations and localized meta/headers.
• Provides per-language SEO artifacts including XML sitemaps and robots.txt, and includes hreflang/locale-related signals (e.g., `og:locale`, `content-language` headers) for translated pages.
• Serves server-rendered translated HTML to search-engine bots for `/{lang}/*` requests (indexable/no-JavaScript requirement for bots), while human visitors receive client-side in-browser translation.
• Localizes WooCommerce Product JSON-LD for Google Shopping rich results (and claims translation of WooCommerce product-related fields), with explicit exclusion of cart/checkout pages from caching to preserve session state.
• Implements caching compatibility by varying cached entries by language and visitor type (bot vs human) via shims for common page-cache plugins (W3 Total Cache, WP Super Cache, LiteSpeed Cache).
• Uses translation cache invalidation via signed HMAC webhooks (no manual purge described), and caches translations both at the edge network and within the WordPress install (object cache/transients).
• Integrates with external endpoints for SEO rendering and sitemap delivery: bot rendering via `proxy.proxylang.dev/v1/render` and sitemap generation via `proxy.proxylang.dev/v1/sitemap`, plus front-end translation script delivery via `proxy.proxylang.dev/script.js` and `v1/script-bundle`.
• Requires configuration of two keys (Production and Local/Development) in `Settings → Proxylang`, and auto-selects the key based on the current site hostname (production vs local staging).