A page can look finished in the editor while a form sends nowhere, a family photo shows a child’s full name, or a button disappears behind an image on a phone. Before I publish, I check the draft as an editor, a visitor, and a parent who would much rather catch a privacy mistake before bedtime than after someone shares the link.
1. Confirm what the page is for
Write down the page’s job in one sentence. A post about making a family photo book might help someone choose pictures. A page about ordering a personalized board book might explain the options and help someone send a question. Those jobs call for different next steps.
- Identify the intended reader. Is this for a parent gathering memories, a relative buying a gift, or someone looking for a caregiving tip?
- Check the promise. Do the title and opening match what the page delivers?
- Choose one useful next step. That might be reading a related page, getting in touch, or simply using the instructions and leaving satisfied.
If you need several sentences to explain the purpose, the page may be answering too many questions. Move unrelated material elsewhere or save it for later.
2. Read the copy once without editing it
Read from top to bottom as if someone had sent you the link. Can you tell which advice applies to you? Are the instructions in the order you’d use them? In a post about photographing a toddler for a keepsake, choosing a safe spot should come before camera settings.
On a second pass, check names, dates, prices, sizes, availability, and claims about materials or delivery against the current source, not an old draft. Replace “ships quickly” with a clear timeframe only if you can keep it up to date. If timing varies, explain why. Give health and child-safety advice extra scrutiny: remove unsupported guarantees, make the limits clear, and point readers to a qualified professional if the situation involves a health risk, violence, or crisis.
Then cut repeated points and explain unfamiliar terms. If you mention “bleed” in photo-book instructions, say it’s the extra image area that may be trimmed during production. No one should need a printing glossary to finish a family project.
3. Inspect every image and file
Photos need their own review on a family site. Check that you have permission to use each one, including pictures sent by another parent or relative. Look past the faces: school logos, house numbers, location clues, name tags, and screens in the background can reveal more than you meant to share. Permission to make a private book is not automatically permission to show its pages on a public website.
- Open each image at full size. Look for awkward crops, blurry text, and details you missed in the thumbnail.
- Write alt text for meaningful images that describes what matters in context. Decorative images can have empty alt text if your publishing system permits it.
- Check file names and downloadable documents for private information you meant to keep off the public site.
- Use appropriately sized images so a phone doesn’t have to download far more than it displays.
If a child or anyone else would be uncomfortable seeing a photo online, choose another image. A close-up of the pages can show a thick-cardboard book without showing an identifiable family portrait.
4. Preview the page the way a visitor will see it
The editor view isn’t the published page. Preview it at phone and desktop widths. Scroll slowly: watch for headings stranded above their paragraphs, captions beside the wrong photos, and buttons overlapping other elements. Try portrait and landscape orientation if the layout changes noticeably.
Check that the type is readable, the contrast is sufficient, and the text still works when enlarged. Don’t rely on color alone for instructions; naming an option is clearer than saying “select the green option.” Forms need clear field labels and error messages that explain what to fix. If phone layouts keep causing trouble, the post on making a family website easier to use on a phone covers the broader design work. Here, you’re checking this particular page before it goes live.
5. Test the paths into and out of the page
Click every link, including those in buttons and images. Does each one open the intended destination? Does an internal link lead to an unpublished draft? Decide whether the new page belongs in the navigation, a relevant category, or a nearby post. It doesn’t need its own menu item, but its intended reader should have a reasonable way to find it.
Actually use the next step. Submit a test inquiry and check what the visitor sees afterward, where the message arrives, and whether the notification includes what you need. Open the real download file. For a product option, follow the choice far enough to check that its name and price stay consistent. Delete test submissions when appropriate, especially if they contain personal details.
For a page with an important contact step, ask someone who hasn’t seen the draft to find it without directions. Where they pause can tell you more than another hour spent staring at your own button.
6. Check the page settings before pressing publish
Pick an address short enough to share and specific enough to recognize later. Check the spelling now; changing it after people have shared the page may mean setting up a redirect. Give the page a distinct title that says what it offers, and add a short description if your site has a field for one. These may appear in search results or shared previews, though that varies by platform.
Check the publication date, author, category, featured image, and visibility setting too. An obscure address won’t protect a page meant to be private; use your site’s access controls and test them while signed out. If the page is meant to be public, make sure it isn’t accidentally password-protected or marked to discourage search indexing. If your system shows a shared-link preview, look for an outdated picture or an awkward first sentence.
7. Publish, then check the live version
Once the page is live, open its address in a private browser window or while signed out. That can reveal differences the logged-in editor view hides. Load it on a phone, follow the main link, and test the form or file if there is one. Check that the address in the browser is the one you intended to publish.
If you changed an existing address, check that the old one takes visitors to the right new page. If you announced the page by email or on social media, open the link in that announcement as well. A working page can’t fix a mistyped link. For time-sensitive details, set a calendar reminder and note what you’ll need to recheck, such as a delivery cutoff or event date.
A reusable release note
Keep a short record of the page address, publication date, reviewer, and any follow-up. Mine might read: “Board-book care page; checked on phone and desktop; sample download opened; revisit cleaning guidance if materials change.” It gives future-me a place to start without turning publication into a paperwork project.