SEOs & Developers: 7 Tips for Working Better Together & Getting Your Projects Implemented

SEOs sit at the intersection of many teams — marketing, editorial, PR, user experience, and engineering. That interdisciplinarity requires that we not only know about those other disciplines and how they affect the KPIs we care about. We also need to know how to communicate and collaborate with our friends in those fields.  

But that’s often easier said than done. 

I’m sure I’m not the only one whose redirect project didn’t get done before launch because it wasn’t a priority or who has waited years to finally get permission to update canonicals.   

When we’re short on time, have competing priorities, and often don’t even work in the same department, it can be difficult to come together to tackle critical SEO projects. 

SEOs and developers in particular need to work together because in many cases, although the SEO team will identify the issues and opportunities, it’s the engineering team that has to execute them.

So how can we work together to ensure our SEO projects get handled?

1. Consider their time and resources

Before you submit your first ticket, it’s important to take the time to consider your engineering team’s time and resources. 

Ask questions like:

• How many people are working on the team? 
• What other projects are they working on right now?
• What are their goals and priorities for the current development cycle? For the quarter?

Asking these types of questions will help orient you so that you’ll understand when to make requests and also how (e.g. submitting large projects vs. breaking the ask into smaller chunks). 

According to Uber’s SEO Lead Jackie Chu, engineering hours are notoriously scarce, so avoid asking for a huge project without considering their resources unless you want an instant “no.”

Or they ask for a HUGE project without buy-in or considering resourcing. That’s a good way to get an instant no. Eng hours are scarce so they have to prioritize. Getting months-long projects funded needs a track record and leadership buy-in IMO

— Jackie Chu (@jackiecchu) May 4, 2020

2. Know the difference between features and bugs

There are generally two sides to the SEO coin: proactively pursuing opportunities for growth and fixing issues that prevent growth. 

That’s the difference between features and bugs.

You’re almost guaranteed to get bugs fixed faster than features, which is why Jackie also recommends separating those projects out instead of bundling them.

And lastly (sorry SO many thoughts on this) things like server errors are generally considered bugs, not a feature. So you can get things like that prioritized a bit easier if you don’t bundle it with other features/new functionality

— Jackie Chu (@jackiecchu) May 4, 2020

What are some examples of bugs? Things like:

• Server errors
• Browser or device compatibility issues
• Very slow page speeds

And the like generally fall into that category.

3. Get leadership buy-in first

What motivates you to do what you do at work? It’s likely that you perform the tasks that you do because you’re trying to achieve an objective set by your boss or the wider leadership team at your organization.

It’s the same for your development team.

For that reason, it can be beneficial to make the business case for your SEO projects to senior leadership first. Then, once you have buy-in, make your request to the development team.

However, the exact process will depend heavily on your organizational setup. 

When I asked Digital Marketing Consultant Natalie Arney whether it was important if directives come from managers & execs, she said that it can depend on who typically assigns SEO tasks, whether there are project or product managers involved, and whether the SEO team is an agency or in-house.

When in-house I speak directly to Devs and set tickets and actions for them (both in house jobs I’ve had) and agency side, especially at iCrossing, we found if really helpful for an exec to go and work on site with the internal teams, including Dev, to ease communication.

— Nat (@__nca) May 5, 2020

Jackie Chu also added that the bigger the project, the more likely you’ll need executive buy-in. Smaller projects may not require that extra legwork.

4. Break silos

How effectively you’re able to work with your development team will depend a lot on how openly you’re able to communicate with them.

I’ve personally worked with organizations where the development team was an impenetrable fortress by design. The idea was to protect their time, but the unintended byproduct was that SEO requests never made it onto their radar.

In other cases, although SEO teams work alongside development teams, the department lines are rigid and don’t foster collaboration.

Some organizations have solved this problem by integrating SEO into their development teams.

Yep! I’m in the same department as them, rather than sitting in editorial

— Dan Morehead (@Danny11M) May 4, 2020

We talk about that in more detail in Where Does SEO Live? Tips for Structuring a Successful Enterprise SEO Team. 

If integrating SEO onto your engineering teams isn’t in the cards, then try meeting with your developers directly for brainstorming sessions rather than going through a middleman.

Very much so. The most beneficial part for me is being a programmer helps me talk to both marketing and eng without having to have a translator for either. Become technical and ask the devs for help. They will love it.

— Jody J. O’Donnell (@gimpslice) May 4, 2020

5. Learn to speak their language

It’s unlikely that you’ll get your requests implemented if the development team doesn’t understand what you’re asking. It’s also much easier to get requests approved if you frame them in a language your engineers will understand from the get-go.

For this reason, many SEOs who said they had good relationships with their development teams suggested putting the work in to understand the world devs live in and the language they speak.

For example, familiarize yourself with an agile development cycle, if that’s how your development team operates. Understand terms such as:

• Scrum
• Sprints
• Acceptance Testing 
• Epics / User Stories 
• Kanban 
• Product Owner 

You’ll not only want to know what terms like these mean, but also how they change the way you need to work with your engineering team. You can find a thorough list of agile development terms here. 

How you position your SEO asks is equally important. 

Cooper Hollmaier, SEO at REI, explained that he often frames these conversations as customer problems rather than SEO problems. That’s because the developer’s goal is most often going to be delivering the best experience for people. By framing SEO problems as customer problems, and describing search engine bots as another type of customer/visitor, it’ll be more obvious that SEOs and developers are working toward the same goal.

In my experience, yes. Because user stories are fundamental tools in agile software development, devs are already focused on delivering the best experience for people. When framing my SEO initiatives, I’m consistently thinking about Googlebot, Bingbot, etc., as another customer.

— Cooper Hollmaier (@CooperHollmaier) May 5, 2020

Others commented that they’ve had success reframing SEO issues as site health issues, another thing development teams will definitely care about.

It’s great because they appreciate SEO not just as a marketing channel, but from a site health perspective. We observe the same things and have a better shot at getting our shared needs met when we present these findings together.

— Daniela 🌺 LaFave (@daniela_lafave) May 4, 2020

When it comes to speaking the development team’s language, some SEOs even recommended learning how to code. When I asked whether coding skills were a “nice to have” or required, one product manager responded that certain skills definitely made his job easier.

In my case, “needs” were html, css, and js. Then I went down the rabbit hole with data so I took time to learn SQL. Made my job exponentially easier. I know the same will happen when I dive into PHP. Not “necessary” but always pays off in the end.

— 🟥 Diogo (@ordacowski) May 6, 2020

Someone else commented that a development background makes it easier for SEOs to understand what is and isn’t possible. This knowledge can make for requests that are better received by the development team, and therefore more likely to get implemented.

Dev background makes that much easier. Having a handle on what’s possible and what will create havoc makes those conversations a lot easier.

— Dr. David Sewell (@DrDavidRSewell) May 4, 2020

The minimum viable knowledge SEOs will need to have of web development is going to depend heavily on the organization and unique goals, but all SEOs should at least have the ability to speak to developers in a language they can understand. If you’re interested in learning more about that, Lily Ray has a great list of common SEO requests and what details web developers need from you in order to effectively execute them.

6. Describe, don’t prescribe

When you need development help for an SEO project, you tell your developer exactly what you need to be done, right? 

Not so fast.

It can feel natural to want to prescribe your desired solution to the person who needs to carry it out, but when it comes to developers, that method can backfire, causing tension.

It’s easier to work together when you they aren’t told what to do. Let them find the solution to the problem or work through it together. Often, I see SEOs telling their dev team what to do, which causes tension.

— Megan (@MSMondays) May 5, 2020

Instead, respect their expertise by describing the problem. Jayna Grassel, Director of Marketing Services at Bounteous, explains that this works because developers are natural troubleshooters.

Good! I’ve found bringing them a problem rather than a solution goes a long way. Counter to what you’re supposed to do with problems, but they’re natural troubleshooters and partnering with them goes a long way. Treat them like the experts they are.

— Jayna Grassel (@jaynagrassel) May 4, 2020

In addition to describing the problem, it can be helpful to describe your objective. Go beyond explaining the issue to explain why it’s a problem worth solving. Why is it important to you? To the company?

I’ve always made it a priority to have good relationships with eng. I think a big thing is, not prescribing the solutions + only describing what is your requirements/objective. Also being sure to follow up w/ results so you’re not wasting their time

— Jackie Chu (@jackiecchu) May 4, 2020

Cooper Hollmaier echoed that sentiment, saying that instead of prescribing the solution, he’ll describe the friction he’s trying to alleviate, and that tends to be much more effective.

Absolutely. I’m careful not to prescribe solutions but the friction I’m trying to aleviate. It’s important to me to be a partner that helps to develop SEO-friendly solutions to *customer* problems. When we’re all working towards the same goal the work becomes much easier.

— Cooper Hollmaier (@CooperHollmaier) May 4, 2020

So, want your SEO projects implemented? Trust your development team’s expertise and focus on describing what problem you’re trying to solve and why it’s important.

7. Keep the conversation going

You’ve effectively secured your development team’s time and gotten them to complete your project. Your job is done, right?

Not quite!

Your development team will want to know that the time and resources they invested in your project were well spent, which is why reporting can be so crucial, as Jackie Chu pointed out.

I’ve always made it a priority to have good relationships with eng. I think a big thing is, not prescribing the solutions + only describing what is your requirements/objective. Also being sure to follow up w/ results so you’re not wasting their time

— Jackie Chu (@jackiecchu) May 4, 2020

Sharing results with your development team can:

• Make it easier to get future SEO projects approved
• Validate your expertise
• Show your appreciation for their hard work 

For more on using reporting to improve the feedback loop with your engineering team, Ben Goodsell (Founder of Tight Ship Consulting) and Clara Li (Product Manager at GrubHub) wrote up a great list of tips you can use. 

Reporting isn’t the only way to keep the conversation going though. You can also improve relationships with your development team by creating avenues for discussion. Try setting up a Slack channel where you can discuss articles and news, or setting up recurring meetings to cover topics in-depth.

Talking outside of just projects worked wonders. We had a Slack channel where we would drop articles & discuss. We also had a weekly meeting where we’d cover a topic in-depth & share perspectives. When a client project came up, we were already on a similar page ~90% of the time.

— Andrew Prince (@AndrewPrince16) May 4, 2020

Even if you don’t sit in the same department as your development team, you can still create relationships and share best practices so that you’re already on the same page before a need comes up, making it much easier to get projects approved and implemented. 

There’s definitely a learning curve to working with developers if you’ve never done it before, but learning what motivates them and how they operate can be critical to getting your SEO projects implemented. 

Respect their expertise, know what drives them, and work on fostering positive two-way conversations for the best chance of success.