Overview

Dashboard Quickstart

How CiteLoop turns your domain into evidence-backed SEO and GEO content.

Interactive quickstartDashboard-firstEvidence-backedOne review gateSEO + GEO

Your role

Provide the domain, confirm context, approve drafts, and handle distribution decisions when needed.

CiteLoop role

Read, analyze, plan, write, check evidence, publish canonical content, prepare variants, and measure results.

Prerequisite

Create a project from a public product domain. CiteLoop needs enough accessible source material to build context, find recommendations, and keep every draft tied to evidence.

Use a crawlable homepage, docs site, changelog, or product marketing site.
Confirm product facts in Context before generated content becomes publishable.
Review analysis before recommendations enter the Content Plan.

The four steps

Create a project

Start with a public domain so CiteLoop can build a workspace around real product evidence.

Confirm context

Review product facts, source pages, rules, and crawl boundaries before planning content.

Review analysis

Keep the recommendations that should enter the plan; ignore the rest.

Approve and publish

Use the review gate once, then move canonical content toward publishing and distribution.

At a glance

Account owner	You or your team, starting from one product domain.
Context source	Public pages, confirmed facts, evidence snippets, and product rules.
Human gate	Review is the one approval step before content can move toward publishing.
What you get back	Analysis recommendations, planned topics, evidence-backed drafts, canonical URLs, and variants.
Best for	Teams that want a steady SEO and GEO content loop without inventing private metrics.
Need audit detail?	Use Settings > Activity Log for background events, failures, and degraded checks.

Install and initialize

Dashboard-firstAPI-style handoff

Initialize from the dashboard

Open CiteLoop, create a project, and move through Context, Analysis, Content Plan, Review, Publish, and Results in order.

project
  -> context profile
  -> accepted analysis
  -> content plan
  -> evidence-backed draft
  -> approved canonical article
  -> distribution variants
  -> result signals

Start here

Pick the path that matches where you are in the product loop. A new user can start from this page before a project exists; project-specific links appear after a project has been created.

Set up context

Connect a domain, let CiteLoop read public pages, then confirm the product facts and evidence it should use.

Create a content plan

Review analysis recommendations, then turn the ones you keep into topics, schedules, and content intent.

Review and publish

Approve evidence-backed drafts once, then let CiteLoop publish canonical content and prepare variants.

Core concepts

Project: The domain-level workspace CiteLoop reads, plans, reviews, publishes, and measures.
Context: The product profile, evidence library, source pages, voice, and rules used for every draft.
Analysis: Decision-ready recommendations that need review before they enter the plan.
Content Plan: The backlog of reviewed topics, angles, schedules, and generation intent.
Canonical: The primary article published on your main content surface.
Variant: A rewritten version prepared for a distribution surface after the canonical URL exists.
Distribution / Syndication: The semi-manual channel path for Dev.to, Hashnode, LinkedIn, forums, and other surfaces.
Review gate: The only human approval step before publishable content can go live.
Results: Measurement and diagnostics for SEO, GEO, crawler access, and AI-answer signals.
Settings > Activity Log: The advanced audit trail for degraded checks, failures, and automation details.

Workflow model

Home is the live source of next action

Docs explains why actions exist. Home decides what you should do now from current context health, review load, publishing state, and result signals.

Review is the only human gate

CiteLoop can prepare content automatically, but publishable content requires one approval step. Evidence blocked drafts must be corrected before approval.

The CiteLoop loop

Analysis feeds planning

Read your domain

Build context

Review analysis

Plan content

Generate drafts

Check evidence

Review once

Publish and distribute

Measure results

Feed analysis back into the plan

back to Content Plan

Pages in the dashboard

Home

Shows the current next action, loop momentum, context health, and what needs attention now.

Context

Shows what CiteLoop believes about your domain and the evidence behind publishable claims.

Analysis

Reviews automatically generated recommendations before they become content work.

Content Plan

Turns accepted analysis into topics, schedules, and drafting intent.

Review

Groups drafts that need approval and explains evidence issues in reviewer language.

Publish

Tracks canonical publishing, URL verification, and distribution-ready variants.

Results

Shows measurement coverage, diagnostics, crawler access, and GEO visibility signals.

Settings

Controls cadence, budget, automation, crawl boundaries, publisher connections, and notifications.

Settings > Activity Log

Keeps run details available for audit without making them a daily navigation item.

Common states and signals

CiteLoop docs explain stable user-facing concepts instead of hand-maintaining a second list of internal status strings. Exact labels should come from shared status mappings in product code.

Needs review

A draft is waiting for the one human gate before it can move toward publishing.

Evidence blocked

A claim needs support in Context or must be edited before approval.

Scheduled or published

Canonical content has moved from approved intent into the publishing lane.

Ready to distribute

Variants unlock only after the canonical URL is confirmed.

Visibility degraded

A provider or signal is limited; this is not the same as a negative visibility result.

Human decision needed

The system has enough information to ask for judgment instead of guessing.

Activity log entry

A background event exists for audit, cost, failure, or degraded automation context.

Limits and expectations

Public pages only

CiteLoop reads public pages and respects crawl boundaries. It does not bypass login walls or robots rules.

No invented metrics

Without Search Console or GA4, CiteLoop does not fake CTR, position, conversion, or private analytics.

Provider unavailable is not failure

A degraded answer-engine check lowers confidence. It does not prove visibility is bad.

Syndication is semi-manual in V1

CiteLoop prepares variants and compose links, while third-party posting still needs human handling.

Next steps

Create your first project

Start from a domain and let CiteLoop build context.

After a project exists

Open Context, Analysis, Content Plan, Review, Publish, Results, and Settings from the project sidebar.