If the Ryte Dashboard shows that your homepage URL is not indexable you need to check two things: first, confirm which URL is listed as the homepage URL of your project via the single page analysis or the project settings, and then check to make sure that the URL truly is indexable. If the homepage URL of the project is not indexable due to being redirected or a non-canonical URL, you need to enter the correct homepage URL in the project settings.
Confirm homepage URL
The first thing to check when the Dashboard shows that the homepage is not indexable is the precise URL that is listed in the project as the homepage. The easiest way of doing that is by using the single page analysis. Go to Website Success > Single Page Analysis and check the URL in the text box (but don’t start an analysis of the URL yet). This is the exact URL that is listed as the homepage in the project.
If you can already see that the URL is wrong due to a typo, missing trailing slash, wrong subdomain, or anything else of the sort, you can skip right ahead to Correct homepage URL in the project settings. If you don’t see anything out of the ordinary yet, just continue below.
Notice that in the example above the URL is missing the trailing slash. The root directory always has a trailing slash at the end due to technical reasons. The canonical tag on our URL points to https://es.ryte.com/ accordingly. So, in this case, we already identified a possible error just by looking at the URL.
Now that we know the homepage URL of the project it’s time to check what the issue is. There are various reasons why a URL might not be indexable and our indexability report lists them all. One way to check the indexability is to copy the exact homepage URL from the single page analysis and using it to filter for this exact URL in the indexability report. Check the column “indexability” to see why the URL isn’t indexable.
Seeing as we’re already in the single page analysis, we can also use that to identify the issue. Just click the “Single Page Analysis” button. It tells you straight away in the results if the page is indexable. The primary errors section lets you know what your next step should be.
Depending on the reason why the URL is not indexable the steps you need to take to correct this issue vary. Here’s a very brief overview of the most common cases:
Blocked in robots.txt: Check your robots.txt file. One or more of the directives prohibit search engine crawlers access to the URL.
Status Code 3xx (Redirect): The URL redirects to a different URL. Check if this redirect is correct. If it is, the target URL of the redirect is the actual homepage URL. See Correct homepage URL in the project settings on how to enter this URL in the project settings. You can check the target of the redirect in the single page analysis or by using the redirect report in Website Success > Indexability > Redirects > Status Codes.
If your domain has gone through several relaunches or been restructured several times redirect chains might have cropped up. To get to the endpoint of a redirect chain easily just copy the URL from the single page analysis into the address bar of your browser and hit enter. Because of the redirects, you will automatically be forwarded to the target URL. Copy this URL from your address bar and enter it in the project settings as new homepage URL as described above.
Set to noindex: If a meta-tag or the HTTP request header shows the attribute “noindex” the page isn’t indexable. Remove the tag or enter the actual indexable homepage URL in the project settings.
Canonical tag points to a different page: If the canonical tag on a page points to a different URL the page you’re checking isn’t indexable. Check if the canonical is set right. If it is you need to change the homepage URL in the project settings so the URL the canonical tag points to.
There is one special case where the single page analysis tells you that the URL is indexable even though the regular crawl analysis says it’s not. This case comes up if the homepage URL is just the root directory, but without the trailing slash as shown in the screenshot in the section Confirm homepage URL. When sending a server a request for the root directory, a client (i. e. your browser or our crawler) always has to include the trailing slash in the request. It’s impossible to send that request without the trailing slash. As such, the single page analysis adds the trailing slash automatically if it’s missing in the URL. You’ll be notified if that happens. If the URL is shown as indexable after the trailing slash was added you already know that the missing trailing slash is the reason for the warning in the Dashboard. All you need to do is correct the homepage URL, now!
Correct the homepage URL in the project settings
If the issue was a redirect or canonical tag you might have to correct the homepage URL in the project settings. The single page analysis and indexability report tell you to where the link juice goes (that’s the target of the canonical tag or redirect) so you can go straight to project settings > Advanced analysis > What to analyze > Homepage URL and just enter the URL in the text field.