Coronation Street fans noticed a pretty huge error in last night’s episode

HOW could producers not notice it?!

Coronation Street fans reckon they noticed a glaring error in Friday night’s episode as the baby-swap storyline continues.

Jim McDonald returned to Weatherfield last week, with a woman who he claimed was Katie, the long thought to be dead daughter he shared with ex-wife Liz.

But it was revealed a few days later that…well, the young woman – now going by the name Hannah – isn’t actually his daughter.

The pair, who were seen kissing in a recent episode, are actually planning to clear out Liz’s bank account and rob Steve of his business, which would set them up for a cushy life.

The scheme continued in last night’s episode, with Hannah and Liz spending some time together.

The mother-and-faux-daughter duo were chatting over breakfast, and Liz gave her a necklace “to make up for all the missed birthdays and Christmas'”.

But when Hannah asked Liz to put the necklace around her neck, viewers noticed something fairly strange.

Earlier in the week, she had “proved” who she was with a birthmark behind her ear – the same one that Katie also had.

However, last night, eagle-eyed Coronation Street fans noticed the birthmark was nowhere to be seen – and took to social media to wonder why continuity wasn’t actually kept up.

Oh Liz! Wake up and smell the non-existant birth mark! #Corrie

— Andrew Rees (@AndrewRees14) September 14, 2018

#corrie how did liz not notice that her daughters kates birthmark had all of a sudden vanished lol !x😂🤣

— Sharon Gibbs (@SharonG40210896) September 14, 2018

https://twitter.com/Zero6Eleven/status/1040690139796791296

Watching #corrie on a delay but what happened to fake Katie's (Hannah's) birthmark? Like, we know it's fake cos she rubbed if off on Wednesday… but shouldn't she have reapplied, y'know, to keep the lie going?!

— Kimberley (@KimberleyW1983) September 14, 2018

https://twitter.com/BradfordMouse/status/1040670536119078912

#Corrie… the birthmark not visable tonight… continuity error, or deliberate? Surely someone that scheming wouldn't make such a mistake🤔?

— Kevin Field 💙 (@fieldy56) September 14, 2018