My introduction to Search Engine Optimization was at a firm wherein our clients gave us direct access to their sites via FTP and we made changes. There was no version control, just people like me making changes in Notepad or Dreamweaver and then uploading. When I transitioned into the network agency world, the idea of writing about SEO was a bit foreign to me.
Throughout my career, I have refined and defined many deliverables for SEO, Content Strategy, Measurement, and Development. In this episode of Rank and File, I share our approach to developing effective SEO deliverables.
Video Transcription
Intro
Greetings and salutations, folks. Welcome back to another edition of Rank and File. I’ll be your host for this week, Mike King. I am the managing director here at iPullRank, also founder, just in case you care. So today what I want to talk about is how to build an effective SEO deliverable.
So I’ve been doing this for 12 years now, and I’ve worked at a number of different agencies. I’ve seen a lot of other agencies work, and I was lucky to have been taught how to build out the deliverables that we work on in what I think is a very effective way. What I want to talk about today is how you can also do the same.
The Anatomy of a Strong SEO Deliverable
So here’s the anatomy of a strong SEO deliverable. The first thing is that we have an issue class, and everything is numbered. The issue class is numbered, the actual issues are numbered, your recommendations are numbered, so they can be referenced in other documents pretty easily. An issue class could be something like duplicate content, and under that will be the issues that are causing the duplicate content. But let me not skip the other things first.
Priority Scores
Then we have priority scores. It’s very important to have prioritization. We have three different measures for it, and we go from one to three. It’s very similar to how people prioritize things with respect to an agile methodology. Basically, we have benefit, ease, and readiness on a scale of one to three, and that way we can see at a glance how valuable it’s going to be for us to tackle these issues.
Overview
Then we give an overview, which is basically high-level context as to why this thing matters. I can tell somebody, “Hey, you have duplicate content,” but if they don’t understand how that can affect their SEO, then they’re not going to care. And the reality of it is, when you do deliverables like this, you don’t have control over everyone who’s going to see it. They may not be involved in your presentation meeting, so you have to give context so that anyone that picks it up really cares about why you’ve said this. So we give an overview of why it matters, and then we move into the issues.
Issues
In the issues, we’ll give you screenshots, we’ll give you descriptions, and we’ll also give you code snippets as to why these things are happening. That way you, as the client or the third party that’s working on this, will be able to recreate what we’re seeing.
Recommendations
Then we move into recommendations, and we say how to fix them. We give explicit instructions as to how to fix the issue. We give screenshots, or we might do mockups showing what it should look like, or we’ll make changes to code and then show you what that looks like so you can implement it.
Reference Documents
Then we also give you reference documents. Oftentimes we’ll create spreadsheets that reflect all the URLs where this stuff is happening, or we’ll give you direct links to tools that we might be using, and things of that nature.
Dos
So, some key things that you need to think about as far as dos and don’ts. One, you want to make sure you’re tailoring it to your client. You shouldn’t just have templates that you use over and over and never update to speak to the specific situation of your client. It’s fine to have descriptions that you use over and over, but with respect to what the issue is for the client, you want to be as specific as possible.
You also want to segment your crawl data. This is actually very important because different page types are governed by different mechanisms. If we’re talking about a product detail page versus a category page, they may have different templates and different code that’s constructing them. So if you segment your crawl data, it helps it be far more actionable to the people that are implementing it, because they know where to start.
You should also segment your keyword data, so you can get an understanding of the benefit of the recommendation based on what keywords it impacts, what type of search volume is available there, and what segments of your keywords are going to be the most valuable with respect to keyword difficulty and such.
And I’ve said this before, but I think it’s incredibly important for you to be as specific as possible, because if you give people generic recommendations, they’re not going to move on them. They’re not going to know what to do with them either.
Don’ts
As far as some don’ts: don’t just take screenshots of tools and say, “Here’s a deliverable.” That doesn’t really help anybody. Anybody can go to PageSpeed Insights and say, “Oh, I have a low page speed score and I should remove these things.” You need to be giving them more insight as to what to do, why it matters, and again, how to prioritize these different things that they’re doing.
And finally, don’t just link out to Google documentation or to other people’s blog posts. Your client didn’t hire you so you can go on the web and say, “Oh yeah, such and such said that you should be doing these things.” They’re hiring you because they want your interpretation of those things for their website.
That’s all I got for today. Looking forward to seeing you on the next edition of Rank and File.
Now over to you, what have you found to be effective in your SEO deliverables?
More from Rank & File
- How to write User Stories for SEO
- How to Prove SEO Performance Value to Non-SEOs
- How to do Projections for SEO