Skip to main content

Issues with goog-rtopics

James Dunworth
Edited

Sections labeled "Discover More" are being injected into the body of my content. However, they appear to be completely non-functional. When I (or my readers) click on the topics, nothing happens.

You can see an example here: https://www.compostmagazine.com/rats-in-compost/ 

I’ve inspected the code, and these units are identified by the class: <div class="goog-rtopics" aria-label="These are topics related to the article...">

It appears these are Google Related Search units. While I don't mind the concept, having "dead" buttons in my content is a poor user experience and may look broken to my audience.

Grow Settings: I have checked my Grow Publisher Portal. Turning off the "Inline Widget" in Grow did not remove these, confirming they are ad-related and not Grow-related.

Troubleshooting: Tested in Incognito mode with ad-blockers disabled. The buttons still appear but remain unclickable.

Incompatible apps: I do not currently have a lazy loading app set, and I don't think I can identify a problem here: https://journeymv.zendesk.com/hc/en-us/articles/24233893069595-Conflicts-and-Compatibilities

Any ideas on how to turn this off? 

0

Comments

2 comments

Date Votes
  • Support
    • Journey Support Team

    James Dunworth Thanks for reaching out! This doesn't look to be something that's implemented through the Journey script. I checked the link you sent along, but I'm not seeing ‘Discover more’ load in

    Did you figure out what was causing this? 

    0
  • James Dunworth

    Thanks for the swift reply. 

    Yes, I disabled google site kit and the problem disappeared. Then I re-enabled it and found that the connection to google adsense still existed. i removed this and it seems to have resolved the issue. 

    0

Journey is Self Supported

Our support staff is monitoring this forum everyday for bugs related to ad delivery, the display and functionality of the Journey dashboard, and any bugs related to the onboarding process. We are typically unable to assist with non-bug related issues like RPM performance expectations, issues setting up the ads.txt file, and questions already answered by our existing help docs. Read here for a more detailed breakdown of how Journey is self-supported and our recommendations for how to find answers to common issues.

Please sign in to leave a comment.

Powered by Zendesk