Backend-first SEO operations

Make your SEO pipeline feel like a product team — not a pile of prompts, tabs, and TODOs.

Ghost Rank is the operating system for content teams that need strategy, generation, publishing, billing, and backlink economics to live in one deliberate workflow.

Run homepage audit See pricing

WordPress, Webflow, Shopify, Wix, Ghost, and secure webhooksCredits and backlinks tracked in one ledgerDesigned for modern TypeScript content stacks

publishing adapters already modeled

WordPress, Webflow, Shopify, Wix, Ghost, and secure webhooks ship in the current backend slice.

credit lanes under one ledger

AI credits and backlink credits are derived from immutable ledger entries rather than hidden counters.

workflow stages with explicit state

Analyze, generate, refine, publish, and observe without losing ownership of the underlying system state.

AED

billing designed around one clear contract

Ziina handles checkout while the backend owns entitlements, purchases, idempotency, and period logic.

What launches first

Connect the stack

Start with native CMS adapters for WordPress, Webflow, Shopify, Wix, and Ghost — or a secure webhook path for custom Next.js, Astro, and Remix stacks.

Generate with guardrails

Articles, image jobs, credits, and approval-friendly publishing states are all modeled in the backend.

Ship with observability

Retry history, webhook verification, and backlink refunds make the automation safer than “click and hope.”

Public audit

Turn the landing site into a real SEO-intelligence entry point

Instead of asking prospects to trust screenshots, we now let them run a live homepage audit. The backend owns the job, the worker performs the fetch and parsing, and the landing app renders the report cleanly.

Live fetch, not theatre

We follow the live homepage, redirect chain, and crawl surface so the report starts from the public reality.

Async and backend-owned

The public page submits work, but the backend and worker keep the queue, state, and result contract where they belong.

Actionable first-pass report

Access, indexability, on-page, and social signals are summarized with prioritized findings your team can fix next.

Why teams switch

A marketing site for a backend-led product

The point is not just to generate content. The point is to make SEO operations reliable enough that your team can trust them.

Backend-first

Your product logic lives behind the glass, not inside a page component.

Publishing adapters, retries, billing, credits, and backlink lifecycles stay in the backend so your frontend can stay elegant instead of carrying critical business rules in disguise.

Operational safety

Automation with receipts, not mystery meat.

Tracked publish attempts, webhook verification, idempotent credit grants, and refund-aware backlink states make the workflow safer than one-click magic that collapses under edge cases.

Modern stack support

Built for CMS teams and TypeScript site teams alike.

Native adapters cover classic publishing paths, while the product direction explicitly supports webhook, revalidation, and future repo-driven flows for Next.js, Astro, and Remix teams.

Workflow

One pipeline, five deliberate stages

The product stays opinionated where it matters: ownership, retries, billing, and content state transitions.

Model the website

Add the site, map the stack, and keep workspace ownership explicit from the first touchpoint.

Find opportunities

Build a backlog of article opportunities and internal-link suggestions instead of guessing topic demand.

Generate with context

Treat content and image generation as tracked jobs that feed a real content lifecycle, not isolated prompts.

Publish safely

Push to native adapters or secure webhook destinations with retries, status history, and destination identity.

Observe economics

See subscription entitlements, extra-credit purchases, and backlink refunds in one coherent operating model.

Integrations

Built for real stacks, not just one CMS lane

The current product slice already covers WordPress, Webflow, Shopify, Wix, Ghost, and secure webhooks, while the landing narrative keeps the TypeScript-first direction clear.

WordPress

Live adapter

Application-password validation, post create/update flows, and reusable destination IDs for repeat publishing.

• Verified credentials and permissions
• Draft and live publish modes
• Stored published URL and overwrite path

Webflow

Live adapter

Collection-aware publishing with field validation, domain matching, and live-publish guardrails.

• Collection slug and content field checks
• Staged versus live publishing control
• Published URL generation when live

Shopify

Live adapter

Blog-aware article publishing via Admin GraphQL with shop validation and explicit live-publish permission.

• Storefront domain verification
• Reusable article destination IDs
• Draft and live blog publishing

Wix

Live adapter

Draft-post publishing with site verification, API-key validation, and optional live release when the connection allows it.

• Site ID and Manage Blog permission checks
• Draft-first publishing with optional live release
• Reusable draft destination IDs for repeat updates

Ghost

Live adapter

Ghost Admin API publishing with site validation, HTML delivery, and reusable post IDs for safer repeat publishing.

• HTTPS site and admin-key verification
• Draft and live publish modes
• Published post URLs captured after successful delivery

Secure webhook

Live adapter

A clean bridge for custom stacks that want signed payloads, dedupe keys, retries, and stable destination IDs.

• Public HTTPS targets only
• Bearer or custom header authentication
• Deterministic dedupe keys for article delivery

Next.js / Astro / Remix

Planned first-class

The landing story makes our TypeScript direction explicit: webhook, revalidation, and content-store friendly patterns from day one.

• Webhook-friendly route handlers and server endpoints
• Revalidation or rebuild-driven publish modes
• Future Git / PR content recipes for repo-owned blogs

Headless and repo flows

Planned next

Future support is aimed at teams that want PR-reviewed content, headless CMS bridges, or static-site rebuild orchestration.

• Headless CMS bridge mode
• Revalidation trigger and rebuild workflows
• Git / PR publishing for docs-style content repos

Pricing snapshot

Clear plans, visible credit economics

The public pricing story should match the backend contract: AED billing, subscription entitlements, and additional credits when teams need extra throughput.

Free

A no-risk starting point for early evaluation and setup.

AED 0 / month

AED 0 / year yearly • Good for first workflow mapping

• 10 AI credits included
• 0 backlink credits
• Use it to test the workflow before committing

Basic

For solo founders and small teams shipping consistently.

AED 99 / month

AED 990 / year yearly • Save AED 198 yearly

• 100 AI credits each cycle
• 5 backlink credits included
• Great for one primary site and a predictable cadence

Pro

Most balanced

The balanced operating plan for growth teams with real publishing volume.

AED 299 / month

AED 2,990 / year yearly • Save AED 598 yearly

• 300 AI credits each cycle
• 15 backlink credits included
• The best fit for teams running content as an actual engine

Enterprise

For operators managing multiple sites, heavier publishing, and more rigorous collaboration.

AED 999 / month

AED 9,990 / year yearly • Save AED 1,998 yearly

• 1,500 AI credits each cycle
• 100 backlink credits included
• Built for larger portfolios and higher operational throughput

View detailed pricing →

Docs and help

The docs surface starts with integration clarity

Even before the full docs system lands, the marketing repo should explain how customers get from sign-up to their first working publish path.

Quick start

Choose the right integration lane first

The fastest path is not always the same path. The docs surface should help customers decide between native adapters, secure webhooks, and future rebuild or repo modes.

• CMS teams start with native adapters, including WordPress, Webflow, Shopify, Wix, and Ghost
• Custom app teams start with signed webhooks
• Static content teams prepare for rebuild or Git workflows

Billing and credits

Explain the economics without hand-waving

Subscriptions grant entitlements, extra purchases mint immutable records, and backlink failures can trigger refunds through the same ledger model.

• Ziina for checkout and payment events
• Separate AI and backlink credit balances
• One readable history for grants, purchases, and refunds

Publishing ops

Teach users what happens after they press publish

The docs should set expectations around validation, retries, destination IDs, and how live versus draft publishing differs across adapters.

• Explain verification before publish, including Ghost Admin API and Wix site permission checks
• Show retry and failure handling
• Document how draft versus live behavior differs across each integration

Launch direction

Start with the stack you already own. Let the platform handle the orchestration.

The landing repo now tells the story: backend-owned billing, credits, publishing adapters, and a clean path toward the full authenticated product — without pretending mobile is part of the plan.

Run a live audit Review integrations