Tutorial

Agency Guide: Scaling Multilingual Sites with SiteLocaleAI

Published April 9, 2026

Agency Guide: Scaling Multilingual Sites with SiteLocaleAI

Agency Guide: Scaling Multilingual Sites with SiteLocaleAI

Running an agency that services 20+ client websites means juggling different tech stacks, languages, and SEO requirements. SiteLocaleAI’s self‑hosted JavaScript library, volume‑licensing options, and SEO‑focused CLI make it possible to standardise localisation while keeping costs predictable.

1. Why Choose SiteLocaleAI for an Agency?

Feature Agency Benefit
Drop‑in JS library Works with React, Vue, WordPress, Shopify, or any static site – no rewrite needed.
Self‑hosted API keys Each client can use their own LLM provider (Claude, GPT‑4o‑mini, etc.) – you never share keys across projects.
Psychological price rounding Prices appear natural in every currency, boosting conversion rates.
CLI pre‑rendering Generates fully translated HTML for crawlers, improving international SEO.
Volume licensing One‑time bulk purchase (e.g., $249 Enterprise) covers all client sites, simplifying invoicing.

These capabilities line up perfectly with an agency’s need for scalability, security, and predictable pricing.

2. Setting Up a Central Repository

Create a Git‑submodule or npm workspace that contains the SiteLocaleAI library and shared configuration. This way every client project can pull the same version.

# In your agency monorepo
mkdir site‑locale‑shared && cd site‑locale‑shared
npm init -y
npm i @sitelocaleai/locale-js

Add a locale.config.js that reads the client‑specific API key from an environment variable:

// locale.config.js
module.exports = {
  llmProvider: process.env.LLM_PROVIDER || "openai",
  apiKey: process.env.LLM_API_KEY,
  targetLanguages: ["en", "es", "fr", "de", "ja"],
  priceRounding: {
    USD: 0.99,
    EUR: 0.95,
    GBP: 0.95,
    JPY: 0.00
  }
};

Each client’s deployment pipeline will set LLM_API_KEY (and optionally LLM_PROVIDER) in its CI environment, keeping keys isolated.

3. Adding the Library to a Client Site

Because the library is framework‑agnostic, you only need to insert a single script tag. Here’s a generic HTML snippet you can drop into any template:

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8" />
  <title>My Client Site</title>
  <script type="module" src="https://cdn.sitelocaleai.com/locale-js.min.js"></script>
  <script type="module">
    import { initLocale } from "https://cdn.sitelocaleai.com/locale-js.min.js";
    import config from "./locale.config.js";
    initLocale(config);
  </script>
</head>
<body>
  <!-- Your existing markup -->
</body>
</html>

For React or Vue projects you can wrap the init call in a useEffect or mounted hook, but the core logic stays identical.

4. Bulk Translating Content with the CLI

SiteLocaleAI ships a CLI that pre‑renders translated pages. This is crucial for international SEO because search bots see the final HTML.

# Install CLI globally (once per agency workstation)
npm i -g @sitelocaleai/cli

# Run against a client’s static build folder
sitelocale-cli render \
  --src ./client-site/build \
  --out ./client-site/build-localized \
  --config ./locale.config.js \
  --lang es,fr,de,ja

The CLI reads the same locale.config.js, calls the LLM API for each translatable string, and writes language‑specific folders (/es/, /fr/, …). You can automate this step in a CI pipeline:

# .github/workflows/locale.yml
name: Localize & Deploy
on: [push]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Install dependencies
        run: npm ci
      - name: Build site
        run: npm run build
      - name: Localize
        env:
          LLM_API_KEY: ${{ secrets.LLM_API_KEY }}
        run: |
          npm i -g @sitelocaleai/cli
          sitelocale-cli render --src ./build --out ./build-localized --config ./locale.config.js --lang es,fr,de,ja
      - name: Deploy
        uses: some/deploy-action@v2
        with:
          folder: ./build-localized

The rendered folders can be served directly from a CDN, ensuring fast, localized experiences for end‑users.

5. WordPress Integration (No Node Required)

Many of your clients may be on WordPress. SiteLocaleAI provides a drop‑in plugin that eliminates the need for a Node environment.

  1. Download the plugin from the SiteLocaleAI docs.
  2. Upload it via the WordPress admin → Plugins → Add New → Upload Plugin.
  3. In the plugin settings, paste the LLM API key and select the target languages.
  4. Enable “Price Rounding” and set the rounding rules per currency.

The plugin automatically injects the JS library and runs the CLI‑style pre‑rendering on every publish, so editors see the translated preview instantly.

6. Managing Volume Licensing

SiteLocaleAI’s Enterprise tier ($249) includes up to 100,000 translated tokens per month and unlimited sites. For an agency with 20+ clients, you’ll likely stay well within that quota.

  • Central Billing – One invoice for the entire agency.
  • Per‑Client Usage Dashboard – The admin console lets you assign a “client bucket” to each site, tracking token consumption in real‑time.
  • Scalable Upgrade – If you outgrow the Enterprise quota, you can move to a custom plan without code changes.

To activate the license, add the following to locale.config.js:

module.exports = {
  // existing keys …
  licenseKey: "YOUR_ENTERPRISE_LICENSE_KEY",
};

The library validates the key on each request, ensuring you stay within the agreed limits.

7. SEO Best Practices with Pre‑Rendered Pages

  1. Sitemap Generation – After the CLI run, generate a multilingual sitemap: bash sitelocale-cli sitemap --out ./build-localized/sitemap.xml --langs es,fr,de,ja
  2. Hreflang Tags – The CLI automatically injects <link rel="alternate" hreflang="…"> tags.
  3. Canonical URLs – Keep the original language as the canonical version to avoid duplicate‑content penalties.

These steps give you the same SEO signal quality you’d get from a fully server‑side rendered solution, but with the flexibility of a client‑side library.

8. Wrap‑Up Checklist

  • [ ] Create a shared locale.config.js and store API keys securely per client.
  • [ ] Add the drop‑in script tag (or WordPress plugin) to every site.
  • [ ] Run the CLI in CI to generate SEO‑friendly, translated HTML.
  • [ ] Enable price rounding rules for each currency.
  • [ ] Activate your Enterprise license key in the config.
  • [ ] Generate multilingual sitemaps and verify hreflang tags.

By following this workflow, your agency can onboard new clients in minutes, keep translation costs transparent, and dominate international search rankings.

Ready to streamline your multilingual projects?

Try SiteLocaleAI for free and see how easy it is to scale localisation across all your client sites.

Back to blog