PlugIndex

Directory / plugin

Creator Assistant Planner

v1.2.0 · by Alessandro Lioce

Suggests new blog post topics from Google Search Console content gaps, prioritized with Google Analytics data.

View on WordPress.orgHomepage

About this plugin

Creator Assistant Planner connects to your site’s Google Search Console and Google Analytics data (via Creator Assistant Hub’s shared Google connection) to find search queries with real demand but no dedicated content on your site, groups them into topic clusters, and ranks them by priority so you always know what to write next.

Requires Creator Assistant Hub, active and connected to Google.

External services

This plugin connects to the following third-party services. Data is sent only after the site owner has connected Creator Assistant Hub to Google and accepted the Creator Assistant terms in the Hub settings, and only when the weekly content-gap run (or “Generate now”) runs, or when a plan item is saved. Nothing is sent on activation.

  • Google Search Console API and Google Analytics (GA4) Data and Admin APIs (searchconsole.googleapis.com, analyticsdata.googleapis.com, analyticsadmin.googleapis.com): read the site’s search queries (query text, impressions, clicks) and page views of its own posts, and list the properties of the connected Google account so the site owner can choose one. The requests are authenticated with the access token of the Google connection managed by Creator Assistant Hub (read-only scopes webmasters.readonly and analytics.readonly). What is sent to Google is the property identifier, the date range and the page paths of the site itself. No visitor data is sent.

  • Clustering service (AWS Lambda and AWS Fargate), operated by the plugin author: groups the unclaimed search queries into topic clusters. When a run reaches that step, the plugin sends the service the URLs of two REST endpoints of your own site (to read the query vectors and to post the result back), the name of the vector collection and the clustering parameters. The service then reads the search queries and their vectors from your site and posts the clusters back. It processes them only while the job runs and does not store them.

  • OpenAI and Qdrant Cloud, through Creator Assistant Hub: to check that a suggestion does not duplicate existing content, the text of the suggested titles and summaries and of the editorial plan items is sent to OpenAI to generate embeddings and short summaries, and the resulting vectors are stored in the site owner’s own Qdrant Cloud cluster. The API credentials are the ones configured in Creator Assistant Hub; see its readme for details.

Plugin tags