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 URLPaste a public address. Eqlo reads what a stranger can already fetch and drafts a new tree from those pages. You keep the URLs that earn. You drop the ones that never had a job. This is a starting move, not a promise that every pixel survives.
You already have pages people know
A new services tree invents /about-us while /about still ranks. Starting from the live URL makes the old sitemap visible before you write a sentence. The redesign guide is the longer argument about 301s. This page is the first hour: get a draft that knows the current tree.
The current site is a shell
If view-source is empty, the import will still see what the first HTML holds: often a title and not much else. That is useful. It tells you the rebuild is also an indexation job. Run the index-check tool on the same address before you decide the old site is "fine".
You only wanted a moodboard
Import is not a pixel-perfect copy. It is a reading of public pages so the first Eqlo tree is not generic. If you need a clickable argument with no migration, use prototyping and say so in the first line.
The brief was the live URL, not a mood sentence. Eqlo listed Home, Team, Fees, and a contact form that still pointed at a personal mailbox. The walkthrough kept /fees and /team, dropped a blog with three posts from 2019, and put a real intake sentence on Contact. No revenue number is attached. The useful output was a tree that already knew the addresses.
A first tree that remembers the live site. Not a clone, not a ranking guarantee.
The address must be fetchable without a login. A tool behind a password is the wrong door. Internal tools start from the loop you already run, not from a URL scrape.
Keep, merge, retire. Write the map before you publish. The redesign page is the checklist for redirects. Import is how the draft begins with names you already use.
The first sentences will still be a draft. Your prices, your hours, your town. Import saves you from inventing the IA again. It does not publish for you.
Three doors. They are not the same Tuesday.
You have a live site and you want the first Eqlo tree to know it. This page. Then you correct in English.
You already rank and the look is tired. Read that guide before you publish. Import can feed the draft. The 301s are still your job.
You are new, or the old URL should die. Use the website builder or a template. Do not import a competitor and call it yours.
I wanted the live tree in the draft, not a generic five-page salon. The useful hour was marking /fees as keep before anyone picked a typeface.
It reads public pages to propose a tree and a draft. It is not a pixel-perfect clone and it is not a licence to lift someone else's photos. Use your own files before you share the preview.
Do not. A public URL is still someone else's work. This tool is for an address you are allowed to replace. Scraping a competitor into Eqlo is not a brief we will help you finish.
The draft will be thin, which is the point. Run the index-check tool. If the first response has no H1, the rebuild should put words in the first HTML, not only a new coat.
No. Index-check reports title, H1s, JSON-LD and word count on a fetch. Import uses a URL as the start of a project. You can run both on the same address.
Five free projects is the plan once seats open. The redesign guide is the companion if those URLs already earn.