TopicLift Connector

TopicLift Connector connects a WordPress publication to TopicLift. It is a lightweight bridge: it collects the visitor signals and editorial metadata needed by the TopicLift SaaS, while the reports, analysis, recommendations, and editorial workflow remain in your secure TopicLift workspace. The plugin does not try to turn WordPress into an analytics dashboard. It does not add dashboard widgets, editor panels, post-edit boxes, or local report screens. After the connection is configured, you use TopicLift at https://topiclift.io to read and act on the data from your publication. What you can do in TopicLift Depending on the data and integrations available for your workspace, TopicLift helps publishers:

• Monitor realtime readers, pageviews, reading activity, sources, devices, and outbound or affiliate interactions.
• Review synced editorial content and open detailed article metrics.
• Connect Google Search Console to understand Search, Google Discover, and Google News visibility.
• Receive a daily editorial briefing that brings the most useful signals together.
• Identify editorial opportunities, such as articles to create, update, relaunch, monitor, or improve.
• Compare traffic, visibility, engagement, and monetization signals before deciding what to do next.
• Use AI-assisted readings and recommendations that are grounded in the data available to the workspace.

TopicLift suggests. Editors decide and act. The service is designed to support editorial judgment, not to publish or change articles automatically. Private Beta TopicLift is currently in Private Beta for approved WordPress publishers. During the beta, the service is free for approved participants and no credit card or automatic billing is required. Publishers can apply for a free diagnosis of their Google Discover traffic and, if approved, use TopicLift with their own WordPress and Search Console data. Apply at https://topiclift.io/register. External service This plugin requires a TopicLift account and an approved WordPress site connection. After an administrator enters the Site Key and Site Secret provided by TopicLift, the plugin communicates with:

• https://topiclift.io/api/v1/collect/{site_key} for frontend event batches.
• https://topiclift.io/api/v1/sites/{site_key}/handshake for connection verification.
• https://topiclift.io/api/v1/sites/{site_key}/contents/sync for editorial metadata synchronization.
• https://topiclift.io/api/v1/sites/{site_key}/contents/recovery for bounded recovery requests when recent Google data refers to an article outside the initial import.

Use of TopicLift is subject to the TopicLift Privacy Policy and Terms of Service. Data sent to TopicLift When an administrator enables tracking, the plugin may send page URL, referrer, device category, event timestamp, session identifier, active reading time, scroll depth, and outbound or affiliate-link interactions. For published posts, it may send article ID, URL, title, author, categories, tags, dates, word count, and featured-image URL. The plugin does not send WordPress passwords, administrator credentials, or full article body text. Logged-in WordPress users are excluded by default. Privacy and consent Tracking is disabled by default on new installations. An administrator must actively enable it in Settings > TopicLift and is responsible for ensuring that the site's visitor notice and consent process provide an appropriate lawful basis for tracking.

1.1.180

• Bound the initial content import to the latest 365 days and no more than 10,000 articles.
• Recover older omitted articles when they are visited or appear in recent Google Search Console data.
• Reuse the existing background event for lightweight post-setup maintenance.

1.1.179

• Align the WordPress.org translation domain and contributor metadata with the official plugin slug.

1.1.178

• Extend the client-side guard to skip recognizable crawlers and automated monitoring tools before sending tracking requests.

1.1.177

• Exclude clearly automated or prerendered browser sessions before they create TopicLift tracking events.

1.1.176

• Normalize outbound image alt text, titles, authors, categories, and tags to TopicLift API limits so one unusually long WordPress field cannot block a content batch.

1.1.175

• Normalize outbound category and tag metadata to TopicLift API limits so one unusually long WordPress term cannot block a content batch.

1.1.174

• Restore the standard topiclift-connector package folder so WordPress recognizes updates in place.

1.1.173

• Resume a pending published-content import automatically after a connector update, without requiring an administrator to open the settings screen.

1.1.172

• Import the complete published content library progressively in resumable background batches.
• Add visible historical-import progress to the connector settings page.

1.1.171

• Declare compatibility through WordPress 7.0 in the plugin-directory readme header.

1.1.170

• Require an explicit administrator choice before enabling frontend tracking on new installations.
• Add WordPress privacy-policy helper content and clearer data-processing documentation.
• Load the local tracker through WordPress script APIs instead of a manual browser bootstrap.
• Remove unused legacy connector files from the distributable package.

1.1.169

• Prevent internal URLs containing affiliate-like keywords from being classified as affiliate clicks.