Before a website goes live, make it prove itself.
A practical launch checklist from the first release of casagrowth.studio. These are checks we ran on our own site, what they found, and what they still cannot promise.
CASA GROWTH / WEBSITE LAUNCH NOTESPublishing is one step. Verification is the next.
A live website has to work for visitors, search engines, and the people who will maintain it. Our launch exposed small issues that a design review alone missed: a heading whose text lacked a space, low-contrast service copy, and a contact address that did not receive mail. Fixing those details mattered more than declaring the project finished.
This is a record of our own work, not a claim that every page ranks or that a PageSpeed score predicts sales. Use the same questions with any website partner, including us.
The release, examined.
Make every important page findable.
We listed the final launch pages in a public sitemap and linked each service page from the services hub or footer. A sitemap helps discovery, but a page still needs an internal path a visitor can follow. The launch sitemap listed 17 URLs, including service, project, and legal pages; new useful pages can be added as the site grows.
Open the sitemap and follow each important page from the main site. Remove dead ends and redirect old URLs when replacing existing pages.
Check the version a crawler receives.
For all 17 listed URLs, we checked the live response rather than relying on a local preview. Each returned HTTP 200 at its listed address, a unique nonempty title and description, one H1, a self-referencing canonical, and no noindex instruction. We also checked image alt attributes and internal link targets. Two headings looked right on screen but joined words in their underlying text, so we corrected them.
Test the published URL and its HTML. A successful build does not prove the production page has the intended title, canonical, or readable heading.
Test on a phone and fix the specific failure.
The homepage, services page, and projects page received mobile PageSpeed checks. The services report found low-contrast copy in a light section; we changed its text color and reran the audit. On October 18, the resulting mobile lab scores were 96 for homepage performance, 95 for services, and 99 for projects. All three scored 100 for automated accessibility and SEO checks in those runs.
Look beyond a single score. Check the finding, correct it, and inspect the live page at a phone width. Lab scores can vary and do not replace real-user data or manual accessibility testing.
Connect measurement to honest actions.
We verified domain ownership in Google Search Console with a DNS record, submitted the sitemap, and set up GA4. Analytics loads only after a visitor opts in. We distinguish a contact click or opened email draft from a message actually received. Until direct form delivery is working and tested, the site does not count a draft as a submitted inquiry.
Decide what each event means before calling it a lead. Test real delivery, keep the domain in an account you control, and check Search Console's actual indexing decision later.
See the public checks.
These links show the current sitemap and the dated mobile lab reports. Search indexing and field speed data change over time; a report is a snapshot, not a ranking promise.
Ask for the working version.
Before approving a launch, walk through the page a customer will use: find the service, read it on a phone, try the contact path, and confirm who receives the message. Ask who owns the domain and editing account, which URLs changed, and how you will measure inquiries. A clear answer to those questions is more useful than a promise to “do SEO.”