In the fifth stage of our Build Week series, the site’s structure and features are in place, and it is time to fill it with the real thing. Content loading is when placeholder text and stock images give way to your words, your photos and your details. It is also when many small issues surface, which is exactly why it gets its own stage.
Getting content into the site
Depending on the agreement, content may be entered by the web team, by the business or by both. Either way, it typically involves:
- Adding final text to every page in the sitemap.
- Uploading photos, resized and compressed appropriately, with descriptive alt text.
- Creating products, services, events or staff profiles.
- Moving over blog posts or resources from the old website, if they are being kept.
- Adding downloadable documents, ideally in accessible formats.
- Writing page titles and descriptions for each page.
Real content often does not fit the design exactly as imagined. A heading may be longer than expected, or a section may have more items than planned. Small layout adjustments are common at this stage and are part of the process.
Planning redirects
If there is an existing website, some page addresses will change. Old addresses may be bookmarked, linked from other sites or listed in search results. During this stage, the team builds a redirect map that pairs each old address with its new equivalent, so visitors following an old link land somewhere useful instead of an error page.
Reviewing page by page
Once content is loaded, the business reviews the site carefully. This is the time to read every word. A systematic approach helps:
- Work through the sitemap in order, checking off each page as you go.
- Read on a phone as well as a computer.
- Check names, phone numbers, addresses, hours and prices against your records.
- Confirm that photos show what they claim and that you have permission to use them.
- Click every button and link on each page.
- Note anything that is unclear, outdated or missing.
It helps to have someone outside the daily business read through too. Fresh eyes catch jargon and assumptions that insiders overlook.
Keeping feedback organized
Content review generates many small comments. Collecting them in one place, such as a shared document or a feedback tool, with the page and the exact change noted, makes them faster to handle and less likely to be missed. Group related comments, and separate must-fix items from nice-to-have ideas that could wait until after launch.
Leaving week five
By the end of this stage, every page should have final content, the redirect map should be ready and the business should be comfortable with what the site says. Next, Build Week 6 focuses on testing: making sure everything works across devices, browsers and real-world situations before the site goes live.
A Page-Review Checklist
Reading every page carefully is easier with a consistent set of questions. Keep this list next to you and run each page through it:
- Purpose: Does the page do the job described in the content plan?
- First screen: On a phone, does the top of the page make clear what it is about and what to do next?
- Accuracy: Are names, numbers, hours, addresses and prices correct and consistent with every other page?
- Clarity: Would a first-time visitor understand every term, or is there jargon to explain or replace?
- Length: Is there anything that could be shorter without losing meaning?
- Images: Are photos sharp, relevant, properly cropped on phones and described with alt text?
- Links and buttons: Does each one go where it says it will?
- Page title and description: Do they describe the page accurately in words someone might search for?
- Next step: Is there a clear way forward at the end of the page?
Writing Content That Reads Well on a Screen
People rarely read web pages word for word. They scan, looking for the part that answers their question. A few habits make your content easier to use:
- Put the most important information first, then add detail.
- Use descriptive headings so a visitor can jump to the part they need.
- Keep paragraphs short. A few sentences each is plenty on a phone.
- Use lists for steps, options and requirements.
- Write the way you would explain things to a customer in person.
- Avoid repeating the same paragraph on several pages. Link to the main page on a topic instead.
Building the Redirect Map
If your old website is being replaced, the business can help make the redirect map complete. The web team will usually start from a list of the old site’s pages. Your role is to answer questions such as:
- Which old pages have direct new equivalents?
- Which old pages are being combined into one new page?
- Which old pages are being retired, and what is the closest helpful page to send visitors to instead?
- Are there addresses printed on flyers, vehicles, business cards or packaging that must keep working?
- Are there pages other organizations link to, such as a directory listing or a partner’s site?
That last pair of questions is easy to forget. A web address printed on a truck or menu cannot be updated with a click, so it deserves a redirect even if few people use it.
Mistakes That Show Up After Launch
- Different hours on different pages. Check every place hours appear, including the footer and contact page.
- Old prices or services left in place. Content carried over from the old site may describe things you no longer offer.
- Photos you do not have rights to. Images pulled from the web or from a past vendor may not be yours to use. Confirm permission now.
- Huge image files. Uploading photos straight from a camera can slow pages down. Ask your web team about the right sizes.
- Feedback that never gets marked done. Track each change until someone confirms it was made.
Questions Owners Ask
Who should proofread?
At least two people: someone who knows the business well, to check facts, and someone who does not, to check clarity. Reading on a phone catches problems that a computer screen hides.
What if some content is not ready?
Talk with your web team about whether a page can launch in a simpler form or be added shortly after launch. It is usually better than delaying the whole site for one section.




