Knowledge-base SEO

Knowledge-base SEO means helping a person find the right answer through public search as well as through the help centre's own navigation. It is not a reason to publish a separate thin page for every phrasing of the same question. A useful help article should work even if the reader arrives directly from a search result with no previous context.

Google's SEO starter guide recommends logical structure, descriptive URLs, clear titles, original helpful content and links that connect related pages. Those principles fit support documentation particularly well. They do not guarantee rankings, and no amount of metadata can repair a page whose instructions are wrong.

Choose the right pages for public search

Start with customer tasks that can be answered publicly: how to start a return, find a bill, configure a product or understand a common error. A private ticket transcript, staff-only procedure or customer's account status should not be indexed. A page hidden by login is not a public-search landing page. Conversely, a public answer that requires login merely to read may introduce friction when the information itself is not sensitive.

Map one primary intent to one authoritative URL. “Change a shipping address” and “edit delivery details” may be two ways to ask the same thing. Use both natural phrases on one complete page rather than cloning it into two articles. Separate pages only when the actual task differs—for example, before dispatch versus after dispatch—then make the distinction clear in the title and links. Our structure guide shows how to place the answer without duplicating it.

Prioritise based on contact evidence, not a list of keywords alone. A page that prevents a confusing account-access journey may be valuable even if a commercial keyword tool reports modest volume. Google's helpful-content guidance explicitly warns against creating pages mainly to target searches while leaving readers needing another answer.

Write search results that make an honest promise

Use a unique, concise title that names the task or symptom. A title such as “How to download an invoice” is clearer than “Billing information”. The page's first paragraph should confirm scope and give the short answer. A person who arrives from Google should not need to click through several introductory screens before learning whether the article applies.

Write a short, distinctive meta description explaining the outcome and relevant condition. Google may generate its own snippet from page text, so the body must also be clear. Use headings to separate prerequisites, steps, exceptions and next actions. Describe images in alternative text when they carry meaning, and keep instructions in text rather than embedding them only in screenshots.

Do not repeat a keyword mechanically in every heading. Google says its language systems can understand related wording and that keyword stuffing is an anti-pattern. Include the words customers actually use, including a helpful synonym or old feature name where relevant. A support page is not improved by turning every sentence into a variation of “best help centre article”.

Make the help centre crawlable and navigable

Check a public article without an admin session. Confirm that the full answer appears in the rendered HTML, the page can be reached from a category or related page, and search-engine crawlers are not blocked by a stray noindex directive or login requirement. A public help centre can have a sitemap, but its most important pages should also have ordinary HTML links from the main site and from nearby articles.

Use readable URLs and keep them stable. If the platform adds an article ID, the descriptive part still helps readers. When a category changes, preserve the existing URL if possible or redirect it to the new article. Avoid a site redesign that turns every old support link in emails into a 404. Google's documentation treats redirects, canonical annotations and sitemap entries as different signals; a canonical tag is not a substitute for fixing navigation.

On a help-centre subdomain, verify the main site's links and the help centre's own sitemap, ownership and analytics. A subfolder may simplify some governance, but there is no general rule that moving a working help centre to a subfolder produces a ranking gain. Choose what lets the team maintain content, permissions and redirects correctly.

Handle duplicates, private content and structured data carefully

Duplicate answers cause two problems: search engines must select a representative URL, and staff may update one copy but not the other. Consolidate editorially first. Keep the clearer page, link to it from related topics, and redirect an older path when that is the right reader journey. Use a canonical annotation for legitimate alternate versions that must remain accessible. Google's canonical guidance explains that even an explicit preference is not an absolute command.

Do not use noindex as a privacy boundary. It asks search engines not to show a page; it does not stop a person with the URL reading it. Staff and account-specific content needs real access control. The internal-versus-external guide covers the audience decision.

Visible FAQs can help a reader who has a genuine follow-up question, and structured data should match what the page visibly says. But Google's current guidance says FAQ rich results are generally limited to well-known authoritative government and health sites. Do not sell an FAQ module as a dependable search-result enhancement for a software support publication. Answer questions because they improve the page.

Measure qualified help, not raw traffic

Search impressions and clicks show discovery; they do not prove resolution. Pair Search Console data with the help centre's search terms, article feedback, contact-after-view rate and a sample of completed tasks. A page might rank well for “refund policy” but send people to support because the eligibility rule is unclear. Another page may get less search traffic but resolve a costly technical problem well.

Review queries that land on the wrong article, zero-result internal searches and pages whose traffic changes after a product release. Sometimes the problem is a title or internal link; sometimes the answer is outdated; sometimes the product itself needs improvement. Use the content audit to correct the full journey rather than adding more keywords to the same weak page.

The highest-value SEO work is often operational: an accurate answer, a stable URL, a clear link from the product interface and an owner who updates the page when the product changes. There is no shortcut to sustained search usefulness.

Sources

• Google Search Central SEO starter guide
• Google Search Central on helpful, people-first content
• Google Search Central on canonical URLs
• Google Search Central on FAQ rich-result changes

SEO and product-fit conclusions are editorial guidance; search visibility and rich results are never guaranteed.