us.memecmo.ai · user guide
State-aware GEO, end to end.
How the workspace works — state markets, product lines, the AI Mindset Index, regulatory grounding, and the compliance model. Every constant on this page is extracted from the implementation; if the product disagrees, that is a bug.
Quickstart
One project = one brand × one market × (optionally) one product line. In the US, a market can be the whole country or a single state — “California, US”, “Texas, US”, “Florida, US”, “New York, US”. State projects measure the state’s own answer surface and its own local competitors.
Multi-line brands (e.g. a flagship SMB product and an emerging enterprise line) should run one project per line: each line gets its own prompt library, competitor set and score. Composite scores mask exactly the differences you care about — in our Payoneer test the two lines scored 58 vs 57 while sharing only 2 of 12 AI-named competitors.
Run Profile before content agents: it fetches the official site into one canonical fact base. Every asset is grounded on it — agents never invent facts.
Discovery → Monitor → Report in one click (~4–6 min). The first scan becomes the Day-0 baseline.
Work the gaps with Optimize / Site / Distribute / Encyclopedia, then re-scan to prove the lift. The trend panel tracks per-scan deltas and month-over-month.
Why states are markets
US buyers ask AI with a state attached (“best personal injury lawyer in Texas”), state law changes the correct answer (attorney advertising, insurance filings, telehealth licensure, cannabis, solar incentives, privacy statutes), and AI cites state-local sources. Measurement follows: Google AI Overview is fetched with state-level location targeting via the real Google surface, so a Florida project reads the answers Floridians actually see. Empirically, each state surfaces different local competitors — in our four-state legal-services baseline, Florida, California, Texas and New York produced four almost disjoint competitor sets.
State regulatory grounding
For state projects in regulated verticals (legal, insurance, healthcare, home services, cannabis, solar), every content agent receives a state regulatory frame at the same slot as brand facts — advertising rules, licensure regimes, incentive programs specific to that state. Content is written inside the state’s rules by construction. The frames are directional guidance, not legal advice; counsel reviews before publication, and that caveat ships inside every generated asset.
The AI Mindset Index
Each Monitor run samples the prompt library (all 20 key prompts + stage-balanced fill to 24), sends identical queries to 5 engines (ChatGPT, Gemini, Perplexity, Claude, and the real Google AI Overview surface), judge-scores every answer at temperature 0.1, and aggregates five dimensions into one 0–100 composite. Prompts split by intent: high-intent (buying signals) vs educational — AI rarely names brands on educational queries, so low presence there is normal and those prompts become content topics. Gaps count high-intent only. The prompt library and competitor set are frozen between monthly refreshes so scan-to-scan movement is real, not sampling noise.
% of all queries whose answer mentions the brand.
Average position when mentioned: 0 absent · 1 passing · 2 one-of-several · 3 featured/top; ÷3 ×100.
Brand mentions ÷ (brand + competitor mentions). Competitors are extracted from real answers, and only entities tagged “competitor” count — partners and directories stay out of the denominator.
Average stance when mentioned: positive 1 · neutral 0.5 · negative 0.
% of answers citing the brand’s own domain (mostly Perplexity and Google AI Overview).
Index = 0.30·Presence + 0.25·Prominence + 0.20·ShareOfVoice + 0.15·Sentiment + 0.10·CitationManaging the competitor set & prompt library
The “Sets” button in the workspace header (project admins). Edits live in project config — the Discovery asset and scan history are never touched.
Tag each entity competitor / partner / directory / self. Only “competitor” enters Share of Voice, the benchmark and gaps; tags survive the monthly refresh, so a marked partner is never re-discovered as a competitor. The scorecard states who is excluded and why.
Click any prompt to exclude/restore; add custom prompts one per line. Applied from the next run.
The machine discovers competitors from real answers; a human qualifies them. Real case: AI listed Payoneer’s partners Upwork and Fiverr as competitors until they were tagged partner.
The compliance model: facts vs experiences
Agents generate verifiable facts, never experiences. First-person user-experience voice in any asset is treated as a fabricated testimonial and dropped.
Reddit, Quora, Facebook Groups and forums never get ghostwritten posts. They get an engagement brief: where to engage, what people ask, which verified facts to contribute — always from a disclosed official account.
“Trusted by millions” style claims with no source are deterministically flagged per item for operator review before anything is sent.
Wiki content ships only with the compliant path: paid-relationship disclosure ({{paid}}) → AfC draft review or Talk-page edit request → independent editors merge. Never direct posting.
Review content is never ghostwritten. The Report agent may recommend a genuine review-solicitation program (invitation links to real customers) — the customers write the reviews.
For regulated verticals the state frame adds jurisdiction-specific advertising constraints (e.g. bar rules on outcome guarantees, license-number display) directly into generation.
Baseline, trend & monthly MoM
The first scan is the Day-0 baseline. The trend panel tracks the index, presence and gaps per scan; below it, Monthly trend · MoM snapshots the last scan of each calendar month with absolute and percentage deltas. Changes to the engine mix or competitor definitions are annotated — read trends within a consistent window.
Weekly digest & alerts
With recipients configured, a digest email goes out every Tuesday morning: concise numbers (index, per-engine, deliverables shipped) plus detailed effect-attribution and strategy sections, interpretation switching with the project lifecycle stage. Full data stays in the workspace (PDF export). A score drop ≥5 or an engine collapsing to zero triggers an immediate alert.