BrightonSEO_How to create harmony between SEOs & Developers
1 like540 views
The document discusses how to create harmony between SEOs and developers to get SEO tickets implemented. It outlines 7 steps: 1) speaking developers' language by learning HTML, CSS, and JavaScript, 2) knowing how new features are developed using Scrum frameworks, 3) knowing who works on projects, 4) asking for realistic changes, 5) knowing the tools developers use to communicate, 6) knowing preferred communication channels, and 7) publicly thanking developers. An example is provided of using these steps for a Core Web Vitals audit by checking prerequisites like the next sprint dates and constraints before submitting tickets through official and preferred channels.
BrightonSEO_How to create harmony between SEOs & Developers
- 1. — How to create harmony between SEOs & developers & get your SEO tickets implemented
- 2. Let me introduce myself – I work at Liip, a web & mobile development agency – #SEOnerdSwitzerland Meetup co-founder @moccandsayegh #brightonSEO | March 2021
- 3. Agenda 1. Devs & SEOs have common goals 2. The 7 steps to harmony 3. Recap of the steps @moccandsayegh #brightonSEO | March 2021
- 4. “Devs & SEOs have common goals”
- 5. SEOs & Devs have common goals SEOs E.g.: Performance Devs
- 6. If devs & SEOs have common goals, what can possibly go wrong? @moccandsayegh #brightonSEO | March 2021
- 7. Everything @moccandsayegh #brightonSEO | March 2021
- 8. 3 classic sentences... 1. “Since when do we make websites for robots?” 2. “I'm pretty sure I already know everything about SEO” 3. “SEOs just do shit with their black hats” @moccandsayegh #brightonSEO | March 2021
- 9. What were the problems? 1. Devs did not respect me. 2. I did not understand devs’ needs. 3. I was not communicating properly with them. @moccandsayegh #brightonSEO | March 2021
- 10. “The 7 steps to harmony”
- 12. You don’t need to be a dev to talk to devs You still need to know the basics of HTML, CSS & JS! Success:⭐⭐⭐⭐⭐ @moccandsayegh #brightonSEO | March 2021
- 13. Bonus: steps I took to learn more about programming 1. Read web.dev documentation 2. Read everything about crawling, indexing & JavaScript 3. Take a front end course
- 14. 2. Knowing how new features are developed
- 15. Most common framework - Scrum 1. Join Scrum Events where relevant. Such as daily. 2. Be aware of sprint dates. Success: ⭐⭐⭐
- 16. Bonus: how to learn more about Scrum Have a look at the Scrum Guide 2020 (only 12 pages) https://www.scrumguides.org/scru m-guide.html @moccandsayegh #brightonSEO | March 2021
- 17. 3. Knowing who works on a project
- 18. Know key people working on a project You need to know which devs & POs will work on the project to push fwd your tickets. Success: ⭐⭐⭐⭐⭐
- 19. 4. Asking for realistic changes
- 20. Adapt to companies’ constraints Speak with POs & devs to learn about resource limits, time constraints, infrastructure constraints. Success:⭐⭐⭐⭐⭐
- 21. 5. Knowing tools devs use to officially communicate
- 22. Common information devs need to do their Job Success:⭐⭐⭐⭐
- 23. Official communication channel The previous info needs to be updated in the tool that devs use to work with. @moccandsayegh #brightonSEO | March 2021
- 25. 6. Knowing preferred communication channels
- 26. Identify “non-official” communication channels Use official & non-official communication: Email, Slack, Jira, Phone, etc. Success:⭐⭐⭐⭐⭐
- 27. Bonus: write tickets with devs 1. Devs will be aware of the existence of your ticket 2. It will be written in a way that makes it clear to them Success:⭐⭐⭐⭐⭐
- 28. 7. Public thank yous are not complicated
- 29. Devs are not aliens, they also appreciate a ty! If you have a thank you channel - use it! If you have a group email - use it! Success: ⭐⭐
- 30. “Let’s use these steps to get tickets implemented”
- 31. Core Web Vitals audit example Pre-requirements: You have a report in which problems, observations, possible solutions, priorities & exemples are defined @moccandsayegh #brightonSEO | March 2021
- 32. Steps to success Do you know…? 1. Next Sprint 2. Team members 3. Constraints 4. Official comm. 5. Dev check 6. POs/Devs Channel @moccandsayegh #brightonSEO | March 2021