SEO and Development. How to Avoid Friction

SEO and Development. How to Avoid Friction 🔗 **Source:** [SEO and Development. How to Avoid Friction](https://www.youtube.com/watch?v=m-MmVN4ktu0) > [!note]+ Document Notes > tags: [seo, web-development, team-collaboration] > author: Montse Cano > source: WordCamp Europe 2024 > reference: https://www.youtube.com/watch?v=m-MmVN4ktu0 > date created: 2024-12-19 10:30 > > # 🏷️ Title: SEO and Development. How to Avoid Friction >  ## 🧰 Action Inbox - [H1] Establish regular communication workflows with development teams — improve project delivery #collaboration - [H2] Create feedback loops between SEO and engineering teams — prevent implementation bottlenecks #workflow - [H3] Document technical requirements in developer-friendly language — reduce misunderstandings #communication ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [SEO and Development. How to Avoid Friction](https://www.youtube.com/watch?v=m-MmVN4ktu0) - [Google Women Techmakers Program](https://www.womentechmakers.com/) ## 📝 Summary - Montse Cano addresses the communication friction between SEO professionals and development teams that often blocks project implementation - Communication barriers stem from cultural differences, technical language gaps, and lack of transparency between teams - The fourth and fifth industrial revolutions create opportunities for collaboration but also uncertainty and digital fragmentation - Successful collaboration requires transparency, compassion, regular workflows, and understanding different communication preferences - Both SEO and development teams work on the same end products (websites/mobile apps) and need each other's expertise to succeed ## 📖 Main Content Montse Cano, an SEO professional with 21 years of experience working with developers, explains how to overcome communication friction between SEO and development teams. She argues that despite the excitement around AI and technological advancement, implementation remains crucial - great SEO strategies are worthless if they can't be executed by development teams. The presentation occurs during the fourth industrial revolution (starting 2010-2011) and the emerging fifth industrial revolution (2020+) focused on collaboration. While these create opportunities, they also bring uncertainty, imposter syndrome, and digital fragmentation through restrictive regulations and the need to constantly learn new technologies. Common communication problems include developers feeling patronized by non-technical requests, SEOs unable to explain requirements clearly, and both teams sitting in organizational silos. Historical office layouts literally separated engineering teams from marketing/SEO teams, symbolizing the communication gap. Cano proposes a workflow: identify key contacts (business analysts, project managers), establish regular meetings, create feedback loops, and adapt communication styles to cultural preferences. She emphasizes that SEO professionals do build websites and mobile applications - they're not just "the coloring-in department" but technical specialists who need solid implementation for visibility, accessibility, and monetization. ## 🗒️ Notes #### ⏱️ [00:00](https://www.youtube.com/watch?v=m-MmVN4ktu0?t=0) — [H1] Speaker Introduction and Conference Context - Key idea: Montse Cano has 13+ years WordPress experience and 21+ years working with developers - Evidence: "Google women Tech makers program ambassador to help Inspire women to have a successful career in Tech" #### ⏱️ [03:15](https://www.youtube.com/watch?v=m-MmVN4ktu0?t=195) — [H2] The Implementation Problem - Key idea: Technical knowledge means nothing without successful implementation - Evidence: "no matter how well you know about artificial intelligence and generative AI...you will always have the need to implement your recommendations" #### ⏱️ [05:30](https://www.youtube.com/watch?v=m-MmVN4ktu0?t=330) — [H2] Communication Barriers and Patronization - Key idea: Teams often feel patronized when receiving requests they don't understand - Evidence: "somebody coming to you and say well I have no idea what I'm talking about please could you implement this and could you do it right now" #### ⏱️ [08:45](https://www.youtube.com/watch?v=m-MmVN4ktu0?t=525) — [H2] Historical Team Separation - Key idea: Physical office layouts reflected and reinforced communication silos - Evidence: "developers or engineering teams were sitting there...marketing and then seos were sitting there...we were not communicating" #### ⏱️ [12:00](https://www.youtube.com/watch?v=m-MmVN4ktu0?t=720) — [H1] Benefits of Improved Communication - Key idea: Better communication improves products, work environment, and internal reputation - Evidence: "Communication improves three things one the end product...then the working environment...and then lastly your internal internal reputation" #### ⏱️ [14:30](https://www.youtube.com/watch?v=m-MmVN4ktu0?t=870) — [H3] Cultural Communication Differences - Key idea: International teams require understanding of different communication preferences - Evidence: "some cultures...they like writing long emails...in some others they don't like writing emails at all" #### ⏱️ [16:45](https://www.youtube.com/watch?v=m-MmVN4ktu0?t=1005) — [H2] The Black Box Website Story - Key idea: Poor documentation and setup create fear and resistance to changes - Evidence: "I consider this website to be a black box because the the setup was terrible there was no documentation" #### ⏱️ [18:20](https://www.youtube.com/watch?v=m-MmVN4ktu0?t=1100) — [H1] Industrial Revolution Context - Key idea: We're living through the fourth and fifth industrial revolutions affecting all collaboration - Evidence: "fourth Industrial Revolution started in 2010 or 2011...2020 for some propelled the fifth Industrial Revolution which is all to do with collaboration" #### ⏱️ [22:15](https://www.youtube.com/watch?v=m-MmVN4ktu0?t=1335) — [H2] Digital Fragmentation Challenges - Key idea: Regulations and rapid technology changes create barriers to collaboration - Evidence: "regulation which is not making it possible for the free flow of data and talents" #### ⏱️ [25:40](https://www.youtube.com/watch?v=m-MmVN4ktu0?t=1540) — [H2] Industry Uncertainty and Reputation Issues - Key idea: AI developments are making clients question the value of SEO services - Evidence: "clients are becoming a lot more skeptical and lot more negative...is it worth it and also where is my traffic" #### ⏱️ [28:30](https://www.youtube.com/watch?v=m-MmVN4ktu0?t=1710) — [H2] Common Developer Frustrations - Key idea: Developers frequently receive unclear, urgent requests from non-technical colleagues - Evidence: "My 5-year-old neighbor can actually do this better than you...could you please do it now" #### ⏱️ [31:45](https://www.youtube.com/watch?v=m-MmVN4ktu0?t=1905) — [H1] What SEOs Need From Developers - Key idea: SEOs need solid technical implementation and advice on limitations - Evidence: "we need you to help us doing a fantastic solid technical implementation...we still need a fantastic implementation" #### ⏱️ [34:20](https://www.youtube.com/watch?v=m-MmVN4ktu0?t=2060) — [H2] Technical Collaboration Areas - Key idea: Uptime, accessibility, migrations, and security require both SEO and development expertise - Evidence: "website migrations particularly the the two riskiest examples servers um and S platforming we definitely need you there" #### ⏱️ [37:10](https://www.youtube.com/watch?v=m-MmVN4ktu0?t=2230) — [H1] Suggested Collaboration Workflow - Key idea: Establish clear contacts, regular meetings, and feedback loops - Evidence: "find out who you need to talk to...agree a workflow meaning maybe just regular meetings" #### ⏱️ [40:25](https://www.youtube.com/watch?v=m-MmVN4ktu0?t=2425) — [H2] Success Story Resolution - Key idea: Transparency and mutual support can overcome initial resistance - Evidence: "I actually proved to them...that nothing could actually break that easily...the developer ended up confiding in me" ## 📚 References - [WordCamp Europe 2024](https://europe.wordcamp.org/2024/) - [Google Women Techmakers](https://www.womentechmakers.com/) - [Atlassian Jira](https://www.atlassian.com/software/jira) ## 🗣️ Paraphrase - SEO professionals and developers often struggle to communicate effectively, leading to failed project implementations despite good strategies and technical skills - The current industrial revolution context creates both collaboration opportunities and uncertainty that can worsen communication problems between technical teams - Successful collaboration requires understanding cultural differences, establishing regular workflows, and recognizing that both SEO and development work toward the same goal of building successful websites and applications ## 📰 Newsletter **Breaking Down Silos: Why SEO and Development Teams Need Each Other** Montse Cano's WordCamp Europe presentation tackles a persistent challenge in WordPress development: the communication gap between SEO specialists and developers. With AI changing the digital landscape, solid technical implementation remains crucial for website success. **Key insight**: Both teams work on the same end products - websites and mobile applications that need to be visible, accessible, and profitable. SEOs aren't just "the coloring-in department" but technical specialists who understand how sites should function for search engines and users. **Practical approach**: Establish regular workflows, identify key contacts (business analysts, project managers), and adapt communication styles to team preferences. Some cultures prefer detailed emails, others need face-to-face conversations. **Common collaboration areas**: Website migrations, accessibility implementation, server management, cybersecurity, and platform integrations all require both SEO knowledge and development expertise. The bottom line: In an era of AI uncertainty, teams that collaborate effectively will build better products and advance their careers. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### DevRel - Developer advocacy: Create SEO-developer collaboration workshops for conferences - Education: Develop curriculum on technical SEO for developers and development basics for SEOs - Developer experience: Improve WordPress documentation for SEO implementation patterns - Community management: Facilitate cross-team discussions in WordPress forums #### WordPress - Core: Prioritize SEO-friendly defaults in WordPress core development - Documentation: Create technical SEO implementation guides for developers - Community: Develop meetup formats that bring together SEO and development professionals - Training: Build lesson plans for cross-functional team collaboration #### Community - Maintainers: Develop governance templates that include both SEO and development perspectives - Contributors: Create first-issue programs that require both SEO and development skills - Ecosystem: Coordinate between SEO plugin developers and theme developers ## 🧪 Hypotheses - Teams with regular SEO-developer communication workflows deliver projects faster and with fewer post-launch issues - Organizations that physically or virtually co-locate SEO and development teams see better collaboration outcomes - Cultural communication training reduces project friction between international SEO and development teams - WordPress sites with SEO-developer collaboration from the start achieve better search performance than those with retrofitted SEO ### 📊 Methodology - Survey WordPress agencies to compare project delivery times and post-launch issues between teams with formal SEO-developer workflows versus ad-hoc communication - A/B test different communication formats (email, meetings, documentation) with international WordPress teams - Analyze search performance data from WordPress sites built with integrated SEO-developer teams versus traditional handoff approaches ### ❓ Questions - What specific WordPress development practices most commonly conflict with SEO requirements? - How do different international cultures within the WordPress community prefer to structure technical communication? - What metrics best measure the success of SEO-developer collaboration in WordPress projects? ### 🔮 Future Research - Impact of AI tools on SEO-developer collaboration patterns in WordPress development - Effectiveness of different project management methodologies for cross-functional WordPress teams - Role of technical documentation quality in reducing SEO-developer friction ### 💡 Implications - Practice: WordPress developers need SEO knowledge as a core competency, not an afterthought - Policy: Organizations should structure teams to encourage SEO-developer collaboration rather than maintaining silos - Education: WordPress training programs should include cross-functional team communication skills - Funding: Investment in collaboration tools and processes pays off in faster project delivery and better outcomes ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade (Flesch-Kincaid Grade Level) #### 👀 Visual learners - Present: Speaker slides, office layout diagrams - Improve: Process flowcharts, before/after collaboration examples, team structure diagrams #### 🔊 Aural learners - Present: Conference presentation format with Q&A - Improve: Podcast version of key concepts, audio case studies #### 🗣️ Verbal learners - Present: Clear definitions of SEO vs development roles, detailed examples - Improve: Glossary of technical terms, metaphors for complex concepts #### 🧩 Kinesthetic learners - Present: Real-world case studies and workflows - Improve: Interactive collaboration exercises, hands-on workshop formats #### 🧠 Logical learners - Present: Step-by-step workflow, cause-and-effect relationships - Improve: Decision trees for communication choices, metrics for success #### 🧑‍🤝‍🧑 Social learners - Present: Conference Q&A format, team collaboration focus - Improve: Group discussion guides, peer collaboration exercises #### 🧘‍♀️ Solitary learners - Present: Individual reflection on past collaboration experiences - Improve: Self-assessment tools, personal action planning templates #### 🌿 Naturalistic learners - Present: Industrial revolution context, ecosystem thinking - Improve: Organizational ecosystem maps, evolution of collaboration patterns ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure, descriptive content - Improve: Alt text for presentation slides, transcript formatting #### Keyboard navigation - Present: Standard video player controls - Improve: Chapter navigation, searchable transcript #### Contrast and readability - Present: High contrast presentation slides - Improve: Larger font sizes in slides, color-blind friendly palette #### Media and captions - Present: Full transcript provided - Improve: Professional captions with speaker identification ### 🌍 DEIB Assessment #### Cultural breadth - Present: Discussion of international communication differences, multiple cultural examples - Improve: Specific examples from diverse WordPress communities globally #### Inclusive language - Present: Gender-neutral terms, avoids technical jargon without explanation - Improve: More inclusive examples beyond traditional corporate structures #### Neurodiversity support - Present: Clear structure, consistent format - Improve: Visual aids for different processing styles #### Representation - Present: Female speaker in male-dominated field, cultural diversity emphasis - Improve: Examples from developers and SEOs of varied backgrounds ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Clear cause-effect relationships between communication and project success - Inductive strength: Multiple case studies support general principles - Causal reasoning: Links communication barriers to specific project failures - Analogical strength: Industrial revolution context effectively illustrates current changes #### Fallacies - Hasty generalization: Some broad claims about developer/SEO relationships based on limited examples - Appeal to authority: Google Women Techmakers credential used without direct relevance to communication skills #### Tone of voice - Overall tone: Professional but conversational, includes humor and personal anecdotes to maintain engagement ### 🛡️