May domain Vacbid.Com
Due to server errors, Google bots cannot index my site. I use React and Pre-rendering. I moved to netlify on 12/04/2024. I was in Vercel before. While on Vercel, there are no errors, but after moving to Netlify, Google does not index my site due to server errors. I want it to be resolved very urgently.
I request you to give some priority to this issue because your server rejected 470 thousand scanning requests. I’m falling way behind on Google. This is causing huge losses to me and my business. I don’t want to miss these browsing requests. I would be glad if you are interested.
This is happening due to prerendering. It’s a beta service and can sometimes cause these issues. On Pro and above plans you can contact us to switch to Prerender.io: prerender.io if you prefer. Or you can use a server-side framework like Next.js which would generate a static output of your site, so you don’t have to rely on prerendering.
Hello, I understand from your comment that Netlify provides Prerender service, and since this service is in beta, it cannot meet 1 out of every 2 requests and the server returns a 500 error code. It works with 50% failure. Is this issue unresolved for you? I want to help you solve it. When I researched your forums, your prerender service appears to be in beta version since 2021. When do you plan to solve this question? I will change the frame accordingly. Moreover, with this statement, no one wants to move their site to Netlify with your pre-rendering service, which is 50% not working. It is obvious that it is a complete deception. I think you need to solve this problem before you lose a large amount of customers. I think this problem is caused by the repetition of DNS registration with prerender. To solve this, can you please explain the reason for the error!
Hi, @HakanSungur. The prerendering service isn’t working with your site sometimes. This is almost certainly due to something relating to your client-side javascript and you will need to debug that javascript, not us.
There is a support guide with instructions about how to do so here:
About this:
Moreover, with this statement, no one wants to move their site to Netlify with your pre-rendering service, which is 50% not working.
Even for your site, the error rate is far below 50% and it certainly not 50% for all prerendering requests. These statements are simply false and I would appreciate if you stop making false statements here. It doesn’t help anything to cloud the conversation with false information.
About this:
I think this problem is caused by the repetition of DNS registration with prerender.
Netlify has nothing to do with the registration of this domain. It is using Netlify DNS but it was registered with https://www.isimtescil.net/. This statement above just doesn’t make sense.
You will need to debug your client-side javascript to fix the prerendering issue. If you do not wish do do that, your choices are to disable prerendering or to upgrade to Pro and use a third-party prerendering service.
When I said that 50% of the requests do not respond, I wrote it based on the Google data I mentioned in my first post. According to Google data, it cannot respond to 50% of requests. I will debug it and write it here.
Hello again,
Following your advice, I enabled debugging with Sentry and watched for a long time, but I did not receive any errors. Server Error in Google Search Console persists. When I researched the problem, I read forums that said it was due to the server’s slow response time.
So I switched to the pro plan hoping it would speed things up, but I’m still experiencing the current problem.
Google dropped my site’s ranking very low. I am suffering great damage.
I request your help.
Kind regards.
I also see that Google does not give this error when the server response time is 49 ms. However, as of April 13, 2024, I switched from Vercel to Netlify and the server response time increased from 49ms to 10500ms. I think this may have an impact as well. I switched to the pro plan to reduce server response time, but it had no effect.
That’s to be expected, as there is no speed difference between the Starter Plan and the Pro Plan.
Note: I believe Netlify unceremoniously dropped the “Business Plan” at some point last year, but the information is otherwise likely still correct.
So what should be done to solve the above problem?
@HakanSungur I can’t really say, I don’t work for Netlify and it’s not an issue I’ve ever had.
I was just trying to correct a misunderstanding that I could see you had, didn’t want you potentially paying for Pro only to find there’s no “speed” difference.
If I were in your shoes and didn’t like what Netlify was offering, I’d just investigate other options.
Since you are on the Pro plan now, you could get Netlify to switch your site to use prerender.io as @hrishikesh mentioned above, if the issue is the pre-rendering then that may resolve it.
See, the subject is branching out and getting very scattered. I don’t want a 3rd party sir SSR. I wrote this in my first post. Netlify claims to make its users use SSR and that’s what I use. I’m trying to fix this low server response time. Then Netlify will not say that we offer SSR solution. Users will say that we offer SSR and it really works, but it works very slowly. I’m looking for a solution to this here. I’m using SSR with React and google is not crawling my site. I think this is due to low server response time, I’m still looking for a solution. My problem is not solved!
I disagree, I’ve not changed the topic at all.
You didn’t write anything about not wanting “3rd party anything” in your first post?
Or second post… your 3rd post mostly just raised that Netlify’s Pre-render service isn’t a good fit for you.
They do, and it doesn’t seem to work well enough for your use case, so you shouldn’t use it.
If you don’t want to use something else, that’s also your choice.
I don’t understand what you mean.
As mentioned above, if what Netlify provide isn’t good enough for your site, you may want to look elsewhere.
I understand that doesn’t “solve your problem”, but there may not be a solution provided by Netlify.
You have to do what’s best for your site and yourself.
The information given to you by Netlify’s staff so far has been to:
So you’ve exhausted the existing options, maybe they’ll provide new ones, maybe something will get adjusted in future that changes behavior, but if you avoid vendor lock-in you can bounce between providers to whoever serves you best.
To get the point across, I’m using Netlify SSR and I won’t give up on it. I am using Pro plan. And as I shared above, due to the high server response time, Google both reduces my ranking and does not index my website. I haven’t found a solution yet.
@HakanSungur That’s fine, and you can absolutely do that.
However obviously if hosting with Netlify and/or using whatever SSR (or pre-rendering) you’re using is what is causing those negative impacts for you (reduced ranking, not being indexed), then you will continue to experience those issues until such time as something changes.
So if your aim is to try and force Netlify to provide you a solution, best of luck!
I don’t write about a problem specific to me. I think that thousands of customers who use Netlify and apply for the SSR solution will have problems with Google with this response time, so there is or will be a solution. Naturally, I am looking for a solution to this issue.
So to recap…
There are known issues with the Netlify pre-rendering system and Netlify are aware of it:
The solutions proposed to you were:
To confirm:
The Netlify team will be able to let you know if any changes to their pre-render service are likely.
But as you said yourself:
I’d be wary that it doesn’t seem to be high priority piece of the system for them.
I understand you, very well. But netlify needs to give these answers itself. In this way, I will decide whether to leave Netlify or try to contribute to the solution of this problem. You are convinced that netlify cannot solve the problem and you want me to find another solution. I really thank you from the bottom of my heart for this contribution. But why doesn’t netlify solve this problem? I’m researching it and I want to contribute to the solution.
I’m not convinced of that exactly.
Only that they may not solve it quickly (or could abandon it in preference of something else).
Not really, I’d prefer you had not hit any issue at all!
It’s just something that you can control yourself and doesn’t rely on waiting for others.
Netlify will respond again, they’re just not super active during these hours.
When did pre-rendering become SSR? Those are 2 different features from what I know. @HakanSungur, you seem to be confusing yourself (and others) with your mixed usage of these features.
To recap here:
You’re not using SSR. You’re using prerendering. The latter is not working and we don’t expect it to change any time soon. It’s a beta service and doesn’t match our production standards. With so many modern frameworks providing SSR and preredering out of the box, changing our feature is currently not a priority.
Solutions:
