Zendesk SEO: what the help center already does for search, what you control, and how to move articles without losing their URLs

A Zendesk help center arrives with most technical SEO already handled: readable article URLs, canonical tags, hreflang for translations, HTTPS, a mobile layout and an automatic XML sitemap at /hc/sitemap.xml. What is left to you is the part that decides whether articles get found: clear titles, articles that answer one question each, a branded address through host mapping, 301 redirects when you move or delete content, and making sure you have not hidden the help center from search by accident. This guide goes through each, using Zendesk's own documentation as read in October 2026.

What the help center does for search out of the box

Zendesk's article "About search engine optimization (SEO) in the help center" lists the built-in pieces. They apply to the help center on Suite Team, Growth, Professional, Enterprise and Enterprise Plus, and to Support with Knowledge Professional or Enterprise, with the sitemap exception noted below.

Built-in feature	What Zendesk says it does	What it means for you
Meta descriptions	Articles and community posts get an automatic description from their first 140 characters	Your opening sentence becomes the search snippet, so write it as a summary
URL structure	/hc/en-us/articles/[id]-[slug]	Renaming an article does not break its URL, because the ID stays
Canonical tags	Each page names its canonical URL	Duplicate paths to the same article consolidate on one URL
hreflang	On the home, category, section and article pages	Translated articles are served to readers in their language
HTTPS and mobile	HTTPS everywhere; mobile site or responsive theme	Nothing to set up
XML sitemap	Automatic, updated every two hours, listed in robots.txt	Submit it in Search Console; it is not on Suite Team

Zendesk is precise about what the sitemap does. It helps search engines find your categories, sections and articles, but it "does not improve individual ranking of these pages". It also leaves out community content, so community posts are found through links. If your help center requires sign-in, no sitemap is generated at all.

Check first: is the help center open to search engines?

A help center with no search traffic is often one that search engines cannot see. Zendesk's answer on restricting indexing gives the three ways that happens:

• The whole help center requires sign-in. Search engines do not index pages that need a login, and Zendesk says such help centers are not indexed by default.
• Articles are restricted with user segments. Any article limited to signed-in users stays out of search. That is right for internal or customer-only content and wrong for the how-to articles prospects search for.
• A noindex tag sits in the theme. Zendesk's method for hiding a public help center is to add <meta name="robots" content="noindex" /> to the theme's document_head.hbs file. That tag applies to every page in the theme. If an old theme or a test setup added it, every article is excluded.

To check, open any article, view the page source and search for "noindex". Then open a private browser window and confirm articles load without signing in. Zendesk also notes that after noindex is added, removal from search results can take months. Our guide to the robots meta tag explains every value the tag can carry.

Put the help center on your own domain with host mapping

By default the help center lives at yourcompany.zendesk.com. Host mapping lets you serve it from a subdomain of your own domain, such as support.yourcompany.com, by adding a CNAME record and setting up hosted SSL. Zendesk's documentation sets three limits worth knowing before you plan it:

• It works for subdomains only. You cannot map a second level domain such as yourcompany.com or yourcompany.co.uk.
• It changes only the public address. Agents keep using the default zendesk.com URL.
• Zendesk does not set up redirects for you. If you change a host-mapped address later, redirecting the old one is your job.

A branded subdomain puts your help content under your own name in search results and keeps links to it pointing at an address you control.

Write articles the way people search

Zendesk's own best practices are short and sensible:

• Brief titles that describe the page. Zendesk calls the title the most prominent piece of information in search results. "Reset your password" beats "Account access FAQ".
• One question per article. A focused article matches a focused search. Long catch-all pages match none of them well.
• A first sentence that answers. Because the meta description is taken from the first 140 characters, start with the answer, not with "In this article".
• Original content. Zendesk advises against mass-produced content or content copied from other sites.
• Descriptive links. When one article links to another, the link text should say what the reader will find.
• Labels for internal search. Labels help the help center's own search. Zendesk notes most users do not type underscores, so add both forms of a multi-word label.

Write category and section descriptions too. For those pages Zendesk uses the description you enter as the summary, so a blank description is a missed snippet.

Moving to Zendesk without losing your old URLs

Zendesk's guidance for moving from an old support site lays out an order that protects the pages already ranking:

1. Create and publish every destination article in the help center first, so the new URLs exist.
2. Build a map that pairs each old URL with its new help center URL.
3. Set up 301 redirects on the old host, in .htaccess on Apache or in the server's control panel.
4. Prefer one-to-one rules, avoid chains and loops, and keep pattern rules specific.
5. Test a sample of old URLs and confirm a single 301 to the right article.
6. Update internal links on the old site, then ask Google to crawl the new pages.

Zendesk adds that it has no influence over how often Google crawls, so the timing of the switch in search results is set by Google.

Deleted or merged articles: use 301s, not script redirects

When you retire an article, visitors and search engines still arrive at the old URL. Zendesk documents a JavaScript method in the theme's script.js file, but its own warning says those redirects may affect Google rankings and suit only short-term or internal cases with no search traffic. For anything that matters in search, Zendesk points developers to the redirect rules API, which creates real HTTP 301 redirects on the help center. Use the API for high-traffic public articles and permanent URL changes.

Measure it

Zendesk supports Google Analytics in the help center, which shows which articles get visits and from where. Pair it with Google Search Console on the help center's address to see the search terms that bring people in and the articles that appear without being clicked. An article with many impressions and few clicks usually needs a clearer title or first sentence.

Questions about Zendesk SEO

Does Zendesk create a sitemap for the help center?

Yes, automatically, at /hc/sitemap.xml, refreshed every two hours. It is not available on Suite Team, it excludes community posts, and it is not generated for help centers that require sign-in.

Why is my Zendesk help center not on Google?

Check three things: whether the help center requires sign-in, whether the articles are restricted with user segments, and whether the theme's document_head.hbs contains a noindex tag. Any one of them keeps articles out of search.

Can I set a custom meta description for each article?

Zendesk generates article descriptions from the first 140 characters of the body. The dependable way to control the snippet is to make that opening sentence a clear summary of the answer.

Is a help center on a subdomain good for SEO?

Host mapping puts it on a subdomain of your own domain, which is the option Zendesk supports. It keeps your brand in the address and keeps links pointed at a URL you own.

How do I hide some articles from Google but not others?

Restrict those articles to signed-in users with user segments. The noindex tag in document_head.hbs applies to the whole theme, so it is the tool for hiding everything, not individual articles.

Help articles are what assistants quote

A help center is written as plain answers to specific questions, which is the shape AI assistants look for when someone asks how a product works or which tool can do a job. One help centre was cited in 269 of our readings, and we wrote up what its robots file allowed against what its server returned. If your help center is open and well titled, it is a candidate source. Whether ChatGPT, Gemini or Perplexity then name your product in the answer is something you can measure, and AI Knows Us is built to track exactly that.