⚠️ All images on this page use src URLs that return 301 redirects (audit rule: images3xx)
Each <img src="..."> below points to an old URL that redirects to the actual image.
The browser follows the redirect and renders the image fine — but crawlers, image indexers, and
Google Image Search see the redirect and may fail to index the image or pass full signals.
Open DevTools → Network tab to see the 301 responses before the 200.
Page With Image 3XX Redirects
Pattern 1 — Logo renamed during rebrand
img src: /images/old-logo.svg
→ 301 →
/images/new-logo.svg
The HTML still says src="/images/old-logo.svg" even though the file was
renamed to new-logo.svg after a rebrand. A redirect was added to avoid
a 404, but the img src was never updated.
Pattern 2 — Asset folder restructured (/assets/ → /images/)
img src: /assets/banner.svg
→ 301 →
/images/banner.svg
The /assets/ folder was renamed to /images/ in a site restructure.
A wildcard redirect handles the folder, but the img src in the template was
never updated. Every page load fires a redirect for this banner.
Pattern 3 — Image folder renamed (/img/ → /images/)
img src: /img/product-photo.svg
→ 301 →
/images/product.svg
The old /img/ folder was standardised to /images/.
The product image file was also renamed from product-photo.svg to product.svg.
Both changes combined mean the src now has two mismatches with the final file location.
How to verify with DevTools
- Open this page in Chrome/Firefox
- Press F12 → Network tab → check Img filter
- Reload the page
- Each image will show TWO entries: the redirect (301) and the final image (200)
- The 301 entry is the
images3xx issue
← Back to demo home