JavaScript SEO office hours, December 9th, 2020

TL;DR

Discussion on JavaScript SEO and Googlebot behavior.

Transcript

MARTIN SPLITT: Hello, and welcome to the JavaScript SEO Office Hours today, December 9, 2020. I don't know. Today has been the longest month of the year, or the longest year of the month. I'm not sure. Great to have you all here. We will go through some of the submitted questions from YouTube, and then I'll hand over the word to the audience. If yo... Read More

Key Insights

• The session provides insights into handling JavaScript SEO queries, focusing on page speed issues related to Google AdSense and the use of WP Rocket.
• Martin Splitt discusses the challenges of lazy loading images and the role of the intersection observer in managing viewport sizes for Googlebot.
• Googlebot's viewport can expand vertically to accommodate content, but horizontal expansion is not typically used.
• Content visibility issues on different devices can arise due to viewport size thresholds, highlighting the need for responsive design.
• The no archive tag's behavior with JavaScript is discussed, with emphasis on potential issues due to rendering stages.
• The cache service in Google Search might not always reflect JavaScript-rendered versions due to its early-stage data extraction.
• Publishers may have specific reasons for avoiding cached versions of their pages, impacting their SEO strategies.
• The office hours serve as a platform for addressing specific technical SEO concerns, providing real-time solutions and insights.

Questions & Answers

Q: What is the primary focus of the JavaScript SEO Office Hours?

The JavaScript SEO Office Hours primarily focus on addressing questions and concerns related to JavaScript SEO, including issues such as page speed, Google AdSense integration, and the behavior of Googlebot. The session provides a platform for participants to seek guidance and solutions for their specific SEO challenges.

Q: How does Googlebot handle viewport size for rendering pages?

Googlebot uses a dynamically expanding viewport to render pages, particularly in the vertical direction to accommodate content. However, horizontal expansion is not typically used. The viewport can grow as needed, but there are limits due to memory constraints. It's important to ensure that all essential content is accessible without relying on specific viewport dimensions.

Q: What challenges are associated with lazy loading and intersection observers?

Lazy loading and intersection observers present challenges in ensuring that all content is indexed by Googlebot. If content is loaded outside of the viewport used by Googlebot, it may not be indexed. Therefore, it's crucial to implement lazy loading in a way that allows content to be accessed through specific URLs or paginated versions to ensure visibility to Googlebot.

Q: Why might publishers want to avoid having their pages cached?

Publishers might want to avoid having their pages cached to prevent unauthorized access to their content when their site is down. Additionally, caching can impact the control publishers have over the presentation of their content, which is crucial for maintaining their brand and user experience.

Q: What is the significance of the no archive tag in SEO?

The no archive tag is used to prevent Google from storing a cached version of a page. This can be important for publishers who want to control how their content is accessed and presented. However, when implemented via JavaScript, the tag's effectiveness can be inconsistent due to the stage at which Google extracts data for caching.

Q: How does responsive design impact SEO and content visibility?

Responsive design is crucial for ensuring that content is visible and accessible across different devices and screen sizes. If content is only loaded or displayed at specific viewport sizes, it may not be indexed by Googlebot, which can impact SEO. Ensuring that all important content is present in the DOM regardless of screen size is essential.

Q: What role do intersection observers play in managing content visibility?

Intersection observers are used to manage content visibility by detecting when an element enters the viewport. This is particularly useful for lazy loading images. However, if the page is much taller than the viewport used by Googlebot, content not included in the viewport may be ignored, highlighting the need for strategic implementation.

Q: What are the potential issues with Google Search's cache service?

Google Search's cache service may not always reflect the JavaScript-rendered version of a page due to its early-stage data extraction. This can lead to inconsistencies in how content is cached and presented, which can impact SEO strategies. Relying on server-side rendering for important meta tags can mitigate these issues.

Summary & Key Takeaways

• During the JavaScript SEO Office Hours, Martin Splitt addresses various questions related to JavaScript SEO, including issues with page speed and Google AdSense. The session provides insights into handling these challenges effectively.

• The discussion highlights the importance of understanding Googlebot's viewport behavior, particularly in relation to lazy loading and the use of intersection observers for managing content visibility.

• Participants gain valuable knowledge on handling responsive design challenges, the implications of the no archive tag with JavaScript, and the intricacies of Google's cache service in relation to SEO.