Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Bartosz Góralewicz
@bart_goralewicz
JavaScript SEO?
JavaScript SEO?
JavaScript SEO
is dying
Google Hangouts
(August 23rd 2019)
JavaScript SEO is not dying.
It's getting even more complex
Is JavaScript SEO dying?
JavaScript SEO is not dying.
It's getting even more complex
Is JavaScript SEO dying?
JavaScript SEO is not dying.
It's getting even more complex
Is JavaScript SEO dying?
Future of JavaScipt SEO
There are so many things that you
can do wrong, and it takes a lot of
experience to be able to debug
and find out and impr...
HTML HTMLHTML
HTML HTMLHTML
Everything is JS
HTML
Even HTML
pages CAN
be rendered.
HTML
Even HTML
pages CAN
be rendered.
BUT
We found out
that JavaScript
of non-JavaScript
websites.
is a problem
We found out
that JavaScript
of non-JavaScript
websites.
is a problem
We found out
that JavaScript
of non-JavaScript
websites.
is a problem
We found out
that JavaScript
with non-JavaScript
websites.
is a problem
SEO and post factum learning
CHANGE
THE PROBLEM of 2019
THE PROBLEM of 2019
CHANGE
THE PROBLEM of 2019
CHANGE
JavaScript SEO evolved from “JS
websites” to all websites.
The
irony
v
v
v
v
v
v v
v
v
v v
v v
v v
v
v
v v
v
v
Timeframe (of JS indexing)
or the lack thereof
Timeframe (of JS indexing)
or the lack thereof
Timeframe (of JS indexing)
or the lack thereof
Timeframe (of JS indexing)
or the lack thereof
Timeframe (of JS indexing)
or the lack thereof
It is 2019 and our
research shows that
there are hundreds
of thousands of
domains not fully
indexed.
Even after… Months of...
Even after… Months of
publishing content.
It is 2019 and our
research shows that
there are hundreds
of thousands of
domain...
Blame
JavaScript
Blame
JavaScript
Blame
Blame
Rendering
How rendering works with Google
How rendering works with Google
Bartosz: So, you look at the
difference between the initial
HTML, and, then, if after
rend...
How rendering works with Google
Bartosz: So, you look at the
difference between the initial
HTML, and, then, if after
rend...
The Heuristics
There are certain heuristics, that,
if we see after a while, like, oh, this
page, actually, the renderer do...
There are certain heuristics, that,
if we see after a while, like, oh, this
page, actually, the renderer does not
diff as ...
… those heuristics are FAR from perfect though.
… those heuristics are FAR from perfect though.
… those heuristics are FAR from perfect though.
… those heuristics are FAR from perfect though.
… those heuristics are FAR from perfect though.
Pretty much every website, when
we see them for the first time, goes
to rendering. So there’s no indexing
before it hasn’t...
But what is
a new website exactly?
What is a new website?
But what is
a new website exactly?
What is a new website?
What if
a new website doesn’t have
any comments yet?
Experiments on staging?
Experiments on staging? Don't go this way
Experiments on staging? Don't go this way
We decided to experiment
with how good Google is
with their heuristics.
We decided to experiment
with how good Google is
with their heuristics.
Benchmarking Google's heuristics:
Our own JS Budget Experiment (2019)
Benchmarking Google's heuristics:
Our own JS Budget Experiment (2019)
3 domains with <a href> links in the initial HTML re...
Benchmarking Google's heuristics:
Our own JS Budget Experiment (2019)
3 domains with <a href> links in the initial HTML re...
Benchmarking Google's heuristics:
Our own JS Budget Experiment (2019)
3 domains with <a href> links in the initial HTML re...
Benchmarking Google's heuristics:
Our own JS Budget Experiment (2019)
3 domains with <a href> links in the initial HTML re...
LET’S GO BACK TO 2017
Crawler budget experiment 2017
List of experiment websites
Time needed to reach the 7th level of nested content
(server logs)
htmlcrawling.party
first 6 ...
I was right
Results – 2019
List of experiment websites
Time needed to reach the 7th level of nested content
(server logs)
...
Crawler budget experiment 2019
Google in 2017 vs Google in 2019.
0:1
Google in 2017 vs Google in 2019.
Good job,
Google!
0:1
Google in 2017 vs Google in 2019.
Ok, Let's do another experiment!
0:1
Google in 2017 vs Google in 2019.
Ok, Let's do another experiment!
0:1
HTML to JS ratio experiment
v
HTML to JS ratio experiment
v
HTML to JS ratio experiment
v
3 types
of test pages
HTML to JS ratio experiment- results
Raw data:
HTML to JS ratio experiment- results
Raw data: Most of the JavaScript content indexed after
a half-hour (!)
HTML to JS ratio experiment- results
Raw data: Most of the JavaScript content indexed after
a half-hour (!)
With the exception of 5 URLs.
HTML to JS ratio expe...
Raw data: Most of the JavaScript content indexed after
a half-hour (!)
With the exception of 5 URLs.
HTML to JS ratio expe...
Raw data: Most of the JavaScript content indexed after
a half-hour (!)
With the exception of 5 URLs.
But here, Google didn...
Raw data: Most of the JavaScript content indexed after
a half-hour (!)
With the exception of 5 URLs.
But here, Google didn...
Raw data: Most of the JavaScript content indexed after
a half-hour (!)
With the exception of 5 URLs.
But here, Google didn...
Google in 2017 vs Google in 2019.
0:2
Google in 2017 vs Google in 2019.
Good job,
Google!
0:2
Google in 2017 vs Google in 2019.
Ok, Let's do another experiment!
0:2
Google in 2017 vs Google in 2019.
Ok, Let's do another experiment!
0:2
JSSEO.expert v1 - 2017
V2 Inline
GSC fetch
URL Indexed?
Content
cached
Links
Content
Indexed?
Test URL
Inline Inline
JSSEO.expert v2 - 2019
JSSEO.expert v2 - results
V2 Inline
GSC fetch
URL Indexed?
Content
cached
Links
Content
Indexed?
Test URL
Inline Inline
Google in 2017 vs Google in 2019.
0:3
Google in 2017 vs Google in 2019.
Good job,
Google!
0:3
But what about popular websites having some
content generated by JS?
Martin Splitt was right
about the new websites.
Martin Splitt was right
about the new websites.
Let's find out!Can Google deal with them?
But what about popular websites ...
The State of JavaScript Indexing
Experiment 2019
The State of JavaScript Indexing
Experiment 2019
The State of JavaScript Indexing
Experiment 2019
The State of JavaScript Indexing
Experiment 2019
The State of JavaScript Indexing
Experiment 2019
National Geographic - with JS
v
National Geographic - NO JS
v
National Geographic - NO JS
v
100%of JS content indexed
ASOS - with JS
ASOS - NO JS
ASOS - NO JS
v
100%of JS content indexed
v
But not every website
is lucky enough
v
But not every website
is lucky enough
82%
0%
0%
0%
42%
73%
Percentage
of the
JavaScript
content
indexed
2 WAVES
O F I N D E X I N G
2 WAVES
O F I N D E X I N G
T I M E F R A M E
4%
0%
66%
30%
99,5%
Percentage of the JavaScript
content not indexed after 14 days
4%
0%
66%
30%
99,5%
4%
0%
66%
30%
99,5%
Percentage of the JavaScript
content not indexed after 14 days
Blame Google or say that JS is evil
Blame Google or say that JS is evil
Every JavaScript SEO issue we saw
was 100% self-induced
Every JavaScript SEO issue we saw
was 100% self-induced
2 WAVES
O F I N D E X I N G - T I M E L I N E
2 WAVES
O F I N D E X I N G - T I M E L I N E
I expect, eventually rendering,
crawling and indexing will come
closer together
We are going like: ”Oh, all right, we
are ...
Crawling
and indexing
to come
together
I expect, eventually rendering,
crawling and indexing will come
closer together
We ...
What to do?
Now it's time for
the BIG news!
Now it's time for
the BIG news!
OMFG
Onely Made for Geeks – free toolset
OMFG
Onely Made for Geeks – free toolset
OMFG
www.onely.com/tools
Onely Made for Geeks – free toolset
OMFG
www.onely.com/tools
WARNING – still an early alpha version.
Onely Made for Geeks – free toolset
OMFG
www.onely.com/tools
WARNING – still an early alpha version.
Onely Made for Geeks – free toolset
OMFG
www.onely.com/tools
WARNING – still an early alpha version.
Onely Made for Geeks – free toolset
www.onely.com/tools
Fully built within the last 3 weeks 
WARNING – still an early alp...
TGIF - The Google Indexing Forecast
HTML vs. JavaScript indexing
HTML vs. JavaScript indexing
WWJD – What Would JavaScript Do?
WWJD – What Would JavaScript Do?
BBC.CO.UK - example
WWJD – What Would JavaScript Do?
WWJD – BBC & meta tags vs. rendering
WWJD – BBC & meta tags vs. rendering
WWJD – BBC & meta tags vs. rendering
WWJD – BBC & meta tags vs. rendering
WWJD – Links added by JS
WWJD – Links removed by JS
TL;DR – Too Long Didn’t Render
Chrome
Mobile-
Friendly Tester
A LOT of cool FREE tools coming soon!
JS
Let's talk about
HTML
Let's talk about
HTML
Let's talk about
HTML
JavaScript SEO is important. But other
parts of technical SEO are important too.
JavaScript SEO is important. But other
parts of technical SEO are important too.
I mentioned The Guardian has some issues ...
JavaScript SEO is important. But other
parts of technical SEO are important too.
I mentioned The Guardian has some issues ...
JavaScript SEO is important. But other
parts of technical SEO are important too.
I mentioned The Guardian has some issues ...
JavaScript SEO is important. But other
parts of technical SEO are important too.
I mentioned The Guardian has some issues ...
But other websites aren't as lucky
as The Guardian.
Medium is...medium*
Medium is...medium*
A quick check of 100 URLs of Medium...
*Tomek’s joke :D
A quick check of 100 URLs of Medium...
Only 70% of them are indexed in Google.
*Tomek’s joke :D
Medium is...medium*
A quick check of 100 URLs of Medium...
Only 70% of them are indexed in Google.
*Tomek’s joke :D
Medium is...medium*
Spoiler alert: 50% of the indexed URLs has JS content indexed.
That's the...medium value**.
A quick check of 100 URLs of M...
Spoiler alert: 50% of the indexed URLs has JS content indexed.
That's the...medium value**.
A quick check of 100 URLs of M...
Let’s talk hat
Cloaking in 2019
Nomoregunsusa.com
case study
vv
More data is coming soon
More data is coming soon
Cloaking in 2019
www.onely.com
@bart_goralewicz
THANK YOU
Cloaking in 2019
www.onely.com
@bart_goralewicz
THANK YOU
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019
Upcoming SlideShare
Loading in …5
×

0

Share

Download to read offline

How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019

Download to read offline

This is Onely's Bartosz Goralewicz's deck "How Much Content is Not Indexed in Google in 2019?" as presented at SIXT Wiesn on October 4, 2019.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all
  • Be the first to like this

How Much Content is Not Indexed in Google in 2019? | SIXT Wiesn 2019

  1. 1. Bartosz Góralewicz @bart_goralewicz
  2. 2. JavaScript SEO?
  3. 3. JavaScript SEO?
  4. 4. JavaScript SEO is dying
  5. 5. Google Hangouts (August 23rd 2019)
  6. 6. JavaScript SEO is not dying. It's getting even more complex Is JavaScript SEO dying?
  7. 7. JavaScript SEO is not dying. It's getting even more complex Is JavaScript SEO dying?
  8. 8. JavaScript SEO is not dying. It's getting even more complex Is JavaScript SEO dying?
  9. 9. Future of JavaScipt SEO
  10. 10. There are so many things that you can do wrong, and it takes a lot of experience to be able to debug and find out and improve things
  11. 11. HTML HTMLHTML
  12. 12. HTML HTMLHTML Everything is JS
  13. 13. HTML Even HTML pages CAN be rendered.
  14. 14. HTML Even HTML pages CAN be rendered. BUT
  15. 15. We found out that JavaScript of non-JavaScript websites. is a problem
  16. 16. We found out that JavaScript of non-JavaScript websites. is a problem
  17. 17. We found out that JavaScript of non-JavaScript websites. is a problem
  18. 18. We found out that JavaScript with non-JavaScript websites. is a problem
  19. 19. SEO and post factum learning
  20. 20. CHANGE THE PROBLEM of 2019
  21. 21. THE PROBLEM of 2019 CHANGE
  22. 22. THE PROBLEM of 2019 CHANGE
  23. 23. JavaScript SEO evolved from “JS websites” to all websites.
  24. 24. The irony
  25. 25. v
  26. 26. v v
  27. 27. v v v v v v
  28. 28. v v
  29. 29. v v
  30. 30. v v
  31. 31. v v v v v v
  32. 32. Timeframe (of JS indexing) or the lack thereof
  33. 33. Timeframe (of JS indexing) or the lack thereof
  34. 34. Timeframe (of JS indexing) or the lack thereof
  35. 35. Timeframe (of JS indexing) or the lack thereof
  36. 36. Timeframe (of JS indexing) or the lack thereof
  37. 37. It is 2019 and our research shows that there are hundreds of thousands of domains not fully indexed. Even after… Months of publishing the content
  38. 38. Even after… Months of publishing content. It is 2019 and our research shows that there are hundreds of thousands of domains not fully indexed.
  39. 39. Blame JavaScript
  40. 40. Blame JavaScript
  41. 41. Blame
  42. 42. Blame Rendering
  43. 43. How rendering works with Google
  44. 44. How rendering works with Google Bartosz: So, you look at the difference between the initial HTML, and, then, if after rendering you see extra content?
  45. 45. How rendering works with Google Bartosz: So, you look at the difference between the initial HTML, and, then, if after rendering you see extra content? Martin Splitt: Yeah.
  46. 46. The Heuristics There are certain heuristics, that, if we see after a while, like, oh, this page, actually, the renderer does not diff as much or doesn’t diff, it looks the way before
  47. 47. There are certain heuristics, that, if we see after a while, like, oh, this page, actually, the renderer does not diff as much or doesn’t diff, it looks the way before The Heuristics I still haven’t fully, like, grasped what exactly triggers the heuristics
  48. 48. … those heuristics are FAR from perfect though.
  49. 49. … those heuristics are FAR from perfect though.
  50. 50. … those heuristics are FAR from perfect though.
  51. 51. … those heuristics are FAR from perfect though.
  52. 52. … those heuristics are FAR from perfect though.
  53. 53. Pretty much every website, when we see them for the first time, goes to rendering. So there’s no indexing before it hasn’t been rendered.” ALL NEW SITES GET RENDERED
  54. 54. But what is a new website exactly? What is a new website?
  55. 55. But what is a new website exactly? What is a new website?
  56. 56. What if a new website doesn’t have any comments yet?
  57. 57. Experiments on staging?
  58. 58. Experiments on staging? Don't go this way
  59. 59. Experiments on staging? Don't go this way
  60. 60. We decided to experiment with how good Google is with their heuristics.
  61. 61. We decided to experiment with how good Google is with their heuristics.
  62. 62. Benchmarking Google's heuristics: Our own JS Budget Experiment (2019)
  63. 63. Benchmarking Google's heuristics: Our own JS Budget Experiment (2019) 3 domains with <a href> links in the initial HTML response
  64. 64. Benchmarking Google's heuristics: Our own JS Budget Experiment (2019) 3 domains with <a href> links in the initial HTML response 3 other domains with <a href> links generated with external JavaScript files
  65. 65. Benchmarking Google's heuristics: Our own JS Budget Experiment (2019) 3 domains with <a href> links in the initial HTML response Each domain runs on a different IP (UK) 3 other domains with <a href> links generated with external JavaScript files
  66. 66. Benchmarking Google's heuristics: Our own JS Budget Experiment (2019) 3 domains with <a href> links in the initial HTML response Each domain runs on a different IP (UK) Content generated using Articoolo 3 other domains with <a href> links generated with external JavaScript files
  67. 67. LET’S GO BACK TO 2017
  68. 68. Crawler budget experiment 2017
  69. 69. List of experiment websites Time needed to reach the 7th level of nested content (server logs) htmlcrawling.party first 6 levels: 6 minutes. We had to wait as much as 6 days for the 7th level. jscrawling.party 17 minutes htmlcrawling.wine 4 minutes jscrawling.wine We had to wait 1 day for Google to reach the 2nd level, but then it went through the remaining levels within minutes. jscrawling.pizza 8 minutes htmlcrawling.pizza 7 minutes Results – 2019
  70. 70. I was right Results – 2019 List of experiment websites Time needed to reach the 7th level of nested content (server logs) htmlcrawling.party first 6 levels: 6 minutes. We had to wait as much as 6 days for the 7th level. jscrawling.party 17 minutes htmlcrawling.wine 4 minutes jscrawling.wine We had to wait 1 day for Google to reach the 2nd level, but then it went through the remaining levels within minutes. jscrawling.pizza 8 minutes htmlcrawling.pizza 7 minutes
  71. 71. Crawler budget experiment 2019
  72. 72. Google in 2017 vs Google in 2019. 0:1
  73. 73. Google in 2017 vs Google in 2019. Good job, Google! 0:1
  74. 74. Google in 2017 vs Google in 2019. Ok, Let's do another experiment! 0:1
  75. 75. Google in 2017 vs Google in 2019. Ok, Let's do another experiment! 0:1
  76. 76. HTML to JS ratio experiment v
  77. 77. HTML to JS ratio experiment v
  78. 78. HTML to JS ratio experiment v 3 types of test pages
  79. 79. HTML to JS ratio experiment- results
  80. 80. Raw data: HTML to JS ratio experiment- results
  81. 81. Raw data: Most of the JavaScript content indexed after a half-hour (!) HTML to JS ratio experiment- results
  82. 82. Raw data: Most of the JavaScript content indexed after a half-hour (!) With the exception of 5 URLs. HTML to JS ratio experiment- results
  83. 83. Raw data: Most of the JavaScript content indexed after a half-hour (!) With the exception of 5 URLs. HTML to JS ratio experiment- results
  84. 84. Raw data: Most of the JavaScript content indexed after a half-hour (!) With the exception of 5 URLs. But here, Google didn’t even crawl it, so it’s not related to rendering at all HTML to JS ratio experiment- results
  85. 85. Raw data: Most of the JavaScript content indexed after a half-hour (!) With the exception of 5 URLs. But here, Google didn’t even crawl it, so it’s not related to rendering at all After 4 hours: 29/30 JavaScript content indexed. HTML to JS ratio experiment- results
  86. 86. Raw data: Most of the JavaScript content indexed after a half-hour (!) With the exception of 5 URLs. But here, Google didn’t even crawl it, so it’s not related to rendering at all After 4 hours: 29/30 JavaScript content indexed. After 8 hours: 30/30 JavaScript content indexed. HTML to JS ratio experiment- results
  87. 87. Google in 2017 vs Google in 2019. 0:2
  88. 88. Google in 2017 vs Google in 2019. Good job, Google! 0:2
  89. 89. Google in 2017 vs Google in 2019. Ok, Let's do another experiment! 0:2
  90. 90. Google in 2017 vs Google in 2019. Ok, Let's do another experiment! 0:2
  91. 91. JSSEO.expert v1 - 2017 V2 Inline GSC fetch URL Indexed? Content cached Links Content Indexed? Test URL Inline Inline
  92. 92. JSSEO.expert v2 - 2019
  93. 93. JSSEO.expert v2 - results V2 Inline GSC fetch URL Indexed? Content cached Links Content Indexed? Test URL Inline Inline
  94. 94. Google in 2017 vs Google in 2019. 0:3
  95. 95. Google in 2017 vs Google in 2019. Good job, Google! 0:3
  96. 96. But what about popular websites having some content generated by JS? Martin Splitt was right about the new websites.
  97. 97. Martin Splitt was right about the new websites. Let's find out!Can Google deal with them? But what about popular websites having some content generated by JS?
  98. 98. The State of JavaScript Indexing Experiment 2019
  99. 99. The State of JavaScript Indexing Experiment 2019
  100. 100. The State of JavaScript Indexing Experiment 2019
  101. 101. The State of JavaScript Indexing Experiment 2019
  102. 102. The State of JavaScript Indexing Experiment 2019
  103. 103. National Geographic - with JS v
  104. 104. National Geographic - NO JS v
  105. 105. National Geographic - NO JS v 100%of JS content indexed
  106. 106. ASOS - with JS
  107. 107. ASOS - NO JS
  108. 108. ASOS - NO JS v 100%of JS content indexed
  109. 109. v But not every website is lucky enough
  110. 110. v But not every website is lucky enough
  111. 111. 82% 0% 0% 0% 42% 73% Percentage of the JavaScript content indexed
  112. 112. 2 WAVES O F I N D E X I N G
  113. 113. 2 WAVES O F I N D E X I N G T I M E F R A M E
  114. 114. 4% 0% 66% 30% 99,5%
  115. 115. Percentage of the JavaScript content not indexed after 14 days 4% 0% 66% 30% 99,5%
  116. 116. 4% 0% 66% 30% 99,5% Percentage of the JavaScript content not indexed after 14 days
  117. 117. Blame Google or say that JS is evil
  118. 118. Blame Google or say that JS is evil
  119. 119. Every JavaScript SEO issue we saw was 100% self-induced
  120. 120. Every JavaScript SEO issue we saw was 100% self-induced
  121. 121. 2 WAVES O F I N D E X I N G - T I M E L I N E
  122. 122. 2 WAVES O F I N D E X I N G - T I M E L I N E
  123. 123. I expect, eventually rendering, crawling and indexing will come closer together We are going like: ”Oh, all right, we are gonna skip rendering.” It is not as frequently happening anymore. (...) Many websites even if they do not run JavaScript, they might still go through the render phase, because it doesn’t make a difference as much
  124. 124. Crawling and indexing to come together I expect, eventually rendering, crawling and indexing will come closer together We are going like: ”Oh, all right, we are gonna skip rendering.” It is not as frequently happening anymore. (...) Many websites even if they do not run JavaScript, they might still go through the render phase, because it doesn’t make a difference as much
  125. 125. What to do?
  126. 126. Now it's time for the BIG news!
  127. 127. Now it's time for the BIG news!
  128. 128. OMFG
  129. 129. Onely Made for Geeks – free toolset OMFG
  130. 130. Onely Made for Geeks – free toolset OMFG www.onely.com/tools
  131. 131. Onely Made for Geeks – free toolset OMFG www.onely.com/tools WARNING – still an early alpha version.
  132. 132. Onely Made for Geeks – free toolset OMFG www.onely.com/tools WARNING – still an early alpha version.
  133. 133. Onely Made for Geeks – free toolset OMFG www.onely.com/tools WARNING – still an early alpha version.
  134. 134. Onely Made for Geeks – free toolset www.onely.com/tools Fully built within the last 3 weeks  WARNING – still an early alpha version. OMFG
  135. 135. TGIF - The Google Indexing Forecast
  136. 136. HTML vs. JavaScript indexing
  137. 137. HTML vs. JavaScript indexing
  138. 138. WWJD – What Would JavaScript Do?
  139. 139. WWJD – What Would JavaScript Do?
  140. 140. BBC.CO.UK - example
  141. 141. WWJD – What Would JavaScript Do?
  142. 142. WWJD – BBC & meta tags vs. rendering
  143. 143. WWJD – BBC & meta tags vs. rendering
  144. 144. WWJD – BBC & meta tags vs. rendering
  145. 145. WWJD – BBC & meta tags vs. rendering
  146. 146. WWJD – Links added by JS
  147. 147. WWJD – Links removed by JS
  148. 148. TL;DR – Too Long Didn’t Render
  149. 149. Chrome Mobile- Friendly Tester
  150. 150. A LOT of cool FREE tools coming soon!
  151. 151. JS
  152. 152. Let's talk about HTML
  153. 153. Let's talk about HTML
  154. 154. Let's talk about HTML
  155. 155. JavaScript SEO is important. But other parts of technical SEO are important too.
  156. 156. JavaScript SEO is important. But other parts of technical SEO are important too. I mentioned The Guardian has some issues with JavaScript SEO.
  157. 157. JavaScript SEO is important. But other parts of technical SEO are important too. I mentioned The Guardian has some issues with JavaScript SEO. But Google indexes their HTML content really fast.
  158. 158. JavaScript SEO is important. But other parts of technical SEO are important too. I mentioned The Guardian has some issues with JavaScript SEO. Sample of 1300 URLs. Number of pages indexed after 1 day: 1280 = 98.5% But Google indexes their HTML content really fast.
  159. 159. JavaScript SEO is important. But other parts of technical SEO are important too. I mentioned The Guardian has some issues with JavaScript SEO. What about the rest? Sample of 1300 URLs. Number of pages indexed after 1 day: 1280 = 98.5% But Google indexes their HTML content really fast.
  160. 160. But other websites aren't as lucky as The Guardian.
  161. 161. Medium is...medium*
  162. 162. Medium is...medium* A quick check of 100 URLs of Medium... *Tomek’s joke :D
  163. 163. A quick check of 100 URLs of Medium... Only 70% of them are indexed in Google. *Tomek’s joke :D Medium is...medium*
  164. 164. A quick check of 100 URLs of Medium... Only 70% of them are indexed in Google. *Tomek’s joke :D Medium is...medium*
  165. 165. Spoiler alert: 50% of the indexed URLs has JS content indexed. That's the...medium value**. A quick check of 100 URLs of Medium... Only 70% of them are indexed in Google. *Tomek’s joke :D**  Medium is...medium*
  166. 166. Spoiler alert: 50% of the indexed URLs has JS content indexed. That's the...medium value**. A quick check of 100 URLs of Medium... Only 70% of them are indexed in Google. *Tomek’s joke :D**  Medium is...medium*
  167. 167. Let’s talk hat
  168. 168. Cloaking in 2019
  169. 169. Nomoregunsusa.com case study vv
  170. 170. More data is coming soon
  171. 171. More data is coming soon
  172. 172. Cloaking in 2019 www.onely.com @bart_goralewicz THANK YOU
  173. 173. Cloaking in 2019 www.onely.com @bart_goralewicz THANK YOU

This is Onely's Bartosz Goralewicz's deck "How Much Content is Not Indexed in Google in 2019?" as presented at SIXT Wiesn on October 4, 2019.

Views

Total views

114

On Slideshare

0

From embeds

0

Number of embeds

0

Actions

Downloads

4

Shares

0

Comments

0

Likes

0

×