id, title, category, status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, verification_status, tags, raw_sources, last_reinforced, github_commit, tech_stack
id
title
category
status
canonical_id
aliases
duplicate_of
source_trust_level
confidence_score
verification_status
tags
raw_sources
last_reinforced
github_commit
tech_stack
wiki-2026-0508-seo-중심의-마케팅-및-블로그-사이트-구축
SEO 중심의 마케팅 및 블로그 사이트 구축
10_Wiki/Topics
verified
self
seo-marketing-site
blog-site-construction
none
A
0.9
applied
seo
marketing-site
blog
ssg
frontend
next-js
astro
2026-05-10
pending
language
framework
typescript
astro-next-js
SEO 중심의 마케팅 및 블로그 사이트 구축
매 한 줄
"매 organic search 의 의 LCP < 2.5s + crawlability + structured data + content velocity 의 four-pillar 의 site architecture." . 2026 의 의 SEO-first build 의 의 default stack 의 Astro / Next.js (SSG) + MDX content + Schema.org JSON-LD + Core Web Vitals optimization — 매 GEO (Generative Engine Optimization, AI overview) 의 등장 의 의 traditional SEO 의 augment.
매 핵심
매 4-pillar
Crawlability : server-rendered HTML, sitemap, robots.txt, canonical URLs, hreflang.
Performance : LCP < 2.5s, INP < 200ms, CLS < 0.1 — Core Web Vitals 의 ranking factor.
Content : depth, freshness, E-E-A-T (Experience, Expertise, Authoritativeness, Trust).
Structure : Schema.org JSON-LD, OpenGraph, semantic HTML, internal linking.
매 stack 선택
Astro : content-heavy, Islands architecture, minimal JS — best LCP.
Next.js (App Router, SSG mode) : hybrid 가능, MDX support, vast ecosystem.
Hugo / 11ty : pure SSG, sub-second build, no JS runtime.
WordPress (headless) : editorial workflow + Astro/Next frontend.
매 2026 GEO consideration
AI overview (Google SGE, Perplexity, ChatGPT search) 의 citation 의 desired — clear <h1>, summary paragraph, bulleted facts, schema markup.
LLM-friendly: clean semantic HTML, llms.txt 의 publishing.
매 응용
SaaS marketing site (homepage + features + pricing + blog).
Tech blog with MDX + code highlighting.
Documentation site (Mintlify, Nextra, Starlight).
Local business + multi-region landing pages.
💻 패턴
Astro 의 blog setup
JSON-LD (Article schema)
Sitemap (Next.js App Router)
Robots + canonical (Next.js metadata)
LCP 최적화 (preload hero image)
MDX + content collection (Astro)
llms.txt (2026 GEO)
CWV 의 monitoring (Vercel Speed Insights / web-vitals)
매 결정 기준
상황
Stack
Pure content / blog
Astro (Islands, near-zero JS)
Marketing + app shell
Next.js (App Router, SSG/ISR)
Editorial team (CMS)
Headless WP / Sanity + Astro
Docs site
Starlight / Nextra / Mintlify
Multi-region SEO
Next.js + i18n routing + hreflang
기본값 : Astro + MDX + Vercel/Netlify deploy + Sanity/Contentlayer (if CMS needed).
🔗 Graph
🤖 LLM 활용
언제 : marketing site, blog, docs, public-facing SEO-critical content, GEO optimization.
언제 X : authenticated app (SPA), real-time UI (SPA/SSR), no SEO requirement.
❌ 안티패턴
SPA 의 marketing site : crawlable HTML 의 부재 — SSG/SSR 의 mandatory.
Render-blocking JS / fonts : LCP 의 destroy — font-display: swap, defer non-critical JS.
Image 의 dimensions 의 unspecified : CLS regression — width/height 의 항상 의 specify.
Duplicate content 의 canonical 의 부재 : SEO penalty — <link rel="canonical"> 의 필수.
Schema.org 없음 : rich result + AI overview citation 의 lose — JSON-LD 의 add.
Sitemap 의 stale : ISR / on-demand revalidate or build-time regenerate.
GEO ignore : AI search traffic 의 2026 의 surge — llms.txt + clear semantic HTML.
🧪 검증 / 중복
Verified (Google Search Central, web.dev CWV, Astro/Next.js 2026 docs, llms.txt spec).
신뢰도 A.
🕓 Changelog
날짜
변경
2026-05-08
Phase 1
2026-05-10
Manual cleanup — full 2026 SEO playbook with GEO + Astro/Next stack