I thought I would add a quick update on how Google indexed my Blogger static home page. One of my main concerns was that Google might not like the Blogger page redirect in the search results. Frankly, it was difficult to tell just what kind of redirect Google was using.
First, take a look at the search results. This static home page blog is already indexed by Google and looks to have been successfully indexed:
Note that the URL does not show the final redirected URL of Static Home Page - which is a good thing.
Now, taking a look at the actual page HTTP response you can see that Google does a 302 temporary page redirect for the static home page:
From what I could see on the Google help pages and forums, this looks good for Blogger static home pages. Take a look at this response from a Google representative on 302 redirect behavior.
To quote the representative from Google, "Generally speaking, with a 302 redirect we'd try to take the content of the redirect target (in your case PAGE-B) and index it under the redirecting URL (in your case PAGE-A). If the target has a noindex meta tag, then it's likely that we'd apply that to the redirecting URL as well."
First, take a look at the search results. This static home page blog is already indexed by Google and looks to have been successfully indexed:
Note that the URL does not show the final redirected URL of Static Home Page - which is a good thing.
Now, taking a look at the actual page HTTP response you can see that Google does a 302 temporary page redirect for the static home page:
From what I could see on the Google help pages and forums, this looks good for Blogger static home pages. Take a look at this response from a Google representative on 302 redirect behavior.
To quote the representative from Google, "Generally speaking, with a 302 redirect we'd try to take the content of the redirect target (in your case PAGE-B) and index it under the redirecting URL (in your case PAGE-A). If the target has a noindex meta tag, then it's likely that we'd apply that to the redirecting URL as well."
0 comments:
Post a Comment