Name the release and the URLs at risk

Record the source revision or a dated artifact identifier, the changed routes and any important shared templates. A metadata helper can affect every article even when only one source file changed. Choose a representative sample and a complete route inventory. Keep the previous working export available before replacing generated files.

Run source checks before packaging

Lint and type checks catch useful classes of mistakes, while focused behavior tests assess transformations such as query encoding. Use commands that exist in the project and fail the release when a required check fails. A test that merely repeats a function’s source does not establish its behavior; include expected output and invalid-input cases.

Inspect the artifact rather than the editor

After building, compare the generated title, description, canonical and social metadata with each page. Parse the structured data and ensure its important facts are visible. Check that every canonical URL has a real generated page and that links and anchors resolve. This verifies the files a host will serve instead of assuming the build copied your intention correctly.

Add a short browser task

Open the tool, change a value, run it and inspect the output. Use the clipboard action where available, then clear or reset the form. Visit a deep article on a narrow screen and check whether code and tables scroll inside their containers. Keep screenshots of the final state where they help a reviewer assess the result.

Package exactly what passed

Create an archive containing the export contents at the intended root. Compare its inventory and bytes with the verified directory. Do not rebuild after approval with different environment values and assume the second artifact is equivalent. Packaging and authorization to publish are separate steps, especially when production credentials are managed outside the application.

Close with production checks after authorized publication

Inspect real response codes, redirects, content types, the sitemap, a deep link and one primary interaction. Record the release time for subsequent search comparisons. A successful upload only proves transfer; it does not establish that the host serves the intended release. Keep rollback instructions attached to a complete previous artifact.

text / WORKED EXAMPLE
Source: lint + types + focused utility tests
Build: generate one complete release artifact
Export: metadata + schema + sitemap + links + assets
Browser: direct route + interaction + narrow viewport
Package: inventory and byte comparison
Publish: separate authorization, then real host checks

Frequently asked questions

Does packaging deploy a static site?

No. A local ZIP is a reviewable artifact. Uploading it requires a separately authorized publication step.

Can local checks establish field Core Web Vitals?

No. Local checks and compressed file sizes do not substitute for real-user performance data.

Further reading

Put the idea to work.

Explore free browser tools for images, text and developer workflows.

Try a free tool