By default, the validation page lives at Virtualbadge.io. With the credential validator, verification runs on a page of your own website. QR codes and links of new credentials then lead there.
Step 1: Create a page on your website
Create a dedicated page for verification in your CMS, for example at /verify-certificate. Exclude the page from search engine indexing so it does not appear in search results.
Step 2: Open the instructions
Open “Settings” and “Integrations”. Under “Credential Validator”, click “Instructions”. The “iFrame Integration” dialog leads through the setup in three steps.
Step 3: Add the iFrame
In the first step of the dialog, “Add the iFrame”, choose the language and copy the code for HTML or WordPress to the spot where the validator should appear. Paste the code unchanged. The outer container should have the full width of the window and not be limited by any other container.
Step 4: Add the library
Insert the script from step 2 of the dialog, “Add the library”, right before the closing body tag. It resizes the iFrame automatically and forwards links to individual credentials to the iFrame. Without the script, the validator opens empty.
In WordPress, install the plugin “Virtualbadge.io Certificate Validator”, create a Group block at full width and place a Custom HTML block with the shortcode [VBCertValidator] inside it.
Step 5: Report the address
The third step of the dialog is called “Set the URL”: send us the address where the validator can be reached in the chat. We switch the validation path to your page. If everything is set up correctly, you see a sample certificate with an input field on your page.
Step 6: Test with a certificate
Issue a new test certificate and open the validation link. The address ends in ?credential= followed by the credential's number. Your website must not strip this parameter, and redirects have to keep it.
| What you see | Why | What helps |
|---|---|---|
| The validator opens empty | The script is missing | Insert the script right before the closing body tag |
| The page shows the sample certificate instead of the credential | The credential parameter gets lost in a redirect | Exempt the parameter from stripping rules and check your redirects |
| The validator is narrow or cut off | An outer container limits the width | Give the container the full width of the window |
| Older credentials still open the page at Virtualbadge.io | Only credentials issued after the switch use your page | Not an error; older links stay valid |
Follow this guide with your own data.
Check the result
- The link of a new credential opens the verification on your website.
- The QR code on the PDF leads to the same page.
- The page does not appear in search engines.
More on this: Verifiable Certificates
Frequently asked questions
Does our own page also apply to older credentials?
No. Only new credentials are verified on your page. Older ones keep the path at Virtualbadge.io.
What happens if we move to a smaller plan?
Validation then runs on the default page at Virtualbadge.io again. The identification numbers of the credentials stay the same.
Our website strips parameters from the address. What should we do?
Exempt the credential parameter from that rule. In TYPO3 it belongs on the list of parameters excluded from the cacheHash.
How do companies we have recognized show their credential on their own website?
With a Trust Badge: the company pastes a short HTML code, and every click on the badge leads to the validation page. The guide Embed Trust Badges on partner websites shows the steps.