I checked the public repository and Pages site today (20 October 2026). The site still returns a 404, but main already contains an index.html file.

The strongest clue is in your latest listed Pages run, #32: the build was cancelled and its annotations say owner marked spammy. That points to an account-level restriction at the time of that build, rather than just an HTML filename problem. It may also relate to the search-visibility symptom you described, although I cannot confirm your account's current internal status.

Please contact GitHub Support and include that run URL, the exact annotation, your username, and the Pages URL. If you believe an account restriction was applied incorrectly, GitHub documents the review route here: GitHub Appeal and Reinstatement. Only GitHub can review that restriction.

Once Support confirms the account is clear, check Settings → Pages: if publishing from the current main branch, select the folder containing index.html (/ for its current location), then let a new Pages build and deployment complete. GitHub's 404 troubleshooting guide explains the entry-file location and filename requirements. If it still fails, share the new run link and its first error so the remaining deployment issue can be diagnosed.