Blog Builder
Workflow
Analytics
Integrations
System
Matchnode Intelligence
Persistent knowledge base that informs every article. Set it once, use it everywhere.
This URL is injected into every generation command.
Reader Personas
Who reads Matchnode articles. Used to calibrate tone, examples, and depth.
0 personas
Competitive Landscape
Context for positioning Matchnode's differentiation in content.
0 competitors
Case Studies
Client results used as proof points in articles. Anonymize as needed.
0 case studies
CTAs & Links
Approved calls to action and partner links used across all content.
0 CTAs
Article Visual Components
Choose one visual per article. Pick the format that makes the content easiest to understand.
0 components
Image Guidance
Rules for suggesting inline images. Images should improve readability, pacing, or comprehension — never decorative.
0 rules
Trusted Sources
Approved external references and data sources for factual claims.
0 sources
Business Decisions
Editorial rules and strategic decisions that govern all content production.
0 decisions
Learning Notes
Ongoing editorial learnings from published articles and experiments.
0 notes
Article Package Viewer
Load a generated article package (HTML file from your Claude chat) to view all sections, copy into WordPress, and track publish status.
Workflow: Generate in Claude chat  →  Download HTML package  →  Drop it here  →  Copy sections into WordPress  →  Mark status below
Drop your Article Package here
Or click to select the .html file generated in your Claude chat session. Works with any matchnode_article_package_*.html file.
Load Package
Planning Workspace
Plan every article before you write it. Strategy comes before generation.
How this works
1. Select a pillar + cluster  →  2. Complete Article Strategy (persona, decision, RSO, framework, gate)  →  3. Complete Planning Brief (Why Now, confirm strategic context)  →  4. Copy the generation command  →  5. Paste into your Claude chat  →  6. Open result in Package Viewer
Total articles
12
across all pillars
Published
10
live on site
In draft
2
ready to publish
Pillars covered
5
of 5 Matchnode pillars
—Clicks
—Impressions
—Avg Position
—Articles with Data
GSC data available ·
Have a topic in mind?
Describe it, add source URLs, or upload reference docs. Claude will map it to the best pillar and cluster.
Describe what you want to write about. Be as specific or vague as you like.
Competitor articles, research, industry data — Claude will reference these when mapping and generating.
PDF, DOCX, TXT — Claude reads these for context, terminology, and angles to cover.
Click to upload or drag files here — PDF · DOCX · TXT (up to 5)
Analyzing topic and mapping to pillar…
Suggested mapping
1Choose this week's pillar
One pillar per week. Published clusters are tracked automatically.
Cluster Differentiation Check
Complete your Planning Brief and click Check to verify this article is differentiated from existing cluster content.
Article Log
Every article produced by this workflow. Update status as articles are published.
All Draft Review Published
Article & Planning Brief Pillar Status Publish date Quality Schema Actions
Visibility Intelligence
Three-layer editorial analysis — Search Performance · Technical Health · Matchnode Editorial Intelligence
Search Performance
Source: Google Search Console · No data imported yet
Import a Google Search Console Pages report (CSV or TSV) to see real clicks, impressions, CTR, and position data.
Technical Health
Schema · Rich Results · Index Status · Factual only — Unknown or Pending if not yet verified
Article Schema Rich Results Canonical Last Verified
Matchnode Intelligence
Auto-generated · SEO Health · AEO Pulse · GEO Signal · Matchnode Quality · Growth Plan

The Builder automatically evaluates every article using Matchnode Intelligence, GSC performance data, and Matchnode's editorial doctrine. Evaluations run in the background — no action required. Scores refresh whenever Search Console data is imported.

Publishing Calendar
Plan your weekly Tue/Thu cadence. Click any day to assign articles and add notes.
Mon
Tue
Wed
Thu
Fri
Sat
Sun
Click a day to plan it
Publish day (Tue/Thu)
Published
Improving
Planned
Today
Content Quality Scores
Relevance, timeliness, readability, and SEO strength per article.
Select an article to review or update scores
Strategy Map
Visual overview of all 5 pillars and 27 clusters. Published clusters turn green automatically.
5
27
0
0
0
0%
Suggested / Idea In Progress Published
Article Editor
Select an article to view and edit all fields, scores, body content, and metadata.
Planning Brief — permanent strategic record
Saved with the article — remains stable after publication. —
Core fields
SEO fields
0 / 155
Quality scores
Verification
Notes
Article body — Gutenberg block markup

Paste updated body content from Claude here, or edit directly. This is the content that goes into the WordPress post content field.

Team Sync
Share your Intelligence library and GSC data across all browsers and team members.
Temporary workflow. This uses file export/import via your shared Google Drive folder — no credentials stored, no server required. Supabase automatic sync will replace this once Chris and Marina approve the setup.
How team sync works
1
Whoever sets up the data clicks Export below to download a file.
2
Drop the file into your shared Matchnode Google Drive folder (create one called "Blog Builder Sync" if it doesn't exist).
3
Any team member on any browser opens this panel, clicks Import, and selects the file from Drive. Done.
4
When anything changes (new framework added, GSC updated), repeat steps 1–3. Each file is dated so you always know which is newest.
Intelligence Library
Company profile, personas, frameworks, business decisions, learning notes
Loading status…
Export filename: matchnode-intelligence-YYYY-MM-DD.json
GSC Search Performance
Imported Google Search Console data — clicks, impressions, CTR, positions
Loading status…
Export filename: matchnode-gsc-YYYY-MM-DD.json  ·  Original GSC CSV report format is not supported here — use the Builder's Visibility panel to import CSVs.
Settings
Configure the Blog Builder workflow and integration status.
Taxonomy Status
Matchnode Taxonomy v1.0 · The operational backbone of the Builder

Navigate to Settings to see Taxonomy Status.

Workflow preferences
Include excerpt in every package
Auto-adds excerpt to the article command
Include image prompt in every package
Generates featured image AI prompt per article
Auto-log after generating
Automatically adds article to log as Draft
Tuesday + Thursday publish schedule
Follows 2026 peak engagement day data
WordPress Push
Drafts only. Production credentials live in Render env vars — not in this file, git, or the team’s browsers.
Checking proxy…

Production: the Builder still lives on WordPress at matchnode.com/tools/blog-builder. It calls a new Render Web Service named matchnode-blog-builder in the existing Render project Matchnode dashboard (alongside the superapp matchnode-full-dashboard) — not a new Render project and not a GitHub repo move. The proxy (/api/wp) attaches WP_USERNAME and WP_APPLICATION_PASSWORD. Username on the WP side is cmadden (Application Password name: blog builder). Never auto-publishes.

Local-dev override — not production

Only for opening this HTML on your machine. The rest of the team will not have this. Production must use Render env vars.

Integrations
Still locked — GSC OAuth, Rank Math, in-app generation
Google Search Console

OAuth in existing GCP project matchnode-full-dashboard. Client ID only — never the secret in this HTML file. CSV import stays as fallback.

Rank Math API

Auto-sync focus keywords and SEO scores. Needs Rank Math PRO + REST API token.

Anthropic API (in-app generation)

In-app article generation. Needs Anthropic API key approval before activation.