Ghost and online course

Selling a course on Ghost, where half the site is deliberately unreadable

A course run on Ghost has a clean split down the middle. The sales side is public: what is included, how long access lasts, what the certificate is, what it costs. The course itself is behind a paid tier, and a crawl signed out gets a teaser and a signup prompt. That split is a feature, and it happens to map exactly onto what an assistant should and should not be answering. The complication is that the launcher renders on the gated posts too, in front of a reader it knows nothing about.

Why this pairing is its own job

The Ghost install guide covers the tag, and the online course guide covers what the assistant has to know. What follows is the part that belongs to neither.

  • Tier gating means the lessons are unreadable to any crawl, so the material is necessarily the offer: curriculum outline, access terms, refund policy, certificate status. That is the correct scope for a course assistant anyway, which makes this the rare case where the platform's structure enforces the right decision for you.
  • The launcher still appears on gated posts and on the teaser a signed out visitor sees, which means it sits beside a lesson it cannot read, in front of a paying learner asking about their own progress. What it says there has to be written for that reader specifically.
  • The terms that generate every post purchase dispute, how long access lasts and what the cancellation window is, are usually on a page nobody links from the navigation, or only inside the checkout flow, which is not a page at all.
  • A course provider sends most of its writing by email. The welcome sequence, the module reminders and the onboarding instructions are newsletters, and the assistant reads none of them unless the same content also exists on the site.

What changes about the install here

<script src="https://cdn.askably.xyz/w.js" data-key="pk_live_YOUR_KEY" defer></script>

The tag is the same one on the Ghost guide. Everything below is about where it goes on a online course site specifically.

Write the greeting for a reader who is already inside

The default assumption behind most widget greetings is that the visitor is deciding whether to buy. On a Ghost course site the launcher is also sitting on lesson pages, where the visitor has already bought and wants their certificate, their progress or their login fixed.

Write the greeting so it says what it can do and what it cannot see, in one line, before anybody asks. A learner who is told at the outset that this answers questions about access, the curriculum and the policies, and cannot see their account, asks a different and more answerable question than one who finds out after typing a paragraph.

Make the handover the obvious next step in the same message. The productive pattern for a course is that the assistant explains how a thing works in general, then takes the name and the signup email and passes it on, so the reply that follows is an answer rather than a request for details.

Publish the terms as a page, then index that

Access length, what happens when access ends, whether an extension can be bought, whether later additions are included, the cancellation window and how a refund is requested. Put all of it on one page on the site, even if the authoritative version is also inside your checkout.

This is worth doing whether or not you run an assistant, because these terms produce more disputes after purchase than anything else. But it is the difference here between an assistant that ends a refund conversation accurately in one message and one that has to hand every single one of them to a person.

Index the compliant version rather than the sales page wording. Where a country gives a buyer a statutory cancellation right on a distance sale, that sits above whatever your page says, and an assistant repeating a friendlier marketing line creates the dispute instead of preventing it.

Move the useful parts of your emails onto the site

The onboarding sequence usually contains the best writing a course provider produces: how the platform works, what to do in week one, what the common technical failures are and how to fix them. None of it is readable by anything, because it went out as email.

Turn the durable parts into a public help page. It answers the questions your inbox already receives, it survives a learner deleting the welcome message, and it gives the assistant something to say on a lesson page other than an apology.

Where the answerable material lives

Source material on a Ghost online course site
The curriculum outline with real lengthsModule by module, what form each part takes, and the realistic time each one takes. Buyers are working out whether it fits their week, and an outline saying twelve modules answers none of that. Keep it on the page you update when the course changes, not the launch copy.
Access and cancellation terms on one public pageHow long access lasts, what happens at the end, whether extensions exist, whether later material is included, the cancellation window and the refund process. The single highest value page to write, and the one most course sites do not have.
What the certificate actually isA completion certificate you issue, a credential recognised by a named body, or hours accepted by a particular profession. Write it precisely and name the body. The word on its own, with nothing behind it, is a claim rather than a description.
The technical help page you build from your own inboxSupported browsers, whether anything needs downloading, video bandwidth, and the failures you already see: the mistyped email at checkout, the welcome message in a spam folder, the corporate network blocking video. Currently this lives in your sent items.

The first thing to get right

Do this first
Write one public page holding the access terms, the cancellation window and the refund process, and index it before anything else.

It is the material that stops the most purchases and causes the most arguments after them, it is what a buyer looks for and cannot find, and on a Ghost site it is frequently the one thing that exists only inside the checkout. Everything else on the sales side is already published.

The failure that belongs to this combination

A progress question answered from the syllabus

A learner opens a lesson, sees the launcher, and asks how far through the course they are. It is a completely reasonable question in that context, and the assistant cannot see the answer, because it reads pages and documents and a learner's position is neither.

The failure is what it reaches for instead. With a detailed curriculum indexed and a caution level left low, the closest matching material is the module list, so the reply is a confident description of where module four sits in the course. It reads like an answer to the question that was asked. The learner takes it as one.

Two settings fix it and both are one line of work. Raise the caution level so a question about the learner's own account falls below the threshold rather than reaching for the syllabus, and write the refusal to say explicitly that it cannot see accounts or progress, then ask for the signup email so a person can. The gated half of the site is invisible for good reasons, and the assistant has to say so rather than fill the gap.

Before you go live

  • The origin the page is served from has to be on the allowlist for that assistant, or nothing renders and the browser console says which origin was refused. An apex domain and its www are two different origins to a browser, so list both, along with any staging or preview host you want it to work on.
  • Open the site as a visitor would, on the pages a online course visitor actually lands on, and ask it something only your own material could answer. A widget that renders is not the same as a widget that has read anything.

Questions

Can it read our lessons if they are behind a paid tier?
No. A crawl arrives signed out and gets the teaser and the signup prompt, which is exactly what any non member sees. For a course that is the right outcome: the assistant sells the course and answers about the terms, and the course itself stays behind the tier you sell.
It shows up on lesson pages. Should it?
It can, provided the greeting is written for somebody who has already bought. That reader asks about access, certificates and logins rather than about buying, so tell them in the first line what it can answer and what it cannot see, and make the handover the obvious next step.
Can it approve a refund or extend somebody's access?
No, and it should not appear to. It can state the policy, the window and the process precisely, which resolves most refund messages because most of them are really requests to understand the deadline. Deciding a case is a person's job, on the record.

Keep reading

Try it on your own material

Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.