One of our enterprise customers used JekCMS to publish 240 posts over twelve months. Organic traffic grew from 3,100 to 41,000 monthly visitors. The growth came from consistent publishing frequency, rigorous internal linking, and a content brief process that prioritised genuine usefulness over keyword density.
The company — a B2B software vendor selling to mid-market finance teams — started with two posts per week, each between 1,500 and 3,000 words on topics their target buyers actively searched for. Every article had a named author from their internal team; no content was AI-generated or bylined to a generic company name. Each piece went through a two-step review: a technical accuracy check by a subject-matter expert and an editorial pass for clarity and tone.
Internal Linking as a First-Class Strategy
Internal linking was treated as seriously as external link acquisition. Every new post linked to at least three existing posts on related topics. The team maintained a content map in a shared spreadsheet that tracked which articles covered which subtopics, making it easy for writers to identify linking opportunities without reading every published piece. By month eight, average internal links per post had grown from 1.2 to 4.7.
Content Briefs Over Keyword Targets
Content briefs were the most important structural element. Before any writing began, the brief specified the primary search query, estimated intent, three competing articles to analyse and surpass, and a list of claims that required data or concrete examples. Keyword density was not measured or targeted. The editorial guideline was simple: if a knowledgeable reader would not find this article useful, it did not get published.
The 23/78 Split: Power Law in Content
After twelve months, 23% of published posts accounted for 78% of organic traffic — a power-law distribution consistent with most content sites. The team used this finding to identify topics with untapped demand and commissioned follow-up articles targeting adjacent queries within those high-performing clusters. Monthly organic traffic continued growing at 15% month-over-month through the analysis period.
Technical Setup: How JekCMS Supported the Workflow
The team used JekCMS's scheduled publishing to batch content releases every Tuesday and Thursday at 09:00. The content queue feature allowed editors to load an entire week of posts on Monday and let the system handle timing. Each post went through three statuses: draft during writing, review during editorial passes, and scheduled once approved. This workflow eliminated the need for someone to be online at publish time.
n8n Automation for Content Briefs
The team connected their content brief spreadsheet to JekCMS via n8n. When a brief was marked "approved" in Google Sheets, an n8n workflow created a draft post in JekCMS with the title, target keyword, and assigned author pre-filled. This saved approximately 8 minutes per post in administrative overhead — across 240 posts, that is 32 hours of saved time.
Month-by-Month Growth Timeline
- Months 1-3: 24 posts published, traffic grew from 3,100 to 5,200 (+68%). Most gains came from long-tail queries with minimal competition.
- Months 4-6: 48 posts published, traffic reached 12,400. Three cornerstone articles began ranking on page one for competitive terms.
- Months 7-9: 72 posts published, traffic hit 24,800. Internal linking between related articles created topical authority signals that Google rewarded.
- Months 10-12: 96 posts published, traffic reached 41,000. The content flywheel was self-sustaining — new posts ranked faster because the domain had established authority.
Conversion Impact
Organic traffic was not the only metric that mattered. The team tracked demo requests sourced from blog content. In month one, the blog generated 4 demo requests. By month twelve, it generated 47 demo requests per month — a cost-per-lead of approximately $18, compared to $142 for paid search in the same industry vertical. The blog became the company's most cost-effective lead generation channel by month eight.
Lessons Learned and Mistakes Made
- Publishing frequency matters more than post length. Two 1,500-word posts per week outperformed one 4,000-word post per week in both traffic and lead generation.
- Author attribution builds trust. Posts with named authors and photos received 34% more time-on-page than posts attributed to the company name.
- Internal linking compounds over time. The traffic impact of internal links was not visible until month five, but by month ten it was the single largest ranking factor the team could control.
- Do not neglect updating old posts. The team started updating high-performing posts with new data in month nine. Updated posts saw an average 23% traffic increase within 30 days of the update.
- Content briefs prevent wasted effort. The three posts that performed worst all skipped the brief process. Every post that followed the full brief workflow reached at least 100 organic visits per month within 90 days.
Scaling the Operation: What Changed After Month Six
At the halfway point the team recognised that two posts per week was sustainable only because they had streamlined the editorial pipeline early on. They introduced a dedicated content coordinator whose sole responsibility was managing the flow from brief to publication.
This role eliminated the back-and-forth between writers and subject-matter experts that had previously added two to three days per article. The coordinator also maintained a living style guide that standardised formatting, header hierarchy, and image placement across all posts, which reduced the editorial pass from an average of 45 minutes to under 20 minutes per article.
By month nine the team began experimenting with content repurposing. High-performing blog posts were condensed into LinkedIn carousel posts and email newsletter features.
These secondary formats drove an additional 8% of traffic back to the original articles through referral links. The repurposing effort required roughly 30 minutes per piece and became a regular part of the weekly publishing cadence. The lesson was clear: a well-written blog post is not a single-use asset but a source that can feed multiple distribution channels over its lifetime.