Did you change the site design at some point?
The placeholder table (-> Generated Ads) shows WP placeholders from before.

Are you intentionally excluding ads from within the main content? I'm just seeing top of page, sidebar and bottom anchor ads mostly.

Is your site now built entirely with React? That's not fully compatible with standard integration methods and could be interfering with the ad placeholders too.

  • Yon replied to this.

    Mohammad2306 Yes its built fully with react. Not sure how that excludes works. I think because its a custom react site it dosent detect the content. If there is a way to manually place them inside with a div or something similar let me know. Site design never changed. I think the react and standard integration has messed something up.

      Yon - you can get the tags for each placeholder from your ad tester menu, but it's very possible that this will still not fix the issue that you're having. The problem is that React will load assets client side, while ads are loaded server side. This means your content is essentially overwriting your ad setup.

      here's the link to the placeholders page in your dashboard if you'd like to try and manually insert ads ->https://pubdash.ezoic.com/ezoicads/adpositions/placeholders

      If not, we can enable JS based integration options with Ezoic - It'll be much lighter on features, but you should be able to get in content ads showing on your site.

      • Yon replied to this.

        HarryB Hey Harry. Yes JS would be great. That wouldn't affect revenue though correct? What do you mean by lighter features?

          Yon Hi, so our Basic Ads platform (which requires JS integration) doesn't come with speed, video or SEO features. Your ability to control or change ad setups would also be more limited.

          Let us know if that is something you're still interested in. Ultimately there'll be a trade off in getting more ads showing vs giving up access to some features

          • Yon replied to this.

            Ethan Yes I'll give it a go. By video, you are referring to video ads?

              We're referring to Flickify and Humix 🙂
              We don't limit the advertisers creatives --- that's entirely up to the advertiser.

              Your account has been switched over to BasicAds now - you'll see instructions in the Dashboard.
              Make sure to remove cloud integrations first (so switch the NS at the registrar to point back to your host).

              Let us know once you've completed the steps in the BasicAds dashboard and we can make sure the ad setup is pushed through.

              • Yon replied to this.

                Tucker_P_Ezoic Thanks Tucker. Oh, I see. Great so I added the script and changed the Name Servers back. Let me know if anything else is required. Appreciate the awesome support.

                  Let's give it another few hours for the nameserver change to be detected on our end - that should just allow things to kick in as needed.

                  • Yon replied to this.

                    Tucker_P_Ezoic Hey Tucker, NS have have been detected. But the ads.txt file was added automatically but not showing and the script was only added to specific pages so if you can mark that as done also? Greatly appreciated

                      Yon Hey,

                      In terms of the script, you need to add that to your site header which then automatically applies the script site wide. Looks like you actually need to create a header on React, and these two guides should run you through that:
                      https://stackoverflow.com/questions/67864378/how-to-change-header-and-footer-of-a-specific-webpage-while-using-react-route
                      https://reactgo.com/reactrouter-header-footer/

                      In terms of the ads.txt file, we cannot add that entirely automatically for script integrated sites. You need to add in a redirect so your ads.txt file points to the Ezoic ads.txt app - there is additional instructions in the dashboard on how to set up an ads.txt redirect

                      • Yon replied to this.

                        Ethan Hi Ethan, the script has been applied to the /blog directory and the ads.txt can be found in petfluence.co/ads.txt what else needs to be done?

                          Yon Hi, the script would need to be on the site header, so that it is accessible on the entire site, rather than just the blog directory. The guide I sent above should run over how to add a header with react, or your host may be able to help with that.

                          In terms of the ads.txt, you need to set up a redirect as I mentioned, because we dynamically load ads.txt files. The .htaccess redirect is probably the best option for you to set up. Here's a guide on that: https://www.semrush.com/blog/301-redirect-htaccess/

                          • Yon replied to this.

                            Ethan So I've done what you said. But now the ads will be showing on the whole site and I need them just on the /blog directory.

                            • Yon replied to this.

                              Yon Just got it fixed by adding them to the "DISABLE ADS BY PAGE"

                              Last question. Are the ads appearing for you as they aren't being shown on my side?

                                Yon
                                I currently do not. Did you change the header script for these pages? Or did you add any new rules to disable ads for these pages?

                                • Yon replied to this.

                                  Charlie No i did not. The header script is showing when I pull up the dev tools. Very weird.

                                  • Yon replied to this.

                                    Yon The url is /blog which they should be showing on

                                      We've just re-run the placeholder generation.
                                      Clear all caching for the site now, and you should start seeing ads over the next few hours.

                                      • Yon replied to this.