Understanding Your Lovalingo Dashboard

Reading time: 4 minutes

Your Lovalingo dashboard shows numbers, badges, and progress bars. This guide explains what they mean and when to take action.

📊 Overview Page: The Essentials

Pages Found: "250 pages"

What it means: Lovalingo discovered 250 URLs on your site.

Expected numbers:

• Small site: 10-50 pages

• E-commerce: 100-500 pages

• Content site: 500+ pages

✅ Good: Number matches your expectations

⚠️ Problem: You have 10 pages but see 500+

Why this happens: Dynamic URLs creating duplicates (/user-123, /user-456...)

Fix it:

1. Go to Advanced > Page Blocking

2. Add pattern: /dashboard* or /*/*/*/*/*

3. Click Add

Pages Crawled: "37 pages crawled"

What it means: Lovalingo scanned 37 pages for content.

Timeline:

• First hour: 10-20% crawled

• First 6 hours: 40-60% crawled

• First 24 hours: 80-100% crawled

✅ Good: Number increases over time

⚠️ Problem: Still at 5 pages after 48 hours

Fix it:

1. Visit every page on your live site

2. Click all menus and buttons

3. Wait 30 minutes

4. Check dashboard again

Translation Progress: "98%"

What it means: 98% of text is translated.

Quality guide:

Stuck at 98%?

1. Go to Pages tab

2. Find languages showing <100%

3. Click dropdown to see missing strings

4. Visit those specific pages

5. Wait 30 minutes

Still stuck? Click "Reset and Rerun this Locale" → Wait 1 hour

Plan Limit: "Plan limit reached (3/3)"

What it means: You're using all language slots for your plan.

Plans:

• Start-up: 3 languages (1 free)

• Global: Unlimited

This is informational only - nothing breaks. Upgrade when you want more languages.

🚦 Status Indicators

✅ Status: Ready (Green)

Everything works! You're live and translations are active.

Do nothing - enjoy your multilingual site.

⏳ Status: Pending (Yellow)

Setup in progress.

Normal: First 10-30 minutes after installation

Take action if: Still pending after 30 minutes

1. Go to Setup tab

2. Check Verification section

3. Click Verify now

❌ Status: Error (Red)

Something's wrong.

Fix it immediately:

Step 1: Go to Setup > Verification

• Green "OK" badge? → Issue elsewhere

• No green badge? → See Troubleshooting Guide

Step 2: Check your site loads at https://yourdomain.com

Step 3: Verify manifest exists at https://yourdomain.com/.well-known/lovalingo.json

Still broken? Contact support with:

• Your project URL

• Screenshot of dashboard

• When error appeared

📄 Pages Tab: Understanding Coverage

Click Pages in sidebar. Here's what you see:

Path Column

See /fr/fr/fr/fr? This is usually fine, but if it bothers you:

1. Advanced > Page Blocking

2. Add: /*/*/*/*

3. Blocks excessive nesting

Strings Column

"74" next to homepage = 74 text elements found

Expected counts:

• Homepage: 50-150 strings

• Product page: 40-100 strings

• Blog post: 100-300 strings

Suspiciously low? (e.g., 3 strings on rich page)

• Content loads via JavaScript

• Text is in images

• Visit page and interact with everything

Coverage Column (Most Important!)

DE: 100% ✅ All strings translated
FR: 98% ⚠️  2 strings missing
ZH: 0% ❌  Not crawled yet

What to do:

Click dropdown to see exact missing strings:

French (FR): 98% (72/74)
Missing:
- "Add to cart" button
- "39% response" text

💬 Translations Tab: Quality Check

Click Translations to review individual strings.

What you see:

Source (EN): 39% response rate
German (DE): 39% Antwortquote
French (FR): Taux de réponse de 39%

Fixing bad translations

When to override:

• Brand name was translated

• Technical term is wrong

• Tone doesn't match

How to fix:

1. Click on translated text

2. Edit in popup

3. Click Save

4. Live in 5 minutes

Better option: Use Glossary tab to create rules:

• "CloudSync" → Always keep as "CloudSync"

• "API" → Never translate

🔍 SEO Tab: Get Found on Google

Enable Lovalingo SEO signals (Toggle)

Turn ON when:

• Ready for public launch

• Want Google to find translated pages

What it does:

• Adds metadata translations

• Generates /sitemap.xml

• Injects hreflang tags

Sitemap Setup

Step-by-step:

1. Toggle SEO signals ON

2. Click Copy prompt

3. Run in your dev tool (Lovable/Cursor)

4. Deploy your site

5. Wait 5 minutes

6. Test: Visit https://yourdomain.com/sitemap.xml

7. Click Mark it as done

Success: Green "SEO installed" badge

Failed?

• Re-run prompt

• Check build logs

• Deploy again

Noindex Pages

Add paths to exclude from sitemap:

• /dashboard* - User pages

• /auth* - Login pages

• /admin* - Admin panel

How:

1. Type path

2. Select exact or prefix

3. Click Add

🎯 Common Issues (Quick Fixes)

"Pages found keeps increasing"

Cause: Dynamic routes
Fix: Use Page Blocking to exclude patterns

"100% translated but text still in English"

Causes:

• Text is in an image (can't translate)

• Text loads via AJAX (after page render)

• Text in modal/dropdown (trigger manually)

Fix: Visit page, interact with everything, wait 30 min

"Only 10 pages crawled out of 250"

Causes:

• Pages not linked in navigation

• Pages require login

Fix:

• Navigate entire site manually

• Submit sitemap in SEO tab

"Stuck at 98% coverage"

Reality check: 97-100% is launch-ready

Only obsess over 100% for:

• E-commerce checkout

• Legal pages

• Critical user flows

For marketing sites: 98% is perfectly fine

🚨 Quick Decision Guide

RED = Fix Now

• ❌ Status: Error

• 🚨 Coverage <50% after 48h

• 🚨 Pages found = 0 after 1h

YELLOW = Monitor

• ⚠️ Plan limit reached (upgrade when ready)

• ⚠️ Coverage 80-95% (acceptable)

• ⚠️ Pages found > expected (use blocking)

GREEN = Launch!

• ✅ Status: Ready

• ✅ Coverage 95-100%

• ✅ SEO installed

✅ Ready to Launch Checklist

Your site is ready when:

• Status badge is green

• Translation progress: 95%+

• Key pages show 100% coverage (homepage, about, main products)

• Language switcher works on live site

• /sitemap.xml loads correctly

• SEO tab shows "SEO installed" badge

Everything else is optional polish.

📚 Next Steps

1. Dashboard green? → Set up SEO (see SEO Setup Guide)

2. First 48 hours? → See 48-Hour Checklist

3. Need help? → Click Help in bottom-left

Questions? Contact support with your project URL and screenshots.