Welcome to the Q&A Forum
Browse the forum for helpful insights and fresh discussions about all things SEO.
I think thats a good idea to try and comment them out to see if it makes a difference.
Oh wow, 45 slider images?? That's def got to be hurting your search rankings! Hopefully you've found some one better to manage your site. Let me know if you need any help, I've worked in the industry for quite some time now.
Good luck, and let us know if it still doesn't work after commenting.
Why not use Moz Local? https://moz.com/local
Keep in mind that Google displays search results based on your search patterns. Try using https://duckduckgo.com and using the prefix !g before your search term to see unfiltered results ( !g Emerald Coast Carpet Cleaning ). This will search for your query on Google anonymously. Also, be sure to log out of your Google account(s) prior to using it.
You could always block DESKTOP content spiders from crawling the mobile portion of your site using your robots.txt file. Then, to make sure your mobile site gets indexed properly, make sure to add a link on your desktop site somewhere so that a mobile content crawler can still go through it. This should take care of your issue.
I'm using Magento Community 1.7
Upon running the Moz Pro site crawler, I noticed that I received quite a bit of duplicate titles along with 302 redirects (which is our site creating a temporary 302 to our "cookies not enabled" page). How would I get around the crawler being redirected to this page? I've never ran across this issue before, despite using the crawler with sites that use the same framework as the one thats affected. Any ideas?
As long as you don't have a novel in your bio that have been copied/pasted throughout, I wouldn't worry about it too much. As Prestashop said, the unique content within each site will most likely cause the crawlers to consider each one unique. However, if its more a resume rather than a bio, I'd play it safe and reword it for each.
Hmm, there's definitely way too much duplication going on in your .htaccess file. What exactly are the following pages used for?
Each rewrite section seems to be set up for the pages above, including the last one for index.html. I presume it has something to do with supercache? I'd try consolidating the .htaccess file, as there are a lot of duplicate rules that can be combined. For example, the URIs, request method, etc are all the same in each section. However, in order to figure out what to consolidate and remove, we need to figure out what each of the rewrite pages are doing for your site.
You could always try commenting out each rewrite block at a time to see if its needed or not. I'm guessing your .htaccess has something to do with why Google cant access your site properly.
For the redirected URLs that GWMT is throwing a 404 error for, can you access them directly in your browser? I'd double check a few random links that Google is saying doesnt exist, and then from there I'd look into the .htaccess. It would be helpful if you could provide us with the .htaccess file here.
You also need to factor in extra load times using images as opposed to a CSS-initiated background. Although it is important to have anchor text for images on your site, I dont think that you should go out of your way to purposely make the site less usable in exchange for a negligible amount of rank increase. After all, it doesn't matter how well you rank if it doesnt create conversions for you due to slow load times, incompatibilities, etc. I generally like to tell my clients to keep the end-user in mind first, as implementing this type of mindset will usually automatically help you with SEO (quicker load times, better quality content, etc). Just make sure to use alt/anchors for the actual images on your site, and you'll be good. I'd definitely recommend using CSS over hard-coding a bg image. It's better practice, and will decrease load times on all your pages.
Hmm, I'm not too familiar with Oracle ATG. Is that Java-based? I mainly work with PHP. To answer your question, yes it does return a clean 301 redirect response for crawlers.
I came across this link on Oracles doc for ATG. It looks like you could possibly use the URL templates to accomplish this. Do the URLs that you plan on redirecting have a commonality between them? (ie. switching 100 URLs from http://example.com/example1/* to http://example.com/*). If so, you can possibly separate them into these common "groups" and develop a redirect for each group instead of each URL.
That sounds like a great plan. Furthermore, on the high-performance sites that you have the higher CF plan on, you'll also get Railgun. I've had a chance to utilize CF's railgun technology through a partnership with a hosting company, and i can say that its quite effective with even dynamic content (unlike most CDNs). Furthermore, it may decrease your overall technology budget by mitigating the need for a separate CDN. Visit https://www.cloudflare.com/railgun to read more about it.
Good luck!
You should have migrated the sold domains "authority" to the new site using Google Webmaster Tools. Doing this would have transferred all of your SEO to the new site. However, since this was not done (or 301 redirect each link to the new site), i'm sorry to say that you'll need to start over 
I've been using Cloudflare for about 2 years now with 10+ sites (including 2-3 that receive 20k+ unique visitors monthly), and to be quite honest I have not found a DNS provider that provides the same level of optimization and security as them. I've tried some of the top companies in the DNS industry (including Dyn, which I still use for enterprise DNS redundancy & fail-over), however they all seem to be missing functionality that I regularly use within Cloudflare, which I ended up moving back within a week. Furthermore, performance-wise, I've yet to find a service that can match site load times accomplished with an optimized CF setup.
It does take some time & experimentation to dial in the optimization/security settings within Cloudflare for your particular site(s)/technology, however once dialed in, everything runs quite well. My favorite features are the DNS-based smart redirects (you can create URL patterns which will automatically redirect pages for you at the DNS-level.) along with their DNS-based firewall. The latter stops malicious attacks at the DNS level (it can cut off the hacker/spammer at the DNS level before it hits your serrver, as long as the user accesses your site using the protected domain), and has been quite effective for us for the past 2 years. Furthermore, Cloudflare reduces load times in various ways (caching at the DNS-level, JS/CSS minified, etc). They also allow you to integrate apps such as Google Analytics without having to directly add the JS code into your site.
In regards to Cloudflare optimization, after implementing the proper settings for one of my clients ecommerce sites, we've seen load times decrease by about 3 seconds on avg. Like I've said, it does take some time to get the optimal settings for your specific site, however I feel that its definitely worth it.
I'd recommend subscribing to CloudFlare Pro ($20/month for first site, and $5 for each one afterwards), as it comes with the WAP firewall at the DNS-level (which works almost TOO well. Sometimes detects actions on the backend as SQL injection due to the query patterns), along with SSL support (really cool, you can have SSL connected at the DNS-level). I believe you also get a LOT more slots for the smart redirects, which is invaluable to me. I know I probably sound like I work for CF, but to be quite honest I've experienced nothing but great service from them. The one time I had an issue, I contacted them on Twitter (which they actively check) and they replied/fixed the issue for me within a few minutes.
Hope this helps you make a more informative decision. Feel free to send me a private message if you have any other specific questions. I'll see what I can do to help out.
What language is the new site coded in? You can always create a redirector within the new sites code all at once using a database query and amending a URL. This will prevent you from having to create such a large .htaccess file for redirects. I may be able to help you if you let me know which language you're using along with providing examples of the type of redirects you'd like to setup.