15 things to check before you send a website link (30 seconds each)
Last updated: 2026-11-12
Contents · 7
- 1. Open it on your phone first (checks 1–3)
- 2. Check that everything you tap really opens (checks 4–6)
- 3. Decide what it looks like when shared (checks 7–9)
- 4. Unknown addresses, refresh, secret keys, search (checks 10–13)
- 5. Last: secure connection and a version to go back to (checks 14–15)
- Frequently asked questions
- Read next
Short answer: before you send the link, run through 15 checks in this order: phone view, whether links and images really open, the share preview, then unknown addresses, search and security. Each one below has a 30-second way to check and the place to fix it, so save this page and use it every time you publish.
At a glance
- Time needed
- About 10 min
- Plan required
- Free plan
- Coding knowledge
- None
- Where to do it
- Editor
Step by step
- 1
Open it on your phone first (checks 1–3)
The phone view is what breaks most often. Opening the published address on a real phone is the fastest check, and you can do it with the QR code on the “Published” screen (“Open on your phone”) or the QR code under Settings > Share. Fixes go in index.html in the editor's “Files” tab. After editing, press Publish so visitors see the change.
Checks 1–3 · On your phone1. Fits a phone screen 30-second check: open it on a phone and see whether the text is tiny or the page slides sideways / Fix: add <meta name="viewport" content="width=device-width, initial-scale=1"> inside <head>2. Text and button size 30-second check: tap every button and link with your thumb; neighbours getting hit, or text you squint at, is a fail / Fix: ask the AI for body text of at least 16px, buttons about 44px tall and a gap between buttons3. Open it on a real phone 30-second check: point the phone camera at the QR code on the “Published” screen or under Settings > Share / Fix: if only the phone looks wrong, go back to checks 1 and 2, then check file paths (check 5) - 2
Check that everything you tap really opens (checks 4–6)
Links and images that work on your own computer but break once uploaded are the most common surprise. Open the editor's “Files” tab, read the uploaded file names, and match them letter by letter against the names your page asks for. Names with spaces or brackets can't be uploaded, and capital letters must match too.
Checks 4–6 · Links and files4. Where links and buttons go 30-second check: tap every button and link once on your phone / Fix: replace links that are just “#” and paths from your own computer (file:///…) with real addresses; write phone numbers as tel: and email as mailto:5. Image, CSS and JS paths 30-second check: open the published address and look for empty image boxes / Fix: in the “Files” tab confirm the file exists and matches the name in the page, capitals included; if not, use the + button, then “Upload files” (a page you pasted in carries no images with it)6. Contact details, dates, addresses 30-second check: read each phone number, email, date and opening hour out loud, one character at a time / Fix: edit in the “Files” tab and press Publish; tap the phone number to see that it really dials - 3
Decide what it looks like when shared (checks 7–9)
Send a link in a chat and a card with a title, description and image appears. Set the description and image under Settings > Site settings > Search & sharing, in “Share card”; the title comes from your page's <title> first. Changes there apply without publishing, except an image or tab icon file you just uploaded.
Checks 7–9 · Search & sharing7. Title and one-line description 30-second check: look at “This is how your link looks when shared” in settings / Fix: change <title> in index.html for the title and the “One-line description” field for the description (the “Title in search results” field is used only when the page has no title)8. Link preview image 30-second check: see whether a picture shows in that same preview / Fix: “Link preview image” > “Upload new” (1200×630 recommended), then press Publish9. Browser tab icon 30-second check: open the published address and look for an icon on the tab / Fix: Site > “More” > “Browser tab icon”, upload one, then press Publish - 4
Unknown addresses, refresh, secret keys, search (checks 10–13)
Decide ahead what happens when a visitor mistypes an address, refreshes, or finds you in search. These settings are in Settings > Site settings under “Site” and “Search & sharing”; they save by themselves and apply without publishing. A key written into your code is something no setting can hide, so you have to look for it yourself.
Checks 10–13 · Site settings10. Page for unknown addresses 30-second check: add random letters to the end of your address and open it / Fix: make a “New page” in the “Files” tab for a not-found message, then pick it under “Page to show for unknown addresses” in Site settings > Site11. Refresh still works 30-second check: if the site has several app screens, refresh on an inner screen / Fix: if you get a 404, turn on “Open the main page for unknown addresses (for app-style sites)” under Site > “More” (keep it off for an ordinary page)12. Secret keys in the code 30-second check: in the code editor, file by file, press Ctrl/⌘+F and search for key, token, secret and password / Fix: delete any you find; if it was already live, revoke it where it was issued and get a new one. The safety scan at publish looks for malware, not for keys13. Show up in search or not 30-second check: look at the “Search” On/Off choice and the “Create a page list for search engines automatically” switch / Fix: choose Off for private events and drafts; that only hides it from search, so anyone with the link can still open it. To really block it, use Page lock (Plus and up) - 5
Last: secure connection and a version to go back to (checks 14–15)
Two last looks before you send. The secure connection (HTTPS) is automatic, but if your code loads something over http://, browsers warn or block it. A version to return to is saved each time you publish, so you can undo a bad edit in a few clicks.
Checks 14–15 · Last look14. Secure connection (HTTPS) 30-second check: the address opens with https:// and the browser shows no security warning / Fix: both the default address and a connected domain are automatic; change images, scripts and fonts written as http:// in your code to https://15. A version to go back to 30-second check: open Versions in the editor and look for the row marked “Live now” / Fix: if you break something, “Review” an earlier version, press “Restore this version”, then Publish (saving versions yourself starts with Plus)
Frequently asked questions
Which of these breaks first?
The phone view (checks 1–3) and file paths (check 5). A page built on a computer easily looks tiny or slides sideways on a phone, and images or CSS that exist on your computer but were never uploaded show up as empty boxes. If you're short on time, check just those two on a real phone and then send.
I changed the title, description or image but the chat preview didn't change.
The page's own <title> is used first, and the description in settings beats the page's. An image counts once you upload it and press Publish. If it still looks old, the messaging app has probably cached the preview. Services differ, but sending the link with ?v=2 added to the end often makes it read the page fresh.
Does turning off Search hide the site completely?
No. It asks search engines not to list the site, so it only disappears from search; anyone who has the link can still open it. To really keep people out, use Page lock, which starts with Plus.
Can an AI run this checklist for me?
The code part, yes. Paste your HTML and ask: “Check the mobile viewport meta tag, button sizes, empty links that are just #, image and CSS paths for capital letters and spaces, anything loaded over http://, and any key or token written in the code, then give me the fixed code.” Opening it on a phone and the share preview you still have to look at yourself.
Can I fix things after publishing? Is one check enough?
Yes, fix away. Edit in the editor and press Publish: the address stays the same. After a big change run through this list again, and if an edit goes wrong, roll back from Versions.
Read next
- Put an HTML file you already have on a real address Step-by-step guide to putting an existing HTML file online at your own address, free, with no server, GitHub, or hosting account (English)
- SPA gives a 404 on refresh? One setting fixes it How to fix 404 on refresh for React and Vue single-page apps on static hosting, using the SPA setting and how it interacts with the 404 page (English)
- Undo a publish: roll your site back to an earlier version How to roll back a published website to an earlier version: review, restore, undo the restore, and what free and Plus keep (English)
- How to connect your own domain to your site Step-by-step guide to connect your own domain to a published HTML site: enter the address, add the CNAME and TXT values at your domain provider, wait for Connected, HTTPS automatic (from Plus)
Trying it is faster than reading about it — paste your HTML and publish it in a minute.