As bybe points out the issue is that almost all content served up by raw.github.com is sent down as a text file - that way the content is rendered in plain text in your browser without any other applications or issues getting in the way. Otherwise you would get into the situation where attempting to view a .js file might cause the browser to attempt to run ...
Something like this should do the trick: _gaq.push(['_setCustomVar', 1, // This custom var is set to slot #1. Required parameter. 'Company', // The name acts as a kind of category for the user activity. Required parameter. $_GET['company_name'], // This value of the custom variable. Required ...
This will not hurt you. Having your site do different things depending on environmental factors (such as the type of device) is common and ok to do. You only have an issue when you intentionally serve different content to search engines than to users and that clearly is not the case here.
By the HTTP protocol, clause 7.2.1, “Any HTTP/1.1 message containing an entity-body SHOULD include a Content-Type header field defining the media type of that body. If and only if the media type is not given by a Content-Type field, the recipient MAY attempt to guess the media type via inspection of its content and/or the name extension(s) of the URI used to ...
According to a Matt Cutts 2012 post, sites with a lot of ads "above-the-fold", meaning before the content, can be penalized. However, a normal amount of ads and a content rich site won't suffer. However, they recently made updates for mobile search and said to avoid download apps pop-ups or you'll lose mobile search rankings. Reference : ...
Top 50 recent answers are included