HREFLang Tags & The Eternal Wait for Implementation - How Devs & SEOs Can Help Each Other
Tags: webdev, productivity, beginners
Published: 2019-10-07 16:48:40

How long should it take to get a relatively simple request *"[HREFLANG](https://support.google.com/webmasters/answer/189077?hl=en) TAGS PLS"* implemented via an external dev team?

<blockquote class="twitter-tweet"><p lang="en" dir="ltr">That moment when you find out hreflang is finally implemented correctly.<a href="https://twitter.com/hashtag/thestruggleisreal?src=hash&amp;ref_src=twsrc%5Etfw">#thestruggleisreal</a> <a href="https://twitter.com/hashtag/SEO?src=hash&amp;ref_src=twsrc%5Etfw">#SEO</a> <a href="https://twitter.com/hashtag/LinkedInRepost?src=hash&amp;ref_src=twsrc%5Etfw">#LinkedInRepost</a> <a href="https://t.co/YFOngDmmwj">pic.twitter.com/YFOngDmmwj</a></p>&mdash; Jordy Noll (@Noll) <a href="https://twitter.com/Noll/status/1177494006239940608?ref_src=twsrc%5Etfw">September 27, 2019</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

Unfortunately for my client [Splash About](https://www.splashabout.com/) - an ecommerce retailer and manufacturer of childrens' swimwear - the answer is potentially over 3-4 months.

In Splash About's case, there are various things holding the implementation back - such as running multiple CMS systems - which adds complexity to the task.

But this is such a common issue.

Why would this take so long? Here are some of the reasons even a relatively simple technical implementation can drag on.

##1) Failure to give sufficient detail

Not giving enough detail in the initial brief can cause huge problems later down the line. Things that you might consider to be obvious may not be obvious to other people.

Include as much detail as you can, consider any questions the developers could have, and answer them in advance.

The general rule of thumb - especially when working with outsourced teams - is that if you do not explain exactly what to do - it will be done in a different way and you will be annoyed at yourself for not realising just how badly it could go wrong.

##2) Failure to consider complexity & plan for failure

What can be done wrong probably will be done wrong. Think of all the potential mistakes that could be made, and how to avoid them or mitigate them.

In the case of Hreflang tags - this would for example cover: not adding the tags to all pages, not making the tags reciprocal, using a different URL to that which is in the canonical tag, etc etc.

If you do not clearly explain to the developers what potential issues they could face, they may not even be aware that those potential issues exist.

##3) Regular chasing

People can be forgetful. Don't assume that just because a job is important to you, that the team tasked to complete also consider to be equally as important. They won't.

If you want your job completed quickly, you will often have to chase at regular intervals. Set up a calendar appointments to remind yourself, or use project management software to set hard deadlines for different components of the task.

Unsure of how to use the Hreflang tag? I wrote a [guide to the Hreflang tag and specification here](https://www.searchcandy.uk/seo/seo-glossary/rel-alternate-hreflang-definition-guide-usage-examples/).