# Generating a read-only no-javascript light version from a discourse instance

**URL:** <https://meta.discourse.org/t/generating-a-read-only-no-javascript-light-version-from-a-discourse-instance/238320>\
**Category:** Product Support\
**Created:** [September 7, 2022, 9:37am UTC](https://meta.discourse.org/t/generating-a-read-only-no-javascript-light-version-from-a-discourse-instance/238320 "2022-09-07T09:37:57Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)\
**Post date:** [September 7, 2022, 9:49am UTC](https://meta.discourse.org/t/generating-a-read-only-no-javascript-light-version-from-a-discourse-instance/238320/3 "2022-09-07T09:49:47Z")

</div>

AFAIK out there isn’t any such solution at large. But it can’t be too hard to develop. It is basically just static not-up-to-date-mirror with proper headers for Google.

But what would be the point for that? Quite few don’t use JS and when one is doing that he/she knows that the most of functionalites offered by sites are lost.

Sure, that would be blazing fast and easy to cache. But… why? Discourse isn’t painfully slow. It would be a honeypot for useless seo-bots, but even then those wouldn’t leave ”master-Discourse” alone. It wouldn’t help googlebot or does anything helpful as far as I can understand.

There is one situation where it could be helpful, though. And it is situation when Discourse is down and server/reverse proxy/load balancer knows how to redirect traffic.

---

_[View the full topic](https://meta.discourse.org/t/generating-a-read-only-no-javascript-light-version-from-a-discourse-instance/238320)._