What does the Link Preview API return?+
It returns structured URL metadata: url, title, description, image, logo, publisher, author, date and lang. Your application can use those fields to build rich link previews, prefill website entries or enrich saved links.
Is the preview image a screenshot of the website?+
No. The image field contains a cover or preview image reference extracted from the webpage metadata. It does not capture the page as it appears on screen. Use a website screenshot workflow when you need an image of the rendered page.
Which preview card styles can I try?+
The console offers Hero, Inline, Notification, WhatsApp and Tweet previews. These are ways to inspect the same metadata in different layouts. The API provides the fields for you to render cards that fit your own application.
Can I request metadata in another language?+
Yes. The access-language setting adds an optional locale code, such as en for English. When a matching hreflang page is available, it is tried; otherwise the original page is returned. Omit locale to use the default. This selects a page language rather than translating its content.
Why might a field be missing or need correction?+
A website's metadata may be incomplete, outdated or inconsistent. Some fields, such as author, can be empty. Review the preview and raw JSON, and let your application provide fallbacks or editorial corrections where needed.
Will WhatsApp or X display exactly the same preview?+
The console styles help you review how a card can look. Third-party platforms fetch, cache and crop previews independently, so their final display may differ. AdsCrawl provides metadata for your integration; it does not post the link to those platforms or control their previews.