Your help article is public to customers. Is it public to Google?

Your help article is public to customers. Is it public to Google?

Put pre-sale answers in a public Help Center collection, then link to them from your product site. Keep account-specific help behind login: an article opening from a direct link does not mean Google can find it.

A direct link is not a visibility setting

In Intercom, these terms describe different things:

Intercom creates a shareable URL for an unlisted article, but says unlisted articles are not indexed by search engines. So “the link works” only proves that a person with the link can open it. It does not prove that Google can discover it. (intercom.com)

One useful distinction: unlisted does not mean protected by a login. Treat it as hidden from browsing and search, not as a safe place for private account details. For instructions that should only be visible to customers who are logged in, set the article’s audience accordingly; Intercom says articles limited to logged-in users are not shown to visitors and leads. (intercom.com)

What Google needs—including for AI Overviews

Google needs to be able to reach and process a page. Its basic technical requirements say Googlebot must not be blocked, the page must work, and it must have indexable content. Meeting those requirements makes a page eligible for indexing; it does not guarantee Google will index it. (developers.google.com)

The same access rule applies to Google AI Overviews: Google says a page must be indexed and eligible to appear in Search with a snippet to be eligible as an AI Overview supporting link. There is no separate AI Overview switch to turn on. (developers.google.com)

That makes the Intercom setting matter. Adding an article to a collection makes it searchable in your Help Center and by search engines, according to Intercom; leaving it unlisted does not. A collection makes the article discoverable, but Google still decides whether to crawl, index, and show it. (intercom.com)

Also check that your Help Center is live, search engine indexing is enabled, and the article is visible to visitors—not only logged-in users. Intercom lets you control article audiences, and its guidance says to link to the Help Center from your marketing site so Google can find it. (intercom.com)

Don’t spend a day adding special schema or AI markup. Google says there are no additional technical requirements for AI Overviews beyond Search eligibility. Put the time into making the answer useful and linking to it with clear words, such as “See whether your plan includes SSO” rather than “Read more.” Google recommends crawlable links with descriptive anchor text. (developers.google.com)

Which articles belong where?

1. Public collection: pre-sale questions. If a prospect can ask it before signing up, and the answer is safe for anyone to read, put it in a collection. Examples include plan limits, integrations, setup needs, data export options, and how a trial works.

2. Unlisted: direct sharing without search discovery. Use this when someone needs a specific answer by link, but you do not want it in Help Center search or Google. It can also work for a preview before you add an article to a collection. Just don’t put secrets or customer-specific data there.

3. Login-restricted or internal help: account-specific steps. Keep instructions that depend on a customer’s account, plan, private data, or access rights out of the public collection. An article that should be visible only to logged-in users needs an audience restriction; an unlisted URL alone is not that restriction. (intercom.com)

There’s a separate AI wrinkle: Intercom says its Fin AI Agent may use unlisted articles, but it will not cite them with a source link. That is different from Google AI Overviews, which requires an indexed, Search-eligible page for a supporting link. (intercom.com)

A 90-minute job for a small SaaS

Say you run a three-person SaaS with 30 Help Center articles and two hours a month for content. Don’t move all 30 articles. Pick one question prospects ask often, such as: “Does your product support SSO?”

Use about 90 minutes:

• 15 minutes: Look through the last 10 pre-sale questions and pick one that is safe to answer publicly.
• 30 minutes: Write the answer. State whether the feature is available, which plan includes it, any limits, and what a new customer needs to do. Use your real product details; don’t leave the key answer buried below a sales pitch.
• 15 minutes: Add the article to the right public Help Center collection. Check that its audience includes visitors and leads.
• 15 minutes: Add a normal link to it from the most relevant page on your product site, such as the pricing or integrations page. Use descriptive link text.
• 15 minutes: Open the article while logged out, then record its Google Search Console impressions and clicks for the last 28 days.

For a simple traffic example, say that article’s starting point is 0 impressions and 0 clicks in that 28-day period. That is a sample baseline, not a forecast; replace it with your actual numbers. Search Console reports impressions and clicks, so you can check later whether the page is appearing in Google and getting visits. (support.google.com)

If you already pay for Intercom, the incremental software cost is $0 for this change. The main cost is the 90 minutes. Being eligible is not a promise of traffic: Google may choose not to index or show the page, so track the actual numbers instead of promising a traffic lift. (developers.google.com)

Who should skip the move

Don’t move account-specific support articles into a public collection just to chase Google or AI visibility. Don’t spend your two-hour monthly budget moving every article, either. Start with one safe answer that helps a prospect decide whether your product fits; leave private instructions where login or account context protects them.

**This week, take one common pre-sale question, publish its answer in a public Help Center collection, and add a descriptive link to it from your product site.