Plugin Author
kubiq
(@kubiq)
Hello, it actually doesn’t matter, because fallback is needed only when your browser doesn’t support WEBP and if it doesn’t support WEBP and you don’t have original JPG or PNG then it will still display broken image, so what’s the point?
It breaks when Google (and other crawlers) don’t send agents that don’t declare support for WebP so your erroneous .htaccess rules point them to original files that were deleted.
The fix is super easy, as I mentioned originally.
Plugin Author
kubiq
(@kubiq)
I’m sure all the Google agents support webp, as they recommend to use it in their pagespeed tool.
But let’s say there is some crawler without webp – it would mean that it is collecting content for system that doesn’t support webp, so when difference is if it receives 404 or a webp code that it cannot process – it will still result into broken image.
Idk, maybe I’m missing something, if you can give me some real example that I can actually try, I would be grateful and if this is true, then I’ll ofc fix this, but currently I don’t see any reasonable usecase for that
Yeah you didn’t test the ‘delete’ option or consider why you’d leave the substitution code in the .htaccess when deleting the originals?
I saw all the complaints about SEO issues, tested it with Google tools, confirmed the issue, tested the simple fix, and then I tried to help you.
Plugin Author
kubiq
(@kubiq)
Yes I know there is no logical reason to leave that htaccess code when delete option is active – the only reason is that I don’t want to spend time on rewriting code that will not change anything at the end…
I know only about one thread in here about SEO and that guy never responded back.
So can you please share the link for that Google tool you’re talking about, so I can test this?
Thanks