A practical Next.js checklist for bilingual SEO
How to make English and Japanese pages discoverable, shareable and useful to both search engines and AI answer systems.
Supacode Editorial
Product and engineering
Quick answer
A reliable AI app workflow is a short feedback loop.
- Give every locale a stable, crawlable URL such as /blog/... and /ja/blog/....
- Render translated titles, descriptions, headings and structured data on the server.
- Connect translations with hreflang and keep canonical URLs self-referential.
- Write answer-first sections so search and AI systems can quote the useful part accurately.
1. Give every language a stable URL
A Japanese translation should be a real URL, not only a client-side toggle. A locale prefix such as /ja makes the page linkable, cacheable and easy for crawlers to understand.
Keep the translated page aligned with its English counterpart through a shared translation key. This lets your sitemap, language links and editorial workflow stay consistent as the library grows.
- Use one canonical URL per language.
- Keep locale in the path, not only in local storage.
- Link the English and Japanese versions explicitly.
2. Make metadata describe the rendered language
Next.js metadata should be generated from the same localized content that the reader sees. Set the title, description, Open Graph locale, image alt text and keywords for the current language.
Add language alternates for the translation pair and a self-referencing canonical URL. This helps search engines choose the right result without treating the translations as duplicate pages.
3. Keep content and structured data server-rendered
Server-render the article body, FAQ and JSON-LD so the first response contains the meaningful content. Use BlogPosting, BreadcrumbList and FAQPage only when the matching content is visible on the page.
Static generation keeps editorial pages fast while preserving full HTML for crawlers, social previews and users on slower connections.
4. Write for search and answer engines
Start each article with a short answer and a scannable summary. Then support it with headings, examples and FAQs that answer real follow-up questions. This structure is useful to people and gives AI systems clear, attributable passages.
Also publish a concise llms.txt index that names the product, links to important pages and exposes the best guides in both languages. Keep claims specific and easy to verify.
FAQ
Frequently asked questions
Should Japanese pages use a /ja URL?
Yes. A stable locale-prefixed URL is linkable and crawlable, and it gives each language its own canonical page and metadata.
Where should hreflang be added in Next.js?
Generate language alternates in the route metadata and keep each locale's canonical URL self-referencing. Include the same relationship in your sitemap when possible.
What makes a page useful for GEO?
Answer the main question early, use clear headings and definitions, include verifiable details, and expose stable URLs and structured data. Optimize for helpfulness first.
Build the first useful version
Turn your idea into something you can test.
Describe the user and outcome. Supacode will create the code, preview it live and save every change as a restorable version.