An SEO checklist for sites built with Lovable
Lovable's newer projects render on the server, so your pages arrive as real HTML that crawlers can read. That helps — but indexing and ranking still depend on what you configure and publish. This checklist separates three kinds of evidence so you always know what you actually verified: source configured (what's in your project), public page observed (what the live URL returns), and Google evidence (what Search Console reports).
Page metadata
Each page has a unique, factual title and description
Set them per route with the head API. Titles should name the page's topic; descriptions should summarise what the visitor gets. Avoid repeating the site name as the whole title.
Evidence: view the published page source and confirm the tags — that's "public page observed".
Canonical URLs point at your preferred public address
Each indexable page should carry a canonical link to its own URL on your public domain. A canonical is a signal: Google may still choose a different URL if it disagrees.
Social preview tags match the page
og:title, og:description and og:image control how links look when shared on platforms that honor them. They don't influence Google rankings.
Content crawlers can read
Useful content, headings and links in the HTML
Google can render JavaScript, but server-rendered content is visible immediately and doesn't depend on rendering. Keep each page's main content, one clear H1 and real links to your other pages in the HTML.
Reference: Google on JavaScript SEO.
A sitemap that lists your public pages
A sitemap helps Google discover pages. Submitting one in Search Console is a discovery aid — it does not guarantee indexing.
robots.txt allows crawling; noindex only where intended
robots.txt controls crawling; noindex controls indexing. A page blocked in robots.txt can't be crawled, so Google may never see a noindex tag on it. Keep public pages crawlable and use noindex for private or utility pages. Note that noindex is indexing hygiene, not security or access control — a noindex page is still reachable by anyone with the link.
Publishing and verification
Publish before checking the live site
The live URL serves the last published build. Metadata edits only reach it on the next publish — check the published page, not the editor preview, when verifying.
Verify your site in Google Search Console
Verification proves ownership and unlocks indexing and performance reports. It does not make Google index anything by itself. The "Request indexing" button can ask Google to look sooner, but it is optional and guarantees nothing.
References: Lovable SEO docs and Google's SEO starter guide.
Judge by Search Console data, not by the scanner
A static HTML check observes what one fetch returned — it is not proof of what Googlebot saw, whether a page is indexed, or how it ranks. For actual indexing evidence, use Search Console's reports; ordinary page analytics only show visits, not whether Google indexed the page.
Structured data expectations
Google removed FAQ rich results (June 2026 updates), so adding FAQPage markup no longer earns a special display — write helpful Q&A for readers, not for rich results. An llms.txt file is not a Google requirement. Google Search updates.
Check a live page
LaunchForge scans the static HTML of an accessible public HTTPS page and reports up to 12 potential on-page checks — only those the returned evidence permits — with observed evidence for each.