Cross-Department Collaboration: How to Get Product/Tech/Content Teams to Work with SEO?
Chapter 6: Practical Advanced Section · Question 101
SEO is never a one-person job. You need the tech team to change code, the content team to write copy, and the product team to leave SEO-friendly interfaces. But the reality is: other teams feel SEO isn't their KPI, and cooperation is extremely low. How do you break through?
Common collaboration pain points
| Team | Typical friction |
|---|---|
| Tech/Development | “This request can't be scheduled”, “changing the URL structure has too big an impact” |
| Content/Editorial | “I'll just write based on my own topic selection, keywords are too rigid” |
| Product/Operations | “New pages went live without notifying SEO, and only after launch did we find they weren't indexed” |
| Design | “Image compression will affect visual quality” |
| Management | “SEO's ROI isn't clear, put it lower in priority” |
The core idea for breaking through: lower the cost of others' cooperation
SEO implementation doesn't rely on reasoning, it relies onmaking cooperation easy：
1. Embed into processes rather than making ad-hoc requests
- Add SEO check items to the product launch Checklist (Title/H1/Canonical/sitemap）
- Build a "Keywordconfirmation" step into the content publishing process
- Reserve a fixed 10% of each tech iteration Sprint for SEO technical debt fixes (empirical suggestion, not a hard ratio)
2. Give templates rather than documents
- For the content team:content brief template(target keywords,search intent, reference articles, word count requirements all filled in)
- For the tech team:SEO Technical Specification Document(precise down to code snippets, so they don't have to figure it out themselves)
- To the product team:New Page SEO Checklist(one page, done in 5 minutes)
3. Let data speak
- Show the traffic and conversion data driven by SEO every month
- Note "because team XX collaborated on YY, traffic grew ZZ%" — give credit
- When problems arise, use data to pinpoint the scope of impact instead of abstractly saying "SEO isn't good"
RACI Matrix Example
| SEO Item | SEO Team | Technical | Content | Product |
|---|---|---|---|---|
| Keyword research | R/A | - | I | C |
| TDK writing | R/A | I | C | - |
| Technical optimization execution | A | R | - | I |
| Content creation | C | - | R/A | - |
| New page launch SEO review | R/A | C | C | I |
R=Responsible A=Accountable C=Consulted I=Informed
How to build trust quickly
- Help others solve their problems first: help the content team find topic inspiration (keyword data), help the technical team pinpoint performance bottlenecks (speed reports), help the product team review competitor pages — you give value first, they collaborate after
- Do a "quick win" showcase: find an optimization item with low collaboration cost and fast results (e.g., fix 10 404s, optimize 5 Titles), deliver results in 2 weeks, and let the team see that SEO really works
- Regular syncs instead of firefighting communication: a 15-minute standup or a briefing email each week, so relevant teams know what SEO is doing and what it needs
Practical recommendations
- Do this week: put together a "New Page Launch SEO Checklist" (one page), push it to product managers and tech leads, and require it to be included in the launch process
- Give the content team a 30-minute training session: no theory, just "how to write titles with high click-through rates, how to structure articles for good rankings", and hand over templates directly
- Produce a monthly "SEO Contribution Attribution Report": clearly mark which traffic growth is the result of which team's collaboration, and CC management — let the people who collaborate with SEO be seen
This article is part of the "100 Questions on Organic Marketing in Chinese" series.View the full table of contents →
