Metadata evidence, not guesswork
Manually audit the metadata behind a public link preview
Use the checklist to review four metadata signals and their sources manually, then turn missing fields into a concrete remediation list.
Automatic URL inspection is currently unavailable. Use this guide to review the four metadata signals manually, then continue in the manual editor or AI image generator.
This guide does not inspect a URL. It does not download a remote image or verify pixels, file size, crop behavior, or safe areas.
A manual metadata audit
- 01
Resolved title
Locate og:title, twitter:title, and the document title in View Source, then record which fallback should win.
- 02
Resolved description
Compare og:description, twitter:description, and the standard meta description in the page source or CMS.
- 03
Resolved site name
Confirm og:site_name or the hostname fallback, then correct the publisher identity in the CMS.
- 04
Declared image and host
Open the image URL in a browser or DevTools to check dimensions, response, crop, and safe areas.
Metadata audit FAQ
Questions about a manual metadata audit
How to edit durable metadata, validate the declared image, and refresh platform previews.
Where should I edit the metadata?
Edit durable metadata in the application, CMS, or page template, then deploy the resulting HTML.
How should I inspect the declared image?
Open the declared image URL to check pixels, bytes, response headers, crop behavior, and safe areas.
How do I refresh a platform preview?
Use the platform’s official debugger or refresh workflow because each network keeps its own cache.
From audit to a resilient preview
Fix the evidence, then build the asset
Open the manual editor to assemble the final card, or use the AI generator to create source artwork.