Website and shop
Your website is the one thing every other part of Autopilot points at. Ads send people there, sales forms fill from it, and the funnel is measured on it. So it is built first, checked constantly, and repaired without being asked.
What gets built
Section titled “What gets built”At onboarding you get a preview wireframe within minutes. It is replaced by the real site once the research is in: a full animated site, built from one scaffold but art-directed per business, so two companies on the platform do not look like two instances of the same template.
It goes live on its own address under run.linkworld.ai. Pointing your
own domain at it is not self-service yet — the certificate at the edge
covers *.run.linkworld.ai only, so a DNS record alone would land a
visitor on a certificate warning. Ask and we set it up.
Three things ship with it, without being asked for:
- The conversion path that fits your business model. A shop gets a checkout, a SaaS gets a signup, a service business gets a booking or an enquiry form. Which one is decided by the business model detected at onboarding.
- First-party tracking. Your own pixel, on your own domain — visits and funnel steps, no third-party dependency.
- The baseline SEO machinery — sitemap, robots, structured data, and a blog you can publish into.
Changing it: point, then say what you want
Section titled “Changing it: point, then say what you want”Open Company → Website. The live site is in front of you, not a form describing it.
- Click the section you want changed. The preview highlights it.
- Say what should be different — in the operator chat on the right, in your own words: “headline sounds like a brochure, make it about the waiting time”.
- The change comes back as an approval, not as a fait accompli. You see what it will look like before it is live.
- A rollback point is kept, so an edit that turns out wrong is one step back and not a rebuild.
The same works for the blog and for product copy. What you cannot do here is edit HTML by hand — that is a deliberate limit, because every change has to pass the checks below.
What gets checked after every change
Section titled “What gets checked after every change”A deploy is not the end of a change. After every one, the site is walked the way a visitor would and six things are asked:
| Check | The question |
|---|---|
| Reachable | Does the site load at all? |
| Content | Is the page that was changed actually reachable, or orphaned? |
| Visuals | Do images render, is the palette intact, is anything visibly broken? |
| Sale-ready | Can a visitor complete the conversion for this business model? |
| Indexable | Can search engines read it — sitemap, robots, structured data? |
| Fresh | Is the live site the version that was last built, or a stale copy? |
A failed check is not a notification you have to act on: it becomes a repair the operator queues and runs itself. Each kind of repair has an attempt limit inside a rolling window — if the third attempt at the same problem does not hold, it stops trying and escalates to you rather than looping.
The sale-ready check is the strict one. An unconfirmed conversion path counts as missing, not as probably fine, and the storefront gate holds until it is proven. That is the mechanism behind “no traffic to a site that cannot sell” — it is not a policy someone has to remember.
Taking money
Section titled “Taking money”If you sell on the site, checkout and subscriptions run in the same workspace as your quotes and invoices, so a payment and its document are not in two systems.
Two things speed up filling a shop:
- Product listing auto-write — upload your catalogue file and every item gets a sales description written from it.
- Lead capture forms — a published form whose entries land directly in the sales pipeline, not in an inbox someone has to copy from.
Seeing what happens on it
Section titled “Seeing what happens on it”Website analytics records sessions and funnel steps and shows where visitors stop. That is also what feeds the ad verdicts: without it, a cost-per-click number is nearly worthless, and Autopilot treats it that way rather than pretending it means something.
If your site is somewhere else
Section titled “If your site is somewhere else”You do not have to move. Autopilot works with a connected site too — but the limits are real and worth knowing before you plan around them:
| Site built here | Your existing shop system | |
|---|---|---|
| Edit content | yes, with approval and rollback | product copy and custom code, preview first |
| Structural changes | yes | come back to you as instructions |
| Self-repair | yes | limited to what the connection allows |
| Tracking | installed automatically | installed if the system permits it |
Where this lives
Section titled “Where this lives”- Company → Website — the live preview and the editing flow
- Company → Commerce-Ops — payments taken through the storefront
- Marketing → Products — the catalogue behind the listings
Where to read next
Section titled “Where to read next”- What Autopilot can do — the full feature list, including the parts not covered here
- How Autopilot works — why the storefront comes before acquisition in the nightly order