https://support.google.com/webmasters/answer/35179?hl=en
Verification is the process of proving that you own the site or app that you claim to own. We need to confirm ownership because once you are verified for a site or app you have access to its private Google Search data, and can affect how Google Search crawls it.
...
If you use Google Analytics to track your site's traffic, you can verify your site using the Google Analytics tracking code associated with the site. To do this, you must have "edit" permission for the web property whose tracking code is used by that page. Also, your tracking code must use the new asynchronous snippet.
To verify ownership using Google Analytics, choose Google Analytics in the verification details page for your site, and follow the instructions shown.
When copying Google Analytics code:
Put the tracking code in the <head> section, not the <body> section, of your page. If you do not, verification will fail.
I see, thanks. I verified for Webmaster Tools with an HTML file, I don't think verifying with Analytics was always an option. Strange that it's more finicky about it being in the <head> than Analytics itself is.Webmastertools and analytics are tightly knit at google. And to use webmaster tools your site has to be verified.
The recommended from google is asynchronous snippet in your head tag
You can literally put any part between the <script> tags and it should pick it up. I'd recommend "google-analytics" because it will work with both the old ga.js and the new universal analytics.jsWhat string did you guys add to blacklist Google Analytics? ga.js?
Yeah, I will release a fix for that shortly. The add-on does disable itself for attachments, but only after it has checked the output for HTML. I will reverse the order there.Hello, for some reason "Defer JS" breaks my downloads of big attachments. We host audio interviews so the files be near 100mb sometimes.
"ErrorException: Fatal Error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 95454275 bytes) - library/Jrahmy/DeferJs/Listener.php:30"
Is there a way to get around this?
A unique string on its own line should have worked. Something like 'adBanner1'. If your script has other dependencies they would need to be blacklisted too, but it appears to be standalone.Also, it breaks this javascript for my banners but when I try to put in a unique string it still does not work. Any ideas?
This fixes a bug where attachments were loaded into memory to check for HTML content. This could result in fatal PHP errors for large attachments. Thanks to @orange7 for reporting this issue.
The query strings are used for cache busting in XenForo. If you remove them (and have far-future expires headers for your static resources, which you absolutely should), then your users will not be able to receive proper updates to these resources.Please can you add option Remove query strings from static resources?
It should function. Not sure why it's saying that on your site though. I can confirm that it's working fine in my forums (with PHP 5.6.12).
Still working for me. If you link me to your site, I can double check whether or not it's working. If it's not working, that'd be down to add-on conflicts or other strange issues though.Does this still function? Installed and Google PageSpeed and my own inspection shows JS still loading closer to first.
Typo. I meant PHP 5.6.21 (for some reason I totally forgotten to upgrade to PHP 5.6.22).I can confirm that it's working fine in my forums (with PHP 5.6.12).
It's working just fine in your site though. Although you seemed to have disabled Compress HTML Source add-on.Sure here you go https://www.axiomgamers.com/
We use essential cookies to make this site work, and optional cookies to enhance your experience.