메뉴
Comprehensive audit of a Webflow site including pages, CMS collections, health scoring, and actionable insights. Use for site analysis, migration planning, or understanding site structure.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Run comprehensive accessibility audit (WCAG 2.1) on Webflow pages - checks buttons, forms, links, focus states, headings, keyboard navigation, and generates detailed reports with fixes. Runs entirely headlessly against a page ID — no Designer connection required. Excludes image alt text (covered by asset-audit skill).
Build and manage pages, elements, components, and styles in Webflow Designer. Use when adding sections, creating layouts, building elements, inspecting or updating components, viewing what's inside a component, restructuring pages, creating new pages, previewing page structure, styling elements, or managing component properties. Building, styling, and inspecting run headlessly against an explicit page ID — no Designer connection needed. Designer is required for `designer_tool` actions (reading/switching the page open on canvas, interactively selecting an element, creating page folders, opening a component's canvas view) and for `element_snapshot_tool` visual previews.
Apply Flowkit CSS naming system in Webflow. Use when creating classes, auditing existing naming, or building new components following Flowkit conventions. Flowkit is Webflow's official CSS framework with utility-first approach. Runs headlessly against a page ID — no Designer connection required, except for the optional live-canvas conveniences (current page, interactive element selection).
Analyze assets on a Webflow site for SEO optimization. Identifies assets missing alt text and assets with non-SEO-friendly names, then generates and applies improvements.
Find and fix broken or insecure links across an entire site, including CMS content, to improve SEO and user experience. Audits HTTP/HTTPS issues and validates all internal and external links.
A Webflow University guided onboarding skill for anyone getting started with the Webflow MCP. Checks your Webflow connection, helps you choose a real workflow to try, coaches prompt writing, and supports you through your first MCP run.
| name | webflow-mcp:site-audit |
| description | Comprehensive audit of a Webflow site including pages, CMS collections, health scoring, and actionable insights. Use for site analysis, migration planning, or understanding site structure. |
Comprehensive audit of a Webflow site's structure, content health, and quality with detailed analysis and multiple export formats.
ALWAYS use Webflow MCP tools for all operations:
data_sites_tool with action list_sites for listing available sitesdata_sites_tool with action get_site for detailed site informationdata_pages_tool with action list_pages for retrieving all pagesdata_cms_tool with action get_collection_list for listing CMS collectionsdata_cms_tool with action get_collection_details for detailed collection schemasdata_cms_tool with action list_collection_items for counting itemswebflow_guide_tool to get best practices before startingcontext parameter (15-25 words, third-person perspective)data_sites_tool with action get_site to retrieve:
data_pages_tool with action list_pages to fetch all pagesdata_cms_tool with action get_collection_listdata_cms_tool with action get_collection_detailsdata_cms_tool with action list_collection_itemsUser prompt:
Give me a complete inventory of my site.
Step 1: Initial Report (Standard Inventory)
📊 Site Audit: MCP Demo#1
**Site Details:**
- Site ID: 6924868ede9d3fbbc3195eb0
- Last published: January 9, 2026
- Last updated: January 9, 2026
- Timezone: Asia/Calcutta
- Primary locale: English (en)
---
**Pages (2 total):**
Static Pages (1):
├── Home (/)
CMS Template Pages (1):
└── Blog Posts Template (/post)
- Collection: Blog Posts
---
**CMS Collections (1):**
Blog Posts (9 items)
├── Slug: post
├── Fields (8):
│ ├── Name (PlainText, required)
│ ├── Slug (PlainText, required)
│ ├── Post Body (RichText)
│ ├── Post Summary (PlainText)
│ ├── Main Image (Image)
│ ├── Thumbnail image (Image)
│ ├── Featured? (Switch)
│ └── Color (Color)
---
**Summary:**
- ✅ 2 pages (1 static, 1 CMS template)
- ✅ 1 CMS collection with 9 published items
- ✅ Site fully published and up-to-date
Would you like a detailed analysis or export in a specific format?
Step 2: Detailed Analysis (when user requests)
🔍 Detailed Analysis: MCP Demo#1
**Content Health Score: 85/100**
✅ Strengths:
- All collections have items (no empty collections)
- All pages are published (no drafts)
- Site recently published (Jan 9, 2026)
- Consistent field structure in Blog Posts
⚠️ Areas for Improvement:
- No SEO metadata on template page (missing meta description)
- Limited page count (consider adding About, Contact pages)
- No reference fields (could link categories/authors to posts)
💡 Recommendations:
1. Add meta descriptions to all pages for better SEO
2. Consider creating a Categories collection for post organization
3. Add an Authors collection for multi-author blog support
4. Create navigation pages (About, Contact, Privacy Policy)
**Collection Breakdown:**
Blog Posts:
- 9 published items (0 drafts, 0 archived)
- 5 featured posts (56%)
- All required fields populated ✓
- Field usage:
- Name: 100% (9/9)
- Slug: 100% (9/9)
- Post Body: 100% (9/9)
- Post Summary: 100% (9/9)
- Main Image: 100% (9/9)
- Thumbnail: 100% (9/9)
- Featured: 100% (9/9)
- Color: 100% (9/9)
**Sample Items:**
1. "Why Webflow is the Best Choice for 2026" (featured)
2. "Top Webflow Features to Look Forward to in 2026"
3. "Webflow vs. Competitors: Who Will Win in 2026?" (featured)
---
Export this inventory? (markdown/json/csv/no)
Step 3: Export Options
📥 Export Format Options:
1. **Markdown** - Human-readable documentation
- Great for README files, wikis, documentation
- Preserves structure and formatting
2. **JSON** - Machine-readable structured data
- Perfect for migrations, integrations
- Includes all raw API data
3. **CSV** - Spreadsheet-friendly
- Easy to analyze in Excel/Google Sheets
- Separate files for pages and collections
Which format would you like? (1/2/3)
Site Information:
data_sites_tool with action get_siteUser Options: Offer multiple detail levels:
Page Categorization:
Page Health Checks:
Collection Details: For each collection, show:
Field Analysis: Categorize by type:
Field Validation:
Content Health Score (0-100): Calculate based on:
Issue Detection:
Recommendations: Suggest improvements based on:
Markdown Export:
# Site Audit: [Site Name]
## Site Information
- ID: [site-id]
- Last Published: [date]
## Pages
### Static Pages
- Home (/)
- About (/about)
### CMS Templates
- Blog Post (/post/[slug])
## Collections
### Blog Posts (47 items)
**Fields:**
- Title (PlainText, required)
- Slug (PlainText, required)
- Content (RichText)
...
JSON Export:
{
"site": {
"id": "...",
"name": "...",
"lastPublished": "..."
},
"pages": [...],
"collections": [...]
}
CSV Export: Generate separate files:
pages.csv: All pages with metadatacollections.csv: Collection metadatafields.csv: All fields across collectionsitems.csv: Item counts per collectionBatch Processing:
Error Handling:
data_pages_tool with action list_pages fails, continue with collectionsdata_cms_tool with action get_collection_details fails, show basic collection infoData Efficiency:
Read-Only Operation:
Clear Organization:
Actionable Output:
Version Tracking: If user runs inventory multiple times: