Indexing (JavaScript) comments and much more! | Search Off the Record podcast

TL;DR

Discussion on Google Search roles, website challenges, and JavaScript indexing.

Transcript

[MUSIC PLAYING] MARTIN: Welcome, everyone, to the next episode of "Search Off The Record," a podcast that we are trying out. Our plan is to talk a bit about what's happening at Google Search, how things work behind the scenes, and maybe have some fun along the way. My name is Martin Splitt. I'm a developer advocate at the Search Relations Team. And... Read More

Key Insights

• Gary discusses the challenges of building a website using WordPress, highlighting the need for custom plugins due to delays in third-party updates.
• John shares his journey to joining Google, emphasizing the transition from running a small company to working in a large corporation.
• The team reflects on their experiences with building content management systems (CMS) and the challenges of relying on third-party services.
• Martin explains the complexities of indexing JavaScript content and the importance of server-side rendering to ensure content visibility.
• The discussion highlights the potential pitfalls of relying on third-party content in JavaScript, such as comments, and the impact on indexing.
• Gary humorously notes the challenges of using JavaScript, suggesting a preference for server-side solutions to maintain control over content.
• The team debates the value of indexing comments, considering the quality and relevance of user-generated content for search visibility.
• Martin emphasizes the importance of understanding the limitations of client-side JavaScript, advocating for server-side solutions where feasible.

Questions & Answers

Q: What challenges does Gary face with his website project?

Gary is facing challenges with his WordPress website, primarily due to the need for custom plugins. He finds that third-party plugin developers may not implement new features quickly enough, leading him to consider creating custom solutions or even building a CMS from scratch.

Q: How did John Mueller join Google?

John Mueller joined Google after running a small software company. He became involved with Google through webmaster forums, helping with site maps and offering advice. An invitation to visit Google's Zurich office led to interviews, and he eventually decided to join the company, leaving his own business behind.

Q: What are the challenges of indexing JavaScript content?

Indexing JavaScript content poses challenges because client-side JavaScript can be unreliable for pulling in third-party data. Issues can arise from server load, API restrictions, or delays in data retrieval. Martin suggests server-side rendering as a solution to maintain control over content availability and indexing.

Q: Why is server-side rendering recommended for JavaScript content?

Server-side rendering is recommended because it allows website owners to control the environment in which data is fetched and rendered. This approach reduces dependency on client-side execution, ensuring that critical content is consistently available to search engines like Googlebot, improving indexing and visibility.

Q: What is the team's perspective on indexing comments?

The team believes that indexing comments depends on their quality and relevance. While valuable comments can enhance a site's search visibility, irrelevant or inappropriate comments may harm it. The positioning of comments on a page can also affect their impact on ranking, with central content typically prioritized.

Q: How does Martin view the role of JavaScript in web development?

Martin acknowledges JavaScript's role in web development but warns against over-reliance on client-side solutions. He highlights the creativity and sometimes misplaced ingenuity of developers and SEOs, advocating for server-side alternatives to ensure reliable content delivery and indexing.

Q: What humorous observation does Gary make about JavaScript?

Gary humorously suggests that JavaScript is 'evil,' reflecting his preference for avoiding it where possible. He jokes about taking notes on Martin's advice, summarizing it as 'do not use JavaScript,' although Martin clarifies that JavaScript can be useful when implemented correctly.

Q: What caution does the team offer regarding third-party content?

The team cautions against over-reliance on third-party content, particularly when using client-side JavaScript to fetch it. They recommend server-side solutions to maintain control and avoid issues such as API restrictions, server load, and potential content blocking by third parties.

Summary & Key Takeaways

• In this podcast episode, the team discusses various aspects of Google Search, including personal experiences and technical challenges. Gary provides an update on his website project, highlighting the difficulties of using WordPress and the need for custom plugins.

• John shares his journey to joining Google, reflecting on the transition from running a small software company to becoming part of a larger corporation. The conversation also touches on the team's experiences with building content management systems.

• Martin delves into the complexities of indexing JavaScript content, discussing the challenges of relying on third-party services and the importance of server-side rendering. The team debates the pros and cons of indexing user-generated content like comments.