Google Search Console Crawl Stats: “Server error (5XX)”; Host status: “Server connectivity — High fail rate last week”. Separately, a curl request returned HTTP/2 520 with body “error code: 520”.
Other Information
Our WordPress site is on the free hosting plan. We understand that curl and automated testing tools can be restricted; the main concern here is actual Googlebot crawl failures recorded in Search Console, not only a live-test failure.
Examples displayed in Search Console on 4 November 2026 (times copied as displayed; report timezone not independently verified):
The Geelong page loaded normally in a browser on 5 November. Search Console reports acceptable DNS resolution and acceptable recent robots.txt fetching, but high server-connectivity failure last week. Some affected URLs are older pages being consolidated.
Separately, a curl GET of https://influenscale.com/perth/real-estate-photography-mindarie/ on 5 November at 05:25:32 UTC returned 520, Cloudflare Ray ID a5597036ebf2709e-PER. A browser visit reached the intended real-estate photography service page. We are not assuming the curl error and Googlebot failures have the same cause.
Could staff check whether verified Googlebot requests are encountering origin errors, entry-process/resource limits, or a hosting security restriction? Please advise what diagnostics are available on the free plan and how to distinguish these causes. We have not disabled security or changed DNS. Thank you.
Welcome to the InfinityFree community forum! Good to have you here.
Most people answering here are volunteers. They’re often the fastest source of help. Admin (the only staff member) checks in about once a day for issues on our end.
Volunteers can’t see your account or website. Share what you actually see, like error messages and what happens when you try something. That’s more useful than your theory of what’s wrong.
AI tools often get InfinityFree wrong. If a volunteer’s advice differs from what an AI told you, please try the volunteer’s suggestion first.
Solving an issue is a joint effort. Try the suggestions you get and report back what happened.
Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.
I couldn’t find a knowledge base article or staff answer that says what causes intermittent Googlebot 5xx errors on free hosting, or one that explains how to tell an origin error from a resource limit or a security restriction. Other topics asking whether Googlebot is blocked have no answer I could cite, so I haven’t linked them.
Your account was temporarily suspended on 17 October for “Entry Process” and reactivated the next day. That’s a few weeks before the failures you describe, so it may be unrelated. But it shows the account has hit a resource limit before. I don’t have a source saying that limit produces the 5xx errors you’re seeing, so I’m not claiming it does.
On diagnostics, I only found what the CPU limit article says. On free hosting, CPU usage is tracked for the account as a whole, with no breakdown by time, domain or script. The detailed per-process metrics and server access logging are premium features. The same article suggests comparing your Daily Hits and Entry Process usage to see whether load comes from traffic or from the site’s code:
So here’s a question: do the usage graphs for this account show Entry Process or CPU usage hitting its limit around the times Search Console logged the errors, such as 2:14–2:58 PM on 4 November? If you can, convert those times to UTC first, since you haven’t verified the report’s timezone. If the graphs are flat then, that points away from a resource limit.
On the curl 520, that’s a Cloudflare error code. It means Cloudflare reached the origin server and didn’t get a valid response. Your browser loading the same page afterwards is consistent with a failure that comes and goes.