Post-Push Deployment Checks

Mandatory checklist run after every git push origin main to x9elysium.com. The site deploys via Hostinger static FTP (.github/workflows/deploy.yml). A green push does not guarantee the live site is healthy — always verify.

When to run

Immediately after git push origin main.
After a manual npm run deploy:zip + Hostinger File Manager upload.
After Hostinger cache purge or DNS changes.
Whenever the user reports the site is broken, slow, or showing stale content.

0. Confirm the deploy actually ran

Open the GitHub Actions run for the commit:

https://github.com/X9elysium/X9Elysium/actions/workflows/deploy.yml

Expected:

deploy job → green.
Deploy to Hostinger via FTP step → completed without login/path errors.
IndexNow ping step → ok or continue-on-error.
Post-deploy smoke test → listed paths return 200.

If the workflow is red (usually missing HOSTINGER_FTP_* secrets), fix secrets first — live still serves the previous upload.

1. HTML status

curl -sI -H "Cache-Control: no-cache" "https://x9elysium.com/?nocache=$(date +%s)" | head -20

Expected:

HTTP/2 200 (or HTTP/1.1 200).
Content is the new export (check homepage title / hero copy).

If stale: hPanel → Cache Manager → Purge All, then hard-reload.

2. Critical routes

for path in / /blog/ /thoughts/ /contact/ /careers/ /services/ /work/ /locations/toronto/; do
  code=$(curl -s -o /dev/null -w '%{http_code}' -H "Cache-Control: no-cache" "https://x9elysium.com${path}?nocache=$(date +%s)")
  echo "$code $path"
done

All should be 200.

3. Contact form path

curl -sL "https://x9elysium.com/contact/" | grep -oE 'Talk to Our Team|api/lead' | sort -u

Expected: Talk to Our Team present. Submit may open mailto when /api/lead is offline (normal on Hostinger static).

4. Do not claim live until

Actions deploy job green
Homepage 200 with expected title
At least /contact/ and /services/ 200
Cache purged if HTML looked stale

Recipe for secrets + DNS: hostinger-static-deploy.md.