I just want to be sure if i use
server.transfer method for display
mobile version of my website, is it good for
Server detect mobile user agent by a function and use this method to change displaying page, with different content and design.
Now i'm wondering does google compare this (mobile) version with my desktop version? and what happen when it find out these are different?
My desktop version has
media and is
responsive but user can see new mobile design with this method, also google can (i tested with fetch as google)
m. sub domain is ok but what about this?
As far as I understand
Server.Transfer method is better than the old
Response.Redirect method because its improve server request performance by reducing the number of requests. To me that is good enough and as long as the path parameter is clean you will always retrieve the necessary resources to load the page.
Responsive Design is Google recommended display method because the page URL and HTML stay the same. If your URL stays the same but the HTML changes google will classify this format as Dynamic Serving, whereas if URL and HTML changes Google will treat it as Separate URLs.
Each format has a different approach when it comes to SEO. The way you identify the user-agent is also important for Dynamic Serving, Google Recommends using Vary HTTP. In the case of Separate URLs you need to establish the relationship between the URL-Version-1 and URL-Version-2, here Google recommends using the using the
<link> tag, where the Desktop version needs
rel=”alternate” and the mobile version needs
rel=”canonical” to link Mobile and Desktop URLs.
Please take into account that if you are using m.example.com vs example.com they are essentially different URLs.
Whatever your approach might be the bottom line is that you need the following to be always true:
I highly recommend you to read what Google have said about going Mobile First