We love digital - Call
03332 207 677 and say hello - Mon - Fri, 9am - 5pm
Call 03332 207 677
Unlike 08 numbers, 03 numbers cost the same to call as geographic landline numbers (starting 01 and 02), even from a mobile phone. They are also normally included in your inclusive call minutes. Please note we may record some calls.
I’ve been working as an SEO for a number of years now and one thing I have come to learn is, more often than not SEOs and Developers don’t get along.
Now of course I appreciate that this is an incredibly sweeping statement, I for one have great working relationships with a number of developers, but then again I have some extremely difficult ones too …
Having attended various industry conferences and being part of a circle of friends involved in the industry, I have also come to realise I am not alone in this thinking or experience either – which when you think about it is crazy, why should two people who have a vested interest in the success of a website not get along?
Whenever I start a new SEO project here at Koozai one of the things I try to prioritise is getting hold of the developer and striking up a relationship. Personally I find the sooner I can speak to this person, the sooner I can start getting things done and start seeing results for my client. More often than not a client will come to us looking for SEO in the belief that, quite rightly, it will help increase awareness of their site and thus drive sales for their business.
SEO is a results based business and if I can’t demonstrate results to my client after a period of time, then rightly questions should be asked. Therefore developing a good relationship with a client’s developer is crucial to the progression of an account here at Koozai.
So that all important first call with the developer …
Well after introducing myself to the developer and telling them why I am calling, broadly speaking their reactions tend to be anyone of the following:
Now as I said, developing this relationship in my opinion can make or break an account. Selecting an appropriate response will help you win this person over early on, making it as easy as possible to get stuff done on the account.
With this in mind, I have put together my thoughts on how I might respond to each of the above reactions – some of you might agree, others not. Either way, I’d love hear from the SEO community out there on how you might respond in the comments section at the end of the post.
There’s nothing wrong with the site – it looks great!
When I hear this I think of two things, one – there’s is lack of appreciation of SEO and two – this person is most probably protective of the site and has put a lot of time and effort into its development. In this scenario, I often find the best course of action is to be firm yet tactful; in any case, who am I to go an pull apart someone’s hard work for the sake of something someone has very little appreciation?
Reaffirming what SEO is, what it can do for the site and how this can help the developer often helps. For example, if a client is suddenly getting more visits and revenue then they are far less likely to abandon their site. If anything, the client is more likely to develop the site further, which most probably means more work for everyone in the long run!
I often like to highlight that, as an SEO, it’s my responsibility to drive more people to the site whilst it’s the developer’s to ensure that once people are there, the site is in order. Clearly defining each other’s role early on often negates any future misunderstandings and helps get the project off the ground on a solid footing.
SEO is a waste of time
Well this is a difficult one – if your primary role is SEO and that person’s opinion of it is that it’s a waste of time, then the potential for friction early on is quite high. In my experience it’s quite easy to spend your time debating the value of SEO but when you think about it, it’s not your job to sell to this person. The reason the two of you are even talking is because the CLIENT already appreciates the value of SEO and that’s the important thing – the client.
If you find yourself in this situation then I would recommend the best course of action is to remind the developer of the client, that you’re here because the client wants you here and believes in SEO and wants to use it to help drive visits to the site. As the developer is employed by the client to maintain the site, then surely they have a responsibility to carry out the client’s wishes?
Personally I find this the most difficult relationship to develop, but then again it’s incredibly rewarding to see great results on an account too!
Sure here’s full FTP/CMS access – do what you want
Whilst I am not the most techie of SEOs getting full access is fantastic as it means I can get a whole host of things done quickly. These are also the accounts I find I get the quickest and most impressive results. Whilst there is a temptation to just get on with things and forget about the developer, I would alway make an effort to involve them as much as possible. Firstly if that person is employed to maintain the site, it’s only common sense to involve that person and most often than not, I have found I have learnt a great deal from working with developers so running things but them first can hardly harm the account – if anything you might learn how to do things more productively on the site.
Great an SEO – what can we learn from this!?
At first glance this is a promising situation to be in, here’s someone who wants to work with you. Then again it’s important to remember your role on the account is not to educate someone on how to do SEO, but rather actually do it! Spending call after call, email after email explaining why a duplicate content issue is holding a site back or why we need to change the title tag on the home page can eat up precious time on your account. Don’t get me wrong, I have no problem sharing a bit of knowledge with someone and helping them out; but at the end of the day I have to work in the best interest of the client and use their time productively.
If you find yourself in this situation, then the best course of action I find is to either request FTP/CMS access yourself so you can get on with things and keep them in the loop, or point them in the right direction as to where you get your information and advice, like industry blogs and so on. Be nice, be helpful – at one time you probably asked someone for advice on SEO – but also be mindful you’re there to work for the client, not educate.
I’ve been doing SEO on this account for years!
Another tough situation – how do you strike up a relationship with someone whose role you’ve just taken over!? Not a great situation I know, but then again you didn’t make the decision to change suppliers, it was the client. So in this situation I tend to not even approach the fact they did SEO in the past, if they bring it up that’s fine but I would never go along the lines of justifying why something is important or not or why something is outdated or not. More often than not it will just lead to a load of admin that you don’t need and it’s not in the best interests of the account or the client.
Find yourself in this situation? Well if this is the case then I wouldn’t recommend asking for FTP/CMS access straight away, you’ve just told someone you’re going to be doing their job. If they offer it then great but requesting it from the get go, I personally think will only create more hostility to the work you’re trying to do for the client. In my experience, the best course of action to take is to just be clear about what needs to be done. No explanation needed as you’ve been employed by the client anyway and you’ll have a reason for requesting the work anyway. You’ll probably find your work being called into question but at the end of the day you can spend your time justifying your work, or you can get on and actually doing stuff that can get results.
What’s a robots.txt file?
Finally you might have a call with someone who knows less about web development than you do. If this is the case, then the best course of action I would say is to request FTP/CMS access from the get go and get on with stuff as best you can within your abilities and experience. If you come across a piece of development work that is outside the scope of your work with the client or you do not feel comfortable doing it, then all you can do is feed back to the client and developer that this is needed to progress the work. Putting it back on to the developer is a good course of action, as in reality that’s what they’re employed to do, if they cannot do it then in reality that’s a conversation for the client and developer and in my opinion, not you.
Well there’s a couple of the situations I have found myself in over the years at Koozai and hopefully I’ve demonstrated not only the importance of a good relationship with your client’s developer, but also how you might want to deal with some of the more common scenarios.
I trust I’ve not been patronising to all you developers out there and hopefully you can see the post has had some good intentions. If an SEO and developer can work together on an account, most of the time in the end everyone wins, the SEO, the developer and most importantly the CLIENT!!
For any developers out there reading this, I of course have only given one side of the arguement being an SEO; therefore, I would love to here from you below with regard to your expereinces being from the other side of the situation and how you recommend dealing with things in this area.
Smiley yellow emoticon via BigStock
Search engine technology is evolving, and so is the digital marketing industry. The more experienced professionals amongst you may remember the days of gleefully stuffing keywords into your copy to boost your rankings, blindly spamming strangers to join your email lists and easily securing media coverage for your thinly veiled advertisements.
Site speed is an important area of website optimisation that people working in the world of Search Engine Optimisation are becoming increasingly concerned about.