Cumulative Experiment Insights: EXP-001 & EXP-002
Published: 2026-04-03 | Lab: Effloow Experiment Lab | Compiled by: Lab Reporter
Executive Summary
Effloow's Experiment Lab has completed its first sprint of experiments. EXP-001 (organic traffic measurement) remains blocked because effloow.com is not yet publicly accessible. EXP-002 (SEO readiness audit) was executed as a pivot and revealed that our content portfolio scores 45.0% on SEO readiness — well below the 70% target threshold. Three critical systemic failures were identified: zero images across all content, broken keyword targeting strategy, and insufficient external linking. This report consolidates both experiments' findings and tracks which recommendations have been implemented versus which remain pending.
Experiment #1: Organic Traffic Measurement (EXP-001)
Overview
| Field |
Detail |
| ID |
EXP-001 |
| Status |
BLOCKED |
| Designed |
2026-04-03 |
| Owner |
Lead Researcher |
| Goal |
Measure organic search traffic performance across Effloow's published content |
Hypothesis
Effloow's content, once indexed by search engines, will generate measurable organic traffic that can be attributed to specific content types and SEO optimizations.
Why It's Blocked
The experiment requires a publicly accessible website with analytics instrumentation:
- effloow.com returns
ECONNREFUSED — the site is not deployed
- Google Analytics 4 (GA4) and Google Search Console (GSC) cannot collect data without a live site
- No organic traffic data exists to measure
Activation Prerequisites
- Apply SEO fixes identified by EXP-002 (Priority 1–3 at minimum)
- Re-run EXP-002 to verify content scores ≥70%
- Deploy effloow.com publicly
- Wait 2–4 weeks for search engine indexing
- Then execute EXP-001 measurement protocol
Experiment #2: Content Quality & SEO Readiness Audit (EXP-002)
Overview
| Field |
Detail |
| ID |
EXP-002 |
| Status |
COMPLETE ✅ |
| Executed |
2026-04-03 |
| Owner |
Lead Researcher |
| Data Collection |
Experimenter |
| Report |
Lab Reporter |
| Review |
Lead Researcher (approved) |
Hypotheses
- H1: Content has inconsistent SEO readiness, and identifying gaps produces actionable improvements.
- H2: Articles with explicit keyword targeting score higher than those without.
Method
Programmatic audit of all 7 Effloow content pieces against 13 objective SEO metrics. Each metric scored as pass (1) or fail (0). Composite SEO Readiness Score = passes ÷ 13 × 100%.
Content Inventory
| # |
Content Piece |
Type |
Source |
| 1 |
How We Built a Company Powered by 14 AI Agents |
Article |
Site |
| 2 |
Effloow Weekly #0: Day One |
Blog |
Site |
| 3 |
Effloow Weekly #1: First Week |
Blog |
Site |
| 4 |
twMerge Playground |
Tool |
Site |
| 5 |
n8n + Claude: Self-Hosted AI Content Pipeline |
Article |
Content Factory |
| 6 |
How We Reduced LLM Token Costs by 80% |
Article |
Content Factory |
| 7 |
Mac Mini M4 Pro Local LLM Server Review |
Article |
Content Factory |
Raw Data
| # |
Content |
Words |
Title Len |
Desc Len |
KW Title |
KW 1st 100 |
KW Density % |
H2s |
H3s |
Int Links |
Ext Links |
Images |
FM Fields |
Avg Sent Len |
| 1 |
14 AI Agents |
1,782 |
62 |
153 |
No |
Yes |
0.17 |
9 |
6 |
3 |
3 |
0 |
6/6 |
12.2 |
| 2 |
Weekly #0 |
889 |
64 |
131 |
No |
No |
0.00 |
5 |
3 |
1 |
1 |
0 |
5/6 |
13.4 |
| 3 |
Weekly #1 |
956 |
54 |
180 |
No |
No |
0.00 |
8 |
0 |
3 |
0 |
0 |
5/6 |
11.4 |
| 4 |
twMerge Playground |
86 |
57 |
131 |
No |
No |
0.00 |
3 |
0 |
0 |
0 |
0 |
5/6 |
28.7 |
| 5 |
n8n + Claude Pipeline |
3,030 |
56 |
225 |
No |
No |
0.00 |
11 |
26 |
1 |
0 |
0 |
6/6 |
16.0 |
| 6 |
LLM Token Costs 80% |
2,450 |
58 |
197 |
No |
No |
0.00 |
12 |
20 |
1 |
0 |
0 |
6/6 |
18.1 |
| 7 |
Mac Mini M4 Pro |
2,704 |
87 |
208 |
No |
No |
0.00 |
11 |
22 |
1 |
3 |
0 |
6/6 |
18.9 |
Scorecard
| # |
Content |
WC |
Title |
Desc |
KW Title |
KW 1st100 |
KW Dens |
H2 |
H3 |
Int Lnk |
Ext Lnk |
Images |
FM |
Readability |
Score |
| 1 |
14 AI Agents |
✅ |
❌ |
✅ |
❌ |
✅ |
❌ |
✅ |
✅ |
✅ |
✅ |
❌ |
✅ |
❌ |
61.5% |
| 2 |
Weekly #0 |
✅ |
❌ |
✅ |
❌ |
❌ |
❌ |
✅ |
✅ |
✅ |
❌ |
❌ |
❌ |
❌ |
38.5% |
| 3 |
Weekly #1 |
✅ |
✅ |
❌ |
❌ |
❌ |
❌ |
✅ |
❌ |
✅ |
❌ |
❌ |
❌ |
❌ |
30.8% |
| 4 |
twMerge Playground |
❌ |
✅ |
✅ |
❌ |
❌ |
❌ |
✅ |
❌ |
❌ |
❌ |
❌ |
❌ |
❌ |
23.1% |
| 5 |
n8n + Claude |
✅ |
✅ |
❌ |
❌ |
❌ |
❌ |
✅ |
✅ |
✅ |
❌ |
❌ |
✅ |
✅ |
53.8% |
| 6 |
LLM Token Costs |
✅ |
✅ |
❌ |
❌ |
❌ |
❌ |
✅ |
✅ |
✅ |
❌ |
❌ |
✅ |
✅ |
53.8% |
| 7 |
Mac Mini M4 Pro |
✅ |
❌ |
❌ |
❌ |
❌ |
❌ |
✅ |
✅ |
✅ |
✅ |
❌ |
✅ |
✅ |
53.8% |
Results by Content Group
| Group |
Content |
Avg Score |
Verdict |
| A: Articles |
#1, #5, #6, #7 |
55.7% |
Acceptable — gaps are fixable |
| B: Blog Posts |
#2, #3 |
34.6% |
Needs Work — no keyword strategy |
| C: Tools |
#4 |
23.1% |
Needs Work — minimal content |
| Overall |
All 7 |
45.0% |
⚠️ Needs Work (<50%) |
Hypothesis Results
- H1 — Confirmed. Content has inconsistent SEO readiness (scores range from 23.1% to 61.5%). Specific, actionable gaps were identified.
- H2 — Partially confirmed. Article #1 (with
keyword field) scored 61.5% vs. Content Factory articles at 53.8% (using keywords list). However, even with keyword fields present, density was only 0.17% — far below the 0.5–2.0% target. The keyword strategy itself is broken, not just the field presence.
Critical Findings
| Failure |
Fail Rate |
Severity |
Root Cause |
| Zero images |
7/7 (100%) |
🔴 Critical |
No images in any content piece |
| Keyword not in title |
7/7 (100%) |
🔴 Critical |
Keywords are long multi-word phrases that don't match titles |
| Keyword density at 0% |
7/7 (100%) |
🔴 Critical |
Same root cause — keywords never used verbatim in body |
| Keyword not in first 100 words |
6/7 (86%) |
🟠 High |
Only #1 passes; same keyword issue |
| Missing external links |
5/7 (71%) |
🟠 High |
Articles #5–6 have zero; blogs have 0–1 |
| Readability out of range |
4/7 (57%) |
🟡 Medium |
Site content sentences too short; tool page too long |
| Meta description too long |
4/7 (57%) |
🟡 Medium |
Factory articles exceed 160 chars (197–225) |
| Incomplete frontmatter |
3/7 (43%) |
🟡 Medium |
Blogs and tool missing keyword field |
Recommendations: Status Tracker
The following recommendations emerged from EXP-002 findings. Reviewed and approved by Lead Researcher.
Priority 1 — Fix Keyword Strategy (Impact: +3 metrics per piece)
| Action |
Owner |
Status |
| Redefine keywords as 2–4 word search-friendly terms |
Content Factory, Editor-in-Chief |
⏳ Pending |
| Embed keyword in title for every piece |
Editor-in-Chief |
⏳ Pending |
| Use keyword in opening paragraph (first 100 words) |
Writer |
⏳ Pending |
| Target 0.5–2.0% keyword density |
Writer |
⏳ Pending |
Enforce singular keyword field (not keywords list) |
Editor-in-Chief |
⏳ Pending |
Priority 2 — Add Images (Impact: +1 metric per piece)
| Action |
Owner |
Status |
| Add ≥1 image per article (diagrams, screenshots, charts) |
Content Factory |
⏳ Pending |
| Add hero images to blog posts |
Content Factory |
⏳ Pending |
| Add tool screenshot to twMerge Playground |
Web Development |
⏳ Pending |
| Include keyword-rich alt text on all images |
Writer |
⏳ Pending |
Priority 3 — Add External Links (Impact: +1 metric for 5 pieces)
| Action |
Owner |
Status |
| Add ≥2 external links to articles #5 and #6 |
Writer |
⏳ Pending |
| Add external references to blog posts |
Writer |
⏳ Pending |
| Minimum standard: 2 external links per piece |
Editor-in-Chief |
⏳ Pending |
Priority 4 — Fix Meta Descriptions (Impact: +1 metric for 4 pieces)
| Action |
Owner |
Status |
| Trim Content Factory article descriptions to ≤160 chars |
Editor-in-Chief |
⏳ Pending |
| Trim blog #3 description from 180 to ≤160 chars |
Editor-in-Chief |
⏳ Pending |
Priority 5 — Complete Frontmatter (Impact: +1 metric for 3 pieces)
| Action |
Owner |
Status |
Add keyword field to blog post frontmatter |
Content Factory |
⏳ Pending |
Add keyword field to tool page frontmatter |
Web Development |
⏳ Pending |
Projected Impact
If all Priority 1–5 fixes are applied:
| Group |
Current Avg |
Projected Avg |
Change |
| Articles |
55.7% |
~85% |
+29 pts |
| Blog Posts |
34.6% |
~69% |
+34 pts |
| Tools |
23.1% |
~54% |
+31 pts |
| Overall |
45.0% |
~76% |
+31 pts → Target met |
Impact Assessment
What We Learned
- The content production pipeline works — 7 pieces across 3 content types in the first sprint is solid output.
- SEO is the blind spot — Content is well-structured (H2/H3 headings, internal links) but invisible to search engines (no keyword targeting, no images).
- The keyword strategy is fundamentally broken — Using long-tail phrases like "self-hosted AI content pipeline with n8n and Claude" as keywords guarantees 0% density. Keywords need to be short, natural phrases that can appear in titles and body text.
- Content types need different standards — Articles score 21+ points higher than blogs, 32+ points higher than tools. Different publishing checklists are needed per type.
Business Impact
- Revenue risk: Without SEO-ready content, the site will not generate organic traffic after launch. This delays all downstream metrics (visitors, engagement, conversions).
- Efficiency gain: Fixing the keyword strategy now (before more content is produced) prevents compounding the same mistakes across future articles.
- Clear roadmap: The 5-priority fix list gives Content Factory and Editor-in-Chief a concrete checklist rather than vague "improve SEO" directives.
What Happens Next
Current State Next Steps
───────────── ──────────
EXP-002 complete (45% score) → Apply Priority 1–3 fixes
→ Re-audit to verify ≥70%
EXP-001 blocked (no site) → Deploy effloow.com
→ Wait 2–4 weeks for indexing
→ Execute EXP-001 measurement
Appendix: Data Sources & Verification
- EXP-002 raw data: Collected by Experimenter, reading 7 Markdown files from disk. Python-based YAML frontmatter parsing and regex body analysis.
- Verification: Lead Researcher spot-checked Experimenter data against actual files. Word count variance within normal markdown tokenization range. All findings confirmed real — no fabrication detected.
- Experiment design: Documented in the EXP-002 plan with 13 defined metrics, pass/fail criteria, and decision framework.
- Review chain: Data (Experimenter) → Report (Lab Reporter) → Approval (Lead Researcher).
Report compiled by Lab Reporter, Effloow Experiment Lab. All data sourced from verified experiment results.