Alternate URL Generator

A quick orientation: this page explains how the alternate URL generator transforms a single-locale URL list into a complete multilingual URL matrix, walks through usage steps, covers the syntax pitfalls that break most bulk-generation workflows, and explains how this tool differs from single-page tag builders.

What is an alternate URL generator?

An alternate URL generator takes a list of page URLs from one locale and expands each entry into a full matrix of localized alternate URLs across every target language and region. Instead of manually constructing hreflang URLs one page at a time, you provide your base URL list — for example, all English pages on your site — and specify the locale codes and URL patterns for each target language. The generator then produces the complete set of alternate URLs for every page in every locale.

This is different from a tag builder that outputs finished <link> elements. The alternate URL generator focuses on the URL-mapping step that comes before tag generation. It answers the question: "Given page /en/pricing, what are the corresponding URLs in es, de, fr, pt, and it?" Once you have that matrix, you can feed it into any hreflang implementation method — HTML <link> tags, HTTP headers, or XML sitemaps.

The tool applies configurable URL pattern rules. If your English pages live at example.com/en/slug and your Spanish pages at example.com/es/slug, the generator applies the pattern substitution across every URL in your input list. It handles subdirectory patterns (/en/ → /es/), subdomain patterns (en.example.com → es.example.com), and ccTLD patterns (example.com → example.es). All processing runs in the browser — your URL list never leaves your machine.

How to use this alternate URL generator

Follow these steps to build a multilingual URL matrix:

1. Paste your base URL list. Enter or paste the full list of absolute HTTPS URLs from your primary locale — one URL per line. These are the pages you want to generate alternate URLs for. The tool validates that every URL is absolute and uses HTTPS.

2. Define your locale targets. For each target language or region, specify the ISO 639-1 language code (optionally with an ISO 3166-1 region code) and the URL transformation pattern. Common patterns include subdirectory replacement (/en/ → /de/), subdomain swap (en. → de.), and domain-level mapping (example.com → example.de).

3. Configure x-default handling. Choose which locale serves as the x-default fallback, or point x-default to a dedicated locale-selector page. The generator includes x-default in every URL set it produces.

4. Generate and review the matrix. The output is a table showing every page across every locale. Each cell contains the generated URL. Cells are color-coded: green for confirmed patterns, yellow for URLs where the transformation produced an unusual result that may need manual review.

5. Export the matrix. Download the URL matrix as CSV or JSON. The CSV format integrates directly with spreadsheet workflows. The JSON format matches the input schema expected by the hreflang tag generator, so you can chain the two tools together for a complete generation pipeline.

Common errors and how to fix them

These are the five mistakes that most often break bulk URL generation workflows.

1. Inconsistent path structures across locales. If your English site uses /en/blog/my-post but your German site uses /de/blog/mein-beitrag (translated slugs), a simple pattern substitution produces incorrect URLs. The generator flags pages where the slug portion changes between locales, prompting you to supply manual mappings for those pages.

2. Mixing URL pattern types. Some sites use subdirectories for some languages and subdomains for others. If you configure a single pattern rule, it won't cover mixed setups. Define one rule per locale to handle heterogeneous URL structures correctly.

3. Forgetting trailing slash consistency. If your base URLs end with a trailing slash but the target locale URLs do not (or vice versa), search engines treat them as different URLs. The generator normalizes trailing slashes across all generated URLs based on your chosen preference.

4. Omitting the source locale. The URL matrix must include the base locale alongside all target locales — this is the self-reference requirement. The generator always includes your source locale in the output so every page set is complete.

5. Using HTTP URLs as input. Submitting http:// URLs produces a matrix where every generated URL also uses HTTP. Search engines strongly prefer HTTPS. The generator rejects HTTP input and prompts you to use HTTPS URLs instead.

How this tool is different

Four things set this alternate URL generator apart from single-page builders and manual spreadsheet workflows:

• Batch-first design. While tools like the hreflang tag generator handle one page group at a time, this generator operates on your entire URL list at once. You get a complete matrix in one pass instead of repeating a single-page workflow hundreds of times.
• Pattern-based transformations. You define rules once and apply them across every URL. This eliminates repetitive manual URL construction and the typos that come with it.
• Export formats that chain into tag generators. The JSON export is specifically designed to feed into hreflang tag generation tools, creating a two-step pipeline: generate the URL matrix, then generate the tags.
• Anomaly detection. The tool flags URLs where the pattern transformation produces unexpected results — such as double locale prefixes or missing path segments — so you catch problems before deploying tags.

Everything runs in your browser. There is no signup, no server processing your URLs, and no usage cap. For background on hreflang fundamentals and why correct URL mapping matters, see the what is hreflang guide.