David N. Posted November 6, 2023 Posted November 6, 2023 I see a link to an URL on our site as one of the results of a Google search, and when I click it all I get is a reddit embed. No suite wrapper. The URL in the Google SERP looks like this: https://www.my-site-name.com/index.php?app=core&module=system&controller=embed&url=https://www.reddit.com/r/name-of-the-reddit-thread
Marc Posted November 6, 2023 Posted November 6, 2023 Im not sure what you are asking here. It appears google have indeed indexed that link from somewhere.
David N. Posted November 6, 2023 Author Posted November 6, 2023 That's an issue though: someone does a search on Google, they click a search result that has my site's URL and favicon, only it takes them to a blank page where the only thing displayed is a reddit link. I'm not sure how Google could have decided to index that, but couldn't that be prevented? Is this a common thing with embeds? Them showing up as search results? Here's what they see after clicking the link - an empty browser window with only the reddit embed:
Marc Posted November 6, 2023 Posted November 6, 2023 My best guess would be that someone has added that link elsewhere for google to have been able to index it. I cant say Ive ever seen them show up on search engine results myself, no. What you are seeing when you click the link is actually correct, as thats all the embed contains
David N. Posted November 6, 2023 Author Posted November 6, 2023 (edited) 10 minutes ago, Marc Stridgen said: My best guess would be that someone has added that link elsewhere for google to have been able to index it. In search console under "Discovery", Google lists only two referring pages for that URL: the topic that contains the embed, and the specific comment that contains the embed. So apparently, Google has found the internal link when scraping the topic, and indexed only the URL of the embed. Edited November 6, 2023 by David N.
Marc Posted November 6, 2023 Posted November 6, 2023 Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release. David N. and georgebkk 2
David N. Posted November 6, 2023 Author Posted November 6, 2023 Great, thank you @Marc Stridgen! Marc 1
Solution Marc Posted January 24 Solution Posted January 24 This issue has been resolved in the recently released 4.7.15 version. Please update your site if you are still experiencing the issue, and let us know if you see any reoccurrence. David N. and SeNioR- 2
David N. Posted January 24 Author Posted January 24 1 hour ago, Marc Stridgen said: This issue has been resolved in the recently released 4.7.15 version. Please update your site if you are still experiencing the issue, and let us know if you see any reoccurrence. Great, thank you Marc for letting me know. I'm updating now.
Recommended Posts