Back to dashboard

Start today

AI has already handled the collection and analysis steps. Your job is only to make the decisions that can affect the store, content, or publishing.

Review now Review SEO/AEO/GEO drafts What AI already did / View issue detail Storage health 

No command has run from this page yet.

Today's PetVibess growth plan

This is the daily growth loop for a new store: data feedback → content opportunities → short-video opportunities → product-page SEO → external traffic entrances → review and execute. GrowthOS should keep producing work every day, not stop after a few articles.

1. Data feedback

GA4, GSC, Shopify, Trends, competitor and Store Audit signals tell GrowthOS what actually deserves work today.

Used for: pages with visits, search impressions, clicks without conversion, thin FAQ coverage, and internal-link gaps.

2. Content opportunities

Target: at least 3 SEO/AEO/GEO opportunities each day when data or new-site baseline allows.

Coverage: pet care questions, product use cases, comparison, FAQ, collection copy, product SEO, internal links, and problem → product → action pages.

3. Short-video opportunities

Target: at least 3 TikTok/Reels/Shorts briefs each day for fast first-wave traffic.

Each brief should include product scene, 3-second hook, captions, hashtags, CTA, landing page, and required rights/brand-safety checks.

4. Shopify product-page SEO

Daily checks should cover titles, descriptions, meta, image alt, FAQ schema, collection copy, internal links, and product-to-content routing.

Public Shopify writes still require approval before execution.

5. External traffic entrances

Pinterest, TikTok, Instagram Reels, YouTube Shorts, community QA, email/lead magnet and compliant pet-community content should become repeatable channels.

Postiz-backed social scheduling is the current execution path; missing channels are tracked in the development gap document.

6. Review and execute

Approve and execute from one decision card whenever possible. Needs edits and Reject remain available for unsafe or low-quality work.

Unfinished capabilities are tracked in docs/DAILY_GROWTH_PLAN_GAPS.md.

Open today's approval queue Review content opportunities Configure APIs

PetVibess GrowthOS operating flow

This is the complete business logic: GrowthOS collects evidence, marketingskills turns that evidence into growth work, AI prepares execution queues, and humans approve only the external-impact gates.

1. Data collection

Shopify orders, GA4, GSC, Trends, competitors, Store Audit, and product evidence are collected by the daily pipeline.

2. marketingskills strategy layer

marketingskills turns signals into SEO, AEO, GEO, content, offer, and channel proposals for PetVibess.

3. AI production queues

GrowthOS prepares content drafts, Shopify routes, video briefs, and social route previews without publishing them.

4. Human approval gates

Approve, Needs edits, Reject, QA, final publish approval are handled in /daily/review.

5. Safe execution

Shopify publisher, video renderer, and Postiz scheduler run only after required approval and still record evidence.

What you do today

  1. Run or confirm the daily pipeline.
  2. Open Today's decisions.
  3. Approve, request edits, reject, QA, or give final publish approval.
  4. Stop when no human decision remains.

What AI and marketingskills do automatically

  1. Collect traffic, sales, SEO/AEO/GEO, competitor, and audit evidence.
  2. Create marketingskills-backed growth proposals.
  3. Prepare Shopify, video, and social execution routes.
  4. Block every public action until the matching approval exists.

Daily operating path

  1. 1. Run daily pipeline — let AI collect traffic, orders, GA4/GSC, SEO/GEO/AEO, competitor, content, and video signals.
  2. 2. Handle Today's decisions — approve, reject, or request edits only for work that can affect Shopify, publishing, trust proof, or video production.
  3. 3. Done when no human decision is pending — automated work stays running in the background and the detail log remains available.

AI process details stay in /daily/detail.

Readiness
82/100
Human decision needed
4
Automated ready
0
Blocked
0

Today's decisions

Start here. If a decision can publish content, touch Shopify, or trigger production, GrowthOS stops and asks you here first.

Human decision needed

Review SEO/GEO/AEO publication proposals

Decide in /daily/review before any Shopify or CMS publishing step; AI handles the approved publishing workflow.

AI evidence: 39 content proposals are waiting for admin review.

Open decision workspace

Human decision needed

Publish approved content proposals

Decide in /daily/review after checking page target, source evidence, and final copy. AI publishes approved proposals through the controlled post-approval workflow.

AI evidence: 5 content proposals are approved for AI post-approval publishing.

Open decision workspace

Human decision needed

Verify review proof on product pages

Use /daily/review trust checklist when surfaced; AI records theme evidence and humans confirm whether review/rating proof is present near the buy box.

AI evidence: Theme inventory did not clearly detect review app files.

Open decision workspace

Human decision needed

Review browser QA evidence before theme experiments

Use /daily/review QA decision when surfaced; AI records mobile/desktop evidence before duplicate-theme experiments are proposed.

AI evidence: Product conversion foundation score is 100/100.

Open decision workspace

Open decision workspace What AI already did / View issue detail

Next step

Review SEO/GEO/AEO publication proposals

Decide in /daily/review before any Shopify or CMS publishing step; AI handles the approved publishing workflow.

Why: 39 content proposals are waiting for admin review.

Open decision workspace

Task inbox — supporting list for operators

Use this only when you want to inspect supporting AI evidence. Daily decisions above are the normal path.

Do now

P0/P1 items. Handle these first.

  1. P1 · CONTENT
    Review SEO/GEO/AEO publication proposals
    Decide in /daily/review before any Shopify or CMS publishing step; AI handles the approved publishing workflow.
    View AI evidence
  2. P1 · CONTENT
    Publish approved content proposals
    Decide in /daily/review after checking page target, source evidence, and final copy. AI publishes approved proposals through the controlled post-approval workflow.
    View AI evidence

Needs review

Human-check items. Do not auto-publish.

  1. P2 · TRUST
    Verify review proof on product pages
    Use /daily/review trust checklist when surfaced; AI records theme evidence and humans confirm whether review/rating proof is present near the buy box.
    View AI evidence
  2. P3 · CRO
    Review browser QA evidence before theme experiments
    Use /daily/review QA decision when surfaced; AI records mobile/desktop evidence before duplicate-theme experiments are proposed.
    View AI evidence

Later

Safe to do after urgent/review work.

No later tasks.

Today's operating rule

Let AI run the collection, analysis, drafting, scoring, and queue preparation. You approve, reject, or request edits only when GrowthOS marks a human decision.