MyBacklinks CLI – Campaign Tracking
Manage SEO projects and track link-building campaign progress using the MyBacklinks CLI.
What this skill does
# MyBacklinks CLI – Campaign Tracking Manage your SEO projects and track every backlink in your link-building campaigns. ## Prerequisites Authenticate once before running any command: ```bash mybacklinks login --api-key <YOUR_API_KEY> mybacklinks status # verify credentials and credits ``` All commands return JSON by default. Use `--md` for Markdown output, and `--base-url <url>` to override the server. --- ## Commands ### 1. list-projects List all projects in your account. Each project represents a website or product you're building backlinks for. **When to use:** Get an overview of active campaigns, find a project ID before querying its backlinks, or audit your project portfolio. ```bash mybacklinks list-projects [options] ``` | Option | Required | Type | Description | |--------|----------|------|-------------| | `--limit` | No | number | Max projects per page | | `--cursor` | No | string | Pagination cursor from previous response | | `--all` | No | boolean | Auto-paginate through all results | **Examples:** ```bash mybacklinks list-projects mybacklinks list-projects --limit 5 mybacklinks list-projects --all --json ``` **Typical response fields per project:** | Field | Description | |-------|-------------| | `id` | Project UUID (used in other commands as `--project-id`) | | `name` | Project display name | | `domain` | Associated domain (may be null) | | `status` | Project status (`active`, etc.) | | `updatedAt` | Last update timestamp | | `createdAt` | Creation timestamp | --- ### 2. create-project Create a new project in your account. Each project can then be used with backlink tracking commands. **When to use:** Start tracking a new website, app, or product before adding campaign backlinks. ```bash mybacklinks create-project --name <name> --url <url> --type <website|app|other> [options] ``` | Option | Required | Type | Description | |--------|----------|------|-------------| | `--name` | Yes | string | Project display name | | `--url` | Yes | string | Project URL with protocol | | `--type` | Yes | string | Project type: `website`, `app`, or `other` | | `--description` | No | string | Project description | | `--contact-email` | No | string | Single project contact email | | `--contact-emails` | No | string | Comma-separated contact emails | | `--long-descriptions` | No | string | Comma-separated reusable long descriptions | | `--comment-templates` | No | string | Comma-separated reusable submission comments | | `--social-urls` | No | string | Comma-separated social profile URLs | | `--sitemap-url` | No | string | Project sitemap URL | | `--llms-txt-url` | No | string | Project llms.txt URL | | `--robots-txt-url` | No | string | Project robots.txt URL | | `--status` | No | string | Project status, default `active` | | `--group-name` | No | string | Project group name | | `--pinned` | No | boolean | Pin the project | **Examples:** ```bash mybacklinks create-project --name "Example" --url https://example.com --type website --json mybacklinks create-project \ --name "Example App" \ --url https://app.example.com \ --type app \ --contact-email [email protected] \ --social-urls https://x.com/example,https://github.com/example \ --json ``` **Typical response fields:** | Field | Description | |-------|-------------| | `id` | Project UUID for follow-up commands | | `name` | Project display name | | `url` | Project URL | | `type` | Project type | | `status` | Project status | | `contactEmails` | Autofill contact emails | | `createdAt` | Creation timestamp | | `updatedAt` | Last update timestamp | --- ### 3. fetch-project-info Fetch detailed information for a single project by ID or domain. **When to use:** Get full project metadata, check settings, or confirm a project exists before updating it. ```bash mybacklinks fetch-project-info [options] ``` | Option | Required | Type | Description | |--------|----------|------|-------------| | `--project-id` | One of these | string | Project UUID | | `--domain` | One of these | string | Project domain | Provide either `--project-id` or `--domain` (not both). **Examples:** ```bash mybacklinks fetch-project-info --project-id 56777265-5db3-48a0-ac38-2cc25d04d80c mybacklinks fetch-project-info --domain mybacklinks.app --json ``` --- ### 4. update-project-info Update metadata for an existing project. **When to use:** Rename a project, update its URL, change its description, or toggle its status. ```bash mybacklinks update-project-info --project-id <id> [options] ``` | Option | Required | Type | Description | |--------|----------|------|-------------| | `--project-id` | Yes | string | Project UUID | | `--name` | No | string | New project name | | `--description` | No | string | New project description | | `--url` | No | string | New project URL | | `--status` | No | string | New status | **Examples:** ```bash mybacklinks update-project-info --project-id proj_abc --name "My SaaS v2" mybacklinks update-project-info --project-id proj_abc --url "https://newsaas.com" --status active ``` --- ### 5. fetch-project-backlinks Retrieve backlinks associated with a project. Supports filtering and pagination. **When to use:** Audit current backlink portfolio, check indexing status, find backlinks from a specific resource domain, or export all backlinks for reporting. ```bash mybacklinks fetch-project-backlinks --project-id <id> [options] ``` | Option | Required | Type | Description | |--------|----------|------|-------------| | `--project-id` | Yes | string | Project UUID | | `--status` | No | string | Filter by status (`indexed`, `pending`, `lost`, etc.) | | `--resource-domain` | No | string | Filter by the domain where the backlink is placed | | `--anchor-text` | No | string | Filter by anchor text substring | | `--target-url` | No | string | Filter by target URL on your site | | `--limit` | No | number | Max backlinks per page | | `--cursor` | No | string | Pagination cursor from previous response | | `--all` | No | boolean | Auto-paginate through all results | **Examples:** ```bash # All backlinks for a project mybacklinks fetch-project-backlinks --project-id proj_abc # Only indexed backlinks mybacklinks fetch-project-backlinks --project-id proj_abc --status indexed # Backlinks from a specific resource domain mybacklinks fetch-project-backlinks --project-id proj_abc --resource-domain producthunt.com # Export everything as JSON mybacklinks fetch-project-backlinks --project-id proj_abc --all --json # Backlinks with specific anchor mybacklinks fetch-project-backlinks --project-id proj_abc --anchor-text "AI tools" ``` --- ### 6. update-project-backlinks Create a new backlink record or update an existing one within a project. Supports single-entry mode via CLI flags or batch mode via a JSON file. **When to use:** Log a newly placed backlink, update its status after verification, batch-import backlinks from a spreadsheet or automation script. ```bash mybacklinks update-project-backlinks --project-id <id> [options] ``` | Option | Required | Type | Description | |--------|----------|------|-------------| | `--project-id` | Yes* | string | Project UUID (*not needed when `--file` contains `projectId`) | | `--backlink-id` | No | string | Existing backlink ID (omit to create new) | | `--resource-id` | No | string | Link to a backlink resource from your database | | `--target-url` | No | string | Target URL on your site | | `--backlink-url` | Cond. | string | URL where the backlink is placed. Required when not using `--backlink-id` or `--resource-id` | | `--anchor` | No | string | Anchor text | | `--status` | No | string | Backlink status | | `--utm-source` | No | string | UTM source tag for attribution | | `--notes` | No | string | Additional notes | | `--file` | No | string | Path to JSON file for batch updates | #### Single-entry mode ```bash # Create a new backlink record mybacklinks update-project-backlinks \ --project-id proj_abc \ --target-url "https:
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".