Loading tutorials…
Loading tutorials…
Every team starts a Notion wiki. Most have 800 orphan pages by year two. This walks the structure, the verification habit, and the governance that keeps a wiki alive and useful.
Who this is forOps leads, founders, and marketing managers building or rescuing a team wiki. If your wiki has more than 200 pages and you cannot tell which ones are current, this tutorial is the rescue.
What you'll need
Step 1
Notion has a dedicated Wiki feature (turn any Teamspace into a Wiki). Wikis support verified pages, owner attribution, and dedicated search ranking.
Pick the Teamspace that will hold the wiki (e.g., 'Company Wiki' or 'Marketing Wiki').
Open the Teamspace settings → '...' menu next to the Teamspace name → 'Turn into Wiki' (in 2026, Notion expanded this from page-level to Teamspace-level).
Wiki Teamspace adds: Verified property on every page, Owner property on every page, Last verified date, and a dedicated Wiki search view.
Existing pages in the Teamspace inherit these properties. You will need to backfill Owner and Verified for legacy pages.
A Wiki Teamspace shows up differently in the sidebar (small wiki icon) and behaves slightly differently in search — verified pages rank higher.
Step 2
Wiki sections mirror the team's knowledge domains. 5-8 top-level sections is the right scope. More than that = sprawl.
Common wiki sections for a marketing team: (1) Brand & Voice, (2) Marketing Strategy, (3) Channel Playbooks, (4) SOPs & Workflows, (5) Tools & Stack, (6) Team & Roles, (7) Reports & Decisions, (8) Onboarding.
Create each as a top-level page inside the Wiki Teamspace. Add an icon and a 1-paragraph intro describing what lives there.
Inside each section, create the canonical sub-pages. For SOPs & Workflows: every recurring process gets a page (How to launch a campaign, How to publish a blog post, How to handle a refund).
Do NOT create sub-pages speculatively ('we might document X someday'). Wikis sprawl when teams pre-create empty pages 'to be filled later.' Only create a page when there is real content to put in it.
Pin the Wiki Home (top of Teamspace) with a 4-column grid linking to the 8 sections. This is the front door.
Step 3
A wiki page without an owner becomes orphan content within months. Every page needs a named human responsible for its accuracy.
On Wiki Teamspaces, every page has an Owner property (built into the Wiki feature).
Set Owner on every page. For SOPs: the function lead. For Brand pages: the brand lead. For Reports: the analyst. Never 'the team' — always a single human.
If a page has no clear owner, the page should not exist. Archive it.
When someone leaves the company, transfer their owned pages within 1 week. Notion does not auto-reassign — this is a manual handoff process.
Add a view of the Wiki Teamspace filtered to 'Owner = me' so each teammate sees their owned pages. This is what makes ownership real.
Step 4
Verified pages mean "this is current as of [date]." Unverified pages mean "this might be stale." Without verification, you cannot tell.
Wiki Teamspaces add a 'Verified' button to every page (top-right of the page). Click it → Notion sets Verified = true and Last Verified Date = today.
Verification expires after a configurable period (default 90 days on Wiki Teamspaces). Expired verifications turn into 'Needs review' status.
Set the verification cycle per page type: SOPs verify every 90 days, Brand pages verify every 180 days, Strategy docs verify every quarter.
Add a Wiki view: 'Pages needing verification' (Filter: Verified = false OR Last Verified Date > 90 days ago). Show this on the Wiki Home for owners.
Make verification a habit: every Friday, owners spend 10 minutes verifying their pages (or marking changes if content drifted). This is the single highest-impact habit for keeping a wiki alive.
Step 5
Nobody navigates a wiki sidebar past page 50. Search is how knowledge gets found. Optimize pages for it.
Use clear, searchable page titles. "How to launch a paid social campaign" beats "Paid social process" — it matches the query someone would actually search.
Front-load important keywords in the first paragraph. Notion search ranks early content higher.
Use clear headings (H1 / H2 / H3) inside pages. Notion indexes heading text separately and surfaces it in search results.
Avoid screenshots-only pages. Notion does not OCR images in search (as of 2026). A page that is 90% screenshot is invisible in search.
Add synonym section at the bottom of canonical pages: 'Also known as: [synonyms]'. Helps people who search for the unofficial term.
Set up the team's search behavior: cmd+P (or ctrl+P) is the universal Notion search. Train new hires to use it as their first navigation.
Step 6
A wiki without a deprecation process accumulates lies. Build the muscle to retire stale pages, not just create new ones.
Create an 'Archive' Teamspace (separate from the live Wiki). When a page is no longer current, move it to Archive — do not delete.
Move criteria: page has not been verified in 180 days AND nobody has edited it in 90 days AND owner confirms it is stale.
Add a redirect note at the top of archived pages: 'This SOP was archived on [date] because [reason]. See [new page] for current process.'
Run a quarterly archive sweep: open the Wiki, filter to 'Last Verified >180 days,' review each page with its owner, decide keep / update / archive.
Without archiving, wikis grow forever. Within 2 years, a no-archive wiki has 80% stale content and the team distrusts everything in it.
Step 7
A page in the wiki should look like a wiki page, not someone's scratch notes. Standards keep quality high.
Create a Wiki page called 'How to write for the wiki' under SOPs.
Document: page structure (intro paragraph → table of contents → content sections → "Last updated by" callout), tone (operational, terse, present tense), naming conventions (action verbs in titles).
Document: must-have elements on every SOP page (overview, prerequisites, step-by-step instructions, common pitfalls, owner).
Document: what does NOT belong in the wiki (drafts, personal notes, meeting transcripts — those live in Private or in dated subpages).
Link this contribution guide from the Wiki Home. Have every new hire read it in week one.
Common mistakes
No verification process — every page is "current" or "not"
What goes wrong: Team cannot tell if the SOP they are reading is from 2024 or 2026. People follow stale SOPs and create real downstream errors (wrong onboarding steps, deprecated tools, outdated processes). Cost of one bad SOP propagated: $5-20K depending on the process.
How to avoid: Use Wiki Teamspace Verification. Set a 90-day verification cadence on SOPs, 180-day on Brand. Build the Friday verify habit for owners.
Wiki sprawl past 500+ pages with no archive
What goes wrong: Search returns 14 results for 'campaign launch' and 11 are stale. Team gives up on wiki and asks in Slack. Slack becomes the de-facto wiki, but Slack is not searchable across years. Productivity loss for a 10-person team: $8-15K/yr in search and rework.
How to avoid: Run quarterly archive sweeps. Move stale pages to Archive Teamspace, not delete. Always link the replacement page at the top of the archived original.
Pages without owners
What goes wrong: When someone leaves, their pages have no one to maintain them. They go stale within 6 months. The wiki is full of zombie content that looks current but is unowned. Hidden cost: bad decisions made from zombie SOPs = $10-30K/yr.
How to avoid: Every page has an Owner property. If a page has no clear owner, archive it. When someone leaves, formal handoff includes owned-pages transfer.
Page titles that nobody would search for
What goes wrong: Page titled 'Q2 internal process update v3 FINAL' is invisible in search because nobody searches for that string. People recreate the content elsewhere because they cannot find the original. Pure waste.
How to avoid: Title pages with the question they answer: "How to publish a blog post," "What is our brand voice," "When to use [tool X] vs [tool Y]." Front-load keywords.
Sidebar with 30+ top-level pages
What goes wrong: New hires cannot navigate. They Slack their manager 'where is the brand book?' every time. Onboarding cost increases by 2-4 weeks of ramp time. For a single new hire, that's $5-15K of delayed productivity.
How to avoid: Cap top-level Wiki sections at 5-8. Build the Wiki Home as a 4-column grid linking to each section. Train search-first navigation.
Mixing operational SOPs with brainstorm drafts
What goes wrong: Half the pages in the wiki are half-finished thinking, not real SOPs. Team cannot tell what is canonical. Trust in the wiki erodes within a quarter.
How to avoid: Drafts go in Private or in a clearly-marked Drafts subsection. Wiki contains finished, verified content only. Move drafts in only after verification.
Recap
Done — what's next
How to set up a Notion workspace for marketing without it becoming a dumping ground
Read the next tutorial
Hand it off
A team wiki is one of the highest-ROI ops investments and one of the easiest to let rot. The difference between a wiki that compounds value and one that becomes a graveyard is governance, not structure. A specialist will set up the Wiki Teamspace, build the section skeleton, assign owners, install the verification cadence, and document the contribution standards. One-shot $300-600; ongoing wiki ops support runs $400-1,200/mo at $14-16/hr.
See specialist rates
Notion Wiki works for teams under ~100 employees who already use Notion for docs. The advantage: one tool, lower cognitive load, no SSO sprawl. Confluence wins at >200 employees, regulated industries, or when you need very deep page hierarchies. For most marketing teams, Notion is the right call.
Structural setup: 3-5 hours (Teamspace, sections, Home page). Migrating existing content: 1-2 weeks of part-time work depending on volume. Building the verification habit so it sticks: 4-8 weeks of weekly nudges. The setup is fast; the habit is slow.
Move them OUT of the main Wiki Teamspace into a separate Closed or Private Teamspace (Business+ for Private). Wiki search is workspace-scoped — confidential pages should not be in the same Teamspace as the public wiki.
Three patterns: (1) add a 'Also known as: [synonyms]' line at the bottom of the canonical page, (2) create redirect pages for common alternate spellings ('Cost per Acquisition' → redirects/links to 'CPA explained'), (3) train the team to use the universal cmd+P search and to trust the top result.
Notion Sites (rebranded from Notion Public Pages in 2026) lets you publish pages as websites. Useful for: public-facing brand guidelines, hiring pages, changelog. Be careful: anything published externally must be reviewed for confidential info first. Build a separate 'External' subsection with its own owner and review process.
Notion
Notion is the easiest tool to spin up and the hardest to keep tidy. Three months in, most marketing workspaces have 400+ orphan pages, three competing content calendars, and a sidebar nobody can navigate. This walks the setup that holds up past the honeymoon.
Notion
Templates and buttons are how you turn Notion from a doc tool into an ops tool. They are also the features most teams skip. This walks the patterns that save 5-10 hrs/week.
Notion
Notion looks easy. Running a real ops system in Notion is not. This walks the honest signals that you have crossed the line from 'DIY is fine' to 'this is costing more than help would.'
ClickUp
ClickUp Docs is the feature most teams ignore — and the one that turns ClickUp from a task tracker into a real Work OS. Done right, it replaces Notion or Confluence for your SOPs, playbooks, and team wiki. Done wrong, it becomes a 47-Doc dumping ground nobody opens.