Opened 3 years ago
Last modified 3 years ago
#5807 new defect (bug)
wp.org images shouldn't use wordpress.com/mshots/ and similar
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | low | |
| Component: | Showcase | Keywords: | seo |
| Cc: |
Description
Showcase pages (like https://wordpress.org/showcase/the-streamy-awards/) and the commercial themes page use https://wordpress.com/mshots/v1/ as an image CDN.
However, that /mshots/v1/ path is blocked via https://wordpress.com/robots.txt (as are equivalent paths, like https://s0.wp.com/mshots/v1/).
That means that Google etc can't see any of those images, which causes SEO problems.
These images should be altered to use https://s.w.org/.
Change History (4)
#2
@
3 years ago
I'm not sure I follow your logic. The image is an important component of the page; it's literally the whole point of the showcase. Why would blocking it make sense?
#3
@
3 years ago
One hacky workaround for this would be to load mshots via the Photon CDN, which would take care of this short term at least.
https://i0.wp.com/wordpress.com/mshots/v1/http%3A%2F%2Fwww.streamys.org%2F?w=1036
Not ideal, but I tend to agree that not blocking the majority of the visual content on these pages is surely going to help the SEO factor in some form.
The mshots are literally screenshots of other sites. Why would these make any difference to our SEO?
If anything, I would think that blocking *all* images on showcases from Google's view would be preferable from an SEO perspective. None of the images there are relevant to any of our content.