Mobile SEO

From Google:
Google’s recommendation

From their FAQ:

Regarding m.example.com sites:
“It’s fine to have a mobile-only page without a desktop equivalent (just make sure these pages don’t include a rel=”canonical” to a non-corresponding desktop version). Please be aware that mobile-only pages will need to build a reputation on their own (i.e., contain unique content, be well-linked from other pages on your site or the web) because they will not receive shared indexing signals from an existing desktop version of the page.”

Is it okay if I have some pages using responsive design and others using dynamic serving?:
“Yes, it’s fine to use more than one configuration for your site. Just check that on a page-level basis, each provides the right indications to search engines (e.g., the responsive page has the @media only screen and (max-width: 600px) {...} information and the dynamic serving page uses the Vary: HTTP header). Or, if you’re using a hybrid of responsive design (e.g., responsive but with images dynamically served), we still consider that responsive since the page is nearly the same – keep the markup @media only screen and (max-width: 600px) {...} and forego the Vary HTTP header if it’s included specifically for Google. If you’re using responsive images, include the<picture> element.”

I have both a mobile website and a native app. Any advice?:
“Yes, first, build your mobile website and native apps with “deep linking capability” or URIs that provide pointers to specific areas of content (vs. a Flash ball that’s only accessible from the start screen). Deep links and URIs provide more acquisition possibilities for your business through Search or social sharing. Second, see App Indexing for Google Search for more information on driving more traffic to your native app from Google Search.”

First question means it doesn’t hurt desktop site and mobile site, but they are considered as different site, which means when you google search the site, it probably won’t show up as “Mobile-friendly” site and result that comes up might not be for device you are visiting with (ie. search result may return indexed content of desktop site, and it might not be available for mobile device to view since mobile device will likely be redirected to m.example.com)

Second question is kind of concerning, as picture element is currently only supported in Chrome. There are polyfills for it, but that rely on JavaScript, and that could sacrifice the page load speed and SEO ranking.

Cool thing about last question is that, if you link it properly, you can even index native app’s page within Google search.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s