Post by account_disabled on Jan 27, 2024 0:32:18 GMT -8
In other words, no one understood what they did and I could tell they didn’t understand/ know what marketing and digital truly do either.” Part of our job, then, as SEOs, is to break down those walls and work towards understanding each other, rather than each of us assuming what we’re asking for or requesting to be . Peter Mindenhall on X Peter Mindenhall on X Going in with a desired end state should include examples and thoroughness. If you want a specific schema markup implemented, show what the end state of that schema should look like for your website.
If you know there’s a weird DB to Data requirement, take time to explain the why behind it. Being curious and going in with a desired end state means being an active listener and not dictating to your team members. Unless you are in the code day-in-day-out as much as they are (and few, if any, SEOs can say that), they know the code better than you. Respect that. And once you’re able to work together and get good things done, share it with the metrics that matter to your business – revenue or otherwise. Speak nicely about them when they aren’t a part of the conversation and when they are.
Dig deeper: Learn to think like an SEO developer Get the daily newsletter search marketers rely on. Business email address Get Search Engine Land in your inbox. See terms. Building trust when working with developers If the new bare minimum I described above is still leaving you short when it comes to mutual respect and the ability to get stuff done with developers, here are a few less common ways to consider building up that rapport with developers. Start with an ‘SEO task’ that shares their KPIs This is an important one because it serves multiple purposes.
