Or, in other words, how can I tell google this is a user login protected page?
The website is basically a single page app with server side rendering. That said, if the visitor is asking for a web page by text/html, the server will do server side rendering to show the html, and download all the app. After that, the app will has its own routing and navigate to the page inside the app. The app only ask for data if necessary.
Now, google show me a warning
Indexed, though blocked by robots.txt, the url is actually one url of the user's account pages. It's protected, of course.
If google visit the url, it will see 200 http code, then download the html, but it's actually an empty container. Then, since this visitor is not logged in. The app will immediately navigate to the sign-in route.
I guess this warning will bring negative impact to our SEO. I'm wondering what should I do for Google SEO, because our seo is quite bad now.
1.Respond with 403 and all the html/app, and navigate to sign in after the app is mounted?
2.Just like traditional website, respond with 302 to redirect google to sign-in page, and request the server again?
Appreciated for your time to let me know what's the correct way to tell google this is an user login required page. It seems it's so hard to please google.