hreflang Explained: A Practical Guide for Multilingual Sites

By 8 min read

You translated your site, but Google keeps showing the English page to visitors in Vienna and the German page to people in Zurich who expected Swiss prices. That is the exact problem hreflang solves. In this guide you get a plain explanation of what hreflang does, copyable code for the three ways to add it, a look at how WordPress, Shopify and Webflow handle it and a checklist of the mistakes that break most setups.

What hreflang actually does

hreflang is an annotation that tells search engines “this page has equivalents in other languages or regions and here they are.” Google uses it to swap in the right URL for each searcher. According to Google Search Central’s guide to localized versions, Google can sometimes find your alternate versions without help, but it still recommends you mark them explicitly.

Two things hreflang does not do are worth knowing up front. First, it does not tell Google what language a page is in. Google’s documentation states that it detects language with its own algorithms and ignores both hreflang and the HTML lang attribute for that purpose. Second, it does not redirect anyone. It only influences which URL appears in search results.

It also helps with a worry many site owners have: duplicate content. Google’s same guide explains that localized pages only count as duplicates when the main content stays untranslated. A properly translated page is its own page.

The building blocks: language and region codes

Every hreflang value starts with a language code in ISO 639-1 format, such as de, fr or en. You can optionally add a region code in ISO 3166-1 Alpha 2 format after a hyphen, which gives you values like de-AT (German for Austria) or en-GB (English for the United Kingdom).

A few rules from Google’s documentation trip people up constantly:

  • A region code on its own is invalid. be is read as Belarusian, not Belgium.
  • The United Kingdom is GB, not UK. Codes like UK, EU or UN are wrong and Google ignores that part of the annotation.
  • Script variants are allowed, for example zh-Hans for Simplified Chinese and zh-Hant for Traditional Chinese.
  • Codes outside these standards, such as es-419 for Latin American Spanish, are not supported by Google.
  • x-default is a special value that needs no language code.

If you only have one German version for everyone, use plain de. Add regions only when the content really differs, for example different prices, currencies or shipping rules.

Three ways to add hreflang (with code)

Google treats all three methods as equivalent and says that using more than one brings no extra benefit. Pick the one that fits your stack and stick with it.

This is the most common option for small sites. Each language version gets the same block of tags in its <head>. Every block lists all versions, including the page itself.

<head>
  <link rel="alternate" hreflang="en" href="https://example.com/en/pricing/" />
  <link rel="alternate" hreflang="de" href="https://example.com/de/preise/" />
  <link rel="alternate" hreflang="de-AT" href="https://example.com/at/preise/" />
  <link rel="alternate" hreflang="fr" href="https://example.com/fr/tarifs/" />
  <link rel="alternate" hreflang="x-default" href="https://example.com/en/pricing/" />
</head>

Notice that the URLs are fully qualified, including https://. Google’s documentation requires this; relative paths like /de/preise/ are not valid here. Alternate URLs may sit on different domains, so example.de and example.fr can point at each other.

Method 2: HTTP headers for PDFs and other files

Non-HTML files have no <head>, so you send the same information in an HTTP Link header. This is handy if you publish price lists or manuals as PDFs in several languages.

Link: <https://example.com/files/manual-en.pdf>; rel="alternate"; hreflang="en",
      <https://example.com/files/manual-de.pdf>; rel="alternate"; hreflang="de",
      <https://example.com/files/manual-en.pdf>; rel="alternate"; hreflang="x-default"

You configure this on the server (for example in Nginx, Apache or your CDN), not in the file itself.

Method 3: the XML sitemap

On larger sites, adding tags to every template gets messy. The sitemap method keeps all annotations in one file. Each <url> entry has its own <loc> and then lists every variant, itself included, as <xhtml:link> children. Do not forget the xmlns:xhtml namespace declaration at the top.

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <url>
    <loc>https://example.com/en/pricing/</loc>
    <xhtml:link rel="alternate" hreflang="en" href="https://example.com/en/pricing/" />
    <xhtml:link rel="alternate" hreflang="de" href="https://example.com/de/preise/" />
    <xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/en/pricing/" />
  </url>
  <url>
    <loc>https://example.com/de/preise/</loc>
    <xhtml:link rel="alternate" hreflang="en" href="https://example.com/en/pricing/" />
    <xhtml:link rel="alternate" hreflang="de" href="https://example.com/de/preise/" />
    <xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/en/pricing/" />
  </url>
</urlset>

Google notes that these xhtml:link child elements do not count toward the sitemap’s URL limit and that a sitemap can only list URLs from its own directory and below.

Which method should you choose?

Here is a quick comparison based on Google’s documentation and the practical trade-offs for small teams.

Method Best for Where you edit it Main drawback
HTML link tags Most CMS sites and hand-coded pages Page template <head> Adds markup to every page; easy to forget on new templates
HTTP header PDFs and other non-HTML files Server or CDN config Needs server access; invisible in page source
XML sitemap Large sites, shops with many products One sitemap file Harder to spot errors by viewing a page

For a typical business site, HTML tags generated by your CMS or plugin are the simplest route. A sitemap starts to pay off once you manage hundreds of product pages per language, because one file is easier to audit than hundreds of templates.

What x-default is for

x-default names the page users should see when none of your language or region versions match them. Google suggests a language picker or an auto-redirecting homepage as typical targets. In practice many sites simply point it at their main language version, as in the examples above.

It is optional, but skipping it is the single most common gap. In Ahrefs’ study of 374,756 domains using hreflang, 56.3% were missing x-default.

The mistakes that break hreflang

That same Ahrefs study found that 67% of domains using hreflang had at least one issue. The most frequent ones after missing x-default were:

  1. Missing self-referencing tags (18% of domains). Every page must list itself as well as its alternates.
  2. Links to redirected or broken pages (16.9%). If you change a URL, update the hreflang targets too.
  3. Missing return links (15.3%). If your English page points to the German one, the German page must point back. Google’s documentation warns that one-way annotations may be ignored.
  4. Pointing to non-canonical URLs (8%). hreflang should only reference the canonical version of each page.
  5. Incorrect hreflang values (4.6%), usually the code errors described above.

The canonical issue deserves a closer look. Ahrefs’ hreflang guide explains that when hreflang points at a URL whose canonical tag names a different page, the two signals contradict each other and confuse search engines. The rule of thumb: each language version should carry a self-referencing canonical. Then point hreflang at exactly those URLs.

One more practical point: Google retired the International Targeting report in Search Console, which used to flag hreflang errors. Its help page on the deprecation confirms that Google continues to support and use hreflang tags. You now check them with crawlers, validators or by reading your page source.

You often do not have to write these tags by hand.

Shopify creates hreflang tags automatically for every international domain or subfolder you set up in Markets, according to the Shopify Help Center. You can switch this off under Online Store > Preferences, but Shopify warns that you then need to add your own tags to the theme. Do not add a second set on top of the automatic one.

Webflow generates hreflang for its Localization feature, either as page-level tags or in the auto-generated sitemap, as described in Webflow’s help article on localized SEO. If you use a custom sitemap instead, you have to add the annotations yourself.

WordPress has no built-in multilingual support, so hreflang comes from your translation plugin. Check what your plugin outputs by viewing the page source and searching for hreflang. If you run a plugin and an SEO plugin side by side, make sure only one of them prints the tags.

Custom HTML sites need the tags in your templates or a sitemap. A clean language menu helps users switch versions too; our language switcher code generator gives you a starting point.

What about Bing?

Bing is the exception. Ahrefs’ hreflang guide describes hreflang as a weak signal for Bing, which relies mainly on the content-language attribute, links and visitor data. The same guide notes that Yandex reads hreflang while Baidu does not. Bing’s own webmaster blog post from 2011 recommends the content-language meta tag with a language and country code:

<meta http-equiv="content-language" content="de-at" />

Adding this alongside hreflang does no harm and covers Bing’s preferred signal. Keep the value consistent with your <html lang> attribute so the signals agree.

FAQ

Do I need hreflang if my site only has one language?

No. hreflang describes relationships between equivalent pages in different languages or regions. With a single version there is nothing to annotate.

Does hreflang improve my rankings?

Not directly. It helps Google show the right language version to the right searcher, which can improve clicks and reduce bounces from people who land on a page they cannot read. It does not boost a page that would not rank anyway.

Should I use both HTML tags and a sitemap?

Google says the methods are equivalent and using more than one gives no extra benefit. Using two also doubles the places where errors can creep in, so choose one.

Can hreflang point to a page on another domain?

Yes. Google explicitly allows alternate URLs on different domains, so example.de and example.com/en/ can reference each other as long as both sides link back.

How do I check if my hreflang works?

Open a page, view the source and confirm every version is listed with full URLs, including the page itself and x-default. Then open one of the alternates and confirm it lists the same set. A site crawler can do this at scale.

Conclusion

hreflang is simple in principle and fiddly in practice. Every version lists every version, including itself; every link is answered by a return link; codes follow ISO standards; and all targets are canonical, live URLs. Add x-default and you already avoid the most common gap from the Ahrefs data. Start by viewing the source of your most important page in each language today, because that five-minute check catches most problems.

If you still need the translations themselves, heylingo adds AI translation with translation memory to your site through one script tag, lets you correct texts inline on the live site and covers 30+ languages for EUR 20 per 1,000,000 translated characters per month. The hreflang setup stays with your CMS, plugin or developer.

See heylingo pricing and start translating your site

Sources

JE

Written by

Jermaine builds and runs heylingo single-handedly from Germany and answers every support email personally.

More from the blog

Information pursuant to § 5 DDG (German Digital Services Act).

Jermaine J. Ernst
c/o Block Services
Stuttgarter Str. 106
70736 Fellbach
Germany

Email: info@heylingo.io
VAT ID: DE370296865

Responsible for content pursuant to § 18 (2) MStV: Jermaine J. Ernst, address as above.

Consumer dispute resolution

We are neither willing nor obliged to take part in dispute resolution proceedings before a consumer arbitration board.

Liability for content

As a service provider we are responsible for our own content on these pages under general law, pursuant to § 7 (1) DDG. Under §§ 8 to 10 DDG we are not obliged to monitor third-party information that is transmitted or stored, or to investigate circumstances that indicate illegal activity. Obligations to remove or block the use of information under general law remain unaffected. Liability in this respect is only possible from the moment we become aware of a specific infringement. As soon as we learn of such an infringement, we will remove the content immediately.

This website links to external websites of third parties whose content we cannot influence, so we cannot accept any liability for that content. The respective provider or operator of a linked page is always responsible for its content. The linked pages were checked for possible legal violations when the link was set, and no illegal content was apparent at that time. Permanent monitoring of linked pages is not reasonable without concrete indications of an infringement. If we become aware of an infringement, we will remove the link immediately.

The content and works created by the site operator on these pages are subject to German copyright law. Reproduction, editing, distribution and any kind of use beyond the limits of copyright law require the written consent of the respective author or creator. Where content on this site was not created by the operator, the copyrights of third parties are respected and such content is marked as such. If you nevertheless become aware of a copyright infringement, please let us know. As soon as we learn of an infringement, we will remove the content immediately.

Last updated 10 October 2026

Privacy policy

This privacy policy explains which personal data we process when you visit heylingo.io, contact us or buy heylingo. It also explains how data is handled when one of our customers uses the heylingo translation service on their own website.

Controller

The controller within the meaning of the EU General Data Protection Regulation (GDPR) is:

Jermaine J. Ernst
c/o Block Services
Stuttgarter Str. 106
70736 Fellbach
Germany

Email: info@heylingo.io

Please use this address for any question about data protection and to exercise your rights.

Overview

heylingo.io is a static website. When you browse it:

Personal data is processed only in the cases described below: delivery of the website by our host, images in blog posts, YouTube videos you choose to play, contact by email and the purchase of heylingo through Stripe. A separate section covers the heylingo translation service.

Hosting and server logs

heylingo.io is hosted by Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. Each time you open a page, Cloudflare processes the following server log data:

Cloudflare uses this data to deliver the website to you and to protect it from attacks and misuse. We do not use it to identify you or to create user profiles.

The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest is the secure and reliable delivery of our website.

Cloudflare may process data outside the European Union, including in the USA. Cloudflare, Inc. is certified under the EU-U.S. Data Privacy Framework, so transfers to it are based on the adequacy decision of the European Commission (Art. 45 GDPR). Where the Data Privacy Framework does not apply, transfers are based on the EU standard contractual clauses (Art. 46(2)(c) GDPR).

More information: Cloudflare privacy policy.

Blog images and videos

Images

Images in our blog posts are loaded from assets.seobotai.com, an external image host. When you open a blog post, your browser requests these images directly from that host. The host thereby receives your IP address and the technical information that is part of every request, such as the requested file, the address of our website and your browser’s user agent.

The host needs your IP address to deliver the images. We have no influence on how the host processes this data.

The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest is showing images in our blog posts.

YouTube videos

Some blog posts contain YouTube videos. They are not loaded when you open the page. No data is sent to YouTube until you click “play”. Only then is the video loaded from youtube-nocookie.com.

YouTube is operated by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Once the video is loaded, Google receives at least your IP address and the address of the page. Google may also store information on your device or read it from your device, for example cookies, and may process data about how you use the video. Google may process data in the USA; Google LLC is certified under the EU-U.S. Data Privacy Framework.

The legal basis is your consent, which you give by clicking “play” (Art. 6(1)(a) GDPR and, for storing and reading information on your device, § 25(1) of the German Telecommunications and Digital Services Data Protection Act, TDDDG).

Your consent applies only to the video you start. You can withdraw it at any time with effect for the future: do not start any further videos and close or reload the page. You can delete cookies set by Google in your browser settings.

More information: Google privacy policy.

Contact by email

If you email us, we process your email address, your message and any other information you provide, such as your name or company. We use this data only to answer your request.

If your request relates to a contract with us or to concluding one, the legal basis is Art. 6(1)(b) GDPR. Otherwise the legal basis is Art. 6(1)(f) GDPR; our legitimate interest is answering requests sent to us.

We delete the data once your request has been fully dealt with, unless statutory retention obligations apply (see “Retention”).

Purchasing heylingo via Stripe

You sign up for heylingo through Stripe Checkout, which you reach via a payment link on heylingo.io. Invoices, your payment method and cancellation are managed in the Stripe Customer Portal. There is no user account on heylingo.io.

The payment provider is Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland. Stripe processes the data you enter during checkout and in the customer portal. This includes your name, email address, billing address, company name and VAT ID if you provide them, your payment details, and transaction and invoice data.

You enter your payment details directly with Stripe. We do not receive your full card or account details.

We receive from Stripe the data we need to manage your subscription and bill your usage, such as your name, email address, billing details and payment status. To bill you, we report your usage (the number of translated characters) to Stripe.

The legal basis is Art. 6(1)(b) GDPR, because the processing is necessary to conclude and perform the contract. We keep invoices and accounting records to meet our retention obligations under German commercial and tax law. The legal basis for this is Art. 6(1)(c) GDPR.

Stripe also processes some data under its own responsibility, for example to prevent fraud and to meet its legal obligations as a payment provider. Stripe may transfer data to Stripe, Inc. in the USA, which is certified under the EU-U.S. Data Privacy Framework.

More information: Stripe privacy policy.

The heylingo translation service

This section is for our customers and for visitors to websites that use heylingo.

Our role

heylingo makes a customer’s website multilingual. When a customer uses heylingo, we process the content of the customer’s website on the customer’s behalf. For any personal data of visitors to that website, the customer is the controller and we act as a processor (Art. 28 GDPR).

If you visit a website that uses heylingo, please read that website’s privacy policy and send requests about your data to its operator.

Customers can request a data processing agreement under Art. 28 GDPR at info@heylingo.io.

In the visitor’s browser

The customer adds the heylingo script to their website. The script shows a language switcher and picks the visitor’s preferred language. It stores the chosen language in the visitor’s browser (localStorage) so the website appears in that language on later visits. The script sets no cookies.

The entry stays in the browser until the visitor deletes it. Storing it is limited to what is strictly necessary for the language function the visitor uses (§ 25(2) no. 2 TDDDG).

Translation

To translate a page, the script sends the page’s text to our translation service. Because the visitor’s browser connects to the service, the service also receives the visitor’s IP address and the technical information that is part of every request.

Page text usually contains no personal data. If a page does contain personal data, for example names on a team page or text shown only to a logged-in user, this text is sent to us as well. The customer decides on which pages the script runs.

Text that is translated for the first time is translated by AI. For this we use a large language model of Anthropic PBC, USA, through its API, as a sub-processor. Transfers to Anthropic are based on the EU standard contractual clauses (Art. 46(2)(c) GDPR).

Each translation is stored in a translation memory for that website. Later visitors receive the stored translation, so the same text is not sent to the AI provider again.

The translation service and the translation memories run on servers of netcup GmbH in Germany.

Inline editing

Customers can correct translations directly on their live website. This edit mode can only be used by the site owner. Corrected sentences are stored in the translation memory and are never re-translated.

Deletion

When a customer cancels, the script stops translating and the website shows its original language. The website’s translation memory, including manual corrections, is deleted 30 days after the cancellation takes effect.

Retention

We keep personal data only as long as it is needed for the purpose it was collected for, unless a statutory retention obligation applies. While such an obligation applies, we use the data only for that purpose.

Your rights

You have the following rights regarding your personal data:

To exercise your rights, email info@heylingo.io. If your request concerns a website that uses heylingo, please contact the operator of that website first, as it is the controller. We support our customers in answering such requests.

Right to object

Where we process your data on the basis of Art. 6(1)(f) GDPR, you can object to the processing at any time on grounds relating to your particular situation (Art. 21 GDPR). We will then stop processing your data, unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing serves to establish, exercise or defend legal claims.

Right to lodge a complaint

You can lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), in particular in the EU member state of your habitual residence, your place of work or the place of the alleged infringement. The authority responsible for us is Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg (the State Commissioner for Data Protection and Freedom of Information of Baden-Württemberg).

No automated decision-making

We do not use automated decision-making, including profiling, within the meaning of Art. 22 GDPR. The AI used by heylingo translates text; it does not make decisions about people.

Changes to this policy

We update this policy when our services or the legal requirements change. The current version is always available on heylingo.io. The date of the last update is shown at the end of this policy.

Last updated 10 October 2026

Terms of service

These terms of service govern the use of heylingo, a service that makes websites multilingual. heylingo is offered to businesses only.

1. Scope and parties

These terms apply to all contracts for the use of heylingo between Jermaine J. Ernst, c/o Block Services, Stuttgarter Str. 106, 70736 Fellbach, Germany, email info@heylingo.io (“we”, “us”) and our customers (“you”).

heylingo is offered exclusively to entrepreneurs (Unternehmer) within the meaning of § 14 BGB. These are natural or legal persons or partnerships with legal capacity who conclude the contract in the exercise of their commercial or independent professional activity. Consumers are not our target group. By concluding a contract, you confirm that you are acting as an entrepreneur.

Your own terms and conditions do not apply, even if we do not expressly object to them, unless we have agreed to them in text form.

2. The service

heylingo makes your website multilingual. You add one script tag to your website. The script shows a language switcher, selects the visitor’s preferred language, stores the chosen language in the visitor’s browser, sends the page’s text to our translation service and replaces it with the translation.

Text that has not been translated before is translated by AI (a large language model) and stored in a translation memory for your website. Later page views receive the stored translation.

All languages supported by heylingo are included. The currently supported languages are listed on heylingo.io.

You can correct translations directly on your live website, in an edit mode that only you as the site owner can use. Sentences you have edited manually are never re-translated.

There is no user account or dashboard on heylingo.io. Invoices, your payment method and cancellation are managed in the Stripe Customer Portal.

For the term of the contract, you receive a non-exclusive, non-transferable right to use the heylingo script on your website. All other rights to heylingo remain with us.

We may use subcontractors to provide the service, in particular for hosting and AI translation. We may develop heylingo further and change its features, provided the core function described in this section is preserved and the change is reasonable for you.

3. Conclusion of the contract

The description of heylingo on heylingo.io is not a binding offer.

You sign up through Stripe Checkout, which you reach via the payment link on heylingo.io. By completing the checkout, you make a binding offer to conclude the contract. We accept it by activating your subscription, which normally happens immediately after checkout.

The contract language is English. These terms can be viewed, saved and printed on heylingo.io at any time.

4. Prices and billing

heylingo has one pricing model: pay per use. The price is a monthly price per one million translated characters, as listed on heylingo.io (currently EUR 20 per 1,000,000 characters per month). It includes all supported languages.

The characters counted for a month are the characters of the translated text that heylingo keeps for your website in its translation memory, across all target languages. Page views and the number of visitors do not affect the price.

Billing runs through Stripe as a metered subscription. Your usage is billed monthly in arrears and charged to the payment method you stored with Stripe. Invoices are available in the Stripe Customer Portal.

All prices are net prices. VAT is added where applicable.

We announce price increases by email at least 30 days before they take effect. A new price applies from the first billing month after it takes effect. As you can cancel at any time, you can avoid a price increase by cancelling before it takes effect.

If a payment fails, we may suspend the service after notifying you until the outstanding amount has been paid. During a suspension, your website shows its original language.

5. Your obligations

You must hold all rights needed to have the content of your website translated, stored and displayed, including in translated form.

You grant us a non-exclusive right to process, translate, store and deliver your content and its translations, to the extent necessary to provide heylingo. This includes the right to have our subcontractors do so. The right is limited to the term of the contract and the deletion period in section 8.

You must not use heylingo for unlawful content, in particular content that infringes the rights of third parties or violates criminal law.

You are responsible for integrating the script correctly, as described by us, and only on websites that you operate or are authorised to operate.

You must not misuse heylingo. In particular, you must not:

If a third party asserts claims against us because of content on your website or because you breached these terms, you indemnify us against these claims, including the reasonable costs of legal defence. This does not apply if you are not responsible for the breach.

6. AI translations

Translations are produced automatically by AI. We do not review them before they are shown on your website.

Machine translations may contain errors, omissions or wording that does not fit the context. We provide machine translation, not a reviewed or certified translation.

You should review translations, especially where errors can have legal or financial consequences, such as legal texts, prices, product information and safety notices. You can correct any translation in the edit mode on your website.

You are responsible for all content published on your website, including its translations.

7. Availability

We aim to keep heylingo available and working, but we do not guarantee a specific availability or uptime. Interruptions can occur, for example due to maintenance, updates or disruptions at our subcontractors.

If heylingo is unavailable, your website shows its original language. As you pay only for translated characters, no charges arise for text that is not translated.

8. Term and cancellation

The contract starts when it is concluded and runs for an indefinite period.

You can cancel at any time in the Stripe Customer Portal or by email to info@heylingo.io. Usage up to the effective date of cancellation is billed.

We can cancel the contract with 30 days’ notice by email.

The right of both parties to terminate for good cause without notice remains unaffected. Good cause for us exists in particular if you are in default of payment despite a reminder, use heylingo for unlawful content or seriously breach your obligations under section 5. In these cases, we may instead suspend the service for your website.

After the contract ends, the script stops translating and your website shows its original language. We delete your website’s translation memory, including manual corrections, 30 days after the contract ends. We recommend removing the script tag from your website.

9. Data protection

We process personal data in accordance with the GDPR and our privacy policy.

When you use heylingo, we process the content of your website on your behalf. For any personal data of visitors to your website, you are the controller and we act as your processor. A data processing agreement under Art. 28 GDPR is available on request at info@heylingo.io.

You are responsible for meeting your own data protection obligations towards the visitors of your website, in particular for informing them about the use of heylingo in your privacy policy.

10. Liability

We are liable without limitation for intent and gross negligence, for injury to life, body or health, where we have given a guarantee, and under the German Product Liability Act (Produkthaftungsgesetz).

For slight negligence, we are liable only for breach of an essential contractual obligation. This is an obligation whose fulfilment makes the proper performance of the contract possible in the first place and on whose fulfilment you may regularly rely. In that case, our liability is limited to the damage that is typical for this type of contract and foreseeable when the contract was concluded.

Otherwise, liability for slight negligence is excluded. Strict liability for defects that already existed when the contract was concluded (§ 536a(1) BGB) is also excluded.

These limitations also apply in favour of our vicarious agents and subcontractors.

11. Changes to these terms

We may change these terms for a valid reason, in particular because of changes in the law or case law, or changes to heylingo. We will notify you of changes by email at least 30 days before they take effect.

You can object to the changes within this period. If you do not object, the changed terms are deemed accepted. We will point this out specifically in our notice. If you object, the contract continues on the previous terms, and we may cancel it in accordance with section 8.

This procedure does not apply to changes to the main obligations of either party. Price changes are governed by section 4, changes to the service by section 2.

12. Final provisions

German law applies, excluding the UN Convention on Contracts for the International Sale of Goods (CISG).

If you are a merchant (Kaufmann), a legal entity under public law or a special fund under public law, or if you have no general place of jurisdiction in Germany, the exclusive place of jurisdiction for all disputes arising from this contract is the competent court for Fellbach, Germany. We may also bring an action at your general place of jurisdiction.

If any provision of these terms is or becomes invalid, the remaining provisions remain valid. The invalid provision is replaced by the statutory provisions.

Last updated 10 October 2026