"Discovered: currently not indexed" problem on Google Search Console caused by Cloud Run

[eWaparts]

Hello everybody,

My problem is that my webpage is not being indexed on Google because I have a low configuration on the sservice on Google Cloud Run. This is my configuration:

I would like to know what values I have to put so that at least we are indexed.

Thank you in advance

[christianpaula]

Hi @eWaparts,

Welcome to Google Cloud Community!

In order to ensure that your webpage is indexed by Google, you may need to make sure that the following is configured correctly:

• Your webpage is accessible and returns a 200 status code when accessed via a web browser.
• Your webpage includes a sitemap that lists all the URLs on your site that you want Google to crawl.
• Your webpage includes a robots.txt file that does not block Googlebot from crawling your site.
• Your webpage is linked to from other sites on the internet.

Additionally, you can check the setting of the Cloud run service and make sure that the request timeout is set to a reasonable value and the number of instances is adequate for your traffic.

It's also important to note that it may take some time for your site to be indexed, even if everything is configured correctly. If you are still having trouble getting your site indexed after checking these things, you can submit your site to Google for indexing by using the URL Inspection tool in Google Search Console.

Here are some resources that may be helpful when configuring your site to be indexed by Google:

• The Google Search Console Help Center has a section on how to submit your sitemap and check for crawl errors: https://support.google.com/webmasters/answer/183668?hl=en
• Google's documentation on the robots.txt file and how to use it: https://developers.google.com/search/docs/advanced/robots/robots-txt
• Google's documentation on the URL Inspection tool, which can be used to submit a URL for indexing: https://developers.google.com/search/docs/advanced/url-inspection/inspect-url
• Google Cloud Run documentation for best practices in terms of configuration: https://cloud.google.com/run/docs/best-practices

Keep in mind that it may take some time for your site to be indexed, even if everything is configured correctly. Be sure to monitor your site's performance using the Search Console.

Thank you

[eWaparts]

---

In order to ensure that your webpage is indexed by Google, you may need to make sure that the following is configured correctly:

• Your webpage is accessible and returns a 200 status code when accessed via a web browser.
• Your webpage includes a sitemap that lists all the URLs on your site that you want Google to crawl.
• Your webpage includes a robots.txt file that does not block Googlebot from crawling your site.
• Your webpage is linked to from other sites on the internet.

---

We already solved all of that and we still dont get indexed thats why I was asking about the Cloud Run Configuration. If its not a problem of the Cloud Run Configuration we dont know what else we can do.

Additionally, you can check the setting of the Cloud run service and make sure that the request timeout is set to a reasonable value and the number of instances is adequate for your traffic.

---

How much is a reasonable value for the request timeout? Which number of instances is adequate? That is the real problem. We dont know the answers to those questions.

Here are some resources that may be helpful when configuring your site to be indexed by Google:

• The Google Search Console Help Center has a section on how to submit your sitemap and check for crawl errors: https://support.google.com/webmasters/answer/183668?hl=en
• Google's documentation on the robots.txt file and how to use it: https://developers.google.com/search/docs/advanced/robots/robots-txt
• Google's documentation on the URL Inspection tool, which can be used to submit a URL for indexing: https://developers.google.com/search/docs/advanced/url-inspection/inspect-url
• Google Cloud Run documentation for best practices in terms of configuration: https://cloud.google.com/run/docs/best-practices

---

Thank you for the resources but only the first link works. I get 404 error on the other three links.

Keep in mind that it may take some time for your site to be indexed, even if everything is configured correctly. Be sure to monitor your site's performance using the Search Console.

---

Four months have passed and they still haven't indexed us. We can not wait any longer. We need to find a solution as soon as possible.

Thank you.

[kolban]

What does "I have a low configuration on the service on Google Cloud Run" mean?  I'm zero of an expert on this area (sorry).  What I sense is that your web presence is partly served by HTML returned from invoking a Cloud Run instance.  Does this mean that if a browser user visits your URL, the HTML is served up by a response from Cloud Run?  Is it all or is it just "some" data?   I have a wild guess that if your Cloud Run instances are not present (i.e. no requests being made on them) then if a Google web crawler visited your site, you would have a cold start of your service which could be tens of seconds depending on what you are doing.  This might be too long for the Web Crawler which would then just say to itself "no response" and move on.  It "might be" that you need to have at least one instance always running to avoid a cold start. Of course, that would have cost implications if you are otherwise idle.

[eWaparts]

Thank you for your answer,

I will change that configuration. I hope it helps with the indexing problem.