Get in Touch About the Hreflang Checker

What to Include in a Bug Report

Email [email protected] with enough detail to reproduce the problem.

For checker bugs

If the checker reports a missing return link you can see in the target's source, rejects a language code that is valid, reads a canonical differently from what the page serves, or misses tags that are there, send:

• The URLs you pasted, or the sitemap URL, and which page the finding is about.
• What the report showed versus what you expected, ideally with the tag line copied from the page source.
• Whether the tags are in the HTML, in a Link header or in the sitemap, if you know.

Codes and near-misses

The language, script and region lists follow the ISO tables, plus a short list of three-letter codes Google accepts. If a code you use is rejected and you can point at the standard that defines it, it gets added. The near-miss table (en-UK, en-EU and friends) grows the same way.

For everything else

Questions about how the return-link check works, corrections to the guide, or a note that something written here is out of date all go to the same address. Requests for full-site crawls, scheduled monitoring, accounts or a higher page cap will get a friendly no; the about page explains the boundaries. How submitted URLs are handled is covered in the privacy policy.

There is no form on this page on purpose: a form needs spam protection, and spam protection means loading a third-party script on a site that otherwise loads none.

Replies usually go out within a few days. If your message includes a URL for debugging, it gets read and then deleted, not kept as data.