Pages couldn't be crawled (DNS resolution issues)

rochon.a1.119 · Post by **rochon.a1.119** » Sun Feb 02, 2025 3:45 am

If you have pages blocked from Google, they will not appear in this search engine and, if they do not appear in it, they will obviously not generate positioning or traffic for the domain.

Normally this type of things happen for several reasons:

We have the tag “<meta name="robots" content="noindex"/> in the URL in question.

The robots.txt file is blocking access to a folder or URL.

The DNS (I'll tell you what they are later) are blocking the domain.

The URL has incorrect formats.

To fix this, you just need to find out what is causing it not to be indexed (shown on Google) and fix that blockage.

As I said at the beginning, it doesn't have to be a mistake as such.

Within SEO strategies we must be aware that not everything has to be on Google.

In fact, on many occasions, the agency blocks access to URLs that do not make sense to exist (discontinued products, shopping sessions, information that is too old or that does not generate any type of turkey mobile database qualified traffic or does not add value to the domain...) and what happens next is that Google focuses on what it needs to read and automatically moves up in the results ranking.

This is a very rare bug.

In fact, we've almost never seen it.

What it is telling us is that the DNS or Domain Name Services are not working well or are not working at all.

To make ourselves understood a little, a DNS is, let's say, an intermediate step between the user searching on Google and accessing the information on our server.

What it really means (don't be scared) is reverse name resolution or, in other words, it converts an IP into a domain.

Pages couldn't be crawled (incorrect URL formats)
This error tells us that there are incorrect characters in the URLs and, for this reason, Google cannot index that URL.

Google wants us to always use alphanumeric characters without Latin characters such as “ñ”, accents, blank spaces, underscores such as “_” and, while we are at it, I advise you to always use lowercase characters.