toprank-setup-cms

Validate CMS connectivity, credentials, and access permissions for WordPress, Strapi, Contentful, and Ghost.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/seppegadeyne/toprank-skills --skill toprank-setup-cms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: toprank-setup-cms
Source: https://github.com/seppegadeyne/toprank-skills/tree/main/toprank-setup-cms
Command: npx skills add https://github.com/seppegadeyne/toprank-skills --skill toprank-setup-cms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of failed SEO field audits caused by unvalidated CMS connectivity, invalid credentials, or insufficient access permissions, saving time troubleshooting issues mid-audit.

Core Features & Use Cases

  • Multi-CMS Preflight Validation: Run connectivity and permission checks for WordPress, Strapi, Contentful, and Ghost CMS instances before starting SEO work.
  • Credential & Scope Verification: Confirm API keys, app passwords, and access tokens are valid and have the required read or write scopes for your audit tasks.
  • Use Case: When preparing to audit a Contentful-powered e-commerce content site, use this Skill to verify your access token can read the product content type you need to analyze, avoiding failed checks later in the workflow.

Quick Start

Use the toprank-setup-cms skill to run a preflight check for your WordPress site at https://yourclientblog.com with your stored CMS credentials to confirm connectivity before starting an SEO audit.

Frequently Asked Questions about toprank-setup-cms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate CMS connectivity before running a SEO field audit?

To validate CMS connectivity before a SEO field audit, run a preflight check against your CMS API to confirm credentials, access tokens, and read scopes are active. This prevents mid-audit failures caused by misconfigured connections.

Does this preflight check work with WordPress, Strapi, Contentful, and Ghost?

Yes, the preflight check works with WordPress, Strapi, Contentful, and Ghost CMS instances. It verifies API keys, app passwords, and access tokens to ensure you have the required permissions for content and schema audits.

Why does my SEO content audit fail midway through checking metadata fields?

Your SEO content audit fails midway because of invalid credentials, insufficient API scopes, or unvalidated CMS connectivity. Running deterministic preflight checks beforehand identifies these access permission issues to prevent workflow interruptions.

How do I verify API scopes and credential validity for a Contentful SEO audit?

To verify API scopes and credential validity for a Contentful SEO audit, test your access token against the specific content type you need to analyze. This confirms read permissions and avoids failed metadata checks later in the workflow.

What is the best way to prevent failed SEO audits caused by insufficient API access?

The best way to prevent failed SEO audits caused by insufficient API access is running deterministic preflight checks. Confirming CMS connection validity and read or write scopes before starting eliminates time spent troubleshooting issues mid-audit.