Using Notion global blocks to create a navigation bar
Based on Tools on Tech's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Build the navigation bar as a heading (heading 1) populated with emojis, then link each emoji to a destination page.
Briefing
A Notion navigation bar can be made fast, clickable, and consistent across many pages—without manually updating the same header dozens of times—by combining emoji-based links with Notion global blocks. The payoff is a day-planner style “top bar” that lets users jump between key sections (home, quick log entries, and life territories) with a single click, even as a Notion workspace grows into a sprawling tree view.
The build starts with a simple header: create a large heading using “#” (heading 1), then add emojis for each destination—home, a day-start log page, and separate “start pages” for major life areas. The header itself is initially non-clickable, but it becomes clickable once the emoji (and importantly the space after it) is selected before inserting a link. That spacing detail matters because it controls how Notion renders the underline: selecting the space yields a clean single-line underline, while skipping it can produce a dotted line.
Linking each destination is straightforward when the target page is known, but Notion’s internal link search can fail for this workflow. The workaround is to open the destination in a browser, copy the page URL from the address bar, paste it into Notion’s link field, and confirm. The result is an emoji icon in the header that jumps directly to the intended page.
The challenge comes when the same navigation bar must appear on many pages. Copying the header to multiple pages quickly turns into maintenance debt: adding or changing an emoji on one page won’t automatically update the others, and updating five, ten, or a hundred pages becomes painful.
Global blocks solve that by letting one “source” block update propagate everywhere it’s used. The method is to create a global header block (stored in a templates folder) and include the linked header content there. Then, on other pages, paste a global-block version of the header so edits made in the global source reflect across all instances. The transcript notes that pasting can be finicky: copying from a code block may introduce formatting issues, so using a paste-without-formatting shortcut (Control+Shift+V) helps ensure the global block works correctly.
To convert a normal link into a global link, the URL needs trimming—removing the extra path segments between the slash and the end—so the resulting link points to the global block target. For people who don’t want to hand-edit URLs, the workflow includes a regex101-based substitution approach: paste the original URL into a test string, highlight what will be replaced, and copy the “substitution” output as the modified URL. Once that global link is pasted into the header area and linked to the page, the navigation bar becomes centrally editable.
Beyond navigation, global blocks also support other repeatable elements like signatures—anything that should stay consistent across many Notion pages without rework.
Cornell Notes
A Notion top navigation bar can be built from emoji-based links inside a heading, but keeping it consistent across many pages is the real problem. Global blocks provide a fix: create the header once as a global block, then paste the global-block version onto other pages so changes (like adding a new emoji) automatically appear everywhere. The workflow relies on proper link formatting—selecting the emoji plus the trailing space for clean underlines—and on using page URLs when Notion’s link search doesn’t surface the target. When pasting global blocks, use paste-without-formatting (Control+Shift+V) to avoid formatting glitches. For turning a normal link into a global link, trimming the URL or using a regex101 substitution output makes updates manageable even without code fluency.
How does the emoji header become clickable in Notion, and why does selecting the trailing space matter?
What’s the workaround when Notion’s link search doesn’t show the page you want?
Why does copying the same navigation bar to multiple pages become a maintenance problem?
How do global blocks prevent that maintenance burden?
What’s involved in turning a normal link into a global link?
Review Questions
- What two small formatting choices make emoji links look and behave correctly in the header (including the underline behavior)?
- Why does paste-without-formatting (Control+Shift+V) matter when using global blocks?
- Describe two ways to convert a normal link into a global link and explain when you’d use each.
Key Points
- 1
Build the navigation bar as a heading (heading 1) populated with emojis, then link each emoji to a destination page.
- 2
Select the emoji and the space after it before inserting the link to get a clean single-line underline.
- 3
If Notion link search fails, copy the destination page URL from a browser and paste it into Notion’s link field.
- 4
Avoid copying the header to many pages manually; updates won’t propagate and maintenance becomes unmanageable at scale.
- 5
Use Notion global blocks so edits to the global header (like adding an emoji) automatically appear on every page using it.
- 6
When pasting global blocks, use Control+Shift+V to prevent formatting issues that can break the expected result.
- 7
Convert normal links into global links by trimming the URL or by using a regex101 substitution output for a repeatable workflow.