| 开发者 | langrelay |
|---|---|
| 更新时间 | 2026年5月29日 14:19 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
yoursite.com/about-us becomes yoursite.com/nl/over-ons.hreflang and x-default tags on every pagelangrelay folder to /wp-content/plugins/.It translates your WordPress site into other languages automatically. AI handles the translations, URLs and slugs are translated, hreflang tags are injected, and a language switcher is added. You don't manage translated posts manually.
Two big things. First, you only pay for words that actually get translated. If the same sentence appears across your whole site, you pay for it once, not once per page. Second, LangRelay handles GEO (Generative Engine Optimization) with translated llms.txt and AI-readable pages, so your site gets cited by ChatGPT and Perplexity in every language.
100+ languages, including Spanish, French, German, Dutch, Italian, Portuguese, Polish, Swedish, Norwegian, Danish, Finnish, Czech, Greek, Turkish, Arabic, Hebrew, Hindi, Japanese, Korean, Chinese (Simplified and Traditional), Vietnamese, Thai, Indonesian, and more.
Yes. LangRelay is a cloud service. You can sign up for free at langrelay.com. No credit card required.
No. The first visit to a translated page takes a moment while the translation is generated. After that, everything is served from a WordPress transient cache. Repeat visitors see translated pages instantly.
Yes, automatically. LangRelay injects hreflang tags for every translated language plus an x-default tag in the page head. Canonical tags are language-aware. No manual SEO work required.
Yes. Product pages, shop pages, cart, and checkout are all translated automatically. Yoast and Rank Math SEO metadata is translated too.
Yes. Meta titles, meta descriptions, Open Graph tags, and Twitter Card tags written in Yoast or Rank Math are translated alongside the page content.
Your site serves the original untranslated page. Nothing breaks.
It's a file AI models like ChatGPT and Perplexity read to understand your site's content. LangRelay generates one for every page in every language so AI search engines can cite your site internationally. No configuration needed.
Yes. The free plan gives you 1 project, 1 language, and 10,000 credits (words) per month. That covers roughly 20 pages, enough to test on a small site before committing.
Yes. Sites on the free plan display a small "Powered by LangRelay" badge next to the language switcher. This is controlled by the LangRelay service based on your plan. Upgrading to a paid plan removes the badge.
GEO stands for Generative Engine Optimization. It's the practice of making your site visible and citable by AI-powered search engines like ChatGPT, Perplexity, and Google AI Overviews. LangRelay handles this automatically with translated AI-readable pages and llms.txt files.
/de/checkout) now correctly associate with the source-language page, so coverage tracking in the dashboard is accurate.X-LangRelay-Crawler request header is present, so the LangRelay crawler always receives the source-language page instead of being redirected to a language-prefixed URL. Also adds langrelay to the bot user-agent bypass list as a fallback./wp-admin, /wp-login.php, or /wp-json paths. With force-fallback enabled, logged-out users were being redirected from /wp-admin to /<lang>/404/.auto_redirect, auto_redirect_fallback, auto_redirect_force_fallback) synced from the LangRelay dashboard now persist correctly. They were being stripped by the settings sanitizer, so auto-redirect never engaged on synced sites even when enabled in the dashboard.X-LangRelay-Handle and X-LangRelay-AutoRedirect response headers, the auto-redirect state in /wp-json/langrelay/v1/debug/status, and a log entry on every "Sync project" attempt — so support can diagnose redirect issues without touching the server.auto_redirect, auto_redirect_fallback, and auto_redirect_force_fallback from the LangRelay API so dashboard changes propagate to the plugin.LangRelay_Auto_Redirect::maybe_redirect to use a pure resolve() method for testability.display: contents) inadvertently broke the default row layout of the customizable select; explicitly making the select an inline-flex row restores it.appearance: base-select, the browser renders a <button> inside the <select> that themes like Elementor were re-styling (red background, uppercase text). The 1.9.3 fix scoped the <select> styles but missed this inner button. Now explicitly resets it with all: unset; display: contents at higher specificity..langrelay-switcher for higher specificity. Also explicitly resets text-transform, letter-spacing, font-weight, and text-align so themes that style bare button elements no longer leak through.?langrelay_debug=1 query param or data-debug="true" on the script tag for troubleshooting.<a> and <img> tags in JavaScript) are no longer corrupted by the URL rewriter. DOMDocument now skips script and style blocks during URL rewriting.