How to Create a Wiki in Google Docs (Step by Step + Free Template)
Build a working team wiki in about an hour, copy a free folder template, and see where the do-it-yourself approach stops scaling.

You can build a working team wiki in Google Docs in about an hour: a shared drive, a simple folder structure, a home page, consistent headings and links between pages. This guide walks through each step, gives you a free folder template to copy, and shows where the do-it-yourself approach stops scaling, plus how to fix that without moving a single doc.
Most teams already write in Google Docs. There is no new editor to learn, co-editing and comments just work, version history is built in, and access is managed in Google Drive, which your admin already controls. That makes Google Docs a natural place to start a wiki. What it lacks is the part that turns a pile of documents into a knowledge base: structure, navigation and a way to find things.
What a team wiki needs
A wiki is not just a folder of documents. It works when people can find an answer in under a minute without asking a colleague. That takes five things, and Google Docs gives you some of them for free.
| Need | What it means | In plain Google Docs |
|---|---|---|
| Structure | Every page has an obvious home | Folders in Google Drive |
| Navigation | You can browse from a home page to any page in a few clicks | A home doc you keep up to date by hand |
| Search | You find a page by what it says, not only its title | Google Drive search, mixed with every other file you own |
| Linking | Pages point to related pages | Links and @-mentions you add yourself |
| Ownership | Every page has an owner and a review date | A line you add at the top of each doc |
The steps below cover all five with nothing but Google Docs and Drive.
How to create a wiki in Google Docs, step by step
1. Create a shared drive for the wiki
Put the wiki in a shared drive, not in someone's My Drive. Files in a shared drive belong to the team, so nothing disappears when the person who created a page leaves. If your plan has no shared drives, use one shared folder owned by a team account.
2. Plan a shallow folder structure
Pick one way to organize the top level, usually by topic or by team, and keep the tree two or three levels deep. Deep trees hide pages and make permissions hard to follow. Start each top-level folder name with a number (01, 02, 03) so Drive keeps them in your order instead of alphabetical order. The template below gives you a starting point, and our guide to Google Drive folder structure for teams has more templates and rules.
3. Write a "Start here" home page
Create one doc at the top of the drive called "00 Start here". It explains what the wiki covers, links to every section and says who to ask when something is missing. This page is your navigation, so it has to stay current.
4. Use heading styles in every doc
Format titles and sections with real heading styles (Heading 1, Heading 2, Heading 3), not bold text. Headings power the document outline, the table of contents and links to a specific section. A doc without headings is one long wall of text.
5. Add a table of contents to long pages
For any page longer than a screen, use Insert > Table of contents. Readers can also open the outline from the left side of the doc. If a page grows into several parts, split it with document tabs or into separate docs.
6. Link pages to each other
Select text and press Ctrl+K (Cmd+K on a Mac) to link to another doc, or type @ and a file name to insert it as a smart chip. You can also link straight to a heading inside a doc. Every page should link back to its section on the home page. More in how to link Google Docs together like a wiki.
7. Agree on naming rules
Name pages the way people search for them: "Expense policy", not "Policy v3 FINAL". Remove "Copy of" from duplicated templates. One topic, one page: when two docs cover the same thing, merge them and leave a link.
8. Set permissions on folders, not on single docs
Give edit access to the people who own each section and view or comment access to everyone else. Set it on the folder so new pages inherit it.
9. Give every page an owner and a review date
Add one line under the title: who owns the page and when it was last checked. Outdated pages are the main reason people stop trusting a wiki, and an owner is the only fix that lasts.
10. Put the wiki where people already look
Pin the home page link in your team chat channel, add it to your onboarding checklist and ask everyone to add a shortcut to the drive. A wiki nobody can find is a wiki nobody uses.
Free template: a wiki folder structure you can copy
Copy this structure into a new shared drive and rename the sections to fit your team. The number prefixes keep folders in this order in Google Drive.
Company Wiki (shared drive) ├── 00 Start here ├── 01 Company │ ├── Mission and values │ ├── Who's who │ └── Holidays and time off ├── 02 Onboarding │ ├── First day checklist │ ├── First 30 days │ └── Tools and accounts ├── 03 Teams │ ├── Engineering │ ├── Product │ ├── Sales │ └── Support ├── 04 How we work │ ├── Meetings and rituals │ └── Processes and how-tos ├── 05 Policies └── 99 Archive
The "00 Start here" page can follow this outline:
- What this wiki is for, in two sentences
- The sections, each with a link and one line on what it holds
- The five pages new people read first
- Who owns the wiki and how to suggest a change
- Where to ask when you can't find something
Where the do-it-yourself wiki breaks down
The manual setup works well for a few dozen pages. As the wiki grows, the same weak spots show up in almost every team:
- Navigation goes stale. The home page is a list someone updates by hand. New pages get added to Drive but not to the home page, so they are invisible to anyone who browses.
- No sidebar. Inside a doc there is no tree of the rest of the wiki. Readers jump back to Drive, lose their place and give up.
- Search finds files, not answers. Drive search mixes wiki pages with every spreadsheet, draft and attachment people own.
- Docs look like drafts. Toolbars, page margins and edit cursors make a finished guide feel like work in progress, especially for new hires and customers.
- Other knowledge lives elsewhere. Figma designs, Miro boards and Loom videos can only be pasted in as links.
- Sharing outside is clumsy. Publish to the web works one doc at a time and gives each page a bare URL, with no navigation between them.
None of this is a reason to leave Google Docs. Writing in Docs is the part that works. What's missing is a layer on top that does the navigation for you.
The faster way: turn your Google Docs into a wiki with Spaceli
Spaceli turns a Google Drive folder into a structured, good-looking wiki in about a minute. Folders become sections, docs become pages, and nothing is copied or migrated. You can edit right inside Spaceli, and every change syncs both ways with Drive. Steps 3, 5 and 10 above happen on their own, and step 6 gets easier: links between docs in the same space open right inside the wiki, down to a specific heading.
- Sign in with Google. Colleagues from your company domain can join your organization automatically, or request access for an admin to approve.
- Create a space from a folder your team already uses, or start fresh and Spaceli creates the folder in Drive. Shared drives work too.
- Invite your team. When you connect an existing folder, Spaceli offers to invite everyone who already has access to it in Drive, with their roles carried over: editors stay editors, viewers stay viewers.
Your folders become the sidebar, in an order you set with drag and drop. Headings become a table of contents that highlights where you are, and every doc gets the same clean typography, however it was styled in Google Docs. Admins can set a default space, so everyone in the company lands on the wiki when they open Spaceli.
| Wiki in plain Google Docs | Wiki with Spaceli | |
|---|---|---|
| Navigation | Home page you update by hand | Sidebar built from your Drive folders, in the order you choose |
| Table of contents | Inserted in each doc | On every page, highlighting the section you're reading |
| Search | Drive search across all your files | Cmd+K search across the space: titles instantly, plus the full text of every doc |
| Reading view | The Docs editor | Clean, consistent typography in light and dark mode |
| Rich formatting | Basic | Callouts (Note, Tip, Warning, Danger, Success) and code blocks with syntax highlighting and a copy button, all written in Google Docs |
| Other content | Links | Sheets, Slides, PDFs and videos open inside; Figma, Miro, Loom, YouTube and other embeds live on the page |
| Editing | Google Docs | Right inside Spaceli: the Google Docs editor opens in the page (Cmd+E), and sync and refresh run on their own when you're done |
| Access | Set in Drive, doc by doc | Space roles, reflected on the Drive folder; external collaborators invited per space |
| Customers | Publish each doc to the web | A public space anyone with the link can read, no account needed |
| Look | Docs default | Five color themes, set per space |
| Your data | In your Drive | Still in your Drive and synced both ways: stop using Spaceli and every doc stays where it is |
A few things a homemade wiki can't do: copy any page as clean Markdown for AI tools or a README, pin up to three quick links in the space header, and hide a page from the wiki without deleting it in Drive. For other tools that do this, see the best tools to turn Google Docs into a wiki.
FAQ
Can you use Google Docs as a wiki?
Yes. With a shared drive, a clear folder structure, a home page and consistent headings, Google Docs works as a basic wiki. It gets harder to navigate as it grows, which is where a tool like Spaceli helps.
Is there a wiki template for Google Docs?
Google Docs has no built-in wiki template. Use the folder structure and home page outline in this guide as your starting point.
Google Sites or Google Docs for a company wiki?
Google Sites gives you a website with navigation, but every page and menu is built and updated by hand, and the content often still lives in Docs. Writing in Docs and adding navigation on top keeps one source of truth. More in Google Sites as a company wiki.
How do I share a Google Docs wiki with customers?
Publishing to the web works for single docs. To share a whole knowledge base with navigation and search, make a Spaceli space public: anyone with the link can read it, no account needed. For clients who should see only their own docs, invite them to a private space as external collaborators.
Will Spaceli move or copy my documents?
No. Your docs stay in your Google Drive, and new pages you create from Spaceli are created in the space's Drive folder. Spaceli keeps no permanent copies of your documents, only works with the folders you connect and can't see the rest of your Drive.
Does Spaceli replace Google Docs?
No. You keep writing in Google Docs, and you can edit right inside Spaceli: the Google Docs editor opens in the page, and syncing happens on its own. Spaceli adds the structure, navigation, search and reading view.

Writes about wikis, documentation and how teams keep their knowledge easy to find.
Keep reading
All articles →How to Build a Public Help Center from Google Docs
Turn a Google Drive folder into a public help center customers can read without signing in. Plan it, write it in Google Docs and keep it current.
Google Drive Folder Structure for Teams: A Template That Scales
A Google Drive folder structure that scales: five rules plus copy-ready templates for startups, agencies and engineering teams.
How to Build a Company Knowledge Base in Google Drive
Build a company knowledge base in Google Drive: what to include, how to structure it, who owns what, and how to make it easy to find.
Your knowledge base is already in Google Drive.
Give your team a better way to organize, find, and share knowledge. Keep your documents right where they are.
Start for FreeFree during the beta. Get started in about a minute.
Spaceli only accesses the folders you choose.