Notion 2026 Controversy: 5 Changes That Split the User Base

Quick Verdict: Between May 2025 and April 2026, five distinct Notion changes generated sustained community pushback that is still active in 2026 discussion. None of them shut Notion down. None of them are settled. Each one shifts a different trade-off for a different group of users.

Here are the five changes, in chronological order, that this article unpacks:

1. AI add-on cancellation and Business-plan bundling (announced April 2025, effective May 2025) — full Notion AI access now requires the Business plan at $20/user/month.
2. Offline mode launch with significant limits (August 2025) — six years after Notion CEO Ivan Zhao acknowledged it as the #1 requested feature, the launch capped database sync at 50 rows and required manual per-page toggles.
3. API version 2025-09-03 breaking change (announced August 2025, effective September 2025) — database_id was split into database_id plus data_source_id, breaking n8n, Retool, and many low-code Notion integrations.
4. Notion 3.0 AI Agent prompt-injection vulnerabilities (September 2025 origin, January 2026 second disclosure) — security researchers from CodeIntegrity and PromptArmor demonstrated data exfiltration paths; Notion deployed a remediation the day after public disclosure.
5. Notion Sites SEO gaps and a November 2025 noindex bug — public Notion sites were temporarily injected with <meta name="robots" content="noindex" />, on top of long-standing per-page meta and schema limitations.

This article walks through each change with primary sources, data points, and quotes from both critics and defenders, then closes with neutral guidance for the user groups above.

How We Researched This

We built this analysis from primary discussion sources rather than secondary tech-press summaries.

What counted as a primary source: Reddit user posts on r/Notion, Hacker News submissions and comments fetched from the HN Firebase API, GitHub issues filed against makenotion/*, n8n-io/n8n, ramnes/notion-sdk-py, and other affected ecosystem projects, the Notion Help Center, the Notion Developers documentation, the Notion Engineering Blog, PromptArmor’s disclosure post, the CodeIntegrity research blog, Schneier on Security, and Simon Willison’s personal blog.

What we treated as secondary: TechCrunch, The Verge, XDA, MakeUseOf, and similar outlets — useful for context but not counted toward our “≥1 primary source per controversy” requirement.

The 2026 active-discussion test: Each of the five controversies we cover has at least one independent post created between January and April 2026 — not a 2025 thread that picked up a 2026 comment. This rule helps separate live debates from settled history.

The two-sided requirement: Every controversy section below pairs a critical quote with a defending quote (or, for Notion Sites, a third-party adaptive view paired with the Notion engineer’s public response). We do not summarize either side in our own words when a direct quote is available.

archive.org snapshots unavailable due to research environment limitations. Where possible, we transcribed full post text into our internal evidence file as a fallback.

Source bias disclosure: Pricing changes (controversy #1), feature limit details (controversies #2 and #5), and security disclosure timelines (#4) are primarily sourced from Notion’s own announcements and help-center pages. Independent third-party verification of precise numerical values is structurally limited because these changes are originated by Notion itself; user-side sources (Reddit, Hacker News, GitHub) confirm the consequence and sentiment but cannot verify, for example, the exact pre/post pricing diff or the exact deprecation date. Where a third-party reviewer is cited (e.g., sync2sheets, aitooldiscovery), the reviewer typically has a commercial relationship with Notion or its ecosystem and should be read as a positioned voice, not a neutral arbiter.

1. AI Add-on Cancellation and Business-Plan Bundling

What changed

In May 2025, Notion stopped selling its standalone Notion AI add-on to new Free and Plus subscribers. The add-on previously cost $8/user/month on annual billing or $10/user/month on monthly billing. Existing add-on customers were grandfathered into their plans. Anyone signing up after the change who wanted full access to Notion AI — Ask Notion, AI Agents, AI Meeting Notes, and Enterprise Search — would need to subscribe to the Business plan at $20/user/month annual ($24/user/month monthly).

Free and Plus users retained a small allotment of complimentary AI responses, intended as a trial allocation rather than a usable monthly budget. The official Notion help center documented the changes in a page titled “Understanding Notion’s pricing changes (May 2025),” posted on the company’s help domain in mid-May 2025.

The structural shift is what drew the most pushback. The previous layered model — Plus at $10/user/month plus an optional $8 AI add-on — let teams add AI without changing their plan tier. Under the new model, Plus users who want full Notion AI access need to upgrade to Business at $20/user/month. Notion paired the change with a Business-tier price freeze and added Business-only features like SAML SSO and 90-day page history, which Notion framed as upgrades that justified the new bundle.

When (timeline)

The change was announced on April 15, 2025, became effective for new subscribers on May 13, 2025, and reached older subscribers via billing adjustments on August 13, 2025. Discussion has continued into 2026: r/Notion thread 1rc8n6t — “Notion AI’s pricing change could penalize power users” — was created on March 1, 2026, and Hacker News thread 47867392 on April 23, 2026 — discussing OpenAI’s ChatGPT workspace agents — generated direct comparisons to Notion AI pricing.

Data points

Current Plus and Business prices are from Notion’s current pricing page (verified May 2026); the discontinued AI add-on price is from archived/cross-verified historical sources, since the original notion.com/help/2025-pricing-changes announcement page is no longer reachable at that URL (HN cross-link 43991242 from May 15, 2025 confirms it was reachable then; multiple 2026 third-party reviews independently cite the same $8/$10 add-on price):

• Plus: $10/user/month annual, $12/user/month monthly.
• Business: $20/user/month annual, $24/user/month monthly.
• AI add-on (no longer sold to new subscribers as of May 13, 2025): previously $8/user/month annual, $10/user/month monthly.

For a 5-person team, the path math is what generated the loudest reaction:

• Old path to AI (pre-May 2025): Plus $50/month + AI add-on $40/month = $90/month annual.
• New path to AI (post-May 2025, new customers only): Business $100/month annual.

That is a roughly $10 monthly difference for new buyers, but in practice the path locks AI behind a tier that bundles features many small teams do not need (SAML SSO, 90-day page history, private teamspaces). For new buyers who only want AI, the effective tier-up is the cost. For grandfathered Plus + add-on subscribers, the cost stayed flat unless they cancelled and re-subscribed.

The pushback

A top-rated r/Notion comment — quoted in third-party coverage with 132 upvotes — captured the most-shared frustration:

I wouldn’t mind it if it were free, but it’s definitely not something worth paying for… Especially because so many options are free and easily accessible.

— r/Notion top comment, 132 upvotes, on thread https://www.reddit.com/r/Notion/comments/1rc8n6t/ (archived via aitooldiscovery.com/guides/notion-ai-reddit, April 7, 2026; the Reddit URL may 403 automated fetchers due to Reddit anti-bot policy)

A separate “open letter to Notion CEO” thread on r/Notion from May 13, 2025 — https://www.reddit.com/r/Notion/comments/1kli8c4/, also indexed via Hacker News item 43971966 — argued that the change was poorly communicated and asked Notion to restore the Plus + add-on path.

The defense / official position

Notion’s framing positions the change as a feature-rich upgrade rather than a tier squeeze. On Hacker News, an active Notion user offered a representative defense in April 2026:

it’s funny how adding AI to notion actually made it a lot more usable. Most products force it on you, but here I feel like it’s actually a massive benefit. It was hard finding content and using the filters felt clunky. (And the whole UI either in a browser or their app feels buggy + slow). But with their notion AI / MCP it’s gotten super easy to get information in and out.

— persedes, Hacker News comment 47875720, April 23, 2026

Notion’s published rationale on the help center notes that Business-plan customers gain SAML SSO and 90-day page history alongside full AI access, framing the consolidation as a feature bundle rather than an add-on removal.

Primary impact: Free and Plus individual users, plus new paying customers who want AI features without other Business-plan capabilities. Existing add-on subscribers are not directly affected as long as they remain on their grandfathered plan.

2. Offline Mode After Six Years — With a 50-Row Database Limit

What changed

On August 19, 2025, Notion released version 2.53 with native offline mode for desktop and mobile, after a gradual rollout that began on August 12, 2025. CEO Ivan Zhao publicly described offline mode as the company’s #1 most-requested feature for more than five years.

The implementation arrived with documented constraints:

• Databases sync only the first 50 rows automatically; additional rows must be downloaded individually for offline use.
• Only the first view of a database is available offline.
• Subpages do not download recursively — users must toggle each page they want offline.
• Embeds, forms, buttons, AI features, formulas, and automations do not work offline.
• Database properties that are select, date, relation, or rollup types cannot be merged when both sides edit offline; only one version is preserved on sync.
• Pages cannot be shared or have permissions changed while offline.
• Browsers are not supported — offline mode is desktop-and-mobile-app only.

Notion’s December 11, 2025 engineering blog post, titled “How we made Notion available offline,” walked through the architecture rationale and was re-submitted to Hacker News on March 24, 2026.

When (timeline)

Notion engineers began discussing offline mode publicly around 2019 and confirmed it as a top community request multiple times before delivery. Gradual rollout started August 12, 2025; general availability arrived with Notion 2.53 on August 19, 2025; the engineering follow-up landed December 11, 2025. r/Notion thread 1qcbze5 — “Still using notion in 2026 or got any good alternative?” — was created January 14, 2026 and surfaced offline limits as a recurring migration driver.

Data points

The numerical constraints are quoted directly from Notion’s own help guide “Working offline in Notion: everything you need to know” (verified May 2026):

• 50 rows per database synced automatically.
• 1 view per database available offline.
• 0 working features for AI, embeds, forms, buttons, formulas, and automations while offline.
• 5+ years between Notion’s first public commitment to offline mode and the August 2025 release.

The Notion engineering blog explained the cap with a direct rationale: “when offline, we never want to show a page that might be missing data… Opening a page and seeing half the content ‘missing’ would be a worse user experience than not being able to open it at all… we wanted to automatically download up to 50 pages in the current view.”

The pushback

For users whose primary objection is that the implementation arrived too narrow to support their workflows, the most-cited Hacker News comment came from a former Notion user explaining their migration:

I was a big Notion fan for years and am now solidly in the Obsidian camp. Speed and local-first was originally the main differentiator, but over time Steph Ango’s “file over app” philosophy has become my favorite feature. Yesterday I used Claude Code to automate some Obsidian cleanup and it was trivial because everything’s just a file.

— photon_garden, Hacker News comment 44955320, August 19, 2025

The 183-comment HN discussion under the offline-mode launch (item 44954665, 242 points) repeatedly returned to the 50-row cap and the manual per-page toggle requirement as the main shortcomings.

The defense / official position

A counterweight came from a fellow product builder who noted the engineering complexity behind the launch:

This is pretty impressive. A lot of people underestimate the amount of work required to make something available offline. Planning the syncing architecture alone is a monumental task, especially at the scale Notion operates. I built a custom sync solution for my own app, Brisqi (https://brisqi.com), and it took me weeks to get it right, albeit with some trade-offs. Kudos to the Notion engineering team for achieving this milestone.

— ashdev, Hacker News comment 44958290, August 20, 2025

Notion’s own engineering team contributed publicly to the discussion as well. In the r/Notion launch thread, a Notion engineer wrote that the August 2025 release is “the start of offline mode, not the end” and committed to “more than 2 years of improvements planned” — language that has been quoted in subsequent 2026 community threads.

Primary impact: Plus and Business users who treat Notion as their primary daily workspace, mobile-first users, travelers, and anyone with low-connectivity work patterns. Self-hosting and local-first users were already on alternatives like Obsidian; the offline launch did not change that calculus much. See our Notion review 2026 for our broader assessment of how this affects Notion’s overall positioning.

3. The 2025-09-03 API Breaking Change for Multi-Source Databases

What changed

On September 3, 2025, Notion released API version 2025-09-03 and the makenotion/notion-sdk-js v5.0.0 SDK. Notion had pre-announced the change on August 26, 2025. The release introduced “multi-source databases,” where a single database container can hold multiple linked data sources — and to express that, Notion split the previous database_id concept into database_id (the container) plus data_source_id (the underlying data source).

The change was, in Notion’s own documentation, “not backwards-compatible.” Specifically:

• Endpoints moved: /v1/databases/{id}/query was replaced by /v1/data_sources/{id}/query.
• The Search API filter changed: filter.value accepted "page" | "database" and now accepts "page" | "data_source" — a literal enum change.
• Webhooks were versioned: the event database.content_updated was deprecated in favor of data_source.content_updated, with new data-source-specific events.
• Integrations that pinned the older API version (2022-06-28 or 2022-02-22) continued to work for single-source databases but would fail when a database adopted the new multi-source feature.

The practical effect: any third-party integration that walked into a workspace where a customer had migrated to the new database structure could fail unless that integration had migrated to the new endpoints.

When (timeline)

Notion pre-announced on August 26, 2025; API version 2025-09-03 shipped on September 3, 2025; the n8n community filed issue #19489 on September 12, 2025 and the issue remained open and updated as of April 21, 2026. Retool community thread on September 21, 2025 confirmed the same break for Retool users. The Notion 3.0 launch Hacker News thread (item 45304816) on September 18, 2025 also surfaced developer comments about the API break, and r/Notion thread 1r79zlz tracked downstream MCP-server reconnection bugs into 2026 spring.

The 2026 active discussion is documented across multiple GitHub repositories: makenotion/notion-mcp-server issue #181 was created January 15, 2026; ramnes/notion-sdk-py issue #309 was created January 16, 2026 by an automated changelog tracker; and 4ier/notion-cli issue #39, titled “Migrate ‘db’ surface to the 2025-09-03 data_sources API,” was created on April 30, 2026 — one day before this article’s publication date.

Data points

The breaking surface, sourced from the Notion Developers upgrade guide and verified May 2026:

• 1 API version anchor: 2025-09-03.
• 1 SDK release: makenotion/notion-sdk-js v5.0.0, published September 3, 2025.
• 4+ separate GitHub repositories with open or updated issues filed January through April 2026.
• 6+ months of ongoing migration work in the n8n community as of the issue’s last update.
• 2 enum values changed in Search filters: "database" → "data_source".

The pushback

The integration-developer experience is captured cleanly in the n8n bug report that opened the migration backlog:

The current Notion node in n8n is still pinned to API version 2022-02-22. With Notion’s recent release of API version 2025-09-03, many database actions now fail if a database uses the new multi-source database feature. This makes the existing Notion node unusable in workspaces where users have adopted the new functionality.

— antonlvovych, GitHub n8n-io/n8n issue #19489, September 12, 2025

A nearly identical pattern played out across Retool, Notero, the Notion Python SDK, and small open-source CLI tools through April 2026.

The defense / official position

Notion’s developer documentation frames the breaking change as a deliberate architecture investment:

This change is not backwards-compatible. … A single database [can now] contain multiple linked data sources — unlocking powerful new workflows.

— Notion Developers, Upgrade Guide for Version 2025-09-03, announced August 26, 2025

The upgrade guide also documents migration steps and timelines, and Notion published the SDK update on the same day that the API version went live, a posture that signals the company expected ecosystem partners to follow on.

Primary impact: Third-party integration developers (n8n, Zapier, Retool, Notero, Make, Notion MCP server users), small teams that depend on low-code automation, and authors of internal Notion API apps. Users who only access Notion through the official Notion clients are not affected. For PM-style integration alternatives, see our Notion vs Jira comparison.

4. Notion 3.0 AI Agent — Prompt Injection and Data Exfiltration

What changed

On September 18, 2025, Notion released version 3.0 with autonomous AI Agents that can run for up to 20 minutes per task, perform multi-step actions, and access connected tools including GitHub, Gmail, Jira, and Slack through workspace connectors.

The next day, security researcher Abi Raghuram of CodeIntegrity published a proof of concept titled “Hidden risk in Notion 3.0 AI agents: Web search tool abuse for data exfiltration.” The PoC used a PDF with white-on-white prompt-injection text. When a user asked the Notion Agent to summarize the PDF, the embedded instructions directed the Agent to search the workspace for sensitive data, format it into a URL, and call the functions.search web search tool against an attacker-controlled domain — exfiltrating data via a single HTTP request that the user could not see in the chat surface.

Simon Willison, the security researcher who coined the term “lethal trifecta” (private data access plus exposure to untrusted content plus the ability to communicate externally), covered the PoC the same day. On September 29, 2025, Bruce Schneier wrote a follow-up titled “Abusing Notion’s AI Agent for Data Theft” on Schneier on Security.

On December 24, 2025, security firm PromptArmor reported a second issue through HackerOne: when an attacker prompt embedded an external image URL in the Agent’s proposed document edits, the user’s browser fetched the image — and any accompanying tracking data — before the user clicked the approval button. The data exfiltration happened in the pre-approval render. Notion closed the HackerOne report as “Not Applicable” on December 29, 2025. PromptArmor publicly disclosed the issue on January 7, 2026, and Notion deployed a remediation on January 8, 2026 — the day after public disclosure.

When (timeline)

Notion 3.0 launched September 18, 2025; CodeIntegrity disclosed the first PoC on September 19, 2025; Schneier covered it September 29, 2025; PromptArmor filed the second report December 24, 2025; Notion closed it as “Not Applicable” on December 29, 2025; PromptArmor published public disclosure on January 7, 2026; Notion deployed the remediation January 8, 2026. The Hacker News thread for the second disclosure (item 46531565) drew 206 points and 39 comments. The September 2025 thread for the original PoC (item 45307095) drew 183 points and 54 comments.

Data points

The disclosure timeline, drawn from the PromptArmor blog and corroborated by the HN comment from PromptArmor’s noleary:

• 1 day between Notion 3.0 release and the first public PoC.
• 5 days between PromptArmor’s HackerOne submission and Notion’s “Not Applicable” closure.
• 10 days between the closure and PromptArmor’s public disclosure.
• 1 day between PromptArmor’s public disclosure and Notion’s production remediation deployment.
• “100 Million Users” — the user-base figure cited in PromptArmor’s headline framing of the exposure.
• 2 separate HN front-page threads with combined 389+ points across the two disclosures.

The pushback

The HackerOne handling itself became part of the controversy. PromptArmor’s researcher posted directly to the Hacker News thread to document Notion’s initial response:

We responsibly disclosed this vulnerability to Notion via HackerOne. Unfortunately, they said “we’re closing this finding as Not Applicable”.

— noleary (PromptArmor researcher), Hacker News comment 46537735, January 8, 2026

PromptArmor’s public post argued that the architectural risk remained: “The only real fix would be to stop rendering images before user approval and implement proper CSP. They haven’t done either.”

The defense / official position

Notion published a layered defense in its help center page “How Notion 3.0 protects against prompt injection risks”:

Workspace admin controls require permission before agents in the workspace visit websites or connect to third party tools. … User approval needed for any suspicious links. … Complete audit logs of everything your agent does. … Continuous security testing to find and fix vulnerabilities proactively.

— Notion Help Center, “How Notion 3.0 protects against prompt injection risks” (verified May 2026, post-January 8, 2026 deployment)

Notion’s broader posture in community threads has been to treat the second PromptArmor finding as a real bug worth a same-day fix, while framing the underlying class of risk as one that requires layered admin controls and ongoing security testing rather than a single architectural fix.

Primary impact: Business and Enterprise customers who have enabled AI Agents and connected workspaces to GitHub, Gmail, Jira, or Slack. Security-sensitive industries — HR, legal, finance — where agent connectors might touch hiring trackers, contract documents, or financial spreadsheets. The PromptArmor headline references the broader 100 million Notion-user surface area, though only Business and Enterprise tenants with Agents enabled are directly exposed.

5. Notion Sites SEO Constraints and the November 2025 Noindex Bug

What changed

Notion Sites lets users publish any Notion page as a website, with optional custom domains via a $8/month annual ($10/month monthly) add-on on top of a Plus or higher plan, up to 25 custom domains per workspace. The product has been positioned as a complete website-publishing solution since its 2024 launch.

For users with SEO-driven workflows — marketing sites, indie SaaS landing pages, blogs — three structural limitations have been documented across 2025-2026:

• Per-page meta title and description editing is restricted to the homepage; subpages and blog posts cannot have customized meta tags.
• No structured data or schema markup is generated automatically.
• No sitemap.xml is published; Notion’s own help center notes that Notion Sites “can take up to four weeks to be indexed and appear in search results.”

In addition to the structural gaps, Notion shipped a bug in November 2025 that injected <meta name="robots" content="noindex" /> into the <head> of every public Notion site that had search-engine indexing explicitly enabled. The issue persisted for several days before being fixed, during which traffic on affected Notion Sites dropped to near-zero in Google search. r/Notion thread 1ove9px on November 12, 2025 documented the bug with the literal HTML view-source as evidence.

A separate but related Notion Sites concern surfaced on April 19, 2026 in Hacker News thread 47824945 (401 points, 154 comments): public Notion site metadata included the email addresses of every editor of the page. The Hacker News thread cross-references Notion’s own help center note that page metadata “may include the names, profile photos, and email addresses associated with any Notion users that have contributed to the page” when published publicly.

When (timeline)

The structural Notion Sites SEO gaps have been documented since the product’s 2024 launch and surface in third-party reviews. Specific 2025-2026 events: the November 12, 2025 noindex bug (r/Notion 1ove9px), the December 7, 2025 r/Notion 1pglzm0 thread on free-plan custom domain limits, the April 14, 2026 update to sync2sheets’ Notion Sites review, and the April 19, 2026 HN thread on editor email metadata exposure.

Data points

Notion’s own help center “Public pages and web publishing” page (verified May 2026) is the source for several of these:

• $8/month annual / $10/month monthly: custom domain add-on pricing.
• 25: maximum custom domains per workspace.
• 1 page: where you can edit meta title and description (homepage only on paid plans).
• 0: schema markup support, sitemap.xml auto-generation, per-page meta tag controls.
• “up to four weeks”: Notion’s stated indexing delay before Notion Sites appear in Google search results, taken verbatim from the help center.
• November 12, 2025: date of the noindex bug r/Notion report.
• 401 points / 154 comments: April 19, 2026 HN engagement on the editor email metadata thread.

The third-party sync2sheets.com review, last updated April 14, 2026, summarizes the per-page meta limitation directly — full quote in “The pushback” section below.

The pushback

For SEO-specific complaints, the most concrete critique comes from third-party reviewer sync2sheets, whose April 14, 2026 update tested Notion Sites against per-page SEO requirements:

you can only edit the meta title and description for your site’s homepage. You can’t customize it for individual subpages or blog posts, limiting how much you can optimize your Notion Sites content for SEO.

— sync2sheets, Notion Sites in 2026 review, last updated April 14, 2026

The November 2025 noindex bug thread on r/Notion (1ove9px) and the December 2025 custom-domain thread (1pglzm0) provided additional concrete user reports of traffic loss and feature limits. The April 19, 2026 HN thread on editor email metadata (item 47824945, 401 points) added a separate Sites-publishing concern on top of the SEO gaps.

The defense / official position

This is the one controversy where Notion has limited public support beyond official communication. Notion did not publish an independent post about the November 2025 noindex bug; the help center pages on “Edit & customize your Notion Sites,” “Connect a custom domain with Notion Sites,” and “Public pages and web publishing” represent the company’s documented position.

The closest thing to a public defense came indirectly. On the April 19, 2026 HN thread about editor email metadata, a Notion engineer engaged directly to acknowledge the issue:

Hi, this is Max from Notion. First: This is documented and we also warn users when they publish a page. But, that’s not good enough! Second: We don’t like this and are looking at ways to fix this either by removing the PII from the public endpoints or by replacing it with an email proxy similar to GitHub’s equivalent functionality for public commits. P.S: Some folks here have speculated that this should be a 1 minute fix. Unfortunately that is not the case. :(

— mschoening (Notion engineer Max), Hacker News comment 47827283, April 19, 2026

A separate adaptive view comes from the third-party patcher community — products like Simple.ink, Bonsites, and Feather built specifically to add per-page meta, schema, and sitemap support on top of Notion Sites. Their existence demonstrates that some Notion Sites users actively work around the structural gaps rather than migrate.

Primary impact: Plus subscribers who pay for the custom domain add-on for marketing sites, indie SaaS landing pages, and personal blogs; SEO-dependent content creators; small businesses that use Notion Sites as a lightweight CMS. For comparison-shopping content site builders, our comparison library covers Notion alongside other workflow tools, and our free Notion alternatives page covers options for users prioritizing different trade-offs.

What This Means for You

We don’t issue blanket migration recommendations. The five 2026 changes hit different user groups differently, and a recommendation that fits one workflow can be wrong for another. Here is a neutral read-through by user group, drawn from the evidence above.

If you’re a Free or Plus individual user, change #1 (AI bundling) is the only one that touches your daily workflow directly. If you do not need full Notion AI, Plus at $10/user/month remains the same product as before May 2025. If you want full Notion AI, the path forward is Business at $20/user/month, which also adds SAML SSO and 90-day page history. For most individuals, no action required.

If you’re a Business team admin, change #4 (prompt injection) is the change that warrants policy attention. Notion ships per-workspace admin controls that gate which sites and tools agents can reach, plus audit logs. Many teams enable AI Agents in restricted modes — workspace-only access without external connectors — and require explicit approval per agent run. If your team has already enabled Notion 3.0 Agents with broad connector access, reviewing the admin controls and audit-log cadence is a worthwhile follow-up.

If you’re an integration developer, change #3 (API breaking) is the change that maps directly to your work. If you maintain an integration that uses database_id-based endpoints, the migration to data_source_id is required to support customers who moved to multi-source databases. The Notion Developers upgrade guide documents the steps, and major ecosystem projects (n8n, Retool, the Notion Python SDK) are working through their own migrations. For internal API apps, test against a workspace that has migrated before rolling out.

If you’re an Enterprise security lead, change #4 (prompt injection) is your central evaluation question. The honest framing is that the underlying class of risk is not eliminated — Simon Willison’s “lethal trifecta” affects most autonomous agent systems with external tool access, not just Notion. Notion’s same-day production remediation on the second disclosure is a useful data point on response speed once issues become public. Most security leads either disable AI Agents at the workspace level, restrict connectors, or require explicit per-action approval flows.

If you’re a content creator using Notion Sites, change #5 (Sites SEO + noindex bug) is the change that affects your traffic. The structural gaps — per-page meta editing, no schema markup, no sitemap.xml — have been present since launch and typically require third-party tooling (Simple.ink, Cloudflare with custom meta injection) or migration to a dedicated CMS (Webflow, Framer, Ghost). The November 2025 noindex bug was fixed but reinforced that Notion Sites is built as part of a larger workspace product, not a dedicated SEO product.

If your workflow is offline-first or mobile-heavy, change #2 (offline mode limits) is the change to evaluate against your requirements. If offline-first workflows are critical to your team, the current 50-row database limit and per-page manual toggle may not meet those requirements; common alternatives include Obsidian (offline-native) and Logseq (local-first). If you are currently using Notion as your primary daily tool, those two specific limits are the ones to test against your real workflow before deciding.

The framing we keep coming back to: Notion in 2026 is the same product it was in 2024 for documentation, wikis, and database-driven workflows — the use case where it remains uniquely strong. The five 2026 changes are about the surfaces around that core: AI pricing, offline access, third-party integrations, agent security, and website publishing. Each surface carries a different cost depending on who you are.

Frequently Asked Questions

What changed in Notion in 2026?

Five distinct changes drove most 2026 community discussion: (1) the May 2025 cancellation of the standalone Notion AI add-on, which routed new users to Business at $20/user/month for full AI access; (2) the August 2025 offline mode launch with a 50-row database sync cap and per-page manual toggles; (3) the September 2025 API version 2025-09-03 that broke database_id-based integrations across n8n, Retool, and other low-code tools; (4) the September 2025 Notion 3.0 AI Agent prompt-injection vulnerabilities disclosed by CodeIntegrity and PromptArmor, with the second issue patched on January 8, 2026 after public disclosure; and (5) ongoing Notion Sites SEO gaps including a November 2025 noindex bug that removed indexed Notion sites from Google. Each change has primary-source threads on Reddit, Hacker News, and GitHub from January through April 2026.

Is Notion still worth using in 2026?

It depends on your workflow. For docs-first teams that build wikis, knowledge bases, and relational databases, Notion remains the most flexible workspace — that’s why our Notion Review 2026 still scores it 8.0/10. For teams that depend on offline access, third-party API integrations, or Notion Sites for SEO traffic, the 2025-2026 changes have introduced real friction. Most teams stay; some migrate to alternatives like Obsidian (offline-first) or Coda (more structured workflows). The five 2026 changes don’t make Notion unusable — they shift the trade-offs.

Why are users upset about Notion AI bundling?

In May 2025, Notion stopped selling the standalone AI add-on (previously $8/user/month annual or $10/user/month monthly) to new subscribers. Existing add-on customers were grandfathered. New paying users who want full Notion AI — Ask Notion, AI Agents, AI Meeting Notes — must now subscribe to Business at $20/user/month. The community concern: a 5-person team’s old path to AI was Plus + AI add-on = $50 + $40 = $90/month annual; the new path is Business = $100/month annual. The dollar difference is small (~$10/month), but the tier shift bundles features many small teams (SAML SSO, 90-day page history, private teamspaces) do not need. A top r/Notion comment with 132 upvotes captures the sentiment that the bundling penalizes Plus users who only wanted AI. Notion has not reversed the decision. For tools that bundle AI differently, see our ClickUp vs Notion comparison.

What’s the prompt injection risk for Notion AI Agents?

Notion 3.0 launched on September 18, 2025 with autonomous AI Agents that can run for up to 20 minutes and access connected tools like GitHub, Gmail, Jira, and Slack. On September 19, 2025, security researcher Abi Raghuram (CodeIntegrity) published a proof of concept showing how a hidden white-on-white prompt in a PDF could direct the Agent to use the functions.search web search tool to exfiltrate workspace data to an attacker-controlled domain. On December 24, 2025, PromptArmor reported a second issue where document edits were applied and external image URLs were fetched before the user clicked approve. PromptArmor publicly disclosed the second issue on January 7, 2026, and Notion deployed a remediation on January 8, 2026. PromptArmor stated that the underlying class of risk — what Simon Willison calls the “lethal trifecta” of private data access, untrusted content, and external communication — is not fully eliminated.

How does Notion Sites’ SEO compare to alternatives?

Notion Sites lets you publish any Notion page as a website, with optional custom domains via an $8/month annual ($10/month monthly) add-on plus a Plus or higher plan. Documented SEO limitations include: meta title and description editable only on the homepage (not per page), no schema markup, no auto-generated sitemap.xml, and Notion’s own help center notes that Notion Sites can take up to four weeks to be indexed by Google. In November 2025, a bug caused all public Notion sites with search-engine indexing enabled to inject <meta name="robots" content="noindex" /> into their HTML, removing them from Google search results until the bug was fixed. For dedicated content sites, Webflow, Framer, Ghost, and traditional CMSs offer per-page SEO controls. Some users layer third-party tools like Simple.ink or Cloudflare in front of Notion Sites to add per-page meta tags. For a broader workflow comparison see our Notion vs Asana and Monday vs Notion breakdowns.

Did Notion finally release offline mode?

Yes, on August 19, 2025 with the Notion 2.53 release, after Notion CEO Ivan Zhao described offline mode as the company’s #1 most-requested feature for over five years. The implementation has documented limits: only the first 50 rows of a database sync per the official help guide, only the first view of a database is available offline, subpages do not download recursively (you must toggle each page), and embeds, forms, buttons, AI features, formulas, and automations do not work offline. Notion’s December 2025 engineering blog post explained the architecture trade-off: “we never want to show a page that might be missing data.” For workflows that depend on full offline databases, alternatives like Obsidian remain a stronger fit; see free Notion alternatives for the broader list.

Should I migrate from Notion?

Migration is a per-team decision. Teams that primarily use Notion for documentation and wikis usually stay — none of the 2026 changes affect docs depth or database flexibility. Teams that depend on heavy automations or third-party integrations (n8n, Zapier, Retool, custom Notion API apps) hit real friction with the 2025-09-03 API breaking change; some have moved automation-heavy workflows to dedicated PM tools like ClickUp or Asana. Teams that need offline-first access have moved to Obsidian. Teams running marketing sites on Notion Sites have either layered third-party SEO tools on top or migrated content to Webflow, Framer, or Ghost. We don’t recommend a blanket migration — review which of the five changes affect your specific workflow and decide based on the cost of switching versus the cost of the friction. Our Notion vs Trello comparison and Notion vs Jira comparison walk through specific migration paths.

Related Reading

• Notion Review 2026 — 8.0/10 — full product review with the same primary-source approach.
• 10 Free Notion Alternatives in 2026 — alternatives for offline-first, SEO-first, or automation-first workflows.
• ClickUp vs Notion — cost and features for teams considering ClickUp’s bundled AI as an alternative to Notion’s Business-tier AI.
• Notion vs Asana — docs-first vs structured PM, for teams reconsidering Notion as their PM tool.
• Notion vs Jira — for engineering teams where the September 2025 API breaking change matters most.
• Monday vs Notion — for teams that need stronger native automations than Notion’s database triggers offer.
• Notion vs Trello — for teams considering simpler kanban-first alternatives.
• SaaS Pricing Decoded 2026 — broader pricing-trend research across 41 SaaS tools, useful context for the bundling shift in change #1.

Sources: Reddit r/Notion threads, Hacker News submissions and comments fetched from the HN Firebase API, GitHub issues across n8n-io/n8n, makenotion/*, ramnes/notion-sdk-py, 4ier/notion-cli, the Notion Help Center, the Notion Developers documentation, the Notion Engineering Blog, PromptArmor, the CodeIntegrity research blog, Schneier on Security, Simon Willison’s blog, and third-party reviews (sync2sheets, Simple.ink, aitooldiscovery, alfred-ai). All URLs verified May 2026 except where noted; archive.org snapshots unavailable due to research environment limitations.