Job search
Notion Sites Review for a Job-Search Portfolio: Free Pages, Paid Features, and Domain Add-Ons
Two completed fictional decisions show a sanitized four-page QA portfolio and one-seat/domain billing choices, with public-access and renewal boundaries.
Notion Sites can present a job-search portfolio without a hosting subscription if a public notion.site address and basic presentation meet your needs. Paid plans add customization and other features; using your own domain requires a separate add-on on top of a paid workspace. The more consequential first decision is which pages, database entries and contributor information you are prepared to make public.
LandOffer publishes this review and offers job-search tools. We reviewed Notion’s public documentation and pricing on October 21, 2026, without creating an account, publishing a page, uploading work samples or connecting a domain. While preparing your portfolio, browse jobs posted in the past 24 hours to keep its examples relevant to actual roles.

Free publishing already covers a basic portfolio
Notion’s Sites availability guide says Free workspaces can publish unlimited Sites, claim one notion.site domain and turn on search engine indexing. Several public case pages and basic search indexing are available without a paid workspace.
That describes publishing capacity, not unlimited capacity for every kind of content. The current pricing comparison lists unlimited pages and blocks for individuals, limits for Free workspaces with two or more members, and a 5 MB file-upload limit on Free. Check an actual artifact’s size before assuming a large PDF or video can be uploaded on that plan. We did not test uploads or media playback.
A candidate who needs a readable introduction, a few authorized case studies and ordinary links may have no immediate reason to buy advanced branding. Give each case a clear ownership statement, useful evidence and a destination the recruiter can access. A page becoming public does not establish that its attachments, external repositories or embedded material will work for a recruiter.
Notion’s publication guide says anyone on the web can view a published Site. That is different from inviting a specific person to a private workspace page. If a work sample must remain restricted, choose an appropriate private-sharing route rather than treating an obscure public address as confidentiality.
What payment changes, and what a custom domain adds
Paid plans include Site customization, a domain Homepage, Google Analytics integration and up to five notion.site domains. The customization documentation describes navigation, themes, share previews, page titles and descriptions. Paid plans also support custom URL slugs; each page’s slug must be set separately, rather than automatically applying to its subpages.
These documented controls let you arrange navigation and label share previews; their effect on a particular portfolio was not measured. They do not establish a hiring advantage or a measured improvement in recruiter engagement. Google Analytics integration is a documented option, not something we connected or tested. A candidate can decide that additional tracking is unnecessary for a simple application portfolio.
| Requirement | Documented route | Important boundary |
|---|---|---|
| Public cases on a Notion address | Free Sites | Public access requires a content and permission review |
| Search-engine indexing | Available on Free and paid plans | Enabling it is not immediate inclusion or a ranking guarantee |
| Customized navigation and share preview | Paid Site customization | Presentation controls do not establish content quality |
| Existing custom domain | Paid workspace plus domain add-on | Domain registration remains separate |
| Remove the Notion watermark | Custom-domain Site option | Paying for a workspace alone is insufficient |
Notion does not sell the custom domain or replace its registrar. Workspace owners on paid plans can connect an existing domain by purchasing an add-on for each domain. The help guide lists an additional $10 per month with monthly billing or $8 per month with annual billing. The add-on must follow the workspace’s billing cadence, and the documentation permits up to 25 custom domains, each requiring its own add-on.
The connection guide also requires a subdomain and provider-side configuration. A registered domain, a paid workspace and an unverified setup are three different states. No connection was attempted for this review, so we cannot claim that a particular applicant’s root address, redirect or custom-domain route works.
Public pages need a separate review from working notes
Publishing a Notion page also publishes its subpages by default, including deeper descendants. Notion says subpage permissions can be restricted, but the safe editorial starting point is to inspect the entire proposed public tree. A folder of useful working notes is not automatically a suitable portfolio root.
The publication guide says visitors can switch database views and open pages within a published database. Review the underlying content and access rules instead of assuming the initially displayed view describes everything a visitor can reach. A tidy presentation view is not evidence that sensitive source records are protected.
There is another easy-to-miss disclosure: Notion says webpage metadata can include names, profile photos and email addresses associated with users who contributed to a page when it is published or shared with anyone on the web. Sanitizing the visible case text alone does not resolve that metadata question. Collaborator consent and the identities involved deserve their own check.
Changes to a published Notion page update the Site automatically. Automatic updates make corrections convenient. Keep interview notes, internal comments and unapproved screenshots out of that same public page. Keep a separate drafting area so new notes do not become public edits.
Worked content decision: Julia’s four-page presentation tree
Julia is a fictional junior QA engineer. All projects and decisions in this example are invented. She wants to show three kinds of contribution: an API-pagination test plan, a browser compatibility investigation and a manual accessibility review. She has permission to describe the stipulated public versions; this is not a review of a real employer’s disclosure rules.
Her initial working root contains those cases, a bug diary, a database of project notes and interview feedback. She rejects publishing that root. The revised presentation tree contains one introduction and three case pages, each stating her own role, the evidence available and the limits of the work.
| Item in the working collection | Completed editorial decision | Reader-facing result |
|---|---|---|
| API-pagination case and raw customer examples | Keep an invented input/output illustration; exclude customer payloads | Explain the tested boundary without exposing records |
| Compatibility case and private bug diary | Keep the authorized finding and her investigation steps; leave diary outside the public tree | Show contribution without publishing every work note |
| Accessibility case and draft notes naming colleagues | Use a scoped summary; hold contributor metadata for review | Avoid implying a complete accessibility certification |
| Project database with mixed approved and unapproved entries | Do not embed the working database | Link only the three selected presentation pages |
| Interview-feedback page | Exclude from the presentation tree | Keep job-search notes separate from work evidence |
Her completed plan is four public-facing pages, not the whole working collection. The API case explains what Julia checked; the compatibility case separates her investigation from a developer’s fix; the accessibility case identifies a limited manual review rather than claiming comprehensive compliance.
Julia chooses Free as the initial publishing tier because this brief does not require a custom domain or paid navigation. That is a plan choice, not a claim that the site is ready to publish. Before release, Julia still needs to review contributor metadata, inspect every nested page and verify each external evidence link. Until those checks pass in her hypothetical workflow, the decision is hold publication, not “hide the questionable page in another database view.”
Turning off template duplication would be appropriate to her stated preference not to offer a reusable template, but it would not make public content confidential. In this example no template was duplicated, no permission changed and no page published. The completed asset is a content-selection decision with a defined outstanding release gate.

Worked cost decision: one seat, one domain and two billing cadences
Eden is another fictional candidate, evaluating an independent personal workspace. He needs one paid seat and one existing domain for a 12-month portfolio. The public pricing page showed Plus at $10 per seat per month with yearly payment selected, and $12 per seat per month with monthly payment selected. We inspected the selected payment controls and both amounts; no account-specific quote or tax total was obtained.
Using those public amounts, one annual Plus seat is $120 for the year. One annually billed domain add-on is another $96. Their combined modeled annual cost is $216, before the separate registrar charge and any applicable tax. The domain add-on’s $8 monthly equivalent is not the whole hosting-and-workspace bill.
| Eden’s stipulated scope | Yearly-billing model | Twelve monthly bills model |
|---|---|---|
| One Plus seat, one custom domain | $120 + $96 = $216 | 12 × ($12 + $10) = $264 |
| One Plus seat, two separately charged domains | $120 + $192 = $312 | 12 × ($12 + $20) = $384 |
| One domain added to an already-budgeted annual paid workspace | $96 incremental add-on | Not a matching monthly add-on on an annual workspace |
The one-domain annual model is $48 below twelve monthly bills; the two-domain difference is $72. These are checked arithmetic under unchanged public-rate assumptions, not promised renewal prices. A second custom domain increases the annual add-on by $96 even though the paid plan already permits multiple notion.site domains.
Eden does not need the second domain and declines it. If he were already paying for an eligible annual workspace for other reasons, the relevant additional Notion charge for one domain would be $96, while his existing workspace expense would still exist. Counting that expense as zero for every new reader would misstate the full purchase.
His shorter alternative is three monthly bills: 3 × ($12 + $10) = $66, plus registrar costs. This is a three-cycle cost model, not a claim that three calendar months always align with an arbitrary application deadline. Annual billing has the lower monthly equivalent but the larger initial modeled commitment. Eden chooses the monthly route for a stipulated three-cycle need and records the next renewal as a decision point; no subscription was purchased or cancelled.
Notion’s public cancellation FAQ says monthly and annual subscriptions renew automatically until cancelled, with paid features remaining through the billing cycle after cancellation. The domain guide says adding an add-on mid-cycle creates a prorated charge before it joins the regular billing cadence. Eden would therefore check the actual invoice dates rather than applying a full-year estimate to a partial first term.
Keep the link, the content and public access distinct
Notion warns that changing a notion.site domain makes links using the previous domain stop working. Before renaming a domain, account for the old links already sent with applications. The management guide also says Notion can reclaim a notion.site name and requires active workspace use to maintain a customized name.
Unpublishing a Site is not necessarily the same as removing all public access. The publication guide says a page can remain accessible through its separate “Anyone on the web with link” setting. Check both states if the objective is to withdraw public content. This review did not change either setting or test a removal.
For continuity, Notion documents HTML and Markdown/CSV exports, with options to include subpages and associated assets. It also says reuploading an exported workspace cannot instantly recreate it. Treat exported content as material to inspect and preserve, not proof of an identical functioning portfolio, permissions or custom-domain site elsewhere.
Notion Sites is a reasonable option to investigate when the priority is maintaining clear text-and-evidence pages in an existing document workflow. Start with the public content boundary and the free route; pay for a specific presentation or domain requirement you can name. Keep the portfolio’s purpose grounded in your work and continue your job search with LandOffer.


