The Google Search team has made a number of relatively minor changes to their JavaScript documentation and has also removed much of the dynamic rendering documentation as it has been deprecated as a workaround for many years.
I’ll show you what’s changed:
At the Understand the basics of JavaScript SEO – if you compare it with the previous version:
Old:
Googlebot queues pages for both crawling and rendering. It’s not immediately obvious when a page is waiting to be crawled and when it’s waiting to be rendered.
When Googlebot gets a crawl queue URL by making an HTTP request, it first checks if you allow crawling. Googlebot reads the robots.txt file. If you mark the URL as disallowed, then Googlebot skips making an HTTP request to that URL and skips the URL.
Reviewed:
Googlebot queues pages for both crawling and rendering. It’s not immediately obvious when a page is waiting to be crawled and when it’s waiting to be rendered. When Googlebot gets a crawl queue URL by making an HTTP request, it first checks if you allow crawling. Googlebot reads the robots.txt file. If you mark the URL as disallowed, then Googlebot skips making an HTTP request to that URL and skips the URL. Google Search will not display JavaScript from blocked files or blocked pages.
Old:
Describe your page with unique titles and snippets
Unique, descriptive title elements and helpful meta descriptions help users quickly identify the best result for their goal, and we explain what makes a good title element and meta descriptions in our guidelines.
You can use JavaScript to set or change the meta description as well as the title element.
Google Search may display a different title link depending on the user’s query. This happens when the title or description has little relevance to the page’s content, or when we find alternatives to the page that better match the search query. Learn more about why the search result title may differ from the page title element.
Reviewed:
Describe your page with unique titles and snippets
Unique, descriptive title elements and meta descriptions help users quickly identify the best result for their target. You can use JavaScript to set or change the meta description as well as the title element.
Old:
Use the History API instead of fragments
Google can only crawl your link if it is an HTML element with an href attribute.
Reviewed:
Use the History API instead of fragments
Google can only discover your links if they are HTML elements with an href attribute.
At the Fix JavaScript issues related to search here’s what’s changed:
Old:
Use Search Console to monitor Googlebot and WRS activity and feedback on your site.
Reviewed:
Use the Google Search Console crawl statistics report to monitor Googlebot and WRS activity and comments on your site.
At the Fix lazy loaded content page, here’s what changed:
Old:
For more information, see the Web Basics guide to lazy loading images and videos.
Reviewed:
For more information, see the guide to lazy loading images and videos.
Added:
Don’t lazy load content that is likely to be visible immediately when a user opens a page. This can cause content to take longer to load and display in the browser, which will be very noticeable to the user.
At the Dynamic rendering as an alternative solution document (old here), Google removed the entire section on how to “Implement Dynamic Rendering”, “Verify Configuration” and the “Troubleshooting” sections.
Old:
Dynamic rendering is a workaround and not a long-term fix for problems with JavaScript-generated content in search engines. Instead, we recommend using server rendering, static rendering, or hydration as a workaround.
Reviewed:
Dynamic rendering was a workaround and not a long-term fix for problems with JavaScript-generated content in search engines. Instead, we recommend using server rendering, static rendering, or hydration as a workaround.
Old:
On some websites, JavaScript generates additional content on a page when it runs in the browser. This is called client-side rendering. Although Google Search runs JavaScript, there are limited JavaScript features in Google Search, and some pages may have issues with content not being displayed in the rendered HTML. Other search engines may choose to ignore JavaScript and will not see content generated by JavaScript.
Reviewed:
On some websites, JavaScript loads additional content when the page is open in a browser. This is called client-side rendering. Google Search sees this content along with content in a website’s HTML. Please note that there are some limitations for JavaScript in Google Search and that some pages may have issues with content not being displayed in the rendered HTML. Other search engines may choose to ignore JavaScript and will not see content generated by JavaScript.
Old:
Sites that should use dynamic rendering
Reviewed:
Sites that can use dynamic rendering
Old:
Dynamic rendering requires your web server to detect crawlers (for example, by checking the user agent). Requests from crawlers are sent to a renderer, requests from users are served as normal. When necessary, the dynamic renderer publishes a crawler-appropriate version of the content, for example, it can publish a static HTML version. You can choose to enable the dynamic renderer for all pages or per page.
Reviewed:
Dynamic rendering requires your web server to detect crawlers (for example, by checking the user agent). When your web server identifies a request from a crawler that does not support JavaScript or the JavaScript functions required to render your content, that request is sent to a rendering server. Requests from users and crawlers without JavaScript issues are served as normal. The rendering server responds to requests with a crawler-appropriate version of the content, for example, it may serve a static HTML version. You can choose to enable the dynamic renderer for all pages or per page.
Old:
Using dynamic rendering to serve completely different content to users and crawlers can be considered obfuscation. For example, a website that offers a page about cats to users and a page about dogs to crawlers may be considered cloaking.
Reviewed:
Using dynamic rendering to serve completely different content to users and crawlers can be considered obfuscation. For example, a website that serves a page about cats to users and a page about dogs to crawlers is hidden.
Discussion in the forum a X.
[ad_2]
Source link
