How should Help Scout Docs be configured for SEO?

Help Scout Docs should be served on a custom subdomain (help.yourdomain.com or docs.yourdomain.com) rather than the default [company].helpscoutdocs.com URL. Custom domain configuration keeps all organic search value — PageRank, domain authority, crawl signals — on your domain rather than Help Scout's. Once configured, add a canonical tag in the Docs custom code header pointing to the custom domain URL to prevent any residual helpscoutdocs.com URLs from competing. Submit a separate sitemap for your Docs knowledge base to Google Search Console under your custom domain property.

Does Help Scout Docs support Article schema for knowledge base articles?

Help Scout Docs does not automatically add Article or HowTo schema to knowledge base articles. You can inject custom JSON-LD schema via the Docs custom code header or article footer settings. The recommended schema for knowledge base articles is Article with datePublished, dateModified, and headline. For instructional step-by-step articles, HowTo schema is more appropriate and can generate rich results in Google search. Verify that any injected schema is rendered in the initial server-side HTML — DeepSEOAnalysis checks whether schema appears in the initial page HTML or is added by JavaScript after load.

Does the Help Scout Beacon widget affect Core Web Vitals?

Yes — the Help Scout Beacon widget loads a JavaScript bundle that can affect INP (Interaction to Next Paint) when the widget is the first interactive element a user engages with, and CLS (Cumulative Layout Shift) on pages where the Beacon button renders into a fixed position over other content without proper layout consideration. The Beacon script should be loaded asynchronously to prevent it from blocking the main thread during initial page rendering. For pages where Beacon is not needed (e.g. checkout pages, landing pages focused on conversion), consider conditionally loading the Beacon script only on pages where support is the primary use case.

Should all Help Scout Docs articles be indexed by Google?

Most knowledge base articles should be indexed — they answer specific how-to and troubleshooting queries that bring in organic search traffic even for users who aren't yet customers. However, some articles should be noindexed: internal process documentation not intended for external users, articles about deprecated features that may cause confusion, and very thin articles (under 200 words) that add no search value. Help Scout Docs allows setting a collection to private (which prevents indexation) or adding noindex via custom code. Review your Docs article list periodically to remove or consolidate thin content.

How do I optimise Help Scout Docs articles for search?

Each Docs article should have a distinct title that matches the exact query it targets (e.g. 'How to reset your password' rather than 'Password reset'). The first paragraph should answer the question directly — Docs articles that front-load the answer are more likely to be featured snippets. Add a custom meta description via the article SEO settings in Help Scout Docs. Internal links between related articles improve both crawlability and topic clustering. Use HowTo schema for step-by-step instructional articles and Article schema for conceptual explainers. Avoid duplicating content between your marketing site and your Docs knowledge base — if the same topic appears in both places, use a canonical tag to designate the primary version.

What is the difference between Help Scout Docs and Help Scout Messages for SEO?

Help Scout Docs is the public-facing knowledge base — articles in Docs are indexable and can drive organic search traffic. Help Scout Messages (the customer support inbox and conversation flow) is not public-facing and has no organic search presence. From an SEO perspective, only Docs requires an SEO strategy. The Beacon widget sits at the intersection: it surfaces Docs articles in an overlay, allowing users to find support without leaving your page, but the Beacon overlay content is not crawlable by search engines — only the underlying Docs articles at their direct URLs are indexable.

DeepSEOAnalysis for Help Scout Docs Pages

Help Scout Docs knowledge bases need custom domain canonicals, injected Article or HowTo schema, and async Beacon loading. DeepSEOAnalysis audits all of it — free, no account required.

Audit your Help Scout Docs page free →

What DeepSEOAnalysis checks on Help Scout-powered pages

Docs knowledge base SEO

Custom domain (help.yourdomain.com) vs helpscoutdocs.com canonical configuration
Article schema injection for knowledge base articles via custom code
HowTo schema on instructional step-by-step Docs articles
Meta description and title optimisation per Docs article

Beacon widget CWV

Beacon JavaScript bundle async loading to prevent INP on initial interactions
CLS from Beacon fixed-position button rendering over page content
Conditional Beacon loading — only on pages where support widget is needed
Beacon Docs article preview INP when opening suggestions overlay

Indexation control

Noindex on private Docs collections intended for internal use only
Noindex on thin Docs articles under 200 words with no unique search value
Separate GSC property for Docs custom subdomain sitemap submission
Canonicals from helpscoutdocs.com default URLs to custom domain equivalents

Schema validation

Server-rendering verification — Article/HowTo schema in initial HTML not JS-injected
datePublished and dateModified accuracy on Docs article schema
Breadcrumb schema on Docs collection and article pages
FAQPage schema on Docs articles structured as Q&A content

Knowledge base content strategy

Duplicate content check — same topics in marketing site and Docs knowledge base
Internal links between related Docs articles for crawlability and topical clustering
Collection structure matching search intent (how-to, troubleshooting, reference)
Featured snippet optimisation — direct answer in first paragraph of Docs articles

Technical configuration

Docs sitemap availability and submission to GSC under custom domain property
robots.txt for Docs custom subdomain — allowing crawl of intended articles
hreflang on Docs articles if knowledge base has multi-language collections
Page speed of custom-domain Docs pages with Beacon script loaded

Custom domain vs helpscoutdocs.com

The single highest-impact Help Scout Docs SEO decision is whether articles live on your custom domain (help.yourdomain.com) or the default [company].helpscoutdocs.com. Every article on helpscoutdocs.com builds organic authority for Help Scout's domain, not yours. Knowledge base articles that rank in Google for "[product] how to [task]" queries should be driving that traffic to your domain.

Custom domain setup in Help Scout requires adding a CNAME record pointing your help subdomain to Help Scout's infrastructure. Once configured, add a canonical tag in the Docs Appearance settings custom header code so any legacy helpscoutdocs.com URLs that Google has indexed redirect attribution to your custom domain version.

Injecting Article and HowTo schema into Docs articles

Help Scout Docs does not generate structured data automatically. You can inject JSON-LD schema via the custom code settings in Docs Appearance. For the majority of knowledge base articles, Article schema with datePublished, dateModified, headline, and author (your organization) is appropriate. For instructional articles structured as numbered steps ("How to configure X in 5 steps"), HowTo schema with individual Step entities can generate rich results in Google search.

The key validation point: schema injected via custom code must appear in the server-rendered HTML, not be added by JavaScript after page load. DeepSEOAnalysis verifies whether schema appears in the initial HTML response — schema that only appears after JavaScript execution is invisible to crawlers that don't execute JavaScript.

Beacon widget and Core Web Vitals

The Help Scout Beacon widget adds a support button to your website that surfaces Docs articles and a contact form. The Beacon JavaScript bundle loads on every page where the widget is active. For pages where Beacon is genuinely useful (product pages, in-app help, checkout support), the async loading impact is acceptable. For high-traffic landing pages optimised for conversion where Beacon is not part of the user flow, conditionally omitting the Beacon script on those specific page types reduces JavaScript payload and eliminates any potential INP impact from the Beacon initialisation.

Frequently asked questions

How should Help Scout Docs be configured for SEO?: Help Scout Docs should be served on a custom subdomain (help.yourdomain.com or docs.yourdomain.com) rather than the default [company].helpscoutdocs.com URL. Custom domain configuration keeps all organic search value — PageRank, domain authority, crawl signals — on your domain rather than Help Scout's. Once configured, add a canonical tag in the Docs custom code header pointing to the custom domain URL to prevent any residual helpscoutdocs.com URLs from competing. Submit a separate sitemap for your Docs knowledge base to Google Search Console under your custom domain property.
Does Help Scout Docs support Article schema for knowledge base articles?: Help Scout Docs does not automatically add Article or HowTo schema to knowledge base articles. You can inject custom JSON-LD schema via the Docs custom code header or article footer settings. The recommended schema for knowledge base articles is Article with datePublished, dateModified, and headline. For instructional step-by-step articles, HowTo schema is more appropriate and can generate rich results in Google search. Verify that any injected schema is rendered in the initial server-side HTML — DeepSEOAnalysis checks whether schema appears in the initial page HTML or is added by JavaScript after load.
Does the Help Scout Beacon widget affect Core Web Vitals?: Yes — the Help Scout Beacon widget loads a JavaScript bundle that can affect INP (Interaction to Next Paint) when the widget is the first interactive element a user engages with, and CLS (Cumulative Layout Shift) on pages where the Beacon button renders into a fixed position over other content without proper layout consideration. The Beacon script should be loaded asynchronously to prevent it from blocking the main thread during initial page rendering. For pages where Beacon is not needed (e.g. checkout pages, landing pages focused on conversion), consider conditionally loading the Beacon script only on pages where support is the primary use case.
Should all Help Scout Docs articles be indexed by Google?: Most knowledge base articles should be indexed — they answer specific how-to and troubleshooting queries that bring in organic search traffic even for users who aren't yet customers. However, some articles should be noindexed: internal process documentation not intended for external users, articles about deprecated features that may cause confusion, and very thin articles (under 200 words) that add no search value. Help Scout Docs allows setting a collection to private (which prevents indexation) or adding noindex via custom code. Review your Docs article list periodically to remove or consolidate thin content.
How do I optimise Help Scout Docs articles for search?: Each Docs article should have a distinct title that matches the exact query it targets (e.g. 'How to reset your password' rather than 'Password reset'). The first paragraph should answer the question directly — Docs articles that front-load the answer are more likely to be featured snippets. Add a custom meta description via the article SEO settings in Help Scout Docs. Internal links between related articles improve both crawlability and topic clustering. Use HowTo schema for step-by-step instructional articles and Article schema for conceptual explainers. Avoid duplicating content between your marketing site and your Docs knowledge base — if the same topic appears in both places, use a canonical tag to designate the primary version.
What is the difference between Help Scout Docs and Help Scout Messages for SEO?: Help Scout Docs is the public-facing knowledge base — articles in Docs are indexable and can drive organic search traffic. Help Scout Messages (the customer support inbox and conversation flow) is not public-facing and has no organic search presence. From an SEO perspective, only Docs requires an SEO strategy. The Beacon widget sits at the intersection: it surfaces Docs articles in an overlay, allowing users to find support without leaving your page, but the Beacon overlay content is not crawlable by search engines — only the underlying Docs articles at their direct URLs are indexable.