GitHub Pages站点子页面访问404问题求助

Let’s walk through the most likely fixes for your 404 issues, since you’re not using Jekyll:

• Check your GitHub Pages source configuration
  Head to your repo’s Settings → Pages section. Make sure the "Source" dropdown points to the correct branch (usually main or master) and root directory. If you’re serving content from the repo root, your web folder needs to live directly there (not nested in another folder). If you want to serve the web folder as the Pages root, you’ll need to either move its contents to the repo root or use a custom GitHub Actions workflow to deploy the web folder specifically.

• Fix filename casing mismatches
  You noted the file is named Abbey-Academies-Trust.html, but your test URL uses Abbey-Academies-trust.html (notice the lowercase t in the last segment). GitHub Pages runs on Linux servers, which are case-sensitive for file paths. Even if your local OS (like Windows/macOS) ignores casing, the server won’t—this is an extremely common cause of 404s. Ensure your URL exactly matches the filename’s case.

• Confirm files are pushed to GitHub
  Double-check your repo on GitHub’s web interface: navigate to web/2044 and verify both Abbey-Academies-Trust.html and index.html are present. Sometimes local files don’t get pushed (e.g., forgotten git add/git commit steps), or a .gitignore rule is excluding the web folder entirely. Check your .gitignore file to make sure there’s no line like web/ blocking those files from being uploaded.

• Wait for deployment and clear browser cache
  GitHub Pages can take 5-10 minutes to deploy new or updated content, especially after initial setup. If you just pushed the files, give it some time, then hard-refresh your browser (Ctrl+F5 or Cmd+Shift+R) to bypass local cache that might be showing old 404 responses.

• Disable accidental Jekyll processing
  Even if you’re not using Jekyll, GitHub Pages might still process your repo with Jekyll by default. To turn this off completely, add an empty file named .nojekyll to the root of your repo. This tells GitHub to serve your files exactly as they are, without any Jekyll-related processing that could hide or rename your web folder content.

内容的提问来源于stack exchange，提问作者philipnye