Use Cases AI Agents Pricing Embeds AI Skill MCP Server Sign in Get Started
All articles

How to test a help desk’s SEO controls before you buy

Put one customer question through a help desk trial. Check how readers find the answer, which URL search engines see and what happens when the article moves.

💡
Quick answer. Ask each help desk vendor to publish one sample answer, show how a customer can find it and change its address. Choose the platform where the answer opens on a public page, search engines can reach it and yesterday’s link still takes customers to the right place.

Imagine a customer searching for “download my VAT invoice”. Your team has written the answer. During a sales demo, an agent finds it instantly by typing “invoice” into the support widget. One question remains. What link could that customer find in Google, bookmark or send to their accountant?

Use that invoice question throughout your trial. Bring a short sample answer that is safe to publish and repeat the same checks for each platform on your shortlist. If the trial keeps articles private, ask for a public example on the same plan and hosting setup you would buy.

Can a customer reach the answer from outside the widget?

Copy the article link into a private browser window. It should open directly on the invoice answer without a login or a second search. Then start at the help centre homepage and follow the billing category to the same article. Save the address you reach by both routes.

Ask the vendor to show the page response. Look for an HTTP 200 and a distinctive sentence from the answer in the HTML. If the first response contains only a loading screen, ask to see the rendered page in Search Console. Google can render JavaScript. What matters here is whether it can access the answer and follow the links on this particular site. Google’s technical requirements and its guide to crawlable links explain what to check.

Do the title, links and sitemap identify the same article?

Give the sample a specific title such as “Download a VAT invoice for your subscription”. Ask an editor to change the title and the short summary. Reload the public page and check the browser title and description in the HTML. This reveals which fields an editor controls and whether a change needs a developer.

Next, compare the address in the browser with the page’s rel="canonical" link. The canonical tells search engines which version the publisher prefers. Open the XML sitemap and find the same address. An article on your custom domain that points back to a vendor’s demo address deserves an explanation before you sign. Google describes how it weighs canonical signals.

You can see what matching signals look like on a real help centre. When we checked HelpDesky’s public redirect guide, its HTML contained the instructions and named that same page as canonical. The public robots.txt pointed to a sitemap listing the guide. Those checks are reproducible without access to the editor. They establish what the platform serves today.

What happens to yesterday’s link?

Save the invoice article’s original address. Ask the vendor to change the last part of the URL from /invoices to /download-vat-invoice. Open the saved address again in a private window. In the browser’s network panel, look for a permanent redirect, usually 301 or 308, followed by the invoice page with a 200 response.

A redirect to the help centre homepage leaves the customer hunting for the answer. A better result is a direct redirect to the renamed article, a billing category link that goes straight there and a sitemap that lists the new address. Ask who can fix a broken redirect after launch. HelpDesky’s redirect guide documents an editor’s choice to keep the old URL working when changing a slug.

📌
Keep a trial record. For each vendor, save the sample URL, the old URL after the rename, the canonical and the sitemap entry. Beside anything you could only see in a sales demo, write down which plan includes it and who will maintain it.

Which checks can you run on HelpDesky?

HelpDesky’s hosted help centre renders the article on the server, builds its sitemap and generates article metadata from the title and excerpt. Editors can review suggested changes and see their history. A useful trial is to have the person who writes your billing answers review a suggested link, then check its wording and destination on the public page. See the hosted SEO features and editorial review controls.

HelpDesky’s SEO Advisor showing Suggestions, Internal Links, AI Optimisation and Change History
The SEO Advisor separates link suggestions from the history of changes. Ask an editor to demonstrate both during a trial. Screenshot from the HelpDesky documentation.

Hosting changes the work involved. With managed hosting, HelpDesky supplies the article template. With headless delivery, your developers render the content and own the navigation, sitemap entries and error pages. Test the version your customers will actually use. The hosting options guide explains that division of work, and our guide to help centres in a subfolder covers the questions to take to your web team.

HelpDesky’s Free plan includes SEO tools, one workspace, unlimited seats, up to 15 articles and 15 conversations per month. That gives an editor and a developer room to try the same sample. Pro is $5 per month for one workspace with unlimited seats, articles and conversations. Connected AI features use your own provider key, with usage billed separately.

What can Search Console confirm?

If you control the trial domain and have access to its Search Console property, inspect the sample URL. The live test helps you see whether Google can access the page now. The indexed report shows what Google recorded on its last visit, including its chosen canonical when available. A newly published sample may have no indexed data yet.

Google’s URL Inspection reference explains how to read the two results. Its short training video shows where to find the tested page, which is especially helpful when a vendor relies on JavaScript to display the answer.

Watch Google Search Central’s URL Inspection training on YouTube.

Questions to settle before you buy

Does a passing trial mean our article will rank?

No. The trial shows that a search engine can reach and interpret your answer. Google decides whether to index it and where it appears for a query. Compare vendors on results you can reproduce during the trial.

Is a widget enough for public help centre SEO?

A widget can be a useful route to an answer. Ask for the standalone URL behind it. A customer should be able to open that exact answer from an email or search result with the widget closed.

Do we need our help centre in a subfolder?

A public article can work on a subdomain or in a folder. Choose an address your team can maintain, then check that links, canonicals and sitemap entries agree on it. If you already have a library, our help desk migration checklist covers the extra work of protecting existing links.

Should an llms.txt file decide the purchase?

Give the public article checks priority. An llms.txt file is an additional resource to inspect if AI discovery matters to you. Our guide to llms.txt for SaaS help centres explains its role, and our guide to citations in AI search explains how to assess those separately.

What if the vendor cannot give us Search Console access?

You can still inspect the public answer, title, canonical, sitemap and redirect yourself. Ask the vendor to demonstrate the indexed and live reports for a public page they own. Record whose property was tested so your team knows what still needs checking on your own domain.