Larger CMS jobs bring together more content, connections, and decisions. Your agent can handle much of that work, but it still needs a plan your team can review as it goes.

Plan the CMS

Whether you're starting fresh or migrating existing content, make sure the plan answers a few key questions before your agent changes the site:

• What does each Collection manage?
• Which fields belong in each Collection, and how will their values be used?
• How should the Collections connect?
• Does the structure fit within the current limits for reference fields and nested Collection lists?
• What might your team need as the content grows?

Ask your agent to explain its recommendations and wait for your approval before building.

If the content should support AEO, plan fields for authorship, freshness, related content, and metadata, and identify where each value will be used on the published site.

Plan the content

Next, decide where the content will come from and how the agent should add it:

• Where does each field value come from?
• What can the agent create from existing content?
• What requires another source or human review?
• What order should the agent follow, and what needs to exist at each step?
• How will the agent access and match images or other files?

For a migration, also check what each source record represents and which value the agent should use to identify a match. If information is missing or conflicting, have the agent flag it instead of filling in facts it can't verify.

Work in reviewable batches

Don't start with the whole job. Choose a small test group that includes a typical CMS item and a few examples that could reveal problems, such as missing values, similar names, references, or images.

Your site’s CMS limits affect how much content it can hold, while API rate limits may affect how quickly your agent completes the work. Check the current limits for your setup before starting a larger job.

Check that:

• Values appear in the intended fields
• References connect to the intended items
• Existing items aren't duplicated
• Images and links work as expected
• Draft and published statuses match your instructions
• Unknown information remains flagged for review

Keep each batch small enough for your team to review before the agent continues. Once the test passes, apply the approved plan to the next group.

Tip: If the job spans several prompts or working sessions, ask your agent to summarize what it completed, what remains, and what needs review. Keep that summary plan instead of relying on the conversation as your only record.

Get more from each request

Efficient AI use isn't about asking your agent to do less. It's about removing avoidable guesswork before the work begins.

When the structure is approved, the request is specific, and the batch is manageable, the agent has a better chance of producing work your team can approve. That means fewer rounds spent correcting the same issues across more content.

Keep learning

These resources can help you revisit part of the workflow or continue into how CMS content is displayed on your site:

• CMS Collections — the Webflow Way guide to planning content types, fields, relationships, and migration order
• Design and manage CMS content in Webflow — a Webflow University course on building, managing, and displaying dynamic content with Collection Pages and Collection Lists
• Webflow MCP server — the Webflow developer documentation for connecting compatible agents and reviewing the current MCP tools
• How do I import content into the Webflow CMS? — the Webflow Help Center guide to preparing and importing CMS content with a CSV file
• Add schema markup in Webflow to improve SEO and AEO — the Webflow Help Center guide to adding schema markup and connecting supported CMS fields

Almost there

Click Complete & continue to decide when a CMS job calls for a reusable skill and start planning one.