This document discusses various approaches to JavaScript rendering and SEO. It begins by discussing the limitations of prerendering/dynamic rendering, noting that it creates duplicate content and outdated pages. It then discusses alternatives like server-side rendering, hybrid rendering, and static site generators that can improve the user experience. The document cautions against relying solely on prerendering and recommends approaches like server-side rendering that allow search engines to properly index the JavaScript content.
Report
Share
Report
Share
1 of 85
Download to read offline
More Related Content
Dynamic Rendering - is this really an SEO silver bullet? SMX WEST
1. #SMX @Bart_Goralewicz
With Bartosz Goralewicz
Dynamic Rendering
Is this really an
SEO silver bullet?
Experiences from setting up
the world's biggest
prerendering engine.
18. #SMX @Bart_Goralewicz
ele.ph/angularU
If you search for any competitive keyword terms, it’s always going to
be server rendered sites. And the reason is because although
Google does index client-side rendered HTML it’s not perfect yet and
other search engines don’t do it as well. So if you care about SEO,
you still need to have server-rendered content.
Jeff Whelpley “Angular 2 Server Rendering”
Angular U conference, June 22-25, 2015,
45. #SMX @Bart_Goralewicz
What if you HAVE TO do
prerendering
Plan your updates and deployments1.
Make sure that your prerendering setup is efficient2.
Remember that you need to crawl and optimize
both HTML and JavaScript versions of your website
3.
50. #SMX @Bart_Goralewicz
Source Code
(before JavaScript):
Disqus -The #1 way
to build your audience
Rendered website:
(after JavaScript):
Disqus -The #1 way to build an
audience on your website
56. #SMX @Bart_Goralewicz
Not too dynamic (pun intended)
Creates two separate structures instead of one
Doesn’t improve UX.
Adds an extra layer of complexity
May work well BUT rarely does. Requires a very good SEO team maintaining it.
WORKAROUND!
Dynamic Rendering - summary
57. #SMX @Bart_Goralewicz
My personal beef
with dynamic rendering
It is only made for the sake of SEO.
It doesn’t improve anything for users…
66. #SMX @Bart_Goralewicz
Yes, Google
recommends it!
„If you have engineering resources though,
I would highly recommend looking into
server-side rendering or even better,
hybrid rendering, because that yields
user experience benefits, as well.”
67. #SMX @Bart_Goralewicz
Next, Nuxt and Angular Universal
are the next (amazing joke) trend!
35% of JS developers
want to learn Next.js
68. #SMX @Bart_Goralewicz
Twitter migrated to
isomorphic JavaScript
in 2012
https://www.oreilly.com/library/view/building-isomorphic-
javascript/9781491932926/ch01.html
– Initial page load decreased 80% (!)
69. #SMX @Bart_Goralewicz
All the HTML files are built with data
BEFORE they are uploaded to a server
Static Site Rendering
Source: https://www.youtube.com/watch?v=3jeznGJHenI
GatsbyJS
NextJS
70. #SMX @Bart_Goralewicz
Pros of
static sites
1.Very fast (even during traffic surge)
2. Increased security
3.Version control
4. Cheap to host
Source: https://www.youtube.com/watch?v=3jeznGJHenI
83. #SMX @Bart_Goralewicz
Get the Starter
Package for FREE
Contact maria@elephate.com
Give the password ”Freelephate”
Within 15 minutes from this lecture
Total value of the package: $1000
Maria Cieślak
Head of SEO