Translate

Google Adsense Mobile Guide and Tutorial

Google Adsense Mobile
Google Adsense Mobile Guide and Tutorial - Google Search has adapted new Google algorithms to help users find Google mobile-friendly web pages and apps. We guide to make sure visitors have a good experience on your site when visiting from their mobile devices.

Google Adsense Mobile Guide and Tutorial

Learn our this Google Adsene Guide get the best practices to provide your visitors a good user experience and to make most of your mobile traffic. New Google algorithms and search about 61% of people will leave a mobile site if they don’t see what they are looking for straight away and 21% of internet users globally only use their smartphone to access the internet. How about your site?

Google Mobile Guide
Make it Mobile Friendly Websites and easy access for your Mobile user
  1. Ease of use
    • Include logo or company name on every page that links back to the home page
  2. Touch friendly
    • Reclaim space by hiding the URL bar
  3. Font size•
    • Configure the viewport & Size tap targets

Google Adense Tutorial Mobile Devices
When a page does not specify a viewport, mobile browsers will render that page at a fallback width ranging from 800 to 1024 CSS pixels. The page scale factor is adjusted so that the page fits on the display, forcing users to zoom before they can interact with the page.

Configure the Viewport
A viewport controls how a webpage is displayed on a mobile device. Without a viewport, mobile devices will render the page at a typical desktop screen width, scaled to fit the screen. Setting a viewport gives control over the page's width and scaling on different devices. This rule triggers when PageSpeed Insights detects that your page does not specify a viewport, or specifies a viewport that does not adapt to different devices.

Pages optimized to display well on mobile devices should include a meta viewport in the head of the document specifying width=device-width, initial-scale=1.
<meta name=viewport content="width=device-width, initial-scale=1">
Google Pages Optimized:
  1. Hardware pixel: A physical pixel on the display. For example, an iPhone 5 has a screen with 640 horizontal hardware pixels.
  2. Device-independent pixel (dip): A scaling of device pixels to match a uniform reference pixel at a normal viewing distance, which should be approximately the same size on all devices. An iPhone 5 is 320 dips wide.
  3. CSS pixel: The unit used for page layout controlled by the viewport. Pixel dimensions in styles such as width: 100px are specified in CSS pixels. The ratio of CSS pixels to device independent pixels is the page's scale factor, or zoom.
Meta Viewport Tag
A meta viewport tag gives the browser instructions on how to control the page's dimensions and scaling, and should be included in the document's head.

Fixed-Width Viewport
The viewport can be set to a specific width, such as width=320 or width=1024. While discouraged, this can be a useful stopgap to ensure pages with fixed dimensions display as expected.

Responsive Viewport
Using the meta viewport value width=device-width instructs the page to match the screen's width in device independent pixels. This allows the page to reflow content to match different screen sizes.
Some browsers, including iOS and Windows Phone, will keep the page's width constant when rotating to landscape mode, and zoom rather than reflow to fill the screen. Adding the attribute initial-scale=1 instructs browsers to establish a 1:1 relationship between CSS pixels and device independent pixels regardless of device orientation, and allows the page to take advantage of the full landscape width.

Avoid minimum-scale, maximum-scale, user-scalable It is possible to set the minimum and maximum zoom, or disable the user's ability to zoom the viewport entirely. These options negatively impact accessibility and should generally be avoided.

The meta viewport tag, while broadly supported, is not part of a formal standard. This behavior is being included in CSS as part of the CSS Device Adaptation specification. Until this specification is finalized and widely implemented, authors should continue to use the meta viewport tag for compatibility, either alone or with corresponding viewport styles.

Size Content to Viewport
This rule triggers when PageSpeed Insights detects that the page content does not fit horizontally within the specified viewport size, thus forcing the user to pan horizontally to view all the content.

On both desktop and mobile devices, users are used to scrolling websites vertically but not horizontally, and forcing the user to scroll horizontally or to zoom out in order to see the whole page results in a poor user experience. When developing a mobile site with a meta viewport tag, it easy to accidentally create page content that doesn't quite fit within the specified viewport. For example, an image that is displayed at a width wider than the viewport can cause the viewport to scroll horizontally. You should adjust this content to fit within the width of the viewport, so that the user does not need to scroll horizontally.

Since screen dimensions vary widely between devices (e.g. between phones and tablets, and even between different phones), you should configure the viewport so that your pages render correctly on many different devices. However, since the width (in CSS pixels) of the viewport may vary, your page content should not rely on a particular viewport width to render well.

Avoid setting large absolute CSS widths for page elements (such as div{width:360px;}), since this may cause the element to be too wide for the viewport on a narrower device (e.g. a device with a width of 320 CSS pixels, such as an iPhone). Instead, consider using relative width values, such as width:100%. Similarly, beware of using large absolute positioning values that may cause the element to fall outside the viewport on small screens. If necessary, CSS media queries can be used to apply different styling for small and large screens. This Web Fundamentals article provides further recommendations on how to go about this.

Test your Mobile Friendly Websites
Pick the metrics that are most important to you and your users and experiment with them. From smartphones and tablets to laptops and television, 90% of all media interactions today are on a screen. Businesses that allow users to interact with their brand across all platforms and on all devices are able to generate more engagement. Many publishers have trouble identifying areas of their sites that need work. Google tutorial identifying Mobile Friendly Websites:
Google Mobile Friendly Websites
  1. Social Sources
    • Shares
    • Page Speed and load time
    • Engagement
  2. Direct Traffic
    • Page Speed and load time
    • Time on site
    • Page views per visit
Be consistent acrossscreens Make it easy for your users to find what they’re looking for no matter
what device they’re using:
  1. Web Fundamentals: Best practices for a great multi-device web
  2. Google Multi-screen Guidelines
Multi-Screen Starter Guide
Google Multi-Screen Starter Guide is for publishers who want to learn why a Adsense multi-screen strategy is important, and how to start building immediately. Google Multi-Screen Implementation Guide is for those who have already built a multi-screen site, and provides monetization tips, user experience tips, and more on how to maximize your mobile audience. Let’s get started Google Adsense Multi-Screen Implementation Guide to grow audience and boost revenue from your multi-screen site:
  1. Monetization tips
  2. Mobile user experience tips
  3. Mobile search engine optimization tips
So, make sure your site's ready for mobile-friendly Google search results

Optimizations for the mobile Web
New Google Search will be expanding its use of mobile-friendliness as a ranking signal. This change will affect mobile searches in all languages worldwide and will have a significant impact in Google Search results. Users will find it easier to get relevant, high quality search results optimized for their devices.
  1. PageSpeed Insights: A free tool that analyzes the content of a web page then generates suggestions to make that page faster.
  2. Device Mode and Mobile Emulator:
    • Device mode brings the insights of mobile testing to your browser tab through the power of mobile emulation
  3. Make images zoomable on tap or pinch to zoom & use lazy loading
Make sure your website is ready for this new Google search change, this change will affect mobile searches in all languages worldwide.

Google Tutorial to check Mobile-friendly Website
You can check your site by testing your pages with the Mobile-Friendly Test tool.
This tool shows how Google Search sees your pages. To get a list of mobile usability issues across your sites, log in to your Search Console account and use the Mobile Usability Report.

Get started Adsense mobile-friendly sites to build your mobile-friendly site. Ensure your site is designed for your mobile users, and your ads should be too. Bumen Media website is already mobile-friendly. If you already have a mobile-friendly site:
  1. Double-check your site’s pages using the Mobile-Friendly Test tool and see how Google Search sees your pages.
  2. Learn about growing audience and revenue from your site.
  3. Use the Mobile Search Engine Optimization to help your site show up in search results.
  4. Go mobile today to provide your visitors a good user experience and to make most of your mobile traffic.
Google Mobile SEO
Let's make sure your site shows up in search results. Here you can learn Google SEO mobile how to configure your site for multiple devices and help search engines understand your site.

Choose your Mobile Configuration
There are three main techniques for implementing a website that can handle view screens of all types and sizes. Here’s a the Google mobile configuration methods:
  1. Responsive Web Design
    • Serves the same HTML code on the same URL regardless of the users’ device (desktop, tablet, mobile, non-visual browser), but can render the display differently (i.e., “respond”) based on the screen size. Responsive design is Google’s recommended design pattern.
  2. Dynamic Serving
    • Uses the same URL regardless of device, but generates a different version of HTML for different device types based on what the server knows about the user’s browser.
  3. Separate URLs
    • Serves different code to each device, and on separate URLs. This configuration tries to detect the users’ device, then redirects to the appropriate page using HTTP redirects along with the Vary HTTP header.
Google does not favor any particular URL format as long as the page(s) and all page assets are accessible to all Googlebot user-agents.

The key points for going mobile
There are key points for going mobile that you should take note of regardless of which configuration you choose to set up.
  1. Signal to Google when a page is formatted for mobile (or has an equivalent page that’s formatted for mobile). This helps Google accurately serve mobile searchers your content in search results.
  2. Keep resources crawlable. Do not use robots.txt to block search engines from accessing critical files on your site that help render the page (including ads). If Googlebot doesn’t have access to a page’s resources, such as CSS, JavaScript, or images, we may not detect that it’s built to display and work well on a mobile browser. In other words, we may not detect that the page is "mobile-friendly," and therefore not properly serve it to mobile searchers.
  3. Avoid common mistakes that frustrate mobile visitors, such as featuring unplayable videos (e.g., Flash video as the page’s significant content). Mobile pages that provide a poor searcher experience can be demoted in rankings or displayed with a warning in mobile search results.
Mobile Devices Type
  1. Mobile: In this article, "mobile" or mobile devices refers to smartphones, such as devices running Android, iPhone, or Windows Phone. Mobile browsers are similar to desktop browsers in that they can render a broad set of the HTML5 specification, although their screen size is smaller and in almost all cases their default orientation is vertical.
  2. Tablets: We consider tablets as devices in their own class, so when we speak of mobile devices, we generally do not include tablets in the definition. Tablets tend to have larger screens, which means that, unless you offer tablet-optimized content, you can assume that users expect to see your site as it would look on a desktop browser rather than on a smartphone browser.
  3. Multimedia phones: These are phones with browsers that are able to render pages coded to meet XHTML standards, support HTML5 Markup, JavaScript/ECMAscript but might not support some of the extension APIs in the HTML5 standard. This generally describes the browser in most 3G-ready phones that are not smartphones.
  4. Feature phones: On these phones, browsers lack the capability to render normal desktop webpages coded using standard HTML. This includes browsers that render only cHTML (iMode), WML, XHTML-MP, etc.
New Google recommendations are geared toward smartphones, but we encourage multimedia and feature phones site owners to follow the same advice where they feel appropriate.

Adsense Placement Tips
The placement of your ads is important. Focus on creating a flow between your content and the ad placements for the ultimate user experience. Consult your analytics data to set events and understand where your users are most receptive. Here is Google Adsense Placement Tips:
  1. When using enhanced features in text ads, decrease accidental clicks by moving the ad units a minimum of 150 pixels away from content
  2. Peek ATF* for a great UX while maximizing revenue potential
  3. Potential eCPMs increase when you swap 320x50 for 320x100 ad units
  4. Anchor social links to make sharing easy
  5. Use the 300x250 ad unit for a potential increase in fill rates and eCPM
As Google publisher shold you know the various Adsene sizes and Adsene formats specific for your mobile site such as:
Adsene Sizes
  1. Responsive Ads
    • Optimize ad size to screen size
    • Works seamlessly with your responsive site
  2. Native Ads
    • Ads that complement the content of your site
    • Focus on both apps and web
  3. Page Level Ads / Anchor Ads
    • Smooth, dismissible, smart
    • Reserved for high CPM ads
    • Ads truly stick to the bottom of the page
  4. Page Level Ads / Vignettes
    • Appear between page navigation
    • Reserved for the highest Adsense paying impressions
    • Ad is pre-loaded
    • Doesn’t slow the user experience on the page
Mobile Web Guide
Engagement ‘Push notifications’ and ‘Add to Home Screen’ allow users to build deep, engaged relationships with the mobile experiences they love. Take advantage of these advanced features directly on the web without the friction associated with installing an app.
  1. Push Notifications
    • Timely, personalized notifications
    • Make it easy to return to your site
    • Increase frequency of engagement with your users
  2. Add to Home Screen
    • Single tap to access your site
    • Keep your users engaged
    • Build your brand
Since your Google Grants account is limited to a $1.00 max CPC, you are unable to activate
keywords whose minimum bid is above $1.00 by raising your bid. If you want to activate a keyword that is 'inactive for search', we suggest you first try optimizing your keyword, ad text, and campaign.
For example, consider adding your keyword to your ad text, or changing your campaign targeting options. Please ensure that the keyword is highly targeted and relevant, as it will be difficult to reactivate general keywords through optimization.
Share: