Notion
Publish SiteLift articles as pages in a Notion database, with the title, slug, cover and your own properties mapped.
How it works
SiteLift writes each article as a page in a Notion database, using an API token connection you create in your workspace. You paste the database link and the API token, pick the data source, and match SiteLift’s fields to your properties; the article body becomes the page content. Pages show up in the database view straight away, and republishing an edited article updates the same page instead of adding a new row. If your blog runs on a Notion-powered site builder such as Super, Potion or Feather, it picks the pages up from the database like any page you write yourself.
Setup Guide
- 1
Create an API token connection
Open app.notion.com/developers/connections and click New connection. Older consoles call this Internal connections → Create a new connection.
Name it SiteLift. Under Authentication method, choose API token and create the connection for the workspace containing your blog database. This is the workspace-scoped connection previously called an internal connection. SiteLift uses its API token; do not choose OAuth for this setup.
On the Configuration tab copy the API token (it starts with
ntn_). Under capabilities make sure Read content, Update content and Insert content are ticked; no user information is needed. - 2
Prepare the database
Use a full-page database for your posts. SiteLift matches properties by name, so these names are mapped automatically: Name or Title (the title property), Slug (text), Excerpt (text), Featured image (files & media), SEO title and SEO description (text), Tags (multi-select), Category (select) and Published date (date). The body needs no property: it is written as the page content.
A text property for the slug is strongly recommended: SiteLift finds an article’s page by it when you republish. Without one, it matches on the title instead.
- 3
Give the connection access to the database
Open the database in Notion, click ••• in the top right, then Connections → Add connection, search for SiteLift and confirm. Connections may be under More. You can also do this from the connection’s Content access tab with Edit access. Until this is done Notion answers every request with “not found”.
- 4
Connect and map the fields
In SiteLift open Settings → Integrations, choose Notion and paste the database link (copy it from the address bar or via ••• → Copy link; a bare database ID works too) and the token. Pick the data source; most databases have exactly one.
SiteLift proposes a mapping: the title property gets the article title, Page content gets the article body and Page cover or a files property gets the featured image. Adjust anything, and give a Status or Published property a fixed value if your site builder only shows pages with it. Test publish creates a page from sample content and moves it to the trash right away, so Notion’s own checks run before you save.
- 5
Publish
Articles publish on your content calendar schedule. Notion has no draft state, so a page is visible in the database as soon as it is written; the published link SiteLift records is the page’s Notion URL.
Tip
What gets published
- Title and featured image. Notion shows the page title and cover itself, so the H1 and hero image leave the body. Map the featured image to the page cover, a files property, or both.
- Body. The article becomes Notion blocks: headings, paragraphs with bold, italic, code and links, bulleted and numbered lists, quotes, code blocks, images, dividers and tables. Fourth-level headings become third-level ones, and lists nest at most two levels deep.
- Images. Images stay hosted by SiteLift and are linked as external files, so nothing counts against your Notion upload limits.
- Structured data. Notion pages have no place for JSON-LD, so it is left out. If your site builder reads it from a property, map the JSON-LD field to a text property.
- Taking comparisons offline. Notion has no draft state. SiteLift’s Move to trash action moves the comparison page to Notion’s trash, where you can restore it. Your site builder controls when that change appears on the public site.
- Republishing. The page’s properties are updated and its content is replaced in full, so edits made to the page body inside Notion are overwritten.
Competitor comparison pages
Supported as blog posts in your existing Notion database and data source, using the same connection and field mapping as your articles. Your Notion-powered site builder decides how these pages appear in its blog layout and feed. No extra collection, content model, template or comparison mapping is needed. Existing supported tag or category fields can group them as Comparisons; no new field is required. SiteLift does not create a separate comparison hub or add a link to one. The blog controls the URLs, so the comparison URL prefix does not apply.
Troubleshooting
- Should I choose API token or OAuth? Choose API token under Authentication method when creating the Notion connection. SiteLift’s current setup takes a workspace-scoped API token and a database link. Older Notion consoles call this an internal connection. Enable Read, Update and Insert content, and explicitly add the connection to your database.
- Notion says the database could not be found. The connection has not been added to the database, or the link points to a page that contains the database. Open the database itself as a full page, add the SiteLift connection under ••• → Connections, and copy that link.
- 401 from Notion. The token is wrong or the connection was deleted. Copy the current token from the connection’s Configuration tab and reconnect.
- 403 from Notion. The connection is missing a capability. Tick Read, Update and Insert content on the Configuration tab. A message about free blocks means a free workspace with several members has used its 1,000-block allowance; upgrade the workspace or remove the extra members.
- A property is out of date or rejected. A property was renamed to a different type, deleted, or a Status value no longer exists. Open Integrations → Notion → Edit field mapping and pick again.
- The page appears twice. The slug is not mapped to a property, or the property was changed by hand. Map Slug to a text property; SiteLift then updates the page whose slug matches.
Still stuck? Use Test Connection on the Integrations page; the message comes straight from Notion. Or write to support.