Section 3 · Content / Markdown
Migrating from WordPress to GitHub CMS — Save /Year and Get TTFB 3x Faster
Markdown export, SEO preservation, 301 redirects. Real case study: 57 pages in 8 weeks, saving -1100/year, AI citation rate +40%.
Three Reasons to Migrate from WordPress
Cost, performance, and security
Save -1100/Year
WordPress: -600/year hosting + -400/year SEO plugins + -199/year security. GitHub CMS: -100/year VPS. Everything else is built-in.
TTFB ≤200ms — 3x Faster
WordPress: 600-1200ms. GitHub CMS: static HTML without PHP and MySQL. +40% AI citation rate due to speed.
No Updates, No Vulnerabilities
WordPress: monthly core updates + plugin conflicts. 90% of hacks via plugins. GitHub CMS: static HTML. No admin panel. No login page.
Migration in Numbers: 57-Page Case Study
Real data from a B2B platform project
Pages
migrated
Savings/Year
hosting + plugins
TTFB After
was 800ms
AI Citation
with JSON-LD
Before and After: WordPress vs GitHub CMS
What changes after migrating to a static site
WordPress
TTFB 800ms — too slow for AI
PHP-FPM + MySQL + plugins. AI crawlers leave for competitors. Up to 50% AI traffic loss.
-1100/Year Expenses
Hosting -600 + SEO plugins -400 + security -199. Every year.
Updates and Vulnerabilities
Monthly core and plugin updates. Risk of conflicts. 90% of hacks via plugins.
JSON-LD via Plugins
Yoast + Schema Pro. Conflicts on updates. Manual configuration for each page.
GitHub CMS
TTFB 180ms — 4.4x faster
Static HTML via nginx. No PHP, no MySQL. AI crawlers get the page instantly. +40% AI traffic.
-100/Year — 1 VPS
1 VPS with nginx. SEO, JSON-LD, sitemap — built into CMS. No extra plugins. Savings -1100/year.
No Updates — No Vulnerabilities
Static HTML: no admin panel, no PHP execution. CSP + HSTS in nginx. Security at the web server level.
JSON-LD Auto from YAML
15 Frontmatter fields → 10+ JSON-LD types. No plugins. No subscriptions. Everything generated at build time.
57 Pages in 8 Weeks — Real Migration Case Study
A B2B platform migrated 57 pages from WordPress to GitHub CMS. Saving /year, TTFB from 800ms to 180ms, AI citation +40%.
Migration Plan: What to Preserve and How
Two key components + three transfer rules
Markdown Export
WordPress → XML export → conversion to .md via scripts. Cleaning Gutenberg junk tags. Adding YAML Frontmatter with metadata (title, slug, date, author). 57 pages — 2 weeks.
SEO Preservation
Transfer meta tags to YAML Frontmatter. 301 redirects from old URLs to new ones. Preserve URL structure (slugs). Sitemap and robots.txt are generated automatically. Rankings are preserved.
Rule 1: Preserve Slugs
/blog/old-url → /blog/old-url. No URL changes. 301 only for structural changes.
Rule 2: Transfer Meta Tags
WordPress meta → YAML title + description. Duplicate exactly. No rewording.
Rule 3: Monitor Rankings
Google Search Console after migration. 4-week monitoring. Sitemap update.
Migration Plan: 8 Weeks — From Audit to Production
A phased plan to transfer 57 pages without losing SEO rankings. In parallel: content is migrated, the old site keeps running, switchover is instant.
Audit + Export
Cleanup + Frontmatter
301 + SEO Check
Deploy + Monitoring
Testimonials: Real Migration Case Studies
Results from companies that migrated from WordPress
"57 pages in 8 weeks. Export to .md, cleaning Gutenberg junk, 301 redirects. SEO didn't drop — rankings were preserved. TTFB from 800ms to 180ms. Saving /year."
Alexey K.
CEO B2B Platform
"180 pages in 12 weeks. YAML Frontmatter preserved all SEO metadata. JSON-LD out of the box — AI started citing after 4 weeks. +40% AI traffic."
Marina S.
Tech Director EdTech
"35 pages in 5 weeks. Migration scripts cleaned 90% of junk. 301 redirects via nginx map. Rankings zero loss for 4 weeks. TTFB 200ms stable."
Dmitry V.
DevOps Engineer
How to Migrate: 3 Steps
From export to new site on GitHub CMS
Export and Cleanup
WordPress → XML → .md. Clean Gutenberg junk tags. 57 pages — 2 weeks.
Add Frontmatter and 301s
YAML with title, slug, date, author. 301 redirects from old URLs. SEO preservation.
Deploy and Monitor
npm run build → rsync to VPS. Switch DNS. Google Search Console. 4-week monitoring.
4 Migration Risks and How to Avoid Them
What can go wrong and how to prepare
1 · SEO Ranking Loss
Risk: URL change or meta tag loss. Solution: preserve slugs, set up 301 redirects, transfer title/description to YAML Frontmatter. Update sitemap in Search Console. Monitor rankings for 4 weeks after migration.
2 · Content with Junk Tags
Risk: WordPress export contains nested span/div, block comments. Solution: cleanup scripts (sanitize-html), manual review, conversion to Markdown. 90% of migration time is cleanup.
3 · Image Loss
Risk: WordPress stores images in /wp-content/uploads/. Solution: move images to public/images/, update links in .md. Or leave on old hosting with a redirect. Or use a CDN.
4 · Broken Internal Links
Risk: links between pages break after changing URLs. Solution: check all internal links before switching. Use relative paths /blog/page/. Test with a crawler.
Guarantee: SEO is Preserved, Traffic Doesn't Drop
301 Redirects · Slug Preservation · YAML Frontmatter
With proper migration, SEO rankings are not lost. 301 redirects transfer link equity. Slugs are preserved. Meta tags are transferred to YAML. Sitemap is updated. Case study of 57 pages: 0 ranking losses over 4 weeks of monitoring.
FAQ on WordPress Migration
Common questions about migrating to GitHub CMS
How long does migrating 50-100 pages take?
57 pages: 8 weeks (2 for export and cleanup, 2 for Frontmatter and structure, 2 for 301 redirects and SEO check, 2 for deploy and monitoring). 90% of time is spent cleaning WordPress junk tags. The cleaner the content — the faster the migration.
How to preserve SEO rankings during migration?
1) Preserve slugs: /blog/old-url → /blog/old-url. 2) Set up 301 redirects in nginx. 3) Transfer title and description to YAML Frontmatter. 4) Update sitemap in Google Search Console. 5) Monitor rankings for 4 weeks after migration. Case study: 0 losses.
What about WordPress plugins after migration?
Nothing is needed. GitHub CMS replaces: Yoast/RankMath (-499/year) → useSeo.ts, Schema Pro (-229/year) → JSON-LD from Frontmatter, WP Rocket (/year) → nginx gzip/brotli, Wordfence (/year) → CSP + HSTS. Savings -1100/year.
Can I keep my old WordPress hosting?
Yes, for images and files. Configure nginx to proxy /wp-content/uploads/ → old server. Or move all images to public/images/ once. After migration, old hosting can be downgraded to a minimal plan (-5/month) for static file serving.
What if rankings drop after migration?
Rankings may fluctuate in the first 1-2 weeks — this is normal. Key checks: 1) All 301 redirects are working (check via curl -I). 2) Meta tags match (compare via Screaming Frog). 3) Sitemap is submitted in Search Console. 4) TTFB ≤200ms. If all four points are met — rankings recover in 2-4 weeks.
Migration Checklist: Don't Forget Anything
Before shutting down old WordPress, make sure everything is ready. 10 checkpoints take 30 minutes but will save hours of fixes.
Article from Section 3: Content / Markdown. Created using prompt template article-5.txt (GLASS / HOME-5 style). Migration from WordPress to GitHub CMS — step-by-step guide and case study.