Skip to content

What you receive

The site is the visible part. This is everything else you receive.

At the end of every project we hand over what makes the site yours and lets anyone keep it running: domain, code, accounts, content and a document that explains each piece, plus a record of how the site was verified. This is the folder, item by item.

The Digital Asset Folder

Eleven items, labelled and in your name.

  1. 01Your websitePublished, with the address of the live site and of the preview.
  2. 02Your domainRegistered in your name, with the registrar access documented.
  3. 03HostingWhere the site lives, in your account, and how to reach it.
  4. 04Site filesThe complete code, ready to hand to any developer.
  5. 05Your brandLogo, colours and typography, if included.
  6. 06Copy and contentAll the text of the site, organised and editable.
  7. 07ImagesOptimised for the web, and in their original quality.
  8. 08Accounts and accessEvery account created for the project and who controls it.
  9. 09SecurityTwo-factor authentication and recovery notes for the accounts that matter.
  10. 10Handoff documentWhat each piece is and how to use it, in plain words.
  11. 11Verification recordWhat was checked before publication, the state of each point and what was left open, dated.

Items marked “if included” depend on the scope of the project. Maintenance is optional and separate.

The handoff document

No knowledge left in someone else's head.

The handoff document is the manual for your site. If you change provider, it is what the next team reads first.

  • The live site and where it is hosted
  • The domain, whose name it is in, and how to renew it
  • Where the code lives and how to deploy it
  • Every account created, and what each one is for
  • How the site was verified, and what its record says
  • How to protect and recover your accounts
  • What the service covers after delivery
  • How to revoke any access we held

A real record

Our own site, verified on 2 October 2026.

This is the verification record of ownsitestudio.com for the release published that day, with internal identifiers removed. It includes the point that failed: a record that only ever shows passes proves nothing.

Site
ownsitestudio.com
Date
2 October 2026, 12:10–12:22 UTC
Checked on
The live site
Standard
The OwnSite standard, version 0.1
Tools
Browser automation (Chromium), axe-core, Lighthouse, Schema Markup Validator, and command-line checks of DNS, certificates and responses

States

Not met
Checked, and it fails.
Not verified
Not checked, and said so.
Owner action
Depends on the site's owner.
Observation
Works, with something worth noting.
Out of scope
Deliberately not covered.
Not applicable
Doesn't apply to this site.
Verified
Checked, with evidence.

No score. Each point keeps its own state.

Summary

  • Not met1
  • Not verified3
  • Owner action4
  • Observation13
  • Out of scope1
  • Not applicable4
  • VerifiedEvery other point

Results by area

Domain and ownership

  • VerifiedThe domain points to the hosting, HTTPS is valid and http redirects to https.
  • Owner actionThe domain expires on 21 June 2027: renew it before that date.
  • Not verifiedControl of the domain at the registrar: it requires the owner's own session.
  • ObservationThe www address answers directly instead of redirecting, with the main address as canonical.
  • ObservationThe domain's email and DNS hardening records are incomplete.

Pages

  • VerifiedAll 18 pages in the sitemap answer correctly, each with its own title, description, one main heading, language and canonical address.
  • ObservationThe error page shows both languages, with two main headings.

Search engines and languages

  • Verifiedrobots.txt, the sitemap and reciprocal language versions on all 18 pages.
  • ObservationThe automatic language redirect adds about 0.8 s on a simulated mobile connection.
  • Out of scopeSearch Console.

Structure and facts

  • VerifiedLandmarks and heading order on every page.
  • VerifiedStructured data with 0 errors in an external validator, on 10 pages.
  • VerifiedThe same facts in the text, the metadata and the structured data.
  • ObservationOne non-critical validator warning.
  • ObservationTwo secondary texts (the footer and the app manifest) still used the previous wording.

Sharing

  • VerifiedTitle, description and preview image complete on all 18 pages, and the preview images checked.

Quality

  • Verified76 page loads at four screen widths, without horizontal overflow.
  • Verified0 script errors, and all 29 links working.
  • Verified0 automated accessibility violations in 38 runs.
  • VerifiedKeyboard navigation, visible focus and the mobile menu; reduced motion respected.
  • Not verifiedManual accessibility review (screen reader, 200% zoom, manual contrast): not done.
  • VerifiedLab performance on the day, as a one-day measurement: the home on mobile showed its largest content in 2.1 s.
  • ObservationOn mobile, the home could show its main content sooner.
  • ObservationA lab tool flags the logo's accessible name, which meets the accessibility guidelines.

Project form

  • VerifiedValidation in the browser and on the server.
  • VerifiedOne real test submission, accepted by the email provider.
  • Not verifiedArrival of that email in the inbox, on the day.
  • Not metThe copy of each inquiry saved to a database failed in production.
  • Owner actionDecide on that database copy.
  • Owner actionConfirm the test inquiry arrived, and delete it.

Security

  • VerifiedSecurity headers present.
  • VerifiedNo secrets or source maps in the served code, and private files unreachable.
  • ObservationTwo optional hardenings of the security headers, not applied.
  • Owner actionA security contact file: it needs a studio mailbox first.

Delivery

  • VerifiedThe site builds cleanly from its repository alone.
  • ObservationThe upload included a build cache file. It isn't source code and doesn't affect the site.
  • Not applicableHandover to a client: it's the studio's own site.

What happened afterwards

The failed point was resolved afterwards: the database copy was removed, and the form now delivers by email only, as the privacy policy describes. The next record will confirm it. This one stays as it was.

The inbox delivery that had been left unverified was later confirmed.

Limits

A record shows the state on one date. It is not a certificate, and it doesn't guarantee rankings, indexing, traffic or how AI systems use the site. Parts of the site depend on third parties: hosting, domain registrar and email provider. This is a summary; the full record lists every check with its evidence.

What ownership means

A specific promise, not a slogan.

  • It's in your name.
    Domain, hosting and accounts are registered to you — not held inside our systems.
  • You don't depend on us.
    The site stays online without any payment to us. Maintenance is optional.
  • You can leave at any time.
    Everything is documented, so any other team can take over where we stopped.
  • You can close our access.
    After handoff you revoke any access we held. The steps are in the document.
A checklist for any handoff, whoever builds your site

Tell us about your project.

A short form with no technical questions and no payment. We reply honestly, and with a proposal if we're the right studio.

Start a project