hreflang

An hreflang tag pairs each EN page with its TR counterpart so search engines and AI search serve the right locale to the right reader. The tag goes in the head of every localized page, alongside the canonical URL.

What it means in operation

A page at /en/pricing carries an hreflang link to /tr/pricing declaring “tr”. The TR page carries the reverse link back to “en”. Both pages also carry an x-default link, usually pointing to the EN version, which tells Google which locale to serve when the visitor’s language is neither English nor Turkish. The MobiTaste marketing site emits these tags from a single registry, so a new page added to the URL map produces the right hreflang block automatically. The same registry feeds the sitemap, so search engines see a consistent picture.

Why it matters

Without hreflang, Google may serve the EN page to a Turkish reader who searched in Turkish, or vice versa. The reader bounces, the rankings drop, and the page’s authority leaks across both locales. With hreflang done right, Google sends each reader to their language and the ranking compounds per locale. The cost is one line in the head per locale per page, which is automated. The buyer’s question is whether the vendor handles it. If you have to add the tags yourself in a CMS, the answer is no.

Related terms

• Locale: the language-region pair hreflang declares.
• Schema markup: the JSON-LD that complements hreflang.
• Sitemap: the file that lists every URL hreflang covers.