Confirm what can be public

Review the company name, contact channels and service descriptions on every page. Check publication permission separately for client names, screenshots and staff photos. Keep test data, unsigned partnerships and unearned credentials out of public claims. Assign a traceable source to each factual claim and have the publishing owner review it.

Walk the visitor journey

On a phone and a desktop, move from the homepage through services, articles and contact. Use the keyboard through menus and filters and check visible focus. Disable JavaScript and confirm that core text and contact details remain available. Visit a missing address and make sure it does not return the homepage as a successful response.

Check origin and indexing

Distinguish the preview origin from the production origin. Mark previews as noindex and rebuild canonical URLs, language alternates and the sitemap when the production origin changes. Check HTTPS, asset paths and sharing images. Robots directives are not access control: confidential material must never enter a static build.

Prepare rollback before switching

Save the version, build command and release checksum. Verify a new release in a separate directory before switching the site root and retain the previous release. After deployment, check the homepage, deep links, 404 and existing download paths. Record observed results, rather than only a deployment success message.

Original insights from Diande Technology.
← Back to insights