A personal website is a monologue. You publish, and visitors either read it or do not. There is no way for someone to ask the one question that would actually move them from "interesting" to "let's talk".
Adding a chatbot changes the shape of the interaction, and for anyone whose work depends on being findable and understandable, that is worth more than another blog post.
Who this is for
Consultants and freelancers: prospects ask about scope, rates, and availability at odd hours.
Writers and researchers: readers ask about a topic across everything you have published, instead of scrolling an archive.
Speakers: organisers ask about your talks, topics, and past events.
Anyone job-hunting: recruiters ask about your experience without messaging you.
Creators: your audience asks questions your back catalogue already answers.
The common thread: you have written a lot, and nobody reads all of it.
What to feed it
Your published site content is a start, but usually too thin; it is written to be read linearly, not queried. Write one source document with:
- What you do in plain terms, without positioning language
- Your background and how you got here
- Your work or writing, with the context that never made it onto the page
- How you engage: consulting, speaking, employment, whatever applies
- Availability, if relevant
- The questions you answer over and over in emails and messages
That last one is the highest-value item. You already know what people ask. Write the answers down once. You can also add your site's pages themselves as sources; the guide to training on your own data covers how documents and pages combine.
Add it to your site
Create the chatbot, then paste the snippet before your closing </body>:
<link rel="stylesheet" href="https://cdn.cortexvia.in/chatbotsdk-web.css" />
<script src="https://cdn.cortexvia.in/chatbotsdk-web.iife.js"></script>
<div id="cv-chat"></div>
<script>
window.ChatbotSDK.mount("#cv-chat", {
chatbotKey: "ctx-cb-xxxxxxxxxxxxxxxx",
config: { mode: "chatbot" }
});
</script>Works on plain HTML, Webflow, Framer, Ghost, Wix, Squarespace, anything with a footer code field. On React or Next.js, mount it in an effect with cleanup so navigation does not leave duplicates; the React and Next.js guides have the code.
If you would rather it be a page than a corner widget, use mode: "chat" inside a container with a fixed height and call the page "Ask me anything".
Configure it like a person, not a product
Name it in your voice. "Ask Meera" reads better than "Support".
Write a welcome message that invites specifics. "Ask about my writing, consulting, or availability."
Set your email as the support contact. Anything unanswered becomes an email rather than a bounce. On a personal site that is the entire conversion path.
Match your design. Colours, header name, and logo are configurable. A default-styled widget on a carefully designed personal site looks bolted on, because it is.
Test it honestly
Ask the five questions you get most often. Then ask something you never wrote down.
It should say it does not know and point at your email. A chatbot inventing claims about your background is a genuine risk on a site that carries your name. Check this before it goes live.
Keep it accurate
The chatbot answers from the document you gave it, so it is exactly as current as that document. New talk, new project, changed rates, changed availability: update the file and re-upload. Put it on the same checklist as updating the site itself, because a chatbot confidently describing last year's availability is worse than no chatbot.
The unexpected benefit
People who add a chatbot to a personal site usually expect it to save them email. It does. What they do not expect is what they learn from the questions: which project people are curious about, which service nobody understands, which page is missing entirely. The questions a chatbot cannot answer are a list of what to write next, and for anyone building a personal brand that list is worth more than the time saved.
Frequently asked questions
Is this overkill for a small site? A small site is where it helps most: there is less to read, so visitors leave with unanswered questions faster. The free plan covers a personal site with a document or two.
Can it book calls or take enquiries? It points people to your booking link or email; it does not run a calendar itself. Add the booking link as a support contact and every unanswered question ends with a way to reach you.
Will it talk about things unrelated to me? No. It answers from your sources and politely declines anything outside them, which keeps it on you rather than becoming a general assistant on your site. The personal website page has the short setup.
