Como configurar e validar páginas AMP.
Não leu ontem? Leia hoje! :)
Sitelinks are the links shown below search results on some queries, to help users navigate your website. Over the years, our algorithms have gotten much better at finding, creating, and showing relevant sitelinks, and so we feel it's time to simplify things.
We only show sitelinks for results when we think they'll be useful to the user. If the structure of your site doesn't allow our algorithms to find good sitelinks, or we don't think that the sitelinks for your site are relevant for the user's query, we won't show them. This process is completely automated. Sitelinks have evolved into being based on traditional web ranking, so the way to influence them is the same as other web pages.
Best practices to improve the quality of your sitelinks include:
# Provide a clear structure for your website, using relevant internal links and anchor text that's informative, compact, and avoids repetition.
# Allow Google to crawl and index important pages within your site. Use Fetch and Render  to check that they can be rendered properly.
# If you need to remove a page from search completely, use a "noindex" robots meta tag  on that page.
Should you run across undesired sitelinks for your site with common queries, feel free to drop by the webmaster help forums  to get advice from other webmasters, and to let us know about it. We appreciate all feedback on our search results, and use it to help further improve our algorithms over time!
 Fetch & render: https://support.google.com/webmasters/answer/6066468
 Noindex: https://support.google.com/webmasters/answer/93710
 Webmaster forum: https://support.google.com/webmasters/go/community
When is it recommended to start thinking about SEO or hiring a consultant?
If you have more questions you'd like to see answered, we're listening!
Q: Should I move my site all at once to HTTPS, or bit by bit?
A: We recommend initially moving just a piece of the site to test any effects on traffic and search indexing. After that you can move the rest of your site all at once or in chunks.
When choosing the initial test section of the site, pick a section that changes less frequently and isn't significantly affected by frequent or unpredictable events.
Also keep in mind that while moving just one section is a great way to test your move, it's not necessarily representative of a whole site move when it comes to search. The more pages that you move, the more likely you'll encounter additional problems to solve. Careful planning can minimize problems.
Q: How long should I run my trial?
A: Plan for a few weeks to allow for crawling and indexing to pick up changes, plus time to monitor traffic.
Q: Even though we are starting with only a section, we plan to make the entire site available on HTTPS. To avoid indexing of the HTTPS content early, should we use redirects or rel=canonicals?
A: With redirects in place, you won't be able to test those pages from a technical point of view, so we'd recommend using rel=canonical.
Q: We reference our HTTP sitemaps in robots.txt. Should we update the robots.txt to include our new HTTPS sitemaps?
A: We recommend separate robots.txt files for HTTP and HTTPS, pointing to separate sitemap files for HTTP and HTTPS. We also recommend listing a specific URL in only one sitemap file.
Q: Which sitemap should map the section in the HTTPS trial?
A: You can create a separate sitemap just for the updated section of your site. This will enable you to track indexing of the trial section more precisely. Be sure not to duplicate these URLs in any other sitemaps, though.
Q: Are there any other specific things we need to add to the robots.txt for the HTTPS version?
Q: Our HTTPS site redirects non-migrated pages back to HTTP. What should our sitemaps list? Should we list in our sitemaps both the HTTP and HTTPS URLs? What if in the test section the HTTP URLs redirect to HTTPS?
A: List all HTTP URLs in your HTTP sitemap, and all HTTPS URLs in your HTTPS sitemap, regardless of redirects when the user visits the page. Having pages listed in your sitemap regardless of redirects will help search engines discover the new URLs faster.
Q: If we set includeSubDomains in our HSTS header, which domains will that affect?
A: After you migrate your entire site to HTTPS, you can support HSTS preloading for extra security. To enable this, you must set the includeSubDomains directive in the HSTS header.
If the site www.example.com serves an HSTS header with includeSubdomains set, then it will apply to www.example.com and foo.www.example.com, but not example.com or foo.example.com.
Keep in mind however that HSTS adds complexity to your rollback strategy. Our recommendation is this:
1. Roll out HTTPS without HSTS first.
2. Start sending HSTS headers with a short TTL. Monitor your traffic both from users and other clients, and also dependants' performance, such as ads.
3. Slowly increase the HSTS TTL.
If HSTS doesn't affect your users and search engines negatively, you can, if you wish, ask your site to be added to the Chrome HSTS preload list (https://hstspreload.appspot.com/).
Q: We use a single Google News sitemap for our entire site. What do we do if we're migrating our site piece by piece?
A: If you want to use a Google News sitemap for the new HTTPS section, you will have to contact the News team (https://support.google.com/news/publisher/contact/update_domain) to let them know about the protocol change, and then in your HTTPS property in Search Console you can submit a new Google News sitemap (https://support.google.com/news/publisher/answer/74288) for each migrated HTTPS section of the site.
Q: Are there any specific recommendations for Google News Publisher Center (https://partnerdash.google.com/) with HTTPS migration?
A: Google News Publisher Center handles the HTTP->HTTPS moves transparently. In general you don't have to do anything from Google News perspective, unless you're also making use of News sitemaps. In that case, please get in touch with the News team and let them know about the change, https://support.google.com/news/publisher/contact/update_domain. You can also let the team know about changing sections, for example in case you're moving to HTTPS, you can specify that you're moving http://example.com/section to https://example.com/section .
- apis3Managing Partner, 2013 - present
- engeenoCo-Founder and Managing Director, 2011 - present
- Webspam, Search Quality, 2006 - 2011
I love the areas of Search, Web Usability, UX and Design. From March 2006 to September 2011 I worked for Google, as an Analyst in the Webspam team where everyday I dealt with spam and attempts of manipulation in the organic search results.
In September 2011 I left Google and Co-Founded Engeeno with another ex-Googler from the Search Quality team. Today we focus on Search Performance, Usability and helping move the web forward.
- IADE - Escola Superior de DesignPost Grad in Communication and Image, 2001 - 2002
- IADE - Escola Superior de DesignMA in Graphic Design, 1996 - 2000
These Top 30 Ashley Madison Passwords are just as Terrible as You'd Think
These are the most worst Ashley Madison users' account passwords are just as Terrible as You'd Think
Study Of Spain's 'Google Tax' On News Shows How Much Damage It Has Done ...
As you may recall, governments across Europe, generally at the behest of traditional newspaper publishers, have been pushing for what they c
Google Opinion Rewards - Android-apps op Google Play
Werk mee aan korte enquêtes en ontvang Google Play-tegoed met Google Opinion Rewards, een app die is ontwikkeld door Google Consumentenonder
Sync for reddit – Apps para Android no Google Play
Sync for reddit (previously reddit sync) is a full-featured app for browsing the popular site reddit on the go. Featuring secure login, comm
Buffer: Social Media, Twitter - Android Apps on Google Play
Buffer is the easiest way to share on Twitter, Facebook, Google+, LinkedIn and App.net. Schedule your updates to post at optimal times, whet