The document discusses the complexities of JavaScript SEO, highlighting when SEOs should be concerned about JavaScript and its impact on crawling and indexing by Google. It provides guidelines for testing and debugging JavaScript-related SEO issues, including tools and techniques for ensuring that critical content is indexed properly. Emphasis is placed on the importance of checking rendered HTML, accessibility of links, and performance-related factors that may affect how Googlebot interacts with JavaScript-heavy pages.

1. 08/05/19

2. JavaScript SEO:
Testing and Debugging
(for non-developers)
@LeighHanney
#smssyd19

3. First, a bit of background…
#smssyd19

4. Technical SEO used to be easier…
JavaScript is
making things a little
more complex.
JavaScript
SEO
Source: BuiltWith.com

5. Average JS Bytes
Downloaded
Up 200.9% on desktop
Up 386.6% on mobile
JavaScript
SEO

6. “… JS is not
going away.”
John Mueller
JavaScript SEO

7. JavaScript SEO
02 CHAPTER HEADING P XX
JavaScript,
Google &
SEO:
A Brief
Timeline

8. JavaScript SEO
02 CHAPTER HEADING
Raw HTML
1998 . . . . . . . . . . 2009 . . . . 2014, 2015 . 2017, 2018, 2019
AJAX Crawling Scheme
WMT Fetch & Render!
It’s official! “…we’ll now
crawl and render
‘AJAX-Based’ sites”.
AJAX Scheme Depreciated

9. Google is getting better at
understanding JavaScript. But…
1. When Should SEOs Worry About
JavaScript?
2. Crawl and Indexing Overview.
3. Some Tools for Testing.
4. What Should You be Looking For?
What We’ll
Cover Today
JavaScript SEO

10. When Should SEOs Worry About
JavaScript?
#smssyd19

11. JavaScript SEO
02 CHAPTER HEADING P XX
When should you worry about JavaScript?
You really need to pay attention if JS is
changing any critical content.
• When JavaScript is required to load all, or
some, of the main content.
• When JavaScript is performing any other
critical functions.
If JS is only used for non-essential interactions
and effects, it’s not really an SEO issue.
Check for
rendering
issues as part
of any
technical
audit.

12. Continue to:
1. Check URLs with JavaScript
disabled.
2. Review the text-based cache.
3. View the raw HTML (view source).
This can provide early indicators of how deep
you might have to go in the JS testing.
First Step…
Pretend it’s 2005.
Pre-JS SEO
JavaScript SEO

13. Does Your Site
Look Like This
With JS
Disabled?
JavaScript
SEO

14. GoogleBot and JavaScript Rendering
#smssyd19

15. JavaScript SEO
02 CHAPTER HEADING
GoogleBot’s Crawl and Index for JS
happens over ‘2 waves’
Wave 1: HTML (instant)
Wave 2: Render (mins, hours, days,
weeks)
• Ensure important content is indexed on
the first pass.
• Especially important for time sensitive
content (news)
• Advisable to minimise the use of JS for
critical content on product detail pages.
Image Source: Google I/O
2018

16. • As of right now, Google officially
render based on Chrome 41 (2015).
• Good for your developers to know.
• Deepcrawl have recently discovered
that GoogleBot is rendering some JS
features not actually supported in 41.
• A sign that Google’s rendering
capabilities are catching up.
Download Chrome 41:
Google render
using Chrome
41 (circa 2015)
JavaScript SEO
GOOD TO KNOW:
https://www.deepcrawl.com/blog/news/what-version-of-chrome-is-google-actually-using-for-rendering/
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/310958/

17. How does
GoogleBot
find links in
JS?…
JavaScript SEO
• GoogleBot looks for an anchor tag and
href element in the JavaScript.
• Without these, the links will not be
discoverable during rendering.

18. Google won’t
click on
buttons to find
links…
JavaScript SEO

19. …or click on
buttons for
paginated
results.
JavaScript SEO

20. A brief note about the DOM
1. The Document Object Model defines
the structure of a page (based on
HTML and CSS).
2. JavaScript is used to update or modify the
DOM.
3. ‘View Source’ only gives you the HTML and
in-line CSS.
4. ‘Inspect Element’ shows you the DOM
Inspect
Element
JavaScript SEO
GOOD TO KNOW:

21. • Technically you can use a tag manager
(e.g. GTM) to modify the DOM and
update SEO elements. Cool.
• It works too! But remember that this
relies on ‘Wave 2’ of indexing.
• While it’s a great solution, as a last
resort, the same rules apply:
• Try not to rely on JS to inject critical
meta data or schema.
• If content or meta data is time
sensitive, best to get it indexed in
the ‘first wave’ e.g. Price Schema
It’s possible
update your
SEO meta
data via JS
too…
JavaScript SEO
https://moz.com/blog/seo-changes-using-google-tag-manager
GOOD TO KNOW:

22. Way back in 2016…
• Working with a large ecommerce site
migrating over to an Angular powered
SPA.
• Gulp... Hugely complex.
• Injecting Canonicals was not working.
• HTTP Canonical was the only ‘reliable’
option we found for an SPA
implementation.
• Google I/O 2018 - Google actually
confirmed that they did not look for the
canonical in the rendered page.
• Others have since disagreed.
• Either way, I recommend avoiding if it’s
critical you get it right.
Avoid
injecting
Canonical
Tags via JS
JavaScript SEO
GOOD TO KNOW:

23. JavaScript Rendering in Action
#smssyd19

24. JavaScript SEO
02 CHAPTER HEADING
Desktop Render - Chrome 73
Desktop – JS Disabled
Desktop Render – Chrome 41

25. JavaScript SEO
02 CHAPTER HEADING
Mobile – Chrome (iOS) Mobile Friendly Test

26. Some Tools For Testing and
Debugging
#smssyd19

27. Chrome DevTools
JavaScript
SEO
‘Elements’
‘Console’
‘Sources’
‘Network’
‘Audit’
‘Coverage’
Control + Shift + C (Windows)
Command + Option + C (Mac)

28. URL Inspection
JavaScript
SEO
Test Live URL (AKA ‘Fetch and
Render’)
https://search.google.com/search-console

29. Mobile Friendly
Test
JavaScript
SEO
Rendered snapshot if you don’t
have access to GSC for the site.
https://search.google.com/test/mobile-friendly

30. Screaming Frog
SEO Spider
JavaScript
SEO
Crawl
Render
Snapshots
https://www.screamingfrog.co.uk/seo-spider/

31. Things You Should Be Testing For
#smssyd19

32. Don’t forget the basics: Ensure external
files (JS and CSS) needed for rendering
are not blocked.
Basics:
Blocked
Resources!
JavaScript SEO
Things to test for:

33. Render Responsibly…
• JS crawling is slower and it puts a
greater load on the servers (more
requests).
• Selectively render URLs by page type /
template.Raw HTML vs
Rendered
HTML
JavaScript SEO
Things to test for:

34. JavaScript SEO
02 CHAPTER HEADING
Step 1: Enable JS Rendering Step 1: Store HTMLStep 2: Check Resources

35. JavaScript SEO
02 CHAPTER HEADING

36. JavaScript SEO
02 CHAPTER HEADING

37. JavaScript SEO
02 CHAPTER HEADING

38. Confirm primary navigation links are in
the DOM.
1. Go to a URL.
2. Find some links to test.
3. Chrome DevTools (disable cache).
4. Reload page.
5. Search for the link in the ‘Elements’
tab.
Are Primary
Navigation
Links Visible?
JavaScript SEO
Things to test for:

39. JavaScript SEO
02 CHAPTER HEADING

40. Is content that requires user
interaction to view, available in the
DOM?
1. Go to a URL.
2. Find some content to test.
3. Chrome DevTools (disable cache).
4. Reload page.
5. Search for the string of content in the
‘Elements’ tab.
6. Perform a ‘site:domain.com “string”’
search in Google.
Check
content
behind tabs
and
accordions.
JavaScript SEO
Things to test for:

41. JavaScript SEO
02 CHAPTER HEADING

42. Check
Whether User
Generated
Content is
Indexed.
JavaScript SEO
Things to test for:

43. Check that any JS links have an anchor
tag and href attribute.
Can Google
Crawl internal
links?
JavaScript SEO
Things to test for:

44. Performance:
• JavaScript errors could result in
Google abandoning the render
process.
• Excessively large files or slow JS
execution time could also result in a
partial render of a page only.
Debugging:
• Screaming Frog’s default AJAX timeout
for the screenshot is 5 seconds. Good
indicator of potential Issues.
• Partial render in MFT, or ‘Other error’
in GSC, could also indicate JS
performance issues.
Look out for
JS errors in
the console
and Timeouts
when
rendering.
JavaScript SEO
Things to test for:

45. Developers, just don’t do this, please!
https://tipping.afl.com.au/landing/index.html#/landing
https://tipping.afl.com.au/help/index.html#/prizes
https://tipping.afl.com.au/help/index.html#/faqs
The Lone Hash
(#)
JavaScript SEO
Things to test for:

46. A Note About Other Crawlers &
JavaScript
#smssyd19

47. Many crawlers
still don't
render your
JS.
JavaScript SEO
• Bing, like Google, claim to be
rendering JS.
• Social media sharing can be
problematic for heavily JS dependent
pages.

48. JavaScript SEO
02 CHAPTER HEADING P XX
• JavaScript and rendering are just another part
of SEO now.
• If JS is used to inject critical content into the
DOM, then it’s a potential SEO issue.
Tools:
• Inspect URL (GSC)
• Mobile Friendly Test
• Chrome DevTools
• Crawl and Render (Screaming Frog)
Test:
• Don’t forget the fundamentals
• Raw vs Rendered HTML
• Internal Links
• Primary Navigation
• Content accessed via user interaction (tabs, etc)
• JavaScript Errors and Performance
Wrapping it
up!

49. Thanks
@LeighHanney
©2019