google-adsense | Web Component wrapper for Google Adsense code using Polymer | Web Framework library

Ok,

my mistake. You first need to put the script shown in the picture above in your normal html code (for vue it would be the index.html after npm run build).

Then google checks and afterwards you get all the information you need ;)

Oh I got it, it seems like there was a misspelling in importing of the component, and thus wasn't connected to the main nuxt network, meaning the component doesn't adhere to the hot reloading watched file.

You just need to wait, when you first implement Adsense it will give this error. It took until next morning for Adsense to start displaying ads. I implemented their Responsive ad type.

c/o https://stackoverflow.com/a/38351709/109941

Supposing your HTML is contained in a variable for the following.

The usage of preg_replace should be a better option, here's a function that should help you a bit:

For complete URL using positive lookbehind:

I also tried the data-adtest="on" approach and it didnt work for me either. I found two different approaches for testing:

• Using Placeholders, the way most Google Adsense Forum Entry suggesting it. e. g. here: https://productforums.google.com/forum/#!msg/adsense/RLeUEq6na-w/i93-TFVRiHUJ (I've tried it on my own and I was satisfied with the solution)
• Use your own (dev) domain explained here: https://medium.com/@jeffersonlicet/testing-ads-on-localhost-300215b415d6 (I was not able to tried this on my own, because I dont have a domain)

If you have opened the developer console you would have saw that you got an 403 Error. The reasons for this error are further explained here: https://www.shoutmeloud.com/adsense-403-forbidden-error.html. To make it short: Adsense Crawlers reject Localhost. Thats you why you got a white space instead of ads.

But if there is a third way I would also be glad to hear it.

If you believe you did nothing wrong, didn't click your own ads or violate any of their policies, then you should appeal

Regarding alternatives, from experience the Facebook Audience Network (FAN) seems to be a better alternative, in fact you can earn more from FAN than with admob, however there's an issue of low fill rate as users must have the Facebook app installed on their devices. You can use other networks as fallback when there's no ad to serve

Also note that FAN is strict with its policies so make sure there isn't a repeat of whatever caused the deactivation of your adsense account.

So there are few themes in your webpack.config.js, some of which conflict. Just going to list them so I can better understand what I think you are trying to achieve.

Theme 1

You have an entry called vendor that is clearly referencing a minified jQuery library you have presumably downloaded and placed in the directory specified.

Theme 2

You also have an expose-loader that is essential exposing the jquery library from its node_modules probably listed in the dependencies of your package.json.

This makes the jquery in the node_modules available as $ and jQuery in the global scope of the page where your bundle is included.

Theme 3

You also have included the ProvidePlugin with configuration for jQuery.

The ProvidePlugin is supposed to inject dependencies into the scope of your module code, meaning you do not need to have import $ from 'jquery' instead $ and jQuery will already be available in all of your modules.

Conclusion

From what I have gathered I think you're trying to bundle jQuery from the static file at ./src/main/webapp/js/vendor/jquery-3.3.1.min.js in a vendor bundle.

You are then trying to expose the libraries in the vendor bundle to the global scope (jQuery).

Then also have your application code able to import jQuery from what is made available by the vendor bundle in the global scope.

Answer

So if that is what you are doing you need to do the following things.

Firstly, check in your package.json files dependencies for jquery. If its there you want to remove it, there's no need for it if you're going to use your jquery-3.3.1.min.js file instead to provide jQuery to your application.

Secondly, change your test of the expose-loader to trigger when it sees your jquery-3.3.1.min.js file in your entries, not resolve it from the jquery dependency from your node_modules.

This regex pattern should do the trick.

I had almost the same problem once. With the settings I made Google was not able to get advertisement for my page. See the answer:

https://support.google.com/adsense/answer/113262?ctx=tltp&hl=en

The solution (for me) was to add a new unit and a completely new channel as well. If You check the If no ads available option You can choose from 3 options:

• Collapse the ad unit, otherwise show blank space (default)
• Collapse the ad unit, otherwise show colour
• Show other URL

If the problem persists you should send a feedback message including the URL, the exact description of the problem. This is maybe an internal problem in Googles algorithm (as if it is not able to find ads for you).

Important: Have you checked from different browsers, other machines and Google accounts? The algorithm behind the whole AdSense motor is relying on those information heavily. (It means that if You do not see ads on your site, it still could show some to others.)

Edit: If You tried to use a newly created unit and it did not work, I suspect a google bug and I am mostly out of ideas. In my case this solved the problem, but if You are unlucky with it You really should use an other account if possible.