Publishing
Going live checklist
What to verify before you publish to the public.
Once something is live, the bar for quality jumps. Run this checklist before your first real publish — it takes five minutes and prevents almost every “I should have caught that” moment.
Content
- Every page’s copy is proofread. Ask PageFork to proofread if you want a second pass.
- Placeholders are replaced — no “Lorem ipsum”, “Your name here”,
or
#buttons. - Images are final — no stock-photo watermarks, no unlicensed photography, no low-resolution hero images.
- Contact details are correct — phone numbers, addresses, email addresses, social links all work.
Layout and responsive
- Desktop preview looks balanced at wide widths.
- Tablet preview (768 px) has no broken layouts.
- Mobile preview (375 px) has readable copy, tappable buttons, and a working nav. See Preview devices.
- Long content doesn’t overflow on mobile (tables, code blocks, long headlines).
Forms
- Every form has the fields you actually want.
- You’ve submitted a test entry to every form after publishing, and checked it arrived in the Submissions inbox.
- You’ve received the email notification (check spam). See Email notifications.
Domain and SSL
- Your free
*.pagefork.aisubdomain is the one you want. See Your PageFork subdomain. - Your custom domain (if any) shows status Active. See Connecting your domain.
- The site loads over HTTPS (padlock in the browser).
- Both
yourbrand.comandwww.yourbrand.comresolve if you want both. See Apex vs www.
Links and navigation
- All nav links go where you expect.
- All CTAs lead to a real destination (form, booking tool, pricing page).
- No accidental links to
/draft,/internal, or similar.
Analytics and SEO
- Page titles and descriptions are meaningful on every page. Ask PageFork to “set a great title and meta description on every page” if you haven’t already.
- Analytics is installed (if you want it).
- Favicon is yours.
Test on a real phone
The in-editor preview is good, but real phones catch issues the preview can’t (touch scrolling, viewport quirks, font rendering). Publish first, then test on your phone.