Crawld and Webflow
CMS collection items updated as drafts.
Status: Connector in progress . Today, scan a Webflow site free with no access granted, and every fix arrives written out for you to apply in the Webflow editor. Below is how the connector will deliver changes once it ships, and what it can honestly verify.
How fixes will arrive
Draft updates to collection items; published on your action.
What the rubric can see here
- Collection SEO fields
- Image alt text
- Slugs and canonicals
Limits worth knowing
- Designer-built static pages are not writable; those come back as advisory findings
Where this sits
| Mode | What we get | How changes arrive | Verified | Status |
|---|---|---|---|---|
| A · Repo write | A repo we can push a branch to | Pull request; you review and merge | Build | In progress |
| B · Read-only repo | Read access plus somewhere to push | Branch or fork you own | Build | In progress |
| C · Cloud mirror | A snapshot or export | Patch or PR from a clone | Build (mirror) | In progress |
| D · CMS drafts | OAuth into a hosted CMS | Unpublished drafts; you publish | Preview | In progress |
| E · URL only | A public URL | Written-out fixes; you apply | Advisory | Live |
Build-verified means a build ran. It applies to A, B and C and nothing else. A hosted CMS has no build, so D is preview-verified and E is advisory. Those labels are never blurred.
What you can do today
Scan the site. The free scan needs no access to Webflow. It reads the published HTML the way a search or answer engine does, runs all 129 checks, and reports what it could not measure rather than counting it as a pass. Every finding names the page and the change, so it is actionable by hand whether or not a connector ever exists.