MarTech All Access passes are sold out, but you can still attend! Learn how.

In one week, join other professionals in tackling issues at the intersection of marketing and technology at MarTech: The Marketing Tech Conference. All Access conference passes are SOLD OUT — but it’s not too late for you to attend. You can still register for an Expo Pass by March 20 and pay…

Please visit Search Engine Land for the full article.

Google 2016 candidate searches now include campaign funding details & search trends

Since launching candidate cards earlier this year, Google continues to expand its 2016 election-related search results.

The post Google 2016 candidate searches now include campaign funding details & search trends appeared first on Search Engine Land.

Please visit Search Engine Land for the full article.

Updating the smartphone user-agent of Googlebot

As technology on the web changes, we periodically update the user-agents we use for Googlebot. Next month, we will be updating the smartphone user-agent of Googlebot:

Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.96 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
(Googlebot smartphone user-agent starting from April 18, 2016)

Today, we use the following smartphone user-agent for Googlebot:

Mozilla/5.0 (iPhone; CPU iPhone OS 8_3 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) Version/8.0 Mobile/12F70 Safari/600.1.4 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
(Current Googlebot smartphone user-agent)

We’re updating the user-agent string so that our renderer can better understand pages that use newer web technologies. Our renderer evolves over time and the user-agent string indicates that that it is becoming more similar to Chrome than Safari. To make sure your site can be viewed properly by a wide range of users and browsers, we recommend using feature detection and progressive enhancement.

Our evaluation suggests that this user-agent change should have no effect on 99% of sites. The most common reason a site might be affected is if it specifically looks for a particular Googlebot user-agent string. User-agent sniffing for Googlebot is not recommended and is considered to be a form of cloaking. Googlebot should be treated like any other browser.

If you believe your site may be affected by this update, we recommend checking your site with the Fetch and Render Tool in Search Console (which has been updated with the new user-agent string) or by changing the user-agent string in Developer Tools in your browser (for example, via Chrome Device Mode). If you have any questions, we’re always happy to answer them in our Webmaster help forums.

Posted by Katsuaki Ikegami, Software Engineer

7 proactive ways to jump-start your SEO before a site launch

About to launch a new website? You may think you can’t do SEO until the site is live, but columnist John Lincoln reminds us that there are many steps you can take beforehand to ensure a smooth site launch.

The post 7 proactive ways to jump-start your …

What your teacher didn’t tell you about optimizing site speed

Site speed impacts your search engine ranks, so how can you make improvements? Columnist Brian Harnish details a few ways to decrease page load time for your top-performing pages.

The post What your teacher didn’t tell you about optimizing site speed appeared first on Search Engine Land.

Please visit Search Engine Land for the full article.