Forty public projects you can open, fork and reshape with a few sentences.
Browse templatesSeparate client workspaces, white label, and the Git repo handed over at the end of the engagement.
See the programmePaste a URL. In thirty seconds you see exactly what Google receives before any JavaScript runs.
Check a URLName the offer, the price, the end date, and the one action. Eqlo writes the reading order, the form, and the first HTML in two to five minutes. The rest of a half hour is your price and your catch. Free is $0 with one seat. Plus is $19 for your domain.
Open a project and type a sentence in the chat. A useful line names the audience, the price, the end date, and the one action. An illustrative starting line is "Landing page for a Saturday glaze workshop in Portland, $85, twelve seats, ends Friday, email to reserve." Attach a photo of the bench if you have one. The first draft lands in two to five minutes. Free holds five projects and one seat, with no card.
Eqlo writes the page, the copy, the form, and the image slots. Scroll once as a stranger would. Check the price, the date, and what happens after submit. If a second product appeared, cut it: "Remove the shop link, this page has one action." Each exchange creates a version you can restore. A page you will send is often the rest of a half hour, once the catch is visible.
Select the H1, the price, or the button, then write an instruction that applies to that element alone. "Change this button to Reserve a seat, and put the Friday deadline under the price" does not invent a second offer. You can also edit a sentence in place. Colors and type apply across the page when you set the graphic charter. Compare two versions if a line went too far.
Publish on a projet.eqlo.app subdomain, then send the link to yourself and open it on a phone. On Plus, at $19 a month with three seats, you add a path on a domain you already own, pass DNS, and receive an SSL certificate. The title, the meta description, and the heading tree leave in the first HTML. Images become WebP. Core Web Vitals are measured on every publish, and a regression raises an alert.
A page that finishes holds four blocks and no extra nav. Eqlo writes the reading order from the sentence you typed.
The first screen is the offer and who it is for. "A Saturday glaze workshop, $85, twelve seats, ends Friday" is a promise. A brand story is not. The H1 should still work if someone only reads that line. Eqlo writes a longer lead under it. You keep the line that already worked in a mail if you have one. Paste it. The generator should not invent a second offer beside yours.
Proof sits before the form. A named result, a short quote you have permission to show, a photo of the bench, a date. Three items are enough. Ten logos nobody can check are not proof. If you have no proof yet, say what happens after they submit: a seat held, a call on Tuesday, a sample in the post. Do not invent a customer name.
The catch belongs on the page, not in the confirmation mail. Who the offer is not for, what is not included, when it ends, how late a seat can be moved. A catch written plainly converts better than a catch found after the click. If the workshop is only for people who already throw, say that before the form.
One form, few fields. A name and an email, or a checkout, not both unless you are taking money now. The button names the action: Reserve a seat, Join the list, Book the call. Eqlo writes the form and the inbox for the requests. Every extra field is a place to stop. A full nav that links everywhere turns the page back into a homepage.
Three choices, made after the first URL is live, decide whether you learn anything from the afternoon.
Once the first page is live, ask for a second version that leads with the price, or with the date. Keep the same form. Each exchange creates a version you can restore, and you can compare two versions visually. Eqlo is not a full experiment platform. It is fast enough that two URLs you split by hand teach you which line people finish.
Count visits, form starts, and finishes. Google Analytics is on the integration list: you ask for it in one sentence, and the key is stored encrypted. A page with four hundred visits and six finishes is a sentence problem, not a color problem. If nobody finishes, change the promise or the catch, not the padding. Do not wait a month to read the first afternoon.
Marketing pages are pre-rendered at build time, so the words sit in the first HTML. Images become WebP, with sizes and alt text. Core Web Vitals are measured on every publish, and a regression raises an alert. That is the speed work Eqlo does. A heavy video you drop on the first screen is still your choice, and it can undo the measurement.
This is an illustrative scenario, not a real company. Suppose a studio in Portland wants twelve seats on a Saturday glaze workshop at $85, existing throwers only, offer ending Friday. The first draft arrives in a few minutes with a one-line H1, a proof block for a photo of the kiln, an objection line about skill level, and a form that asks for a name and an email. The maker then spends the rest of a half hour putting the real price in, cutting a shop link the generator added, and asking for a variant that leads with "twelve seats." Both versions stay in history. The page is published on a projet.eqlo.app subdomain the same afternoon, then moved to a path on an owned domain once Plus is on. Those timings are assumptions for that half hour, not results we measured.
These pages take over when the job is a full brochure, a shop, a campaign role, or the plans.
Long enough to make the catch visible and the next step obvious. For an $85 workshop, a few screens. For a $4,000 course, longer proof. Length is not a virtue. The first draft is two to five minutes either way.
You can run two URLs and send half the traffic each, or switch when one is clearly ahead. History keeps both versions. Eqlo is not a full experiment platform. Two pages is often cheaper than a tool you will not open.
A path on a domain you already own is usually better for trust. That needs Plus at $19. A projet.eqlo.app URL is enough to test the form the same afternoon. Redirect the path when the date dies.
Unpublish, or switch the form to a waitlist and change the H1. Do not leave a dead checkout up. That is how you train people to ignore the next one. A version restore brings the live page back if you need it.
Yes. You add pages in the chat. A landing page that grows a nav is a homepage. The repository stays yours. Automatic GitHub sync starts on Plus.
Five projects, one seat, no card. Plus is $19 a month when the path should sit on a domain you already own.