The Google Search workforce has made numerous comparatively minor modifications to its JavaScript documentation and in addition eliminated a lot of the dynamic rendering documentation, because it has been deprecated as a workaround for a few years now.
I am going to present you what modified:
On the Understand the JavaScript SEO basics – in the event you examine it to the older version:
Previous:
Googlebot queues pages for each crawling and rendering. It’s not instantly apparent when a web page is ready for crawling and when it’s ready for rendering.
When Googlebot fetches a URL from the crawling queue by making an HTTP request, it first checks in the event you permit crawling. Googlebot reads the robots.txt file. If it marks the URL as disallowed, then Googlebot skips making an HTTP request to this URL and skips the URL.
Revised:
Googlebot queues pages for each crawling and rendering. It’s not instantly apparent when a web page is ready for crawling and when it’s ready for rendering. When Googlebot fetches a URL from the crawling queue by making an HTTP request, it first checks in the event you permit crawling. Googlebot reads the robots.txt file. If it marks the URL as disallowed, then Googlebot skips making an HTTP request to this URL and skips the URL. Google Search will not render JavaScript from blocked information or on blocked pages.
Previous:
Describe your web page with distinctive titles and snippets
Distinctive, descriptive title components and useful meta descriptions assist customers to shortly establish the most effective consequence for his or her aim and we clarify what makes good title aspect and meta descriptions in our tips.
You should use JavaScript to set or change the meta description in addition to the title aspect.
Google Search would possibly present a distinct title hyperlink primarily based on the consumer’s question. This occurs when the title or description have a low relevance for the web page content material or after we discovered options within the web page that higher match the search question. Be taught extra about why the search consequence title would possibly differ from the web page’s title aspect.
Revised:
Describe your web page with distinctive titles and snippets
Distinctive, descriptive title components and meta descriptions assist customers shortly establish the most effective consequence for his or her aim. You should use JavaScript to set or change the meta description in addition to the title aspect.
Previous:
Use the Historical past API as an alternative of fragments
Google can solely crawl your hyperlink if it is an a HTML aspect with an href attribute.
Revised:
Use the Historical past API as an alternative of fragments
Google can solely uncover your hyperlinks if they’re a HTML components with an href attribute.
On the Fix Search-related JavaScript problems that is what modified:
Previous:
Use Search Console to observe Googlebot and WRS exercise and suggestions in your website.
Revised:
Use the crawl stats report in Google Search Console to observe Googlebot and WRS exercise and suggestions in your website.
On the Fix lazy-loaded content web page, that is what modified:
Previous:
For extra info, see the Internet Fundamentals information for lazy loading photographs and video.
Revised:
For extra info, see the information for lazy-loading photographs and video.
Added:
Do not add lazy-loading to content material that’s more likely to be instantly seen when a consumer opens a web page. That may trigger content material to take longer to load and present up within the browser, which might be very noticeable to the consumer.
On the Dynamic rendering as a workaround doc (old one here), Google eliminated the entire part on the right way to “Implement dynamic rendering,” “Confirm your configuration” and the “Troubleshooting” sections.
Previous:
Dynamic rendering is a workaround and never a long-term resolution for issues with JavaScript-generated content material in serps. As a substitute, we advocate that you simply use server-side rendering, static rendering, or hydration as an answer.
Revised:
Dynamic rendering was a workaround and never a long-term resolution for issues with JavaScript-generated content material in serps. As a substitute, we advocate that you simply use server-side rendering, static rendering, or hydration as an answer.
Previous:
On some web sites, JavaScript generates further content material on a web page when it is executed within the browser. That is known as client-side rendering. Whereas Google Search executes JavaScript, there are JavaScript options with limitations in Google Search and a few pages could encounter issues with content material not exhibiting up within the rendered HTML. Different serps could select to disregard JavaScript and will not see JavaScript-generated content material.
Revised:
On some web sites, JavaScript hundreds further content material when the web page is open in a browser. That is known as client-side rendering. Google Search sees this content material together with the content material within the HTML of an internet site. Understand that there are some limitations for JavaScript in Google Search and a few pages could encounter issues with content material not exhibiting up within the rendered HTML. Different serps could select to disregard JavaScript and will not see JavaScript-generated content material.
Previous:
Websites that ought to use dynamic rendering
Revised:
Websites which may use dynamic rendering
Previous:
Dynamic rendering requires your net server to detect crawlers (for instance, by checking the consumer agent). Requests from crawlers are routed to a renderer, requests from customers are served usually. The place wanted, the dynamic renderer serves a model of the content material that is appropriate to the crawler, for instance, it might serve a static HTML model. You’ll be able to select to allow the dynamic renderer for all pages or on a per-page foundation.
Revised:
Dynamic rendering requires your net server to detect crawlers (for instance, by checking the consumer agent). When your net server identifies a request from a crawler that doesn’t help JavaScript or the JavaScript options required to render your content material, this request is routed to a rendering server. Requests from customers and crawlers with out JavaScript points are served usually. The rendering server responds to requests with a model of the content material that is appropriate to the crawler, for instance, it might serve a static HTML model. You’ll be able to select to allow the dynamic renderer for all pages or on a per-page foundation.
Previous:
Utilizing dynamic rendering to serve utterly totally different content material to customers and crawlers may be thought of cloaking. For instance, an internet site that serves a web page about cats to customers and a web page about canine to crawlers may be thought of cloaking.
Revised:
Utilizing dynamic rendering to serve utterly totally different content material to customers and crawlers may be thought of cloaking. For instance, an internet site that serves a web page about cats to customers and a web page about canine to crawlers is cloaking.
Discussion board dialogue at X.
