Hreflang is the tag that stops your German page competing with your English one. It is also the tag most often implemented wrongly — and a broken implementation is worse than none at all.
Hreflang is an annotation that tells search engines a page has versions for other languages or regions, and which version suits which audience. Without it, a site published in three languages presents three pages about the same thing and leaves the search engine to guess which one a Norwegian reader should see — often wrongly, and sometimes by treating them as duplicates.
It is not a ranking factor and will not lift a page in results. What it does is make sure the right version is the one shown, which for a business selling into several markets is the difference between a visitor who converts and one who lands on a page in a language they do not read.
A broken hreflang set is worse than no hreflang. When the annotations are invalid or non-reciprocal, search engines ignore them entirely and fall back to their own judgement — but the site has usually been restructured on the assumption that they work, which means duplicate-looking pages across languages with no signal to separate them. If you cannot maintain reciprocity, publishing without hreflang and keeping the languages on clearly separate URLs is the safer position.
The prior question is whether the site should be multilingual at all. Machine-translated pages published at scale are, by most search engines' own guidance, low-value content, and they carry a real cost: someone has to maintain them, and a badly translated page damages trust more than an English one would. A useful test is whether you can answer an enquiry in that language. If nobody in the business can, the translated page is generating conversations you cannot have.
Ettex Sites gives you the URL structure and the page-level control the annotation needs, and the surrounding technical checklist is in seo checklist, with the geographic side of search in local seo — a different problem from the language one, and frequently confused with it.
To be direct: we do not translate content, do not generate hreflang automatically and do not validate the annotations across a site. Those are jobs for a translator and for a technical audit tool, and neither is something a site builder should pretend to do.
Telling search engines which language or regional version of a page to show to which audience, so versions of the same content do not compete or get treated as duplicates.
No. It affects which version is shown, not how highly it ranks. The benefit is that the right visitor lands on the right page.
Non-reciprocal declarations — one version points at another that does not point back. Search engines discard the whole set when that happens.
Subdirectories, in almost every case. Country domains give the strongest local signal and cost far more in registration, hosting and ongoing attention than a small site can justify.
Raising average order value is usually cheaper than winning more customers, and most shops leave it alone because the tactics feel pushy. Done properly they are the opposite — they answer questions the buyer already has.
A privacy policy is a disclosure, not a disclaimer. Generated from a template it describes a business that is not yours — and the first person to notice is usually the regulator or the customer who asked a question.
A returns policy is read before the purchase far more often than after it. Written as a defence against fraud it costs you sales; written as a promise it becomes one of the strongest reasons to order.