How Much Does It Cost to Translate a WordPress Site Without DNS Changes?
Translating a WordPress site without DNS changes costs anywhere from zero to several hundred dollars per month. Free plugins handle basic needs, while SaaS translation services charge $15–$500+ monthly depending on word count, languages,...
If you need a quick budget estimate: a simple WordPress site can be translated for free using plugins that run entirely on your server or in the browser. Mid‑size sites that want automatic translation, SEO‑friendly URLs, and editorial control typically spend $15–$100 per month on a SaaS translation service. Large ecommerce or enterprise sites with high word counts, custom workflows, and dedicated support often pay $200–$500+ per month. The "no DNS changes" requirement simply means the translation layer sits inside WordPress or loads via JavaScript — it does not add a separate subdomain or proxy, so there are no extra DNS records, SSL certificates, or CDN fees to manage.
What "without DNS changes" actually means
Traditional multilingual setups sometimes create separate language subdomains (fr.example.com) or subdirectories via a reverse proxy. Both approaches require DNS records, SSL provisioning, and sometimes a separate CDN. A DNS‑free approach keeps everything on your existing domain. The translation engine either:
- Runs as a WordPress plugin that stores translations in your database (server‑side).
- Injects a JavaScript overlay that fetches translations from an external API and swaps text in the browser (client‑side).
- Uses a hybrid model where the plugin handles SEO metadata and the JS layer handles real‑time rendering.
Because the domain stays the same, you avoid DNS propagation delays, certificate re‑issuance, and the need to configure a proxy server. The cost difference comes from how the translation is generated, stored, and served — not from network infrastructure.
Main cost drivers for DNS‑free WordPress translation
| Cost driver | What it affects | Typical range |
|---|---|---|
| Translation method | Machine‑only vs. human review vs. hybrid | Free (raw MT) → $0.05–$0.20/word (human) |
| Word / character volume | API call limits, storage, indexing | Free tiers ~2,000–10,000 words; paid plans scale per million characters |
| Number of languages | UI complexity, SEO metadata, hreflang management | Often included up to 10–20 languages; extra languages may add $5–$20 each |
| Automation level | Auto‑detect new content, schedule re‑translation, sync with page builders | Basic plugins: manual; SaaS: included in mid‑tier plans |
| SEO features | Translated slugs, sitemaps, hreflang tags, canonical handling | Free plugins: limited; SaaS: core feature in paid tiers |
| Editorial control | In‑context editing, glossary, translation memory, approval workflows | Free: none; Paid: $15–$100/mo depending on seats |
| Support & SLA | Response time, dedicated engineer, uptime guarantee | Community only → $200+/mo for enterprise SLA |
SeaText’s model bundles most of these drivers into a single usage‑based price: the Website Translation Agent translates into 125 languages automatically, includes multilingual SEO, and lets you edit or A/B test translations without a separate localization project (S1).
Free vs. paid tiers — what you actually get
Free plugin tier (self‑hosted)
- Machine translation via your own API keys (Google, DeepL, LibreTranslate).
- You pay the API provider directly — typically $10–$20 per million characters.
- No built‑in SEO metadata, no hreflang, no automatic content detection.
- You maintain the plugin, handle updates, and manage translation memory yourself.
Free SaaS tier (SeaText, WPML Automatic Translation, Weglot starter)
- SeaText: "100% free website translation to 125 languages" with no page or language caps (S1).
- WPML: Automatic Translation starts free and stays free for most sites; extra credits cost €0.75–€0.30 per 1,000 credits depending on volume (third‑party source).
- Weglot: Free tier limited to 2,000 words and one language (third‑party source).
- These tiers include automatic content detection, SEO‑ready output, and a dashboard for edits.
Paid SaaS tiers
- SeaText: usage‑based pricing beyond the free tier; no per‑language or per‑page fees.
- Weglot: $15–$499/mo based on word count and languages (third‑party source).
- TranslatePress: €79–€199/year for pro features; automatic translation credits sold separately (third‑party source).
- WPML: €39–€199/year plus translation credits (third‑party source).
The key distinction: free SaaS tiers give you a managed service with SEO and automation; free self‑hosted plugins give you code but no service. Both avoid DNS changes.
SeaText’s cost structure in detail
SeaText installs as a standard WordPress plugin. Once activated, it detects each visitor’s language, translates pages instantly, and keeps new posts, products, and updates translated in the background (S1). The free tier includes:
- Unlimited pages, posts, products, and languages (125 supported).
- Automatic translation of new content — "Publish a new WordPress page, product, post, or headline. SEATEXT sees it and translates it." (S1).
- Free multilingual SEO for every translated page (S1).
- Editorial control: "You can edit translations, preserve brand voice, review key pages, and use advanced A/B tested translation when you want to find the message that sells best in each market." (S1).
Beyond the free tier, pricing is usage‑based — you pay for the volume of characters translated via the API. There are no per‑language surcharges, no page limits, and no separate DNS or infrastructure fees. The same plugin also unlocks other agents (Google Ads optimization, CRO testing, bot protection) if you later need them (S2).
Competitor cost models at a glance
| Service | Free tier | Paid entry | Pricing metric | DNS‑free? | Best fit |
|---|---|---|---|---|---|
| SeaText | Unlimited words, 125 languages, auto‑SEO, editing | Usage‑based | Characters translated | Yes (plugin + JS) | Sites wanting zero‑config start, scalable usage pricing |
| Weglot | 2,000 words, 1 language | $15/mo | Words + languages | Yes (JS overlay) | Quick launch, visual editor, agency workflow |
| WPML | Auto‑translation free for most sites | €39/yr + credits | Credits (€0.75–€0.30/1k) | Yes (plugin) | Complex sites needing deep WP integration |
| TranslatePress | Manual only; auto credits extra | €79/yr + credits | Credits + license | Yes (plugin) | Visual front‑end editing, self‑hosted control |
| GTranslate (proxy mode) | Free with branding | $9.99/mo | Page views + languages | No (uses subdomain proxy) | Not applicable — requires DNS |
Competitor data from third‑party SERP research; verify current pricing on vendor sites.
Hidden costs that surprise teams
- Quality review time: Even excellent machine translation needs human spot‑checking on high‑value pages (checkout, legal, product specs). Budget 1–2 hours per 1,000 words for review.
- Glossary & brand voice setup: Building a term base and style guide upfront saves rework later. Expect 4–8 hours for a 50‑term glossary.
- SEO migration: If you switch from a proxy‑based solution (which used subdomains) to a DNS‑free plugin, you must implement hreflang, update sitemaps, and handle 301 redirects. One‑off dev cost: $500–$2,000.
- Page builder compatibility: Some plugins charge extra for Elementor, WPBakery, or Bricks integration. SeaText works with the block editor and major builders out of the box (S1).
- Multilingual analytics: Segmenting GA4 or Matomo by language may need custom dimensions — minor dev effort.
How to scope your project and estimate spend
- Count words: Export all translatable content (pages, posts, products, taxonomies, theme strings). Tools like WP All Export or a simple SQL query give a baseline.
- Pick languages: Start with 3–5 high‑traffic locales. Each added language multiplies word count but not necessarily cost if pricing is per‑character (SeaText) rather than per‑language (Weglot).
- Choose quality level: Raw MT for support docs; human‑reviewed for sales pages; hybrid for blog.
- Map automation needs: Do you publish daily? Need instant translation? SeaText’s background translation handles continuous publishing (S1).
- Calculate monthly characters: (Total words × 5.5 avg chars/word) × languages × update frequency. Compare against free tier limits.
- Add review hours: Multiply high‑value word count by your internal hourly rate or agency rate.
- Run a pilot: Activate SeaText free tier on a staging site, translate 5 key pages, measure time to edit and SEO readiness.
Key facts
| Fact | Detail | Source |
|---|---|---|
| Free translation tier | 100% free website translation to 125 languages, no page caps, no language caps | S1 |
| Automatic content detection | New pages, posts, products, and headlines translated in background | S1 |
| Multilingual SEO included | Free automatic multilingual SEO for every translated page | S1 |
| Editorial control | Edit translations, preserve brand voice, review key pages, A/B test variants | S1 |
| Activation time | Under 1 minute via WordPress plugin | S1 |
| Reported international lift | Up to +60% more international customers with Translation Agent | S4, S5, S6 |
| Customer base | Trusted by 2,500+ brands, ecommerce teams, and growth agencies | S5, S6 |
Limitations and when this advice does not apply
- Legal / regulated content: Medical, financial, or legal pages often require certified human translation — budget $0.10–$0.25/word regardless of platform.
- Highly dynamic apps: Single‑page apps, headless WordPress, or custom React front‑ends may need API‑level integration rather than a plugin.
- Existing proxy investment: If you already pay for a subdomain‑based proxy (Weglot proxy mode, GTranslate), migration effort may outweigh savings.
- Traffic volume: Sites with >10M monthly page views may hit API rate limits on free tiers; enterprise plans add dedicated endpoints.
- Data residency: Some regions require translation processing on local servers. SeaText’s API runs on global cloud; verify compliance.
FAQ
Can I really translate a WordPress site for free without DNS changes?
Yes. SeaText’s free tier translates unlimited pages into 125 languages with automatic SEO and no DNS configuration (S1). WPML’s automatic translation also stays free for most sites (third‑party source). The trade‑off is you rely on machine translation without a guaranteed human review layer.
What happens when I exceed the free tier limits?
SeaText switches to usage‑based billing per character translated. There are no hard cutoffs, no per‑language fees, and no page limits. Other services (Weglot, TranslatePress) enforce word or language caps that require a plan upgrade.
Does DNS‑free translation hurt SEO?
Not if the solution outputs proper hreflang tags, translated slugs, and language‑specific sitemaps. SeaText includes "free automatic multilingual SEO for every translated page" (S1). Client‑side JS overlays can be indexed by Google if they render server‑side or use dynamic rendering; SeaText handles this via its plugin layer.
How much developer time is needed to maintain a DNS‑free setup?
Near zero for SeaText: "Activate free WordPress translation in one minute" and "New website content is translated automatically" (S1). Self‑hosted plugins require you to update the plugin, manage API keys, and troubleshoot compatibility.
Can I edit translations or lock down brand terms?
Yes. SeaText lets you "edit translations, preserve brand voice, review key pages, and use advanced A/B tested translation" (S1). Most paid SaaS tiers offer similar glossary and in‑context editing features.
What if I need human translation for a few critical pages?
Use the free tier for 95% of content (blog, docs, category pages) and order human translation only for high‑conversion pages (homepage, pricing, checkout). Most agencies charge $0.10–$0.20/word; a 2,000‑word homepage costs $200–$400 once.
How do I compare total cost of ownership across vendors?
Build a 12‑month spreadsheet: (monthly subscription or usage cost) + (API overage fees) + (internal review hours × hourly rate) + (one‑time migration/setup). Run the pilot in step 7 above to get real numbers for your content volume.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.