Question 1

What is screamingfrog.co.uk's Open Graph type?

Accepted Answer

screamingfrog.co.uk declares `og:type` as `website`. This tells LinkedIn how to categorize the content when generating a preview.

Question 2

What size is screamingfrog.co.uk's social share image?

Accepted Answer

screamingfrog.co.uk's `og:image` is 680×508 pixels. LinkedIn recommends 1200×627 (1.91:1 aspect).

Question 3

What headline does screamingfrog.co.uk use for social previews?

Accepted Answer

screamingfrog.co.uk's social headline is "Screaming Frog | SEO, Search Engine Marketing Agency" (52 characters).

Question 4

What description does screamingfrog.co.uk use for social previews?

Accepted Answer

screamingfrog.co.uk's social description reads: "We run remarkably successful search engine optimisation (SEO) and paid search (PPC) campaigns using a unique blend of data, technology & creativity." (148 characters).

Question 5

What site name does screamingfrog.co.uk display on social cards?

Accepted Answer

screamingfrog.co.uk sets `og:site_name` to "Screaming Frog". This appears as a small attribution label on Facebook, LinkedIn, and Slack.

Question 6

What's the biggest issue with screamingfrog.co.uk's LinkedIn preview?

Accepted Answer

Image won't fit social cards (680×508, 1.34:1). Your square-ish image will be cropped to 1.91:1 on Facebook, LinkedIn, and Slack, and to 2:1 on Twitter. Use 1200×630 (universal) or 1200×675 (Twitter-optimized) for predictable rendering.

Question 7

How can I improve screamingfrog.co.uk's social previews?

Accepted Answer

Review the recommendations above - they list specific issues and provide ready-to-paste meta tag snippets. The highest-impact fixes are usually a properly sized `og:image` (1200×627), a clear `og:title` under 60 characters, and a 50-155 character `og:description`.

How screamingfrog.co.uk Looks on LinkedIn

LinkedIn preview

LinkedIn

Recommendations

Analysis

Frequently Asked Questions

See screamingfrog.co.uk on other platforms

Validate other sites on LinkedIn

Validate your own URL