Going live — Findit HTML
Before you upload
Section titled “Before you upload”| Where | |
|---|---|
| Demo domain replaced by yours | every .html file, sitemap.xml, robots.txt — find https://findit-html-marcframe.vercel.app (Editing the site) |
Name, contact details, address (info@example.com, the phones and the address are placeholders) |
every page (header, footer, Contact page) |
| Titles and descriptions written for your business | each page’s <head> |
| Logo, icons and share image replaced | assets/images/logo.svg, icon.svg, apple-icon.png, opengraph-image.png (2400 × 1260; 1200 × 630 or larger) |
| Demo text, properties and placeholder images replaced | the pages, assets/images/ |
| Home page video replaced or removed | the <video> in index.html |
| Terms of Service and Privacy Policy replaced with your own | legal/*.html |
| Forms deliver to you | assets/js/config.js (Forms) |
| Style guide kept or deleted | style-guide.html |
| Stylesheet rebuilt if you changed the theme or used new classes | npm run build:css (Making it look like your brand) |
Leaving “Findit”, the sample address or the sample listings on a live site is the most common mistake — search the folder for “Findit” one last time. The legal texts are examples, not legal advice — have yours written or reviewed for your country.
What to upload
Section titled “What to upload”Everything except the tools:
| Upload | Leave out |
|---|---|
all .html files, property/, agent/, blog/, legal/, filter/, success/ |
node_modules/, src/, docs/ |
assets/ |
package.json, package-lock.json |
icon.svg, apple-icon.png, opengraph-image.png |
README.md, CHANGELOG.md, LICENSE.md |
sitemap.xml, robots.txt |
(Uploading the extra files does no harm, but there is no reason to publish them.)
Where to host
Section titled “Where to host”| Host | How |
|---|---|
| Netlify | Drag the folder onto Netlify Drop. Done — then add your domain. |
| Cloudflare Pages, Vercel | Upload the folder or connect a Git repository; no build command, output folder is the root. |
| GitHub Pages | Push the folder to a repository and enable Pages. |
| Shared hosting (cPanel, Plesk…) | Upload through the file manager or FTP into public_html (or www). |
No build command, no server software. Pages link to each other as about.html, so no server configuration is needed
either. Most hosts serve 404.html for unknown addresses automatically; on Apache add
ErrorDocument 404 /404.html to .htaccess.
Your domain
Section titled “Your domain”Add it in the host’s domain settings and point your DNS where they tell you (usually an A record or a CNAME). Turn
on HTTPS — every host above does it for free.
After it is live
Section titled “After it is live”- Check the pages. Click through every page on a phone and a laptop: menu, filters, the gallery on a property, the accordions, both tour and contact forms.
- Send yourself a submission from every form on the live site and reply to it.
- Verify the share card. Paste the URL of the home page and of a property into https://www.opengraph.xyz or a chat window and confirm the image and title.
- Tell Google. Add the site to Search Console, verify ownership and
submit
https://yourdomain.com/sitemap.xml. Bing has the same thing in Webmaster Tools. - Analytics, if you want it. Paste your snippet before
</head>in every page (find and replace on</head>does it at once), or use your host’s built-in analytics (Cloudflare Web Analytics, Plausible, Fathom) — none of them need a cookie banner. - Keep the listings current. Add and remove properties as described in Editing the site,
and keep
sitemap.xmlin step.
Performance and SEO
Section titled “Performance and SEO”The pages ship with what search engines look for: real HTML, one <h1> per page, a title and description for every
page, canonical links, sitemap.xml, robots.txt, share cards, lazy-loaded images with fixed dimensions and links in
the HTML to every page, including those behind a filter. Pages that would only list nothing are kept out of search
results. Keep the site fast by compressing the photos you add.