It is hard to ensure that a website would survive for 30 years without requiring maintenance. There are too many components involved in running a website and I

It is hard to ensure that a website would survive for 30 years without requiring maintenance. There are too many components involved in running a website and I think it is quite likely that at least one of them would break if no maintenance is done. I think a breakage is especially more likely if it is a personal website. For example, the domain name may expire, the server hosting the website may go down due to a hardware malfunction in your own server or a payment failure for your server provider, TLS certificates (if any) may fail to renew due to a breaking change in a certificate management tool, etc. But I think it is possible for the HTML pages of a website to survive. If this can be done, then the website can survive in its original form even when it may not be available in its original domain name. Here are some things I have done to increase the odds that my personal website would survive for several decades even if the primary website disappears some day: - The entire website is a collection of static HTML pages. - All internal links and path references, are relative. In fact, the paths to CSS files, images, videos, audios, etc. are also relative. - The HTML pages do not loaded any resource from another domain. - Since I use MathJax on my website to render mathematical content, MathJax is bundled within the website. Further, MathJax is loaded into the pages that need it using relative links only. (This is an example of the previous two points.) - Stick to text as much as possible. Most pages are just text marked up with HTML. Use images, videos, audios, etc. only when absolutely necessary. Similarly, load MathJax using a relative link only on those pages that have mathematical content. - Test that if the website is copied to a directory on the local filesystem, one can still navigate the website locally using a web browser. This is possible due to using relative links/paths (instead of absolute ones). - While the primary copy of the website is hosted at a personal domain name I have registered, I publish a mirror copy on my GitHub account via GitHub pages. Should the primary domain name disappear someday (which did happen once for a few days due to a sinkhole incident), the mirror would still be available via GitHub pages as long as GitHub continues to maintain their service. Finally, and I don't do this, but one could consider http://web.archive.org/ http://web.archive.org/ as well as IPFS to archive the pages of one's website to ensure that tertiary copies of the website also remain on the web.