One line.
Deeper website checks.

Get the tag for this website.

Run a free scan and open its report in the browser that created it. Find “Unlock the deep scan (free): prove you own this site”, choose Meta tag, and select Copy tag.

For a saved website, open your workspace, choose Websites, then expand Verify this website and copy the complete tag shown there.

It looks like this:

<meta name="stacksnack-verify" content="YOUR_UNIQUE_CODE">

This is an example, not a working tag. Use the complete line from your own report or website card, including its unique code.

Put it inside the page’s head.

The <head> is the part of your page’s HTML that holds its title and metadata. Place the tag before </head> on the homepage of the website you scanned.

<!doctype html>
<html lang="en">
  <head>
    <title>My website</title>
    <meta name="stacksnack-verify" content="YOUR_UNIQUE_CODE">
  </head>
  <body>
    Your website content goes here.
  </body>
</html>

Using an AI website builder?

Paste this request into the tool you use to edit your app, and add your complete copied tag after it:

Add the verification meta tag below to the HTML <head> of my
public homepage. Keep the name and content exactly as provided.
Use this project’s HTML or server-rendered metadata setup so the
tag is present in the initial HTML response, before JavaScript runs.
Do not display the tag as visible page text.
Show me where you added it and how to publish the change.

[Paste the complete tag from my StackSnack report here]

If your builder has an HTML head or custom metadata setting, you can use that instead. If it asks for separate fields, the name is stacksnack-verify and the value is your unique code. Confirm that it appears in the published page source.

For a plain HTML or Vite project, this is usually the index.html file. For frameworks that generate the head, use their metadata setup; adding it only after the page loads will not work.

Publish, then come back to verify.

1. Publish or deploy your change. Saving it in an editor or preview is not enough. Update the public website at the exact address you scanned.
2. Check the published homepage. Open its page source and search for stacksnack-verify. Confirm that the complete tag is inside <head> and its code matches your report.
3. Return to the same StackSnack report. Complete the existing authorization checkbox and select Verify & run deep scan. Wait for the report to update.

If you are setting up a saved website, select Verify ownership on its website card. This verifies the project; use the report’s verification control when you want to run a deeper manual scan.

Keep the tag published for future verification and monitoring. StackSnack checks ownership again before deeper scans.

Cannot edit the head? Use a verification file.

In your report’s verification panel, choose File. Create a plain text file that contains only the unique code shown there, without a meta tag or quotation marks.

Publish it at this address on your own website:

https://your-website.example/.well-known/stacksnack-verify.txt

Open that address and confirm it returns the code as plain text, rather than your app’s homepage, a login screen, or a “not found” page. Then return to the report and select Verify & run deep scan.

If verification does not work.

• Wrong website address: the tag must be on the homepage of the exact website you scanned. A preview domain, custom domain, and www address can be different websites.
• Change not published: deploy the change, then refresh the public page. If your host caches HTML, wait for the new version or clear that cache.
• Example or old code: use the full line currently shown in the report or website card you are verifying.
• Wrong placement: the tag must be in the initial HTML <head>, not the visible page body, a code block, or a script that runs after loading.
• Login or bot protection: the homepage must be reachable by the scanner. See scanner and firewall setup for help.
• File method returns HTML: configure your host to serve the text file at the exact path instead of routing it to your app.

Still stuck? Email support@stacksnack.io with the website address and the verification error.

What happens next?

Website verification enables the deeper website checks. Database, storage, and two-account tests have a separate backend setup in the report. Adding the website tag does not complete that setup.

Full reports are already free. Verification adds website checks; it is not a paid upgrade.