How To Translate A Website To English | Get Clean English Pages

Translating a website can mean two different things. Sometimes you just need to read a page right now. Other times you need English URLs that load in English every time, with menus, buttons, and metadata translated too.

This article covers both. You’ll start with the fastest ways to translate any page in your browser. Then you’ll switch to a durable setup for sites you control, with steps that work for WordPress, Shopify, and custom builds.

What “Translating A Website” Means On Real Sites

Pick the outcome you want. The method follows from that choice.

• Read-only preview: you understand the page, but there’s no new English URL.
• English section visitors can share: each page has an English URL that stays English.
• Full bilingual build: navigation, forms, emails, and SEO fields exist in English.

Browser translation covers the first case. The other two require English content stored in your site, not generated on the fly in a visitor’s tab.

Translate A Site In Your Browser For Instant Reading

If you’re translating a site you don’t own, browser tools are the cleanest start. They translate what you see on screen, so you don’t need admin access.

Use Chrome’s Page Translation

Chrome can translate a page in a couple of clicks. If the prompt doesn’t show, open the browser menu and choose Translate. You can set Chrome to always translate pages in a given language, which helps when you’re scanning many pages on one domain.

The translated view is a reading layer. If you copy text, paste it into a plain-text editor first to spot odd line breaks.

For background on how the feature works under the hood, see the Chromium Translate design notes.

Use Microsoft Edge’s Translator

Edge offers a similar flow. When it detects a non-English page, it shows a translate prompt near the URL bar. If you don’t see it, open Settings and search “translate” to confirm the feature is enabled.

Edge is handy for a quick second opinion. Comparing Edge and Chrome output can reveal phrases that keep coming out wrong.

Microsoft’s Edge Translate feature page shows where the controls appear and what to click.

Know Where Browser Translation Breaks

Browser translation is fine for general meaning. It’s shaky for product specs, legal text, UI labels, and form messages. It can misread text injected after load, like cookie banners, chat widgets, and dynamic menus.

If you own the site and want an English section users can rely on, treat browser output as a draft and move to a stored translation workflow.

How To Translate A Website To English For Indexed Pages

When you control the site, the goal is predictable output: the same English text for every visitor, on every device, with English URLs you can link and track. That calls for a workflow that separates translation from publishing.

Step 1: Inventory What Needs Translation

A site is more than blog posts. List your content surfaces so you don’t ship a half-translated experience.

• Core pages: home, about, pricing, contact, policies
• Navigation labels and footer links
• Buttons, notices, and form field labels
• SEO fields: titles, meta descriptions, image alt text
• Emails and receipts tied to user actions

Step 2: Choose A Draft Source, Then Edit For Clarity

Machine translation can be a solid starting point for many tech sites, since terms like “driver,” “firmware,” and “latency” carry stable meaning across languages. The editing pass is where readability appears: consistent terminology, natural verbs, and fewer literal phrases.

The Google Translate interface works well for drafts, quick glossary checks, and comparing alternate phrasings.

Step 3: Decide Where English Lives

Pick one storage pattern and keep it consistent across your site.

• Separate URLs per language: /en/ for English, or an English subdomain like en.example.com.
• Separate domains: used when branding or legal needs differ.
• Single URL with a front-end overlay: fine for reading, weak for sharing and indexing.

Most publishers choose /en/ because it’s clear, easy to link, and keeps authority on one domain.

Step 4: Implement The Method That Fits Your Stack

Your platform decides the tooling. Aim for one source of truth for each English string.

WordPress: Pair Each Page With Its English Version

On WordPress, a multilingual plugin can connect each original page with its English version and translate theme strings. In plugin settings, pay attention to URL format (/en/), string translation coverage, and whether SEO fields can differ by language.

Shopify: Translate Products And Theme Text Together

On Shopify, you’ll translate product titles, descriptions, policy pages, and theme labels. A good setup keeps translated checkout-adjacent text aligned with your theme so shoppers don’t hit mixed-language screens.

Custom Builds: Extract Strings, Translate, Rebuild

On custom sites, keep translatable text in localization files instead of hard-coding it in templates. Your cycle becomes: extract strings, translate them, run a build, then deploy. This keeps UI labels consistent and makes changes easy to track in version control.

Common Translation Approaches And When They Fit

This table maps goals to methods. It’s written for sites that want English pages to feel like first-class pages, not a temporary overlay.

Translating Your Website To English Without Breaking SEO

If you want English pages indexed, crawlers need clean signals for language and page relationships. That means correct language attributes, predictable internal linking, and language annotations between page versions.

Set Language Tags In HTML

Each page should declare its language. In HTML, that’s the lang attribute on the html tag. For CMS builds, confirm the theme outputs the right lang for English URLs and the original language URLs. W3C’s language declaration page explains how lang tags help user agents interpret text.

Use Hreflang Between Page Versions

If you publish the same page in two languages, add hreflang annotations so search engines can pick the right version by language or region. Google’s page on localized versions and hreflang shows accepted patterns and common mistakes.

Keep URLs And Internal Links Predictable

Pick one rule for English URLs and stick to it. If you use /en/, link English pages to English pages in menus and footers. Mixed navigation is where readers bounce between languages.

For the language switcher, use clear labels like “English.” Flags map to countries, not languages.

Table-Driven Checklist For Launching English Pages

Run this checklist on your main English section before you share it publicly. It helps you catch the “almost done” issues that make a site feel patched together.

Maintenance So English Stays Current

Translation isn’t a one-time task. New posts ship, UI labels change, pricing updates, and old screenshots become stale. If you don’t plan for upkeep, the English section falls behind.

Create A Simple “Needs Translation” Flag

When a page changes, mark it so editors know English needs a refresh. In a CMS, this can be a status label. In a code repo, it can be a ticket tied to the string-extraction diff. The point is visibility: changes don’t hide.

Keep A Short Glossary For Tech Terms

Write a one-page glossary for recurring words: product names, feature names, and UI verbs. Include capitalization and whether a term stays in the original language. This prevents drift like “Sign in” turning into “Log in” across half the site.

Do Small Spot Checks

Once a month, open your top English landing pages and click the main navigation. Then test one form. Fixing small issues early keeps the English section readable and trusted.

Editing Moves That Make English Read Like English

When you edit translated text, stick to a few repeatable moves rather than rewriting everything.

• Use direct verbs: “Click Save” beats “Save is clicked.”
• Split long sentences: one idea per line reads better on mobile.
• Standardize UI verbs: pick “Sign in” or “Log in,” then use it everywhere.
• Check headings: headings should match the section content, not drift into slogans.

Final Pre-Publish Pass

Open the English home page in a private window. Click menus, a couple of category pages, and a post. Share one link to yourself and check the preview card text. Then view source and confirm lang and hreflang output. If all of that looks clean, you’re ready to publish.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback