Posicionamiento en buscadores

How listening to our users helped us build a better Search Console

Google herramientas para webmaster - Mar, 06/02/2018 - 15:13
The new Search Console beta is up and running. We’ve been flexing our listening muscles and finding new ways to incorporate your feedback into the design. In this new release we've initially focused on building features supporting the users’ main goals and we'll be expanding functionality in the months to come. While some changes have been long expected, like refreshing the UI with Material Design, many changes are a result of continuous work with you, the Search Console users.
We’ve used 3 main communication channels to hear what our users are saying:
  • Help forum Top Contributors - Top Contributors in our help forums have been very helpful in bringing up topics seen in the forums. They communicate regularly with Google’s Search teams, and help the large community of Search Console users.
  • Open feedback - We analyzed open feedback comments about classic Search Console and identified the top requests coming in. Open feedback can be sent via the ‘Submit feedback’ button in Search Console. This open feedback helped us get more context around one of the top requests from the last years: more than 90 days of data in the Search Analytics (Performance) report. We learned of the need to compare to a similar period in the previous year, which confirmed that our decision to include 16 months of data might be on the right track.
  • Search Console panel - Last year we created a new communication channel by enlisting a group of four hundred randomly selected Search Console users, representing websites of all sizes. The panel members took part in almost every design iteration we had throughout the year, from explorations of new concepts through surveys, interviews and usability tests. The Search Console panel members have been providing valuable feedback which helped us test our assumptions and improve designs.
In one of these rounds we tested the new suggested design for the Performance report. Specifically we wanted to see whether it was clear how to use the ‘compare’ and ‘filter’ functionalities. To create an experience that felt as real as possible, we used a high fidelity prototype connected to real data. The prototype allowed study participants to freely interact with the user interface before even one row of production code had been written.
In this study we learned that the ‘compare’ functionality was often overlooked. We consequently changed the design with ‘filter’ and ‘compare’ appearing in a unified dialogue box, triggered when the ‘Add new’ chip is clicked. We continue to test this design and others to optimize its usability and usefulness.
We incorporated user feedback not only in practical design details, but also in architectural decisions. For example, user feedback led us to make major changes in the product’s core information architecture influencing the navigation and product structure of the new Search Console. The error and coverage reports were originally separated which could lead to multiple views of the same error. As a result of user feedback we united the error and coverage reporting offering one holistic view.
As the launch date grew closer, we performed several larger scale experiments. We A/B tested some of the new Search Console reports against the existing reports with 30,000 users. We tracked issue fix rates to verify new Search Console drives better results and sent out follow-up surveys to learn about their experience. This most recent feedback confirmed that export functionality was not a nice-to-have, but rather a requirement for many users and helped us tune detailed help pages in the initial release.
We are happy to announce that the new Search Console is now available to all sites. Whether it is through Search Console’s feedback button or through the user panel, we truly value a collaborative design process, where all of our users can help us build the best product.
Try out the new search console.
We're not finished yet! Which feature would you love to see in the next iteration of Search Console? Let us know below.
Posted by the Search Console UX team

Launching SEO Audit category in Lighthouse Chrome extension

Google herramientas para webmaster - Lun, 05/02/2018 - 18:52

We're happy to announce that we are introducing another audit category to the Lighthouse Chrome Extension: SEO Audits.

Lighthouse is an open-source, automated auditing tool for improving the quality of web pages. It provides a well-lit path for improving the quality of sites by allowing developers to run audits for performance, accessibility, progressive web apps compatibility and more. Basically, it "keeps you from crashing into the rocks", hence the name Lighthouse.

The SEO audit category within Lighthouse enables developers and webmasters to run a basic SEO health-check for any web page that identifies potential areas for improvement. Lighthouse runs locally in your Chrome browser, enabling you to run the SEO audits on pages in a staging environment as well as on live pages, public pages and pages that require authentication.

Bringing SEO best practices to you

The current list of SEO audits is not an exhaustive list, nor does it make any SEO guarantees for Google websearch or other search engines. The current list of audits was designed to validate and reflect the SEO basics that every site should get right, and provides detailed guidance to developers and SEO practitioners of all skill levels. In the future, we hope to add more and more in-depth audits and guidance — let us know if you have suggestions for specific audits you'd like to see!

How to use it

Currently there are two ways to run these audits.

Using the Lighthouse Chrome Extension:
  1. Install the Lighthouse Chrome Extension
  2. Click on the Lighthouse icon in the extension bar 
  3. Select the Options menu, tick “SEO” and click OK, then Generate report

Running SEO Audits in Lighthouse extension

Using Chrome Developer tools on Chrome Canary:
  1. Open Chrome Developer Tools 
  2. Go to Audits 
  3. Click Perform an audit 
  4. Tick the “SEO” checkbox and click Run Audit

Running SEO Audits in Chrome Canary
The current Lighthouse Chrome extension contains an initial set of SEO audits which we’re planning to extend and enhance in the future. Once we're confident of its functionality, we’ll make the audits available by default in the stable release of Chrome Developer Tools.

We hope you find this functionality useful for your current and future projects. If these basic SEO tips are totally new to you and you find yourself interested in this area, make sure to read our complete SEO starter-guide! Leave your feedback and suggestions in the comments section below, on GitHub or on our Webmaster forum.

Happy auditing!

Posted by Valentyn, Webmaster Outreach Strategist.

Nueva categoría de auditoría de SEO en la extensión de Chrome Lighthouse

Blog oficial de Google para Webmasters - Lun, 05/02/2018 - 18:07
Hoy tenemos el placer de anunciar que añadimos otro tipo de auditoría a la extensión de Chrome Lighthouse: la auditoría de SEO.

Lighthouse es una herramienta automatizada de código abierto que permite llevar a cabo auditorías para mejorar la calidad de las páginas web. Con ella, los programadores pueden auditar varios indicadores, como el rendimiento, la accesibilidad o la compatibilidad de aplicaciones web progresivas, y así mejorar la calidad de sus sitios web. Como su propio icono indica, Lighthouse evita que tu sitio web se vaya a pique.

Con esta nueva auditoría de Lighthouse, los programadores y webmasters pueden comprobar aspectos básicos de SEO en cualquier página web, lo que les permite identificar las áreas que pueden mejorarse. Lighthouse se ejecuta de forma local en tu navegador Chrome, por lo que puedes realizar auditorías de SEO en páginas en construcción, activas y publicadas e, incluso, en páginas que requieren autenticación.

Prácticas recomendadas de SEO a tu alcance

Actualmente, en la lista de auditorías de SEO no se incluyen todos los indicadores, ni tampoco se garantiza que la página web que se audita esté optimizada para la búsqueda web de Google o de otros motores de búsqueda. Esta lista está pensada para validar y mostrar los aspectos básicos de SEO que deberían aplicarse correctamente en todos los sitios web. Además, se ofrecen consejos e instrucciones que pueden resultar útiles a programadores y profesionales de SEO de cualquier nivel. De cara al futuro, esperamos añadir cada vez más auditorías completas y consejos útiles. Si se te ocurre alguna auditoría que te gustaría que incluyéramos, háznoslo saber.

¿Cómo se utiliza?

Actualmente puedes ejecutar estas auditorías de dos formas distintas.

Con la extensión de Chrome Lighthouse:
  1. Instala la extensión de Chrome Lighthouse.
  2. Haz clic en el icono de Lighthouse de la barra de extensiones. 
  3. En el menú Options (Opciones), marca "SEO" y haz clic en OK (Aceptar). A continuación, selecciona Generate report (Generar informe).

Ejecutar auditorías de SEO en la extensión Lighthouse

Con las herramientas para desarrolladores de Chrome de Chrome Canary
  1. Abre las herramientas para desarrolladores de Chrome. 
  2. Accede a Audits (Auditorías).
  3. Haz clic en Perform an audit (Realizar una auditoría).
  4. Maca la casilla de "SEO" y haz clic en Run Audit (Ejecutar auditoría).

Ejecuta auditorías de SEO en Chrome Canary
Actualmente, en la extensión de Chrome Lighthouse solo se incluye un conjunto inicial de auditorías de SEO que tenemos previsto ampliar y mejorar más adelante. Una vez que sepamos con certeza que funcionan, las auditorías pasarán a estar disponibles de manera predeterminada en la versión estable de las herramientas para desarrolladores de Chrome.

Esperamos que esta nueva función te resulte útil tanto en tus proyectos actuales como en los futuros. Si no conocías estos consejos básicos de SEO y te interesa saber más del tema, consulta nuestra guía SEO para principiantes. Déjanos tu opinión en la sección de comentarios, en GitHub o en nuestro foro para webmasters.

¡Que tengas una buena auditoría!

Escrito por Valentyn, especialista en atención a webmasters.

#NoHacked 3.0: Corregir ataques habituales

Blog oficial de Google para Webmasters - Lun, 05/02/2018 - 12:09

Hasta ahora, en #NoHacked hemos compartido algunos consejos para detectar y prevenir ataques. Dado que ya eres capaz de detectarlos, queremos darte a conocer algunos de los métodos que los hackers utilizan con más frecuencia, así como darte instrucciones para poder enfrentarte a ellos.

Corregir ataques con palabras clave y enlaces encubiertos        

Los ataques con palabras clave y enlaces encubiertos crean automáticamente varias páginas con frases, enlaces e imágenes sin sentido. A veces, estas páginas contienen elementos de plantilla básicos del sitio web original, por lo que, a primera vista, parece que las páginas pertenecen al sitio web hasta que se lee el contenido. En este tipo de ataque, los hackers suelen utilizar técnicas de encubrimiento para esconder el contenido malicioso y hacer que la página insertada parezca parte del sitio web original o una página con el error 404. Enlace a la guía completa.

Corregir ataques de texto autogenerado

Los ataques de texto autogenerado crean automáticamente muchas páginas con frases sin sentido y llenas de palabras clave. Los hackers, de esta forma, buscan que las páginas pirateadas aparezcan en los resultados de la Búsqueda de Google. Después, cuando un usuario intenta visitarlas, se le redirige a una página sin relación alguna, como por ejemplo un sitio web con contenido pornográfico. Enlace a la guía completa.

Corregir ataques con palabras clave en japonés        

Los ataques con palabras clave en japonés normalmente crean páginas con texto en japonés en el sitio web, en directorios con nombres generados de forma aleatoria. Estas páginas obtienen ingresos mediante enlaces afiliados a tiendas que venden productos de marca de imitación y que después se muestran en la Búsqueda de Google. A veces, las cuentas de los hackers se añaden a Search Console como propietarios de los sitios web. Enlace a la guía completa.

Por último, una vez que hayas limpiado tu sitio web y solucionado el problema, presenta una solicitud de reconsideración para que nuestros equipos revisen el sitio web.

Si tienes alguna pregunta, puedes publicar tus preguntas en nuestros foros de ayuda para webmasters

#NoHacked 3.0: Consejos de prevención

Blog oficial de Google para Webmasters - Jue, 01/02/2018 - 11:51

En la entrada anterior de la campaña #NoHacked hablamos sobre cómo detectar ataques y por qué puedes ser objetivo de uno. En esta, en cambio, ofrecemos recomendaciones sobre la prevención.

Formas más habituales en las que los spammers piratean sitios web
Para proteger de ataques tu sitio web, es fundamental que entiendas cómo se ha pirateado. A continuación, te mostramos las formas que más utilizan los spammers para atacar sitios web.

Investiga las fuentes: ten cuidado con los temas o complementos premium gratuitos.
Es probable que hayas oído hablar de complementos premium gratuitos. Si alguna vez encuentras un sitio web que ofrece este tipo de complementos de manera gratuita, ten cuidado. La mayoría de los hackers utilizan como cebo un complemento popular, al que añaden puertas traseras o software malicioso que les permitan acceder a tu sitio web. Obtén más información sobre un caso similar en el blog de Sucuri (en inglés).
Incluso los complementos y temas originales y de buena calidad pueden ser peligrosos si cumplen alguna de las siguientes condiciones:
   - No se actualizan cuando hay una nueva versión disponible.
   - Su programador no los actualiza y se quedan anticuados con el tiempo.
En cualquier caso, para evitar que los hackers accedan a tu sitio web, es de vital importancia que todo el software sea moderno y esté actualizado.

Red zombi en WordPress
Una red zombi o botnet (en inglés) es una agrupación de máquinas, dispositivos o sitios web que se encuentran bajo el control de un tercero, que a menudo los utiliza para cometer actos maliciosos, como crear campañas de spam o usar software de clics automáticos o ataques distribuidos de denegación de servicio (DDoS). Es complicado detectar si tu sitio web se ha visto afectado por una red zombi, puesto que normalmente no se producen cambios concretos en él. Sin embargo, si el sitio web está en una red zombi, su reputación, recursos y datos están en peligro. Para obtener más información sobre las redes zombi y saber cómo detectarlas y cómo pueden afectar a tu sitio web, consulta el artículo sobre redes zombi en WordPress y Joomla (en inglés).

Como de costumbre, puedes recibir ayuda si publicas las preguntas que tengas en nuestros foros de ayuda para webmasters

#NoHacked 3.0: ¿Cómo puedo saber si han pirateado mi sitio web?

Blog oficial de Google para Webmasters - Lun, 29/01/2018 - 20:29

Este mes de Enero #NoHacked vuelve a estar en nuestros canales de G+ y Twitter. #NoHacked es nuestra campaña en redes sociales para sensibilizar a los usuarios sobre los ataques de piratería y ofrecerles consejos para que sus sitios web estén protegidos. En esta ocasión, queremos que puedas leer en español el contenido de la campaña #NoHacked que publiquemos en este blog.

¿Por qué se piratean los sitios web? Los hackers tienen varios motivos, y también disponen de diferentes métodos para alcanzar su objetivo, por lo que no siempre resulta sencillo detectar los ataques. A continuación te ofrecemos algunos consejos para facilitarte la tarea de detectar sitios web pirateados.

1. Primera pregunta: han hackeado mi sitio?
Si has recibido una alerta de seguridad, sea de Google u otra fuente, empieza por leer nuestra guía "¿Cómo puedo saber si han pirateado mi sitio web?". En ella se describen los pasos básicos que debes seguir para identificar las señales que indican que se ha vulnerado la seguridad de tu sitio web.

2. Entender la alerta de la Búsqueda de Google: 
En Google, nos enfrentamos a los ataques de piratería de varias formas. Las herramientas de análisis detectan software malicioso con frecuencia; sin embargo, es posible que algunos ataques que utilicen prácticas fraudulentas pasen desapercibidos. Por este motivo es posible que, aunque Navegación Segura no identifique ningún software malicioso, tu sitio web sí se haya pirateado y se esté utilizando para distribuir spam.

  • El mensaje "Este sitio puede haber sido comprometido" indica que es posible que se haya pirateado tu sitio web para mostrar spam; lo que significa, básicamente, que publica anuncios de manera gratuita.

  • El mensaje "Este sitio puede dañar tu ordenador", que puede aparecer bajo la URL de un sitio web, indica que creemos que el sitio web que estás a punto de visitar puede permitir que se instale software malicioso en tu ordenador.

  • Si se muestra una pantalla roja y grande antes de acceder a tu sitio web, puede indicar cualquiera de los siguientes problemas:

    • El mensaje "El sitio al que vas a acceder contiene software malicioso" indica que Google ha detectado que tu sitio web distribuye software malicioso

    • El mensaje "El sitio al que vas a acceder contiene programas dañinos" indica que Google ha detectado que tu sitio web distribuye software no deseado

3. Publicidad maliciosa frente a piratería:Se considera que hay publicidad maliciosa en un sitio web si se carga un anuncio malicioso. Es posible que, a primera vista, parezca que se haya pirateado el sitio web, quizá porque se redirige a los usuarios a otros lugares; sin embargo, solo se trata de un anuncio con mal comportamiento.

4. Redireccionamientos abiertos: comprueba si tu sitio web ha habilitado los redireccionamientos abiertos.
Es posible que los hackers quieran aprovecharse de un buen sitio web para enmascarar sus URL. Para conseguirlo, a veces utilizan redireccionamientos abiertos, lo que les permite redirigir a los usuarios a la URL que quieran mediante tu sitio web. Obtén más información aquí. (en inglés).

5. Comprobación móvil: visualiza tu sitio web desde un navegador móvil en modo incógnito y comprueba que no haya redes publicitarias para móviles maliciosas.
En algunas ocasiones, el contenido malicioso, como anuncios u otros elementos de terceros, redirigen a los usuarios móviles a otras ubicaciones sin que lo sepan. Este comportamiento puede eludir los sistemas de detección con facilidad, puesto que solo es visible en determinados navegadores. Comprueba que tu sitio web muestre el mismo contenido tanto en su versión para móviles como en la de ordenadores.

6. Utiliza Search Console y recibe notificaciones:
Search Console es una plataforma que Google utiliza para comunicarte cuestiones relacionadas con tu sitio web. También incluye muchas herramientas que pueden ayudarte a mejorarlo y gestionarlo. Te recomendamos que verifiques tu sitio web en Search Console, aunque no seas uno de sus programadores principales. Si Google detecta algún error grave en él, te lo notificaremos mediante las alertas y los mensajes de Search Console.

Si después de revisar los puntos anteriores no puedes encontrar indicios de que se haya pirateado tu sitio web, puedes pedir una segunda revisión a un experto de seguridad o en nuestros foros de ayuda para webmasters.

Using page speed in mobile search ranking

Google herramientas para webmaster - Jue, 18/01/2018 - 09:11

People want to be able to find answers to their questions as fast as possible — studies show that people really care about the speed of a page. Although speed has been used in ranking for some time, that signal was focused on desktop searches. Today we’re announcing that starting in July 2018, page speed will be a ranking factor for mobile searches.

The “Speed Update,” as we’re calling it, will only affect pages that deliver the slowest experience to users and will only affect a small percentage of queries. It applies the same standard to all pages, regardless of the technology used to build the page. The intent of the search query is still a very strong signal, so a slow page may still rank highly if it has great, relevant content.

We encourage developers to think broadly about how performance affects a user’s experience of their page and to consider a variety of user experience metrics. Although there is no tool that directly indicates whether a page is affected by this new ranking factor, here are some resources that can be used to evaluate a page’s performance.

  • Chrome User Experience Report, a public dataset of key user experience metrics for popular destinations on the web, as experienced by Chrome users under real-world conditions
  • Lighthouse, an automated tool and a part of Chrome Developer Tools for auditing the quality (performance, accessibility, and more) of web pages
  • PageSpeed Insights, a tool that indicates how well a page performs on the Chrome UX Report and suggests performance optimizations

As always, if you have any questions or feedback, please visit our webmaster forums.

Posted by Zhiheng Wang and Doantam Phan

Nueva versión de la Guía SEO para principiantes

Blog oficial de Google para Webmasters - Mié, 10/01/2018 - 11:40
Existe una gran cantidad de recursos disponibles para crear sitios web atractivos. Los propietarios de sitios web suelen preguntarnos por nuestras prácticas recomendadas para adaptar de manera óptima sus sitios a los motores de búsqueda. Antes, los recursos que ofrecíamos a los usuarios que no estaban familiarizados con este tema eran nuestra Guía SEO para principiantes y la Academia para webmasters. Hoy, para seguir ayudando a los webmasters a crear sitios web modernos y adaptados a los motores de búsqueda, anunciamos la publicación de la nueva versión de la Guía SEO para principiantes.En la versión anterior de esta guía, se describen las prácticas recomendadas para que los motores de búsqueda puedan rastrear, indexar y entender más fácilmente el contenido de sitios web. En la Academia para webmasters, por su parte, los webmasters pueden encontrar la información y las herramientas necesarias para crear sitios web que puedan aparecer en la Búsqueda de Google. Dado que ambos recursos comparten parte del contenido y algunos objetivos y, además, no ofrecen toda la información que nos gustaría sobre cómo crear sitios web seguros y fáciles de usar, la Academia para webmasters dejará de estar disponible y retiraremos el archivo PDF de la versión antigua de la Guía SEO para principiantes.   La Guía SEO para principiantes actualizada sustituirá tanto a su versión antigua como a la Academia para webmasters. Esta nueva versión renueva el contenido de la anterior y añade secciones que tratan de por qué es necesaria la optimización en buscadores, cómo añadir etiquetas de datos estructurados y cómo diseñar sitios web optimizados para móviles. Esta nueva guía está disponible a partir de hoy en nueve idiomas (alemán, español, francés, inglés, italiano, japonés, portugués, ruso y turco) y pronto se publicará en 16 idiomas más.Consulta la nueva Guía SEO para principiantes y danos tu opinión. Si tienes alguna pregunta, no dudes en formularla en nuestros foros de ayuda para webmasters. Escrito por Abhas Tripathi y publicado por Joan Ortiz, equipo de Calidad de Búsqueda.

Real-world data in PageSpeed Insights

Google herramientas para webmaster - Mié, 10/01/2018 - 10:08

PageSpeed Insights provides information about how well a page adheres to a set of best practices. In the past, these recommendations were presented without the context of how fast the page performed in the real world, which made it hard to understand when it was appropriate to apply these optimizations. Today, we’re announcing that PageSpeed Insights will use data from the Chrome User Experience Report to make better recommendations for developers and the optimization score has been tuned to be more aligned with the real-world data.

The PSI report now has several different elements:

  • The Speed score categorizes a page as being Fast, Average, or Slow. This is determined by looking at the median value of two metrics: First Contentful Paint (FCP) and DOM Content Loaded (DCL). If both metrics are in the top one-third of their category, the page is considered fast.
  • The Optimization score categorizes a page as being Good, Medium, or Low by estimating its performance headroom. The calculation assumes that a developer wants to keep the same appearance and functionality of the page.
  • The Page Load Distributions section presents how this page’s FCP and DCL events are distributed in the data set. These events are categorized as Fast (top third), Average (middle third), and Slow (bottom third) by comparing to all events in the Chrome User Experience Report.
  • The Page Stats section describes the round trips required to load the page’s render-blocking resources, the total bytes used by the page, and how it compares to the median number of round trips and bytes used in the dataset. It can indicate if the page might be faster if the developer modifies the appearance and functionality of the page.
  • Optimization Suggestions is a list of best practices that could be applied to this page. If the page is fast, these suggestions are hidden by default, as the page is already in the top third of all pages in the data set.

For more details on these changes, see About PageSpeed Insights. As always, if you have any questions or feedback, please visit our forums and please remember to include the URL that is being evaluated.

Posted by Mushan Yang (杨沐杉) and Xiangyu Luo (罗翔宇), Software Engineers

Introducing the new Search Console

Google herramientas para webmaster - Lun, 08/01/2018 - 20:58

A few months ago we released a beta version of a new Search Console experience to a limited number of users. We are now starting to release this beta version to all users of Search Console, so that everyone can explore this simplified process of optimizing a website's presence on Google Search. The functionality will include Search performance, Index Coverage, AMP status, and Job posting reports. We will send a message once your site is ready in the new Search Console.

We started by adding some of the most popular functionality in the new Search Console (which can now be used in your day-to-day flow of addressing these topics). We are not done yet, so over the course of the year the new Search Console (beta) will continue to add functionality from the classic Search Console. Until the new Search Console is complete, both versions will live side-by-side and will be easily interconnected via links in the navigation bar, so you can use both.

The new Search Console was rebuilt from the ground up by surfacing the most actionable insights and creating an interaction model which guides you through the process of fixing any pending issues. We’ve also added ability to share reports within your own organization in order to simplify internal collaboration.

Search Performance: with 16 months of data!

If you've been a fan of Search Analytics, you'll love the new Search Performance report. Over the years, users have been consistent in asking us for more data in Search Analytics. With the new report, you'll have 16 months of data, to make analyzing longer-term trends easier and enable year-over-year comparisons. In the near future, this data will also be available via the Search Console API.

Index Coverage: a comprehensive view on Google's indexing

The updated Index Coverage report gives you insight into the indexing of URLs from your website. It shows correctly indexed URLs, warnings about potential issues, and reasons why Google isn't indexing some URLs. The report is built on our new Issue tracking functionality that alerts you when new issues are detected and helps you monitor their fix.

So how does that work?

  1. When you drill down into a specific issue you will see a sample of URLs from your site. Clicking on error URLs brings up the page details with links to diagnostic-tools that help you understand what is the source of the problem.
  2. Fixing Search issues often involves multiple teams within a company. Giving the right people access to information about the current status, or about issues that have come up there, is critical to improving an implementation quickly. Now, within most reports in the new Search Console, you can do that with the share button on top of the report which will create a shareable link to the report. Once things are resolved, you can disable sharing just as easily.
  3. The new Search Console can also help you confirm that you've resolved an issue, and help us to update our index accordingly. To do this, select a flagged issue, and click validate fix. Google will then crawl and reprocess the affected URLs with a higher priority, helping your site to get back on track faster than ever.
  4. The Index Coverage report works best for sites that submit sitemap files. Sitemap files are a great way to let search engines know about new and updated URLs. Once you've submitted a sitemap file, you can now use the sitemap filter over the Index Coverage data, so that you're able to focus on an exact list of URLs.
Search Enhancements: improve your AMP and Job Postings pages

The new Search Console is also aimed at helping you implement Search Enhancements such as AMP and Job Postings (more to come). These reports provide details into the specific errors and warnings that Google identified for these topics. In addition to the functionally described in the index coverage report, we augmented the reports with two extra features:

  • The first feature is aimed at providing faster feedback in the process of fixing an issue. This is achieved by running several instantaneous tests once you click the validate fix button. If your pages don’t pass this test we provide you with an immediate notification, otherwise we go ahead and reprocess the rest of the affected pages.
  • The second new feature is aimed at providing positive feedback during the fix process by expanding the validation log with a list of URLs that were identified as fixed (in addition to URLs that failed the validation or might still be pending).

Similar to the AMP report, the new Search Console provides a Job postings report. If you have jobs listings on your website, you may be eligible to have those shown directly through Google for Jobs (currently only available in certain locations).

Feedback welcome

We couldn’t have gotten so far without the ongoing feedback from our diligent trusted testers (we plan to share more on how their feedback helped us dramatically improve Search Console). However, your continued feedback is critical for us: if there's something you find confusing or wrong, or if there's something you really like, please let us know through the feedback feature in the sidebar. Also note that the mobile experience in the new Search Console is still a work in progress.

We want to end this blog sharing an encouraging response we got from a user who has been testing the new Search Console recently:

"The UX of new Search Console is clean and well laid out, everything is where we expect it to be. I can even kick-off validation of my fixes and get email notifications with the result. It’s been a massive help in fixing up some pesky AMP errors and warnings that were affecting pages on our site. On top of all this, the Search Analytics report now extends to 16 months of data which is a total game changer for us" - Noah Szubski, Chief Product Officer, DailyMail.com

Are there any other tools that would make your life as a webmaster easier? Let us know in the comments here, and feel free to jump into our webmaster help forums to discuss your ideas with others!

Posted by John Mueller, Ofir Roval and Hillel Maoz

Introducing the new Webmaster Video Series

Google herramientas para webmaster - Jue, 21/12/2017 - 18:35

Google has a broad range of resources to help you better understand your website and improve its performance. This Webmaster Central Blog, the Help Center, the Webmaster forum, and the recently released Search Engine Optimization (SEO) Starter Guide are just a few.

We also have a YouTube channel, for answers to your questions in video format. To help with short & to the point answers to specific questions, we've just launched a new series, which we call SEO Snippets.

In this series of short videos, the Google team will be answering some of the webmaster and SEO questions that we regularly see on the Webmaster Central Help Forum. From 404 errors, how and when crawling works, a site's URL structure, to duplicate content, we'll have something here for you.

Check out the links shared in the videos to get more helpful webmaster information, drop by our help forum and subscribe to our YouTube channel for more tips and insights!

Posted by Aurora Morales, Google Search Outreach

Introducing Rich Results & the Rich Results Testing Tool

Google herramientas para webmaster - Mar, 19/12/2017 - 15:56

Over the years, the different ways you can choose to highlight your website's content in search has grown dramatically. In the past, we've called these rich snippets, rich cards, or enriched results. Going forward - to simplify the terminology -  our documentation will use the name "rich results" for all of them. Additionally, we're introducing a new rich results testing tool to make diagnosing your pages' structured data easier.

The new testing tool focuses on the structured data types that are eligible to be shown as rich results. It allows you to test all data sources on your pages, such as JSON-LD (which we recommend), Microdata, or RDFa. The new tool provides a more accurate reflection of the page’s appearance on Search and includes improved handling for Structured Data found on dynamically loaded content. The tests for Recipes, Jobs, Movies, and Courses are currently supported -- but this is just a first step, we plan on expanding over time.

Testing a page is easy: just open the testing tool, enter a URL, and review the output. If there are issues, the tool will highlight the invalid code in the page source. If you're working with others on this page, the share-icon on the bottom-right lets you do that quickly. You can also use preview button to view all the different rich results the page is eligible for. And … once you're happy with the result, use Submit To Google to fetch & index this page for search.

Want to get started with rich snippets rich results? Check out our guides for marking up your content. Feel free to drop by our Webmaster Help forums should you have any questions or get stuck; the awesome experts there can often help resolve issues and give you tips in no time!

Posted by Shachar Pooyae, Software Engineer

#NoHacked 3.0: Fixing common hack cases

Google herramientas para webmaster - Mar, 19/12/2017 - 00:05
So far on #NoHacked, we have shared some tips on detection and prevention. Now that you are able to detect hack attack, we would like to introduce some common hacking techniques and guides on how to fix them!

  • Fixing the Cloaked Keywords and Links Hack The cloaked keywords and link hack automatically creates many pages with nonsensical sentences, links, and images. These pages sometimes contain basic template elements from the original site, so at first glance, the pages might look like normal parts of the target site until you read the content. In this type of attack, hackers usually use cloaking techniques to hide the malicious content and make the injected page appear as part of the original site or a 404 error page.
  • Fixing the Gibberish Hack The gibberish hack automatically creates many pages with nonsensical sentences filled with keywords on the target site. Hackers do this so the hacked pages show up in Google Search. Then, when people try to visit these pages, they'll be redirected to an unrelated page, like a porn site for example.
  • Fixing the Japanese Keywords Hack The Japanese keywords hack typically creates new pages with Japanese text on the target site in randomly generated directory names. These pages are monetized using affiliate links to stores selling fake brand merchandise and then shown in Google search. Sometimes the accounts of the hackers get added in Search Console as site owners.

Lastly, after you clean your site and fix the problem, make sure to file for a reconsideration request to have our teams review your site.

If you have any questions, post your questions on our Webmaster Help Forums!

.blgimg1 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } .blgimg2 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } .blgimg3 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } .blgimg4 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; }

Getting your site ready for mobile-first indexing

Google herramientas para webmaster - Lun, 18/12/2017 - 15:08
When we announced almost a year ago that we're experimenting with mobile-first indexing, we said we'd update publishers about our progress, something that we've done the past few months through public talks in office hours on Hangouts on Air and at conferences like Pubcon.

To recap, currently our crawling, indexing, and ranking systems typically look at the desktop version of a page's content, which may cause issues for mobile searchers when that version is vastly different from the mobile version. Mobile-first indexing means that we'll use the mobile version of the content for indexing and ranking, to better help our – primarily mobile – users find what they're looking for. Webmasters will see significantly increased crawling by Smartphone Googlebot, and the snippets in the results, as well as the content on the Google cache pages, will be from the mobile version of the pages.

As we said, sites that make use of responsive web design and correctly implement dynamic serving (that include all of the desktop content and markup) generally don't have to do anything. Here are some extra tips that help ensure a site is ready for mobile-first indexing:
  • Make sure the mobile version of the site also has the important, high-quality content. This includes text, images (with alt-attributes), and videos - in the usual crawlable and indexable formats.
  • Structured data is important for indexing and search features that users love: it should be both on the mobile and desktop version of the site. Ensure URLs within the structured data are updated to the mobile version on the mobile pages.
  • Metadata should be present on both versions of the site. It provides hints about the content on a page for indexing and serving. For example, make sure that titles and meta descriptions are equivalent across both versions of all pages on the site.
  • No changes are necessary for interlinking with separate mobile URLs (m.-dot sites). For sites using separate mobile URLs, keep the existing link rel=canonical and link rel=alternate elements between these versions.
  • Check hreflang links on separate mobile URLs. When using link rel=hreflang elements for internationalization, link between mobile and desktop URLs separately. Your mobile URLs' hreflang should point to the other language/region versions on other mobile URLs, and similarly link desktop with other desktop URLs using hreflang link elements there.
  • Ensure the servers hosting the site have enough capacity to handle potentially increased crawl rate. This doesn't affect sites that use responsive web design and dynamic serving, only sites where the mobile version is on a separate host, such as m.example.com.
We will be evaluating sites independently on their readiness for mobile-first indexing based on the above criteria and transitioning them when ready. This process has already started for a handful of sites and is closely being monitored by the search team.

We continue to be cautious with rolling out mobile-first indexing. We believe taking this slowly will help webmasters get their sites ready for mobile users, and because of that, we currently don't have a timeline for when it's going to be completed. If you have any questions, drop by our Webmaster forums or our public events.

Posted by Gary

#NoHacked 3.0: Tips on prevention

Google herramientas para webmaster - Vie, 15/12/2017 - 14:01
Last week on #NoHacked, we have shared on hack detection and the reasons why you might get hacked. This week we focus on prevention and here are some tips for you!
  • Be mindful of your sources! Be very careful of a free premium theme/plugin!
    You probably have heard about free premium plugins! If you've ever stumbled upon a site offering you plugins you normally have to purchase for free, be very careful. Many hackers lure you in by copying a popular plugin and then add backdoors or malware that will allow them to access your site. Read more about a similar case on the Sucuri blog. Additionally, even legit good quality plugins and themes can become dangerous if :

    • you do not update them as soon as a new version becomes available
    • the developer of said theme or plugin does not update them, and they become old over time

In any case, keeping all your site's software modern and updated is essential in keeping hackers out of your website.
  • Botnet in wordpress A botnetis a cluster of machines, devices, or websites under the control of a third party often used to commit malicious acts, such as operating spam campaigns, clickbots, or DDoS. It's difficult to detect if your site has been infected by a botnet because there are often no specific changes to your site. However, your site's reputation, resources, and data are at risk if your site is in a botnet. Learn more about botnets, how to detect them, and how they can affect your site at Botnet in wordpress and joomla article.
As usual if you have any questions post on our Webmaster Help Forums for help from the friendly community and see you next week!
.blgimg1 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; float: left; } .blgimg2 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; float: left; } .blgimg3 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } .blgimg4 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; }

A revamped SEO Starter Guide

Google herramientas para webmaster - Mar, 12/12/2017 - 18:30
There are lots of resources out there to create great websites. Website owners often ask Google what our recommended practices are to make sure great websites are search-engine-friendly. Traditionally, our resources for beginners were the SEO Starter Guide and the Webmaster Academy. To help webmasters create modern, search-engine-friendly websites, we’re announcing today the launch of a new, updated SEO Starter Guide.

The traditional SEO Starter Guide lists best practices that make it easier for search engines to crawl, index and understand content on websites. The Webmaster Academy has the information and tools to teach webmasters how to create a site and have it found in Google Search. Since these two resources have some overlapping purpose and content, and could be more exhaustive on some aspects of creating a user friendly and safe website, we’re deprecating the Webmaster Academy and removing the old SEO Starter Guide PDF.

The updated SEO Starter Guide will replace both the old Starter Guide and the Webmaster Academy. The updated version builds on top of the previously available document, and has additional sections on the need for search engine optimization, adding structured data markup and building mobile-friendly websites.
This new Guide is available in nine languages (English, German, Spanish, French, Italian, Japanese, Portuguese, Russian and Turkish) starting today, and we’ll be adding sixteen more languages very soon.

Go check out the new SEO Starter Guide, and let us know what you think about it.

For any questions, feel free to drop by our Webmaster Help Forums!

Posted by Abhas Tripathi, Search Quality Strategist

#NoHacked 3.0: How do I know if my site is hacked?

Google herramientas para webmaster - Vie, 08/12/2017 - 20:54
Last week #NoHacked is back on our G+ and Twitter channels! #NoHacked is our social campaign which aims to bring awareness about hacking attacks and offer tips on how to keep your sites safe from hackers. This time we would like to start sharing content from #NoHacked campaign on this blog in your local language!

Why do sites get hacked? Hackers havedifferent motives for compromising a website, and hack attacks can be very different, so they are not always easily detected. Here are some tips which will help you in detecting hacked sites!

  • Getting started:

    Start with our guide "How do I know if my site is hacked?" if you've received a security alert from Google or another party. This guide will walk you through basic steps to check for any signs of compromises on your site.

  • Understand the alert on Google Search:

    At Google, we have different processes to deal with hacking scenarios. Scanning tools will often detect malware, but they can miss some spamming hacks. A clean verdict from Safe Browsing does not mean that you haven't been hacked to distribute spam.

    • If you ever see "This site may be hacked", your site may have been hacked to display spam. Essentially, your site has been hijacked to serve some free advertising.
    • If you see"This site may harm your computer" beneath the site URL then we think the site you're about to visit might allow programs to install malicious software on your computer.
    • If you see a big red screen before your site, that can mean a variety of things:
      • If you see "The site ahead contains malware", Google has detected that your site distributes malware.
      • If you see "The site ahead contains harmful programs", then the site has been flagged for distributing unwanted software.
      • "Deceptive site ahead" warnings indicate that your site may be serving phishing or social engineering. Your site could have been hacked to do any of these things.
  • Malvertising vs Hack:

    Malvertising happens when your site loads a bad ad. It may make it seem as though your site has been hacked, perhaps by redirecting your visitors, but in fact is just an ad behaving badly.

  • Open redirects: check if your site is enabling open redirects

    Hackers might want to take advantage of a good site to mask their URLs. One way they do this is by using open redirects, which allow them to use your site to redirect users to any URL of their choice. You can read more here!

  • Mobile check: make sure to view your site from a mobile browser in incognito mode. Check for bad mobile ad networks.

    Sometimes bad content like ads or other third-party elements unknowingly redirect mobile users. This behavior can easily escape detection because it's only visible from certain browsers. Be sure to check that the mobile and desktop versions of your site show the same content.

  • Use Search Console and get message:

    Search Console is a tool that Google uses to communicate with you about your website. It also includes many other tools that can help you improve and manage your website. Make sure you have your site verified in Search Console even if you aren't a primary developer on your site. The alerts and messages in Search Console will let you know if Google has detected any critical errors on your site.

If you're still unable to find any signs of a hack, ask a security expert or post on our Webmaster Help Forums for a second look.

The #NoHacked campaign will run for the next 3 weeks. Follow us on our G+ and Twitter channels or look out for the content in this blog as we will be posting summary for each week right here at the beginning of each week! Stay safe meanwhile!

.blgimg img { width: 100%; border: 0; margin: 0; padding: 10px 0 0 0; }

Renderizar páginas de rastreo con AJAX

Blog oficial de Google para Webmasters - Lun, 04/12/2017 - 19:26

El esquema de rastreo con AJAX se diseñó con el objetivo de que el robot de Google pudiera acceder a las páginas web basadas en JavaScript. Como hemos anunciado anteriormente, tenemos previsto desactivarlo. Con el tiempo, los ingenieros de Google han mejorado de forma significativa cómo se renderiza JavaScript para que el robot de Google pueda rastrearlo. Gracias a estos avances, a partir del segundo trimestre del 2018 Google se encargará de renderizar estas páginas, en lugar de que tengan que hacerlo los sitios web. En resumen, dejaremos de usar el esquema de rastreo con AJAX. El esquema de rastreo con AJAX admite páginas que contienen "#!" en la URL o bien una metaetiqueta "fragment" y, a continuación, los rastrea incluyendo "?_escaped_fragment_=" en la URL. Esa versión con caracteres de escape, creada por el sitio web, tiene que ser una versión completa o equivalente de la página. Con este cambio, el robot de Google renderizará la URL que contiene #! directamente, por lo que no será necesario que el propietario del sitio web proporcione una versión renderizada de la página. Estas URL se seguirán incluyendo en los resultados de búsqueda. Esperamos que la mayoría de los sitios web que se rastrean con AJAX no experimenten cambios importantes con esta actualización. Los webmasters pueden comprobar sus páginas siguiendo las instrucciones a continuación. Enviaremos notificaciones a los sitios web que detectemos que pueden tener problemas. Si tu sitio web usa URLs que contienen #! o metaetiquetas "fragment", te recomendamos que hagas lo siguiente: ● Verifica la propiedad del sitio web en Google Search Console para acceder a sus herramientas y para que Google te pueda enviar notificaciones sobre los problemas que encuentre.
● Haz pruebas con la herramienta Explorar como Google de Search Console. Compara los resultados de la URL que contiene #! y la URL con caracteres de escape para ver las diferencias. Repite este proceso con cualquier parte del sitio web que sea notablemente distinta. Consulta nuestra documentación para desarrolladores para obtener más información sobre las API admitidas y, si es necesario, consulta nuestra guía de depuración.
● Con la función para inspeccionar elementos de Chrome, comprueba que los enlaces utilizan elementos HTML <a> e incluyen rel=nofollow donde corresponde (por ejemplo, en contenido generado por usuarios).
● Con la función para inspeccionar elementos de Chrome, comprueba el título de la página y la metaetiqueta "description", si hay metaetiquetas "robot" y otros metadatos. Comprueba también que los datos estructurados estén disponibles en la página renderizada.
● Si el contenido debe indexarse en la búsqueda, el contenido creado con Flash, Silverlight u otras tecnologías basadas en complementos debe convertirse a JavaScript o HTML "normal". Esperamos que este cambio facilite el proceso para rastrear tu sitio web y evite en la medida de lo posible que tengas que renderizar páginas. Si tienes cualquier pregunta o comentario, no dudes en consultar nuestros foros de ayuda para webmasters o unirte a nuestro grupo de trabajo de sitios web de JavaScript. Escrito por John Mueller, Google Suiza, publicado por Joan Ortiz, equipo de calidad de búsqueda.

Rendering AJAX-crawling pages

Google herramientas para webmaster - Lun, 04/12/2017 - 15:57

The AJAX crawling scheme was introduced as a way of making JavaScript-based webpages accessible to Googlebot, and we've previously announced our plans to turn it down. Over time, Google engineers have significantly improved rendering of JavaScript for Googlebot. Given these advances, in the second quarter of 2018, we'll be switching to rendering these pages on Google's side, rather than on requiring that sites do this themselves. In short, we'll no longer be using the AJAX crawling scheme.

As a reminder, the AJAX crawling scheme accepts pages with either a "#!" in the URL or a "fragment meta tag" on them, and then crawls them with an "?_escaped_fragment_=" in the URL. That escaped version needs to be a fully-rendered and/or equivalent version of the page, created by the website itself.

With this change, Googlebot will render the #! URL directly, making it unnecessary for the website owner to provide a rendered version of the page. We'll continue to support these URLs in our search results.

We expect that most AJAX-crawling websites won't see significant changes with this update. Webmasters can double-check their pages as detailed below, and we'll be sending notifications to any sites with potential issues.

If your site is currently using either #! URLs or the fragment meta tag, we recommend:

  • Verify ownership of the website in Google Search Console to gain access to the tools there, and to allow Google to notify you of any issues that might be found.
  • Test with Search Console's Fetch & Render. Compare the results of the #! URL and the escaped URL to see any differences. Do this for any significantly different part of the website. Check our developer documentation for more information on supported APIs, and see our debugging guide when needed.
  • Use Chrome's Inspect Element to confirm that links use "a" HTML elements and include a rel=nofollow where appropriate (for example, in user-generated content)
  • Use Chrome's Inspect Element to check the page's title and description meta tag, any robots meta tag, and other meta data. Also check that any structured data is available on the rendered page.
  • Content in Flash, Silverlight, or other plugin-based technologies needs to be converted to either JavaScript or "normal" HTML, if their content should be indexed in search.

We hope that this change makes it a bit easier for your website, and reduces the need to render pages on your end. Should you have any questions or comments, feel free to drop by our webmaster help forums, or to join our JavaScript sites working group.

Posted by John Mueller, Google Switzerland

Recordatorio sobre el marcado de eventos

Blog oficial de Google para Webmasters - Mar, 28/11/2017 - 15:50
Últimamente hemos recibido comentarios de usuarios que afirman haber visto elementos que no son eventos, como cupones, en los resultados de búsqueda en que aparecen fragmentos de eventos.Esta situación confunde mucho a los usuarios y, además, infringe nuestras directrices, a las que hemos añadido más información sobre el tema. En concreto, ¿cuál es el problema?Hemos observado que muchos editores de sitios web que ofrecen cupones describen sus ofertas con el marcado de eventos. Aunque usar un cupón de descuento puede ser algo muy especial, no por eso hay que considerar los cupones como si fueran eventos o saleEvents. Cuando se describe algo que no es un evento con el marcado de eventos, se crea una mala experiencia de usuario, porque se mostrará un resultado enriquecido de algo que sucederá en un momento determinado, aunque no haya ningún evento real.A continuación se muestran algunos ejemplos que ilustran el problema: Dado que en estos casos se generan experiencias de usuario engañosas, es posible que realicemos acciones manuales para corregirlas. Si tu sitio web se ve afectado por alguna de estas medidas, se mostrará una notificación en tu cuenta de Search Console. Si realizamos una acción manual en tu sitio web, es posible que no se utilice el marcado de datos estructurados de todo el sitio web en los resultados de búsqueda. Si bien en esta entrada del blog destacamos específicamente el caso de los cupones, esta información también se aplica a cualquier otro elemento que no sea un evento y que esté marcado como tal; en realidad, se aplica al hecho de etiquetar elementos con un tipo de marcado que no sea el adecuado.Para obtener más información, consulta la documentación para desarrolladores o, si tienes más preguntas, visita nuestro foro para webmasters.
Escrito por Sven Naumann, del equipo de Confianza y seguridad de la Búsqueda

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer