A childcare center director reviewing a tablet at her desk at dusk, with an empty playground beyond the window

Early learning center · Inclusive childcare, NC

Google was told not to read the site, and parents saw a banner that never changed.

A half-finished WordPress rebuild sat on a hosting company's staging server. Its robots file blocked every search engine, the forms did not send, and the closings banner was fixed text that always read open.

The work

What we did, and why

Parents check a childcare center's website for a handful of things, and most of them change often. Is the center open this morning? What is for lunch? When is the next family event? Is there a teaching job open? The site this center inherited could answer none of those reliably.

A WordPress rebuild had been staged and then left. Our review found that its robots file told every search engine to stay out, so the site could not have been found even once it launched. The tour, inquiry, and job forms were placeholders. The events calendar was empty, and the weather banner was typed into the page, so it said the center was open on every day of the year.

The review also showed that nothing on the site needed WordPress. We rebuilt it as static pages in the organization's own Azure tenant and kept every approved sentence exactly as written. The redesign followed the parent organization's brand, and the home page tour video now loads only when a parent presses play.

Search and AI answers were set up in the same pass, not after launch. Each page has its own title, description, and canonical address, and structured data describes the center as a childcare provider with its address and hours. An llms.txt file gives AI assistants a plain-language guide to every page.

The last piece was the editor. Staff sign in with the Microsoft accounts they already use and change closings, menus, events, and job postings themselves. Form messages arrive in an inbox in the same place. The site is built with our AI-assisted method, and the build is described on the portfolio page for this project.

Where they stand

The outcome

Every public page loads, every form reaches a staff inbox, and search engines are invited in rather than turned away. On the home page, the Lighthouse search score went from 92 to 100 and performance from 58 to 87.

For leadership

What changed

The director no longer waits on a developer to tell parents the center is closed for snow. Staff post closings, menus, events, and openings themselves, and the organization owns the site and its hosting outright.

Your turn next

The same method, applied to your systems.

Every engagement on this site started with a written assessment of what the company already ran. Yours starts the same way, and the assessment is yours to keep either way.