Post has attachment
Una nueva herramienta de Google para testear el rendimiento en dispositivos móviles.
https://testmysite.thinkwithgoogle.com/intl/es-419
Es cinco veces más probable que un usuario abandone un sitio si este no está optimizado para dispositivos móviles.
Más info: https://www.thinkwithgoogle.com/intl/es-419/articles/mobile-page-speed-load-time.html
https://testmysite.thinkwithgoogle.com/intl/es-419
Es cinco veces más probable que un usuario abandone un sitio si este no está optimizado para dispositivos móviles.
Más info: https://www.thinkwithgoogle.com/intl/es-419/articles/mobile-page-speed-load-time.html
Buenas tardes,
hemos detectado que han hackeado nuestra web a través de nuestro blog en wordpress, enlazado en la página.
En un principio solucionamos el problema actualizando el blog, eliminando los comentarios spam y volviendo crear el archivo sitemap.xml (aparecían 2000 página indexadas).
El Sábado 12/08 aparecía correctamente la página (sin caracteres Japoneses). Hoy hemos vuelto a detectar problemas en los comentarios de blog y hemos vuelto a solucionarlo.
El problema es el título de la página al buscar en google aparece nuevamente en caracteres Japoneses.
Hemos comprobado el sitemap.xml y parece que está correcto (solo aparece una página indexada).
¿Cómo podemos solucionar el problema de los caracteres Japonenes?
¿Hay alguna forma de volver a indexar para solucionar el problema?
hemos detectado que han hackeado nuestra web a través de nuestro blog en wordpress, enlazado en la página.
En un principio solucionamos el problema actualizando el blog, eliminando los comentarios spam y volviendo crear el archivo sitemap.xml (aparecían 2000 página indexadas).
El Sábado 12/08 aparecía correctamente la página (sin caracteres Japoneses). Hoy hemos vuelto a detectar problemas en los comentarios de blog y hemos vuelto a solucionarlo.
El problema es el título de la página al buscar en google aparece nuevamente en caracteres Japoneses.
Hemos comprobado el sitemap.xml y parece que está correcto (solo aparece una página indexada).
¿Cómo podemos solucionar el problema de los caracteres Japonenes?
¿Hay alguna forma de volver a indexar para solucionar el problema?
Post has attachment
hola. me sancionaron mi web ibsa.es hace aproximadamente 6 meses con puro spam ya que tenia enlaces salientes de baja calidad. Desde entonces he reconstruido la web siguiendo a rajatabla las directrices para webmaster de google eliminando estos enlaces y aprendiendo la leccion jaja He pedido unas 6 veces la reconsideracion y la respuesta es casi automatica en 2 o 3 dias. Es decir estoy seguro que no entra ni en revision manual.
sabeis si cuando una web entra en puro spam por mas que se arregle queda marcada un tiempo?
Es decir como un tiempo de castigo hasta que google vuelva a plantearse reincluirla??
gracias
sabeis si cuando una web entra en puro spam por mas que se arregle queda marcada un tiempo?
Es decir como un tiempo de castigo hasta que google vuelva a plantearse reincluirla??
gracias
Buenas....tengo una duda sobre una cuenta de correo que cree y que me quieren quitar. ¿Alguien puede asesorarme?...saludos
Post has attachment
Las páginas AMP siguen ganando terreno en los resultados móviles.
A configurarlas y colocar Analytics para hacerles seguimiento!
https://webmasters.googleblog.com/2016/08/amp-your-content-preview-of-amped.html
A configurarlas y colocar Analytics para hacerles seguimiento!
https://webmasters.googleblog.com/2016/08/amp-your-content-preview-of-amped.html
Post has attachment
301 Redirects Rules Change: What You Need to Know for SEO
https://moz.com/blog/301-redirection-rules-for-seo
https://moz.com/blog/301-redirection-rules-for-seo
Buenas tardes.....Cordial Saludo,
Me podrian ayudar con la siguiente inquietud?
Revisando mi cuenta de Search Console > Indice de Google > Recursos Bloqueados:
Me aparecen 8 Paginas con recursos bloqueados
Me pueden explicar un poco que significa esto, que problemas me puede estar generando y como lo puedo solucionar???
Les agradezco mucho su valiosa ayuda,
Andres
Me podrian ayudar con la siguiente inquietud?
Revisando mi cuenta de Search Console > Indice de Google > Recursos Bloqueados:
Me aparecen 8 Paginas con recursos bloqueados
Me pueden explicar un poco que significa esto, que problemas me puede estar generando y como lo puedo solucionar???
Les agradezco mucho su valiosa ayuda,
Andres
Buenas Tardes, me podrian ayudar en una inquietud?
Tengo un dominio para Estados Unidos > us.misitio.co
y tengo una tienda virtual para ese dominio ( la cual hicimos a traves de Shopify ) cuando un visitante llega a cierto paso, el dominio > us.misitio.co se convierte en checkout.shopify.com
Deberia crear una cuenta de Search Console para ambos o solo para > us.misitio.com??
Les agradezco su valiosa ayuda,
Tengo un dominio para Estados Unidos > us.misitio.co
y tengo una tienda virtual para ese dominio ( la cual hicimos a traves de Shopify ) cuando un visitante llega a cierto paso, el dominio > us.misitio.co se convierte en checkout.shopify.com
Deberia crear una cuenta de Search Console para ambos o solo para > us.misitio.com??
Les agradezco su valiosa ayuda,
Post has shared content
Algunas preguntas frecuentes de editores de noticias (Google News) que migran sus sitios a HTTPS.
We collected a few questions from news publishers related to HTTP to HTTPS site moves, but some of the answers are relevant to all webmasters who are considering going secure.
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?
A: No.
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 max-age. Monitor your traffic both from users and other clients, and also dependants' performance, such as ads.
3. Slowly increase the HSTS max-age.
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 .
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?
A: No.
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 max-age. Monitor your traffic both from users and other clients, and also dependants' performance, such as ads.
3. Slowly increase the HSTS max-age.
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 .
hola soy de Colombia tengo un juego que se llama clans of clans alguien a logrado meterse a mi juego y jugar por mi como hago para poder eliminar esa persona que se a metido a mi juego ya cambie contraseñas y nada siguen manejando mi juego
Wait while more posts are being loaded