What QuQi Edge does to your site today, the two things it needs from you, the records to add at your DNS provider in the order that keeps the site up, and how to tell it worked.
QuQi Edge puts QuQi in front of your website. Visitors reach your site through QuQi’s edge, and your server stays exactly where it is and exactly as it is. In proxy only mode everything passes through untouched. Switch serving on and the title, description and schema you applied in the Page Optimizer are written into each page on the way through, on every request; everything else still passes through, and nothing is cached.
HIER STARTEN
You connect nothing of yours. There is no password, no token and no account to link: you add a few records at your DNS provider, and that is the whole connection. QuQi Edge is on Scale and Authority.
The two things it needs
A site hosted on a platform that itself answers through Cloudflare — Shopify, Cloudflare Pages, Workers — has no direct address to give, so it cannot connect for now. The drawer says so, naming the platform, before you type anything.
Set it up
1
Open Integrations
Make sure you are on the right website, then find QuQi Edge under Delivery and press Set up.
2
Read what QuQi found, then check the origin address
The hostname is already filled in. Under What QuQi found the drawer says what your DNS looks like today: whether the name answers directly, sits behind Cloudflare’s proxy, or points at a hosting platform; who runs your DNS; whether the bare domain redirects to www; the record’s TTL; and whether a CAA record would block the certificate. Where it can tell, the origin address is filled in for you. What happens next lists the steps to come, written for your setup.
3
Press Test
QuQi fetches the front page from your server at that address, as if it were a visitor to the hostname, and tells you what it answered. A server that answers for a different name, or not at all, shows here before anything is saved.
4
Save
QuQi checks the origin address is a public one and not a loop, fetches your front page from it exactly as the edge will, and refuses to connect if your server does not answer or answers an error. Then it prepares the hostname on the edge, and the drawer stays open on the records to add.
The steps, in this order
The drawer builds the list from your DNS as it is now, with your provider’s own field names, a copy button on every value, and a button that opens the provider’s page for the domain where QuQi recognises the provider. Each step reads Done once your DNS shows it, Later while it waits on an earlier one, and Check again re-reads your DNS. The order matters: the switch record comes last, because a site switched before its certificate exists shows visitors a security warning.
1
Add the TXT records
One lets Cloudflare issue the certificate your site will be served with; where a second one is listed, it proves the hostname is yours so it is active before anything moves. Each record reads seen in DNS once it is found. Nothing changes for visitors.
2
Add CAA records, only if the drawer lists them
A domain that already restricts which authorities may issue its certificates needs one more line each for pki.goog and letsencrypt.org, beside the ones it has. Without them the certificate never reads active, and the drawer says so before you wait for it.
3
Press Check again until the certificate reads active
It usually takes a few minutes after the TXT record is in place. The drawer’s status line says what to do next at every stage. Until then the switch step reads Later and shows no record to copy: a hostname switched before its certificate exists shows visitors a security warning, so the drawer keeps the value back on purpose.
4
Lower the record’s TTL
Listed when the record you are about to change has a TTL above 300 seconds, with the lowest your provider allows. Set it, wait that long, and the switch can be undone as quickly if it ever needs to be.
5
Add the switch record
For www.example.com, a CNAME named www pointing at edge.quqi.io; for a root domain, the record your provider uses to point a root at another name, named in its own words. The step lists what to remove first at the same name — the A or AAAA records that are there today, or the CNAME to change — since a name cannot carry both. It reads Done once the name resolves to the edge.
6
The other name
For a www site, the drawer checks that the bare domain sends visitors to www, and says how to set that redirect if it does not. For a root site, it checks that www follows the root, and gives the CNAME to add if www has a record of its own.
VORSICHT
Do not add the switch record before the certificate reads active. A site switched over without its certificate shows visitors a security warning until the certificate lands.
IF THE SWITCH STEP IS CLOSED
Where the switch step reads Not available yet, QuQi is still finishing the edge setup and the step is closed until it is done. Do not add the switch record by hand: your visitors would see an error page. The certificate you already have stays valid, and the card says when the switch opens.
Root domains
The drawer says which case yours is before you connect, in your provider’s words, and never suggests moving the site to www.
A plain CNAME cannot sit at the root of a domain, so example.com can point at QuQi only where your DNS provider can flatten that for you. Cloudflare DNS does so on every plan, and Namecheap, DNSimple, DNS Made Easy, Hostinger, Porkbun, Gandi, Name.com, Google Cloud DNS and Squarespace each have an ALIAS or ANAME record for it. GoDaddy, Amazon Route 53 and Hetzner cannot: for a root-domain site on one of those, the path is moving the domain’s DNS to Cloudflare’s free plan, which changes nothing else about the site. QuQi tells you this when you connect, and it never proposes a redirect to www instead.
After the switch
- The card starts in proxy only: every request passes through to your server untouched. Once QuQi has seen the edge answer for your site, the Mode section offers Serve optimized pages; from then on your applied title, description and schema appear on the live pages within about two minutes, and Back to proxy only undoes it just as fast.
- Every 15 minutes QuQi fetches a few pages both ways — through the edge and from your server — and compares them. The drawer’s Health line says when it last checked and what it found.
- QuQi’s own audits and the Page Optimizer always read your site as your server serves it, never the edge’s rewrite of it, so a score or a suggestion is about your pages and not about QuQi’s own work.
- Dry run does the same check for the front page on demand, and says in one sentence whether the edge answers the same as your server.
- Details on the card reopens the drawer at any time.
- Applying a suggestion in the Page Optimizer sends it to the edge on its own; nothing to publish, nothing to wait for beyond the two minutes.
- Edge traffic is not metered. Nothing about it counts against your plan.
Undoing it
Point the switch record back at your server first, wait out its TTL, and only then press Disconnect. Disconnecting removes the hostname and its certificate from the edge, so a record still pointing at QuQi at that moment would show visitors an error page. The card says this again before it lets you disconnect.
GUT ZU WISSEN
If your DNS provider later points the origin address somewhere it should not — a private address, or back at QuQi — the health check records it on the card and stops checking that side. Nothing is switched off on its own; the warning is yours to act on.