What We Ship Before You Say Go: Every Default We Wire Into A Small-Business Website

Most local-business website quotes talk about pages: one page, five pages, ten pages. Pages matter, but they are not the whole job. A useful launch also needs the quiet defaults: metadata, structured data, cookie consent, accessible controls, form routing, source ownership, image sizing, a sitemap, and a plan for what happens when the opening hours change next month.

Those defaults are where a cheap site often becomes expensive. If you start with a platform login, the platform may give you a blank canvas and a handful of prompts, but it does not interview your business, decide which questions deserve a page, write a privacy notice around your real data flow, or make sure the enquiry arrives in the right inbox. That is the difference between having a tool and having a website.

Our launch checklist exists because AI summaries and modern search results are less forgiving of vague pages. Pew measured AI summaries appearing on 18% of US Google searches in March 2025, and users clicked a traditional result in 8% of visits with a summary versus 15% without one [`pew-ai-overviews-clicks-2025`]. The lesson is not to chase tricks. The lesson is to make every page clearer, more structured, and more useful than it used to need to be.

The first default is ownership. A client should leave with the source, domain route, hosting notes, content, and enough hand-over context for another developer to continue the work. That rule is not glamorous, but it removes the lock-in anxiety that sits behind many buyer questions. If the site is yours, the relationship stays honest.

Another default is image discipline. Local-business sites often arrive with mixed photos: portrait phone shots, old logos, screenshots, and a few strong images hiding in the camera roll. We crop, name, size, and describe images so they support the page rather than slowing it down. Good alt text is part of that work. So is refusing to use a decorative image as proof when it does not show the business clearly.

The second default is contact plumbing. Every build needs clear phone links, email links, a tested form, spam checks, a confirmation state, and an owner email that contains enough context to reply properly. On this site that means Supabase persistence, Resend delivery, a reCAPTCHA stub that only runs when configured, and Plausible events that avoid personal details. No secret key should be needed at build time, and no form should depend on luck.

The third default is metadata and structured data. Title tags, descriptions, Open Graph defaults, JSON-LD, breadcrumbs, sitemap entries, and visible page content all need to tell the same story. BrightEdge measured overlap between AI summary citations and organic rankings rising from 32.3% to 54.5% over 16 months [`brightedge-rank-overlap-aio-2025`]. That makes traditional SEO foundations more important, not less important.

The fourth default is accessibility. We set a WCAG 2.2 AA floor: visible labels, focus rings, good contrast, tap targets that work on phones, real buttons for actions, and reduced-motion handling. Accessibility is not a decoration after launch. It changes how the design is built, how forms are tested, and whether the site is usable when someone is tired, rushed, or using assistive technology.

The fifth default is plain-language content. A useful page should answer the questions customers ask before they trust the business: what is offered, how it works, what it costs or how quotes are handled, where it happens, and what to do next. The GEO research found quotation, statistics, and source citation among the strongest methods, each delivering 30–40% gains in position-adjusted word count in its benchmark [`geo-aggarwal-arxiv-pdf-2024`]. We do not treat that as a guarantee. We treat it as a reminder that sourced, specific writing beats filler.

The final default is measurement. You cannot improve what you never observe. At launch, a small business should at least know whether the form submits, whether people click the phone number, whether core pages are indexed, and whether the site is fast enough. Measurement does not need to become a dashboard obsession. It just needs to stop the website becoming a brochure nobody checks.

Defaults do not remove the owner from the process. They make the owner's time count. We still need the business shape, services, places served, best proof, real photos where possible, opening hours, pricing posture, and the questions customers ask before they buy. A good website is not made from generic answers. It is made from a clear brief and a disciplined launch system.

That is why our packages are scope-led. P1 is for a high-density single page. P2 is for a multi-page site. P3 is for service and area structure. The defaults travel across all three; the difference is how much content and local-search structure the business needs. The promise is not magic. It is that the important work is wired in before you say go-live.