title: How to handle multiple translated URL routes in Next.js (domain routing)?
body: <p>I have a multi-language web app that I'm refactoring to use Next.js.</p>
  <p>The problem is that I have a few pages that are not under any specific folder, and they have different paths based on the page language.</p>
  <p>The internationalization is domain-based. There will be a domain for each country.</p>
  <p>For example:</p>
  <pre><code>/about-us          // ENGLISH
  /sobre-nosotros    // SPANISH
  
  /privacy           // ENGLISH
  /privacidad        // SPANISH
  
  /contact           // ENGLISH
  /contacto          // SPANISH
  
  /products          // ENGLISH
  /productos         // SPANISH
  </code></pre>
  <p>How would I even route something like that in Next.js ?</p>
  <p>The only way I've thought of so far is to not translate the paths for each country. I would use only the English slugs. So, the Privacy page for every country would be on <code>/privacy</code>. The About page would always be on <code>/about</code> and so on. It's doable, but I guess I'll lose some SEO points without the translated slugs. A doable but terrible idea would be to add a file to each translated route, I guess. Like: <code>about-us.js</code>, <code>sobre-nosotros.js</code>, etc.</p>
  <p>Is there another way? What would be the best practice in this case?</p>