# The help center should look like the company, not the tooling > Why the support domain, share image, footer links, typography, and crawl settings quietly decide whether a help center builds trust or leaks it. - Canonical HTML: https://growth.iangoh.com/blog/the-help-center-should-look-like-the-company-not-the-tooling/ - Published: 2026-05-30 - Updated: 2026-05-30T21:25:00Z - Categories: brand trust, SEO, support-led growth - Niches: SaaS, AI products, creator tools, consumer apps, marketplaces ## On this page - The support domain is part of the product address - Shared article previews do branding work too - The footer is where support pages stop being dead ends - Typography is not decoration on a stressed page - Sometimes the right support page should not rank - Where this cluster is strongest ## Start with these related tactics - [Help center custom domain before support links spread](/growth-ideas/help-center-custom-domain-before-support-links-spread/): Move the help center onto your own domain before support links spread across tickets, docs, and search, so every future answer compounds trust on a branded host. - [Help center social share image for article links](/growth-ideas/help-center-social-share-image-for-article-links/): Upload a real social share image for your help center so shared article links carry brand proof instead of a generic support preview. - [Help center footer columns for next-step navigation](/growth-ideas/help-center-footer-columns-for-next-step-navigation/): Use the help-center footer to group proof, support, product, and contact paths, because every article page is also a next-step page. A lot of software teams treat the help center like rented warehouse space. The real brand lives on the homepage. The real product lives in the app. Support gets whatever theme is easiest to switch on. That sounds harmless until you watch how buyers and customers actually use support pages. They see article links in Google, in onboarding emails, in tickets, in chat, and in internal docs. For many people, the help center is not a side surface. It is the most repeated proof surface the company has. When that surface looks generic, trust leaks in small pieces. Not dramatic pieces. Just enough to make the product feel less settled than it is. ## The support domain is part of the product address [Help center custom domain before support links spread](/growth-ideas/help-center-custom-domain-before-support-links-spread/) is the infrastructure move in this cluster. Once article links start getting copied around the company, a vendor-flavored host becomes sticky. A branded help domain fixes that early and keeps future trust, backlinks, and bookmarks landing on your own address. It also pairs naturally with [same-workspace 301 map after help-center migration](/growth-ideas/same-workspace-301-map-after-help-center-migration/) and [help-center collection link cleanup after domain switch](/growth-ideas/help-center-collection-link-cleanup-after-domain-switch/). One move gets the help center onto the right domain. The follow-up work makes sure the old path still carries people and authority to the right place. ## Shared article previews do branding work too [Help center social share image for article links](/growth-ideas/help-center-social-share-image-for-article-links/) sounds cosmetic until you remember how often support answers travel. A success manager shares one article into a Slack thread. A founder drops another into a community reply. A support lead sends a billing answer during renewal. Each of those links now has a preview card. If the preview looks generic, the team wastes a small proof moment over and over. I would think about it the same way I would think about [Chrome Web Store five-screenshot install story](/growth-ideas/chrome-web-store-five-screenshot-install-story/). The visual wrapper changes whether the user reads the destination as maintained or improvised before they open it. ## The footer is where support pages stop being dead ends [Help center footer columns for next-step navigation](/growth-ideas/help-center-footer-columns-for-next-step-navigation/) is really an internal-linking tactic disguised as design. Someone who reaches the end of an article often needs one more thing: status, contact, pricing, roadmap, migration docs, or the next setup step. A footer that groups those paths keeps the session moving without forcing the reader back into search. This is the same operating idea behind [footer link to integration hub](/growth-ideas/footer-link-to-integration-hub/). The footer is boring, but boring surfaces win when they stay useful on every page. ## Typography is not decoration on a stressed page [Full font family upload before help-center rebrand](/growth-ideas/full-font-family-upload-before-help-center-rebrand/) matters because support pages are usually read under mild stress. The user is scanning quickly. They are looking for headings, warnings, buttons, emphasis, maybe code or setup steps. If the typography breaks between weights, the page starts to feel stitched together even when the answer itself is right. That sounds like a designer complaint until you see the alternative: one product that feels polished in the marketing site and oddly temporary in the knowledge base. Users notice that mismatch faster than teams expect. ## Sometimes the right support page should not rank [Help center noindex during duplicate-content phase](/growth-ideas/help-center-noindex-during-duplicate-content-phase/) is the SEO discipline in this group. A help article can be useful in Messenger, in-product search, or AI support before it should compete in Google with the canonical docs site. The point is not to hide knowledge. The point is to stop duplicate support surfaces from fighting each other. That is especially relevant if the team is already doing things like [preview docs noindex before cutover](/growth-ideas/preview-docs-noindex-before-cutover/) or [single indexed help center during knowledge sync](/growth-ideas/single-indexed-help-center-during-knowledge-sync/). The pattern is simple: keep one search winner at a time. ## Where this cluster is strongest This cluster is strongest for SaaS products, AI tools, creator platforms, support-heavy consumer apps, and marketplaces where a help article is often read before a demo, during onboarding, or in the middle of a renewal risk moment. The support page does not need to look flashy. It just needs to feel like it belongs to the same serious company as the product. If you want help tightening trust, crawlability, and conversion across your docs and support surfaces, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [Help center custom domain before support links spread](/growth-ideas/help-center-custom-domain-before-support-links-spread/) - SEO, Support, Brand - [Help center social share image for article links](/growth-ideas/help-center-social-share-image-for-article-links/) - Brand, SEO, Content - [Help center footer columns for next-step navigation](/growth-ideas/help-center-footer-columns-for-next-step-navigation/) - Website, SEO, Brand - [Full font family upload before help-center rebrand](/growth-ideas/full-font-family-upload-before-help-center-rebrand/) - Brand, Support, Website - [Help center noindex during duplicate-content phase](/growth-ideas/help-center-noindex-during-duplicate-content-phase/) - SEO, Support, AI Search ## Essay chronology - [Newer essay: The Community page should teach the tool before the install](/blog/the-community-page-should-teach-the-tool-before-the-install/) - creator-led growth, marketplaces, brand trust - [Older essay: The Slack app directory page should answer the admin's next question](/blog/the-slack-app-directory-page-should-answer-the-admins-next-question/) - marketplaces, onboarding, brand trust ## Keep reading - [The answer should travel before the queue grows](/blog/the-answer-should-travel-before-the-queue-grows/) - support-led growth, brand trust, SEO - [The help article should know what comes next](/blog/the-help-article-should-know-what-comes-next/) - SEO, support-led growth, brand trust - [The route should stay yours after the click](/blog/the-route-should-stay-yours-after-the-click/) - brand trust, technical SEO, AI visibility ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path ## Sources - [Intercom Help: Set up a custom domain for your Help Center](https://www.intercom.com/help/en/articles/1039696-set-up-a-custom-domain-for-your-help-center/) · [GrowthDex source hub](/sources/intercom-help-set-up-a-custom-domain-for-your-help-center-intercom-com/) - [Intercom Help: Customize your Help Center](https://www.intercom.com/help/en/articles/56644-customize-your-help-center) · [GrowthDex source hub](/sources/intercom-help-customize-your-help-center-intercom-com/) - [Intercom Help: Customize Help Center footer](https://www.intercom.com/help/en/articles/8486727-customize-help-center-footer) · [GrowthDex source hub](/sources/intercom-help-customize-help-center-footer-intercom-com/) - [Intercom Help: Using custom fonts in the Help Center](https://www.intercom.com/help/en/articles/8429204-using-custom-fonts-in-the-help-center) · [GrowthDex source hub](/sources/intercom-help-using-custom-fonts-in-the-help-center-intercom-com/) - [Intercom Help: Prevent search engines indexing your Help Center](https://www.intercom.com/help/en/articles/5145271-prevent-search-engines-indexing-your-help-center) · [GrowthDex source hub](/sources/intercom-help-prevent-search-engines-indexing-your-help-center-intercom-/) ## Editing notes - Kept the essay anchored on one plain idea: support pages get repeated exposure, so small trust leaks matter. - Used concrete page objects like the domain, preview card, footer, and font weights instead of abstract brand language. - Cut generic SEO rhetoric and framed indexing as a practical one-winner rule during duplicate-content phases. - Ended on the operating standard for the page rather than a padded recap. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.