Source and production can diverge
Metadata can be fixed in source while yesterday’s build is uploaded. Assets or redirect rules can be absent from the final package.
Verify the exact package
- Compare source and deploy output.
- Crawl internal links.
- Parse metadata and JSON-LD.
- Confirm referenced assets exist.
- Check redirect and header files.
- Open routes at desktop and mobile widths.
“The code is correct” is not a production verdict.
Retest after hosting
Caching, domains, compression, headers, and hosting redirects can change behavior. Live verification closes the loop.
Release gate
Do not approve a deployment until the uploaded package passes.
- Source and deploy output contain the same approved changes.
- Every internal route, form, image, font, and download resolves.
- Titles, descriptions, canonicals, social metadata, and structured data parse correctly.
- Redirect and security-header files are present.
- Desktop and mobile checks show no overflow or console errors.
- The hosted result is retested after caching and domain rules apply.