Launching a website involves more than choosing a template and clicking publish. This reusable website setup checklist helps you select suitable free website hosting, connect a domain, verify DNS and SSL, test the site on mobile, confirm forms and analytics, and monitor performance after launch. Use it for a new site, a migration, or a quarterly review.
Overview
A reliable launch has three parts: preparation, verification, and ongoing monitoring. Preparation covers your site platform, content, domain, and hosting plan. Verification confirms that visitors can reach the correct pages securely and that important functions work. Monitoring helps you catch problems after launch, when changes to DNS, plugins, forms, or hosting settings can affect the site.
For a simple portfolio, landing page, or small business site, free website hosting may be enough if the provider supports the features you need. Check whether the plan includes the storage, bandwidth, domain connection, SSL, email or form handling, and backup options your project requires. A free website builder can make the initial setup easier, while a content management system may provide more control but require more maintenance.
Keep a simple launch record with the following details:
- Domain name and registrar account
- Hosting or website builder account
- Nameservers or DNS records currently in use
- SSL status and preferred website address
- Important page URLs, forms, integrations, and analytics ID
- Date of the last backup and the person responsible for access
If you are unfamiliar with the relationship between a domain and hosting, review this small business website launch guide before making changes. The domain is the address visitors use; hosting stores and serves the site files or application. A website builder may combine both functions behind one dashboard, but the underlying responsibilities still matter when troubleshooting.
What to track
1. Platform and template fit
Record why you chose the platform. A static site may be appropriate for a fast, low-maintenance landing page, while WordPress or another content system may be better when several people need to publish regularly. For a comparison of basic approaches, see how to choose a website builder and static website hosting for beginners.
Before customizing a template, check its navigation, typography, image behavior, and mobile layout. Replace sample text, stock contact details, placeholder buttons, and unused sections. Confirm that the template allows you to edit page titles, descriptions, headings, image alternative text, and social sharing information.
2. Domain and DNS configuration
Write down the intended versions of the site, such as example.com and www.example.com, and choose one as the primary address. The other should redirect to it when your platform supports redirects.
For DNS records, verify the record type, host or name, destination, and any required priority. Common records include:
- A record: points a domain or subdomain to an IPv4 address.
- AAAA record: points to an IPv6 address when supplied by the host.
- CNAME record: points a subdomain to another hostname.
- MX record: directs email delivery and should not be changed casually.
- TXT record: is often used for verification or email-related settings.
Do not copy records from a generic example without checking your provider's exact instructions. Keep a dated copy of the previous DNS configuration before editing it. The guide to connecting a domain and understanding DNS records provides a useful reference for this step.
3. SSL and canonical access
Open the site using https:// and check that the browser does not show a certificate warning. Test the homepage and at least one internal page. If the site loads at both HTTP and HTTPS, make sure HTTP redirects to HTTPS. Also check whether mixed content—such as an image or script still loaded over HTTP—causes browser warnings.
SSL setup varies between free and paid hosting plans. If the certificate is missing, confirm that the domain points to the correct host, the domain has finished propagating, and the platform has SSL enabled. Do not treat a certificate warning as a cosmetic issue; resolve it before sharing the site. See SSL for new websites for a focused troubleshooting guide.
4. Content, forms, and measurement
Use this page-by-page check:
- Homepage explains what the site offers and who it serves.
- Navigation reaches the main pages without dead ends.
- Contact details, opening hours, service areas, and prices are accurate where applicable.
- Buttons go to the intended destination.
- Contact forms accept a test submission and deliver it to the correct inbox.
- Confirmation messages explain what happens next.
- Page titles and descriptions are unique and descriptive.
- Images are compressed, correctly sized, and labeled with useful alternative text.
Install analytics only after deciding what you need to learn. Useful baseline events may include contact-form submissions, calls, bookings, downloads, or clicks to an external service. Record the measurement tool and account owner so it can be recovered during a future migration.
5. Backups, speed, and uptime
Find out how the platform handles backups. If automatic backups are unavailable, export site files, content, and settings according to the platform's instructions. A backup is only useful if you know where it is stored and how to restore it.
Check the homepage on a normal mobile connection and on a desktop connection. Look for oversized images, unnecessary animations, slow third-party embeds, and fonts that delay the main content. Track basic uptime by using a monitoring tool or by adding a recurring manual check. The website uptime guide explains what to observe without reducing site health to a single number.
Cadence and checkpoints
Use the following schedule as a practical tracker rather than a rigid rule.
Before launch
- Confirm the platform, plan limits, template, and primary domain.
- Review every page, link, form, image, and contact detail.
- Verify DNS instructions and record the current configuration.
- Enable SSL, test HTTPS, and select the preferred domain version.
- Make a backup or export before publishing.
Within the first week
- Test the site from a different device and network.
- Submit each important form and confirm delivery.
- Check analytics or search measurement for basic data collection.
- Review the first uptime and speed observations.
- Fix broken links, missing images, redirect errors, or confusing calls to action.
Monthly
- Open the homepage, key landing pages, and contact page.
- Run a real form test if the form is business-critical.
- Check SSL renewal status, domain renewal status, and account access.
- Review backups and remove outdated accounts or integrations.
- Look for unusual changes in traffic, conversions, loading time, or downtime.
Quarterly
- Review whether the hosting plan still fits traffic, storage, and functionality.
- Test the site on current mobile and desktop browsers.
- Refresh outdated content, screenshots, team details, and legal or contact information.
- Review DNS records and remove entries that are no longer needed.
- Perform a restore test if your platform supports backups.
How to interpret changes
When a site stops working after a domain change, first identify the scope. If the entire domain fails, inspect nameservers and the main A or CNAME record. If only one subdomain fails, check that subdomain's record. If the site works for some people but not others, DNS propagation or cached records may be involved; avoid repeatedly changing records before the previous change has had time to take effect.
If the domain resolves but HTTPS fails, check that the certificate covers the exact domain version visitors are using. If HTTPS works but pages display warnings, inspect embedded images, scripts, and forms for insecure URLs.
A sudden speed reduction can result from larger images, a new plugin, a third-party widget, increased traffic, or a hosting limit. Compare the current page with your previous version and disable or remove one recent change at a time. If forms stop arriving, submit a test, check the form destination, inspect spam folders, and confirm that the receiving mailbox still works.
For a free hosting plan, distinguish between a temporary setup issue and a plan limitation. A small site may work well for a simple landing page but need a different arrangement as traffic, media, team access, or application requirements grow. The goal is not to upgrade automatically; it is to match the platform to the site's actual needs. For context, compare free hosting with a custom domain and the considerations in cloud versus shared hosting.
When to revisit
Return to this checklist whenever you launch a new site, move to a new host, change nameservers, connect a new domain, install a major update, or redesign a key page. Even without a major change, schedule a monthly health check and a more thorough quarterly review. Revisit it immediately if visitors report an error, a form stops working, the certificate warning returns, traffic changes unexpectedly, or monitoring shows repeated downtime.
To make the checklist reusable, keep a dated copy in your project folder. Mark each item as complete, record the result, and note any follow-up owner. At the next review, compare the new observations with the previous record rather than relying on memory. This creates a simple history of DNS changes, SSL status, backups, uptime, forms, and performance.
Next action: copy the five checkpoints into a calendar, open your hosting and domain dashboards, and complete the pre-launch list one item at a time. If you are migrating a static site, start with the static hosting guide; if you are evaluating WordPress, use the WordPress hosting comparison before selecting a platform. A documented launch is easier to troubleshoot, easier to hand over, and safer to repeat.
