Linking Semrush as a source

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

Learn more

The Semrush connector syncs Site Audit and organic search data from your Semrush projects into the PostHog data warehouse, so you can analyze SEO health and keyword performance alongside your product data.

Prerequisites

You need:

A Semrush account with an SEO Business subscription
A project with Site Audit enabled
A v3 API key from your Semrush profile
Sufficient API units (100 units per table request, plus 100 units for connection validation)

Adding a data source

In PostHog, go to the Sources tab of the data pipeline section.
Click + New source and click Link next to this source.
Enter your credentials (see Configuration below) and click Next.
Select the tables you want to sync, choose a sync method and frequency, then click Import.

Once the syncs are complete, you can start querying this data in PostHog.

When linking Semrush, you'll need:

API key (v3) – find it under API keys in your Semrush profile.
Project ID – the numeric project ID from your Semrush project URL. For example, if your project URL is https://www.semrush.com/projects/123456/site-audit/, the project ID is 123456.

Two optional settings let you customize organic search reports:

Domain (optional) – the domain for organic search reports. Defaults to your Semrush project URL if not set.
Regional database (optional) – the Semrush regional database code (e.g. us, uk, de). Defaults to us.

API units

Semrush syncs consume your account's API units:

100 units per Site Audit table request during syncing
10,000 units per audit snapshot for the site_audit_history table (incremental syncs skip already-loaded snapshots)
100 units for connection validation
Retries (up to 3 attempts) can consume additional units
Domain organic reports cost API units per returned row, and each sync reads up to 10,000 rows

Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
Incremental – only new or updated rows are synced on each run, using a cursor field (such as an updated_at timestamp). Cheaper than a full refresh, but deletes aren't captured.
Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See sync methods for a full explanation of how each mode works and how to choose between them.

The site_audit_history table supports incremental syncing based on the audit completion date. Each sync fetches only snapshots completed since the previous sync, which saves API units on projects with many historical audits.

All other Semrush tables use full refresh syncing. The Semrush API doesn't expose pagination or server-side time filters for these tables, so each sync re-downloads all data.

Configuration

Option	Description
`API key (v3)` Type: password Required: True
`Project ID` Type: text Required: True
`Domain for organic reports` Type: text Required: False	Leave empty to use your Semrush project's domain.
`Regional database for organic reports` Type: text Required: False	A Semrush regional database code, such as `us`, `uk` or `de`. Defaults to `us`.

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`site_audit`	Summary of the latest Site Audit for the configured Semrush project.	Full refresh	—	—
`site_audit_snapshots`	Completed audit IDs and completion dates for the configured Semrush project.	Full refresh	—	—
`site_audit_issue_descriptions`	Issue descriptions for Site Audit reports.	Full refresh	—	—
`site_audit_history`	Site health score and issue counts for each completed Site Audit snapshot of the configured project.	Incremental, Full refresh	Audit finish date	—
`site_audit_issue_details`	Pages affected by each issue that the latest Site Audit snapshot found.	Full refresh	—	—
`domain_organic_keywords`	Keywords that bring users to the domain via Google's top 100 organic search results, sorted by traffic share.	Full refresh	—	—
`domain_organic_competitors`	Domains that compete with the domain in organic search, sorted by common keywords.	Full refresh	—	—

Troubleshooting

Authentication failed

If you see "Semrush authentication failed," your API key is invalid or expired. Verify your v3 API key under API keys in your Semrush profile.

API access disabled

If you see "Semrush API access is disabled," check that:

Your Semrush account has an active SEO Business subscription
You have access to the configured project

API units exhausted

If you see "Semrush API units or request limits are exhausted," you need to add more API units to your Semrush account or wait for your limits to reset. Contact Semrush support for help.

Project not found

If you see "Semrush could not find this project," verify:

The project ID is correct (numeric only, from your project URL)
You have access to the project
Site Audit is enabled for the project

Regional database access denied

If you see "Your Semrush plan can't access this regional database," your subscription doesn't include data for the selected region. Choose a different regional database in the source settings, or upgrade your Semrush plan.

Domain report failed

If you see "Semrush rejected the domain report request," check that:

The domain setting is correct and the domain exists
The regional database has data for the domain
Your Semrush plan includes Analytics API access

No domain configured

If you see "Semrush returned no URL for this project," the project doesn't have a URL set and no domain was provided. Enter a domain in the source settings.

If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.