My Webflow MCP Prompt Library: 20 Prompts That Save Hours Every Week

Most Webflow prompt guides give you generic one-liners. "Update my CMS." "Change my site title." These aren't prompts — they're vague instructions that produce inconsistent results.

The prompts that actually save time are specific, structured, and written with a clear mental model of what Claude is doing with the Webflow API. These 20 prompts are the ones our studio uses in real client work. Copy them directly. Adapt the field names and collection names to match your own Webflow site schema.

Key Takeaways

• Specific, structured prompts outperform vague instructions by a wide margin — include field names, formats, and constraints
• Always start any session with a schema audit prompt so Claude knows your exact collection structure
• The review-before-push pattern is essential — always ask Claude to return proposed changes as a table before executing
• Batch operations are where MCP delivers the most time savings — lean into them
• FAQ and SEO prompts are the highest-leverage starting points for most Webflow sites

Foundation Prompts (Start Every Session With These)

1. Schema audit
"List all CMS collections on this site. For each collection, show the collection name, collection ID, and all field names with their types and slugs."

2. Item inventory
"List all items in the [Collection Name] collection. For each item show: item ID, name, slug, published date, and whether it's currently a draft."

3. Site health overview
"List all pages on this site with their current SEO title, meta description, and slug. Flag any pages where the SEO title is missing, over 60 characters, or duplicated."

SEO Prompts

4. Meta title audit and fix
"Review all items in the [Collection Name] collection. For each item where the SEO meta title field is empty or over 60 characters, write a replacement title that includes the primary keyword from the slug, stays under 58 characters, and is compelling. Return as a table: item ID, current title, proposed title, character count."

5. Meta description batch generation
"For all items in the [Collection Name] collection where the meta description field is empty, write a 145–155 character meta description based on the item name and body content. Include a benefit statement and a soft call to action. Return as a table with item ID and proposed description."

6. Duplicate title detector
"Scan all items in the [Collection Name] collection and identify any where the SEO meta title is identical to or a near-duplicate of another item's title. List the duplicates grouped by similarity."

Content Prompts

7. Excerpt generator
"For all items in the [Collection Name] collection where the excerpt field is empty, write a 2–3 sentence excerpt based on the item name and body content. Make each excerpt specific, reader-focused, and free of generic filler phrases like 'In this article' or 'We explore'. Return as a table."

8. Batch item creator
"Create [X] new items in the [Collection Name] collection using the following data: [paste your structured data]. Set all items as drafts. For each item, generate a slug from the name using lowercase letters and hyphens only."

9. Content freshness audit
"List all items in the [Collection Name] collection sorted by published date ascending. Identify any items published before [date]. Return the item ID, name, published date, and the first 100 characters of the body field so I can assess whether they need updating."

10. Field population check
"Audit the [Collection Name] collection for field completeness. For each item, report which of these fields are empty: [list your required fields]. Return a table showing item name and a tick or cross for each field."

Slug and URL Prompts

11. Slug standardisation audit
"Review all slugs in the [Collection Name] collection. Flag any that contain uppercase letters, underscores, spaces, or special characters. For each flagged item, propose a clean slug using only lowercase letters and hyphens. Return as a table: item ID, current slug, proposed slug."

12. Duplicate slug detector
"Scan all items in the [Collection Name] collection for duplicate slugs. List any duplicates with their item IDs so they can be resolved."

Migration Prompts

13. Schema mapping
"I'm migrating content from [Platform] to Webflow. Here is the source data structure: [paste structure]. Here is the Webflow CMS schema: [paste schema]. Map each source field to the appropriate Webflow field and flag any fields that don't have a direct match."

14. Batch migration create
"Create CMS items in the [Collection Name] collection using this migrated content: [paste content]. Match fields according to this mapping: [paste mapping]. Set all items as drafts and return a count of items created plus any errors."

Publishing Prompts

15. Batch publish
"Publish all items in the [Collection Name] collection that are currently set as drafts and have a published date on or before today."

16. Selective publish
"Publish the following items in the [Collection Name] collection: [list item names or IDs]. Confirm the count of items published and flag any errors."

Designer API Prompts (Requires Designer Open)

17. Canvas element audit
"Scan the current page and list all heading elements. For each heading, show the heading level (H1–H6), the text content, and the style class applied. Flag any heading hierarchy issues — for example, an H3 appearing without a preceding H2."

18. Missing alt text finder
"Scan all image elements on the current page. For each image, show the element ID, the current alt text (or flag if empty), and the image asset name. Return a list of all images with missing alt text."

19. Class naming audit
"List all style classes applied to elements on the current page. Flag any that appear to be inline styles rather than named classes, any class names containing spaces or uppercase letters, and any elements with no class applied."

20. Component instance check
"List all component instances on the current page. For each instance, show the component name, the element ID, and any props that have been overridden from the default values."

These 20 prompts cover about 80% of the real MCP work our studio does weekly. The remaining 20% is project-specific — custom schema queries, complex migration logic, integration-specific workflows. Once you're comfortable with these foundations, you'll start writing your own.

Want a session where we help you build a custom prompt library for your specific Webflow site? Get in touch.