<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Marketing Land &#187; Cindy Krum</title>
	<atom:link href="http://marketingland.com/author/cindy-krum/feed" rel="self" type="application/rss+xml" />
	<link>http://marketingland.com</link>
	<description>Marketing Land</description>
	<lastBuildDate>Fri, 24 May 2013 01:55:13 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Will Siri And Voice Search Change Mobile Marketing?</title>
		<link>http://marketingland.com/will-siri-and-voice-search-change-mobile-marketing-10008</link>
		<comments>http://marketingland.com/will-siri-and-voice-search-change-mobile-marketing-10008#comments</comments>
		<pubDate>Fri, 08 Jun 2012 13:00:03 +0000</pubDate>
		<dc:creator>Cindy Krum</dc:creator>
				<category><![CDATA[Channel: Search Marketing]]></category>
		<category><![CDATA[Mobile Marketing]]></category>
		<category><![CDATA[Mobile Marketing Column]]></category>
		<category><![CDATA[Search Marketing]]></category>

		<guid isPermaLink="false">http://marketingland.com/?p=10008</guid>
		<description><![CDATA[Mobile phones are, after all, phones, so it&#8217;s natural that they respond well to voice commands. So it&#8217;s no surprise that voice search has grown dramatically given advances in the technology. According to Google, speech inputs have grown 6X in the past year, as shown in the graph below. As voice technology continues to improve, [...]]]></description>
				<content:encoded><![CDATA[<p style="text-align: left;">Mobile phones are, after all, phones, so it&#8217;s natural that they respond well to voice commands. So it&#8217;s no surprise that voice search has grown dramatically given advances in the technology.</p>
<p style="text-align: left;">According to Google, speech inputs have grown 6X in the past year, as shown in the graph below. As voice technology continues to improve, voice search is quickly becoming more important in mobile content discovery and site optimization.</p>
<p><div id="attachment_10016" class="wp-caption aligncenter" style="width: 564px"><a href="http://marketingland.com/will-siri-and-voice-search-change-mobile-marketing-10008/mobilespeechinputs-2" rel="attachment wp-att-10016"><img class="size-full wp-image-10016 " src="http://marketingland.com/wp-content/ml-loads/2012/04/MobileSpeechInputs1.jpg" alt="Google Mobile Speech Queries" width="554" height="320" /></a><p class="wp-caption-text">Source: http://www.blindfiveyearold.com/search-trends-to-watch-2011</p></div></p>
<p>The fanfare associated with Siri, the voice-activated virtual assistant on the most recent iPhone 4s, is the main reason that voice search has more in the spotlight, but voice search has actually existed for a number of years.</p>
<p>Google has offered a speech-input search app since 2009, available for download on iPhone, BlackBerry and Nokia s60. This functionality is also now standard on Android phones, and can be downloaded from the Android Marketplace if it is not already pre-loaded. Before these apps were available, Google even offered Goog411, which was a phone number that searchers could call to submit a search, and have the results read to them or sent directly to their phone via SMS.</p>
<h2>Big Strides Have Been Made In Voice Recognition</h2>
<p>Historically, the technological interpretation of voice commands has been less than accurate, which made early adoption and enthusiasm for voice search weak. Variations of different languages, dialects, pitches and accents must be cataloged, and understood, even in noisy conditions. It&#8217;s not an easy task.</p>
<div> Since those days, there has been significant improvement in the voice interpretation technology, which has emboldened both Apple and Google to pursue voice search more actively. Google switched to a cloud-based processing of voice searches, which builds understanding of each local language and dialect based on commonalities among queries, and the clicked results. Google <a href="http://googlemobile.blogspot.com/2011/12/voice-search-arrives-in-middle-east.html">says</a>:“While initially we may not accurately recognize words spoken in every regional accent and dialect, one of the major benefits to Google’s cloud-based model is that the more people use Voice Search, the more accurate it becomes.”</div>
<p>While it was not widely publicized, the voice understanding technology that Google uses is probably relying on the same technologies that drive Google Instant and Google QDF and Google Quality Score, in which cloud-based analysis of a consistently strong CTR  (and low bounce rate) for a lower-ranking site will naturally gain it credibility and rankings over time, as it gets more clicks than the listings above it. This kind of long-term reinforcement with clicks is probably informing and altering voice search results, or it will soon.</p>
<p>Here is what Google <a href="http://googlemobile.blogspot.com/2010/06/salut-willkommen-benvenuto-bienvenido.html">is saying</a> about Google’s Voice Search:</p>
<p style="padding-left: 30px;"><em>“Our goal is to bring Google Search by voice to speakers of all languages. We follow a rigorous process to add each new language or dialect. Working directly with native speakers in each country, we spend weeks collecting spoken utterances to create the specific models which power the service. Our helpers are asked to read popular queries in their native tongue, in a variety of acoustic conditions such as in restaurants, out on busy streets, and inside cars. We also construct, for each language, a vocabulary of over one million recognizable words. It’s no small feat, but we love doing it.&#8221;</em></p>
<h2>Similar Queries For Text And Voice Mobile Search</h2>
<p>The good news about voice search, in terms of content discovery, is that it appears to simply translate a voice query then submit it thorough the same mobile search algorithms as if it was typed in. This means that there is no algorithmic change, and the only major change for a mobile SEO strategy would be to anticipate the longer and more casual, question-based queries, which are more common in voice search.</p>
<div class="mceTemp">
<p><div id="attachment_10021" class="wp-caption aligncenter" style="width: 511px"><a href="http://marketingland.com/will-siri-and-voice-search-change-mobile-marketing-10008/speechsearchcategories-3" rel="attachment wp-att-10021"><img class="size-full wp-image-10021 " src="http://marketingland.com/wp-content/ml-loads/2012/04/SpeechSearchCategories2.jpg" alt="Mobile Voice Seach Categories" width="501" height="612" /></a><p class="wp-caption-text">Google Mobile Voice-Based Search Categories are Similar to Mobile Text-Based Search Categories</p></div></p>
</div>
<p>As a whole, voice based search is most common for local searches, but this is likely because most early Android devices included Google Maps with the voice search functionality. Other than that, the categories that are commonly searched for in mobile voice search appear to be very similar to mobile text-based search.</p>
<p>The mobile ad network Chitika <a href=" http://insights.chitika.com/2010/google-voice-search-is-local-search-heaven/">reports</a> that the biggest category of voice search is &#8220;News&#8221; at 20%. After that is &#8220;Reference&#8221; at 17% then &#8220;Other&#8221; at 15%, and these are all largely similar to the text-based searches that they measure from in the Google Search Application.</p>
<h2>Virtual Assistants Drive Data Usage</h2>
<p>Interestingly, access to a virtual assistant like Siri appears to drive lots of engagement with digital information in the form of mobile data. The Huffington Post <a href="http://www.huffingtonpost.com/2012/01/05/iphone-4s-data_n_1187748.html?ncid=edlinkusaolp00000003">reports</a> that: “iPhone 4S users transfer on average three times more data than users of the older iPhone 3G model….”</p>
<p>Some of the data consumption can be attributed directly to the heavy requests that come from Siri, as she scours multiple primary sources to get your answers, but another component is the reduced barrier to search. Without having to type, search and access to digital information becomes much easier and more casual.</p>
<p>While Siri has only launched in the US, Apple Insider <a href="http://www.appleinsider.com/articles/12/01/06/iphone_4s_users_consume_nearly_twice_as_much_data_as_iphone_4_study.html">reports</a> that this will soon change:</p>
<p style="padding-left: 30px;"><em>‘Siri is still in beta mode, with limited functionality outside of the U.S. Apple is, however planning a rapid</em> <a href="http://www.appleinsider.com/articles/11/10/14/siri_functionality_limited_outside_us_but_apple_promises_updates_in_2012.html">international expansion</a> <em>for Siri this year. The company is</em> <a href="http://www.appleinsider.com/articles/11/12/06/apple_hiring_more_siri_engineers_working_on_evolving_api_features_languages.html">actively hiring</a> <em>iOS software engineers to help develop the Application Programming Interface for Siri and port the feature to other languages.’</em></p>
<p>Siri and her other virtual assistant competitors can complete a variety of tasks and access a variety of different information, beyond simply inputting a search query. They can pull information from a number of sources directly and only default to a web search if they do not have access to more specific information.</p>
<h2>Create Feeds To Assist Assistants</h2>
<p>This adds to the complexity of optimizing for voice search. Beyond anticipating what keywords people will use to search, we are now forced to anticipate what sources the virtual assistant will prefer or recommend. The good news, this may be less of a black box, and more influence-able if someday you are able to work directly with Apple, and submit qualified XML feeds.</p>
<p style="text-align: center;"><a href="http://marketingland.com/will-siri-and-voice-search-change-mobile-marketing-10008/siriresults-2" rel="attachment wp-att-10011"><img class="size-large wp-image-10011 aligncenter" src="http://marketingland.com/wp-content/ml-loads/2012/04/SiriResults1-600x461.jpg" alt="Many Types of Siri Search Results" width="600" height="461" /></a></p>
<p>All of the sources that Siri pulls data from are just websites that are sending Apple specialized feeds, so that Siri can access the information more quickly.</p>
<p>While it cedes a lot of information and power to Apple, it seems like the biggest win in voice search would be for Apple to work directly mobile resource sites to accept their information feeds. This would mean that users have quicker access to information about show times, character bios, episode summaries, celebrity bios and maybe even movie trailers and music news.</p>
<p>With this strategic move, you would become a primary source of information for your niche, and would not have to rely so heavily on Google to help people find your mobile content.</p>
]]></content:encoded>
			<wfw:commentRss>http://marketingland.com/will-siri-and-voice-search-change-mobile-marketing-10008/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Too Many Companies Are Ignoring Mobile Web Traffic</title>
		<link>http://marketingland.com/too-many-companies-are-ignoring-mobile-web-traffic-10026</link>
		<comments>http://marketingland.com/too-many-companies-are-ignoring-mobile-web-traffic-10026#comments</comments>
		<pubDate>Thu, 31 May 2012 13:00:06 +0000</pubDate>
		<dc:creator>Cindy Krum</dc:creator>
				<category><![CDATA[Channel: Mobile Marketing]]></category>
		<category><![CDATA[Mobile Marketing Column]]></category>

		<guid isPermaLink="false">http://marketingland.com/?p=10026</guid>
		<description><![CDATA[Marketers are all talking about the massive growth in mobile web access, both in the United States and around the world, but something important to note is that web development teams have been a bit slow to provide mobile specific experiences. This article will look at what percent of sites have developed a mobile-specific website [...]]]></description>
				<content:encoded><![CDATA[<p>Marketers are all talking about the massive growth in mobile web access, both in the United States and around the world, but something important to note is that web development teams have been a bit slow to provide mobile specific experiences.</p>
<p>This article will look at what percent of sites have developed a mobile-specific website experience and how they are presenting the mobile content to their users across different mobile handsets.<strong></strong></p>
<p>Once the Quantcast <a href="http://www.quantcast.com/top-sites">Top Million US Sites Data</a> from 2011 was made public, a company called Mongoose Metrics created a bot that was meant to crawl all these Top Sites and gather data about how they were serving their mobile content.</p>
<p>While the crawler was intended to answer some very specific questions about how mobilization was achieved on top sites, the data mostly show the dearth of Top Sites that are actively addressing their mobile traffic.</p>
<p>Mongoose Metrics began by testing to see what portion of the Top Million sites were accessible to their crawler, and published a cool <a href="http://c296965.r65.cf1.rackcdn.com/Mobile%20Readiness%20Study.pdf">mobile marketing study</a> with the results.</p>
<p>In the study they found 15,981 sites, or 1.6% of sites, were blocking crawlers and could not be evaluated and 112,346 or about 11.2% returned errors to the crawler. So the other 87.2% of sites were available to evaluate (great news!)</p>
<p>They made the crawler simulate a site visit as an iPhone, and Android phone and a Blackberry, and the results of those crawls are in the table below:</p>
<p><div id="attachment_10027" class="wp-caption aligncenter" style="width: 610px"><img class="size-large wp-image-10027 " src="http://marketingland.com/wp-content/ml-loads/2012/04/MobileCrawlData-600x308.jpg" alt="Mobile Crawl Data by OS" width="600" height="308" /><p class="wp-caption-text">Mobile Crawl Results By OS - Mobile Publishing</p></div></p>
<p>An average of only 7.2% of sites were serving mobilized content. You would think that more marketing departments and CEO’s would demand that they be serving a mobile-specific web experience on their sites, especially since these are the US sites with the ‘top’ traffic in 2011, but, according to this study, that is not the case.</p>
<p>The lack of webmaster attention to mobile traffic could indicate a few different things:</p>
<ol>
<li>Companies are ignoring mobile traffic or assuming that people will be able to successfully use a traditional website on their mobile phone.</li>
<li>Decision makers believe that mobile solutions are still too complicated and expensive and are not expected to generate enough revenue to justify the expense.</li>
<li>Companies are confused about what their customers want in a mobile experience and don’t know how to address the problem.</li>
<li>Companies are providing a mobile-specific experience or a mobile-adapted experience that can’t be detected by the crawlers, such as a Responsive Design approach with flexible layout that adapts itself to mobile phones without changing the page code or redirecting to another page.</li>
</ol>
<p>So what does all this data mean to you and your company if you are about to launch a mobile marketing campaign? The Mongoose Metrics study that generated those results evaluated three different types of mobile publishing:</p>
<ol>
<li>Server-Side Redirection</li>
<li>On-Page JavaScript Redirection</li>
<li>Selective Serving of Mobile Content (what they describe as &#8220;cloaking.&#8221;)</li>
</ol>
<p>The summarized results of the findings look like this:</p>
<p style="text-align: left;"><a href="http://marketingland.com/wp-content/ml-loads/2012/04/TopMillionSitesMobile.png"><img class="aligncenter size-full wp-image-13235" style="margin-top: 10px; margin-bottom: 10px;" title="TopMillionSitesMobile" src="http://marketingland.com/wp-content/ml-loads/2012/04/TopMillionSitesMobile.png" alt="" width="443" height="109" /></a>Based on the data from the Mongoose Metrics analysis, the most common strategy for mobile publishing is with server-based user-agent detection and redirection. This means that when the desktop pages are requested, the server will automatically send people to the mobile version of the page instead.</p>
<p>The next option, which Mongoose Metrics describes as &#8220;cloaking,&#8221;’ is the second most popular way to serve mobile pages. I prefer to describe this method as &#8220;selective serving&#8221; rather than &#8220;cloaking&#8221; because, for the most part, you are deciding to &#8220;send&#8221; or &#8220;not send&#8221; content based on the device that is accessing the page, rather than altering the intent of the page.</p>
<p>To understand how it works, consider this example: If there is a massive image on a page, your server might decide to send a smaller, lower resolution photo when a phone is accessing the site. Similarly, if there is heavy Flash video, your server might decide to send a still picture instead.</p>
<p>If you are using this &#8220;cloaking&#8221; method of mobile content negotiation,  make sure that you are showing essentially the same content, so that it does not look like it is an attempt to manipulate the search engines (as in the <em>bad</em> sense of the word &#8220;cloaking&#8221;).</p>
]]></content:encoded>
			<wfw:commentRss>http://marketingland.com/too-many-companies-are-ignoring-mobile-web-traffic-10026/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Mobile URLs vs. Single URLs: Making The Right Decision For Your Company</title>
		<link>http://marketingland.com/mobile-urls-vs-single-urls-making-the-right-decision-for-your-company-10004</link>
		<comments>http://marketingland.com/mobile-urls-vs-single-urls-making-the-right-decision-for-your-company-10004#comments</comments>
		<pubDate>Wed, 09 May 2012 13:00:33 +0000</pubDate>
		<dc:creator>Cindy Krum</dc:creator>
				<category><![CDATA[Channel: Search Marketing]]></category>
		<category><![CDATA[Features & Analysis]]></category>
		<category><![CDATA[Mobile Marketing]]></category>
		<category><![CDATA[Search Marketing]]></category>

		<guid isPermaLink="false">http://marketingland.com/?p=10004</guid>
		<description><![CDATA[The Bing statement about mobile SEO last month, which followed Google’s announcement about the new smartphone crawler in December, has sparked some discussion, and given mobile SEO some time in the spotlight. The debate has been interesting, but all of it seems to focus a bit too much on the wrong question. The search engines all [...]]]></description>
				<content:encoded><![CDATA[<div>
<p><a href="http://marketingland.com/wp-content/ml-loads/2012/05/shutterstock_71478790-tugofwar.jpg"><img class="alignright size-medium wp-image-11579" style="margin-left: 8px; margin-right: 8px;" title="shutterstock_71478790-tugofwar" src="http://marketingland.com/wp-content/ml-loads/2012/05/shutterstock_71478790-tugofwar-300x200.jpg" alt="" width="300" height="200" /></a>The <a href="http://www.bing.com/community/site_blogs/b/webmaster/archive/2012/03/07/building-websites-optimized-for-all-platforms-desktop-mobile-etc.aspx">Bing statement about mobile SEO</a> last month, which followed <a href="http://googlewebmastercentral.blogspot.com/2011/12/introducing-smartphone-googlebot-mobile.html">Google’s announcement about the new smartphone crawler</a> in December, has sparked some discussion, and given mobile SEO some time in the spotlight.</p>
<p>The debate has been interesting, but all of it seems to focus a bit too much on the wrong question. The search engines all emphatically instruct webmasters not to make decisions purely on the SEO implications, but to also consider the user experience.</p>
<p>While I always take this suggestion with a very large and suspicious grain of salt, I do think it is important to consider the users who access the site….as well as the marketing managers who have to promote the mobile content and the developers who maintain the site, (and who will readily tell you that they almost always get the short end of the stick, whether you are talking about mobile design and development, or just about anything else … poor misunderstood souls!).<strong></strong></p>
<p>So let’s discuss the question of mobile site structure from the perspective of an SEO, but also give these other groups a bit more attention.</p>
<p>We can’t forget to consider how users, marketing managers and site development/maintenance teams will be effected by the decision to keep all content on one URL using <a title="Responsive Web Design Isn’t Meant To Replace Mobile Web Sites" href="http://marketingland.com/responsive-web-design-isnt-meant-to-replace-mobile-web-sites-7949">Responsive Design</a> (the most common way to do it) or the decision to break the content out and have separate mobile pages on a mobile subdomain or subdirectory.</p>
<h2>What Do SEOs Want?</h2>
<p>First, we’ll discuss the SEO, since it is obviously very important. In the SEO world, we are commonly asked to look at situations are respond with &#8220;ideal&#8221; solutions that are frequently unachievable without also adding in &#8220;ideal&#8221; budgets, resources and timelines.</p>
<p>This happens even more commonly in mobile, because of the added complexity in mobile SEO, which pushes the ideal much further away from the &#8220;possible.&#8221;</p>
<p>There is a lot of debate on this topic, and that is because there is not one perfect answer. The best option will depend on what you already have in place, and what your assets and limitations are for the mobile SEO effort. In my experience and best estimation, most SEOs will have the following thoughts regarding the question of mobile site architecture:</p>
<table border="1" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td colspan="2" valign="top" width="614">
<h2><strong>SEOs</strong></h2>
</td>
</tr>
<tr>
<td colspan="2" valign="top" width="614"><strong><span style="text-decoration: underline;">One URL Solution</span></strong></td>
</tr>
<tr>
<td valign="top" width="307"><strong>
They Like:</strong></td>
<td valign="top" width="307"><strong>
They Don’t Like:</strong></td>
</tr>
<tr>
<td valign="top" width="307">
<ul>
<li>Not having to build and SEO new pages for mobile</li>
<li>Not having to rely on the new smartphone bot</li>
<li>Not risking over-indexing or under-indexing on a new subdomain or subdirectory</li>
<li>Being able to leverage existing rankings, history, links and SEO efforts on more devices</li>
<li>Scalable solutions that are easy to sell and discuss with other teams</li>
<li>Pages will reliably work on all devices when linked in social media</li>
<li>That Bing has endorsed the one-URL strategy</li>
</ul>
</td>
<td valign="top" width="307">
<ul>
<li>Slow, heavy pages that may cause a high bounce rate that could affect mobile and desktop rankings as well as PPC Quality Score</li>
<li>Not being able to target mobile-specific keywords as well with pages that work on desktop AND mobile</li>
<li>Load time issues associated with having one set of code that serves multiple devices well</li>
<li>Creative limitations of Responsive Design that could hurt bounce rate and conversion</li>
<li>Difficulty associated with tracking and addressing different use-cases and conversion opportunities</li>
</ul>
</td>
</tr>
<tr>
<td colspan="2" valign="top" width="614"><strong> </strong></td>
</tr>
<tr>
<td colspan="2" valign="top" width="614"><strong><span style="text-decoration: underline;">Mobile-Specific Urls</span></strong></td>
</tr>
<tr>
<td valign="top" width="307"><strong>
They Like:</strong></td>
<td valign="top" width="307"><strong>
They Don’t Like:</strong></td>
</tr>
<tr>
<td valign="top" width="307">
<ul>
<li>The Google smartphone bot understands and indexes mobile redirects which minimizes the server load and load time of mobile pages -– a tacit endorsement of this strategy</li>
<li>Faster load time for mobile users and mobile bots</li>
<li>Mobile keyword targeting and use-cases to decrease bounce rate</li>
<li>Easier to track and attribute mobile traffic and mobile campaigns</li>
<li>Social media links that redirect appropriately based on the device</li>
</ul>
</td>
<td valign="top" width="307">
<ul>
<li>Difficulty working with mobile platforms, mobilization engines or just new pages</li>
<li>Complexity of user-agent detection and redirection -– especially if not all pages are mobilized</li>
<li>Risk of indexation problems with new mobile crawlers, redirect rules and more indexes</li>
<li>Different rankings on different devices, in different locations and with different personalization settings</li>
</ul>
</td>
</tr>
</tbody>
</table>
<h2>What Do Users Want?</h2>
<p>While it might be easy to argue that users would prefer multiple designs, suited for whatever device they happen to be on, it is almost impossible to claim that users would prefer multiple URLs, and keep a straight face.</p>
<p>Except for the home page, users are mostly unaware of the file structure or URL formatting of a site, either on mobile or traditional viewing. But they are easily confused and you want to make their lives as easy as possible.</p>
<p>Even the most savvy person in the room could have trouble determining if they should use the &#8220;m.&#8221; version of a site or the desktop version of a site when they are on a tablet, and that is because there are no rules or standards for this yet. Every company is doing it differently, and that won’t change for a while.</p>
<p>The best option for your users is for you to sort it out on their behalf, so that they never have to think about what URL to use and when. Doing everything on one URL eliminates this question altogether, but if you can’t do that or you need very different design layouts on the pages, user-agent detection and redirection from your desktop site to the mobile and tablet versions of each page is the best answer.</p>
<p>User-agent detection and redirection schemes may be the best for your users because they can be based on screen size of the device, the mobile browser or the specific device user-agent. You can have different pages pulled based on any combination of those things. It can get quite complicated, but there is a handy <a href="http://www.mobilemoxie.com/marketing-tools/redirection-script-generator/">mobile redirection script generator tool</a> that can help you with writing the necessary code if you need it. In my experience, users have the following opinions on this topic:</p>
<table border="1" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td colspan="2" valign="top" width="614">
<h2><strong>Users</strong></h2>
</td>
</tr>
<tr>
<td colspan="2" valign="top" width="614"><strong><span style="text-decoration: underline;">One URL Solution</span></strong></td>
</tr>
<tr>
<td valign="top" width="307"><strong>
They Like:</strong></td>
<td valign="top" width="307"><strong>
They Don’t Like:</strong></td>
</tr>
<tr>
<td valign="top" width="307">
<ul>
<li>URLs that they can copy and send to other devices and always work</li>
<li>Not wondering if they should search for &#8220;mobile&#8221; or type in an &#8220;m.&#8221;</li>
<li>Not learning a new site design or navigation</li>
</ul>
</td>
<td valign="top" width="307">
<ul>
<li>Desktop content that doesn’t work on touch screen, like hovers or Flash</li>
<li>Slow download speed on older phones or slower networks</li>
</ul>
</td>
</tr>
<tr>
<td colspan="2" valign="top" width="614"><strong> </strong></td>
</tr>
<tr>
<td colspan="2" valign="top" width="614"><strong><span style="text-decoration: underline;">Mobile-Specific URLs</span></strong></td>
</tr>
<tr>
<td valign="top" width="307"><strong>
They Like:</strong></td>
<td valign="top" width="307"><strong>
They Don’t Like:</strong></td>
</tr>
<tr>
<td valign="top" width="307">
<ul>
<li>Experience that is tailored to the device they are on</li>
<li>Marketing and messaging that is related to the device that they are on</li>
</ul>
</td>
<td valign="top" width="307">
<ul>
<li>Learning a new page layout or navigational scheme</li>
<li>Pages that they want not being available on mobile</li>
</ul>
</td>
</tr>
</tbody>
</table>
<h2>What Do Marketing Managers Want?</h2>
<p><strong></strong>Remember that when you are working with marketing directors or brand managers, they care about more than just the website &#8212; they care about offline marketing and email, PPC, banners, partnerships and apps.</p>
<p>They are trying to keep lots of groups happy and coordinated. The question about how to manage and maintain the mobile site structure impacts many other marketing initiatives including apps, SMS, QR codes, print &amp; outdoor marketing, and online advertising.</p>
<p>Marketing managers want mobile content that is reliable and easy to promote in a variety of different ways. They may lean towards a one-URL system, simply because it makes it easier for them to know that they are always promoting the correct URL, and not have to use different URLs for mobile and desktop, or possibly different URLs for tablet and mobile.</p>
<p>On the other hand, they may prefer mobile-specific URLs, so that the landing page experience is more tailored for the handset of the user, so that they can promote OS-specific app downloads or so that they can easily track mobile and desktop traffic to the site separately.</p>
<p>This is what you will be told if you discuss mobile site structure with a group of marketing managers:</p>
<table border="1" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td colspan="2" valign="top" width="614">
<h2><strong>Marketing Managers</strong></h2>
</td>
</tr>
<tr>
<td colspan="2" valign="top" width="614"><strong><span style="text-decoration: underline;">One URL Solution</span></strong></td>
</tr>
<tr>
<td valign="top" width="307"><strong>
They Like:</strong></td>
<td valign="top" width="307"><strong>
They Don’t Like:</strong></td>
</tr>
<tr>
<td valign="top" width="307">
<ul>
<li>Being able to copy a URL from their desktop and knowing it should work on tablets and mobile phones too</li>
<li>Fast development timelines and a unified look and feel on all devices</li>
</ul>
</td>
<td valign="top" width="307">
<ul>
<li>Slow QA &amp; Errors that are hard to predict and replicate</li>
<li>Limitations on design changes across different devices</li>
<li>Slow load time</li>
</ul>
</td>
</tr>
<tr>
<td colspan="2" valign="top" width="614"><strong> </strong></td>
</tr>
<tr>
<td colspan="2" valign="top" width="614"><strong><span style="text-decoration: underline;">Mobile-Specific URLs</span></strong></td>
</tr>
<tr>
<td valign="top" width="307"><strong>
They Like:</strong></td>
<td valign="top" width="307"><strong>
They Don’t Like:</strong></td>
</tr>
<tr>
<td valign="top" width="307">
<ul>
<li>Device or OS-specific landing pages that can promote apps and other downloads properly</li>
<li>Easily tracking performance for mobile vs. desktop</li>
<li>Flexibility to make mobile-specific and tablet-specific experiences that are not tied to the design of the desktop site.</li>
</ul>
</td>
<td valign="top" width="307">
<ul>
<li>Waiting for templates to be developed and deployed multiple times</li>
<li>Being confused about when it is appropriate to promote specific versions of a page</li>
</ul>
</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<h2>What Do Developers Want?</h2>
<p>Developers are a hard group to please, and they can have a variety of objections to the numerous SEO and mobile requests we put in front of them. Their basic goal is to keep the site up, functioning and preforming at its peak with minimal fire drills and emergencies in the middle of the night.</p>
<p>Some would probably prefer one URL site architecture, especially if they are strong in HTML5, CSS3, jQuery and other Responsive Design tricks that allow them to show off their skills. Others might prefer to work with redirects on the server, and let the designers go nuts designing loads of different templates for every device imaginable.</p>
<p>Their opinions will be varied, but one thing that is certain is that developers are under even more pressure than everyone else. They are expected to understand the needs of all the different groups and then actually build pages to meet those needs and expectations, whether they are reasonable or not.</p>
<p>Here is what you will usually learn if you discuss this question with a team of developers:</p>
<table border="1" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td colspan="2" valign="top" width="614">
<h2><strong>Developers</strong></h2>
</td>
</tr>
<tr>
<td colspan="2" valign="top" width="614"><strong><span style="text-decoration: underline;">One URL Solution</span></strong></td>
</tr>
<tr>
<td valign="top" width="307"><strong>
They Like:</strong></td>
<td valign="top" width="307"><strong>
They Don’t Like:</strong></td>
</tr>
<tr>
<td valign="top" width="307">
<ul>
<li>Being able to show off and try out new coding techniques in Responsive Design</li>
<li>Not having to re-build a page or page templates every time there is a new device or screen size</li>
<li>Not having to assist with separate SEO processes for new pages</li>
<li>Not maintaining and remembering new URL structure or separate tracking</li>
</ul>
</td>
<td valign="top" width="307">
<ul>
<li>Testing their designs on lots of different devices to make sure that everything works as planned</li>
<li>Not being able to replicate mobile errors  reliably on their computers</li>
</ul>
</td>
</tr>
<tr>
<td colspan="2" valign="top" width="614"><strong> </strong></td>
</tr>
<tr>
<td colspan="2" valign="top" width="614"><strong><span style="text-decoration: underline;">Mobile-Specific URLs</span></strong></td>
</tr>
<tr>
<td valign="top" width="307"><strong>
They Like:</strong></td>
<td valign="top" width="307"><strong>
They Don’t Like:</strong></td>
</tr>
<tr>
<td valign="top" width="307">
<ul>
<li>Knowing how and when a page is expected to work and render</li>
<li>Being able to test pages just on a small set of devices that they will need to serve</li>
</ul>
</td>
<td valign="top" width="307">
<ul>
<li>Feeling like they will always be building out a new template for a new device and will never be done</li>
<li>They will have to link the multiple variations of a page for users and on the server with user-agent detection and redirection</li>
<li>User-agent detection and re-direction or mobilization engines can drastically increase server load</li>
</ul>
</td>
</tr>
</tbody>
</table>
<h2> Conclusion</h2>
<p>So just like any good SEO question, the answer on this one is &#8220;it depends.&#8221; The decision to use a one-URL strategy to reach your mobile audience or to build mobile-specific pages on mobile-specific URLs really does depend, not only on the type of content and experience that you want to create, but also on who is really deeply involved in the decision making and planning process.</p>
<p>Everyone will likely have slightly different opinions and experiences, but it will help to remember where they are coming from, what their goals and KPIs are, and then you will hopefully be able to derive a strategy that will please at least some of the people, some of the time.</p>
</div>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://marketingland.com/mobile-urls-vs-single-urls-making-the-right-decision-for-your-company-10004/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
