Toby — Blog & SEO Pipeline

TL;DR#

Run #2 of the Toby blog/SEO motion. One new draft this cycle: onetab-alternative.md — mid-funnel comparison reframing the OneTab → Toby move as "URL list → workspace," anchored by the December 2025 OneTab data-loss warning that's now public on OneTab's own troubleshooting page. Picked because (a) it was queued #1 from run #1, (b) SERP is listicles dominated by competitors not giants, (c) it pairs cleanly with the existing 2024-10-02-workonaAlternative.md post, (d) Toby is mentioned in some SERP results as the "visual organizer" but no one currently owns the calm, emotional reframe lane, and (e) the December 2025 OneTab data-loss-on-reinstall warning gives the post a credible, sourced "why now."

Migration applied this run: legacy toby/blog-*.md files moved into the new toby/blog/ sub-folder. The pipeline doc and the foundational "Why You Have 80 Tabs Open" draft are both now under toby/blog/. No content edits during relocation.

Next cycle target: Bookmarks vs Tab Manager (P4 evergreen) — the bio-line position deserves its own post.

Voice#

Three adjectives: calm, specific, generous. One don't: never breathless. No 🚀, no "supercharge", no "game-changing", no "delve into", no listicle-as-listicle. Voice fingerprint matches toby/x/strategy.md and product/strategy/soul.md.

Sample lines that ARE us (drawn from this run's drafts):

• "47 tabs is not a personality flaw. It's a research pattern."
• "Bookmarks ask you to retrieve. Toby asks you to recognize."
• "URL lists are a step up from bookmarks, but they still ask you to retrieve."
• "OneTab did something real for a long time, and a lot of people are here because it worked for years before it didn't."
• "Saving a tab should feel like setting it down, not filing paperwork."
• "We're not the right tool for everyone. If five tabs is your number, you don't need us."

Sample lines that AREN'T us (drawn from older landing-page blog posts; we are leaving this voice behind):

• "🚀 Tired of losing tabs in the abyss of your browser?" (actual @TobyForTabs tweet, 2024-01-09)
• "Toby Next is your game-changing to-do list for tab management."
• "Discover how Toby for Tabs can subtly integrate into your strategy for a smoother, more efficient workflow." (2024-07-04 post)

Content pillars#

Five pillars. Direct mirror of toby/x/strategy.md so blog and X tell the same story.

1. Tab anxiety, named (P1) — informational top-funnel pieces that articulate the feeling before pitching. Search intent: "why do I have so many tabs open", "tab hoarder", "browser overwhelm". Audience: heavy organisers, AuDHD-identifying knowledge workers, researchers, designers, devs.
2. The save-session ritual (P2) — informational/practical mid-funnel pieces about parking context. Search intent: "save Chrome tabs", "save browser session", "how to save tabs". Audience: knowledge workers searching for a method.
3. Power-user shortcuts & collections (P3) — bottom-funnel feature deep-dives. Search intent: branded ("Toby keyboard shortcuts", "Toby tags"). 🔒 rel-gated — wait until reliability hotfix ships before promoting feature workflows.
4. Better-than-bookmarks (P4) — comparison content. Search intent: "bookmarks vs tab manager", "alternative to bookmarks", "why bookmarks don't work". Audience: people who tried bookmarks and bounced.
5. Competitor alternatives (P5) — mid-funnel comparison. Search intent: "OneTab alternative", "Workona alternative", "Session Buddy alternative", "Arc browser alternative". Audience: switchers. Existing post on Workona; OneTab shipped this run; Session Buddy + Arc queued.

Posting cadence#

• One post every 2 weeks (1st and 15th of each month, 09:00 UTC). Cadence anchored by the run schedule of this agent.
• Pillar mix over an 8-post quarter: ~3 P1, ~2 P5, ~1 P2, ~1 P4, ~1 P3 (the P3 unblocks once reliability is fixed). Slot order is set in "Topic ideas in queue" below.

Posts in pipeline#

Slug	Title	Pillar	Intent	Funnel	Persona	Status	Wrote on
why-you-have-so-many-tabs-open	Why You Have 80 Tabs Open (And Why That's Actually Fine)	P1	informational	top	heavy-organiser / new-adopter	draft	2026-05-09
onetab-alternative	OneTab Alternative: Save Tabs as Workspaces, Not URL Lists	P5	comparison	mid	OneTab refugee (new-adopter / tenured-free overlap)	draft	2026-05-12

Topic ideas in queue#

Ranked by next-up. Each entry includes primary keyword, intent, and one-line winnable rationale.

1. Bookmarks vs Tab Manager (P4 evergreen) — primary kw "bookmarks vs tab manager", intent informational/comparison, mid funnel. Why winnable: SERP is niche productivity blogs (Rambox, TabMark, TabGroupVault, Nest, Haystack). The "Better Than Bookmarks" line is already in @TobyForTabs's bio — let's actually live the position with a post. Pairs back to the foundational tab-hoarder post and forward to the OneTab alternative.
2. How to save Chrome tabs without losing them (P2) — primary kw "how to save Chrome tabs", intent informational, top→mid funnel. Why winnable: high-volume how-to query; SERP is mostly Chrome help docs and listicles. We can rank with a calm step-by-step that doesn't lead with the product.
3. The "I'll deal with it tomorrow" tab problem (P1) — primary kw "tabs to read later", intent informational, top funnel. Why winnable: maps to the "in-between" category gap named in the X strategy (Post 11). Read-later apps (Pocket sunsetted, Instapaper sleepy) leave a soft hole.
4. Session Buddy alternative (P5) — primary kw "Session Buddy alternative", intent comparison, mid funnel. Why winnable: Session Buddy is still alive, but its UX is stuck in 2014. Solid switcher pool. Now safe to schedule — OneTab post just shipped, so we can space competitor-alt posts at one per cycle.
5. Arc browser users — where to put your tabs now (P5, time-sensitive) — primary kw "Arc browser alternative" / "Arc browser shutting down", intent comparison/transactional. Why winnable: Browser Company's Dia pivot is the news; many tab-hoarder Arc fans are stranded. Caveat: never punch down at Arc; our prospects include former-fans, not former-haters.
6. Public collection of the week (P5 / curator series) — recurring series, low SEO weight, high social weight. With permission, write up a top public Toby list with the curator's voice. Builds the Free-Tier Archivist persona's pride loop. Direct hook into playbook O3 KR3 ("4 public collections featured by 2026-06-30") — coordinate with toby-x-strategist.
7. "Chrome 133 vs. Toby" comparison page (P5) — primary kw "Chrome 133 saved tab groups", intent comparison, bottom-of-top funnel. Why winnable: this is in the state-of-project roadmap; the comparison page is a Should-bet in toby/strategy/playbook.md. Lean on axioms 1+2+3 (visual tangibility, ambient surface, persistence-is-product), NOT cloud sync.

Topic ideas explicitly NOT pursued (and why)#

• AI-organize / "let Toby name your collection" hype post. AI relaunch deferred to Q4 2026 per toby/00-state-of-the-project.md. Pre-announcing creates an expectation gap. Compass anti-promise.
• "Bookmarks are dead" hot take. Too on-the-nose. The bookmarks position belongs in calm one-liners, not in shouty form. The queued P4 post does this gracefully.
• Mother's Day / Valentine's Day / IWD content. Voice rules from toby/x/strategy.md apply: no holiday filler.
• "Toby Mini vs Full" comparison. Worth doing only after CWS reviews stabilise post-reliability fix.
• Direct shot at OneTab / Workona / Session Buddy. This run's OneTab post deliberately avoids punching down — describes OneTab's failure modes from public sources (its own troubleshooting page, Partizion's data-loss post, a community GitHub issue) and self-routes readers who'd be better served by Workona or others. Per playbook anti-bet #4: no public punch-down.
• Uncluttr / TabVault Pro / ThoughtFold / tab-out / leap-tabs comparison posts. Per toby/x/engagement-targets.md competitor-watch policy: cordial silence on new entrants. Comparison content stays focused on the established cohort.

Keyword landscape (snapshot — 2026-05-12)#

Keyword	SERP gist (top results)	Toby angle
why do I have so many tabs open	Mental Floss, Fast Company, MaxFocus, Hacking Your ADHD, Workona, Quora, Carnegie Mellon — ~850–2,400 word psych/productivity essays. No tab-manager has this with a calm POV.	"Tabs are working memory; the medium is the problem." Shipped 2026-05-09.
OneTab alternative	TabGroupVault (~2,800 words, mentions Toby), Workona (~1,200, Toby absent), Blackmount (~3,200, AI angle, Toby absent), TheTab (~2,200, mentions Toby), Partizion (~1,200, data-loss angle). Listicles + product-led comparisons dominate. OneTab itself is dormant.	"URL list → workspace" reframe; honest about who we're NOT for. Shipped 2026-05-12.
bookmarks vs tab manager	Rambox, TabMark, TabGroupVault, Nest, Haystack, AlternativeTo, Dewey. Mostly listicles.	"Bookmarks are a folder you never open." Queued #1.
too many tabs open / tab hoarder	Same SERP as the foundational kw plus a Pearlmania500 podcast and a CWS extension named TooManyTabs.	Adjacent to the foundational post; will share traffic. Don't write a second post on the same SERP.
how to save Chrome tabs	Workona, Shift, Partizion, makeuseof, Medium, CMU. Lots of how-to + product mentions.	Calm method post. Queued #2.
Session Buddy alternative	TheTab, TabGroupVault, listicles. Session Buddy is alive but stagnant.	"Same trust, modern visual layer." Queued #4.
Chrome 133 saved tab groups	Google help docs + recent Verge / The Pixel News coverage.	Chrome 133 as table-stakes; Toby axioms 1/2/3 as the wedge. Queued #7.

Competitor blogs we watch#

Domain	What they ship	Why it matters
getworkona.com/blog	Heavy how-to + workspace-as-CRM angle. Active.	Direct competitor on every "too many tabs" query; their "How to Fix The Problem of Too Many Tabs" is the post we differentiate from. Toby not mentioned in their OneTab roundup.
partizion.io/blog	Long-form productivity guides; aggressive SEO.	The "OneTab lost all my tabs" post is a primary citation source for our 2026-05-12 OneTab draft. Adversary but worth a respectful read.
tabgroupvault.com/blog	Listicle-heavy comparison content.	Owns "best OneTab alternative" SERP slot with a ~2,800-word post. Mentions Toby as "visual organizers" — they self-route exactly the persona we want.
thetabextension.com/blog	Active product-led blog; 2,200-word OneTab-vs-TheTab post mentions Toby at "$9/mo" — pricing claim worth tracking for accuracy.	New SERP entrant. Worth occasional check-in.
blackmount.ai/articles	AI-organize lane; long-form (~3,200 words). Toby not mentioned.	Demonstrates the AI-first lane we've deliberately deferred to Q4 2026.
maxfoc.us/blog	Single-author productivity content with light brand.	"Psychology of tab hoarding" is on the foundational SERP. We reject their "set a tab limit" advice.
getlazy.dev/blog	Knowledge-worker / second-brain adjacent.	Distant relative — useful for adjacency content.
tabby.so/blog	Newer, niche.	Watch for new SEO entrants.
raindrop.io/blog	Bookmark-manager-with-a-design-team.	The "calm" axis we're aiming for is closest to their voice; useful reference.
arc.net / diabrowser.com	Browser-as-product. Arc is winding into Dia.	Cultural moment to engage carefully — see queued post #5.
sigmaos.com	Slowed sharply; X dormant since 2024-11.	Watching only; not actively engaged.
onetab.com	Originator of the category, functionally dormant. Now the subject of a published draft.	Their /troubleshooting page is the primary source for our 2026-05-12 draft's "data loss" claim — worth a periodic re-check in case copy changes.

Operator decisions still open#

• Where do drafts get published? The pipeline writes to the wiki; production blog lives at apps/landing/src/content/post/*.md. Drafts get hand-copied across editing? Or change the publish flow? Block on first publish.
• Internal-link URL shape. Astro routing on gettoby.com may not match filename slugs (e.g. 2024-10-02-workonaAlternative.md → /blog/workonaAlternative or /blog/workona-alternative?). Confirm canonical paths before publishing either draft.
• Image hand-off. Cover + in-post images per existing ~/assets/images/blog/<post-folder>/<image>.png pattern. Neither draft has images yet. Operator owns this (or hand off to design). The OneTab draft specifically needs a side-by-side "URL list vs visual collection" hero — the image carries the post's core claim.
• Pricing claim guardrail. Both current drafts deliberately do not mention dollar figures (per toby/00-state-of-the-project.md $4.50 vs $6/$10 contradiction; playbook O3 KR1 due 2026-05-13). The OneTab draft says "free for solo use" + "paid plans exist" — safe regardless of reconcile.
• Reliability gate. Both drafts mention Save Session and the new tab page as core features. Both are exposed to the blank-page hang documented in toby/incidents/2026-05-11-blank-extension-page.md. Recommendation: hold publish of the OneTab draft until the 3-layer hotfix ships (O1 KR1, due 2026-05-24) so we don't drive switchers into the bug. The foundational post (Why 80 Tabs Open) is less feature-promotional and can publish earlier.
• Distribution loop. Each blog post should pair with one X post that links it. The foundational post's natural counterpart is Post 1 from toby/x/content-pipeline.md ("47 tabs is not a personality flaw"). The OneTab draft needs its own dedicated X anchor — recommend operator queues that next.
• Pricing claim in TheTab's comparison post. TheTab's blog claims Toby is "$9/mo." That's not consistent with either $4.50/mo internal or $6/$10 public-listing numbers. Either we have an outdated price somewhere we don't see, or TheTab is wrong. Worth flagging to operator alongside the pricing reconcile.
• socialdata listening cadence. From last run's pending_review: do we always pull fresh X tweets or rely on toby/x/strategy.md? This run again skipped socialdata calls because the OneTab story was fully sourced from public web pages (OneTab's own troubleshooting page + competitor blog posts) and adding X tweets wouldn't have changed the angle. Recommendation: only call socialdata when a topic is genuinely conversation-driven (e.g. live competitor moves, viral incidents). Codify this in the agent orders next iteration.

Open questions#

• Reliability gate logic. Should comparison + feature-promotional posts (P3, P5) wait on the reliability hotfix as a class? Current decision case-by-case. May want a hard rule.
• AI-feature mentions. Q4 2026 AI relaunch is internal. Drafts must not pre-announce it. Both current drafts comply; the OneTab draft explicitly says "AI auto-organize is on the roadmap, not in your hands today" — that line either needs softening or removal depending on how the operator wants to handle the pre-announce guardrail.
• Should we add a Post 13-style 🔒 acct-only series for blog? X uses "🔒 acct-only" to mark drafts that can't ship until @TobyForTabs creds exist. For blog the analog might be "🔒 rel-gated" or "🔒 pricing-gated" — already in use informally in this doc; might be worth a separate column in the Posts table.