AJAX is used with JavaScript and XML to update content without the need to refresh the entire page, allowing less visual intrusion. Previously used to assist Google with the rendering of JavaScript content, our Hangout Notes cover how Google currently deal with AJAX content, with recommendations and examples.

Google Needs to Access JS Files & Server End Points Used For AJAX Requests

October 4, 2019 Source

If AJAX requests that are needed to download JavaScript on page load are being blocked in robots.txt, then Googlebot won’t be able to see or index any of the content that these requests will generate.

AJAX Crawling With Escaped Fragment URLs is a Deprecated Set up

October 17, 2017 Source

Using AJAX crawling set up with escaped fragment URLs is a deprecated set up. At some point Google will be turning off support for escaped fragment URLs and will only crawl and render the hashbang URLs themselves.

AJAX Content Loaded After 20 Seconds Won’t Be Seen by Google

March 7, 2017 Source

Content not loaded onto a page via AJAX immediately, probably won’t be seen by Google. John says 20-30 seconds is too long.

AJAX Loaded Hamburger Menus Won’t Be Seen by Google

February 24, 2017 Source

Hamburger menus with content loaded via AJAX probably won’t be seen by Google.

Google is OK with Manipulated Back Buttons

February 10, 2017 Source

Google doesn’t usually have a problem with Manipulating the back button behaviour, such as preventing users going back to Google’s search results.

May 6, 2016 Source

AJAX is not 100% equivalent to normal static HTML pages, but it should be possible to make pages rank as well. Avoid using fragments in URLs, and check with Fetch and Render.

Escaped Fragment Support will be Dropped

October 27, 2015 Source

Google’s support for the escaped fragment solution is going to continue in the mid-term.

Related Topics

Caching CSS JavaScript Rendering & SEO PWA