So you’re looking for a way to fix the Ezoic origin error that happens when you integrate Ezoic into your website. I was struggling with that error for months, with frequent talks with Ezoic and my hosting provider’s support, and no one could figure it out.
Well, I might have found a solution. After what I tried, I haven’t run into the issue at all, and my website even loads faster than it did before. Of course, there’s a chance it won’t work for you, but it might point you in the right direction.
What You Need to Know:
if you break your website, I’m not responsible. These fixes don’t require much effort and there aren’t any risks involved but there’s a chance your website might go down for a bit or you’ll lose a few days of ad revenue. If you want to reset all the settings back to default, you need to change your nameservers, and then add them to Ezoic again, a process that can take up to 72 hours.
The Ezoic origin error will sometimes completely stop your website from loading (show you the error and that’s it) and other times it will load but very slowly. It’s very random and annoying. It also tends to happen more on the backend, for example, when you’re logged into the WordPress dashboard and trying to configure your website.
When you’re having origin error problems, your website might:
- Display “Origin Error” in-text in the top left corner.
- Ask you to solve a CAPTCHA
- Connection timed out
- Takes obnoxiously long to load
- Say “Error Communicating with Origin”
What’s interesting about this error is that both Ezoic’s and your host’s support won’t usually be able to fix it. I contacted them many times about it, and both sides weren’t able to fix the issue, although they did provide me with some leads.
And Ezoic has an entire support article dedicated to possible solutions to this problem, but most of them didn’t work on my website, or they only were a temporary solution. If you already went through that list, I have some alternative fixes you can try. My suggestion is to first try Ezoic’s official fixes and then try the fixes on this list.
First: Contact Ezoic and Your Host
It’s best to reach out to both Ezoic and your hosting company for advice. In some cases, one end will be able to find a solution for you. If not… well, that’s why this article is here.
Your hosting company’s default suggestion will probably be to change from shared hosting to a VPS or cloud hosting plan. As you can imagine, that costs significantly more than shared hosting which is what most people use, even though it should be much faster.
The reason they recommend using a VPS is that you can bulk-white list IPs on most VPS services, at the cost of risking your own security. I wasn’t about to make a hugely expensive and technical move, unless absolutely necessary, so I decided to look into ways to fix the Origin error on my own.
Ezoic also creates its own cache and other settings for your website, which can interfere with your hosting company’s settings. Not to mention most of the popular WordPress speed plugins don’t work well with Ezoic. In fact, Ezoic recommends disabling all speed-related plugins and functions from your website.
Note: I recommend reaching out to Ezoic’s support centre. In most cases, they can help you narrow down the issue, it could also be caused by a misconfigured DNS record.
The Ugly Truth: Shared Hosting is the Problem
Before we get into the solutions for the origin error, it’s important to be clear about some things. Look, I’ve been dealing with this issue for a really long time, and I understand how incredibly frustrating it is.
Here’s the thing:
The truth is most shared hosting companies, especially the budget ones, are not compatible with Ezoic’s tech because Ezoic uses proxies. These proxies also use numerous IPs for the various ad services and networks and most shared hosting companies block those IPs.
Does Any Shared Hosting Work with Ezoic?
Ezoic is working with a handful of hosting companies, you can take a look at their official compatible technology and hosts here. At the moment, the following hosts work well with Ezoic and you probably won’t run into the origin error if you use them.
- Kinsta
- Siteground
- Hostinger
- A2Hosting
Update: When I wrote this article, Hostinger was not approved as compatible, but that seems to have changed. I haven’t been able to test it, but I’m still receiving messages about people running into the Origin error when using Hostinger.
Even if a host is not on the list, you can get it to work if it offers a way to bulk white list IP addresses. Ezoic has a text file with thousands of IPs (scroll to the bottom) that should be whitelisted for the service to work as intended. Some hosts allow you to bulk whitelist IPS while others only let you manually white list them.
If all of Ezoic’s IPS are whitelisted on your host, you shouldn’t run into origin errors.
What if Your Host Can’t Bulk Whitelist IPs?
You have three options:
- Migrate Your Website to Ezoic’s Free WordPress Hosting Service
- Get a VPS and Bulk Whitelist Ezoic’s IPS
- Move to Shared Hosting that Supports Bulk Whitelisting IPS
If you continue to use shared hosting that doesn’t allow bulk whitelisting IPS, you will probably keep running into the same error over and over. I eventually got sick and tired of trying to find a solution and migrated my website to Ezoic’s free hosting service, and it’s been working perfectly for now.
The Easiest Solution:
The easiest way to get rid of the Ezoic origin error on your website is to move your WordPress website to Ezoic’s free hosting service.
It’s free and hosted with Amazon’s cloud hosting service, so the speed is good. You can always move your website to a different host later on. I’m currently using this option.
How My Website is Integrated with Ezoic:
Ezoic has a few ways to let website owners integrate their websites into the platform. I originally used the Cloudflare option but the origin error was common there too.
Hoping the problem would go away, I switched to the nameserver option, which didn’t work, either. Now I’m trying their free WordPress hosting service, which seems to be working better.
Previous Settings:
- Hosting company: Hostinger Shared Hosting (Plans start from $2.19 a month!)
- Ezoic via Nameservers
- Ezoic SSL set to Flexible
- Ezoic automatic SSL redirect off
- Hostinger cache disabled
- Lightspeed Cache plugin removed
- No WordPress cache plugins
- Cloudflare enabled via Ezoic
- Ezoic CDN cache disabled
Current Settings:
- Hosted on Ezoic’s WordPress Hosting Service
- All Speed Related Plugins & Features Disabled
- Only Ezoic CDN & Cache Enabled
- LEAP coming soon
With the settings above, I haven’t seen the origin error for a couple of months. I will explain how these settings work below.
Well, if you don’t want to move hosts, and you’re still on a shared hosting plan, here are some things that you can try to fix the error.
Fix Ezoic Origin Error Solutions:
These steps assume you’re using Hostinger and you already integrated with Ezoic.
1 – Change to Flexible SSL and Disable “Force HTTPS” on Ezoic’s Side
In most cases, the problem happens because there’s a mismatch between your host’s and Ezoic’s SSL certificates or DNS records. If you didn’t play around with any settings prior to this, then this should be your default configuration with Ezoic. The good news is a simple switch should eliminate the Ezoic origin error.
What to do:
- Change SSL type on Ezoic to Flexible
- Disable Force HTTPS on Ezoic
The easiest way to fix the Ezoic origin error is to change Ezoic’s SSL settings to Flexible and disable automatic HTTPS Redirect because HTTPS redirect will be forced by default on your domain name. Most people will leave the SSL on Ezoic’s side on default settings which enables Force HTTPS.
You don’t want that enabled on Ezoic’s side. For the SSL Type change it to “Flexible” or leave it on Full if you don’t notice the origin error anymore. Changing the SSL type on Ezoic’s side is easy and won’t ruin your website.
Your SSL settings should look like this:
For most people, that solves the Ezoic origin error issue. If you’re still running into the origin error even after changing the SSL settings on Ezoic’s side, there are still some things you can try.
Note: On some hosts, changing to Flexible SSL will trigger an anti-bot Captcha form (usually Bit Ninja). It’s pretty annoying and tends to happen on the admin side of your website.
More on that later.
2 – Move to Free Ezoic WordPress Hosting
Consider moving to their hosting service. Ezoic offers free WordPress hosting that has some great benefits like unlimited cloud-based memory, CDNS, CPU cores, SSD storage, and others. In fact, the hosting is better than most budgets shared hosting plans, and it’s free too. A free solution to fix the origin error? Sign me up!
Moving a site to Ezoic’s hosting is easy and it pretty much guarantees that you won’t run into any origin errors because everything is going through Ezoic, instead of third-party hosting companies that may or may not be compatible.
To top it off, Ezoic provides tech support for any issues. If you keep running into the origin error, I recommend moving your website to Ezoic’s hosting service. But I understand could be many reasons why not to, not to worry, there are still some fixes you can try.
3 – Remove Cloudflare, Integrate Through Ezoic
If you followed the above steps, but you still run into the Ezoic origin error, here’s something to consider.
I suggest removing Cloudflare from any way it’s implemented. For example, you could have enabled it on your host or through the official Cloudflare website. Remove your site from it, don’t worry we’ll get back to it.
Bear in mind, some shared hosting companies will add Cloudflare to your site for free, or for a small fee, but you don’t actually want that. At least not if you’re trying to use Ezoic. The best way is to add Cloudflare from inside Ezoic.
Once your website is removed from Cloudflare, log in to the Ezoic dashboard and integrate Cloudflare through their platform.
If you never did that before, you’ll notice a green button that says “Enable Cloudflare” all you have to do is click it and everything else is automatic. If it’s grey, you probably already did that, so this section is irrelevant.
In my case, the button was green, so I clicked it, but it returned an error saying my website already uses Cloudflare. So I went to the official Cloudflare website, and my website was listed.
For some strange reason, it was only registering a few visits a day (when I clearly have many more than that) so something was weird. I promptly deleted the site from Cloudflare and then hit the Cloudflare button from inside Ezoic’s dashboard and it re-connected.
Since then, I haven’t ran into either the origin error or the BitNinja Captcha (more on that later).
4 – Disable Force HTTPS on Host, Force on Ezoic
Be careful. If you choose this method, and it does not work, you’ll have to re-install the SSL on your domain and re-integrate with Ezoic which means ad-downtime. It took me about 4 days to start earning from Ezoic again. If you can afford to lose that possible ad revenue, proceed. It’s generally not recommended.
Here’s a quick overview of Method 2:
- Disable Force HTTPS on Hostinger
- Head over to Ezoic and Turn Automatic HTTPS Redirect ON
- Switch SSL Type to Flexible
Log in to your Hostinger dashboard and click “Manage” on your hosting account. Scroll down to the “Advanced” section and click on “SSL”.
From there, you’ll see the SSL certificate is installed and you’ll have some options. I turned off “Force HTTPS” and then went to check the Ezoic side of things.
Log in to your Ezoic account, click on Settings, scroll down until you find SSL, and click edit SSL settings. From here, switch the SSL type to Flexible and make sure automatic HTTPS redirect is turn on.
Like this:
These settings will probably take up to 24 hours to change, so you still might get the error within that time window.
Re-Installing Hostinger’s SSL:
Bear in mind, if you already connected to Ezoic, Hostinger won’t let you re-install the SSL on the host side because it thinks your domain is pointed elsewhere (Ezoic’s nameservers). That’s actually not what’s happening (Ezoic is a proxy) but it’s what Hostinger thinks.
To re-install the SSL, you’ll need to change the nameservers back to Hostinger’s, install the SSL, and then change the nameservers back to Ezoic’s nameservers. The process can take one to two days, at least for Ezoic to reintegrate, and another 48 hours or more for the ad revenue to go back to normal. I emailed Ezoic support about this, and they had this to say:
We don’t recommend temporarily changing name servers away from Ezoic, because this can have knock-on effects related to ad permissions via that ads.txt file, which can take 24 hours (propagation and reintegration) plus another 48 hours (ad permissions being recognised via reinstated ads.txt file) to come into effect. So in theory we can see 72 hours of revenue impact after that.
– Ezoic’s Support Team
5 – White-List Ezoic’s IPS
For example, the main solution is to add a text file of Ezoic’s IP Addresses to your host to whitelist. Some hosting companies let you bulk white list IP addresses and that seems to solve the origin error for most people. However, Hostinger, my host, does not allow bulk IP whitelists.
My host lets you manually add IPs, which I started to do, but quickly gave up because there are probably close to a thousand to white-list. No thanks!
I wasn’t able to do this, but maybe your host can.
6 – Install WordFence WordPress Plugin
I’m not sure if this helped, but it has an option that can fix the issue. Besides, it’s a good free security WordPress plugin for your website. It helps block blunt-force password hack attempts and other common website attacks.
To install WordFence, log-in to your website’s WordPress dashboard, head to plugins, search for WordFence Security, install and activate it.
Once activate, open the plugin’s options menu (you’ll have to run through a quick first-time setup) and click on All Options. Scroll down and look for “How does Wordfence get IPs” and select “Use the X-Forwarded-For HTTP header.”.
Remember, that’s the same code that Ezoic recommends adding to your WordPress website. It seems like the WordFence plugin is an easy way to add it. Clearing the website cache and cookies can help too.
BitNinja Captcha:
If everything works properly, the Ezoic origin error will stop interrupting your work. But after you make the change, you might notice this warning when you visit your website:
It only tends to happen when your SSL is set to flexible. The notice will show your IP and ask you to delist it. I noticed that BitNinja is actually not compatible with Ezoic.
It’s listed on Ezoic’s Compatible Technology and labeled: “Any sites on hosting providers using Bitninja have to have it disabled for their site, otherwise will show security captcha.”
In my case, as usual, I kept running into this BitNinja Captcha. The weird part was I ran into it when I was already logged into my site and just navigating menus. After digging around online for hours, I found a solution that might work for you.
BitNinja Captcha Fix: Disable Ezoic CDN Cache
Disable all CDN cache on Ezoic’s side. To do that, open Ezoic, navigate to Speed, scroll down until you see “Cache” and then click “Go to Cache App”. At the top of the page there will be a toggle for Caching and turn that off.
It looks like this:
Flipping that switch removed the BitNinja Captcha. While the cache is supposed to speed up your website, it also seems to trigger the BitNinja captcha, so I turned it off entirely. Besides, if you’re on WordPress, you can use a cache plugin to serve cache anyway.
Another option is to re-enable Cloudflare through Ezoic. I have Ezoic’s CDN cache off and Cloudflare enabled, it seems to be working for now.
Other Possible Fixes for Ezoic’s Origin Error:
1 – Reset Everything & Reconnect to Ezoic
Prepare for 72 hours more of ad-downtime. I ended up doing this because my settings were a bit ruined. So I set everything back to Hostinger’s nameservers, hit reset DNS Records on my domain name, re-installed the SSL, changed nameservers back to Ezoic, pulled the Ezoic SSL from my domain name, changed Ezoic’s SSL to flexible, and disabled Ezoic’s HTTPS redirect. Phew!
The good news is it all reconnected pretty fast. I’ve been using my website with that configuration for a while now and I haven’t run into either the Ezoic origin error or the WordPress “The response is not a valid JSON response.” error either.
Hopefully, it stays that way! In other words, I’m currently using Method 1. I was using method 2 for a while and it was working fine but I decided to go back to the default settings.
2 – Double Check DNS Records Match
Some times this error happens when there’s something missing from the DNS records on one end, either your host’s or Ezoic’s. You might have to manually add a record from one end.
Normally Ezoic will pull all the records but some times things can get lost. Hostinger won’t let you edit the DNS records because it thinks Ezoic is managing them but you can still find a copy in the Advanced section of your hosting panel in DNS Zone Editor.
From there you can either manually check if the records match Ezoic, or reset the DNS settings to default. You might need to manually add or remove a DNS record on the Ezoic side.
3 – Uninstall LiteSpeed Cache
While I have been using LiteSpeed cache with Ezoic for some time now, one Ezoic rep recommended disabling it because it’s not compatible. I followed suit, and we will see if it makes a difference.
Incidentally, I notice when inspecting your site that you’re using LiteSpeed cache. LiteSpeed cache isn’t compatible with Ezoic, so please do switch it off as this might very well be the cause of this issue (and in any case wouldn’t likely be helping your revenue).
– Ezoic Support Team
Incidentally, Hostinger uses LiteSpeed cache on their server’s side. I don’t know if switching off the cache on Hostinger will disable LiteSpeed, but it’s worth a shot. I tried disabling all my cache plugins and even the hosting side cache. The result? Not much.
My website actually seemed to load faster, and my Page Speed Scores were a bit better. I believe the reason is either the host’s cache or the plugin’s cache was having issues with Ezoic’s cache. The idea is to disable all cache services besides Ezoic’s because they have Cloudflare already.
4 – Wait it out.
In some cases, the problem is caused by some misconfigured cache settings. If you leave the website alone, the cache will refresh, and it should work again.
I was having a particularly bad day where every link on my website lead to an origin error, so I waited for a few hours, and the problem went away on its own. You can also try manually refreshing your website’s cache.
Conclusion:
So that’s how you fix the Ezoic origin error. I know how annoying the error can be, especially when it gets in the way of your website’s earnings and blocks you from working on the site.
It’s a dilemma because you want to earn more, but you also don’t want to be locked out of your own website. Most people will recommend disabling Ezoic, and while that will eliminate the errors, it also will take your potential Ezoic earnings away too.
It is possible to remove the errors on a budget shared hosting plan like Hostinger, but it’s not guaranteed. Eventually, I got so tired of dealing with the error and decided to try out Ezoic’s free hosting service, which seems to be working pretty well for now. Luckily my website is not very large so it’s easy to move around.
Please let me know if it works for you, I’m pretty happy that it works for me. There’s a chance it might not work for you, but it can point you in the right direction. Most of the time, the error is caused by either an issue with the SSL or DNS records.
Thanks!
Anaso Emmanuel says
Hello Timothy,
I’m glad you shared your insights. However, does the WordPress editor error have anything to do with the origin error or just plugins?
And yes, I’ve been frustrated about this error 520 that it freaks me out anytime I worry about it. I’ve tried lots of possible solutions but to no avail. I’d try the SSL option. Thanks for the guide!
Timothy says
Hey, I’m not 100% sure if the two errors are related, but I think so. I haven’t got the WordPress or Origin error after switching the SSL settings. You could also try white-listing your Ip, clearing cookies & cache for your website, and flushing your computer’s DNS (CMD – ipconfig /flushdns).
Marvin says
I have some origin failures since I use ezoic hosting and my ad revenue dropped… They told me its due to a plugin, but I checked them all and that wasn’t the culprit.
Even some ads dont show up with images anymore… and whats most fruststrating is that my place holders all al over the place now (after the hosting change I set up everything properly with an ezoic manager but after some while most of the ads are not at their places where they should be…)
Do you have an idea Timothy?
Timothy says
That’s weird, all of my errors stopped after moving to their hosting service. Have you tried changing the SSL settings on Ezoic to flexible? You might also try disabling the cache on your host’s CPANEL side. If you are using Ezoic’s nameservers, they cache pretty much everything so you don’t really need any other cache or tools.
Mr. KingsHOK says
I turned off the SSL settings as you instructed, but it seems the error keep coming up once in a while though. Wht do you think I should do now?
Timothy says
You could try disabling WordPress cache plugins. I ended up moving to Ezoic’s free hosting service because the issue kept coming back.
Tina de Peralta says
Hi Timothy. Just wondering if you’ve noticed if your origin error was due to your ISP. I am also having the same problem right now. I asked some friends using a different network if they could access my website and they said they do. Me and my sister who are using the same network couldn’t. When I tried using a diffferent network, it worked fine. Problem is I need to fix this because the network is the biggest network here.
Timothy says
Hey, yes I think it could be. Have you tried from your phone’s cellular? It’s pretty random. In my case, it would happen on both my home network and 4G. The annoying thing is by the time you can get your host to check it out, it’s already gone, and they can’t replicate it. Here are some other things you can try: reset your computer’s network adapter, flush the DNS in CMD (ipconfig /flushdns), delete the local cookies of your website on Chrome, or try a different browser. You could also try whitelisting your computer’s IP on your host. It’s a really annoying problem and I wasn’t able to solve it on my shared hosting account, so I moved my main website that runs Ezoic ads to Ezoic’s hosting service, and it’s been great so far. You could also go with a VPS from a different hosting provider, but those can be tricky to setup, as well as expensive. I hope that helps!
Tony says
I have been on ezoic for a month now and it has been a nightmare. My earnings are at an all-time low worse than adsense. I first integrated my site with their plugin and started getting 503 errors, then l added nameservers integration and now getting ezoic communicating with origin error. The problems keep on coming and setup endless. Now you recommend moving my WordPress to their free host
Timothy says
Sorry to hear that. The only issue I had with Ezoic is the origin error, which was solved by moving hosts. If your host allows it, you could probably solve it through bulk white-listing Ezoic’s IPs. The earnings on Ezoic should almost always be higher than AdSense because Ezoic uses lots of different ad networks, AdSense is only one. Have you contacted Ezoic’s support about your issues? It could also be a theme/hosting/conflicting plugin/country traffic/niche problem.
Pieter says
Hey. I have just moved my website to ezoic hosting but I can still see it hosted on my previous host (hostinger). Is that normal?
Timothy says
Hey, I think that’s normal. It’s most likely just taking a while to register the DNS changes, sometimes it takes up to 72 hours. You might also be seeing a cache version from your old host. As long as the nameservers on your domain are pointed to Ezoic, Ezoic should pull the site files from their servers. I still have my old website files on Hostinger too. You could test your site with this https://sitechecker.pro/hosting-checker/, it should say Amazon.com Inc because Ezoic uses Amazon’s hosting service.
Jan says
Timothy, thank you for this great article. I was able to resolve the issue that I had with 3 of my sites. I changed the Ezoic SSL to Flexible and updated that header setting in Wordfence. All working fine now.
Timothy says
Awesome, that’s great to hear. It seems like Ezoic has been working with Hostinger, so hopefully Hostinger shared hosting won’t run into that issue.
Steve says
Thanks you so much for publishing this!
I have a Forum on Hostinger and go through Ezoic.
User in Germany reported ‘origin’ error and so I set Ezoic SSL to Flexible
This fixed his problem (which I could not reproduce).
Timothy says
Great to hear! Hopefully, Hostinger will work better with Ezoic because they’re supposed to be partnered now.
Chathu says
Thank you for your guide. I have recently integrated Ezoic with Cloudflare. May I know you have enabled “CloudFlare proxy” from the Ezoic DNS settings? Because when I enabled it my site got Cloudflare 522 timeout error.
Timothy says
You’re welcome! If you enable Cloudflare, it should automatically add the Cloudflare proxy records to the DNS settings. I’m using Cloudflare with no issues. Maybe you need to refresh the cache and wait a bit?
Rahim says
Thanks a lot!
This fixed my issue.
Timothy says
That’s great to hear! Which solution worked for you?
Edwin says
Thank you for these guides.
I fixed mine by transferring my hosting to EZOIC. I tried almost all other methods, and transferring is the only method that works.
Best regards,
Edwin
Timothy says
Yeah, that worked for me too, thanks! I guess if you plan to move your site, you’ll need to go with a VPS that can white list all of Ezoic’s IP addresses.
paul says
hi i encountered this issue, i have tried almost all the steps you posted here on your blog but none worked for me i had to contact my host and i was given an ip to upload in the A record which i did. my blog came back to life but i faced another issue which was too much redirection i had to change my ssl on ezoic to full and bang it did the magic my website loads faster than before even without using the leap feature
Timothy says
That’s interesting! Yeah, sometimes the DNS records don’t match and you have to manually change things. I’m happy that you got it working! It’s really frustrating!
CLASSBASIC.COM says
Thanks for this article. Most of the methods I have tried except for moving to Ezoic WordPress hosting. I’m on VPS, yet none of them work. There is only one solution that worked for me is to remove cloudflare integration and integrate with Ezoic plugin.
Timothy says
Good to know. Are you able to bulk white-list IPs on your VPS? That should do the trick.
Stephen says
How is Ezoic’s Free WordPress hosting? I am wary of moving my money site to Free WordPress hosting. I don’t know how good Ezoic’s hosting is.
Moreover, I understand there is no Cpanel for their Free WordPress hosting, how did you cope with that?
Timothy says
It’s okay, it’s Amazon’s Lightsail service. That’s right you don’t get a Cpanel, it’s only hosting with FTP access, but you need FTP software to access it. You don’t get any hosting support too, so you’ll need to manually backup your website from time to time. I’ve been using it for a while with no issues. However, if you need other services like email, backups, and the ability to edit all the hosting configurations, it’s probably not a good fit.
Michael says
Hi Timothy,
Origin error is very frustrating. I hate it when when website is one second down. I changed my integration immediately I experience the error to plugin integration.
Something court my attention on disable my cloudflare from website and reintegrate through ezoic. I need more clarification…. If I’m correct, you do mean… I should disable Cloudflare by changing my nameservers to the host nameservers and head to Ezoic to connect to cloudflare.
This is a fantastic article, thank you.
Hope to hear from you soon.
Sincerely,
Michael
Timothy says
Thanks for the comment. I can’t say exactly what will work because there are a lot of factors to consider. I would do everything from inside Ezoic, use their nameserver integration option and then enable Cloudflare from inside their dashboard. You can try logging directly into the Cloudflare website to see if you linked your website before. If it’s there, I would remove it, and add it again through Ezoic. I solved my origin errors by switching to Ezoic’s WordPress hosting which has been working fine for now.
Cindy says
Thank you so much! Changing the SSL settings worked for me. I appreciate it!
Timothy says
Happy to help!
Beer Basket says
If you are getting below error..
“Error communicating with origin”
Simply remove ezoic’s cname records from DNS.. then check your website. It will work fine.
Thanks
Yatender says
I am sorry for writing such a long comment, but I am extremely frustrated and need assistance.
Prior to integrating my website with Ezoic, everything was functioning well. Google ads were appearing on my website without any errors in the Search Console. My new articles were being indexed and traffic increased steadily day-by-day.
However, after integrating with Ezoic, the google ads are no longer appearing on my website. Furthermore, there are errors in the Search Console which are as follows:
1. Google cannot fetch my sitemap due to 403 forbidden error
2. New articles are not being indexed and, when I test the live URLs in the Search Console, it cannot fetch the page; instead, it shows the error: Page fetch: Failed: Blocked due to access forbidden (403)
3. In addition, my articles which were ranked before are no longer appearing in search results. Consequently, I am slowly losing all the traffic and hard work of the past 2 years.
Although I am still able to access my website, it has become very slow.
I have tried the following methods to resolve the issues stated above:
1. I whitelisted all the IP’s for ezoic on my host (bluehost).
2. I completed the Wordfence header step.
3. I changed the ezoic SSL certificate to flexible.
4. I removed my website from Cloudflare.
5. I replaced my Cloudflare DNS with the DNS recommended by Ezoic.
Unfortunately nothing worked out.
In addition, I have been approved by Ezoic, but Google Ad Manager is not approving my domain status and rejecting my with same error that my website is down or unavailable. As a result, ezoic ads are not being showed on my website
I have reached out to Google Support and they say the problem lies with ezoic, but ezoic is not responding to my emails.
If you could provide any guidance as to how to solve these issues, it would be greatly appreciated. I understand this is a long comment, but any help would be lifesaving.
Timothy says
Hey Yatender, sorry this isn’t official Ezoic support, I’m just another Ezoic user who found a way to fix the origin error on my website. I understand, those issues are really frustrating! Unfortunately, I don’t really know how to help. Maybe you can resubmit the site map? Maybe there’s a no-index tag somewhere on those pages? Sometimes SEO plugins can malfunction and flag everything on your site as no-index. You could try the Ezoic Publisher Facebook group for help too. In my case, I moved my site to their WordPress hosting service and it fixed most of my issues, although the back-end is still slow from time to time. You could try deleting all the local cache from your site too. Sorry I don’t really know how to help here!
Yatender says
No problem. Thanks for your precious time. I will try to resubmit the sitemap and see what happens.