/site-audit

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.

Site Audit

Comprehensive audit of a Webflow site's structure, content health, and quality with detailed analysis and multiple export formats.

Important Note

**ALWAYS use Webflow MCP tools for all operations:**

• Use Webflow MCP's `data_sites_tool` with action `list_sites` for listing available sites
• Use Webflow MCP's `data_sites_tool` with action `get_site` for detailed site information
• Use Webflow MCP's `data_pages_tool` with action `list_pages` for retrieving all pages
• Use Webflow MCP's `data_cms_tool` with action `get_collection_list` for listing CMS collections
• Use Webflow MCP's `data_cms_tool` with action `get_collection_details` for detailed collection schemas
• Use Webflow MCP's `data_cms_tool` with action `list_collection_items` for counting items
• Use Webflow MCP's `webflow_guide_tool` to get best practices before starting
• DO NOT use any other tools or methods for Webflow operations
• All tool calls must include the required `context` parameter (15-25 words, third-person perspective)

Instructions

Phase 1: Site Selection & Discovery

1. **Get site**: Identify the target site. If user does not provide site ID, ask for it. 2. **Fetch site details**: Use Webflow MCP's `data_sites_tool` with action `get_site` to retrieve:

• Site name and ID
• Last published date
• Last updated date
• Timezone
• Locales (primary and secondary)
• Custom domains

3. **Ask user preferences**: Ask what level of detail they want:

• Quick summary (counts only)
• Standard inventory (pages + collections + counts)
• Detailed inventory (includes all field schemas, item samples, SEO data)
• Full export (everything + export to file format)

Phase 2: Pages Inventory

4. **List all pages**: Use Webflow MCP's `data_pages_tool` with action `list_pages` to fetch all pages 5. **Categorize pages**:

• Static pages (no collectionId)
• CMS template pages (has collectionId)
• Archived pages
• Draft pages

6. **Analyze page structure**:

• Count pages by type
• Identify pages missing SEO metadata
• Detect orphaned pages (no navigation links)
• Check for duplicate slugs

Phase 3: CMS Collections Inventory

7. **List all collections**: Use Webflow MCP's `data_cms_tool` with action `get_collection_list` 8. **For each collection**:

• Get detailed schema using Webflow MCP's `data_cms_tool` with action `get_collection_details`
• Count items using Webflow MCP's `data_cms_tool` with action `list_collection_items`
• Analyze field types and requirements
• Identify required vs optional fields
• Detect reference fields and relationships

9. **Collection analysis**:

• Empty collections (0 items)
• Unused collections (no template page)
• Large collections (100+ items)
• Collections with missing required fields

Phase 4: Analysis & Insights

10. **Generate insights**:

• Total content count (pages + items)
• Content health score
• SEO readiness
• Recommended improvements

11. **Identify issues**:

• Missing SEO metadata
• Empty collections
• Orphaned pages
• Draft content ratio

12. **Show relationships**:

• Which pages use which collections
• Reference field connections
• Content dependencies

Phase 5: Export & Formatting

13. **Ask export format** (if user wants full export):

• Markdown (readable, great for documentation)
• JSON (machine-readable, for migrations)
• CSV (spreadsheet-friendly, for analysis)
• Text summary (console output only)

14. **Generate report** in requested format 15. **Provide actionable insights**: Suggest next steps based on findings

Examples

**User 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)
  - Feat