Redirect error on Google Search console for non-https bare URL

Actually, this is an incorrect DNS configuration and as a member of the Netlify support team I ask that people please not do this.

The NETLIFY type DNS records are the correct way to link custom domains to sites at Netlify when using Netlify DNS. So, I do ask that anyone reading this topic not follow that suggestion. It is definitely not a recommended configuration in any way.

Also, after doing testing with https://www.redirect-checker.org/index.php I believe it provides highly inaccurate information and I will not accept any data from that tool as valid until I can see it is working correctly. I just tested an example tonight where the tool reports a redirect loop when in fact it is actually requesting the exact same URL over and over (the HTTP only URL) and getting the exact same redirect again and again (the redirect from HTTP to HTTPS). That isn’t a loop. The tool also incorrectly reports it is requesting HTTPS when in fact it does not. To summarize, I cannot trust the data returned by https://www.redirect-checker.org/index.php as I know it is providing false data. (Note, I don’t think that is intentional but I do think it has a bug of some kind.)

EDIT: Further testing indicates that https://www.redirect-checker.org/index.php is giving accurate and correct information and it was our logging, not theirs, which was giving inaccurate information.

Also, we cannot see what Google’s tools are doing. We need some way to see this without using third-party tools.

Can anyone reproduce this outside of these two tools? If so, no one has share that information. I’m going to summarize my post in a parallel topic by saying:

  • We cannot troubleshoot Google. We can only troubleshoot Netlify. To troubleshoot Netlify, we need to identify the incorrect redirects.

We need information to identify the incorrect response. There is a longer reply with what details are required to troubleshoot here:

If you would provide any of the three possible sets of details to troubleshoot, we will be happy to take another look at this. If there are any questions about to get that information, please let us know.