body { -ms-overflow-style: scrollbar; overflow-y: scroll; overscroll-behavior-y: none; } .errorContainer { background-color: #FFF; color: #0F1419; max-width: 600px; margin: 0 auto; padding: 10%; font-family: Helvetica, sans-serif; font-size: 16px; } .errorButton { margin: 3em 0; } .errorButton a { background: #1DA1F2; border-radius: 2.5em; color: white; padding: 1em 2em; text-decoration: none; } .errorButton a:hover, .errorButton a:focus { background: rgb(26, 145, 218); } .errorFooter { color: #657786; font-size: 80%; line-height: 1.5; padding: 1em 0; } .errorFooter a, .errorFooter a:visited { color: #657786; text-decoration: none; padding-right: 1em; } .errorFooter a:hover, .errorFooter a:active { text-decoration: underline; } #placeholder, #react-root { display: none !important; } body { background-color: #FFF !important; }

JavaScript is not available.

We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using twitter.com. You can see a list of supported browsers in our Help Center.

Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2023 Twitter, Inc.

Conversation

Google Search Central

Are your JavaScript-framework pages not showing in Google's cached view? 🤯 Catch our latest episode of #AskGooglebot where

speaks to why or why not this may be an indication of an issue. 🤔 Watch now → goo.gle/3uXilCn

11:30 AM · Apr 6, 2022

Justin Aldridge

@justinaldridge

Replying to

and

Hi John. Thanks for clarifying. One question, as JS is rendered separately to the page by Google, does it see a blank page on first index before the JS is rendered? And when the page is recrawled, is it blank again? Thanks

1

2

johnmu is a ranking factor and so are you

Replying to

@justinaldridge

and

Not necessarily - the initial view depends a lot on how the page is built, rendering happens very quickly, and afterwards indexing should be fairly stable. I don't think I've seen a "flash of unrendered content in indexing"-kind of thing in practice.

1

1

Show replies

Replying to

and

I see... Google celebrities prefer to make stupid videos on YouTube instead of fixing the issues. 🤣 Oh it is normal of course, nothing is wrong with JavaScript pages, it is just Google not able to cache them anymore 🤣

2

Replying to

and

How about to cache more JavaScript pages than spent more time to indicate that it may be an issue?

1

Replying to

Your tweet was quoted in an article by seroundtable

seroundtable.com

Daily Search Forum Recap: April 7, 2022

Here is a recap of what happened in the search forums today, through the eyes of the Search Engine Roundtable and other search forums on the web. For the past couple days now, it seems many but not

Replying to

and

Conveniently timed as I'm looking into this issue for a client. Thanks

!

1

Show additional replies, including those that may contain offensive content

Show