⚡ Promptolis Original · Writing & Editing
📃 Blog Post Structure Architect
A full blog post blueprint — hook, headings, word counts, stats to find, and a SERP-calibrated meta description. No 'In today's digital world.'
Why this is epic
Kills the generic intro forever — gives you a specific, sharp hook tied to your actual topic, not a recycled 'In today's fast-paced world' opener.
Tells you exactly which 3 statistics to find before you write, with suggested sources. Most outlines skip this and you end up writing stats-free fluff.
Calibrates your meta description for SERP click-through rate by analyzing likely competing results and telling you which angle to lean into.
The prompt
Example: input → output
Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.
Topic: Why most async-first remote companies quietly reintroduce meetings after year 2 Target keyword: async communication fails Audience: Heads of Operations and founders at 30-150 person remote-first startups who drank the async kool-aid in 2021-2022 and are now privately frustrated Target word count: 1,400 words Optional — top 3 competing URLs: doist.com/blog/async-communication, gitlab.com/handbook/communication, a medium post titled 'The Async Revolution' Optional — brand voice notes: Direct, slightly contrarian, data-backed. We're a remote ops consultancy. We've seen 40+ companies try full-async. We're not anti-async, we're anti-dogma.
1. Angle Check
Strong topic, sharper angle available. 'Async communication fails' as a keyword has ~320 monthly searches and low difficulty — the existing results are almost all evangelism pieces from Doist, GitLab, and async-tool vendors who have a commercial reason to tell you it works. That's your opening. The topic is worth writing because the contrarian, operator-grounded version doesn't exist yet. Recommended angle refinement: don't frame it as 'async fails.' Frame it as 'async works, until it doesn't — here's the 18-month breaking point.' This keeps you credible (you're not anti-async) and gives you a specific, testable claim competitors can't match.
2. The Hook (first 50-80 words)
> Every async-first company we've worked with has followed the same arc. Months 1-18: async is a religion. Slack channels instead of standups. Loom instead of all-hands. Productivity, allegedly, soars. Then something shifts. A senior hire quits citing 'no connection to strategy.' A product launch slips because three teams had different assumptions nobody surfaced in writing. Quietly, the weekly sync returns. We've seen this pattern 40+ times. It's not a failure of async — it's a failure of the dogma around it.
Why it works: It opens with lived pattern-recognition (Experience signal), gives a specific timeline the reader can map to their own company, and defuses the 'you're just anti-remote' objection in the final sentence. The audience — ops leaders privately frustrated — will feel seen in sentence two.
3. Section Outline
| # | Heading | Purpose | Word count |
|---|---|---|---|
| 1 | The 18-Month Honeymoon Pattern | Frame the arc with data from our 40+ company dataset; establish credibility | 220 |
| 2 | What Actually Breaks First (It's Not What You Think) | Name the 3 failure modes: strategic drift, onboarding collapse, decision latency | 280 |
| 3 | Why Async Dogma Makes It Worse | Contrarian section — show how the *ideology* prevents fixes | 220 |
| 4 | The Meetings That Actually Survive the Async Filter | Concrete: which meetings pass the cost-benefit test (strategy, onboarding, conflict resolution) | 260 |
| 5 | A Diagnostic: Is Your Async Quietly Failing? | 7-question checklist the reader can run Monday morning | 200 |
| 6 | What the Next-Gen Hybrid Looks Like | Forward-looking — not a return to 2019, a calibrated model | 180 |
| 7 | The Bottom Line | 3-bullet takeaway | 80 |
Total: ~1,440 words. On target.
4. The 3 Statistics to Find
1. Claim it supports: Async-first companies see measurable decision latency after scale.
Data point: Average time-to-decision in fully async vs. hybrid teams. Look for: Atlassian State of Teams 2024, Microsoft Work Trend Index, or Slack's Workforce Lab.
2. Claim it supports: Strategic drift is real and measurable.
Data point: % of remote employees who report 'unclear company direction' — ideally segmented by async-heavy vs. meeting-heavy cultures. Try: GitLab Remote Report, Buffer State of Remote Work, or Gallup Q12 remote subset.
3. Claim it supports: Onboarding is where async breaks first.
Data point: Time-to-productivity for new hires in async-first vs. hybrid orgs, OR voluntary turnover rate in first 6 months. Try: BambooHR onboarding report, or Lattice People Strategy data.
If you can't find at least 2 of these with real sources, weaken the claims or cite your own consulting dataset explicitly (which actually strengthens the piece given the audience).
5. SERP Angle Analysis
Oversaturated: 'How to do async right' evangelism. Doist, GitLab, Twist, Trello — all have polished versions. You cannot out-evangelize them and shouldn't try.
Underserved: The honest post-mortem. There is near-zero content written by people who watched async-first companies hit the wall. The closest competitor is a handful of HN comments and a few Reverse Reddit threads.
Lean into: Operator authority + specific timeline (18 months) + the reframe that this isn't about async vs. meetings, it's about async vs. async dogma. This lets you cite competitors approvingly while still beating them.
6. Meta Description (150-160 chars)
> Async communication fails on a predictable 18-month timeline. We've watched 40+ remote companies hit the wall. Here's what breaks — and what to do about it.
Character count: 157.
Why this out-CTRs alternatives: Most SERP results for this keyword promise a framework. This one promises a pattern with a specific timeline and a number (40+) that signals real experience. The phrase 'hit the wall' creates mild curiosity tension. Avoid the temptation to add 'Learn more inside' — it flattens CTR.
7. Risks & Kill Criteria
- Risk: The piece drifts into anti-remote territory and alienates your own client base. Fix: In section 3, explicitly state your team is still 80% async after the recalibration.
- Risk: Without real stats, the 18-month claim reads as anecdote. Fix: If you can't find 2 of the 3 statistics, lead with your consulting dataset transparently ('across 40+ engagements between 2021-2024...').
- Do not: End with a tool recommendation. The audience will smell the pitch and bounce. Close with the diagnostic; let the consulting inquiry come inbound.
Key Takeaways
- Don't write the generic 'async fails' post — write the 18-month-timeline post. That's the keyword-adjacent angle nobody owns.
- Lead with pattern-recognition, not theory. Your 40+ company dataset is the moat.
- Target stat: decision latency, strategic drift, and onboarding time-to-productivity. If you can land 2 of 3, the piece has teeth.
- Meta description at 157 chars is optimal; specificity beats comprehensiveness for CTR.
- Kill criterion: if this reads as anti-async by draft 2, you've lost the frame. Re-anchor on dogma, not the method.
Common use cases
- Content marketers writing SEO-targeted blog posts for SaaS or B2B
- Solo creators who keep staring at a blinking cursor after 'Introduction:'
- Freelance writers scoping a piece before quoting a client
- Founders writing thought-leadership posts that need to actually rank
- Newsletter writers adapting a topic into a long-form version
- Agencies producing briefs for contract writers
- Anyone whose last 10 blog intros started with a rhetorical question
Best AI model for this
Claude Sonnet 4.5 or GPT-5. Both handle the strategic + structural reasoning well. Claude tends to produce sharper hooks; GPT-5 is slightly better at SERP angle analysis. Avoid smaller models — they default to generic outline templates.
Pro tips
- Feed it the URLs of the top 3 results for your keyword — the SERP angle analysis gets 10x sharper when it knows what it's competing against.
- Tell it your word count budget upfront. 'A 1,200-word post' produces tighter section estimates than leaving it open-ended.
- If the hook it generates feels too clever, ask for 'three alternative hooks at different emotional registers: data-shock, contrarian, and story.'
- Paste your brand voice notes into the audience field. It will calibrate heading tone accordingly.
- Use the 'stats to find' list as a research checklist before writing. If you can't find 2 of the 3 stats, reconsider the angle — the post probably isn't strong enough.
- Run the meta description through a pixel-width checker. Google truncates around 155-160 characters on desktop.
Customization tips
- If your topic is bottom-of-funnel (e.g., 'best X software'), add a line in the input: 'This is a BOFU commercial-intent piece' — the architect will shift the structure toward comparison tables and decision criteria instead of narrative hooks.
- For thought-leadership posts where SEO isn't the goal, leave the target keyword blank and write 'N/A — distribution is newsletter + LinkedIn.' The output will deprioritize SERP analysis and sharpen the contrarian angle.
- When the output feels too safe, reply with: 'Rewrite the hook and section 2 for a reader who has already read 10 posts on this topic and is slightly cynical.' This usually produces the version you actually wanted.
- Save the 'Angle Check' output even if you don't write the post. It's a useful kill-or-proceed signal that's worth the 45 seconds on its own.
- If you're writing a series, run this prompt for each post then ask: 'Given these 5 blueprints, what's the optimal publication order and what internal links should connect them?' — it turns the architect into a content calendar tool.
Variants
Listicle Mode
Restructures the output as a numbered list post (e.g., '9 X that Y') with heading patterns optimized for featured snippets.
Thought-Leadership Mode
Drops the SEO-heavy framing and produces a contrarian-opinion structure with a central thesis and counter-argument section.
Pillar Page Mode
Scales the output to a 3,000-5,000 word pillar structure with internal link anchor suggestions and 3-5 planned sub-posts.
Frequently asked questions
How do I use the Blog Post Structure Architect prompt?
Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.
Which AI model works best with Blog Post Structure Architect?
Claude Sonnet 4.5 or GPT-5. Both handle the strategic + structural reasoning well. Claude tends to produce sharper hooks; GPT-5 is slightly better at SERP angle analysis. Avoid smaller models — they default to generic outline templates.
Can I customize the Blog Post Structure Architect prompt for my use case?
Yes — every Promptolis Original is designed to be customized. Key levers: Feed it the URLs of the top 3 results for your keyword — the SERP angle analysis gets 10x sharper when it knows what it's competing against.; Tell it your word count budget upfront. 'A 1,200-word post' produces tighter section estimates than leaving it open-ended.
Explore more Originals
Hand-crafted 2026-grade prompts that actually change how you work.
← All Promptolis Originals