SEO - the title

Another pretty good one is All in One SEO Pack… these plugins are fairly popular on WordPress. Yoast is the most popular.

If you get a chance to see if they are able to be added with a JavaScript snippet. Let us know!

And if you have meta tags you’d like us to add on the Hub level, I’m happy to push to get those added. Just let me know which ones other than keywords that you’d like to see.

1 Like

had a chance - the answer is yes …

I would like this added because good SEO improves a site’s searchability and helps developers find what they are looking for. I’d be happy to help investigate this further if that makes it more likely to happen.

UPDATE: Bummed to report that you have to have an open source project to build Yoast into your platform. They have a page of requirements for adding their tool here:


I definitely agree about the SEO. That’s why I want to first make sure meta tags on Hubs are looking good before we expand beyond there.

Dang, sad to hear that.

1 Like

I was trying to research plugins but it looks like most are wordpress - you guys can’t use any wordpress plugins right? Are there any general requirements that knowing would help customers find tools you guys could consider including?

Correct. We are a totally different tech stack than Wordpress, so it wouldn’t be possible to use them.

It’s kind of hard to say, for example some of the integrations we have are Google Analytics, Google Tag Manager, Segment. These are all platforms that we can integrate by including their JavaScript library in your Hub and adding the user specific credentials to it. So it would likely be another SaaS type platform that has an easy to integrate JavaScript library.

I’m not totally sure how this would work for SEO though, since most of those platforms are more on the analytics side.

I have to research this and get back - I think you do need to improve the SEO offering and this detail about Google integration is great. I will see what they have and suggest something.

I am back! Can we do something to allow use of Google Search Console?

I can look into it! I’ll probably need to try it out on my own site for testing.

1 Like

I can’t get any of the verification methods to work for Google Search Console. It looks like at least one of those choices should work though so I’m not sure what’s going on.

Any update on search console?

Based on some work we did to fix this (Add Google Site Verification), you should be able to verify now with Google Tag Manager. Can you try the verification again and share how it goes on that topic link?

The code is displaying an extra tag I didn’t add. Is it adding it by itself, or did it not properly remove a tag that got added previously?

Welcome to TeleSign&#x27;s Enterprise documentation portal. Here you can find everything you need to get started with Enterpris..." id="og:description" data-react-helmet="true"/><link rel="shortcut icon" href=""/><link rel="preload" href="/_/assets/fonts/icons.woff2?v=5.0.6" as="font" type="font/woff2" crossorigin="anonymous"/><link href="/_/assets/css/semantic.min.css" rel="preload" as="style"/><link href="/_/assets/css/custom-theme.34277.css" rel="preload" as="style"/><link href="/_/assets/css/custom-file.34277.css" rel="preload" as="style"/></head><body><noscript><iframe src="//" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript><noscript><iframe src="//" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript><link rel="stylesheet" href="/_/assets/css/custom-theme.34277.css"/><link rel="stylesheet" href="/_/assets/css/custom-file.34277.css"/><style type="text/css"> @font-face { font-family: 'Icons'; src: url('/_/assets/fonts/icons.woff2?v=5.0.6') format('woff2'), url('/_/assets/fonts/icons.woff?v=5.0.6') format('woff'); font-style: normal; font-weight: normal; font-variant: normal; text-decoration: inherit; text-transform: none;


<!DOCTYPE html><html lang="en-US"><head><script async="" type="text/javascript">(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= ''+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-TNGJT5N');</script><script async="" id="gtm-script" type="text/javascript">(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= ''+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-N6767WJ');</script><script defer="" async="" src="/_/assets/js/bugsnag.min.js"></script><script type="text/javascript">try { var _vwo_code=(function(){ var account_id=408739, settings_tolerance=2000, library_tolerance=2500, use_existing_jquery=false, is_spa=1, /* DO NOT EDIT BELOW THIS LINE */

See there are two tags in there instead of one. Only GTM-N6767WJ ought to be in there.

I’ll check on that. Are you seeing data coming through for your’s?

The other tag we added looks like it’s working, but we don’t want to have an extra tag in there, that could mess things up potentially.

Any update? The extra tag could mess up our analytics data.

Hey @einnes!

I talked to Chris, one of our frontend engineers, and he confirmed it should not mess up your analytics data. It looks like it is one of our tags in there.

Why would Stoplight include an analytics tag of their own? That seems mildly invasive.

Can you please remove your tag?

The analytics tags allow us visibility into the browsers viewing the published hub pages so that we can ensure that changes are properly tested before launching new features. Removing our analytics tags is something that is already bundled within our enterprise package. We haven’t included it in self service options yet although there’s a feature request in for it.

I can pass along that you would like it removed and see what the team says.