Managing 255 Articles Solo: A Content Operations System with Feishu Multidimensional Tables

Every content site owner goes through a phase: you go from 10 articles to 50 to 100, and suddenly you realize — more articles mean more chaos. Which ones have been written? Which haven't? Where is each keyword ranking? Which articles need updating? Your brain can't track all of this, and Excel won't cut it for long either.

I learned this the hard way. By 50 articles, things were already messy. By 80, it was complete chaos — I had written 3 articles targeting the same keyword without realizing it. Then I built a content operations system using Feishu's multidimensional tables. It ended up supporting the ongoing production and maintenance of 255 articles.

A systematic content operations approach isn't just for big companies. Solo entrepreneurs need it even more because our margin for error is thinner.

Why Content Operations Management Is Non-Negotiable

Many people think "you just write, what's there to manage?" This works at 10 articles. At 50, it starts hurting. At 100, it's a disaster. Without systematic management, you'll experience symptoms: writing duplicate content without knowing; keywords dropping from top positions unnoticed; articles needing updates you completely forget.

More importantly, without data-driven management, you can't tell which strategies work. Operating on gut feeling is inefficient. Solo companies need every strategy to be effective — that's what a system provides.

Content operations management boils down to three capabilities: see the full picture (how many articles, what status?); trace history (ranking changes over time); drive decisions (which content types perform best?).

Step 1: Article Lifecycle Management

My core approach: treat every article as a "product" rather than a one-time piece of writing. I set 5 statuses: To Plan, Writing, Published, Optimizing, Archived.

Using the kanban view, each status is a column. Drag and drop moves articles between statuses. When a Published article's ranking drops, drag it to Optimizing. Once optimized, drag it back. No config files needed.

Every Monday, I sort by status and instantly see my week's focus: how many To Plan (new topics needed), Writing (in progress), Optimizing (ranking recovery needed). Fifteen seconds to plan the week.

Combined with a 3-month review cycle after each publication, this ensures 200+ articles don't collectively lose rankings due to stale content.

Step 2: Keyword and Content Association

Every article links to a target keyword and long-tail variations. The key is many-to-many: one keyword maps to multiple articles.

Example: "what fabric for sports suits" can link to both a fabric buying guide and a cotton vs. polyester comparison. This covers different search intents — fabric education vs. direct comparison. When one article's ranking drops, quickly find related articles for internal links or supplemental content.

Implementation: create two tables in Feishu — Articles and Keywords — link them with a relation column. Before writing any new article, check the association table to complement rather than duplicate.

Step 3: Ranking Tracking and Data-Driven Decisions

I added a "Ranking Data" column. Weekly export from Google Search Console, manual entry. Track movements like "position 9 last week, position 5 this week."

Over time, this becomes an "operations playbook" answering: which article types hit page one most easily? Which hold rankings longer? Which low-volume keywords convert best? Which topics need updates?

I also tag each article with a content type: Buying Guide, Product Comparison, Scenario Recommendation, Fabric Education — about 7-8 types. After two months, data showed Buying Guides and Product Comparisons averaged 2-3x the UV of Scenario Recommendations. This directly shifted content strategy — reduce underperforming types, double down on winners.

Step 4: Internal Link Management

Internal linking is the highest-ROI yet most ignored SEO strategy. I added a "Related Articles" field in the table recording which internal pages each article links to.

Standard process before writing: check the table for existing related content, ensure every new article links to at least 2-3 existing high-value articles. Improves user dwell time and helps Google crawlers understand site structure. Five minutes per article, continuous SEO returns.

Step 5: Build Your System in Five Steps

Step 1: Create a Feishu multidimensional table. Start with basic fields: article title, status, target keyword, publication date. Don't overcomplicate.

Step 2: Set up status field. Create 5 options: To Plan, Writing, Published, Optimizing, Archived. Switch to kanban view.

Step 3: Create keyword association table. Link to articles table with relation column for many-to-many mapping.

Step 4: Add content type tags and ranking data columns.

Step 5: Build weekly update habit. 15 minutes every Monday — enter new ranking data, adjust statuses, plan topics.

Real Case: Managing 255 Articles

Daily flow: open Feishu table → check Writing column for articles in progress → select a new topic from To Plan → check keyword association table for uniqueness → write → change status to Published → sync to GitHub.

Monthly audit: review all Published articles beyond 3 months without updates, drag to Optimizing. Analyze ranking data for declining keywords.

This simple flow supported continuous production and maintenance of 255 articles. Without the system, something would have slipped — duplicate topics, missed updates, or unnoticed ranking drops.

FAQ

Q: Why not Notion or Airtable? A: In a Chinese context, Feishu has better network stability, easier sharing, and a more generous free tier. Notion is slow in China. Airtable's free row limit is hit quickly with content sites.

Q: Do I need this with few articles? A: Set it up before reaching 20 articles. Building the habit early is much easier than scrambling at 100.

Q: Does this replace a CMS? A: No. It sits above the CMS as an operations management layer. CMS handles display; Feishu handles planning, production, and optimization.

Q: Do I need a team? A: Not at all. This is designed for solo operations. If you hire later, sharing the table is faster than teaching a CMS.

Summary

Content operations management isn't a nice-to-have — it's essential for content site survival. Feishu's multidimensional tables give you: full visibility at a glance, a foundation for continuous optimization, and data to drive decisions. Spend one afternoon building it, and it pays off throughout your entire content journey. A solo company's greatest advantage is flexibility, and its biggest challenge is scattered energy. A systematic management tool helps you focus your limited energy where it matters most. One important caveat: don't manage for management's sake. The goal is to write better content more efficiently, not to spend hours maintaining a table. Keep it lean — 15 minutes per week is enough.