Are you challenged as an SEO with getting developers to implement your recommendations?
Then this SEO tip might be for you.
Hello. Thanks for listening to SEO tips today.
I watched a great Deepcrawl event related to building SEO & Developer Relationships with some tips I wanted to share. A link to the Full recap is here.
These are the bits I thought were most impactful:
- When you talk to the developers, call your SEO recommendations “improvements or opportunities” and they’ll be more open to helping.
- Allocate a day where both sides (SEOs and developers) spend some time learning one another’s processes, priorities, and roadblocks. Try to *not* send long reports of requirements, instead split them into separate requests (current behavior/expected behavior) and ideally load them into their ticketing system. And as SEOs we need to learn how to write user-stories.
- Page speed improvements are tough to fix after the fact. It’s best to instead work on making sure new pages are built to hit page speed requirements.
- Use a framework and get buy-in from the dev team on the framework you’re using. Here’s a great one for larger sites.
- Use competitive data to explain the business impact of a change to the development team to see if that helps to get it bumped in the queue.
- Try to overlay revenue and traffic data on top of your SEO tech fixes to prioritize just those key pages.
- Never throw an individual under the bus. Ideally SEOs are able to take full responsibility as we should be involved in checking and validate development pushes. Also keep in mind that it’s normal to have errors during projects.
So that’s your tip for today – think through your developer interactions and try to work in these adjustments.
Thanks for listening. Come back tomorrow for another SEO tip.