Can I redirect Google bot to another domain with escaped_fragments?

Can I redirect Google bot to another domain with escaped_fragments? - If a page has internal and external outgoing links to redirecting URLs, it’s returning 3xx (301, 302, etc.) HTTP status codes standing for redirection. This issue means that the page does not exist on a permanent or temporary basis. It appears on most of the popular web browsers, usually caused by a misconfigured website. However, there are some steps you can take to ensure the issue isn’t on your side. You can find more details about redirecting URLs by reading the Google Search Central overview. In this article, we’ll go over how you can fix the Can I redirect Google bot to another domain with escaped_fragments? error on your web browser. Problem :

I'm trying to make my Webapp SEO friendly. I read that I can redirect Google's bot to another URL with escaped_fragments. I'd like to use Phantom.js to serve Google my pages. Unfortunately, I can't run Node with my hosting solution.

Can I redirect Google bot to another domain? Will it hurt?

Solution :

You can serve different content to search bots but typically, if you are serving different content (or at least handling search bots differently) to human visitors, then you need to be wary of cloaking which can produce negative effects in how your site performs.

Google addresses redirects from _escaped_fragment URLs in their FAQ:

Can I use redirects to point the crawler at my static content?

Redirects are okay to use, as long as they eventually get you to a page that's equivalent to what the user would see on the #! version of the page. This may be more convenient for some webmasters than serving up the content directly. If you choose this approach, please keep the following in mind:

1. Compared to serving the content directly, using redirects will result in extra traffic because the crawler has to follow redirects to get the content. This will result in a somewhat higher number of fetches/second in crawl activity.


2. Note that if you use a permanent (301) redirect, the url shown in our search results will typically be the target of the redirect, whereas if a temporary (302) redirect is used, we'll typically show the #! url in search results.


3. Depending on how your site is set up, showing #! may produce a better user experience, because the user will be taken straight into the AJAX experience from the Google search results page. Clicking on a static page will take them to the static content, and they may experience avoidable extra page load time if the site later wants to switch them to the AJAX experience.

Given that redirects are fine as long as they get to the same content that the user would see, I don't see any reason that cross-site redirects wouldn't be fine as long as they get to the correct content.

We hope that this article has helped you resolve the seo, redirects, node-js error in your web browsers. Enjoy browsing the internet uninterrupted!