I’m encountering an issue with verifying a sub-domain for one of my clients, and I’m hoping to get some guidance. The sub-domain in question, which is hosted on HubSpot. We’re trying to verify it in Google Search Console to track user data, but we’ve hit a roadblock.
Initially, we attempted to verify the sub-domain by placing the HTML tag provided by Google inside the sub-domain’s code. However, this method didn’t yield success. When we reached out to the support team, we were informed that we needed to place the HTML tag on every page of the sub-domain to effectively track users.
This solution seems impractical, as it would require placing the tag on numerous pages, which could be cumbersome and time-consuming. I believe there must be a more efficient way to verify the sub-domain without resorting to this method.
Has anyone else encountered a similar issue when verifying sub-domains hosted on HubSpot? If so, how did you overcome it?
Any insights or suggestions would be greatly appreciated.
When you say subdomain, I am going to assume you are not talking about www subdomain and this might just be for landing pages or a blog. Is that correct? If so, especially with landing pages, there is not a home page so I don’t think the HTML tag verification will work. If you have a google analytics/tag manager account specific to the subdomain you may be able to verify with that. Otherwise, if it’s only for landing pages, I would typically setup a client to verify their domain at the DNS level verification as the subdomain, if it is landing pages, might not all be indexed, thus there might not be as much value in the search console data for those as you would with the www subdomain.
The sub-domain is hosted on hubspot. Let me share the response we got from hubspot support team.
Thank you for reaching out to Hubspot support. My name’s Ingrid and I’ll be happy to assist here. From your screenshots I can see that the verification method you selected is an HTML upload ; I see that you’re using the HTML tag verification instead. After reviewing the code for your KB page, I don’t find the tag inserted either and I see that Hubspot displays a warning that such changes won’t be applied to your KB articles. That is expected though, as it’s not possible to add global snippets of code to the header of knowledge base pages but you can only add code to the site header HTML of specific knowledge base articles by following the instructions outlined in this knowledge base document: Create and Customize Knowledge Base Articles .
That said, my suggestion here would be to add the code to each specific KB article, or choose a different verification method from Google Search Console as Hubspot seems to be working as designed at this point.
I hope this answers your questions. Please don’t hesitate to reach back out in case you have any further concerns.
I would try one of the other verification methods such as DNS or Google Analytics/Tag Manager to verify the domain if you are unable to add the code to the service hub. Unfortunately I don’t work much in the service hub so I don’t know if other options such as the design manager or adding global header code can be done like it can for the web pages and landing pages.
Do you have the Google analytics code installed on the pages of this subdomain? If so, you should be able to verify via that prompt in your search console.
Like @Ben_M I don’t have much experience with Service Hub and setting up the HS knowledge base but wouldn’t you just follow the steps outline here and simply integrate with GTM? That way the GTM code gets added to all your HubSpot content.
Not with Google search console specific but we’re having issues with verifying a sub domain at the DNS level verification. because HubSpot requires CNAME input as authentication method, but as a sub domain we cant add this (we dont own the domain, only the sub domain). HubSpot support havent previously been helpful with this issue but now it’s impacting our sender reputation with increased spam reports due to the email sender being auto displayed by HubSpot.