Help Center SEO When Zendesk Owns Your Rankings

If your help center lives at yourcompany.zendesk.com, the pages that rank are on a hostname you don’t own. That subdomain belongs to the vendor’s domain; your brand in the URL doesn’t change who controls it. Every feature explainer, integration guide and use-case article that earns rankings there is an asset you can’t fully manage, can’t report on alongside your own site, and may not be able to take with you if you leave. The fix has two parts: host-map a subdomain of your own domain as the minimum move, and selectively migrate your highest-value, acquisition-oriented articles onto your main site, while leaving operational support content where it is.

What the vendor subdomain costs you

yourcompany.zendesk.com is a subdomain of zendesk.com. “yourcompany” is a label on the vendor’s domain, not a domain you control. That has practical consequences:

• Reporting. A Search Console Domain property for yourcompany.com, which Google’s help on adding a property says aggregates data for all subdomains, protocols and subpaths of your domain, doesn’t include the vendor’s hostname. Your help center’s search performance sits outside your main reporting.
• Portability. If you change help desk vendors, the old URLs live on a domain you don’t control, and whether they can redirect to their new home depends on the vendor, not on you.
• Integration. Articles on a separate vendor hostname can’t share your site’s navigation and internal links the way native pages can.

Don’t overstate it into “subdomains never work.” A subdomain on a domain you own, such as help.yourcompany.com, is your property. The problem is specifically the vendor-owned hostname.

Triage: acquisition content versus retention content

Not every help article deserves to move. Sort by what the content is for.

Acquisition content targets real search demand from people who aren’t customers yet or are evaluating: feature explainers, integration and setup guides, use-case walkthroughs and how-to articles that match real queries. This is the content whose value you want on your own site.

Retention and operational content serves existing customers looking for account help: billing, password resets, plan changes, account settings. It targets little external search demand, and moving it adds maintenance for little ranking benefit. It can stay on the platform.

A middle category causes the arguments: content that serves customers but ranks for outside demand anyway, such as a troubleshooting guide for a feature that prospects also search before buying. Let the search data decide, not the article’s stated purpose. The test: if a page earns meaningful non-branded search impressions, treat it as acquisition content and move it, even though it doubles as support.

To run the triage, pull the help center’s page-level analytics and any search data you have, and sort articles by search entrances and impressions. Articles bringing in non-logged-in visitors from search are acquisition candidates; articles viewed by signed-in customers and not reached from search are operational. Check query intent too: an article that ranks for a feature or integration term is acquisition content even if its traffic is low today.

Host mapping is the minimum fix

Zendesk’s mechanism for serving your help center on your own domain is host mapping. Its host mapping article sets out what it does and doesn’t do:

• Subdomains only. Host mapping can only be done to subdomains, such as support.yourcompany.com, not to a root domain such as yourcompany.com.
• A CNAME record. You create a CNAME record at your domain registrar pointing the subdomain to your Zendesk subdomain.
• SSL is required. Zendesk offers a free certificate from Let’s Encrypt, included with the plan, or you can upload your own. The article warns that without a Zendesk-provisioned certificate or your own, help center traffic on the host-mapped domain will result in SSL errors. Set up the certificate as part of the same change.
• Scope. Host mapping only changes the external-facing URL of your help center; it doesn’t change the URL of the sign-in page or the agent interface.

Once host-mapped, the help center sits on a subdomain of your domain, so your Search Console Domain property covers it, and you can add a URL-prefix property for the help subdomain if you want its data on its own.

When full integration is the stronger option

Host mapping puts the content on your domain, but it still lives in a separate property with the platform’s templates and navigation. The stronger version is full integration: bringing the high-value articles into your own site’s CMS, where they share your navigation, templates and internal links and can link to and from your product pages.

The trade-off is effort against payoff. Host mapping is a DNS change and a certificate. Full integration is a content migration and an ongoing editorial commitment. A practical rule: host-map the whole help center first, then fully migrate the acquisition articles whose ranking and conversion value justify living on your main site.

Migration mechanics

When you move an article from the platform to your main site, the mechanics decide how cleanly it transfers:

• Redirect the old URLs. Google’s guide to consolidating duplicate URLs lists redirects as a strong signal that the redirect target should become canonical. Point each old help URL to its new page with a permanent redirect, where the platform allows it.
• Use canonical only where the content exists. The same guide lists rel=”canonical” as a strong signal too, but it only makes sense when equivalent content exists at the target. If the content isn’t on your site yet, you aren’t canonicalizing; you’re migrating, and you need the real page plus the redirect.
• Improve the content as you move it. These were written as support docs. Rewrite them as acquisition content, with the context and depth a prospect needs. Moving a thin article unchanged just relocates a thin article.

The community forum variant

The same issue applies to a community forum on a vendor subdomain. User-generated threads can build long-tail coverage over time, and on a vendor hostname that coverage sits outside your domain. Host-mapping works for the community too: map it onto a subdomain you own, if the platform supports it.

Frequently asked questions

Does having my brand name in the vendor subdomain help?

It identifies you to readers, but the hostname still belongs to the vendor’s domain. Serving the content on a subdomain of a domain you own, through host mapping or migration, is what brings it under your control and into your own Search Console Domain property.

Should I move billing and password-reset articles too?

Not as a rule. Those are operational pages with little outside search demand; moving them adds maintenance for little benefit. Migrate acquisition content and leave operational support on the platform.