← All installation guides Modern deployments

Install a VerifySeal seal on Netlify, Vercel, Cloudflare Pages or GitHub Pages

Commit the seal to the site template and deploy the callback file from the project’s public/static directory.

GIT
Recommended methodJavaScript embed recommended
Website installation

Step-by-step instructions

  1. 1

    Edit the source project

    Add the Recommended JavaScript embed to the shared footer or page source in the repository. Do not edit generated deployment files in the provider dashboard.

  2. 2

    Commit the change

    Review the diff, commit the seal placement and push it through the normal production deployment workflow.

  3. 3

    Wait for production deployment

    Confirm the deployment is complete and the custom domain is assigned to the new version.

  4. 4

    Test the live certificate

    Open the production custom domain, click the seal and compare the hostname and organization on the certificate.

Domain ownership callback

Complete domain validation on Netlify, Vercel, Cloudflare Pages or GitHub Pages

Use the unique callback code displayed on the customer order. Never reuse a code from another domain or application.

  1. 1

    Create public/.well-known/verifyseal.txt or the equivalent static-assets path used by the project.

  2. 2

    Place the callback code on its own line and include the file in the deployment. Keep any other VerifySeal codes on separate lines.

  3. 3

    Confirm the provider serves the file at the exact HTTPS callback URL without a framework rewrite.

Testing checklist

Confirm the installation is working

01

Visible

The complete 300 × 106 seal is visible and not cropped on desktop or mobile.

02

Clickable

The seal opens the VerifySeal public certificate rather than a copied local image.

03

Current

The certificate status is verified, the expiry is current and the details match.

04

Correct domain

The registered production hostname matches the website displaying the seal.

Platform notes
  • Preview deployment hostnames are expected to differ from the registered production domain.