How do I SEO a Lovable website?

A practical checklist

Work through these roughly in order — most take one chat message each:

1. Custom domain — connect one and confirm HTTPS is active (Lovable does this automatically once verified).
2. Titles and descriptions — give every important page a unique <title> and meta description that describes what's actually on that page. See how do I change meta titles.
3. Open Graph and social image — so shared links look right on social platforms.
4. Alt text — every meaningful image needs descriptive alt text, both for SEO and accessibility.
5. Sitemap.xml and robots.txt — tell search engines what exists and what to skip.
6. Canonical URLs — avoid duplicate-content issues if the same content is reachable at more than one URL.
7. Schema markup — structured data (JSON-LD) helps Google understand your content type (article, product, FAQ, etc.).
8. Google Search Console — verify your domain and submit your sitemap so Google actually crawls it.

A prompt to kick this off

Review this app for SEO: check meta titles, descriptions, alt text on images, and Open Graph tags on each page, and tell me what's missing.

Newer Lovable projects can run a built-in SEO and AI-search review that checks many of these automatically and researches relevant keywords — ask Lovable to run one if it's available on your project.

Content still matters most

None of the technical items above compensate for thin or duplicate content. Each page should answer a specific, real question or serve a specific purpose — search engines reward genuinely useful pages over technically-perfect empty ones.

What usually goes wrong

• Doing the technical checklist but leaving every page with the same generic title ("Home", "App") — defeats the purpose.
• Adding a sitemap but never submitting it to Search Console, so Google doesn't know to look.
• Treating SEO as a one-off task rather than an ongoing habit as you add pages.

Related

• Is Lovable good for SEO
• Does Lovable automatically create a sitemap
• How do I connect Google Search Console

If SEO is business-critical and you don't have time to work through this yourself, a specialist at PromptSites.com can audit and fix it in your project directly.

A practical SEO order of work

Do these in sequence — each one is cheap and each unlocks the next.

1. One page per search intent. Separate routes for separate topics; anchors on one long page do not rank separately.
2. Titles and descriptions per page. Unique title under 60 characters leading with the phrase people search, description under 160 characters that reads like a result snippet.
3. One H1 per page matching the page's topic, with H2s for real sections.
4. Canonical URL on every page, absolute, matching your primary domain.
5. Open Graph and Twitter tags so shared links render with a title, description and image.
6. Structured data — Article, FAQPage, QAPage, Product or LocalBusiness depending on the page.
7. Sitemap and robots.txt listing every public route, submitted in Search Console.
8. Internal links from hub pages to detail pages using descriptive anchor text.
9. Speed — compressed images, lazy loading below the fold, no oversized hero files.
10. Content depth — answer the question completely, including the parts competitors skip.

Prompts that produce the tags correctly

For every public route, add a unique title, meta description, canonical URL, og:title, og:description, og:image and twitter:card. Use absolute URLs on my primary domain. Don't add metadata to the root layout that would override page-level tags.

Generate sitemap.xml from the actual route list plus all database-backed pages, and a robots.txt that allows crawling and points to the sitemap.

Ranking for long-tail phrases

Most traffic for a new site comes from specific questions, not head terms. Write the page title as the question a person types, answer it in the first paragraph in two sentences, then expand. Add the exact question as an H1 and use QAPage or FAQPage structured data so search engines and AI assistants can lift the answer.

Measuring instead of guessing

Connect Google Search Console, submit the sitemap, then watch impressions before positions — impressions rising means the pages are being considered, and improving the title and first paragraph is usually what converts those into clicks. Give new pages a few weeks before judging them.

Common Lovable-specific mistakes

• Metadata set once in the shared layout, so every page has the same title
• Relative canonical or og:url values on a custom domain
• Sitemap generated once by hand and never updated as pages are added
• Preview URL indexed instead of the live domain
• Content that answers in one line and stops — thin pages rarely hold a position