Zendesk Guide SEO
A help centre that ranks deflects tickets from people who never visit your site. Most Zendesk Guide SEO problems are entirely fixable.
Why Zendesk Guide SEO is worth doing
People do not go to your help centre and search. They go to Google and search. The query is "how do I cancel my acme subscription", and whoever ranks for it answers the question. If that is not you, it's a forum, a competitor comparison page, or nobody, and the customer files a ticket.
Help centre SEO is the cheapest ticket deflection there is, because you're writing the articles anyway. The only extra work is making them findable.
Titles and structure, the part you control most
Write article titles as the question the customer types. "Cancelling your subscription" beats "Subscription cancellation policy", and both beat "Billing FAQ #4".
One article, one question. The single most common Guide mistake is the mega-article: a 4,000 word page covering setup, billing, troubleshooting and limits, which ranks for nothing because it is specifically about nothing. Split it. Five focused articles will out-rank one comprehensive one, every time.
Structure inside the article matters too. The H1 is the article title, generated by the theme, so use H2 and H3 for your sections and never skip levels for visual effect. Answer the question in the first paragraph, then explain. Search engines and impatient humans want the same thing here, which is convenient.
Sections and categories are your site architecture. A flat pile of two hundred uncategorised articles gives search engines no signal about what your help centre is about, and gives readers no way to browse.
The traps that are specific to Guide
These are the ones that cost real traffic and that nobody warns you about.
Multibrand and multiple help centres. If you run several brands, each has its own help centre. Publishing the same article in more than one is duplicate content, and search engines will pick one and discount the rest. Pick a canonical home per article, or write genuinely different content per brand.
Localisation. Guide supports multiple languages, and translated variants need hreflang handling so Google understands they're alternates rather than duplicates. Check your theme actually emits it. Many custom themes quietly dropped it during a redesign.
Restricted content. Articles visible only to signed-in users cannot be indexed. That is correct behaviour. It also means half your knowledge base may be invisible to search without anyone realising, so audit which articles are public and confirm the ones that should be public actually are.
Theme rendering. If a theme renders article content through JavaScript after page load, indexing gets unreliable. View the page source, not the inspector, and confirm your article body text is actually in the HTML.
Search results pages. Internal help centre search result URLs should not be indexed. They are thin, infinite and duplicative. Check your robots handling.
Canonicals, sitemaps and the technical floor
Guide generates a sitemap for your help centre automatically. Submit it in Google Search Console, which you should be doing anyway, since Search Console is the only place you will see what your help centre actually ranks for.
Canonical tags are the part people get wrong. If the same content genuinely exists on your marketing site and in your help centre, decide which one is canonical and point the other at it. Do not leave both live and hope. And if your help centre is on a Zendesk subdomain rather than your own domain, understand that you are building authority for a hostname you do not fully own. Hosting the help centre on a subdomain of your own domain is generally better for the long game, though it is a migration, not a checkbox.
Two more basics. Article URLs in Guide include a numeric ID, which is fine and not worth fighting. Page speed matters, and heavy themes with large hero images are the usual culprit, so measure before you blame anything else.
Internal linking, the lever nobody pulls
Link from every article to the two or three related articles a reader is most likely to need next. Not an automated related-articles block, which everyone ignores, but real links inside the prose where the reference makes sense.
This does three things at once. It spreads authority across your knowledge base rather than concentrating it on the handful of articles that happen to have external links. It keeps readers on your help centre instead of back on Google. And it helps search engines understand which articles are important, because internal links are a ranking signal you fully control.
While you're in there, check your help centre search isn't the only navigation you offer. A reader who arrives from Google on a deep article needs a route to the rest.
Measuring it honestly
Track three things and ignore the rest. Impressions and clicks in Search Console, which tells you what people are finding you for. Ticket volume by topic, which tells you what they aren't finding. And the gap between them, which is your content roadmap.
The most useful report in support is the list of queries where you get impressions but almost no clicks. Those are questions people ask, where your article exists and fails to look like the answer. Rewriting the title is usually a fifteen minute job with a measurable outcome, which is rare enough in SEO to be worth doing first.
Frequently asked questions
Does help centre SEO differ from normal SEO?
Only in the constraints. Zendesk help center SEO is the same discipline with less control over URLs and templates, and Zendesk knowledge base SEO wins come mostly from titles, internal links and putting the help centre on your own domain.
Does Zendesk Guide SEO include a sitemap?
Yes, automatically for your help centre. Submit it in Google Search Console so you can see what is indexed and what's ranking.
Should my help centre be on my own domain?
Generally yes, on a subdomain of your own domain rather than a Zendesk hostname. It is a migration rather than a setting, so plan redirects carefully.
Why are my help centre articles not indexed?
Most often they are restricted to signed-in users, or the theme renders content via JavaScript. Check the page source as a signed-out visitor first.
Do multiple brands create duplicate content problems?
Yes, if you publish the same article in several help centres. Pick one canonical home per article or write brand-specific content.
How long does help centre SEO take to work?
Months, not weeks, for competitive queries. Long-tail product-specific questions can start ranking much faster, which is where to start.
Deflection has a ceiling
Even a help centre that ranks well leaves a queue, and a tenth of that queue is the same question more than once.
Start free trial14-day free trial. No credit card required.