The n8n authority engine

The problem

Most automation content asserts expertise. The goal was for the site itself to be the evidence, built on the same systems it teaches rather than on a page describing them.

The n8n plus Claude Code and MCP intersection is barely written about, which is an opening only if publishing is cheap enough to sustain.

What we built

1. 01

   Publishing as a pipeline, not a task

   Posts are date-gated in the repo and a scheduled build publishes whatever has come due, so the queue empties itself. No human flips a flag on publication day.

2. 02

   Structured data as a first-class output

   Every page composes a JSON-LD @graph with entity IDs linking author, publisher and organisation, emitted into static HTML rather than assembled in the browser where crawlers may never see it.

3. 03

   Invariants enforced at build time

   The build runs SEO invariant checks across every route and fails rather than shipping a regression, which is how a site this size stays correct without manual auditing.

4. 04

   Built for AI answers, not only blue links

   Content is structured to be quotable and attributable, because the engines that matter increasingly summarise rather than list.

What changed

• ✓The site now builds 140 routes, with invariant checks passing across all of them on every deploy.
• ✓It is one of very few sites covering the n8n plus Claude Code and MCP integration specifically, which is why it ranks for it.