I can't really know what needs work without seeing your html but generally the list goes.

• Don't load meta keywords tag / don't even use it at all
• Make descriptive unique titles
• Only one h1 tag per page
• Keep DOM structure simple and easy to read
• Have a sitemap
• Upload sitemap to Google Webmaster Tools

If there is anything I can do to help resolve this issue, then please let me know as I am glad to help out.

P.S. The new sites look great BTW!

Because this whole log4shell crap, I had to bump the recommended label for all the old versions. Would be nice to be able to do that in bulk.

The text format is stupid simple, we already do a good job of indexing everything in project_index.html, so it shouldn't be needed.
But if someone feels like making a sitemap.txt generator.
https://developers.google.com/search/docs/advanced/sitemaps/build-sitemap#text

Steps to reproduce:

1. Visit https://files.minecraftforge.net/ - this is loaded over TLS
2. Pick a link
3. Users are forced onto HTTP ad-laden interstitial page: http://adfoc.us/serve/sitelinks/?id=271228&url=http://files.minecraftforge.net/maven/net/minecraftforge/forge/1.12.2-14.23.2.2653/forge-1.12.2-14.23.2.2653-installer.jar
4. Users are redirected back to the plaintext URL for the requested file - e.g. http://files.minecraftforge.net/maven/net/minecraftforge/forge/1.12.2-14.23.2.2653/forge-1.12.2-14.23.2.2653-installer.jar

Ergo, download can be MitM'd.

Because it's a Google service. I can only tell you here.
And we can't see ADs in the download page, then we can't download.

Some projects may fit into the 1.0.0-1.0 version formatting without actually being MC related. So add a page config setting to force single page index generation.

I enabled GZip compression on the files server, would be nice to have page gen auto-generate the .gz files, so that the nginx server doesn't have to do it at runtime.

    :wave: We use the issue tracker exclusively for final bug reports and feature requests.  However, this issue appears to be better suited for the  [Forge Support Forums](https://forums.minecraftforge.net/) or  [Forge Discord](https://discord.gg/UvedJ9m). Please create a new topic on the support forum with this issue or ask in the `#tech-support` channel in the Discord server, and the  conversation can continue there.

Originally posted by @github-actions[bot] in MinecraftForge/MinecraftForge#9124 (comment)

I am unable to register an account on forge forums because i see no options to pass the security check

The Files of universal for forge are gone
Some files of compiled forge are gone.
The link below results in no download button for anything besides docs or source

Example Link:
http://files.minecraftforge.net/maven/net/minecraftforge/forge/index_1.3.2.html

While testing GZip support for MinecraftForge/MinecraftForge#8148 , I noticed that it is not enabled server-side for https://files.minecraftforge.net .

I've estimated significant bandwidth savings with this tool and manually checked what it would be myself to make sure it's roughly correct.

Note that the download pages also serve up other currently-uncompressed content such as CSS, SVG and JS files which would also benefit from compression. These are not factored in here for simplicity's sake.

I assume that it was disabled to avoid compressing already-compressed jar files but with some changes to the configuration it can be set to only compress json, html, css, svg, js, jsm, txt, pom, xml, etc... It is also possible to set the server to compress static files once and serve them multiple times to avoid the CPU load of compressing on each request.