Showcase

Name: Intlayer
Author: Intlayer

Discover projects built with Intlayer

Submit Your Project

Back to Showcase Gallery

GitHub Repo

Visit Website

Intlayer React Router V7

This is the home page description.

PublishedMarch 11, 2026

Last ScanMarch 11, 2026

Intlayer Versionlatest

Rate this project

Libraries Used

Intlayer

v8.2.2

intlayer

vlatest

react-intlayer

vlatest

More Projects

Explore other projects that use Intlayer for their internationalization.

SEO & Global Reach

Technical analysis of internationalization best practices.

Lang tag:

"en"

The lang attribute on the <html> tag declares the primary language of the page. This helps search engines and browsers understand the content language.

<html lang="en">

Why it matters: Essential for SEO and accessibility. Screen readers use it to pronounce content correctly.

HTML dir:

"ltr"

The dir attribute on the <html> tag specifies the text directionality of the content. This is essential for languages that are written right-to-left (RTL).

<html lang="ar" dir="rtl"><html lang="en" dir="ltr">

Why it matters: Critical for proper rendering of RTL languages like Arabic, Hebrew, Persian, and Urdu. Improves readability and user experience. Values: ltr (left-to-right), rtl (right-to-left), or auto.

Hreflangs:

[]

Hreflang links tell search engines about alternative language versions of your page. They prevent duplicate content issues and help serve the right language to users.

<link rel="alternate" hreflang="en" href="https://example.com/en" /><link rel="alternate" hreflang="fr" href="https://example.com/fr" /><link rel="alternate" hreflang="x-default" href="https://example.com/" />

Best practice: Include an x-default for users whose language you don't support.

x-default:

Indicates whether the page includes an x-default hreflang tag. This tag specifies a default/fallback page for users whose language preferences don't match any specific hreflang.

<link rel="alternate" hreflang="x-default" href="https://example.com/" /><link rel="alternate" hreflang="en" href="https://example.com/en/" /><link rel="alternate" hreflang="fr" href="https://example.com/fr/" />

Best practice: Always include x-default in multilingual sites. It should point to a language selector page or your primary language version. Why it matters: Ensures international users get directed to an appropriate page even if their language isn't specifically supported.

Canonical:

A canonical tag tells search engines which version of a URL is the "master" copy. Critical for avoiding duplicate content penalties in multilingual sites.

<link rel="canonical" href="https://example.com/en/page" />

Best practice: Each language version should have its own canonical pointing to itself, not to another language.

Localized links:

Checks if the site contains links to localized content. This indicates proper internal linking between language versions.

Good practice: Cross-link between language versions using hreflang alternates and language switchers. Helps with: User navigation between languages and search engine discovery of all versions.

All anchors localized:

Checks if all internal links on the page include a locale prefix in their path (e.g., /en/, /fr/). This is crucial for proper language routing.

<!-- Good --><a href="/en/about">About</a><a href="/fr/about">À propos</a><!-- Bad --><a href="/about">About</a>

Why it matters: Ensures consistent language experience and proper URL structure for multilingual sites.

robots.txt

Accessible:

The robots.txt file is a text file that tells search engine crawlers which pages or sections of your website they can or cannot access.

User-agent: *Disallow: /admin/Allow: /

Why it matters: Essential for controlling crawler access and protecting sensitive areas while allowing important content to be indexed.

Disallow w/o locale alternates:

Paths that are disallowed in robots.txt but have no equivalent locale-specific versions. This can indicate incomplete internationalization.

Example issue: If /admin/ is disallowed but there's no /en/admin/, /fr/admin/, etc., it may suggest the site structure doesn't consistently use locale prefixes.

Best practice: Ensure all disallowed paths have locale equivalents if your site uses URL-based localization.

sitemap.xml

URLs discovered:

The total number of URLs found in your sitemap.xml file(s). Sitemaps help search engines discover and index all pages on your website.

Good practice: Keep sitemaps up-to-date and organized. For large sites, use sitemap index files that reference multiple sitemaps. Impact: More discovered URLs mean better coverage for search engine indexing.

Alternates present:

Indicates whether your sitemap includes <xhtml:link> elements with alternate language versions. This tells search engines about all language variations of each page.

<url>  <loc>https://example.com/en/page</loc>  <xhtml:link rel="alternate" hreflang="en" href="https://example.com/en/page"/>  <xhtml:link rel="alternate" hreflang="fr" href="https://example.com/fr/page"/></url>

Best practice: Include alternates in sitemap to help search engines understand the relationship between language versions.

x-default present:

The x-default hreflang tag specifies a default page for users whose language isn't explicitly targeted. It's a fallback for international users.

<xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/" />

Best practice: Point x-default to a language selector page or your most universal language version (often English). Important: Every set of hreflang alternates should include an x-default.