TL;DR
Third-party help center platforms create a domain authority split where your support content builds equity for their subdomain, not yours. Zendesk, Intercom, and Freshdesk articles ranking for your product questions means traffic bypasses your domain entirely. The fix requires evaluating whether the canonical content should live on your domain versus the support platform, not just accepting the default architecture.
The Conversation
Tomas, product marketing manager, B2B SaaS, 500+ help center articles on Zendesk: I’m trying to understand why our competitors show up when people search for our product’s features. Like, someone searches “how to use [our feature name]” and a competitor’s comparison page outranks our own help documentation.
SDC SEO Brain: Where does your help documentation live?
Tomas: Zendesk. We have a help center at support.ourcompany.zendesk.com.
SDC SEO Brain: That’s your problem. Your help content is building authority for Zendesk’s domain, not yours. When someone searches for your feature, Google sees that your main domain has limited content about it, while your Zendesk subdomain (which Google may not strongly associate with your brand) has the details but less overall authority than your main site.
Tomas: But it’s our subdomain. support.ourcompany.zendesk.com is clearly connected to us.
SDC SEO Brain: It’s not a subdomain of your domain. It’s a subdomain of zendesk.com. Google sees ourcompany.zendesk.com as part of the zendesk.com domain family, not as part of yourcompany.com. Your articles are building zendesk.com’s domain authority, not yours.
Tomas: Wait, really? I assumed since it has our company name in the URL…
SDC SEO Brain: URL structure doesn’t determine domain ownership in Google’s eyes. The domain is zendesk.com. Everything before the first dot is a subdomain of that domain. Your content equity flows to Zendesk’s overall domain authority pool.
Tomas: So every help article we publish makes Zendesk stronger, not us?
SDC SEO Brain: Essentially, yes. And this matters because your help content often targets valuable product-related keywords. “How to set up [feature],” “troubleshooting [product error],” “[product name] integration with [other tool].” These are bottom-funnel queries from people actively using or evaluating your product. You’re giving those queries to a third-party domain.
Tomas: We have 500 articles. Some of them rank pretty well.
SDC SEO Brain: Check which domain they rank on. Go to Google, search for one of your help article topics, and look at the URL in the results. Is it showing your Zendesk URL or are competitors ranking for those same topics on their own domains?
Tomas: Let me search… “how to connect [our product] to Salesforce.” Okay, the first result is a competitor’s integration guide on their main domain. Our Zendesk article is on page 2.
SDC SEO Brain: There’s your answer. Your competitor put their integration content on their own domain and it outranks your Zendesk content. They own that traffic, you don’t.
Tomas: So what do we do? Migrate 500 articles to our main site?
SDC SEO Brain: Not necessarily all 500, but likely the important ones. You need to categorize your help content by SEO value. Some articles are truly support content that existing customers need: account settings, password resets, billing questions. Those can stay on Zendesk because they’re not competitive keywords. Other articles are essentially product marketing: feature explanations, use cases, integration guides, onboarding tutorials. Those should live on your domain.
Tomas: How do I figure out which is which?
SDC SEO Brain: Search volume and intent. Run your article titles and topics through a keyword research tool. Articles targeting keywords with meaningful search volume and discovery intent belong on your domain. Articles targeting zero-volume operational queries can stay on Zendesk.
Tomas: Can’t we just use a custom domain on Zendesk? Like help.ourcompany.com?
SDC SEO Brain: Zendesk does support custom domains. That’s the minimum viable fix. With help.ourcompany.com, the content builds authority for your domain instead of Zendesk’s. It’s not as good as full site integration, but it’s dramatically better than the current setup.
Tomas: What’s the difference between a custom domain and full site integration?
SDC SEO Brain: Custom domain means your help center is still a separate property, just hosted on your domain. Full integration means your help content lives in the same CMS as your marketing site, shares navigation, templates, and internal linking structure. Full integration is stronger for SEO because it’s truly part of your site. Custom domain is a middle ground.
Tomas: Full integration sounds like a huge project.
SDC SEO Brain: It is. Custom domain is a configuration change. Full integration is a content migration plus CMS development. Most companies do custom domain as the immediate fix and then selectively migrate high-value content to their main site over time.
Tomas: What about canonical tags? Could we canonicalize the Zendesk content to our main site?
SDC SEO Brain: Only if you have equivalent content on your main site. Canonical tags point to the preferred version of duplicate or near-duplicate content. If the content only exists on Zendesk, there’s nothing to canonicalize to. You’d need to create the content on your site first, then canonical from Zendesk, which is essentially migration.
Tomas: Our competitors seem to have this figured out. Their help content ranks better.
SDC SEO Brain: Check their architecture. Do they use Zendesk or a similar platform? If so, are they using a custom domain? Or did they build their help center on their own domain entirely?
Tomas: Let me look… competitor A has docs.competitor.com and it looks like their own design, not Zendesk. Competitor B has a /help section on their main domain.
SDC SEO Brain: Both of those architectures keep the SEO value. Competitor A has a subdomain of their own domain, which Google associates with their main site. Competitor B has full integration. Either approach beats third-party platform subdomains.
Tomas: If we set up a custom domain, do we lose anything from the existing Zendesk URLs?
SDC SEO Brain: You’ll need redirects from the old zendesk.com URLs to the new custom domain URLs. Zendesk supports this in their domain configuration. Anyone who bookmarked or linked to your old help articles will be redirected. The transition should preserve whatever authority those articles had.
Tomas: How long does the custom domain setup take?
SDC SEO Brain: From a technical standpoint, days. You configure the domain in Zendesk, update DNS settings, and enable HTTPS. The delay is usually in getting IT or DNS access, not the actual configuration. Most teams can do this in under a week if they prioritize it.
Tomas: And then our rankings improve?
SDC SEO Brain: Over time. You’re changing the domain, which means Google needs to recrawl and reassociate the content with your domain. Expect a few weeks of fluctuation, then stabilization. The improvement comes from future authority building on your domain rather than instant ranking jumps.
Tomas: What should we do about the 500 existing articles? Any immediate cleanup?
SDC SEO Brain: Audit for quality and overlap first. Help centers often have redundant articles, outdated content, and thin pages that add nothing. Clean those up before or during the domain migration. Fewer, better articles outperform hundreds of mediocre ones.
Tomas: We definitely have some outdated stuff. Old feature documentation for things we’ve sunset.
SDC SEO Brain: Remove or redirect those. Outdated content that doesn’t match your current product creates user confusion and potential quality signals. If someone finds a help article about a deprecated feature, they’ll bounce, which doesn’t help anyone.
Tomas: For the high-value articles that should be on our main site, do we migrate them or create new versions?
SDC SEO Brain: If the existing article is good, migrate and redirect. If the existing article is just a quick FAQ answer, create a more comprehensive version on your main site that deserves to rank. Use the migration as an opportunity to improve content, not just move mediocre content to a better domain.
Tomas: That sounds like a lot of content work.
SDC SEO Brain: It is. But it’s content work with direct SEO and business impact. Every comprehensive integration guide or feature tutorial on your domain is an asset that ranks, attracts leads, and builds authority. The same content on Zendesk is a support resource that maybe helps existing customers but doesn’t grow your business.
Tomas: Should we keep anything on Zendesk after migration?
SDC SEO Brain: Keep true support content: billing questions, account management, troubleshooting for logged-in users. These are operational necessities that don’t need SEO value. They serve existing customers who are already in your product and using help search. The distinction is acquisition content (belongs on your domain) versus retention content (can stay on support platform).
Tomas: One more thing. We also have a community forum on Zendesk. Same problem?
SDC SEO Brain: Potentially worse. Community forums generate user-created content that often ranks for long-tail queries. Every forum post is building Zendesk’s authority. If your community is active and generating valuable content, it should definitely be on a custom domain at minimum.
Tomas: Got it. Custom domain as the immediate fix, selective migration for high-value content, cleanup of outdated stuff.
SDC SEO Brain: Exactly. And track the impact. Before migration, document which articles rank and for what keywords. After migration, monitor if rankings transfer and improve. This gives you data for the investment case of further migration work.
FAQ
Q: Why doesn’t my Zendesk help center build SEO authority for my company?
A: Zendesk help centers use yourcompany.zendesk.com URLs by default. In Google’s view, this is a subdomain of zendesk.com, not your domain. All the authority your content builds flows to Zendesk’s domain, not yours. Your company name in the URL doesn’t change domain ownership.
Q: Should I migrate all help center content to my main site?
A: Not necessarily. Categorize content by SEO value. Feature explanations, integration guides, and use case documentation should live on your domain because they target valuable keywords. True support content like billing FAQs and account settings can stay on the support platform since they serve existing customers, not SEO.
Q: What’s the difference between a custom domain and full site integration?
A: Custom domain (help.yourcompany.com) keeps your help center as a separate property but hosted on your domain. Full integration means help content lives in your main CMS with shared navigation and internal linking. Custom domain is faster to implement; full integration is stronger for SEO.
Q: Will I lose rankings when switching to a custom domain?
A: Expect temporary fluctuation during the transition. Set up redirects from old Zendesk URLs to new custom domain URLs to preserve existing link equity and user bookmarks. Rankings should stabilize within a few weeks, then improve as content builds authority on your domain.
Q: What about community forums on support platforms?
A: Community forums have the same problem, potentially worse. User-generated forum content often ranks for long-tail queries, building third-party domain authority. Active forums generating valuable content should be on a custom domain at minimum.
Summary
Third-party help center platforms split your SEO authority across domains. Zendesk, Intercom, and Freshdesk subdomains build their domain authority, not yours. Your feature tutorials and integration guides are acquisition content ranking on someone else’s property.
Custom domain is the minimum viable fix. Configuring help.yourcompany.com takes days and redirects authority to your domain. Full integration with your main CMS is stronger but requires significant development investment.
Categorize content by SEO value. Feature explanations, use cases, and integration guides target valuable keywords and should live on your domain. Billing FAQs and account settings serve existing customers and can stay on the support platform.
Use migration as an improvement opportunity. Don’t just move mediocre content to a better domain. Create comprehensive versions of high-value topics that deserve to rank. Fewer, better articles outperform hundreds of thin help center pages.
Sources
- Zendesk: Custom domain configuration documentation
- Google Search Central: Subdomain and domain authority signals
- Intercom: Knowledge base SEO settings