Description

CometRank connects your WordPress site to CometRank, an external content and lead-generation platform. After you connect your site, CometRank can publish HTML pages to WordPress and provision lead-capture forms on published content.

Official WordPress connector for CometRank, developed and maintained by Brandshark.

What this plugin does on your WordPress site:

Pairs your site with CometRank using a secure bearer token (no manual token copy/paste).
Receives published HTML or zip bundles from CometRank and creates/updates WordPress posts and pages.
Normalizes CometRank HTML into native WordPress block markup (images, buttons, FAQs).
Stores visitor lead submissions locally before forwarding them to CometRank.
Retries failed lead deliveries automatically and lets admins review or export leads.

External service required

This plugin is a connector to CometRank. You need a CometRank account and an active connection before publishing and lead forwarding work. See CometRank for product details and account terms.

Privacy

Data stored in WordPress

Hashed bearer tokens and connection settings (options table).
Lead form submissions (custom cometrank_leads table).
Post metadata for published CometRank content (SEO fields, asset references, project IDs).

Data sent to CometRank

Site pairing registration (install ID, site URL, plugin version).
Published content payloads you send from CometRank.
Lead form submissions (name, email, phone, company, message, source URL, and related metadata).

When outbound calls occur

After activation and when connecting from CometRank (pairing).
When CometRank publishes content to your site (inbound to WordPress).
When visitor leads are forwarded or retried to CometRank.

By activating the plugin and completing the Connect flow in CometRank, the site administrator authorizes this integration. Review CometRank privacy and terms on cometrank.ai.

Screenshots

CometRank - AI SEO Writer settings page showing connection and lead capture status. — CometRank – AI SEO Writer settings page showing connection and lead capture status.

Local leads archive with export to CSV. — CometRank – AI SEO Writer settings page showing connection and lead capture status.

Installation

Install and activate the plugin from the WordPress Plugins screen (or upload the zip).
In WordPress admin, go to Settings CometRank – AI SEO Writer.
In your CometRank account, open Settings WordPress and click Connect.
Return to WordPress — the connection completes automatically.

For manual installs, upload the cometrank-publisher folder to wp-content/plugins/ and activate it.

FAQ

Do I need a CometRank account?: Yes. Publishing, pairing, and lead forwarding require an active CometRank account and a completed site connection.
Does the plugin work without CometRank?: The plugin installs and stores settings locally, but publishing and lead forwarding to CometRank require the external service. Visitor leads are still archived locally when submissions are received.
What happens if CometRank is temporarily unreachable?: Lead submissions are saved in WordPress first. The plugin queues failed forwards and retries them automatically. You can review leads under Settings CometRank – AI SEO Writer.
Does the plugin add “powered by” links on my public site?: No. The plugin does not add branding links to your front-end pages.
Can I publish from CometRank to existing WordPress posts?: Yes. CometRank can target an existing post by ID or slug when publishing via the plugin REST API.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“CometRank – AI SEO Writer” is open source software. The following people have contributed to this plugin.

Brandshark — CometRank

Translate “CometRank – AI SEO Writer” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

0.7.3

Lead form treats locally stored submissions as success (thank-you when forward is queued).
Settings page shows last lead forward error for admin debugging.

0.7.2

Lead capture modal: always enqueue lead-form script and config when post has lead capture enabled.
Do not require site-config or inline bundle CSS/JS meta before loading the contact modal.
Lead-form script depends on config so window.cometrankLeadForm is defined before handlers attach.
Skip duplicate inline bundled cometrank-lead-form.js; use plugin asset instead.

0.7.1

Accept POST on /categories for CometRank category sync (avoids cached HTML on GET REST URLs).

0.7.0

Seed default blog categories on activation when only Uncategorized exists.
New GET /categories endpoint for CometRank category sync.
Publish endpoints accept category_ids for WordPress posts.
WordPress.org review: inline bundle CSS, sideload images to Media Library, JSON-LD and inline script escaping fixes.

0.6.6

Bundle JS stored in post meta and enqueued via WordPress script API; uploads/cometrank holds static assets only (CSS, images, fonts).

0.6.5

install-verify response includes signed reconnect_url for CometRank Connect handoff.

0.6.4

Text domain aligned to WordPress.org slug cometrank.
Pairing redirect requires cometrank_verify matching install-verify nonce (CSRF protection).
Bundle upload path hardening for version segments and file copy containment.

0.6.3

Display name updated to CometRank – AI SEO Writer for WordPress.org.

0.6.2

WordPress.org review fixes: Author URI brandshark.com, wp_enqueue for lead config, IP sanitization, normalize-content capability checks, bundle upload allowlist.

0.6.1

Renamed display name to CometRank Publisher for WordPress.org clarity.
Updated author to Brandshark (CometRank) and added official connector affiliation in readme.

0.6.0

WordPress.org submission release.
Added GPL license, uninstall cleanup, and directory hardening.
Improved REST API permission callbacks and JSON-LD output safety.
Removed third-party CDN JavaScript loading (WordPress.org guideline compliance).
Rewrote plugin readme for the WordPress.org plugin directory.

0.5.6

Local lead archive with CSV export and retry queue.
Docker-aware API base URL resolution for lead forwarding.
Content normalization for images, CTAs, and FAQ sections.