LinkedIn/WordPress Application Domain Mapping Problem

Screenshot of LinkedIn WordPress application, broken
The LinkedIn WordPress application picking up old content from the wrong place.

We had an interesting one today. The LinkedIn WordPress application is a widget that allows you to have your latest WordPress posts on your site. The references within it all relate to – however, I knew it worked full well with self-hosted sites as well as I use the application.

So I was a bit bemused when a client called today to say that they were only getting old posts in LinkedIn. My initial reaction is to consider this a LinkedIn/Automattic problem because they’re the ones that supply the application, not us. However, a support contract is a support contract.

Looking a bit more deeply I could confirm what was happening.  If you put into the field it got changed to – how peculiar.

Domain Mapping

So as is my usual approach to this, I wondered what it could be that could relate the domain to the old blog they had on – and I could think of only one possibility.

When we migrate a site to the first stage is to get the domain and map it on the original blog.  We then take leave the site running like that for a month before then pointing the domain at the site’s new server.  It’s a simple way to maintain your link juice, and is very effective.

But what happens when you use the LinkedIn WordPress app is that for some reason it looks up the domain on and uses the URL rather than the mapped domain.  I guess there are reasons for this, but if you’ve migrated your blog from this could be mighty confusing.

The answer is to delete the domain mapping extra.  You can’t just change your primary domain – you have to delete the domain you’re using for the live site.  Otherwise the application won’t work correctly.  This may well cause us some future migration headaches for heavy LinkedIn users of going self-hosted.

David Coveney

David Coveney

Dave has been working in software development since 1988, starting with payroll development and then ERP consultancy for large corporates. He is a keen traveller, photographer and motorsport enthusiast, but now puts family first as he’s massively in love with his two little boys. Dave is still an early adopter. He was connected to the internet from his bedroom, way back in the eighties, had a personal website by 1994, was into the connected house in the late '90s, a smartphone by 2002, and a was the first in the office with a fitness tracker.

7 responses to “LinkedIn/WordPress Application Domain Mapping Problem

  1. Hi David, your post describes my problem exactly. Yes, I migrated from .com to .org. Yes, I purchased an extra for mapping my domain on Yes, Linkedin erroneously points back to the old .com blog.

    But I can somehow not figure out how to delete the .com domain mapping extra …..

    What are the exact steps I need to take ? Any help extremely appreciated – I am going nuts here.

    1. If I remember rightly you have to sign into the back-end of that domain and delete or stop the addon for the domain. Sadly it’s been a while, so I can’t memorise the route and I’m a bit stretched just right now so can’t help further. Good luck! You can always ask in the forums – they may be able to help.

Leave a Reply to Maarten Susan Cancel reply

Your email address will not be published. Required fields are marked *