> A content growth scorecard turns a large blog archive into a weekly operating system. Instead of asking what to write next, AIKit teams can score every article by search intent, funnel fit, conversion path, and refresh urgency, then ship the ten highest-leverage improvements first.
The Problem
Most content teams eventually hit the same wall: the archive gets big enough that new posts are no longer the only growth lever. A site with hundreds of articles has hidden opportunities in older tutorials, launch posts, comparison pages, and product notes. Some rank on page two and need a stronger answer-first opening. Some attract qualified readers but have no lead magnet. Some explain a feature well but never send the reader to a demo, pricing page, checklist, or email capture. Without a scoring system, the team keeps publishing at random while the highest-value pages decay.
The AIKit answer is to treat the archive like a product backlog. Every URL gets a score. Every score maps to a clear action. The goal is not generic SEO maintenance; it is a repeatable growth loop that connects discoverability, helpful content, and measurable funnel movement.
The Scorecard Model
Use five dimensions, each scored from 0 to 5. The final priority score is a weighted sum, not a vague editorial opinion. A post with moderate traffic and a perfect product fit can beat a high-traffic informational page because it is closer to revenue.
| Dimension | Weight | What to Check | Example Win |
|---|---:|---|---|
| Search intent match | 25% | Does the post answer the exact query in the first 150 words? | Rewrite the opening with a direct answer |
| Product fit | 25% | Does the topic naturally connect to AIKit, EmDash, automation, or launch workflows? | Add a product walkthrough block |
| Funnel path | 20% | Is there a relevant CTA or lead magnet? | Add checklist download or demo CTA |
| Freshness risk | 15% | Are screenshots, APIs, pricing, or examples stale? | Update commands and dates |
| Internal link leverage | 15% | Can this page link to three stronger assets? | Add related tutorials and hub links |
The scorecard should produce a ranked list of actions. A good weekly target is ten archive improvements: three openings, two CTAs, two internal-link updates, two technical refreshes, and one deeper rewrite. That mix keeps velocity high while still creating meaningful compounding gains.
Step 1: Export the Archive
Start by exporting the core fields needed for scoring: slug, title, excerpt, published date, category, and body preview. If the site uses EmDash with D1, the query can be simple.
```bash
cd ~/Projects/AIKitLLC/EmDash
npx wrangler d1 execute ai-kit-net --remote --json --command "SELECT slug, title, excerpt, category, published_at FROM ec_posts WHERE status='published' ORDER BY published_at DESC" > archive.json
```
For a first pass, do not wait for perfect analytics integration. The archive metadata alone is enough to identify obvious gaps: thin excerpts, titles without buyer intent, categories with no CTA, and old posts that mention outdated feature names. Add traffic and conversion data later when the weekly loop is already running.
Step 2: Compute a Practical Score
A lightweight script can turn editorial judgment into a repeatable operating system. The exact heuristics will evolve, but the important part is consistency.
```python
import json, re
BUYER_TERMS = ["checklist", "template", "demo", "pricing", "automation", "workflow", "launch"]
PRODUCT_TERMS = ["aikit", "emdash", "ai agent", "content", "funnel", "seo"]
def score_post(post):
text = (post["title"] + " " + (post.get("excerpt") or "")).lower()
intent = min(5, sum(term in text for term in BUYER_TERMS) * 2)
product = min(5, sum(term in text for term in PRODUCT_TERMS))
funnel = 1 if "demo" not in text and "checklist" not in text else 4
freshness = 4 if re.search(r"2024|2025|old|legacy", text) else 2
links = 3
return round(intent*.25 + product*.25 + funnel*.20 + freshness*.15 + links*.15, 2)
data = json.load(open("archive.json"))[0]["results"]
ranked = sorted([(score_post(p), p["slug"], p["title"]) for p in data], reverse=True)
for score, slug, title in ranked[:10]:
print(score, slug, title)
```
This first version intentionally favors posts that are close to the funnel. A launch checklist, marketing automation tutorial, or SEO workflow page should usually outrank a broad thought-leadership article because the next action is clearer.
Step 3: Map Scores to Actions
The score is only useful if it creates work orders. Each high-priority URL should get exactly one primary action for the week. Avoid turning the scorecard into a research artifact. If a post has no answer-first opening, rewrite the opening. If it has no conversion path, add one CTA. If it ranks for a process keyword, add a numbered tutorial block.
Use this action map:
- Score above 4.0: full refresh with new opening, CTA, internal links, and examples.
- Score 3.0 to 4.0: targeted funnel upgrade, usually a checklist, demo CTA, or product walkthrough.
- Score 2.0 to 3.0: internal-link and excerpt improvement.
- Score below 2.0: leave alone unless analytics show traffic.
The operating rhythm matters more than the math. Ten small improvements every week will outperform one quarterly audit that never becomes production content.
Step 4: Add AI-Ready Blocks
Because AI agents read pages differently from humans, each refreshed post should include structured blocks that are easy to extract. Add a short answer at the top, a problem-solution section, a numbered implementation guide, and a compact takeaway list. These sections also improve llms.txt usefulness because summaries and excerpts become more direct.
A practical refresh block can look like this:
```markdown
Quick Implementation Checklist
1. Identify the target reader and funnel stage.
2. Rewrite the first paragraph with the direct answer.
3. Add one product-relevant example.
4. Add a CTA that matches intent.
5. Link to three related tutorials or case studies.
```
This is not padding. It makes the page easier for readers, search engines, and AI crawlers to understand. It also gives the marketing team a reusable template for future updates.
Results to Track
Measure the scorecard like a funnel, not like a writing calendar. Track updated URLs, changed titles or excerpts, CTA additions, internal links added, and downstream events such as newsletter signups or demo clicks. For SEO, watch impressions and average position over a four-week window. For funnel quality, watch click-through rate from content to the next step.
A realistic weekly target for AIKit is simple: improve ten archive pages, add at least twenty internal links, ship five stronger CTAs, and refresh three outdated technical examples. If even two pages move from passive traffic to qualified lead capture, the archive becomes a compounding asset instead of a storage folder.
Key Takeaways
- A blog archive should be managed like a backlog, with scores, actions, and weekly shipping cadence.
- The best opportunities combine search intent, product fit, and a missing funnel path.
- AI-ready structure helps both human readers and automated discovery through llms.txt-style surfaces.
- Ten focused archive improvements per week can create more growth than ten brand-new unfocused posts.