Why is SEO documentation so confusing?

TL;DR

SEO documentation causes confusion due to outdated and unclear guidelines.

Transcript

MARTIN SPLITT: Why do SEOs give strange recommendations to us developers sometimes? MICHAEL KING: Why can't the Google documentation be up to date? MARTIN SPLITT: Why won't all SEOs use their tools and documentation properly? MICHAEL KING: Why is the Google documentation written so strangely? [MUSIC PLAYING] MARTIN SPLITT: Hello, and welcome back t... Read More

Key Insights

• SEO recommendations often seem confusing to developers due to differing levels of technical understanding and tool-generated reports that lack context.
• Tools used in SEO can generate outdated or incorrect recommendations, as they often follow generic best practices without considering specific business needs.
• SEO documentation may not always align with the latest practices or Google's internal changes, leading to discrepancies in implementation.
• The documentation is often written for a broad audience, which can lead to misunderstandings among advanced users or those with specific needs.
• Feedback on documentation is crucial for improvement, but it can be challenging to address every edge case or specific user need.
• Trust issues between SEOs and developers stem from differing backgrounds and perspectives, often exacerbated by outdated or vague documentation.
• Collaboration and open communication between SEOs and developers can help bridge the gap, allowing for better understanding and implementation of SEO practices.
• SEOs and developers should focus on learning from each other and working together to achieve the common goal of improving website performance.

Questions & Answers

Q: Why do SEO tools generate outdated recommendations?

SEO tools often follow generic best practices that may not account for specific business needs or the latest changes in SEO practices. These tools may not be updated frequently enough to reflect the most current guidelines or Google's internal changes, leading to outdated or incorrect recommendations.

Q: How does documentation contribute to misunderstandings between SEOs and developers?

Documentation is often written for a broad audience, which can lead to misunderstandings among advanced users or those with specific needs. The language may be too generic, and the guidelines may not always align with the latest practices, causing discrepancies in implementation and contributing to mistrust between SEOs and developers.

Q: What role does feedback play in improving SEO documentation?

Feedback is crucial for improving SEO documentation, as it helps identify areas that are unclear or outdated. While it can be challenging to address every edge case or specific user need, constructive feedback allows documentation teams to refine guidelines and make them more relevant and useful for a wider audience.

Q: How can SEOs and developers build trust and work together effectively?

SEOs and developers can build trust by focusing on open communication and collaboration. They should aim to understand each other's perspectives and work together to solve problems. Developers should be open to SEO insights, while SEOs should be willing to admit when they don't know something and work with developers to find solutions.

Q: What challenges do SEOs face when making recommendations based on documentation?

SEOs face challenges when making recommendations based on documentation that may be outdated or not aligned with current practices. This can lead to disagreements with developers who rely on documentation as a source of truth. SEOs must navigate these discrepancies and find ways to justify their recommendations effectively.

Q: Why is it important for SEO tools to consider business context?

SEO tools need to consider business context because generic best practices may not apply to every situation. A tool might flag an issue based on a standard guideline, but that issue might be necessary for the specific business model or strategy. Understanding the context helps prioritize actions that truly benefit the business.

Q: How can SEOs ensure their recommendations are taken seriously by developers?

SEOs can ensure their recommendations are taken seriously by providing clear, evidence-based justifications and demonstrating an understanding of the technical aspects. Building a collaborative relationship with developers, where both parties respect each other's expertise, can also help in making SEO recommendations more credible and actionable.

Q: What improvements can be made to SEO documentation to better serve its audience?

SEO documentation can be improved by clearly defining its target audience and providing sections tailored to different user levels, such as beginners and advanced users. Regular updates to reflect the latest SEO practices and more detailed explanations of complex concepts can also help users better understand and implement the guidelines.

Summary & Key Takeaways

• SEO documentation often causes confusion due to outdated guidelines and a lack of clarity, leading to mistrust between SEOs and developers. Tools generate reports based on generic best practices, which may not apply to specific business contexts, further complicating the issue.

• The documentation aims to address a broad audience, which can result in misunderstandings for more advanced users. Feedback is essential for improvement, but it's challenging to address all user needs. Trust issues arise from different backgrounds and perspectives.

• Collaboration and open communication between SEOs and developers are crucial for bridging gaps and achieving better website performance. SEOs and developers should focus on learning from each other and working together to overcome challenges posed by documentation and tool limitations.