Website Translation Isn't Enough: Don't Forget Your PDFs

Intro

The product page is in German. The navigation works, and the contact form routes straight to your local sales team. Then a visitor downloads your buyer’s guide and gets the English version.

That handoff is easy to miss, and it’s where a lot of international deals quietly stall. PDFs, slide decks, and price lists often hold the details buyers actually came for: specs, delivery terms, or a comparison chart they can forward to their manager.

This guide covers how to:

• Pick the first files worth translating
• Check local search results before rewriting anything
• Keep terminology consistent across your site and files
• Test translation tools on the files that actually matter
• Review the output the way a buyer would
• Publish translated PDFs so Google can match the language versions
• Track whether any of it is paying off

Why translated downloads matter

Language preference doesn’t switch off when someone clicks “Download.” In a 2020 CSA Research survey of 8,709 consumers across 29 countries, 76% said they prefer buying products with information in their native language, and 40% said they never buy from websites in other languages.

Now think about who reads your files. The person who visited your German product page might be comfortable with English. The finance lead they forward your PDF to might not be. And that second reader has no salesperson beside them to explain anything.

Doc2Lang’s usage data offers a snapshot of this demand. Excel files made up 27.6% of the 1,225 translation jobs created between October 4 and 12, 2026. That’s more than any other file type. MP4 video came second at 17.9%, and PDF third at 14.4%. This short snapshot shows demand for translating working files alongside published materials.

Choose a file your sales team already uses

Ask your sales team to open the exact files they sent to prospects last week. You’ll get a short, honest starting list. You’ll also catch a common problem early: the PDF in your website’s download section often isn’t the version anyone actually sends.

For a first project, pick a document that:

• Answers a question prospects ask again and again
• Has an internal expert available to review it
• Won’t change in the next few months

A buyer’s guide, product comparison, or short onboarding deck works well. Skip the price list if prices are about to change.

Check your search data too. In Google Search Console’s Performance report, filter for URLs containing “.pdf,” then open the Countries tab. If an English guide already gets impressions in Germany or Brazil, people there are looking for it. The queries that trigger those impressions show you what readers want from the document before you change a word.

Keep the project record simple: source file, target language, reviewer, where the finished file will live, and a date to review it again. That’s enough structure for a first project.

Context matters, too. A public guide needs a visible download link and a landing page that introduces it. A deck emailed after a demo has to make sense to a colleague who missed the call.

Check how buyers search in the target market

Translating your English keyword gives you a guess, not a keyword. People in Spain and Mexico can use completely different words for the same product, and a literal translation might match neither.

Run a few local-language candidates through Keyword Finder with the target country selected. Then open the actual results in SERP Checker and look at what ranks. Are searchers getting definitions, how-to guides, comparisons, or product listings?

A keyword can have decent volume and still be a bad fit for a downloadable guide. If the top results are all beginner explainers, your detailed comparison PDF might need a simple landing page in front of it first.

Once you’ve picked your terms, use them in the PDF’s title, opening paragraph, and section headings, plus the landing page that links to it. Name the file properly, too. A perfectly localized guide called “Document_v7_final.pdf” looks unfinished.

Keep terminology consistent

A one-page glossary saves a surprising amount of back-and-forth. For each important term, write down:

• The preferred local name
• What it means
• What must stay unchanged, such as product codes, trademarks, and units

Ask your local reviewer to settle ambiguous terms before the full file goes through translation, not after.

Then use the same glossary on your website and in your sales files. A buyer moving from your feature page to your comparison sheet shouldn’t wonder whether two different labels describe two different products.

Test the tool with your real files

Most document translators list the same file types. That list won’t tell you what happens to your formulas, your timecodes, or your crowded slides.

A Doc2Lang user reported that other AI services they’d tried for subtitles would skip lines or shift timecodes on their own. They didn’t run into either problem with Doc2Lang, but they did notice a few lines came back blank. That’s the kind of detail you only find by running a real file through a tool, and it cuts both ways.

So test with the file that actually matters: the workbook with formula-driven tables, the deck with crowded slides, the PDF with scanned pages. A clean sheet of plain text tells you almost nothing.

Tools that translate the file directly, such as Doc2Lang, save you from rebuilding layouts by hand. You upload the file, check a free preview and the price, and pay per file only if the output works for you. For teams localizing a few assets at a time, that’s a low-risk way to see how a tool handles your real files.

Two habits help here:

• Test with a sanitized copy if the file contains client names or unpublished pricing.
• Work from the editable source. Use the PPTX, DOCX, or XLSX rather than an exported PDF, and keep an untouched original. Export to the final format only after review.

Focus on what usually breaks:

• Excel: Compare formulas and calculated values with the original. Check chart labels and make sure product IDs didn’t change.
• PowerPoint: Open the deck in presentation mode. Read the busiest slides, check chart legends, and don’t forget the speaker notes.
• PDF: Check tables, reading order, and fine print. On scanned pages, double-check OCR output around numbers and part codes.
• CSV: Check encoding, delimiters, and column alignment. CSVs don’t store charts, formatting, or multiple sheets, so don’t expect them back.

Don’t trust averages here. The Doc2Lang team rechecked two spreadsheet translation previews. In an English-to-French workbook with long explanatory notes, 18 translated text cells grew from 2,003 to 2,521 characters (spaces and punctuation included), about 26%. One merged note cell kept its original height, and the last word got cut off.

An English-to-German sheet with mostly short labels told a different story. It grew about 21% overall, but the median cell grew only 5%, and the team found no clipping in the checked range. A few long labels did most of the growing.

So start with fixed-height merged cells, narrow column headers, and long text boxes. That’s where the extra length usually shows up.

Then do a quick functional check. Recalculate the workbook. Click every hyperlink. Search the translated PDF for a product name you know is in there. Open the deck on the laptop your sales team uses for calls. A screenshot won’t catch any of these problems.

Review meaning as well as layout

Once the file works, ask a reviewer who knows the market to read it start to finish. Give them the source file and your glossary, and have them start with the title, the opening, and the next step you want readers to take.

Ask specific questions:

• Is the product limitation still clear?
• Does “included” still clearly mean every plan, or does it now read like premium only?
• Can the reader tell which model each spec belongs to?

Intact formulas don’t mean intact meaning. During an internal quality check of an English-to-Japanese payment schedule, the Doc2Lang team found a line item that used a single letter as a building label. The translation read that letter as a measurement, so the line now described different work. Every formula in the workbook was untouched.

The clue was elsewhere in the file, where other rows used the same letter to name a building. A reviewer who knows the project would catch that. A spot check of a few cells wouldn’t.

Do a separate pass just for prices, dates, and units. Get currency changes approved by whoever owns the price list, and make sure dates can’t be read two ways (03/04 means different things in the US and the UK). Log every fix so the next update starts from the corrected version.

Finally, click every call to action. If the guide sends readers to the wrong language site or a dead campaign page, a better translation won’t fix that.

Publish PDFs for readers and search engines

Host each translated file on its matching localized page. Say what’s inside, show the language and the last update date, and make the download button easy to find. Use a stable URL so sales can share a link instead of an attachment that goes out of date.

For equivalent public PDFs in different languages, Google supports hreflang in HTTP headers. You can’t add a link tag inside a PDF, so the server sends the language information instead. An English and German pair looks like this:

Link: <https://example.com/en/buyers-guide.pdf>; rel="alternate"; hreflang="en", <https://example.com/de/kaufleitfaden.pdf>; rel="alternate"; hreflang="de"

Both files should return the complete set, including their own version. Send Google’s documentation to whoever manages your server or CDN, and check the live headers after deployment.

Run a Web Audit on the pages that host your downloads to catch broken links and indexing issues. Check the PDF URLs and headers separately, since a site audit won’t necessarily inspect every file’s response headers. And keep confidential price lists and private decks behind proper access controls.

Before you announce anything, walk the full route yourself: landing page, download button, the links inside the document, and the contact form. Then do it again on your phone.

Track results and keep files up to date

Save a baseline on launch day: the date, target country, target queries, and current impressions and clicks. Then track those queries by location in Rank Tracker. Note whether the ranking URL is the PDF itself or the page that introduces it.

Track download clicks and contact form submissions by language, too. Search Console can show visits that go straight to a PDF and skip your download page, so read both data sources together.

For sales files, just ask the people sending them:

• Are you actually using the translated version?
• Which slides do prospects ask about most?
• Is the distributor still working from the old spreadsheet?

Their answers tell you what to fix next. Set a review date with each file’s owner so that when a product or price changes, the local versions get updated at the same time.

Start with one file this week

Ask sales for one PDF they send every week. Pick one market, translate it, and have a local reviewer work through it. Send that version to the next relevant prospect and ask what still needs explaining.

That one file will teach you more about your localization gaps than any audit.