A user is experiencing the “Your site isn’t ready to show ads” error on a Discourse site hosted by Communiteq. TimothyDonaghue has set up AdSense plugin settings and added the site to AdSense, but still faces the error. neil advises adding a theme component to the <head> section for AdSense verification, which is necessary until the site is verified. TimothyDonaghue confirms that the subdomain was added to AdSense, and neil is unsure about subdomain verification rules. After adding the component, AdSense shows the site as ready, and ads appear. TimothyDonaghue removes the component and configures the plugin, but AdSense reports an error crawling /new. neil explains that /new is only accessible when logged in, so the crawler won’t see it, and advises not to worry about this particular page.
I use Communiteq (formerly DiscourseHosting) and their Adsense plugin — I do not know whether this factoid matters but I share it regardless.
Anyhoo, I have added my necessary publisher ID and slot unit ID’s and such in plugin settings, and also added my site and subdomain on Adsense under their Sites settings. However, I have received this error, see attached:
To add it to the head section, you can create a theme component. Note that the plugin is already going to load the adsbygoogle.js library for you, so once your site is verified by AdSense, you should remove this theme component!
Go to Admin > Customize > Themes > Components and click “Install”. Give it a name like “verify AdSense”.
I did this as you said. One concern: I have not placed it anywhere in my top-level domain — only in my subdomain. I had added that subdomain to Sites settings prior to this. It will still scan and accept that, right?
To summarize, I inserted that theme component, and Google came back saying “Ready” and units finally appeared and it seems functional. Then, I have deleted that theme component leaving only my plugin settings in place.
The “/new” route is only valid when logged in, so I guess you’re supposed to follow these instructions:
Not sure that will actually help since the crawler user won’t see the same topic list as the current user. I wouldn’t worry about that particular page.