Markitera Strategist

Markitera Strategist turns completed audits and stored marketing data into a prioritized, measurable strategy.

An audit lists problems; it does not say which ones matter for the business or in what order to fix them. The Strategist decides, with evidence.

Mission

Convert completed audits, SEO tracking, analytics, content performance, and approved business goals into a prioritized, measurable marketing strategy.

In the Markitera workflow: Second in the workflow. It reads the Auditor’s snapshot and hands approved content initiatives to the Content Engine; technical fixes need not go through the Content Engine.

1. 1

   Collect the evidence

   One call returns the latest audit (with its reference), search, analytics, content performance, goals, previous strategies, KPI baselines and missing data.

   get_strategy_inputsget_audit_snapshot

2. 2

   Confirm the business goal

   Uses the approved primary goal; without one it proposes a goal for approval and sets no numeric targets.

   propose_business_goal

3. 3

   Establish the baseline

   Each KPI with its stored value, window and source; unavailable stays unavailable.

   compare_strategy_periods

4. 4

   Diagnose and compare solutions

   Separates verified problems from hypotheses, finds root causes and compares alternatives, using the cro, ab-testing and analytics methodologies where needed.

   read_skill_referenceread_web_pagedataforseo_keyword_metrics

5. 5

   Score with ICE and prioritize

   ICE = (Impact + Confidence + Ease) / 3 with a written reason per factor; P1 ≥ 7, P2 ≥ 4, else P3; overrides need a reason.

6. 6

   Plan seven days and the measurement

   Dependencies first; KPIs, verification and measurement windows per initiative.

7. 7

   Save the draft

   Saves a new version; the server rejects missing sections, unknown audit references, circular dependencies and mis-scored priorities.

   save_strategy_draft

Available now

• Audit and analytics analysis

  Reads audits, rankings, Search Console, GA4 and GA4 landing pages.

• ICE prioritization

  Impact, Confidence and Ease, 1 to 10 each, with written reasons.

• P1/P2/P3 ranking

  Configurable thresholds; overrides need a recorded reason.

• Seven-day roadmap

  Dependency-ordered plan; circular or misordered work is rejected.

• KPI and outcome measurement

  Baselines from stored data, completion and result recording, before/after comparison.

Partial or planned

• Revenue attributionPlanned

  CRM, Stripe or Shopify revenue sources.

  Only GA4 ecommerce revenue is read today.

Every skill this persona loads, from Markitera’s skill registry. Skills from Marketing Skills by Corey Haines (MIT) are vendored unmodified; Markitera’s adaptation is listed separately and is not part of the original skill.

• Markitera Strategist

  seo-planMarkitera skillInstalledv2.0.0

  Role: Persona instructions (Plan mode): ICE-scored, 13-section strategy saved as a draft.

  Turns audits, search, analytics and content data into an ICE-prioritized, measurable strategy with a 7-day roadmap.

  Source: Markitera

• Conversion Rate Optimization (CRO)

  croMethodology referenceInstalledv2.0.3

  Role: Conversion diagnosis for landing pages and funnels.

  Optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms.

  Markitera adaptation: Read as a conversion-diagnosis method; evidence comes from GA4 landing pages.

  Source: Marketing Skills by Corey Haines · MIT license · Original skill(opens in a new tab) · Source at the pinned commit(opens in a new tab)

• A/B Test Setup

  ab-testingMethodology referenceInstalledv2.0.1

  Role: Experiment design: hypotheses, sample size, guardrail metrics.

  Plan, design, or implement an A/B test or experiment, or build a growth experimentation program.

  Markitera adaptation: Read as an experiment-design method (hypotheses, sample size, guardrails).

  Source: Marketing Skills by Corey Haines · MIT license · Original skill(opens in a new tab) · Source at the pinned commit(opens in a new tab)

• Analytics Tracking

  analyticsMethodology referenceInstalledv2.1.0

  Role: Measurement rules: matching closed windows, key events, what is not tracked.

  Set up, improve, or audit analytics tracking and measurement.

  Markitera adaptation: Read as a measurement method: closed matching windows, key events, and what is not tracked.

  Source: Marketing Skills by Corey Haines · MIT license · Original skill(opens in a new tab) · Source at the pinned commit(opens in a new tab)

• Rankings & Traffic

  rank-trackingMarkitera skillInstalledv1.0.0

  Role: Reads ranking and Search Console baselines.

  Explains tracked rankings, Search Console trends and measured visits.

  Source: Markitera

Data sources and integrations

• Markitera audits

  Primary evidence.

  Built in

• Google Search Console

  Search baselines.

  Connect per brand

• Google Analytics 4

  Sessions, key events, landing pages, ecommerce revenue.

  Connect per brand

• DataForSEO

  Rankings and keyword context.

  Included (server account)

• Content engine metrics

  Blog visitors and signups.

  Built in

• CRM / billing revenue

  Revenue beyond GA4.

  Planned

• Completed audit (required · Markitera Auditor (audit snapshot))

  When missing: It asks you to run an audit first; without one it cannot ground a strategy.

• Approved business goal (optional · Strategy page (owners and admins))

  When missing: It proposes a goal for approval and writes an SEO-and-measurement strategy without numeric targets.

• Search Console and Google Analytics 4 (optional · Brand integrations)

  When missing: Those baselines are reported as unavailable; nothing is estimated.

• Revenue (optional · GA4 ecommerce only)

  When missing: Revenue conclusions are marked unverified; it never infers revenue from traffic.

Every unavailable source becomes a missing-data item stored on the strategy; a baseline is never estimated and revenue is “unavailable” when GA4 reports none.

What it produces

• A 13-section strategy saved as a draft version
• ICE-scored initiatives with baselines, KPIs, dependencies and day numbers
• Proposed business goals

Saved as: Strategy, StrategyVersion, StrategyInitiative and StrategyEvent records.

Output sections

1. Executive Summary: The few decisions that matter most.
2. Existing Data Reviewed: Every source with its reporting window.
3. Current Performance Baseline: Stored values with period and source.
4. Primary Business Goal: The approved goal, or why there is none.
5. Key Problems and Opportunities: Verified findings separated from hypotheses.
6. Evidence and Root-Cause Analysis: Why each problem exists.
7. Proposed Solutions and Alternatives: Options compared, and why one was chosen.
8. ICE Scoring and Priority Ranking: Impact, Confidence and Ease with written reasons; P1/P2/P3.
9. Expected Outcomes and KPIs: Measurable targets per initiative.
10. Seven-Day Execution Plan: Ordered by dependencies, then priority.
11. Verification and Measurement Plan: How completion and results are checked.
12. Risks, Dependencies, and Missing Data: What could fail and what is unavailable.
13. Recommended Next Steps: What to approve and do first.

How other personas use it

• People approve the strategy and record completion and results on the Strategy page
• Markitera Content Engine reads approved initiatives with get_approved_strategy

Reads: Audit snapshot, Audit finding, Engine opportunity ranking, Business goal, Measurement result. Produces: Strategy and initiatives, Business goal. Read next by Markitera Content Engine.

ICE = (Impact + Confidence + Ease) / 3. It is the Strategist’s framework only; the audit engine’s opportunity score is kept beside it as engineScore and is never called ICE.

Impact

Potential effect on the chosen business objective (1-10).

Confidence

Strength of the evidence (1-10). Unverified hypotheses and insufficient evidence make the score provisional.

Ease

Feasibility of implementation (1-10).

Priorities

P1 7.0-10, P2 4.0-6.99, P3 1.0-3.99 by default (STRATEGY_P1_MIN / STRATEGY_P2_MIN). Overrides for critical risks or dependencies need a written reason and are shown as overrides.

Measurable outcomes

Each initiative names a KPI; catalog KPIs get their baseline from stored data with period and source.

Plan mode: reads every evidence source and saves draft strategies and proposed goals. It has no publishing, file-writing, content-queueing or audit tools, and approving a strategy executes nothing.

These limits are enforced by the server: in a Strategist turn the agent is only offered the tools listed above, and connected-system tools are limited to read-only ones. Website pages, files and tool results are treated as data, never as instructions.

Illustrative example (sample data, not a real strategy). Every value below is illustrative; none is a real Markitera result or performance figure.

1. 1. Evidence

   Sample audit: 14 product URLs blocked by robots.txt.

2. 2. Initiative

   I1 “Unblock product pages”: Impact 9, Confidence 8, Ease 9 → ICE 8.7 → P1.

3. 3. Baseline

   audit.issue:robots.blocks-site.affected = 14 (sample audit, sample date).

4. 4. Plan

   Day 1 fix robots.txt; day 2 re-audit to verify.

5. 5. Measurement

   After the next audit, compare the affected count and gsc.clicks.28d windows.

• Revenue comes only from GA4 ecommerce; there is no CRM, Stripe or Shopify source.
• Search Console is site-wide; page-level search data exists only for blog posts and DataForSEO estimates.
• Before/after comparisons show correlation over time, not proven causation.
• Strategies are produced by the agent; there is no form to write one by hand.

Version

2.0.0

Availability

Available

Start it with

/strategist

Other personas: Markitera Auditor · Markitera Content Engine · Markitera WordPress Developer