v0
Clickjacking protection on a v0 app
v0 generates UI you then deploy, often on Vercel. The scan starts at the deployed URL. It sees the shipped page, not the v0 chat that produced the components.
Whether another site can frame the page.
What the scan can see
The scan looks for X-Frame-Options or a CSP frame-ancestors directive. One of them is enough. If both are missing, the finding is that the page can be framed.
What it does not do
We do not embed your page in a test frame. The header is the evidence.
A component that was generated but never deployed is not part of the check.
What to do next
Add Content-Security-Policy: frame-ancestors 'none', or X-Frame-Options: DENY, unless a specific partner must embed the page.
Questions
Does this open my v0 project?
No. A component that was generated but never deployed is not part of the check.
Can the scan prove clickjacking protection is fully fixed?
We do not embed your page in a test frame. The header is the evidence.
What should I do if the scan finds it?
Add Content-Security-Policy: frame-ancestors 'none', or X-Frame-Options: DENY, unless a specific partner must embed the page.
Scan a URL you own
The same free check as the homepage. You confirm the app is yours before it runs.