Best way to create SEO tasks for Developers [Free Template]

When working with clients or as in-house SEO, sooner or later, you’ll have to work and collaborate with other departments such as Content, Marketing and Development.

Each of those departments have their own objective to deal with and their own tasks.

So when you want to step into their currently workflow, and ask them to create time for your SEO tasks, it might not be the easiest thing.

I’m sure you’ve come across a post of two online, about SEOs & Developers working together.

The usual love & hate situation.

Or more precisely the disconnection and how these two teams don’t have much love for each other.

Is it all SEOs and Developers that don’t work well together?

No, I don’t think that is always the case but in my experience there’s two main things that can cause the disconnection between these two teams.

1. They don’t understand each others work
2. They don’t understand the importance and impact your implementation can have on the business

Let me explain.

They don’t understand each others work

While you know how to do your job well, and have an idea of what your task should be, that doesn’t mean that everyone else does too. So for that reason, you should try to explain what is it that you want them to do.

And ideally, you should speak with the devs and educate them a little on SEO and things like:

• Proper H-tag structure
• Hreflang tags
• Canonical
• Noindex
• Pagination
• and the list goes on

They don’t understand the importance

Once the know the basic and some more technical stuff, it’s really important to know the importance of the task, like:

• What is the outcome
• What problem will we fix
• How much money and/or time will it save us?

The solution

Finally, to the sweet bits.

In the beggining I explained how to write a SEO brief for Dev teams.

Because, in the end, we all work for the same goal.

Let’s make our work easier.

All of that is included in the Google doc template below.

Go ahead make a copy of the Google doc. If you have any questions, find me on LinkedIn.

My DMs are open.

Further explanation of MVP.

What does MVP stand for?

An MVP (Minimum Viable Product) is a version of a product with minimum features that are enough to be launched early in order to validate a product idea early in the product development cycle.

What are the 3 elements of MVP?

The three elements of a minimum viable product (MVP) are the core product, necessary features, and early adopters.

• The core product is the basic offering that addresses the problem or need that the MVP is intended to solve. This can be a product, service, or platform, and it is the foundation on which the MVP is built.
• Necessary features are those that are essential to the functioning and usefulness of the MVP. These are the minimum set of features that the MVP needs to have in order to be viable, and they are typically focused on solving the core problem or need that the MVP is intended to address.
• Early adopters are the initial group of users who try out the MVP and provide feedback on its performance and potential for improvement. These users are typically selected because they are representative of the target audience for the MVP, and their feedback is used to refine and improve the product before it is released to the wider market.

Photo by Daniel Tafjord on Unsplash