Netlify Deployment Checklist for Non-Developers

01

Start by separating what the repository knows

Your repository may show build scripts, framework settings, redirects, functions, and variable names. It usually cannot prove what is configured in the Netlify dashboard or what happened in the latest production deploy.

• Repository evidence: package scripts, configuration files, redirects, functions, and referenced variable names
• Dashboard evidence: site settings, environment scopes, domain status, deploy context, and permissions
• Live-site evidence: the production URL, browser behavior, headers, forms, functions, and error handling
• Keep preview and production results separate; a successful preview is not proof of a successful production deploy

02

Build command, publish directory, and runtime

• Confirm the build command matches the project scripts and intended framework
• Confirm the publish directory matches the output produced by the build
• Check the Node or runtime version expected by the repository and dashboard
• Review dependency install behavior and lockfile consistency
• Read the complete deploy log, including warnings, generated routes, and failed post-build steps
• Do not copy a setting from another site without checking this repository

03

Environment variables and deploy contexts

List names, not secret values. Check which values are needed for local development, previews, and production, and whether each context intentionally differs.

• Every referenced variable has an owner and a documented purpose
• Private keys and server-only values are not exposed to browser bundles
• Preview deployments do not accidentally use production data or payment mode
• Production values are present in the correct Netlify scope
• A missing variable produces a clear failure rather than a misleading success state
• Rotate a value if it may have appeared in code, logs, screenshots, or prompts

04

Domains, HTTPS, redirects, and forms

• Confirm the intended primary domain and www/non-www behavior in the dashboard
• Verify HTTPS is active and the certificate covers the intended hostname
• Check redirects for loops, old routes, trailing slashes, and authenticated pages
• Confirm canonical, robots, and sitemap behavior on the live site
• Test forms with a real permitted test submission and verify the failure state
• Review spam protection, notification ownership, and privacy wording for public forms

05

Functions, logs, rollback, and smoke testing

• Confirm serverless or edge functions are discovered and deployed where expected
• Check function logs for errors, timeouts, sensitive values, and provider responses
• Test authentication, database, email, and payment calls from the deployed environment
• Record the deployment commit, URL, variables changed, and known issues
• Know how to redeploy the last known-good commit before making a risky change
• Smoke-test the homepage, signup or main action, error state, mobile layout, and one authenticated or data-backed path

06

Manual Netlify dashboard verification

Open the Netlify site dashboard and mark each item only after checking it there. These settings are intentionally not claimed by this page.

• Deploy settings: build command, publish directory, runtime, and deploy context
• Environment variables: names, scopes, values, and last-change ownership
• Domain management: primary domain, aliases, DNS guidance, and HTTPS status
• Redirects and headers: deployed behavior, not only local configuration
• Functions: deployed names, runtime, logs, timeout behavior, and access assumptions
• Deploy history: current production commit, preview relationship, failed deploys, and rollback option

07

Copy-paste deployment audit prompt