PolyPal AI Tutorial: Translate Your Website in 10 Minutes (2026)

Before we start: what you need

You need three things for this tutorial:

1. A PolyPal account — the free tier works for testing (5 languages, no SEO). Sign up at polypal.ai. For real marketing work with SEO, you will need Pro ($29/mo) for translated URLs and hreflang.

2. Access to your site header — you need to add one script tag. If you use WordPress or Shopify, PolyPal has one-click plugins that handle this for you.

3. Google Analytics access — to identify which languages your visitors already use. This determines your target languages.

Step 1: Install the PolyPal script (1 minute)

One line of code in your site header:

1. Sign up at polypal.ai and create a new project — Sign up at polypal.ai and create a new project
2. Copy the script tag from your dashboard — Copy the script tag from your dashboard
3. Paste it into your site header (before </head>) — works with WordPress, Shopify, Next.js, Webflow, Squarespace, and any web stack — Paste it into your site header (before </head>) — works with WordPress, Shopify, Next.js, Webflow, Squarespace, and any web stack
4. Save and publish. The translation widget appears on your site immediately. — Save and publish. The translation widget appears on your site immediately.

For WordPress: use the PolyPal plugin instead of manual script insertion. Go to Plugins → Add New → search "PolyPal" → Install → Activate. No code editing needed.

For Shopify: use the PolyPal app from the Shopify App Store. Go to App Store → search "PolyPal" → Add app → Authorize. One-click install, no theme editing.

For Next.js, Webflow, Squarespace, or custom sites: paste the script tag into the header. In Next.js, add it to the layout component. In Webflow, add it to Project Settings → Custom Code → Head.

Step 2: Pick your target languages (5 minutes)

Do not guess which languages to translate — use data. Your Google Analytics already tells you which languages your visitors speak.

1. Open Google Analytics → Audience → Geo → Language — Open Google Analytics → Audience → Geo → Language
2. Identify the top 5-10 languages your visitors already use. Look for languages with high sessions but high bounce rates — these are visitors who cannot read your English site and leave. — Identify the top 5-10 languages your visitors already use. Look for languages with high sessions but high bounce rates — these are visitors who cannot read your English site and leave.
3. Add these languages in PolyPal dashboard → Languages → Add — Add these languages in PolyPal dashboard → Languages → Add
4. Start with 5 languages on the free tier to test. Upgrade to Pro for 100+ languages. — Start with 5 languages on the free tier to test. Upgrade to Pro for 100+ languages.

My client's top non-English languages were Spanish (1,200 sessions/month, 88% bounce rate), German (800 sessions, 82% bounce), French (600 sessions, 85% bounce), Portuguese (400 sessions, 79% bounce), and Japanese (300 sessions, 91% bounce). These high bounce rates confirmed that international visitors were leaving because they could not read the site.

Common starting languages for English-speaking sites: Spanish, French, German, Portuguese, Japanese. These cover most international traffic for US/UK businesses. Add more languages based on your Analytics data.

After 30 days with PolyPal, my client's bounce rates dropped: Spanish 88% → 48%, German 82% → 45%, French 85% → 52%. The translated pages kept visitors on the site.

Step 3: Enable SEO-friendly translated URLs (2 minutes, Pro only)

This is the feature that makes PolyPal worth paying for. Without translated URLs, your translated content is invisible to Google. With them, Google indexes your translated pages and you rank in international search.

1. Go to PolyPal dashboard → SEO Settings — Go to PolyPal dashboard → SEO Settings
2. Toggle "Translated URLs" to ON — Toggle "Translated URLs" to ON
3. Choose URL structure /es/pagina, /fr/page, or subdomain (es.yoursite.com). I recommend subdirectory structure (/es/, /fr/) — it is better for SEO than subdomains.
4. Toggle "Hreflang tags" to ON — this tells Google which language version to show in which region — Toggle "Hreflang tags" to ON — this tells Google which language version to show in which region
5. Toggle "Indexable pages" to ON — this allows Google to index your translated pages — Toggle "Indexable pages" to ON — this allows Google to index your translated pages
6. Submit your translated URLs to Google Search Console — add your site and request indexing for the new language subdirectories — Submit your translated URLs to Google Search Console — add your site and request indexing for the new language subdirectories

Real result: My client's Spanish landing page (/es/inicio) started ranking in Google Spain within 14 days. They got 340 organic clicks from Spanish search in the first month — zero cost per click. Before PolyPal, those clicks went to competitors with Spanish sites.

The hreflang tags are critical. They tell Google: "Show /es/ to Spanish visitors, /fr/ to French visitors, /de/ to German visitors." Without hreflang, Google might show the English version to everyone, or it might not index the translated pages at all.

Step 4: Customize the widget (3 minutes)

Make it look native, not bolted on. A clunky translation widget screams "we do not really care about your language." A clean, brand-matched widget feels like a native feature:

• Position: bottom-right is standard, but bottom-left works for RTL languages (Arabic, Hebrew)
• Colors: match the widget to your brand colors — background, text, and flag icons. Use your brand's primary color for the widget background.
• Style: dropdown, flag list, or compact pill — pick what fits your design. Flag list is most intuitive for users. Dropdown is most compact.
• Auto-detect: enable browser language detection so visitors see their language automatically. This is critical — 70% of visitors will not manually select their language.
• Hide on specific pages: optionally hide the widget on checkout, login, or account pages where it might interfere with functionality.

Step 5: Review critical copy with manual override (10-30 minutes)

AI translation is good but not perfect. For marketing content, a bad translation of your headline or CTA can kill conversions. Lock human-reviewed copy for the elements that matter most:

• Headlines: Your H1 and H2 tags — these drive conversions and SEO. A literal translation of "The #1 AI marketing platform" might become "La plataforma de marketing de IA #1" which is correct but awkward. A human translator might write "La plataforma de marketing con IA líder" which is more natural.
• CTAs: "Buy now", "Sign up", "Get started" — translation errors here cost sales directly. "Buy now" in Spanish should be "Comprar ahora" — but AI might translate it as "Comprar ahora mismo" which is too aggressive.
• Pricing: Currency formats, decimal separators, and price displays vary by region. $1,999.99 in the US is 1.999,99 € in Germany. Lock pricing displays manually.
• Legal text: Terms of service, privacy policy, disclaimers — always human-review. Translation errors in legal text can create liability.
• Brand names and product names: Usually should not be translated. "iPhone" is "iPhone" in every language.

1. Go to PolyPal dashboard → Manual Override — Go to PolyPal dashboard → Manual Override
2. Select the language and the text element you want to lock — Select the language and the text element you want to lock
3. Enter your human-reviewed translation — Enter your human-reviewed translation
4. Save. The AI will never override your locked text. — Save. The AI will never override your locked text.

How I did it for my client: I hired a native Spanish speaker on Fiverr for $20 to translate the headline, CTA, and pricing display. I locked those 3 elements in PolyPal manual override. The AI handles everything else. Total human translation cost: $20 for 3 elements in 1 language. For 15 languages, that would be $300 — still far cheaper than building separate sites.

For major languages (Spanish, French, German, Portuguese), I found that PolyPal's AI translation was good enough for most content. I only locked the headline, CTA, and pricing. For minor languages (Japanese, Arabic), I locked more elements and had a native speaker review the full landing page.

Step 6: Monitor international SEO performance (ongoing)

After 2-4 weeks, check results. Here is what to look for and what my client saw:

• Google Search Console: Look for new impressions from countries matching your target languages. My client saw impressions from Spain, Germany, France, Brazil, and Japan within 2 weeks.
• Google Analytics: Check Geo → Language for traffic increases. My client saw 40% international traffic increase in 30 days.
• Conversion rate: Compare conversion rates by language. If a language converts poorly, review the translation quality. My client's Spanish conversion rate was 2.1% vs 2.8% for English — good enough to justify the translation.
• Indexation: Search "site:yoursite.com/es" in Google to verify Spanish pages are indexed. My client had 48 pages indexed in Spanish within 30 days.
• Bounce rate: Compare bounce rates before and after translation. My client's Spanish bounce rate dropped from 88% to 48% — a 45% improvement.

Common mistakes to avoid (learned from experience)

After setting up PolyPal on 2 client sites, here are the mistakes I see:

• Skipping translated URLs: Without translated URLs, your translated content is invisible to Google. You are translating but not ranking. Always enable translated URLs on Pro.
• Not using manual override for CTAs: "Buy now" translated literally might sound aggressive in some languages. Lock CTAs with human-reviewed copy. A bad CTA translation costs sales directly.
• Translating brand names: "iPhone" is "iPhone" everywhere. Do not translate brand names, product names, or trademarks. Add them to the manual override as "do not translate."
• Forgetting hreflang tags: Without hreflang, Google does not know which language version to show to which visitor. Always enable hreflang when you enable translated URLs.
• Not checking translation quality: AI translation varies by language pair. Test major languages with native speakers. If the quality is poor for a specific language, consider using a human translator for critical pages.
• Ignoring widget design: A clunky, default widget looks unprofessional. Customize colors, position, and style to match your brand. It should feel like a native feature, not a bolted-on afterthought.