AI builders get you from idea to live site in an afternoon. They also leave behind a recognisable set of loose ends that make a new site look unfinished to Google, to AI assistants and to the first people who share your link. Go through this list before you post your launch.
Template leftovers
- The page title: "Vite + React + TS", "Create Next App" or "Lovable App" in the browser tab is the most common one. Replace it with what your product does.
- Placeholder text: search your pages for "lorem ipsum", "Your Company" and "example.com".
- The favicon: the default Vite or React logo in the tab looks like a demo, not a product.
Links and redirects
- localhost links: links or images pointing to
localhost:3000work on your machine and break for everyone else. - http and www: make sure
http://redirects tohttps://, and that www and non-www end up on one version. - Real 404s: many single-page apps return "200 OK" for every URL, so Google indexes endless copies of your homepage. A missing page should return a 404 status.
Sharing previews
When you post your launch on X, LinkedIn or WhatsApp, the preview comes from Open Graph tags. Add og:title, og:description and a 1200×630 og:image. Without them, your big announcement shows a bare link.
Security basics
- Exposed files: check that
/.envand/.git/configreturn 404. If they load, rotate every key in them immediately. - HTTPS everywhere: no images or scripts loaded over plain http.
- Security headers: at least
X-Content-Type-Options, a frame policy and a referrer policy.
Search basics
- One H1 per page, a unique title and meta description on each page.
- A
sitemap.xml, listed in robots.txt and submitted in Google Search Console. - No stray
noindexfrom your staging environment.
Fix it with the same AI that built it
RankHoot checks every item on this list in one scan and gives you a ready-made prompt for each problem. Paste it into the tool you built the site with and let it make the change.