Welcome to the Q&A Forum

So I wanted to get everyone's opinion. Have a client in online retail on ASP and their developers built a mobile site a while back before we took the client on. For the sake of this post, just assume, resources are limited anddevelopers are not good (constantly break things we request to get fixed). They never installed analytics on the mobile site, so all I have to go off of is referral data on the main stores GA account for m.example.com However if I look to see what is indexed by doing site:m.example.com am not seeing many pages. The mobile site has a ton of internal links in GWT and am questioning its negative impact as there are no canonicals, no mobile sitemap present. In the ideal world, I would implement proper Mobile SEO practices but given the resources of no dev budget and devs not being good, I was thinking about noindexing the mobile site since I can RDP into the site and access robots. Thoughts?

I have an ecommerce site where https is being crawled for some pages. Wondering if the below solution will fix the issue www.example.com will be my domain In the nav there is a login page www.example.com/login which is redirecting to the https://www.example.com/login If I just disallowed /login in the robots file wouldn't it not follow the redirect and index that stuff? The redirect part is what I am questioning.

So I have a store which has been around for a while and is custom built on ASP.net.  Store has thousands of sku's and at least a few hundred subcategories. Have been tackling a bunch of the onsite issues and for categories which have more than 6 products in them, there are multiple pages and a view all present. Example.com/category example.com/category?PageIndex=2 example.com/category?PageIndex=3 example.com/category?PageIndex=4 example.com/category?viewall=True As well as the following for every page example.com/category?PageIndex=2&viewall=True So I know how I wish to handle the pagination/canoncial issue as per google's suggestions you do it to the view all or they have the rel=next/prev. But my question is google says if view all is present they should already do a good job at ranking the view all version. Well in the rankings, there are a lot of page1 variations showing. So once this is implementated, is it safe to assume that I will see a drop?  Feel like if it was a brand new site it is easy but for something this old and established, it could cause some decent harm which at the current time we are already tackling a massive list of issues which in the long haul will improve it. Looking for some insight for someone who has dealt with ASP.net and this specific area. thanks
Sean