SEO Problem: Images will never be indexed
See original GitHub issueI just found out that in the PageSource itself all images have this format:
<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" width="90" height="90" alt="" loading="lazy">
That is a total disaster for all SEO Crawlers as they will never index any of the images on the site. Why not just display the image-url with /_ipx/
in the front?
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
14 Top Reasons Why Google Isn't Indexing Your Site
The first reason why Google won't index your site is that you don't have a domain name. This could be because you're using...
Read more >Not all images indexed in Google | SEO Forum - Moz
Hi all, Recently, got an unusual issue with images in Google index. We have more than 1500 images in our sitemap, but according...
Read more >Fixing A Google Images Indexing Problem Caused By ... - GSQi
In addition, having your images properly indexed can lead to stronger listings in Google's Top Stories (if you're a news publisher). Therefore, ...
Read more >Should you have your images indexed or added to no ... - Reddit
Also I've never had a problem with stock photos in the past but the client said they read that using stock images can...
Read more >Product Images not indexed by Google - BigCommerce Support
Doing a site: search in the Image Search shows that there seems to be no problem in Google indexing the images and associating...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
and by the way: @shadow81627 I’m glad you like it 😃
@thomas4Bitcraft as @shadow81627 says it is due to lazy loading. I have the same on my lazy loaded (
loading="lazy"
) images but not on my ‘normally’ non-lazy loaded images, all usingNuxtImg
component.