Profile cover photo
Profile photo
Aaseesh Marina
1,848 followers
1,848 followers
About
Aaseesh's posts

Post has shared content
Whether you're using a Content Management System or e-commerce platform to build your site, one of the easiest things you can do to keep your site safe is to keep up with updates.
Set auto-updates where possible, and sign up for security announcements when available. Don't waste time when updates are available. Leaving your site vulnerable means it's only a matter of time before it's compromised. #NoHacked

Here are a few security resources from common CMSs and e-commerce platforms:

Magento→ https://goo.gl/ZUcoz4
Joomla→ https://goo.gl/oUH7l0
Drupal→ https://goo.gl/7UJZZo
Wordpress→ https://goo.gl/eTGXT4
WooCommerce→ https://goo.gl/8TaiHP
Photo

Post has attachment
Please join us for a Webmaster Office Hours Hangout in Hindi/English at 11:00 AM tomorrow[Thursday, Nov 24]

You may add the questions here in the comment section, we'll answer them during the session.



Post has shared content
How can Google Search Console help you #AMPlify your site? #AcceleratedMobilePages

Find answers here: https://goo.gl/PtyKBH
Photo

Post has shared content
Check out a Q&A where Google Anti-abuse Research Lead +Elie Bursztein discusses some of the research that goes into making Gmail safe.

Post has shared content
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 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 .

Post has shared content
We're hosting this month's office hours next Tuesday at 11:00 AM. Please add your questions to the Q&A app in the event.
All Indian Webmasters are invited to join us for a Webmaster Central hangout at 11:00 IST next Tuesday :)

Add your questions to this event page, this session is open to anything webmaster related like crawling, indexing, mobile sites, internationalization, duplicate content, Sitemaps, Webmaster Tools, pagination, duplicate content, multi-lingual/multi-regional sites, etc.

This is a Hangout on Air on Google+. It works best with a webcam + headset. You can find out more about Hangouts and how to participate at https://sites.google.com/site/webmasterhelpforum/en/office-hours

Feel free to drop by - we welcome webmasters of all levels!

Post has shared content
Have a problem with a Google product? Here is how forum escalations work

+John Mueller explained how escalations work in the official +Google Webmasters help forum:

And usually what happens there is that the top contributors, rising stars, the more active people in the forums, they'll take these threads. And if they can't figure it out on their own they'll it escalated to us and, someone on Google side will get back to them and say, oh, they have to do this, this or, this. Or maybe we'll go to the thread directly and say, oh, you need to do kind of this. Or maybe we'll just take that escalation, say, OK we'll fix this on our side manually, with the manual web spam team to kind of make sure that this problem is solved.

In my experience, that's pretty much how it works in other Google Product Help Forums as well.

Here are some tips:

1. Clearly explain your issue, including all the relevant details

(which details are relevant will vary from product to product - for Webmasters include the website URL, for Hangouts include the app or your browser details, etc)

2. If a Top Contributor, Rising Star or other expert asks for more details provide them

You may not realize which details are important. And even if you feel like you provided all the necessary information, the forum experts may ask for clarification to be sure they fully understand what you are reporting.

3. Remember people are trying to help, so try not to take out your anger on them

Top Contributors are not Google Employees, and we definitely didn't cause the problem you are experiencing.

4. Don't expect a direct response from a Google employee

In my experience Googlers rarely respond directly to user questions. Count on the forum experts to relay your question or report a bug to staff.

Fnd all the official Google Product help forums, from AdSense to YouTube

https://productforums.google.com/forum/#!home

There is also a link to each help forum from the relevant help center. Look at the top right above any Google help article for the Forum or Community link.

+Barry Schwartz has the discussion clip here:
https://www.seroundtable.com/google-explains-how-webmaster-forums-escalation-works-22067.html

Post has shared content
+Google Webmasters Structured Data Testing Tool gets new design, moves to new address #structureddata #semanticweb   #SEO . Wonder why they double index it ;) Perhaps they forgot to tag it semantically :0 (which they did, not a bit of structured data on the page, actually not even a rel=canonical) +John Mueller BTW, isn't the color a bit Bingish?
Photo

Post has shared content
Check out our 2015 Webspam Report → https://goo.gl/3tI6Lv

Our Webspam Report highlights webspam insights we gathered in 2015 on global trends, our spam-fighting efforts, and how we're working with webmasters and users like you to make the web ecosystem better.
Photo

Post has shared content
नमस्ते,

हमें येह घोषणा कर्ते हुए खुशि हैं कि हम विशेष रूप से हिन्दि वेबमास्टर्स के लिये hangouts का आयोजन कर रहें हैं। आप यहाँ गूगल से संबंधित अपने सभी सवाल पूछ सकते हैं।

Hangouts ऑन एयर के बारे में अधिक जानकारी के लिए, यहां क्लिक करें: https://support.google.com/plus/answer/2553119?hl=hi
Wait while more posts are being loaded