Not set Vs not provided Keyword - Google Analytics

on Wednesday, 1 March 2017
(Not Provided) = Organic visits from a keyword search

In 2011 Google switched to a secure server (https) which encrypts search results. Meaning anytime you’re logged into Google (i.e. Gmail, Calendar or YouTube) your searches become protected – Leaving all keyword data as (not provided) in Google Analytics.
We’re noticing most accounts have more than 50% of all keyword information replaced with (not provided).

(Not Set) = A direct visit or a referral from another site

This is a little more complicated, but basically refers to a catch-all for information Google Analytics wasn’t able to identify.

For example, if you see landing page = (not set), it probably means that session didn’t have a page or screen view. The session could have been triggered an Event or an E-commerce hit type.

Conclusion

Google’s ‘not provided’ data is a controversial topic, and there’s no failsafe way to access the data. However, if you’re losing a significant amount of statistical data to ‘not provided’, it’s certainly worth investing some time to overcome the problem. Implementing one or more workarounds may help you to improve your understanding of organic keywords and get a better insight into your missing statistics.

Basics of Mobile SEO

on Tuesday, 7 February 2017
Mobile optimization is the process of ensuring that visitors who access your site from mobile devices have an experience optimized for the device.

Every year people spend more and more time on their mobile devices and tablets, but many websites still aren't designed to account for different screen sizes and load times. Mobile optimization takes a look at site design, site structure, page speed, and more to make sure you're not inadvertently turning mobile visitors away.

Best Practices 

 

If your site is already well optimized for search engines, there are only a few additional things that you need to think about when optimizing for mobile.

Page speed

 

Because of hardware and connectivity issues, page speed is even more important for mobile users than desktop users. Beyond optimizing images, you'll want to minify code, leverage browser caching, and reduce redirects. More information on page speed can be found on our SEO Best Practices for Page Speed page.

Don't block CSS, JavaScript, or images

 

In the old days, some mobile devices couldn't support all of these elements, so webmasters of mobile sites blocked one or all three. But for the most part that's no longer true, and the Smartphone GoogleBot wants to be able to see and categorize the same content that users do. So don't hide it. These elements are also critical to helping Google understand if you have a responsive site or a different mobile solution.

Site design for mobile

 

Mobile devices are simplifying and revolutionizing the ways sites are designed. "Above the fold" has no longer meaning in a world where we scroll endlessly.

Don't use Flash

 

The plugin may not be available on your user's phone, which means they'll miss out on all the fun. If you want to create special effects, use HTML5 instead.

Don't use pop-ups either

 

It can be difficult and frustrating to try and close these on a mobile device. This might lead to a high bounce rate.

Design for the fat finger

 

Touch screen navigation can lead to accidental clicks if your buttons are too big, too small, or in the path of a finger that's trying to get the page to scroll.

Optimize titles and meta descriptions

 

Remember that you're working with less screen space when a user searches using a mobile device. To show off your best work in SERPS, be as concise as possible (without sacrificing the quality of the information) when creating titles, URLs, and meta descriptions.

Use Schema.org structured data

 

Because of the limited screen space, a search result with rich snippets is even more likely to stand out than on a desktop. Read more about Schema.org structured data.

Optimize for local search


If your business has a local element, remember to optimize your mobile content for local search. This includes standardizing your name, address, and phone number and including your city and state name in your site's metadata.

Mobile site configuration


Probably the most important decision you'll make when setting up a site is deciding whether you want to use a responsive, dynamic serving, or separate site configuration. Each has its advantages and disadvantages. Google prefers responsive design but supports all three options as long as you have set them up properly.

Responsive web design

 

Responsively designed sites use CSS3 media queries to serve the same content to mobile and desktop users using a fluid grid and a flexible design to automatically adapt to the size of a user's screen.
Responsive designs use media queries to target the layout based on screen width, orientation, and resolution. For example, you could use the following CSS to instruct browsers how to display content for a screen that's 420 or fewer pixels wide:

Dynamic serving

 

If you don't have the resources for a complete site redesign or want to display different content for mobile visitors than you do for desktop ones, one solution is to use one URL to display different sets of HTML and CSS depending on what type of device your visitor is using (also called detecting user agents). This can be useful, for example, if you're a restaurant who wants a mobile visitor (who might be wandering your neighborhood) to see a sampling of reviews and a map to your location, instead of your full website.
Displaying different content based on the user agent is called dynamic serving and it's done using the Vary HTTP header, which looks like this:

Vary HTTP Header

 

GET /page-1 HTTP/1.1
Host: www.example.com
(...rest of HTTP request headers...)
HTTP/1.1 200 OK
Content-Type: text/html
Vary: User-Agent
Content-Length: 5710
(... rest of HTTP response headers...)

Example from the Google Developers Blog.

Simply put, this means that the content displayed will vary based on the user agent requesting the page.
Dynamic serving is not the perfect compromise that it might seem to be. For one, it relies on having an updated list of user agents, which means that every time a new mobile device comes to market that list needs to be updated. And it's not uncommon for desktops and mobile devices to be wrongly served with the HTML for the other device.

Separate mobile URL

 

Another option is to create a second, parallel site for mobile users. This allows you to create completely custom content for mobile visitors. To avoid URL confusion, most parallel mobile sites use an "m" subdomain.

Parallel mobile sites can be as imperfect as dynamic serving sites at sending visitors to the right version, so be sure to make it easy for visitors who end up in the wrong place to click over to their preferred experience.

You'll also want to make sure that your site redirects are all in place and as lean as possible to decrease page speed. And to avoid duplicate content issues, you'll need to set up rel="canonical".

Post credit : SeoMoz.