SignalMind Blog

Responsive and mobile content builder. API-enabled.

How to prevent "Faulty Redirects" with piJnz

faulty redirects - GoogleEarlier this summer Google has announced a few changes in ranking of smartphone search results, possibly penalizing sites that are not following the new recommendations. One of the most common ones is "Faulty Redirects". A "faulty redirect" is when a user is redirected to an irrelevant page on the mobile site. For instance, when a smartphone user arrives at a specific secondary desktop page - "about us" page or "products" page - as a result of Google search or direct entry, and is redirected to the home page of the mobile site.

This is a very common scenario, and unfortunately it generates poor user experience, since it makes it difficult for users to find the information they expected to see (or in cases when the information is absent on the mobile site - makes it impossible for users to access that information on their mobile devices).

Google is asking that instead of always redirecting visitors to the home page of the mobile site, the redirects are set up separately per page (so that each desktop site page is redirecting to its equivalent on the mobile site). And if the desktop page has no equivalent on the mobile site, then do not redirect that page at all.

Our redirect script allows you to configure separate per-page redirects, including your default redirect settings (for pages not individually listed in your per-page instructions), and no-redirect settings (when the desktop page has no mobile equivalent and should not have a redirect at all). For details, please visit this knowledge base article.

-------------------------------------

image credit: Google Webmaster Central Blog

Elena English

Mobile afficionado and tech entrepreneur. Follow on Google+

Comments are closed