← Plugin catalog
Data & Analytics

TopicLift Editorial Insights

TopicLift v1.0.1

Editorial traffic insights

Create a free account to save this plugin.

From the developer

Not specified in the available declarations: capabilities, limitations, pricing & account requirements.

Onboarding example

How are my articles performing today?
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 20, 2026. Package observed Nov 20, 2026.

View package source →

Description

From the marketplace listing

TopicLift gives publishers read-only access to realtime and historical editorial traffic, article performance, aggregate search-query data, and evidence-based editorial recommendations from their authorized workspace. It cannot create, edit, or publish content.

Language: English · Automatically detected from descriptions.

What changed

· 3 observations

Capabilities & instructions

Plugin name changed from “TopicLift Editorial Copilot” to “TopicLift Editorial Insights”. App-6a8c946ae1bc819196a64d8fc9810c6d updated; open the comparison for details. Topiclift updated; open the comparison for details. Full description changed from “TopicLift Editorial Copilot gives publishers a read-only...

View comparison →
Capabilities & instructions

Plugin name changed from “TopicLift Editorial Copilot” to “TopicLift Editorial Insights”. App-6a8c946ae1bc819196a64d8fc9810c6d updated; open the comparison for details. Topiclift updated; open the comparison for details. Full description changed from “TopicLift Editorial Copilot gives publishers a read-only...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Files & skills

File archives

Plugin package6 files · 185 KBBrowse files →
Skill instructions
topiclift-editorial-copilot5.99 KB

View saved version →

---
name: topiclift-editorial-copilot
description: Use authenticated TopicLift data to answer questions about realtime and historical editorial traffic, Google Search and Discover performance, and what a publisher should publish next. Use only TopicLift MCP data for editorial recommendations. Public installations use TopicLift OAuth 2.1; local Codex and Claude development may use the documented personal token.
---

# TopicLift Editorial Copilot

Use the `topiclift` MCP server whenever the user asks about a TopicLift site's traffic, article performance, Google Search, Google Discover, aggregate search queries, an editorial idea, or publishing recommendations.

## Operating rules

- Detect the language of the current user message, not the conversation history, site language, tool output, or account locale. Write the complete conversational answer in that language: English input requires an English answer, Italian input requires an Italian answer, and so on. Keep tool names, schema fields, URLs, and quoted source labels unchanged when needed, but translate explanatory prose, headings, recommendations, titles, and angles. If the current message is genuinely mixed or ambiguous, follow its dominant language.
- On every TopicLift tool call, set `response_language` to the BCP 47 tag for the current user message (`en` for English, `it` for Italian, and so on). Follow the returned `response_guidance` when composing the answer.
- Use only data returned by TopicLift. Do not browse the web or add external trend data to fill gaps.
- Keep every analysis scoped to one site. If the site is missing or ambiguous, call `list_sites` and ask the user to choose only when more than one plausible site remains.
- Select the period from the question. Use realtime for current activity; otherwise use today, yesterday, 7 days, 28 days, or 90 days as the closest supported range.
- Use comparisons when they materially help. The server is authoritative for metrics and comparison windows.
- Never claim access to individual visitors or raw sessions. TopicLift exposes editorial and aggregate Search Console data only.
- Do not modify content, settings, opportunities, or WordPress. This integration is read-only.
- Never reveal or repeat the user's access token.

## Traffic questions

Use `get_traffic_overview` for totals, trends, sources, and realtime status. Its traffic metrics are restricted to synced, published editorial WordPress posts; homepage, pages, archives, unknown post IDs, and other non-editorial URLs are excluded. State this scope briefly when reporting the numbers. Use `get_top_articles` when the question is about individual articles, winners, declines, or unusual growth.

Always identify the site and period in the answer. Include the most relevant metrics and supporting articles. Do not overwhelm a short operational question with every available metric.

## Editorial idea review

Use `review_editorial_idea` when the user provides an idea, provisional title, outline, draft, or existing article URL and asks whether it is worth publishing or how to improve it. The tool is read-only and compares the input with the selected site's published editorial inventory and aggregate Google evidence.

Explain the overlap risk, matching Search demand, related articles, confidence, and the suggested angles or titles. For a URL, distinguish an update opportunity from a genuinely new article. If the input is only an idea, do not imply that a URL or complete draft is required.

## Google Search and Discover questions

Use `get_google_performance` for Search, Discover, and Google News performance. Use `get_search_queries` only for aggregate web-search queries. All Google metrics, pages, queries, and associated articles returned by these tools are restricted to synced, published editorial WordPress posts with a non-empty canonical URL; non-editorial pages, homepage/archive URLs, drafts, and unmapped Search Console rows are excluded. Treat missing Discover query data as e

Preview of the first 4,000 characters. Read full instructions →

Release notes

Added a reusable TopicLift editorial-analysis skill to guide recommendations. Updated MCP guidance for consistent interpretation of traffic and search-performance data. No new permissions, authentication flows, tools, or data scopes were added.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
TopicLift

Package observed Nov 20, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 20, 2026 · 12:00 UTC
Latest observed change
Oct 25, 2026 · 12:04 UTC
Collection status
Collected

plugin_asdk_app_6a8c946ae1bc819196a64d8fc9810c6d

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.