Separate source from the published copy
Keep the editable source and the ready-to-publish files in distinct folders. Record how a release is produced. A static website does not need a database to serve its pages, but its source still needs versioning or dated backups. The only copy should not live in the public folder of the hosting account.
Check the complete release
Open each page directly, follow its navigation and check image and download paths. Test a missing page as well as a successful one. Check titles, descriptions and canonical addresses. Use a site map containing the pages you actually intend visitors and search engines to find.
Remove unnecessary dependencies
A simple reading site may not need third-party fonts, trackers or a client-side framework. Self-contained files make behaviour easier to understand and reduce external requests. Remove a dependency because the site does not need it, not merely to chase a score. Keep the interactions that genuinely help readers.
Keep hosting decisions visible
Record the domain owner, DNS provider, hosting provider and certificate renewal route. Ask how to restore a previous release and how the host handles service disruption. If availability protection is a requirement, compare the current offering and exclusions with a provider such as KoDDoS rather than assuming all hosting plans behave alike.
Publish with a way back
Upload a complete release to a staging directory, verify it and then switch the served copy. Retain the previous release outside the public directory. After publication, check the actual HTTPS address from a fresh browser and test a deep link. Record the release date and what was checked so the next update starts from a known state.
Put it into practice
- Export images for their actual display size.
- Check every article as a direct link.
- Keep an earlier release outside the public directory.
- Test a narrow screen and a missing address.
Sources & further reading
Examples and worksheets on this page are illustrative. Documentation links were checked in November 2026; follow the relevant product’s current instructions.
