How to Fix Schema Image Errors

Schema images are what Google uses for rich result thumbnails, news carousels, recipe cards, and the visual element of most enhanced search features. Get them wrong and your content shows without a thumbnail — losing click-through to competitors who got it right. Errors typically cluster around: bare URLs instead of ImageObject, missing dimensions, relative paths, and images too small for Google's minimums. This guide covers the format, requirements, and tooling for getting it right consistently.

1. Audit current image schema

2. Use ImageObject not bare URLs

Bare URL (limited)

{
  "@type": "Article",
  "image": "https://yoursite.com/article-hero.jpg"
}

Works for basic structured data. Doesn't qualify for Article rich results, which need explicit dimensions.

ImageObject (full)

{
  "@type": "Article",
  "image": {
    "@type": "ImageObject",
    "url": "https://yoursite.com/article-hero.jpg",
    "width": 1200,
    "height": 675,
    "caption": "Optional caption text"
  }
}

Multiple ImageObjects (best for Articles)

{
  "@type": "Article",
  "image": [
    {
      "@type": "ImageObject",
      "url": "https://yoursite.com/article-hero-16x9.jpg",
      "width": 1200,
      "height": 675
    },
    {
      "@type": "ImageObject",
      "url": "https://yoursite.com/article-hero-4x3.jpg",
      "width": 1200,
      "height": 900
    },
    {
      "@type": "ImageObject",
      "url": "https://yoursite.com/article-hero-1x1.jpg",
      "width": 1200,
      "height": 1200
    }
  ]
}

Google picks the right aspect ratio for each surface. Article rich results in different layouts use different ratios; providing all three maximises placement.

3. Meet Google's dimension requirements

Article rich results

• Minimum width: 1200 px
• Preferred aspect ratios: 16x9, 4x3, 1x1
• Format: JPEG, PNG, WebP, AVIF, or GIF
• Max file size: 5 MB
• Crawlable URL (not blocked by robots.txt)

Product images

• Minimum width: 696 px (less strict than Article)
• Square (1x1) preferred for shopping carousels
• Background colour: clean white usually performs best in shopping

Recipe images

• Minimum 1200 px wide
• Multiple aspect ratios highly recommended for recipe card carousels

4. Use absolute URLs

// WRONG
"url": "/images/article-hero.jpg"
"url": "//cdn.example.com/image.jpg"  // protocol-relative also fails

// RIGHT
"url": "https://yoursite.com/images/article-hero.jpg"
"url": "https://cdn.example.com/image.jpg"

In templates, prepend the canonical domain:

// WordPress
"url": "<?php echo esc_url(get_the_post_thumbnail_url($post, 'large')); ?>"

// Next.js
"url": `https://yoursite.com${image.url}`

5. Verify accessibility

Google needs to fetch the image. Common reasons fetching fails:

• URL behind authentication (admin-only paths)
• URL returns 404 or 500
• Hotlinked from another domain that blocks Googlebot
• Blocked by robots.txt
• CDN signed URL that's expired (S3 presigned URLs)
• CORS restrictions (rare but possible)

Test image URLs

# Verify Googlebot can fetch
curl -A "Mozilla/5.0 (compatible; Googlebot/2.1)" \
     -I https://yoursite.com/images/article-hero.jpg

# Expect: 200 OK, Content-Type: image/...

6. Logo schema for Organization

Organization.logo has stricter requirements than article images:

{
  "@type": "Organization",
  "@id": "https://yoursite.com/#organization",
  "name": "Acme Co",
  "url": "https://yoursite.com",
  "logo": {
    "@type": "ImageObject",
    "url": "https://yoursite.com/logo.png",
    "width": 600,
    "height": 60
  }
}

Logo specifics

• Maximum dimensions: 112x112 px (for Google's knowledge panel)
• Or wider rectangle for AMP logo (600x60 or similar)
• SVG, PNG, JPEG accepted; SVG ideal
• Solid backgroud or transparent — both work

7. Build image schema correctly

WordPress

$thumb_id = get_post_thumbnail_id($post);
$meta = wp_get_attachment_metadata($thumb_id);
$url = wp_get_attachment_url($thumb_id);

$image_object = [
  '@type' => 'ImageObject',
  'url' => $url,
  'width' => $meta['width'],
  'height' => $meta['height']
];

Next.js with Sharp or similar

import sharp from 'sharp';

async function getImageDimensions(filePath) {
  const meta = await sharp(filePath).metadata();
  return { width: meta.width, height: meta.height };
}

// At build or request time
const { width, height } = await getImageDimensions(article.imagePath);
const imageObject = {
  '@type': 'ImageObject',
  url: `https://yoursite.com${article.image}`,
  width,
  height
};

8. Verify