Notion

Rankturn connects to your Notion workspace and mirrors your keywords, articles, and series into a set of Notion databases. Once connected, edits flow both ways: changes you make in Rankturn push to Notion, and changes you make in Notion can pull back into Rankturn. You can also approve articles for publishing straight from Notion using a single checkbox.

Notion is set up from Settings → Integrations, on the Notion card.

Connecting & Setup

Connecting Notion takes two steps: you authorize Rankturn in Notion, then a short setup screen creates the databases for you.

1. Go to Settings → Integrations and find the Notion card.
2. Click Connect with Notion. Notion opens so you can authorize Rankturn and choose which workspace and pages it can access. Grant access to at least the page you want the databases created under.
3. After you authorize, Notion sends you back to Rankturn. The card now shows Connected, but setup isn't finished yet — you'll see a Complete setup prompt.
4. Click Complete setup to open the setup screen.

On the setup screen:

1. Rankturn shows the top-level pages it can see in your workspace. If it can see exactly one page, that page is pre-selected for you to confirm. Otherwise you get a searchable list — start typing to find a page by title.
2. Select the parent page the databases should be created under.
3. Choose the column language for the database property names — English or Japanese. This defaults to your current Rankturn interface language. (See Column Mapping & Localized Property Names below.)
4. Click Create databases. Rankturn creates a RankTurn page inside the page you selected, builds the synced databases in it, and then copies your existing keywords, articles, and series into Notion for the first time.

That first copy runs in the background. Because Notion limits how fast data can be added, it can take 10–30 minutes depending on how much you're syncing.

Once setup is complete the card switches to its normal state with Sync, Reconnect, and Disconnect buttons.

Reconnecting: Use Reconnect if your Notion access expires or you need to grant access again. It re-authorizes the connection without deleting your existing databases.

The four databases (keywords, articles, series)

Rankturn doesn't use a single Notion database. It creates four linked databases under the parent page, each with its own icon and a default table view:

The databases are related to each other inside Notion:

• An Article has a Keyword relation linking it to its row in the Keywords database.
• A Series Topic has a Series relation and an Article relation linking it to the matching rows in the Series and Articles databases.

Keywords columns: Keyword (title), Intent, Search Volume, Difficulty, CPC, Source. A few hidden columns hold the dates and an internal ID Rankturn uses to match records.

Articles columns: Title (title), Status, Auto Publish, Slug, Excerpt, Category, Tags, Author, Keyword (relation), Meta Title, Meta Description, Canonical URL, SEO Score, Word Count, Reading Time, Published At, plus the same hidden date and ID columns. The article body itself is written into the Notion page's content, not into a column.

Series columns: Name (title) and Theme only. The rest of a series' settings — frequency, numbering, schedule, templates, auto-generate, and auto-publish — are managed in Rankturn and are intentionally not mirrored to Notion.

Series Topics columns: Title (title), Description, Keyword, Status, plus a Series relation, an Article relation, and the same hidden ordering, date, and ID columns.

Column Mapping & Localized Property Names (EN/JA)

Notion identifies a property by its name, so the column names Rankturn writes have to stay stable for sync to work. The column language you pick in the wizard decides those names.

• Visible columns are localized. For example, in English the keyword volume column is Search Volume, and in Japanese it is 検索ボリューム. The article Title becomes タイトル, Status becomes ステータス, Auto Publish becomes 自動公開, and so on.
• The hidden date and ID columns keep their English names in both languages. This lets Rankturn match records reliably no matter which language you chose.

A short selection of the localized property names:

Do not rename the synced properties in Notion. Because the name is the key, renaming a column breaks the mapping for that field. If you want different labels, choose the right column language when you set up the connection.

Two-way sync & realtime updates

By default the sync is one-way: Rankturn pushes your changes into Notion. To also pull edits from Notion as they happen, turn on realtime sync.

On the connected Notion card, the Realtime sync toggle controls this. When you turn it on:

1. Rankturn shows a connection URL for your account. Copy it.
2. In Notion's integration settings, add this URL so Notion can send Rankturn an instant update notification whenever something changes.
3. Notion sends a one-time verification code. Reveal it on the card with Show token, copy it, and paste it back where Notion asks you to verify.
4. Once Notion confirms, the card shows a Verified badge. Until then it shows Pending.

After it's verified, page changes in Notion (create, update, delete) reach Rankturn and are applied to the matching record. If the same record was changed in both places, the most recent edit wins: if your Rankturn record was updated more recently than the Notion page, the incoming Notion change is skipped so it can't overwrite newer work.

What pulls back from Notion, per database:

• Keywords — keyword text, search volume, difficulty, CPC, intent, source.
• Articles — title, slug, excerpt, meta title, meta description, canonical URL, SEO score, word count, reading time, tags, category, author, the keyword relation, and the body (your edits in the Notion page become the article's content). Status is never pulled — Rankturn is the single source of truth for status and only pushes it to Notion so you can see it.
• Series — name and theme only.
• Series Topics — title, description, and keyword, and only while the topic is still waiting in the queue. Once a topic has started generating or been used, Notion edits to it are ignored.

Deleting a page in Notion (with realtime sync on) deletes the matching Rankturn record; deleting a record in Rankturn archives the matching Notion page.

Creating records from Notion: With realtime sync on, adding a brand-new row in the Keywords, Articles, or Series Topics database creates a matching record in Rankturn. New articles you write in Notion come in as a Draft and are marked as imported, and a new Series Topic must have its Series relation set so Rankturn knows which series it belongs to. New rows in the Series database are not created back into Rankturn — series are set up in Rankturn only.

Manual Sync & Import New

You don't have to turn on realtime sync to move data. On the connected card, Sync runs a one-off two-way sync:

1. It pushes all of your current Rankturn keywords, articles, and series up to Notion.
2. It then pulls changes back down from Notion using the same rules described above.

Use Sync when you've made a batch of edits in Notion without realtime sync turned on, or to force everything back into alignment after toggling settings. Like the initial sync, it is paced for Notion's rate limits, so a large account can take a little while.

Rows you add in Notion are picked up during the pull half of a manual sync the same way they are with realtime sync — a brand-new Keyword, Article, or Series Topic row becomes a new Rankturn record, while rows that already came from Rankturn are treated as existing records and updated, not duplicated.

Approving articles for publishing from Notion

The Articles database has an Auto Publish checkbox. This is the one Notion control that can trigger a publish — checking it approves the article for publishing in Rankturn.

How it behaves:

• Status is display-only. Rankturn pushes the article Status (Draft, Generating, Published, Rejected, and so on) into Notion so you can see where each article stands, but any edit you make to the Status column in Notion is ignored and overwritten on the next sync. You can't change an article's status from Notion.
• Auto Publish is the approval signal. Tick it in Notion and, on the next sync (realtime or manual), Rankturn applies the approval and moves the article toward publishing. It works whether you check it on an article that's already synced or on a new article you wrote directly in Notion.

This makes Notion a lightweight review space: your team can read and refine articles in Notion, watch their status, and approve them for publishing with a single checkbox — without ever leaving Notion.

To learn more about how publishing works, see Automatic Publishing and Publishing & Scheduling. For how two-way sync behaves across all integrations, see Bidirectional Sync.