Automated Framer Pre-Publish Site Checks
Every Monday, WebRun opens Framer, walks every page of the sites you are about to publish, checks each for a missing page title or description, placeholder text, empty CMS entries, broken links and an unset custom domain, posts the fix list to Slack, and texts the designer anything that would block a publish.
How do I check a site for problems before publishing it?
WebRun runs your pre-publish checklist every Monday. It walks each Framer page for a missing title or description, leftover placeholder text, empty CMS fields, broken links and an unattached domain, posts the fix list to Slack, and texts the designer the blockers, so no page goes live half finished.
- Placeholder text and broken links are caught before the client sees them
- Every page gets a title and description check, not just the homepage
- A clean site is confirmed explicitly, so silence is never ambiguous
Built for web designers · digital agencies · freelancers · marketing teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
framer.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Framer - walk the pages for problems
framer.com
WebRun opens Framer to walk the pages for problems. - Open Framer and go to each site on the pre-publish list
- Walk every page and check the page title and description are set and not duplicated
- Look for placeholder text left in headings, buttons and body copy
- Check the CMS collections for entries with empty required fields
- Follow the internal and external links on each page and note the broken ones
- Confirm the custom domain is attached and the publish status is what you expect
Done when Every page of every listed site has been checked against the same list.
-
2
Slack - post the fix list
slack.com
WebRun opens Slack to post the fix list. - Post the fix list grouped by site and then by page
- Put missing titles and descriptions first, then placeholder text, then broken links
- List the CMS entries with empty required fields separately
- Say plainly when a site passed every check
- Leave publishing to a person. WebRun never publishes a site or edits a page
Done when The design channel has this week's fix list per site.
-
3
Twilio - text the designer blockers
twilio.com
WebRun opens Twilio to text the designer blockers. - Text the designer the problems that would embarrass you if published: placeholder text and broken links on live-facing pages
- Include the site and the page for each
- Send only to your own team numbers. WebRun never contacts the client
Done when The designer knows the blockers before touching publish.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it publish the site or edit a page?
No. WebRun only reads the site and reports. Editing content, fixing links, and pressing publish all stay with your designer.
What exactly does it check?
Page title and description on every page, leftover placeholder text, CMS entries with empty required fields, broken internal and external links, and whether the custom domain is attached.
Does it tell me when a site is clean?
Yes. A site that passes every check is stated explicitly in the Slack post, so you know the run happened rather than assuming silence means fine.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.