By Eric Enge
You’ve come up with some fantastic SEO insight for your website. You know that it’s going to double your organic search traffic, and you are stoked! You bring the idea to the web dev project priority meeting and present it with a great deal of excitement, certain that it will be put to the top of the priority stack — after all, it’s a killer idea!
Then it happens. The CTO questions your competence. He or she simply believes that SEO does not work that way: “That’s stupid! Google isn’t stupid, so you must be wrong, and you are stupid.” Your jaw drops, and you don’t know what to do. The project is tabled, you have to regroup. Now, you have a much more difficult sales effort in front of you.
How can you avoid this scenario? How can you stop it from happening in the first place? The basic formula is simple:
- Understand the technical aspects of SEO better than anyone else in the room.
- Realize that you know more than anyone else as you present your plan, and let that confidence show in the presentation.
- Be able to back up your plan (and your confidence level) when the challenges arise.
In today’s column, I will focus on helping you succeed in getting your dev team to buy into those critical projects. Note that similar problems can happen with other people, as well, such as the PR team, the social media team, the CEO, etc. – but for today, the dev team will be the focus.
I have had many arguments over the years with various developers, dev managers and CTOs on a variety of different points. Three of the most common ones are: