What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
In SerpPrism’s selected sample of 60 accessible high-traffic homepages, 28 (46.7%) exposed hreflang annotations in their initial HTML. That is a snapshot of those homepages, not a universal adoption rate or a score for whether the sites’ implementations were correct. Google’s practical test is whether the annotations accurately connect equivalent localized pages—and whether those links are reciprocal.
What the 60-site report found
SerpPrism’s report says it started with 78 high-traffic domains and fetched their homepages on September 24, 2026. Sixty returned a usable page: 41 directly and 19 through a local proxy. The other 18 were unreadable because of bot protection, timeouts, or 404 responses.
In the usable sample, 28 homepages declared hreflang and 32 declared none. Among the 28 adopters, 24 had six or more alternate links, the median count was 15, and the mean was 30.9 annotations. Nine of the 28 adopters—32.1%—did not include an x-default annotation. These are counts of annotations found on sampled homepages, not counts of all locale pages or proof that each annotation was useful.
The report is marked updated September 22, 2026, but says pages were fetched on September 24, 2026. Because the stated collection date is later than the displayed update date, the page’s update label does not independently verify when the reported collection occurred. The report says its script and domain list are published alongside it; the figures here remain the report’s stated findings.
#1 Best Overall
Why some apparent omissions may be sampling artifacts
The report notes that GitLab, Notion, Zoom, and Spotify localized content on a different host or subdomain from the bare homepage it sampled. Their absence of hreflang on that sampled homepage alone is not evidence that their localized pages are broken or lack annotations.
SerpPrism interprets many of the 32 non-adopters as effectively monolingual or single-locale sites for which hreflang would not help. That is the report’s interpretation of its examples, not a controlled assessment of whether every organization in the sample needs hreflang.
Rank #2
How this compares with the broader Web Almanac crawl
The 2025 HTTP Archive Web Almanac detected raw hreflang on 20.3% of desktop pages and 19.7% of mobile pages; its rendered observations were 20.8% on desktop and 20.2% on mobile. Those figures are page-level crawl rates, not percentages of sites or homepages.
| Source and measure | Population and denominator | Reported result |
|---|---|---|
| SerpPrism, initial HTML | 60 accessible homepages from a selected set of high-traffic domains; 28 adopters | 28 of 60, or 46.7% |
| HTTP Archive Web Almanac 2025, raw crawl | Pages observed on desktop and mobile | 20.3% desktop; 19.7% mobile |
| HTTP Archive Web Almanac 2025, rendered crawl | Pages observed on desktop and mobile | 20.8% desktop; 20.2% mobile |
These rates are not directly comparable. SerpPrism counted selected homepages at the domain level and inspected initial HTML; the Web Almanac measured page-level prevalence across a broader crawl and reported raw and rendered observations by device. Neither percentage says whether a particular site’s annotations are valid or whether hreflang is needed on a particular page.
Rank #3
What hreflang tells Google—and what it does not
Hreflang connects pages that are localized versions of the same content, helping Google understand which version is intended for a language or region. It is not a command to detect a page’s language. Google says it determines language algorithmically and does not use hreflang or the HTML lang attribute to detect it.
Use a language code, optionally followed by a region code. For example, Google identifies de-BE, nl-BE, and fr-BE as valid language-region values; a generic language value such as de is also valid. A region-only value is invalid, and UK does not work as a region code in hreflang.
How to implement localized versions
Choose one of Google’s three equivalent methods
Google supports HTML <link> annotations, HTTP Link headers, and XML sitemaps. Its documentation says, “The three methods are equivalent from Google’s perspective and you can choose the method that’s the most convenient for your site.” Pick the method your team can maintain accurately; using all three provides no Search benefit and can make management harder. HTTP headers can be useful for non-HTML files such as PDFs.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Make every language version part of the same reciprocal set
For a group of equivalent pages, each version should list itself as well as the other localized versions. The URLs must be fully qualified, and alternates may live on different domains. Google warns: “If two pages don’t both point to each other, the tags will be ignored.”
If maintaining a complete network is difficult, Google says some language links can be omitted while mutually linked versions can still be processed. Its guidance emphasizes linking new languages back to the originating or dominant language. That is preferable to publishing one-way references that do not form a reciprocal relationship.
Add a fallback only when it serves the unmatched visitor
x-default identifies a fallback for users whose language settings do not match a localized version. Google recommends it especially for language or country selectors and auto-redirecting homepages, but it is recommended rather than mandatory. The fact that nine adopters in the SerpPrism sample lacked it does not, by itself, establish an implementation error.
Check the locale relationships, not the annotation count
- Confirm each alternate URL is the intended localized equivalent, rather than merely another page on the site.
- Check that every version lists itself and the other versions in its group.
- Verify that the links are reciprocal between pages.
- Use valid language or language-region codes; do not use a region without a language.
- Keep the chosen implementation method consistent and manageable.
- Consider
x-defaultfor a selector or redirecting homepage when a fallback would help users whose language is unmatched.
A large site with many locales may naturally have many annotations. The report’s median of 15 and mean of 30.9 among adopters are observations, not targets for smaller sites. The quality of the locale relationships matters more than the raw total.
Free tools Windows power users keep installed
One-click scans. No signup required.
Google’s official guidance and troubleshooting details are in Localized Versions of your Pages (last updated September 21, 2026 UTC). SerpPrism’s report is What 60 Sites Actually Do With hreflang; the broader crawl figures appear in the 2025 HTTP Archive Web Almanac SEO chapter.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
