I need some assistance as the URL preview card for socials is not working. I believe this to be an issue with vercels security features after using the Vercel AI tool.
Has anyone had the same issue and how did they resolve?
As you can see there is a 403 error.
Hi @info-uforikaio!
Welcome to the Vercel Community! I’m also happy to help 
Can you share your meta data code and generally more about your project (e.g. is it on Next.js)? It’d help us debug!
I just have a html website which i push via Github to Vercel, i dont think i have set up next.js
<meta property="og:type" content="website">
<meta property="og:locale" content="en_US">
<meta property="og:title" content="I've just Shared my personal referral link">
<meta property="og:description" content="Apply for WL Now, Earn your Ticket for 130 SOL prize pool">
<meta property="og:image" content="assets/images/kholtak/kholtakticket2.jpg">
<meta property="og:image:type" content="image/jpeg">
<!-- Twitter Card Meta Tags -->
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="I've just Shared my personal referral link">
<meta name="twitter:description" content="Apply for WL Now, Earn your Ticket for 130 SOL prize pool">
<meta name="twitter:image" content="/assets/images/kholtak/Kholtakticket.jpg">
You need to use /assets instead of assets it’s a image routing issue that can work in local development but break in deployments, super annoying thing that slips through easily, we had this issue with ladybird.org until adding a test suite that explicitly checks we always add the / in front of any local route
@info-uforikaio, I think @versecafe is spot on here! Can you give this a go and report back?
I updated as suggested but its not working.
the 403 error is still there irrespective of the code:
I have tried all variations of HTML and image sizes to try and de-bug, i have updated the robots.txt file so there are no issue there, when using the AI support tool on vercel it mentioned something regarding the security settings?
Hi @info-uforikaio, if the deployment URL you are using in the sharing debugger tool is a protected deployment it may cause a 403 error. You can see this in project settings → deployment protection.
To get around this for testing purposes you can use one of these bypass methods. .
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.