← All installation guides Hosting control panels

Install a VerifySeal seal on cPanel

Use cPanel File Manager to add the seal to a website template and create the domain callback file.

CP
Recommended methodJavaScript embed recommended
Website installation

Step-by-step instructions

  1. 1

    Find the document root

    Open cPanel, choose File Manager and locate the document root for the registered domain. It may be public_html or a separate addon-domain directory.

  2. 2

    Back up the website file

    Download the footer, template, HTML or PHP file you will edit so it can be restored if the layout changes unexpectedly.

  3. 3

    Insert the seal

    Use Edit or Code Editor and paste the Recommended JavaScript embed where the seal should appear. Avoid the visual HTML editor if it removes script tags.

  4. 4

    Publish and verify

    Save, purge page or CDN caches, load the live HTTPS page and click the seal to verify the certificate opens on the correct hostname.

Open cPanel File Manager documentation ↗
Domain ownership callback

Complete domain validation on cPanel

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

  1. 1

    Turn on Show Hidden Files in File Manager, then create .well-known in the registered domain document root.

  2. 2

    Create verifyseal.txt inside that folder and paste the callback code on its own line. Keep other VerifySeal codes on separate lines.

  3. 3

    Confirm the public HTTPS callback URL returns the code without a login, redirect or error page.

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
  • If a CMS manages the site, follow its CMS guide instead of editing generated files that an update may overwrite.