DEEPCRAWL’S

ULTIMATE GUIDE TO
JAVASCRIPT FOR SEO
Contents
The state of the modern web 4

What is JavaScript? 5

How JavaScript works 8

The different JavaScript frameworks 11

How does JavaScript rendering work? 12

How search engines render JavaScript 14

How social media platforms render JavaScript 22

How browsers render JavaScript 23

The different rendering methods 24

Pre-rendering 24

Client-side rendering 25

Server-side rendering 26

Dynamic rendering 28

Hybrid rendering 30

Isomorphic JavaScript 31

The main things to watch out for with JavaScript 33

Testing how your website renders 41

What to test for 42

Tools for analysing JavaScript 43

Optimisation tips for JavaScript-powered websites 60

Conclusion 69
The state of the
modern web
To succeed in the current digital landscape, it is
crucial to understand how JavaScript works as well
as how to optimise JavaScript-powered websites
for both users and search engines. Why? Because
JavaScript is all around us.

JavaScript is becoming ever more prevalent on the

modern web. Over the years, the average number
of JavaScript bytes downloaded across the web
has increased by 335.6% on desktop and 588.4%
on mobile.

The word “JavaScript” can have negative

implications for many SEOs and digital marketers,
as they may associate it with search engine
indexing problems, testing difficulties and slow
websites. For developers, however, JavaScript can
actually provide a world of opportunities,
considering the scope of functionalities it provides.

I M AG E S O U R C E : H T T P A R C H I V E

04
 The purpose of this guide is to address and
alleviate some of the fears around JavaScript by
explaining exactly how it works, how it can
impact website performance and what you can
do to make sure your JavaScript-powered
ASCRIPT website
HAS performs in search. JAVASCRIPT HAS
COME A CRUCIAL BECOME A CRUCIAL
JavaScript isn’t going anywhere, so let’s get
T OF THEmore familiar with it. PART OF THE
DERN WEB, SO MODERN WEB, SO
NEED TO DO WE NEED TO DO
R PART TO OUR PART TO
RN MORE LEARN MORE
OUT IT AND HOW ABOUT IT AND HOW
AN IMPACT OUR IT CAN IMPACT OUR
BSITES. WEBSITES.
I M AG E S O U R C E : T W I T T E R

What is JavaScript?
To learn more about JavaScript, the first place “Every time a web page does more than
to start is understanding exactly what it is and
just sit there and display static information
how it works on the websites we manage.
for you to look at — displaying timely
JavaScript is essentially a programming content updates, interactive maps,
language that is used to implement the
animated 2D/3D graphics, scrolling video
interactive or dynamic elements of a website,
including personalisation, dynamically updating jukeboxes, etc. — you can bet that
content and notifications. The HTML and CSS of JavaScript is probably involved.”
a page usually form the main structure and
styling of a page, but JavaScript is what brings it 1

to life. MDN Web Docs

1 MDN Web Docs, https://developer.mozilla.org/en-US/docs/Learn/JavaScript/First_steps/What_is_JavaScript, 31st January 2019 05

JAVASCRIPT
SHOULDN’T JUST
BE VIEWED AS AN
INCONVENIENCE
FOR SEOS, AS IT JavaScript opens up a world of possibility for
user interactivity, because it can respond to
OFTEN POWERS
input and change content accordingly within
INTERACTIVITY the browser without having to keep making full
AND THE ELEMENTS page requests to the server. This creates
smoother interactions for users.
OF A WEBSITE THAT
CAN TRULY ENGAGE
To better understand the capabilities of
A USER. JavaScript and why it’s necessary to the
modern web, we need to learn more from the
people who are building the web with it:
developers.

“JavaScript allows you to add complex

animations, fetch and process customer
data, use open APIs to integrate with
popular products and technologies, and
enhance the user experience. And while
there are ways in which we can optimize
our JavaScript code to reduce overhead,
JavaScript will never disappear.”

Emma Wedekind,
UX Engineer
at LogMeIn

06
“There are many benefits and arguments for using JavaScript, and the fact
it’s taking over the web, mobile and desktop landscapes only solidifies its
position in the industry. JavaScript is unique. Times have changed where
the server environment does the heavy lifting, this is down to the client
(browser) now. We deploy static JavaScript assets and the server simply
acts as a JSON API gateway, transferring information between database
and client. This helps clean up architecture and allows us to bring sensible
engineering patterns to the front-end development landscape. User
interactions are much more powerful, we can validate things such as email
addresses, passwords and complex logic on the fly - without full page
reloads and waiting times. The user’s perception of speed is altered with a
powerful JavaScript environment.

All in all, the benefits of JavaScript are immense and seeing that 95.1% of
websites use JS doesn’t surprise me.”

Ana Cidre,
Developer Advocate &
Engineer at Ultimate Angular

07
How JavaScript works DOCUMENT
ROOT
<HTML>

When a page is requested, the HTML and

CSS are parsed and constructed to create
the DOM (Document Object Model),
which is then rendered and loaded. The ELEMENT ELEMENT
DOM maps out a page in a clear, <HEAD> <BODY>

structured way using nodes and objects

to represent all of its different elements.
This is so that other programs and scripts
can easily come in and modify the page’s
ELEMENT ELEMENT ELEMENT
content and styling. <LITTLE> <P> <H1>

To the right is an example of what the

DOM might look like:

TEXT NODE
TEXT NODE TEXT NODE
You can see what the DOM looks like for “THIS IS AN
“EXAMPLE” EXAMPLE PAGE” “EXAMPLE PAGE”
your website by using the ‘Inspect’
element in your browser, which will lay
out the different head and body elements
of a page. I M AG E S O U R C E : C O M P U T E R H O P E

Once a page’s structure has been defined, then JavaScript can be triggered which will make any changes
necessary and modify the DOM and HTML, meaning that the final view of the page can then be updated.

08
 “A very common use of JavaScript is to dynamically modify HTML and MDN Web
2
CSS to update a user interface, via the Document Object Model API. If Docs
the JavaScript loaded and tried to run before the HTML and CSS were
there to affect, then errors would occur.”

HTML AND CSS USUALLY FORM THE STRUCTURAL FOUNDATIONS OF

A WEBSITE, THEN JAVASCRIPT WILL SEND INSTRUCTIONS ON WHAT
CODE NEEDS TO BE UPDATED AND ADD THE FINISHING TOUCHES.

“Until a few years ago, SEOs focused on HTML and CSS. HTML has traditionally been responsible
for content and CSS for the layout, design, and visual effects. These two languages can craft an
aesthetically appealing, functional, flat pages.

If Google is a library, a website is a book. A site built with JavaScript is a pop-up book. With
JavaScript, a dozen lines of flat HTML sent from your server unfurl and execute a web version of
programming code. The desire for personalized, interactive, and engaging user experiences is
why today more than 95% of sites use JavaScript. For search engines and SEOs to experience
site content, they need to execute JavaScript.”

Jamie Alberico,
SEO Product Owner at
Arrow Electronics

2 MDN Web Docs, https://developer.mozilla.org/en-US/docs/Learn/JavaScript/First_steps/What_is_JavaScript, 31st January 2019 09

 Either internal or external JavaScript can be used on a website. Internal JavaScript is integrated into the
page’s source code. E.g.:

External JavaScript, on the other hand, is included in a link to a separate file that is requested. E.g.:

JavaScript is an embedded scripting language, meaning that it can be embedded into different applications
using an API (Application Programming Interface). This flexibility is one of the reasons why JavaScript can
be so powerful for developers when building websites.

“Application Programming Interfaces (APIs) provide you with extra superpowers to use in your
JavaScript code.”

MDN Web Docs

If you’d like to brush up on some more of the key terms and concepts around JavaScript and rendering,
then make sure you read this guide on JavaScript fundamentals.

3 MDN Web Docs, https://developer.mozilla.org/en-US/docs/Learn/JavaScript/First_steps/What_is_JavaScript, 18th November 2018 10

 The different JavaScript frameworks

A JavaScript framework contains a set of “At their most basic, JavaScript frameworks
libraries, components and instructions for
are collections of JavaScript code libraries
building websites and user interfaces with
code. that provide developers with pre-written JS
code to use for routine programming
Each framework comes with its own positives
features and tasks—literally a framework to
and negatives, so choosing the right one will
depend on a developer’s needs and the build websites or web applications around.”
specifications of the project they’re working on.
4
Skillcrush
These are the main JavaScript frameworks:

B AC K B O N E METEOR EMBER R E AC T

AU R E L I A VUE ANGULAR NODE

REASON S V E LT E ELM P R E AC T

There are some great guides which compare

the different frameworks in detail, such as these
ones from RubyGarage and unicorn.supplies.

INFERNO P O LY M E R

4 Skillcrush, https://skillcrush.com/2018/07/23/what-is-a-javascript-framework/, 22nd January 2019 11

How does
JavaScript
rendering work?
JavaScript code by itself doesn’t always mean
that much. It needs to be processed and
rendered before output code can be displayed
and the requested page can be shown to the
client, such as the user’s browser or the search
engine crawler. Can you tell what this example
website is about by looking at this HTML alone?

I M AG E S O U R C E :
M A R T I N S P L I T T, F R O N T E N D C O N N E C T

No? Well, neither can a search engine or

browser unless JavaScript is executed. This is
why rendering is needed to run scripts like the
one above and populate a page’s HTML with
content so it can be read, understood and used
for indexing.

As opposed to content in the HTML, JavaScript-

powered content takes a little more preparation
before it is meaningful to the client requesting
it, and this happens through the process of
rendering.

12
 I M AG E S O U R C E : B A R T O S Z G Ó R A L E W I C Z , S M X

JAVASCRIPT-POWERED CONTENT NEEDS TO BE

RENDERED BEFORE IT CAN OUTPUT MEANINGFUL CODE
AND BE DISPLAYED FOR THE CLIENT.

These are the different steps involved in the JavaScript rendering process:

JAVASCRIPT STYLE LAYOUT PAINT COMPOSITE

I M AG E S O U R C E : G O O G L E D E V E LO P E R S

1 “JavaScript: Typically JavaScript is used to handle work that will result in visual changes.

2 Style calculations: This is the process of figuring out which CSS rules apply to which elements. They
are applied and the final styles for each element are calculated.

3 Layout: Once the browser knows which rules apply to an element it can begin to calculate how
much space it takes up and where it is on screen.

4 Paint: Painting is the process of filling in pixels. It involves drawing out text, colors, images, borders,
and shadows, essentially every visual part of the elements.

5 Compositing: Since the parts of the page were drawn into potentially multiple layers they need to be
drawn to the screen in the correct order so that the page renders correctly.” 5

5 Google Web Fundamentals, https://developers.google.com/web/fundamentals/performance/rendering/, 29th January 2019 19

13
VED
How search engines CONTENT AND LINKS SERVED
HE
render JavaScript VIA JAVASCRIPT RUN THE
BY RISK OF NOT BEING SEEN BY
It’s important to bear in mind that most search
HEY engines can’t render at all, and those that do SEARCH ENGINES, AS THEY
NG have their own rendering limitations. This EITHER HAVE RENDERING
means that if your website relies on JavaScript
OR to power its content and navigation, search
LIMITATIONS AT BEST, OR
. engines could end up seeing a blank screen DON’T RENDER AT ALL.
with nothing of value to crawl or index.

“One of the biggest struggles which search Until search engines have a way to handle
engines (and SEOs) have with JavaScript is this new world, it's imperative that SEO
that it often breaks our working model of practitioners understand how JavaScript
what a "page" is. We're used to a world websites work, and can wrangle them into
where content lives in HTML code, on a a format which Google can consume and
webpage, which is represented by a URL; understand. In most cases, that's as simple
and for the most part, pages are generally (and as complex) as ensuring that the
consistent in form and behaviour. This website behaves like a "normal" site when
model sits at the very heart of how Google JavaScript isn't enabled.
crawls, processes, and evaluates content.
Make no mistake, JavaScript websites are
With JavaScript, that paradigm shatters. We the future. Consumers expect and demand
lose the connection between URLs, pages the kinds of rich experiences which only
and content, as the browser fluidly changes apps can deliver. But if we don't step in,
based on user interaction. We move into a steer best practice and level-up the
world of "states" and "views", which don't development community, the
neatly fit our model. This makes it hard for web as we know it will break.”
search engines to understand what a
"page" is, nevermind the challenges of
Jono Alderson,
accessing, evaluating and associating the
Mad Scientist at Yoast
value of content with a URL.

14
 We’ve put together the latest updates on how Google
the main search engines are currently equipped
for rendering, as well as some key Google is one of the few search engines that
considerations for each one. currently renders JavaScript, and provides a lot
of documentation and resources on JavaScript
best practice for search. This means we’re able
to build a pretty clear picture of what we need
to do to get our websites indexed in Google’s
SERPs (Search Engine Results Pages).

How Google renders JavaScript

When Google renders, it generates markup

from templates and data from a database or an
API. This markup is then sent to the client to
update the DOM and paint pixels to the screen.
The key step in this process is to get the fully
generated markup though, because this is
what’s readable for Googlebot.

Rendering
I M AG E S O U R C E :
M A R T I N S P L I T T, A N G U L A R U P C O N F E R E N C E

TEMPLATES

MARKUP DOM PIXELS

DATA

To carry out this process, Googlebot uses a The most recent version at the time of writing is
headless browser for its web rendering service Chrome 72, so there is a gap between the
(WRS). A headless browser is essentially a latest browser functionalities and how
browser without the visual elements, which Googlebot is able to render content. To put this
outputs rendered code rather than a visually in perspective, since Chrome 41 was released,
rendered page. Google’s WRS is based on 892 new Chrome features have been added.
6
Chrome 41 which was launched in 2015, and is
limited by the features of the Chrome version it
is using.

6 Google Search, https://developers.google.com/search/docs/guides/rendering, 1st October 2018 15

 I M AG E S O U R C E : C H R O M E P L AT F O R M S TAT U S

“The last time I checked my calendar, it was 2019. I wish search engines were perfect at
rendering JavaScript, but unfortunately, that's not the case. The key is to know search engines’
limitations and how to deal with them.

Google’s Web Rendering Service uses a 4-year old browser for rendering. You can’t change that
but you should ensure that Google can access your content by using proper tools, like the URL
Inspection Tool, Chrome 41, Mobile-friendly Test and Rich Results Test. In addition, make sure
Google has indexed your content by using the “site” command.

If something is wrong, you can analyze what errors Google gets while
rendering. Maybe you forgot about polyfills or transpiling to ES6? Sit with
your developer and start talking about the issue. If you can’t find
anything that helps, you may consider moving to hybrid
rendering or dynamic rendering.”

Tomek Rudzki,
R&D Specialist at Elephate

16
How Google’s rendering
process impacts search

Google has a two-wave indexing process,

which means that there are no guarantees on
when pages will actually be rendered. The
crawling and indexing process is usually very
quick for sites that don’t rely on JavaScript,
however, Google can’t crawl, render and index
all in one go due to the scale of the internet
and the processing power that would be
required to do so.

After a page has initially been crawled,

Googlebot will find all pages with JavaScript on
them that need to be rendered, and will then
add them to a queue to be rendered at a later
date when enough resources become
available.

“The internet is gigantic, that’s the problem.

We see over 160 trillion documents on the
web daily, so Googlebot is very busy.
Computing resources, even in the cloud
age, are pretty tricky to come by. This
process takes a lot of time, especially if your
pages are really large, we have to render a
lot of images, or we have to process a lot of
megabytes of JavaScript.”

Martin Splitt,
Webmaster Trends
7
Analyst at Google

7 AngularUP Conference, https://www.youtube.com/watch?

v=Z9mHopLeE40, 17th October 2018
17
 I M AG E S O U R C E : T W I T T E R

A page will only be added to the index in the

second wave after it has been rendered.

Instant,
first wave of indexing
CRAWL

As rendering resources
become available
INDEX
New links to be
crawled

RENDER
Second wave of
indexing

I M AG E S O U R C E : G O O G L E I / O 2 0 1 8

When resources do become available, there What is the gap between the first and second
isn’t a specific way of prioritising the pages that wave of indexing then? According to Google’s
will be rendered first. Google’s John Mueller Tom Greenaway and Martin Splitt during
explained that any prioritisation is done in the Chrome Dev Summit 2018, it could take
same way as for regular crawling and indexing. “minutes, an hour, a day or up to a week” for
Google to render content after a page has been
crawled.
Google doesn't have a separate way of
prioritising pages for rendering. If your website gets stuck between these two
waves of indexing, any new content you add or
John Mueller, any changes you make to your website won’t
8
Google Webmaster Hangout be seen or indexed for an undetermined
amount of time. This will have the biggest
impact on sites that rely on fresh search results,
such as ecommerce or news sites.

8 DeepCrawl, https://www.deepcrawl.com/blog/news/google-webmaster-hangout-notes-july-13th-2018/, 13th July 2018 18

 Ecommerce websites should avoid serving
HAT RELY product
ON page content via JavaScript. SITES THAT RELY ON
T FRESHNESS CONTENT FRESHNESS
AVOID John Mueller, SHOULD AVOID
9
Google Webmaster Hangout
CONTENT SERVING CONTENT
ASCRIPT, AS VIA JAVASCRIPT, AS
’S INDEXING GOOGLE’S INDEXING
News sites should avoid content that
DERED PAGES OF RENDERED PAGES
requires JavaScript to load.
YED. IS DELAYED.

John Mueller,
10
Google Webmaster Hangout

The team at Google are aware that this isn’t an “In general, Bing does not have crawling
ideal situation for website owners and are and indexing issues with web sites using
working on updating their rendering services.
JavaScript, but occasionally Bingbot
At Chrome Dev Summit 2018, Martin Splitt
announced that Google will be updating its
encounters websites heavily relying on
WRS so that it stays up to date with Chrome’s JavaScript to render their content,
release schedule, meaning that the WRS will especially as in the past few years. Some of
always use the latest version of Chrome. these sites require far more than one HTTP
request per web page to render the whole
Bearing all of this in mind, you can start to see
page, meaning that it is difficult for
that Google needs some additional help to
render your modern JavaScript websites and Bingbot, like other search engines, to
applications. We’ll go over some of the things process at scale on every page of every
you can do later on in this guide. large website.

Therefore, in order to increase the

Bing
predictability of crawling and indexing of
Bing’s crawler allegedly does render JavaScript, websites relying heavily on JavaScript by
but is limited in being able to process the latest
Bing, we recommend dynamic rendering as
browser features and render at scale, which
a great alternative.
sounds like a similar situation to Google’s.

9 DeepCrawl, https://www.deepcrawl.com/blog/news/google-webmaster-hangout-notes-september-21st-2018/, 21st September 2018

10 DeepCrawl, https://www.deepcrawl.com/blog/news/google-webmaster-hangout-notes-september-4th-2018/, 4th September 2018

19
 Dynamic rendering is about detecting Yahoo!
search engines bot by parsing the HTTP
Yahoo cannot currently render. It is
request user agent, prerendering the
recommended to make sure that content isn’t
content on the server-side and outputting
‘hidden’ behind JavaScript, as the search
static HTML, helping to minimize the engine won’t be able to render JavaScript to
number of HTTP requests needed per web find any content within it. Only content that is
page and ensure we get the best and most served within the HTML will be picked up.
complete version of your web pages every
time Bingbot visits your site. “Unhide content that’s behind JavaScript.
Content that’s available only through

When it comes to rendering content JavaScript should be presented to non-

specifically for search engine crawlers, we JavaScript user agents and crawlers with

inevitably get asked whether this is noscript HTML elements.”

considered cloaking... and there is nothing 12

scarier for the SEO community than getting Yahoo Webmaster Resources
penalized for cloaking. The good news is
that as long as you make a good faith effort
Yandex
to return the same content to all visitors,
with the only difference being that the Yandex’s documentation explains that the
content is rendered on the server for bots search engine doesn’t render JavaScript and
and on the client for real users, this is can’t index any content that is generated by it. If
you want your site to appear in Yandex, make
acceptable and not considered cloaking.”
sure your key content is returned in the HTML
upon the initial request for the page.
Fabrice Canel,
Principal Program Manager at Bing “Make sure that the pages return the full
content to the robot. If they use JavaScript

Even though Bing can render in some capacity, code, the robot will not be able to index the
it isn’t able to extract and follow URLs that are content generated by the script. The
contained within JavaScript. content you want to include in the search
should be available in the HTML code
“Don’t bury links to content inside immediately after requesting the page,
JavaScript.” without using JavaScript code. To do this,
use HTML copies.”
11
Bing Webmaster Guidelines
13
Yandex Support

11 Bing Webmaster Guidelines, https://www.bing.com/webmaster/help/webmaster-guidelines-30fba23a, 5th February 2019 (last accessed)

12 Yahoo Webmaster Resources, https://help.yahoo.com/kb/higher-website-rank-sln2216.html, 13th February 2019 (last accessed)

13 Yandex Support, https://yandex.com/support/webmaster/recommendations/changing-site-structure.html, 13th February 2019 (last accessed) 20

 The other search engines
DuckDuckGo, Baidu, AOL and Ask are much
less open about their rendering capabilities.
The only way to find this out currently is to run
tests ourselves, but luckily Bartosz Góralewicz
has done some of this work already.

In 2017, Bartosz ran some experiments using a

test site that used different JavaScript
frameworks to serve content and analysed
which search engines were able to render and
index the content. We can never make definitive
conclusions based on the indexing of test sites
alone, but the results showed that only Google
and, surprisingly, AOL were able to index
rendered content.

Not indexed I M AG E S O U R C E : M O Z

“Bing, Yahoo, AOL, DuckDuckGo, and Take a look at the full article covering the

Yandex are completely JavaScript-blind and experiment and results to learn more about
Bartosz’s conclusions.
won’t see your content if it isn’t in the HTML.”

Bartosz Góralewicz,
14
Co-founder of Elephate

14 Moz, https://moz.com/blog/search-engines-ready-for-javascript-crawling, 29th August 2017 21

 How social media platforms
render JavaScript
It’s important to know that social media and
sharing platforms generally can’t render
JavaScript.

Facebook and Twitters' crawlers can’t

render JavaScript.

Martin Splitt,
15
Google Webmaster Hangout

If you rely on JavaScript to serve content that

would feed into Open Graph tags, Twitter Cards
or even meta descriptions that would show
when you share an article on Slack, for
example, this content wouldn’t be able to be
shown.

Rachel Costello

I M AG E S O U R C E : S L AC K

15 DeepCrawl, https://www.deepcrawl.com/blog/news/google-webmaster-hangout-notes-october-30th-2018/, 30th October 2018 22

How browsers render JavaScript

When a user tries to access a page that uses JavaScript causes an issue for browser
JavaScript, their browser will firstly receive rendering because it has the potential to modify
HTML, CSS and JavaScript in packets of data. the page. This means that rendering has to be
The code from these packets is then parsed paused each time a new script is found and the
and mapped out to create the DOM, which structuring and styling of the page is put on
defines the structure of the page. This structure hold to keep up with any changes that
is combined with instructions from the CSS JavaScript might make to the page.
about the styling of the different elements on
the page, which creates the render tree. This is To learn more about how browsers render
what the browser uses to layout the page and JavaScript, this guide explains the process in
start painting pixels to the screen. more detail.

The most commonly used browsers are:

CHROME S A FA R I F I R E F OX

SAMSUNG INTERNET OPERA EDGE

JAVASCRIPT CAUSES THE BROWSER TO STOP AND START

THE PROCESS OF RENDERING, WHICH CAN HAVE A BIG
IMPACT ON PAGE LOAD SPEED.

23
Each browser has its own rendering environment and can have its own unique challenges. This is why it’s
crucial to test how your website loads across different browsers. Find out the main browsers that are used
by people visiting your website, and test how those render as a priority. You can find this information in the
Audience section of Google Analytics under ‘Technology’.

The different rendering methods

It’s possible to make alterations to how your content is delivered to users and search engines by
implementing different rendering methods. You can alter how much of the rendering work falls on the client,
i.e. the user’s browser or the search engine bot requesting the page. In this section of the guide, we’ll take a
look at how some of these different methods work

Pre-rendering

Pre-rendering a page is when the client creates the structure of a page which is shown before the final
content is rendered to the screen. It shows a static snapshot of the page immediately which can be useful
for showing content to search engines on page load without them having to render anything. However, this
snapshot is not the complete version of the page.

“As SEOs, it's important that we prioritize our sites' users and ensure search engines are able to
grasp our experience. Luckily for us, there are a variety of solutions to ensure that both users and
bots can receive the optimal experience. Two top options include:

24
1. Do nothing. Perhaps the simplest technical solution, we can test whether or not a more
JavaScript-heavy solution has any effect on performance (including: rankings, crawl logs,
traffic, and engagement metrics). If you are changing experiences, (if possible) attempt on a
smaller section of the site. This will enable any kinks to be ironed out early in the process.

2. Pre-render. Pre-rendering is a solution where we send bots an HTML experience (i.e. a

rendered version of the DOM (i.e. what people see)), circumventing the issue. The most
important element here is to: make sure search engines are being served a valid, accurate
representation of the JavaScript-based equivalent at all times.”

Alexis Sanders, PROS

SEO Manager at Merkle
Allows search engines to see some
content immediately for indexing.

CONS

Doesn’t show the full content.

Prone to loading issues.

Pre-rendered content lacks interactivity

for users.

Client-side rendering

Client-side rendering is when the client, such as the user’s browser or search engine crawler, does the work
of processing and rendering any JavaScript. The server will respond to the initial request for the page, but
the rest is down to the client. Client-side rendering is often advised against because the time and expense
of processing JavaScript falls on users’ devices and on search engines. Also, most search engines can’t
even render JavaScript in the first place.

SERVER BROWSER & CRAWLER

PRIMARILY JS RENDER &

(HTML BASED) DISPLAY

I M AG E S O U R C E : G O O G L E I / O 2 0 1 8
25
PROS CONS

Puts less strain on the server. Puts more strain on the CPU (Central
Processing Unit) of the user’s device.

Increases page load time.

Most search engines and social media

crawlers don’t render JavaScript, so
won’t see your content.

“If client-side JavaScript isn’t benefiting the user-experience, ask

yourself if it’s really necessary. Maybe server-side-rendered HTML would
actually be faster. Consider limiting the use of client-side frameworks to
pages that absolutely require them.”

Addy Osmani,
16
Engineering Manager at Google

Server-side rendering

With server-side rendering, the server does the heavy lifting and will render any JavaScript on the page,
meaning that it can send a fully processed page straight to the client. All the client has to do is display the
finished content. Server-side rendering allows search engines and social media crawlers to index your
content, even the ones that struggle with rendering.

SERVER BROWSER & CRAWLER

PRE-RENDERED
DISPLAY
HTML

I M AG E S O U R C E : G O O G L E I / O 2 0 1 8

Implementing server-side rendering has shown dramatic increases in page speed and performance for
some of the biggest brands, including Netflix.

16 Medium, https://medium.com/@addyosmani/the-cost-of-javascript-in-2018-7d8950fbb5d4, 1st August 2018 26

 I M AG E S O U R C E : T W I T T E R

Some solutions for implementing server-side

rendering are Prerender.io, Universal,
Puppeteer and Rendertron.

PROS

Processes and sends the full content to the

client.

Link discovery is faster as markup is available

quickly for search engines.

Content is available quickly for users.

Increases site speed and performance.

“The issue is that many JavaScript-based

websites are relying too heavily on client-side
rendering, where they should do everything
server-side. Sure, server-side rendering is more
complex and expensive, but why are we risking
David Iwanow,

SEO and punishing our users to make

Global Search &

developers’ jobs easier by implementing the

Traffic Manager at

simpler client-side rendering?”

Danone

17 36
27
CONS “Server-side rendering TTFB (Time To First
Byte) is slower than client-side rendering
Can cause UX issues if a user can see a page
but has to wait until the client is alive and able TTFB, because your server will have to
to process any interactivity.
spend the time to create the HTML for your
Puts more strain on the server. page instead of just sending out a relatively
empty response.”

17

WalmartLabs

Dynamic rendering

Dynamic rendering works by detecting the user agent of the client making the request. If Googlebot or
another search engine or social media crawler user agent is detected, a mini client-side renderer will be
used to render all JavaScript. The fully rendered page will then be sent to the client. Any other user agents
will need to render JavaScript client-side.

SERVER INFRASTRUCTURE

WEB
SERVER

INITIAL HTML COMPLETE

DYNAMIC
REQUIRED TO RENDER “DYNAMICALLY RENDERED”
RENDERER
CLIENT-SIDE VERSION HTML

INITIAL HTML
PRE-RENDERED
REQUIRED TO RENDER DISPLAY
HTML
CLIENT-SIDE VERSION

I M AG E S O U R C E : G O O G L E I / O 2 0 1 8

17 WalmartLabs, https://medium.com/walmartlabs/the-benefits-of-server-side-rendering-over-client-side-rendering-5d07ff2cefe8, 17th April 2017 28

36
Here’s an example of the bot user agents you
might want to dynamically render for:

export const botUserAgents = [

‘googlebot’,
‘google-structured-data-testing-tool’,
‘bingbot’,
‘linkedinbot’,
‘mediapartners-google’,
];

Dynamic rendering is considered to be a

workaround for search engines or social media
crawlers that might not run JavaScript.
Rendering is taken care of for search engines,
but browser processing times and user
experience are still an issue when using this
method.

Google and other search engines like Bing

recommend dynamic rendering as a solution for
getting content generated by JavaScript
indexed.

“In order to increase the predictability of

crawling and indexing by Bing, we
recommend dynamic rendering as a great
alternative for websites relying heavily on
JavaScript.”

18

Bing Blog

Some solutions for implementing server-side

rendering are Prerender.io, Puppeteer and
Rendertron.

PROS

Markup is available quickly for search engines

to index.

18 Bing Blog, https://blogs.bing.com/webmaster/october-2018/bingbot-Series-JavaScript,-Dynamic-Rendering,-and-Cloaking-Oh-My, 31st October 2018 29

 “Dynamic rendering is good for indexable, CONS
public JavaScript-generated content that
Puts more strain on the server.
changes rapidly, or content that uses
JavaScript features that aren't supported Users’ browsers will still be required to render
JavaScript.
by the crawlers you care about. Not all sites
need to use dynamic rendering, and it's Adds another layer of complexity for testing.

worth noting that dynamic rendering is a

workaround for crawlers.”
“Dynamic rendering creates two separate
19
structures instead of one. It doesn’t
Google Search
improve UX, but instead it adds another
layer of complexity. Dynamic rendering is a
workaround that was made for SEO, it
doesn’t improve anything for users.”

Bartosz Góralewicz,
20
Co-founder of Elephate

Hybrid rendering

Hybrid rendering involves a combination of server-side and client-side rendering. The core content of the
page is rendered on the server and is sent to either the browser or search engine requesting the page. This
means that the client will always receive the rendered content and markup straight away.

There is a final step in this process for users. Once the core content has been displayed, additional
JavaScript is then sent to be rendered client-side so the user can interact with the page.

SERVER BROWSER & CRAWLER I M AG E S O U R C E :

GOOGLE I/O 2018

PRE-RENDERED DISPLAY
HTML
INDEXED

ON INTERACTION BROWSER ONLY

JS UPDATE DISPLAY

19 Google Search, https://developers.google.com/search/docs/guides/dynamic-rendering, 17th October 2018

SMX,
20 17 https://www.slideshare.net/goralewicz/dynamic-rendering-is-this-really-an-seo-silver-bullet, 30th January 2019 30
 Hybrid rendering is a popular choice and has been adopted by some of the biggest brands, including Netflix
and Nike.

PROS CONS

Faster content and link discovery for The full-page experience isn’t available
search engines. without some client-side rendering.

Content is available faster for users. Can be complex to implement.

Allows interactivity for users. Can cause speed issues as rendering

needs to happen twice.

Isomorphic JavaScript

Isomorphic JavaScript, also referred to as Twitter and Airbnb are just a couple of the
Universal JavaScript, renders on both the prominent brands that have been implementing
server-side and client-side. Pre-rendering is and experimenting with Isomorphic JavaScript.
used to serve content to the user or search
engine on the first request, then interactivity
PROS
that requires JavaScript is handled on the
client-side.
Content is available quickly to search engines
for indexing.

“Isomorphism means that you can feed The site is perceived to load faster and is user-
friendly.
your application with some data coming
from the database on the server, run it, and
capture the resulting HTML output that
would normally require a browser to
assemble. This output can then be served
as your initial HTML to everyone who
requests it (including crawlers, such as
Googlebot).”

Bartosz Góralewicz,
21
Co-founder of Elephate

21 Search Engine Journal, https://www.searchenginejournal.com/javascript-seo-like-peanut-butter-and-jelly-thanks-to-isomorphic-js/, 19th January 2017 31

 “JavaScript is going nowhere. More
websites will be adopting JavaScript
frameworks so we need to learn how to
make JavaScript websites crawlable and
indexable by search engines. Google
capabilities for rendering are impressive
but do you want to rely on that? I don't.

Dynamic rendering is a good solution for

already existing websites. If you go down
NO MATTER WHICH this route, set automated monitoring of the
RENDERING METHOD pre-rendering process. It's easy to miss a
pre-rendering issue because those HTML
YOU USE, FOCUS ON
snapshots are only served to crawlers and
MAKING SURE THAT not to users.
THE LESS ADVANCED
If you're building a new site, go with
SEARCH ENGINES,
Isomorphic JavaScript. It combines the
BROWSERS AND speed and search engine friendliness of
DEVICES WILL STILL server-side rendering with the interactivity
of client-side JavaScript.”
BE ABLE TO ACCESS
YOUR CONTENT.

Robin Rozhon,
SEO Strategist
CONS
at EA
Your server needs to support Node JS
applications to enable isomorphism.

Can be complex to implement.

Whichever rendering method you use, make Your choice of rendering method should be
sure the content you’re serving is accessible to informed by the needs of your business and
and works for whichever search engine bot or website. For example, if you have a section of
browser that is requesting it. Client-side your site that requires a log in to be accessed,
rendering might work for users on a modern none of that will need to server-side rendered.
browser and a high-end CPU, but search You would implement server-side rendering for
engines, social media crawlers or users on a your publicly accessible landing pages that
lower end CPU device will need some help to contain descriptive content about your services
be able to see your website’s content. instead.

32
The main things to watch out
for with JavaScript
JavaScript rendering is often a complicated and 1 Rendering speed
resource-intensive process for a number of
different reasons, and can significantly impact a 2 Main thread activity
variety of different performance and user
3 Conflicting signals between HTML
experience factors. It’s crucial to understand
and JavaScript
where these issues can occur and how they can
impact your website. 4 Blocked scripts

These are the 8 main things to watch out for 5 Scripts in the head
within a JavaScript-powered website:
6 Content duplication

1
7 User events

8 Service workers

Rendering speed
JavaScript is hosted in the browser which it relies on for all the heavy lifting because it doesn’t have its own
storage or network facilities. The JavaScript will give instructions on what needs to happen to construct and
load the page, but it relies on its host environment to actually do all of this.

The process of rendering JavaScript is also very expensive because of the four different stages that it runs
through:

Download Parse Compile Execute

These multiple steps are one of the main reasons why JavaScript is much more expensive to process than
other elements, such as images or HTML.

I M AG E S O U R C E : B A R T O S Z G Ó R A L E W I C Z , D E E P C R AW L W E B I N A R
33
 Having JavaScript-heavy pages that take a long Another issue to consider is that a user’s device
time to process and render means that they are and CPU will usually have to do the hard work
at risk of not being rendered or processed by with JavaScript rendering, but not all CPUs are
search engines. up for the challenge. It’s important to be aware
that users will experience page load times
differently depending on their device. Just
“If your web server is unable to handle the because a site appears to load quickly on a
volume of crawl requests for resources, it high-end phone, it doesn’t mean that this will be
may have a negative impact on our the case for a user accessing the same page
capability to render your pages. If you’d like with a lower-end phone.

to ensure that your pages can be rendered

by Google, make sure your servers are able
“What about a real-world site, like
to handle crawl requests for resources.”
CNN.com? On the high-end iPhone 8 it
22 takes just ~4s to parse/compile CNN’s JS
Google Webmaster Central Blog compared to ~13s for an average phone
(Moto G4). This can significantly impact

JavaScript that renders slowly will also impact

how quickly a user can fully interact with
your users because, with the increase of page this site.”
load time, bounce rates will also rise. Nowadays
23
a user will expect a page to load within a few
Google Web Fundamentals
seconds or less. However, getting a page that
requires JavaScript rendering to load quickly
enough to meet those expectations can be
challenging.

VASCRIPT JAVASCRIPT
NDERING CAN BE RENDERING CAN BE
EXPENSIVE AND AN EXPENSIVE AND
RENUOUS STRENUOUS
OCESS. THIS PROCESS. THIS
USES CAUSES
NIFICANT SIGNIFICANT
UES WHEN THAT ISSUES WHEN THAT
RK FALLS ON A WORK FALLS ON A
I M AG E S O U R C E : T H I N K W I T H G O O G L E
ER’S BROWSER USER’S BROWSER
SEARCH ENGINE OR SEARCH ENGINE
22 Google Webmaster Central Blog, https://
AWLER. webmasters.googleblog.com/2014/05/understanding-web-pages- CRAWLER.
better.html, 23rd May 2014

23 Google Web Fundamentals, https://developers.google.com/web/

fundamentals/performance/optimizing-content-efficiency/
javascript-startup-optimization/, 2nd July 2018
34
 I M AG E S O U R C E : G O O G L E D E V E LO P E R S

It’s important to perform the required research

to understand what your users’ browsing and
network conditions are first to be able to
optimise for them accordingly. To get a sense of
what these are, the ‘Audience’ tab in Google
Analytics is a great place to start looking. The
‘Devices’ report will show details such as the
specific devices that are most commonly used
to view your website.

35
2
Main thread activity
JavaScript is single-threaded, meaning that each command is run one at a time on the browser’s main
thread of activity. The entire main thread is halted while JavaScript is parsed, compiled and executed. With
this kind of setup, queues can form and bottlenecks can happen, meaning that the entire process of loading
a page can be delayed.

Delays within the main thread can significantly increase the time it takes to load a page and for it to become
interactive for users, so avoid blocking main thread activity wherever possible. Keep an eye on how many
resources are being executed and where request timeouts are happening, as these can be some of the
main culprits which create bottlenecks.

3
Conflicting signals between HTML and JavaScript
Adding important meta tags using JavaScript is The signals you provide via JavaScript
advised against because either Google won’t shouldn't conflict with the ones in the
see these tags straight away because of its
HTML.
delayed rendering process, or other search
engines won’t see them at all due to the fact
John Mueller,
that they can’t render. 24
Google Webmaster Hangout
All search engines will use the signals from the
HTML in the initial fetch to determine crawling
For example, if you use JavaScript to remove a
and indexing. Google and the few search
robots meta tag like noindex, Google will have
engines that have rendering capabilities will
already seen the noindex tag in the HTML and
then render pages at a later date, but if the
won’t waste resources rendering a page it has
signals served via JavaScript differ from what
been told not to include in its index. This means
was initially found in the HTML, then this will
that the instructions to remove the noindex
contradict what the search engine has already
won’t even be seen as they’re hidden behind
been told about the page.
JavaScript which won’t be rendered.

24 DeepCrawl, https://www.deepcrawl.com/blog/news/google-webmaster-hangout-notes-june-26th-2018/, 26th June 2018 36

 Avoid using Google Tag Manager to Some website owners have to find a
implement critical tags like noindex. workaround for this, however, as they may not
be able to edit the HTML through their CMS.
Even though adding meta tags using JavaScript
John Mueller, isn’t recommended, it can work as a last resort.
25
Google Webmaster Hangout

“Google has recently announced that

Aim to include the most important tags and
canonical tags are not processed if they’re
signals within the HTML where possible and
make sure they’re not being altered by only found in the rendered HTML and not
JavaScript. This includes page titles, content,
in the HTML source document. We tested
hreflang and any other elements that are used
for indexing. this by injecting canonical tags into four

URLs using GTM and our test results

suggest that Google does use these

canonical tags. It took more than three

weeks for some of the tested URLs to be

canonicalised to the targets of the

JavaScript-injected canonical tags.”

FIRST
Eoghan Henn,
IMPRESSIONS
Co-founder of
COUNT WITH searchVIU
26

SEARCH ENGINES,
SO MAKE SURE
YOU’RE GIVING
THEM CLEAR,
STRAIGHTFORWAR
D INSTRUCTIONS IN
THE HTML AS SOON
AS THEY COME
ACROSS THE PAGE.

25 DeepCrawl, https://www.deepcrawl.com/blog/news/google-webmaster-hangout-notes-september-4th-2018/, 4th September 2018

26 searchVIU, https://www.searchviu.com/en/javascript-canonical-tags/, 5th June 2018 37

4
Blocked scripts
If a script is blocked, such as in the robots.txt, “If resources like JavaScript or CSS in
this will impact how search engines will be able separate files are blocked (say, with
to see and understand a website. Scripts that
robots.txt) so that Googlebot can’t retrieve
are crucial to the layout and content of a page
them, our indexing systems won’t be able
need to be accessible so that the page can be
to see your site like an average user. This is
rendered properly.
especially important for mobile websites,
where external resources like CSS and
Blocking scripts for Googlebot can impact
JavaScript help our algorithms understand
its ability to render pages.
that the pages are optimized for mobile.”

John Mueller, 28

27 Google Webmaster Central Blog

Google Webmaster Hangout

“The robots.txt file must allow scanning

This is especially important for mobile devices,
as search engines rely on being able to fetch CSS and Javascript that are responsible for
external resources to be able to display mobile displaying the site on mobile devices.
results correctly. Otherwise, the site pages might be
displayed incorrectly in the search results.”

29

Yandex Support

5
Scripts in the head

When JavaScript is served in the head, this can delay the rendering and loading of the entire page. This is
because everything in the head is loaded as a priority before the body can start to be loaded.

Don't serve critical JavaScript in the head as this can block rendering.

John Mueller,
30
Google Webmaster Hangout

27 DeepCrawl, https://www.deepcrawl.com/blog/news/google-webmaster-hangout-notes-june-1st-2018/, 1st June 2018

28 Google Webmaster Central Blog, https://webmasters.googleblog.com/2014/05/understanding-web-pages-better.html, 23rd May 2014

29 Yandex Support, https://yandex.com/support/webmaster/recommendations/mobile-site.html, 13th February 2019 (last accessed)

30 DeepCrawl, https://www.deepcrawl.com/blog/news/google-webmaster-hangout-notes-october-30th-2018/, 30th October 2018 36

38
 Serving JavaScript in the head is also advised against because it can cause search engines to ignore any
other head tags below it. If Google sees a JavaScript tag within the contents of the head, it can assume that
the body section has begun and ignore any other elements below it that were meant to be included in the
head.

JavaScript snippets can close the head prematurely and cause any elements below to be
overlooked.

John Mueller,
31
Google Webmaster Hangout

6
Content duplication
JavaScript can cause duplication and “If you're using a SPA-type setup where the
canonicalisation issues when it is used to serve
content. This is because if scripts take too long
static HTML is mostly the same, and
to process, then the content they generate JavaScript has to be run in order to see any
won’t be seen. This can cause Google to only
of the unique content, then if that
see boilerplate, duplicate content across the
site, meaning it won’t be able to find any unique JavaScript can't be executed properly, then
content to rank pages with. This can often be
the content ends up looking the same. This
an issue for Single Page Applications (SPAs)
where the content dynamically changes without is probably a sign that it's too hard to get to
having to reload the page. your unique content -- it takes too many

requests to load, the responses (in sum

across the required requests) take too long

to get back, so the focus stays on the

boilerplate HTML rather than the JS-loaded

content.”

John Mueller,
32
Webmaster Trends Analyst at Google

31 DeepCrawl, https://www.deepcrawl.com/blog/news/google-webmaster-hangout-notes-october-19th-2018/, 19th October 2018

32 Reddit, https://www.reddit.com/r/TechSEO/comments/ag77vi/canonicals_and_angular_js/, 21st January 2019 39

7
User events
JavaScript elements that require interactivity Google doesn't handle all onclick events.
may work well for users, but they don’t for
search engines. Search engines have a very John Mueller,
different experience with JavaScript than a 33
Google Webmaster Hangout
regular user. This is because search engine
bots can’t interact with a page in the same way
that a human being would. They don’t click, Another thing to bear in mind is that Googlebot
scroll or select options from menus. Their main and the other search engine crawlers don’t use
purpose is to discover and follow links to or store things like cookies, so this will be a
content that they can add to their index. problem for website owners who rely on
cookies to serve any kind of personalised,
This means that any content that depends on unique content that they want to have indexed.
JavaScript interactions to be generated won’t Cookies, local storage and session storage are
be indexed. For example, search engines will all cleared by search engines after each page
struggle to see any content hidden behind an load.
‘onclick’ event, which tells the browser to run a
particular script once the user clicks.
“Any features that requires user consent
are auto-declined by Googlebot.”

34

Google Search

8
Service workers
A service worker is a script that works in the background of the browser and on a separate thread. Service
workers can run pages and provide content based on their own memory, meaning they can work offline
without the server being involved.

“A service worker is a script that your browser runs in the background, separate from a web page,
opening the door to features that don't need a web page or user interaction. Today, they already
include features like push notifications and background sync.”

35
Google Web Fundamentals

33 DeepCrawl, https://www.deepcrawl.com/blog/news/google-webmaster-hangout-notes-may-16th-2017/, 16th May 2017

34 Google Search, https://developers.google.com/search/docs/guides/rendering, 1st October 2018

35 Google Web Fundamentals, https://developers.google.com/web/fundamentals/primers/service-workers/, 12th February 2019 40

36
The benefit of using a service worker is that it decreases page load time because it doesn’t reload assets
that aren’t needed. However, the issue is that Google and other search engine crawlers don’t support
service workers. The service worker can make it look like content is rendering correctly, but this may not be
the case. Make sure your website and its key content still works properly without a service worker, and test
your server configuration to avoid this issue.

Testing how your We also need to learn how Google deals

with these differences and which
website renders mechanisms it applies when crawling and
indexing the web. More work needs to be

We’ve explored the different pitfalls of

done to analyse differences in the
JavaScript-powered websites to watch out for, frequencies of HTML crawling and
but how do you know if these issues are rendering. Solutions have to be developed
impacting your website? Thorough testing and
for better tracking Google's crawling and
auditing is essential for demystifying how your
rendering activity. This will help with
site renders and determining what is and isn’t
available for the different rendering capabilities understanding how and when changes that
of users and search engines. are only made to the rendered version of a
page, but not to the source HTML, can
have an impact on Google's search results.
“We have to change the way we analyse
websites technically and also the way we
The SEO industry as a whole faces the
think about crawling and indexing. A few
same issues as Google when it comes to
years ago, we would disable JavaScript in
keeping up with the rapid pace that web
our browser to get an idea of how Google
development is evolving at. We need to
"saw" the websites we were working on.
keep moving fast, in order to be able to
Now, we have to be aware of the
continue delivering outstanding results.”
differences between the raw HTML we find
at "show source code" and the rendered
HTML we find at "inspect" in our browsers Eoghan Henn,
and how these differences affect the Co-founder of searchVIU
crawling and indexing of our websites.

41
 What to test for
When running a JavaScript audit for a website,
it’s important to focus on these main areas:

Differences in the HTML content before

and after the DOM is rendered: Make sure
key content is included in the DOM before
rendering, and check that JavaScript isn’t
removing any of your content or links after
rendering.

“Some JavaScript removes content from

the page rather than adding it, which
prevents us from indexing the content.”

36

Google Webmaster Central Blog

Check that URLs and content are being

indexed: Use the site: or site: “” command
to see if the URL itself or a section of text
from the page is being indexed. Try this in
incognito mode too in case caching affects
the results.

Test rendering on different devices: Pay

attention to the rendering capabilities of the
devices most commonly used by your site’s
visitors, especially the ones with lower-end
CPUs. These tests will also show how
dynamically rendered content appears for
different devices and viewports.

Google’s crawling and rendering capacity:

Look at log file data to see where Google
and other search engines are having
difficulty in accessing your pages that rely
on JavaScript. Compare which ones can
crawl normally and which ones are
struggling.

36 Google Webmaster Central Blog, https://webmasters.googleblog.com/2014/05/understanding-web-pages-better.html, 23rd May 2014 42

 The speed of rendering: If it takes too long
for the resources on a page to be rendered,
this will impact user experience and prevent
Google from being able to index your
content

“If you're sure that your code works for

ME OF THE KEY SOME OF THE KEY
Googlebot (a quick way to test is the
NGS TO WATCH
mobile-friendly test), then it's worth THINGS TO WATCH
T FOR WHEN
estimating if speed of processing might be OUT FOR WHEN
TING an issue. My way of eyeballing it is to see TESTING
how
NDERING ARE long the mobile-friendly test roughly RENDERING ARE
takes, and to check with webpagetest.org
FERENCES DIFFERENCES
to see how long a page might take to load
TWEEN BETWEEN
the critical / unique content, and how many
RENDERED AND
resources are required to get there. The
UNRENDERED AND
NDERED more resources required, the longer time RENDERED
NTENT, until the critical content is visible, the more CONTENT,
likely Google will have trouble indexing the
NDERING SPEED RENDERING SPEED
critical
D INDEXING content.” AND INDEXING
UES. ISSUES.
John Mueller,
37
Webmaster Trends Analyst at Google

Tools for analysing JavaScript

Here is a list of 10 of the main tools you can use to analyse and debug JavaScript issues on your site:

URL Inspection Tool Google Search Console Chrome DevTools

Mobile-friendly Test PageSpeed Insights Web Developer Extension

Rich Results Test Diffchecker WebPageTest

DeepCrawl

For more detail on each of these tools and their highlight features, take a look at this guide on tips and
tools for testing rendering.

37 Reddit, https://www.reddit.com/r/TechSEO/comments/ag77vi/canonicals_and_angular_js/, 21st January 2019 43

 URL Inspection Tool

ASCRIPT Google’s URL Inspection Tool shows details JAVASCRIPT

DERING about the issues preventing a page from being RENDERING
indexed, as well as what Google found when it
SN’T HAVE TO
tried to crawl and render a page. You can even
DOESN’T HAVE TO
AIN A run live tests for URLs to see how Google REMAIN A
handles them in real-time. This is helpful to be
TERY. THERE MYSTERY. THERE
able to test because Google’s index often uses
A NUMBER OF
caching so it can be difficult to see if particular ARE A NUMBER OF
fixes have worked.
LS OUT THERE TOOLS OUT THERE
T CAN HELP THAT CAN HELP
When you run a live test of a URL, you can see
ANALYSEresources
AND that were blocked as well as YOU ANALYSE AND
UG JavaScript
JAVASCRIPT errors that were encountered. This DEBUG JAVASCRIPT
section of the tool is especially useful for
YOUR SITE.
debugging.
ON YOUR SITE.

44
 The JavaScript console messages even provide stack trace reports which allow developers to see where
errors are happening in the code and debug them.

Remember that the results you see from Google’s tools may not reflect real rendering. These tools have a
shorter timeout as they aim to give results to their users as quickly as possible. Google’s indexing systems
will wait for a page to render for a longer period of time.

Google's indexing systems are more patient with rendering than the live testing tools are.

John Mueller,
38
Google Webmaster Hangout

Mobile-friendly Test

The Mobile-friendly Test shows the rendered HTML of a page so you can check that everything is showing
properly and making sense for Google. It lists different elements that could negatively impact how your site
appears on mobile devices, such as blocked resources and JavaScript errors.

38 DeepCrawl, https://www.deepcrawl.com/blog/news/google-webmaster-hangout-notes-july-10th-2018/, 10th July 2018 45

46
 Use the mobile-friendly test and the Googlebot user agent in the browser to check for rendering
issues.

John Mueller,
39
Google Webmaster Hangout

39 DeepCrawl, https://www.deepcrawl.com/blog/news/google-webmaster-hangout-notes-december-14th-2018/, 14th December 2018 47

 Rich Results Test

The Rich Results Test can also be used to see how Google renders a page and how it handles different
JavaScript frameworks. This tool can be used for testing rendering on a page-by-page basis.

Test JavaScript frameworks with the Rich Results feature in Google Search Console.

John Mueller,
40
Google Webmaster Hangout

40 DeepCrawl, https://www.deepcrawl.com/blog/news/google-webmaster-hangout-notes-april-6th-2018/, 6th April 2018 48

Google Search Console

The Index Coverage report in Google Search Console is useful for getting an overview of what is and isn’t
being indexed on a website. Whereas some of Google’s other tools can provide granular information on
errors at a page-level, this top-level view can give valuable insights into more widespread issues with
JavaScript that could be impacting indexing across the site.

PageSpeed Insights

The PageSpeed Insights tool has been revamped to include Lighthouse data and a variety of new
performance and JavaScript-related reports. The ‘Opportunities’ and ‘Diagnostics’ sections show key issues
that need to be addressed, as well as how much time could be saved on page load time if they were fixed.

49
Diffchecker

Diffchecker allows you to analyse the differences between the unrendered source code of a page side by
side against the rendered DOM. This allows for detailed comparisons between rendered and unrendered
content on a page-by-page basis.

50
You can copy the HTML that is shown once you right click and select ‘View Page Source’ in the browser and
paste this in the ‘Original Text’ box in Diffchecker. Then copy the ‘outerHTML’ after right clicking in the
browser and selecting ‘Inspect’, and paste this code in the ‘Changed Text’ box. Diffchecker will then show
you any differences between the two sets of code.

I M AG E S O U R C E : P O L E M I C D I G I TA L

You can also compare the difference between

the unrendered and rendered code that Google
displays in the URL Inspection Tool. Firstly, copy
all of the ‘Crawled page’ HTML and paste it into
the ‘Original Text’ section in Diffchecker. This is
the source code.

Then copy all of the ‘Tested page’ HTML and

paste it into the ‘Changed Text’ section. This is
the rendered HTML.

51
Chrome DevTools

Chrome DevTools can be used to debug and edit pages within the Chrome browser. By right clicking on a
page when viewing it and clicking ‘Inspect’, the DevTools dock will appear with a wide variety of analysis
options, such as monitoring performance and network conditions as well as showing JavaScript and
resource errors.

The ‘Performance’ tab shows a log of the

activity that occurs when a page is loaded,
including a summary of how long is spent
loading, scripting, rendering and painting the
page. Watch out for spikes in orange and purple
within your page’s loading activity, as these
colours relate to scripting and rendering
respectively.

52
 The waterfall under the
‘Network’ tab shows exactly
which scripts were run and in
which order, visualising
dependencies and roadblocks
to be addressed. This is a
really useful report as you can
see the Load Event as a red
line, which is the point when
Google determines that
rendering has been
completed and takes a
snapshot of the rendered
HTML. Any content produced
by resources that load after
this point may not be seen.
Focus on getting key content
to load before this red line so
Google won’t miss it.

JavaScript-powered content is
indexed depending on
whether it is visible to
Googlebot on page load.

John Mueller,
Google Webmaster
41
Hangout

You can also test how

JavaScript executes in the
browser by running particular
snippets. Select ‘Sources’ and
‘Snippets’ to add and observe
how the code affects a page.

41 DeepCrawl, https://www.deepcrawl.com/blog/news/google-webmaster-hangout-notes-august-11th-2017/, 11th August 2017 53

Chrome DevTools can also be
used to find unused JavaScript
code. This is incredibly useful
for highlighting what users
actually need from a page and
areas where the amount of
code can be trimmed down to
speed up the page. The
‘Coverage’ tab shows how
many unused bytes there are,
as well as a comparison
between how much JavaScript
was executed as opposed to
how much was actually
loaded.

You can even test how your

website renders across
different devices with the
‘Device Mode’ in Chrome
DevTools. I M AG E S O U R C E : T W I T T E R

Select from a list of different

devices, or even add your own
custom devices to test.

54
Chrome isn’t the only browser that provides JavaScript debugging functionality, there are also developer
tools available for the main browsers such as Firefox, Opera and Safari, so you should be able to find a
solution for JavaScript analysis that works for you.

I M AG E S O U R C E : F I R E F OX D E V E LO P E R T O O L S

55
O P E R A D E V E LO P E R T O O L S . S O U R C E : R AYG U N

S O U R C E : S A FA R I D E V E LO P E R T O O L S

56
Web Developer Extension

An easy way to see what works and what doesn’t work without JavaScript rendering is to use the Web
Developer Extension to disable JavaScript in the browser. This will show you what can function and be
displayed in the browser without the page being rendered. This extension can be used on Chrome, Firefox
and Opera.

WebPageTest

WebPageTest provides insights into the different types of resources on a page and how quickly they are
able to be processed. This tool can give you an idea of how much time is spent on which stages of
JavaScript rendering on a page-by-page basis, so you can spot patterns of performance issues and
bottlenecks.

57
The ‘Request Map’ is a great feature as it shows all of the different requests made on a page and the
dependencies between them. Each circle is a different request and you can see what type of resource each
one is when you hover over them, such as JavaScript or an image. The larger the circle, the longer the
request took. For example, the large green circle in this request map is a JavaScript file which had the
longest load time for the page.

DeepCrawl

DeepCrawl is a website crawler which can render JavaScript like search engines can by using its own Page
Rendering Service (PRS). This allows you to monitor rendering and resource issues at scale, rather than
having to analyse them on a page-by-page basis. The tool shows you whether or not links and content
modified by JavaScript can be crawled and indexed by search engines.

With JavaScript rendering enabled in the project setup, you’ll be able to see reports on the number of
JavaScript files you have on your site, broken or disallowed JavaScript files, JavaScript redirects and more.

58
The key things to watch out for within your
crawls are thin pages and low internal linking as
this gives an indication of important elements
that are being hidden from search engines.
Also, watch out for pages that exceed the
maximum file size as this could prevent
browsers and search engines from being able
to process them.

You can run comparison crawls with and without

JavaScript enabled to compare how much
content and how many links couldn’t be found
without the crawler rendering JavaScript. This
highlights the pages that are most at risk of
performance issues for the search engines and
social media platforms that can’t render.

Bonus tip: Use the Tasks Manager to set up

email alerts for key metrics around low word
counts, low numbers of internal links and
maximum page file size, so you can be the first
to spot rendering issues before they start
impacting users and search engines.

DeepCrawl also has a custom JavaScript

feature which allows you to either inject
changes or remove things from DOM while the
tool is crawling your site. This feature can be
used to report on a number of JavaScript
issues, such as:

Speed and performance metrics

Which frameworks are being used

Iframes and scripts in the head

External files

Resource counts

To find out more about DeepCrawl’s JavaScript

rendering capabilities, simply get in touch with
Try out DeepCrawl for free
our team. If you want to try out these features
yourself then take out a free trial on us, or sign
up for an account.

59
“A reliance on client-side JavaScript means a delayed and inefficient indexing process, plus a
plethora of related repercussions such as poor flow of internal link value and potential conflicts
between pre- and post-rendered content.

The best solution is to prevent the problem entirely in the first place. Make sure a webpage's
content, links, and relevant meta data is present in the raw HTML source and doesn't rely on any
client-side JavaScript. Progressive Enhancement is a great approach, where the webpage's base
content is in the HTML and JavaScript is then used to enhance the page's functionality.

To test how your site's reliance on JavaScript could impact on your SEO, you
can use crawling tools that allow you to compare raw HTML to rendered code
(such as DeepCrawl). Significant variances between the HTML and fully
rendered page could point to possible problems with Google's crawling and
indexing of your site.”

Barry Adams,
Founder of Polemic Digital

Optimisation tips for JavaScript-

powered websites
Now that we know the main areas in which 1 Prioritise your most important
JavaScript can negatively impact websites in content and resources.
search, let’s explore some of the ways you can
optimise your website and make sure it
2 Provide options for clients that can’t
render fully.
performs for both users and search engines.

3 Use clean URLs, links and markup.

Here are 5 key pieces of advice for optimising
your JavaScript-powered website: 4 Reduce file transfer size.

5 Enhance JavaScript performance.

60
 1
Prioritise your most
important content and
resources
Sending JavaScript to the browser or search
engine all at once in the initial request to be
rendered client-side is a bad idea. This is a big
ask even for users with higher-end devices and
Google which has relatively sophisticated
rendering capabilities.

ORITISINGInstead,
THE focusing on the core content of the PRIORITISING THE
page, such as the above-the-fold, hero content
ST IMPORTANT MOST IMPORTANT
and making sure that it is available first as a
NTENT ONpriority,
A is a much better strategy. CONTENT ON A
E TO LOAD PAGE TO LOAD
Here are some solutions to look into for helping
ST CAN FIRST CAN
to prioritise key resources:
MATICALLY DRAMATICALLY
ROVE THE IMPROVE THE
Optimise the critical rendering path: Make
R’S sure that none of the most important USER’S
CEPTION resources
OF on a page are being blocked and PERCEPTION OF
that they can render as soon as possible.
D TIME. LOAD TIME.

“A critical resource is a resource that could

block initial rendering of the page. The
fewer of these resources, the less work for
the browser, the CPU, and other
resources.”

Ilya Grigorik,
Web Performance
42
Engineer at Google

42 Google Web Fundamentals, https://developers.google.com/web/fundamentals/performance/critical-rendering-path/optimizing-critical-rendering-path,

12th February 2019 61
 Utilise async and defer loading: Using the Implement progressive enhancement:
async and defer attributes allows the DOM Focuses on the core content of a page
to be constructed before being interrupted first, then progressively adds more
by the loading of scripts. Non-essential technically advanced features on top of
scripts are downloaded lazily in the that if the conditions of the client allow for
background, keeping the critical rendering this. This means that the main content is
path unblocked. accessible to any browser or search
engine requesting it, no matter what their
rendering capabilities are.
“Async scripts will download the script
without blocking rendering the page and
“Rather than copying bad examples from
will execute it as soon as the script finishes
the history of native apps, where
downloading. You get no guarantee that
everything is delivered in one big lump, we
scripts will run in any specific order, only
should be doing a little with a little, then
that they will not stop the rest of the page
getting a little more and doing a little more,
from displaying. It is best to use async
repeating until complete. Think about the
when the scripts in the page run
things users are going to do when they
independently from each other and depend
first arrive, and deliver that. Especially
on no other script on the page.”
consider those most-likely to arrive with

43
empty caches.”
MDN Web Docs

Jake Archibald,
44

Developer Advocate at Google

43 MDN Web Docs, https://developer.mozilla.org/en-US/docs/Learn/JavaScript/First_steps/What_is_JavaScript, 31st January 2019

44 Jake Archibald, https://jakearchibald.com/2017/netflix-and-react/, 31st October 2017 62

 2
KE SURE Provide
YOUR options for MAKE SURE YOUR
BSITE WORKS,
clients that can’t WEBSITE WORKS,
CHES AND CACHES AND
render fully
NDERS FOR THE RENDERS FOR THE
OST BASICAs we’ve discussed earlier in this guide, not MOST BASIC
every client will be able to render fully. This is
OWSER, DEVICE BROWSER, DEVICE
why it’s important to make sure that your pages
CRAWLER, AND
are still usable without needing to be able to OR CRAWLER, AND
S A run
BASELINEthe latest JavaScript features. HAS A BASELINE
VEL OF This process is referred to as graceful
LEVEL OF
RFORMANCE
degradation, meaning that the website or PERFORMANCE
application will fall back to a less complex
AT WORKS FOR THAT WORKS FOR
experience if the client is unable to handle
ERYONE. some of the latest JavaScript features. EVERYONE.

“It's always a good idea to have your site

degrade gracefully. This will help users
enjoy your content even if their browser
doesn't have compatible JavaScript
implementations. It will also help visitors
with JavaScript disabled or off, as well as
search engines that can't execute
JavaScript yet.”

45
Google Webmaster Central Blog

An example of this is using transpiling to allow

Google’s WRS, which uses Chrome 41, to be
able to process modern ES6 JavaScript code.
ECMAScript (ES) is a scripting language that
was created to standardise JavaScript. Different
versions are released as the language evolves Google’s rendering service doesn't support
and updates, such as ES5 and ES6. Google’s ES6 as Chrome 41 is used for rendering.
WRS doesn’t support ES6 as this version was
launched after Chrome 41, so a transpiling tool
can be used to transform it into ES5 which John Mueller,
46
Google will be able to process. Google Webmaster Hangout

45 Google Webmaster Central Blog, https://webmasters.googleblog.com/2014/05/understanding-web-pages-better.html, 23rd May 2014

46 DeepCrawl, https://www.deepcrawl.com/blog/news/google-webmaster-hangout-notes-july-27th-2018/, 27th July 2018 63

 “With regards to the discussion surrounding "JavaScript vs. SEO", it should first be clearly stated
that JavaScript is not “bad” per se. However, the use of JavaScript certainly increases the
complexity in terms of search engines, as well as web performance optimisation.

Essentially, SEOs should ensure that there is a version of their website available that works
without JavaScript. This could be achieved, for example, by using Puppeteer which is a Node
library that can be used to control a headless Chrome browser. This browser could then be used
to crawl either a JavaScript-heavy website or even a single page JavaScript application and as a
result, generate pre-rendered content.

As it currently stands, choosing to rely heavily on JavaScript should be carefully

considered – it’s not impossible to rank JavaScript-powered sites, nor is it
impossible to make them fast, however, be aware that it adds a great deal of
complexity on many different levels, all of which needs to be dealt with!”

Bastian Grimm,
Director of Organic Search at
Peak Ace AG

Graceful degradation doesn’t just benefit Google, it also helps

other search engines like Bing that struggle with rendering.

“The technology used on your website can sometimes prevent Bingbot from being able to find
your content. Rich media (Flash, JavaScript, etc.) can lead to Bing not being able to crawl through
navigation, or not see content embedded in a webpage. To avoid any issue, you should consider
implementing a down-level experience which includes the same content elements and links as
your rich version does. This will allow anyone (Bingbot) without rich media enabled to see and
interact with your website.”

47
Bing Webmaster Guidelines

47 Bing Webmaster Guidelines, https://www.bing.com/webmaster/help/webmaster-guidelines-30fba23a, 5th February 2019 (last accessed) 64

 3
Use clean URLs, links
and markup
Each page should have a unique, indexable
URL which shows its own content. JavaScript
can complicate this, however, as it can be used
to dynamically alter or update the content and
links on a page which can cause confusion for
search engines.
SOURCE: SBLUM

Make sure your website is using only clean links

with the <a href> attribute so that they are
discoverable and clear for search engines to
follow and pass on signals to. Using <a> tags for
KE SURE URLS, MAKE SURE URLS,
links also helps people browsing with assistive
KS AND technologies, not just search engine crawlers. LINKS AND
RKUP AREN’T MARKUP AREN’T
This also applies to markup, so make sure key
VED VIA markup is structured clearly and displayed in
SERVED VIA
ASCRIPT the
AND HTML where possible for search engines. JAVASCRIPT AND
This includes:
T THEY’RE THAT THEY’RE
ARLY CLEARLY
Page titles
ESSIBLE IN THE ACCESSIBLE IN THE
Meta descriptions
ML, SO SEARCH HTML, SO SEARCH
Canonical tags
INES CAN FIND ENGINES CAN FIND
Robots meta tags
D PROCESS AND PROCESS
Alt attributes
M. THEM.
Image source attributes

Check that these are in place using ‘Inspect’ in

the browser.

65
 Here’s what Google’s Martin Splitt recommends for optimising web apps for
search engines and users:

1 “Use good URLs: URLs should be reliable, user-friendly and clean.

2 Use meaningful markup: Use clean links and clear page title, meta
description and canonical tags.

3 Use the right HTTP status codes: Avoid soft 404s so Google can serve the
right pages.

4 Use structured data: This will help search engines better understand your
content.

5 Know the tools: Test your content with the

Mobile-friendly Test, Structured Data Testing Tool
and Google Search Console.”

Martin Splitt,
Webmaster Trends
48
Analyst at Google

4
Reduce file transfer size
Reducing the file size of a page and its resources where possible will improve the speed with which it can
be rendered. You can do this by making sure that only the necessary JavaScript code is being shipped.

Some ways of reducing file size are:

Minification: Removing redundant code that has no function, such as whitespace or code comments.

Compression: Use GZIP or zlib to compress text-based resources. Remember that even if something is
initially compressed, it will still have to be unzipped and downloaded.

Code splitting: This involves dividing long, expensive tasks into smaller ones so the main thread doesn’t
become blocked and is still able to react to user interactions. This increases the perceived speed of a
page for users.

48 AngularUP Conference, https://www.youtube.com/watch?v=Z9mHopLeE40, 17th October 2018 66

 “To stay fast, only load JavaScript needed for the current page. Prioritize what a user will need
and lazy-load the rest with code-splitting. This gives you the best chance at loading and getting
interactive fast.

Learn how to audit and trim your JavaScript bundles. There’s a high chance
you’re shipping full-libraries when you only need a fraction, polyfills for
browsers that don’t need them, or duplicate code.”

Addy Osmani,
49
Engineering Manager at Google

SHIP LESS CODE WITH A SMALLER FILE SIZE SO THERE IS LESS

FOR BROWSERS AND SEARCH ENGINES TO HAVE TO DOWNLOAD
AND PROCESS.

5
Enhance JavaScript performance
JavaScript doesn’t have to dramatically decrease site speed; there are things you can do to optimise
the performance of the JavaScript on your website. Enhancing JavaScript performance should be a
focus topic for developers and SEOs alike going forwards. Here are some methods to potentially
implement on your site:

Cache resources: This is especially helpful for users making repeat visits and server-side rendered or
dynamically rendered content, as too many pre-render requests at once can slow down your server.

Preload resources: This allows you to tell the browser which scripts and resources are the most
important and should be loaded first as a priority.

Prefetch links: This allows the browser to proactively fetch links and documents that a user is likely to
visit soon within their journey, and store them in its cache. This means that the resource will load very
quickly once a user goes to access it.

49 Medium,https://medium.com/@addyosmani/the-cost-of-javascript-in-2018-7d8950fbb5d4, 1st August 2018 67

Implement script streaming: This can be used to parse scripts in the background on a different thread to
prevent the main thread from being blocked.

Use the PRPL pattern: This method is an acronym for the different elements that its process is made up
of: Push, Render, Pre-cache and Lazy-load. The PRPL pattern is recommended for improving
performance and load times on mobile devices especially.

S O U R C E : G O O G L E W E B F U N DA M E N TA L S

USE METHODS SUCH AS CACHING, PREFETCHING AND

PRELOADING TO MAKE ANY NECESSARY JAVASCRIPT
CODE MORE PERFORMANT AND LOAD FASTER.

68
 In conclusion
SEOs and developers need to learn to work “SEOs need to stay ahead of the curve
better together to get their websites when it comes to JavaScript. This means a
discovered, crawled and indexed by search
lot of research, experimentation, crunching
engines, and, therefore, seen by more users.
Both departments have a lot of influence over data, etc. It also means being ready for the
the different aspects of this process and we next big thing that probably dropped
share common goals of serving optimised yesterday and you now need to adapt to,
websites that perform well for both search
whether it’s Google finally updating its
engine bots and humans.
rendering browser or one of the countless
JavaScript frameworks suddenly becoming
popular among developers.”

Bartosz Góralewicz,
50

JavaScript rendering and page loading can be Co-founder of Elephate

an expensive, time-consuming process, but it
can be tailored to either the user or search
The best way to make sure your JavaScript-
engine to help them achieve their main goals.
powered website or application performs as it
For users, you can prioritise what they need
should, is to conduct regular JavaScript audits
immediately as they’re browsing to load first
looking at the key issues laid out in this guide.
and increase perceived site speed. For search
Keep crawling, monitoring and testing your
engines, you can provide alternative rendering
website for rendering speed, blocked scripts
methods such as server-side rendering to make
and content differences between the
sure they can access your core content despite
unrendered and rendered content. This way
their limited rendering capabilities.
you can keep on top of any issues that are
putting a roadblock between users and search
The landscape of JavaScript is constantly
engines, and your website’s content.
evolving and we all need to do our part to keep
up and learn more about it, for the sake of our
websites’ health and performance.

50 DeepCrawl, https://www.deepcrawl.com/blog/events/bartosz-goralewicz-js-q-and-a/, 9th July 2018 69

 Address: Website:
DeepCrawl www.deepcrawl.com
29 Throgmorton Street
We don’t believe in fads, we believe in building London Email:
EC2N 2AT [email protected]
solid foundations which you can build upon. In
our opinion, your site’s architecture is the Phone: Twitter:
foundation needed for optimal SEO (UK) 020 7947 9617 @DeepCrawl
performance. (US) +1 929 294 9420
LinkedIn:
https://www.linkedin.com/
Originally there were no options out there for company/deepcrawl
crawling the largest, hardest-to-manage
websites, so our founders created a new, tailor-
made tool that could meet their needs from an About the Author
SEO perspective. DeepCrawl was built by SEOs
for SEOs. Rachel Costello is a Technical SEO & Content
Manager at DeepCrawl and spends her time
We aim to build a comprehensive search researching and communicating the latest
marketing platform with a unified vision by developments in search, as well as driving the
delivering, growing and innovating together DeepCrawl brand forwards.
with the marketing community.

70