From deployment to repeatable client growth

Your step-by-step Organic Signal operating guide

Follow this path for every client: establish the account boundary, capture the business brief, connect verified evidence, approve focused actions, deploy controlled sequences, and report measurable value.

Start here

The shortest path to the first useful result

If the platform is already deployed, these six moves take a new client from zero to an evidence-backed action queue.

1

Create organization

One secure client boundary.

2

Create workspace

One site, brand, location, or market.

3

Run AI discovery

Capture goals, customers, offers, and constraints.

4

Create OpenSEO project

One verified evidence project for the site/market.

5

Connect and verify

Map OpenSEO and the relevant client systems.

6

Review Today

Approve the first prioritized Growth Actions.

Before the first client

Production readiness checklist

Complete this once for the platform. The repository’s ENV.example separates the values that belong on Vercel, Railway, the worker, and the private OpenSEO service.

Frontend

Clerk keys, public app URL, backend API URL, and shared gateway secret.

Backend API

PostgreSQL, Clerk issuer, cron secret, frontend/CORS URLs, integration encryption key, AI provider, and email delivery.

Worker

The backend variables plus Redis and the arq worker start command.

OpenSEO

Private network URL, DataForSEO credential, local_noauth mode, optional GSC OAuth, and telemetry preference.

Never commit real credentials. OpenSEO in local_noauth mode must remain on a private network; do not give it an unprotected public Railway domain.

Repeat for every client

The complete 10-step workflow

Each step has a clear outcome. Do not move to scale until the earlier evidence, access, and approval steps are healthy.

01

Sign in and confirm app health

You know the frontend, API, database, queue, and AI services are reachable.

  1. 1Sign in with the first administrator account created through Clerk.
  2. 2Open App Health and resolve any red or degraded capability before onboarding a paying client.
  3. 3Confirm at least one AI provider is available and that the backend can reach PostgreSQL and Redis.
Open App Health

02

Create one organization for the client

The client’s users, sites, workspaces, and data have a secure tenant boundary.

  1. 1Open Organizations and select New organization.
  2. 2Use the client company name, add a short description, and set the permitted seat count.
  3. 3Use New demo client only for a time-limited trial; it creates an organization, starter workspace, and client-admin invite.

Do not combine unrelated clients inside one organization.

Manage organizations

03

Create the client workspace

You have an operating space for one site, brand, location, or search market.

  1. 1Open the organization, remain on the Workspaces tab, and select Create workspace.
  2. 2Name it for the site or market, such as “Main Store – US” or “Dallas Restaurant”.
  3. 3Create separate workspaces when a client has different domains, countries, languages, or independently managed locations.

04

Run AI-guided discovery

Organic Signal understands the business, audience, offers, competitors, constraints, and success metric.

  1. 1Open AI Assistant and choose the workspace.
  2. 2Answer the discovery questions with real business detail: products or services, locations, customers, margins, seasonality, competitors, and conversion goals.
  3. 3Generate the campaign plan, refine anything that is incorrect, then approve it to create the initial campaign.

A strong brief produces better AI decisions than a vague request such as “improve SEO”.

Start AI discovery

05

Create the matching OpenSEO project

The workspace can use verified SERP, backlink, domain, GSC, and audit evidence.

  1. 1Open your private OpenSEO dashboard and create one project for this domain, language, and market.
  2. 2Configure rank-tracked keywords, connect Google Search Console where available, and run the initial site audit.
  3. 3Copy the project ID from OpenSEO. Do not reuse another client’s project.

One OpenSEO installation can serve every client, but each client site/market needs its own OpenSEO project.

06

Connect and verify integrations

Organic Signal can measure performance and execute approved work through client systems.

  1. 1Inside the workspace, open Integrations and connect OpenSEO Intelligence.
  2. 2Enter the OpenSEO project ID, exact domain, location code, and language code; then select Verify project.
  3. 3Connect the relevant CMS or commerce platform: Shopify, WordPress, Ghost, or Webflow.
  4. 4Only workspace or organization owners should manage credentials.

07

Build the first evidence-backed priorities

The team has a short queue of actions tied to observed evidence instead of generic AI suggestions.

  1. 1Open Today and review capability status, evidence, findings, and Growth Actions.
  2. 2Confirm the business impact, confidence, source, and freshness before accepting an action.
  3. 3Add known competitors and priority keywords where the discovery plan did not already create them.

08

Deploy a controlled sequence

Agents execute a defined workflow with traceable handoffs.

  1. 1Open Deploy Sequence, select the workspace campaign, and choose the workflow that matches the approved objective.
  2. 2Use a precise seed topic, product category, service, location, or backlink objective.
  3. 3Start with one focused sequence, review its outputs, and expand only after the evidence and quality are acceptable.
Deploy a sequence

09

Review, approve, and publish

AI accelerates production without silently publishing unsupported or off-brand work.

  1. 1Review Content Drafts and Outreach for factual accuracy, tone, offer details, links, claims, and target fit.
  2. 2Approve only work supported by the client brief and current evidence.
  3. 3Use the connected CMS for publishing after approval; retain the audit trail for client reporting.

10

Monitor results and report value

The client sees what changed, why it mattered, and what happens next.

  1. 1Use Jobs, Agent Logs, Event Alerts, and Error Report to supervise execution.
  2. 2Track rankings, clicks, impressions, backlinks, content outcomes, leads, and revenue where the integrations support them.
  3. 3Create Report Clients only for people who need the simplified client portal; organization members use the main application.
  4. 4Use the weekly operating cadence below to keep every account moving.

Client playbooks

How the setup changes by business type

The operating model stays consistent, but the workspace boundary, integrations, first actions, and success metrics must match the client’s market.

Shopify / ecommerce

Workspace
One workspace per storefront, country, or language.
Connect
OpenSEO, Shopify, GSC, GA4, and the publishing CMS.
First actions
Category and product indexation, collection gaps, low-CTR queries, internal links, schema, out-of-stock risk, and linkable buying guides.
Measure
Organic revenue, non-brand clicks, ranking product/collection pages, assisted conversions, and gross-margin opportunity.

Property / real estate

Workspace
One workspace per domain or independently managed city/region.
Connect
OpenSEO, GSC, GA4, CRM/form tracking, listing feed, and CMS.
First actions
Neighborhood hubs, stale or duplicate listings, development pages, market reports, local authority links, schema, and lead-intent gaps.
Measure
Qualified enquiries, calls, viewing requests, location rankings, indexed listings, and cost per organic lead.

Local restaurant

Workspace
One workspace per location when listings, reviews, or offers differ.
Connect
OpenSEO, GSC, GA4, Google Business Profile workflow, menu/CMS, booking and call tracking.
First actions
NAP/hours consistency, menu and local schema, review themes, local landing pages, nearby citations, events, and neighborhood partnerships.
Measure
Calls, directions, bookings, local pack visibility, branded discovery, and high-intent menu/location visits.

Agency / multi-client team

Workspace
One organization per client; one workspace per site, brand, or market.
Connect
Client-specific OpenSEO project and connectors; never share credentials or project IDs between tenants.
First actions
Standardized discovery, capability checks, reusable playbooks, evidence review, approval SLAs, and portfolio risk monitoring.
Measure
Time to first value, actions completed, client outcomes, approval delay, account health, workload, and retention risk.

Operating rhythm

A simple weekly client cadence

Consistency compounds. Use the same review loop for every account, then adapt the actions to its evidence and commercial goals.

Monday

Evidence and priorities

Review Today, new GSC/SERP/backlink evidence, capability warnings, and overdue Growth Actions.

Tuesday

Production

Approve briefs and deploy the smallest sequences needed for the week’s top opportunities.

Wednesday

Quality and publication

Review drafts/outreach, verify claims and links, then publish approved work.

Thursday

Authority and distribution

Run backlink reclamation, partner outreach, internal linking, and content distribution.

Friday

Measurement and client update

Record outcomes, explain movement, identify blockers, and agree on next week’s three priorities.

Troubleshooting

When something does not work

Start with capability and evidence status. Do not compensate for a broken measurement connection with generated estimates.

The app will not start

Check Railway variables for DATABASE_URL, CRON_SECRET, and CLERK_JWT_ISSUER; then inspect backend logs and App Health.

OpenSEO verification fails

Confirm OpenSEO is running, the MCP URL ends in /mcp, private networking resolves, the project ID exists, and the configured domain exactly matches.

No ranking or backlink data

Verify DataForSEO credentials on OpenSEO, confirm budget guardrails have not been reached, and inspect Jobs and Error Report.

AI produces weak output

Improve the discovery brief, narrow the task, add the exact audience/offer/market constraints, and require current evidence before generation.

A job is queued but not running

Confirm Redis and the Railway worker are online, then review Jobs, Agent Logs, worker logs, and the scheduled cron trigger.

Client cannot sign in or receive an invite

Check Clerk, FRONTEND_URL, email provider credentials, sender verification, seat limits, invite expiry, and spam folders.

Ready to implement the first client?

Create the organization and workspace first. Then let AI discovery guide the campaign brief before connecting evidence and deploying work.

Create client
Client data and AI output still require human judgment, access controls, and approval before publication or outreach.