Hreflang Hub
Hreflang Hub
@HreflangHub

Three ways to declare hreflang, and when each one breaks

Three ways to declare hreflang, and when each one breaks

Google accepts hreflang from HTML link elements, from HTTP headers, and from XML sitemaps. They are equivalent in weight, but each has a failure mode you should know before choosing.

HTML head. Simple to inspect, easy to template. Breaks when the number of alternates grows: a site with forty locales adds forty link tags to every page, which bloats HTML and slows first paint. Also breaks in JS-injected heads.

HTTP headers. The only option for non-HTML files such as PDFs. Breaks when a CDN or caching layer strips or rewrites headers, and almost nobody looks at response headers during a routine audit, so the breakage stays invisible.

XML sitemap. Scales well, keeps HTML clean, and is easy to regenerate from a database. Breaks when the sitemap and the pages disagree, for example after a URL migration when the sitemap still lists old paths.

Pick one method and use it consistently. Mixing two is allowed, but any conflict between them turns into "Google ignores both". The audit question is always the same: does every source say the same thing about every URL?

—
Если понравилось — посмотри @affcareers_dubai
Этот пост опубликован в Telegram-канале Hreflang Hub. Подписаться можно по ссылке: @HreflangHub.
tech

Свежие посты в категории «Tech Infrastructure»

Все каналы категории →

start

Готовы запустить рекламу через сеть public.tg?

Новый оффер, продукт, GEO, кейс, событие или партнёрский запуск — соберём маршрут под задачу и отдадим медиаплан.

Telegram для медиаплана: @AFFtop_connect. Быстрый тест: $20 за канал, $1000 за пакет по сети.