Hi guys, We’re running our forum on Discourse (on a subfolder), our SEO specialists made an analysis on it. Besides the speed of the website, they have one more concern about JavaScript processing. For now, Discourse uses dynamic rendering as a workaround, but what are your plans for the future, wh…

[이미지] Agnieszka_Jaskiewicz: For now, Discourse uses dynamic rendering as a workaround, but what are your plans for the future, when Google will fully handle processing JavaScripts and DR becomes simply a form of cloaking? By “dynamic rendering”, I suppose you mean we have a dedicated crawler …

You’re serving almost the same content for both human and crawler-only views, with completely different functionality around that content. This is kind of okay at the moment. However, as soon as Google feels comfortable enough with JS, it will inevitably become a form of cloaking - this already havi…

Once we’re confident that Google is crawling our application as well as our crawler view, we’ll just automatically redirect Google Bot to the app instead of the crawler view.

We believe your SEO advisors are wildly off base here. We have had a lot of bad experiences with SEO “experts” that don’t know what they are talking about.

Discourse is a JavaScript app, so it trades first run time for insanely fast subsequent page loads. The first hit requires the JavaScript app, Discourse, to be downloaded to the browser.

Google and JS scripts

지원

Agnieszka_Jaskiewicz (Agnieszka Jaśkiewicz) 9월 4, 2019, 1:09오후 6

Another problem connected with these JS is the speed limit of our website:

글		댓글	조회수
Googlebot is getting non-javascript version of the site Development	16	1804	3월 9, 2024
Disable or bypass feature detect for Googlebot (while serving JS app to crawlers) Support unsupported-install	7	3588	6월 14, 2022
What is the Discourse approach to SEO? Site feedback search	8	8604	6월 21, 2016
Can we have a conversation about SEO? Development	2	908	4월 4, 2022
Discourse noscript Support	3	770	10월 23, 2018

Google and JS scripts

Related topics