Google Webmaster Tools Verification Issues

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
12/11/2012 3:11:39 PM
Gravatar
Total Posts 5

Google Webmaster Tools Verification Issues

Hi,

I ran into some troubles verifying Google Webmaster Tools with my website today, and while I managed to resolve them myself, I was wondering why certain things are implemented as they are.

I basically used the Analytics async controls as they were installed in the original skin, with the <portal:AnalyticsAsyncTopScript id="analyticsTop" runat="server" /> and <portal:AnalyticsAsyncBottomScript ID="analyticsBottom" runat="server" /> at the top and bottom of the body, as outlined in this article.

Even though the code generated by these controls is the same as the one given by Google Analytics, the ownership verification process of Google Webmaster Tools has some issues with this (Google Analytics itself worked fine). The support article indicates that the GA snippet should be added at the end of the header and not in the body or just before the body as it is setup in the skin. Besides the default position in the layout file, I tried placing the controls outside the body, inside it and even both in the header, but Webmaster tools failed to verify on all occasions. The analytics account code is correct and that is not the issue. I eventually managed to verify using two separate ways, the first being an html meta tag provided by GWT as well as by removing the analytics controls and replacing them with Google's snippet. I would prefer using the mojoPortal controls though.

I'm just curious if anyone else ran into this issue.

I noticed that pretty much everything in mojoPortal has a precise and deliberate purpose (which I like), so I was also wondering why the controls were not implemented as per Google's specifications, in the header (I know there must be a very good reason). Thank you.

Regards.

12/11/2012 3:34:37 PM
Gravatar
Total Posts 18439

Re: Google Webmaster Tools Verification Issues

Off the top of my head I can't remember for sure why we don't put the top script in the head but I do seem to remember there was a reason. They only say it is ideal to have it in the head not required.

Generally I recommend the html file upload way of verifying webmaster tools. That way it is independent of needing a (meaningless) meta tag in the layout.master file which you may forget if you make a new skin or use more than one skin on your site or have any static html pages in your site that are not part of mojoPortal.  It also makes the verification almost immediate.

Hope that helps,

Joe

You must sign in to post in the forums. This thread is closed to new posts.