A complete company site with a bespoke template, copy, SEO, a form and analytics.
A company with no site, or with a site from 2015.
The smallest sensible scope that is not a compromise. The site gets a design made for its content, copy written by a person, full technical SEO and structured data, AA accessibility and a form whose messages actually arrive.
The things that are usually an upsell — the OG image, analytics, backups, the certificate, one-push deployment — are inside the scope here, because they stand on a platform that already exists.
A complete company site: a design made for your subject, the copy, and a launch with certificate, email and analytics.
A marketplace theme is picked to match an industry. We pick the design to match the content. First we know what the site has to say and to whom, and only then does AI propose a visual direction from a base of 67 styles, 161 palettes and 57 font pairings. A human makes the call and writes it down as the visual canon in the repository — that file then outranks any tool suggestion, so the site does not drift as changes pile up.
No Figma mock-up stage and no "template number 7". The first pass of the layout takes hours, and the time normally spent clicking through mock-ups goes back into the content and the details.
What you getVisual direction, the first pass of layout and components, draft copy, images, the OG image, alt texts.
The direction decision and its record, semantics and accessibility, performance, structured data that matches what is on the page, a review of all copy, deployment and maintenance.
Metadata, canonicals, sitemap, internal linking — and the decision about what belongs in the index at all.
The most common mistake on AI-generated sites: everything is indexable. Thousands of filter URLs, the crawl budget burned, and the site still does not grow. Here filtered views get `noindex, follow` and a canonical to the clean path.
Internal linking is a feature, not editorial goodwill: "more in this category", "previous and next", "similar by tags" and category and tag hub pages are generated from the data.
What you getDraft meta descriptions, spotting missing metadata, generating OG images.
Deciding what belongs in the index, and making sure internal links come from the data rather than from an editor’s memory.
Describing content in the format search engines and AI models read. Here it is a requirement, not an add-on.
One graph per page. `Organization` and `WebSite` with a search action sit once in the layout, and page nodes link to them by `@id`. On top of that: breadcrumbs and the narrowest entity type for the page — `Store`, `BlogPosting`, `Event`, `Product` with an offer, `FAQPage`, `HowTo`, `Person`, `Book`, `VideoObject`.
The hard rule: structured data must match what is visible on the page. A language model will happily add a 4.9 rating from 87 reviews that do not exist. That is a straight path to a penalty, not to stars in the results.
What you getA first pass of the graph from the content model, and spotting gaps.
Matching the type to the content and making sure the graph claims nothing the page does not show.
Page copy, articles, category descriptions and meta descriptions — written to a written canon, not "generated".
One steady author for the whole site, the choice recorded in the repository. Someone who cares about the subject, not an "editorial team". Spoken but correct language, domain vocabulary used naturally, and once per text room for a deeper thought — one sentence that follows from the subject, without preaching.
Resistance to detectors does not rest on a list of banned words but on a list of banned patterns: paragraph symmetry, triads, "not only… but also", an intro with no content, a summary ending, walls of lists, an even sentence rhythm, no specifics.
What you getDraft and research, title options, shortening to a meta description.
Fact-checking, rewriting in the persona’s voice, cutting the patterns that give a generator away.
Proof: A ban on inventing facts, data, quotes, opinions and testimonials is part of the service. The persona is a style, not a licence for fiction.
Contrast, focus, keyboard, semantics and forms you can fill in without a mouse.
Contrast of 4.5:1 measured against the lightest surface of each theme, visible focus, full keyboard support, alt texts that say something, semantics before ARIA, form fields with labels and errors tied to the field, `prefers-reduced-motion` respected, touch targets of at least 44 px.
A real example: accessibility went 96 → 100 with one colour fix (a token sat at 3.2:1 under 10–12 px labels, where 4.5:1 is required) and one map fix (every pin was a button with no name — now it carries the shop name and city). Two changes, two perfect scores.
What you getSpotting missing alt texts and labels, a first pass of fixes.
Contrast measured against the real background, screen-reader behaviour, and deciding where semantics is enough instead of ARIA.
A form with bot protection plus the mail setup that keeps the message out of spam.
Validation on both sides, a honeypot, rate limiting, optionally a captcha, sending from an address in your own domain, a message template, a copy for the sender, a GDPR consent next to the form and submissions stored in the panel.
Deliverability is a separate job: a sender address in your domain plus SPF, DKIM and DMARC records, and the contact alias routed to the owner’s real mailbox. That is the difference between "the form sends" and "the message arrives".
What you getThe form component, validation, the message template.
Mail and DNS configuration, deliverability tests, limits and spam protection.
A cookieless visitor counter — so no consent banner — on our server, with access for you.
Custom events (a discount code clicked, a form sent) and a monthly report that answers "where did they come from and what did they do", not "how many page views were there".
Where it stands today: our own instance, five registered domains, the script wired into four sites, traffic confirmed on three.
What you getA draft report and spotting anomalies in the traffic.
Wiring the counter, defining the events and interpreting the numbers.
Private project: The analytics panel is private, so the proof is a screenshot on a call, not an address.
Usually five to eight: home, about, services, contact, legal documents, and optionally a blog and a work section. More pages is not a technical problem, only more copy to write.
In this package the content lives in the repository, so we make the changes. If you want to edit it yourself, the right scope is the Content website package with a panel.
Yes. The repository, the database and the file storage are yours. We do not lock anyone into our platform.
We estimate in hours, after a phone call and a look at the project. Our latest projects took 15 to 45 hours.
