How to make a D&D campaign website your players will open
A D&D campaign website is the one link your players get: the campaign primer, the house rules and schedule, who is in the party, the people they have met and the story so far. Build it in whatever you can keep current with the least effort, because the sites that die are the ones only the DM can update. A free Google Sites or Notion page covers most tables; pick something heavier only when you need passwords, a wiki, or a site that fills itself in from your sessions.
· 6 min read
What a campaign website is for
A campaign website answers the questions players ask in the group chat, so you stop answering them one by one: what is this campaign, when do we play, what are the table rules, who is my character again, and what happened while I was away. It is for the players. Your prep, your secrets and the world you have not shown them yet belong somewhere else.
That makes it a different thing from a campaign wiki, although the two overlap. The wiki is the record of play, entry by entry. The website is the front door: a handful of pages a new player can read in ten minutes, with the wiki (if you keep one) linked from it. Many tables only ever need the front door.
What to put on a D&D campaign website
Six pages cover nearly every table. Start with the first two before session zero and add the rest as play gives you something to put on them.
The campaign primer. One page: the pitch, the tone, the starting location, what the characters know, and what kind of game it is not. It is the page players read before character creation, so it carries your session zero decisions.
Table info. The schedule and where you play (an address or the Discord server), house rules, the safety tools you agreed on, and what happens when someone cannot come.
The party. One line per character with the player's first name or handle, the class and a portrait if they want one. New players use it more than anyone.
People and places met. Only what the characters know, in the words they would use. This is the page that grows; if it gets long, it is turning into a wiki, and the NPC tracker template is a good shape for it.
The story so far. A short recap per session, newest first. It is the page a player opens when they missed a session, and the hardest one to keep current. See how to write a session recap for a five-minute format.
Handouts. Maps, letters and images you have already shown at the table.
A campaign primer template
Copy this into the first page of the site and replace every line. Keep it to one screen; anything longer will not be read before session one.
D&D campaign primer template (copy this)
CAMPAIGN PRIMER - <campaign name> THE PITCH (two sentences) <What the characters are doing and why it matters now.> TONE <e.g. heroic, grim, comedic, political; how deadly combat is.> WHERE YOU START <Town or region, and the one problem everyone there is talking about.> WHAT YOUR CHARACTER KNOWS <Common knowledge: rulers, factions, rumours. Nothing secret.> CHARACTER RULES <System and edition, allowed sources, starting level, how stats are made.> THIS IS NOT <What the campaign will not include: content limits, play styles.> TABLE <Day and time, place or server, how to say you cannot make it.>
Five ways to host a D&D campaign website
The best host is the one you will still open in month six. Pick by two questions: who will update it, and who should be able to read it.
Google Sites is the common default, and most campaign sites in search results are built with it. Pages are drag-and-drop, players can be added as editors, and when you publish you choose Public or Restricted, so a site can be limited to the people you share it with.
A public Notion page. If your notes already live in Notion, publishing a page to the web is included on Notion's free plan and players get a link. A custom domain costs extra (see the table below). Keep secrets on a separate page, because everything under a published page is easy to publish by accident. Our Obsidian and Notion comparison covers both as campaign tools.
GitHub Pages suits a DM who is comfortable with Git or Markdown: a static site, free from a public repository, at a github.io address. On GitHub's free plans the repository must be public, so treat everything in it as public.
Obsidian Publish turns an Obsidian vault into a site with its links and graph intact, and can be protected with passwords. It is paid, per site.
A public Kanka campaign. Kanka is a campaign manager with a wiki shape already built in. Setting a campaign's visibility to public gives everyone outside it read-only access through a public role, and they see only what that role is allowed to see, entry by entry.
World Anvil and LegendKeeper also publish worlds to readers, but both are worldbuilding platforms first; if you are not already authoring your setting there, a lighter host is less to maintain.
Public, link-only or private: who should be able to read it
Decide this before you write anything, because it changes what you can put on the site.
A public site can be found by anyone and, eventually, by search engines. That is fine for a primer and house rules. It is not fine for players' real names, your address, or a schedule that says when a house is empty. Use first names or handles.
A link-only site is not listed but is readable by anyone who has the link. Links get pasted into other servers, so assume it will travel.
A restricted site (Google Sites' Restricted option, Obsidian Publish passwords) is the only kind that stays inside the table. Use it if your players are minors, if the campaign uses real people or places, or if the story-so-far page records anything personal said at the table.
Spoilers are a separate question. Whatever the setting, never put on the site anything you would not say out loud at the table. A hidden page is still a page.
Keeping the site current without it becoming a second job
Campaign websites usually die on the story-so-far page. The primer is written once; the recap has to be written every week, by the person who also has to prep the next session.
Three things help. Let players write: a rotating scribe who posts the recap, or one player per page (the party page is a good first assignment). Keep the format small: five bullet points per session beats a page you never finish. And link the site where players already are, pinned in the Discord channel or the group chat's description; see how to run D&D on Discord for a channel layout that has a place for it.
Update the site in the ten minutes after a session, while you still remember the names, and skip a week rather than rewriting from memory a month later.
If you record your sessions, the people and recap pages can fill themselves in
The two pages that grow every week are the two that DM Scribe writes. It transcribes a recorded or uploaded session, writes the recap, and builds a campaign wiki of the people, places and items mentioned. The wiki is on the free plan.
You can share that wiki with your players as a read-only link: players open it in a browser with no account and cannot edit anything, private GM notes on each entry are never sent, and the shared view stays current as new sessions process, with a session list beside the entries. Share links are not indexed by search engines, expire after at most 90 days and can be revoked. Sharing needs the Dungeon Master plan ($7.99 a month) or Guild Master.
What it does not do: it is not a site builder, so the primer, house rules and schedule still go on a page you write. The usual pattern is a small Google Sites or Notion front page with the primer and table info, linking to the shared wiki for the people, places and story so far.
What each host says about itself, with sources
Every third-party figure quoted above, with where it came from and when it was checked. Prices move — if a date here is old, verify before relying on it.
| What | Value | Source |
|---|---|---|
| Google Sites: who can see a published site | "Next to 'Published site,' from the drop-down list, select Restricted or Public." Restricted lets you "share your site with specific people and add groups." | sourceas of 2026-11-16 |
| Notion: publishing and custom domains | Free plan includes "Publish a Notion page to the web"; custom domain "$8/month/domain paid annually, or $10/month per domain paid monthly" | sourceas of 2026-11-16 |
| GitHub Pages: free plans, address and limits | On GitHub Free "the repository must be public"; sites at <owner>.github.io; "no larger than 1 GB"; "soft bandwidth limit of 100 GB per month" | sourceas of 2026-11-16 |
| Obsidian Publish: price and passwords | $8 per site per month billed annually, $10 billed monthly; "Restrict access to your site with the ability to manage multiple passwords" | sourceas of 2026-11-16 |
| Kanka: public campaigns | Set "Campaign visibility" to public; "The public role only has read permissions, and is used by all users not part of the campaign" | sourceas of 2026-11-16 |
How we sourced this: Each row quotes the vendor’s own page, read on that date. Prices and plans change; check the linked page before you build. The advice and the page list are ours.
Related guides
- How to start a D&D campaign as a DM: the setup, in order
Start a D&D campaign in seven steps: the game, the players, a schedule that holds, session zero, session one and the notes. Which step stalls yours?
- How to record your D&D session — in person or online — so the audio is actually usable
Where to put the mic at a real table, how to record Discord and Zoom games, cheap gear that helps, and what good enough session audio actually means.
- How to Take Notes During a D&D Session Without Wrecking the Game
You cannot run the game and write it down at once. What earns one line mid-session, what can wait until after, and who takes the notes when nobody will?