01
Rendering
Crawlers can only rank what they receive.
- Raw HTML against the rendered page
- TanStack Start or older React and Vite
- What Googlebot and AI crawlers each get
- Content that only appears after JavaScript
Lovable Sites That Rank
Your Lovable site looks great. Now make it rank.
I fix how your Lovable site renders, describes and links its pages, wire up forms that actually deliver leads, and build new pages and tools planned to be found.
Live check
fetches your site nowAI Visibility Checker
What the check covers
- robots.txt rules for 13 search and AI crawlers
- Content readable without JavaScript
- noindex tags and firewall challenge pages
- Title, description, canonical and language
- Organization and Person schema, sameAs links
- Sitemap, H1 and llms.txt
Free, no sign-up. Results in about 20 seconds; the fix for each problem unlocks with your email.
- Server rendering checked on every page
- Metadata, sitemap and schema done right
- Forms that reach your inbox
- Changes in your own GitHub repository
All pages
Checked for crawlers
5 days
Until your Lovable report
Your repo
Every change committed
1 person
Audits and builds
Your Lovable builder
Lovable sites built and fixed by someone who ships on Lovable.
Ashikur Rahman, SEO and AI Search Specialist
Much of my recent work is on Lovable: moving sites from WordPress to Lovable, fixing Lovable sites that Google ignored, and building lead tools. This site runs on Lovable and was built the same way.
Law training (LLB, LLM in International Law) means I check the platform's own documentation before I advise. Lovable's hosting rules, such as how it handles redirects and pre-rendering, decide what is possible, and I plan around them.
I work in your project's GitHub repository, so every change is visible, versioned and yours. I also run criticnest.com, itself on Lovable, where I publish search news and reviews of SEO tools.
- Works in your GitHub repository
- Every change committed, reviewable and synced back to your Lovable project.
- WordPress to Lovable moves
- Content, URLs and redirects carried over so rankings come with you.
- Server rendering and metadata
- Pages crawlers can read, with titles, canonicals and schema on every route.
- Lead capture that works
- Forms connected to a database and your inbox, tested end to end.
Check who you are hiring
Lovable, decoded
What your Lovable site is telling you.
Open your site's page source, search for it in Google and test your forms. Pick the symptom to see the usual cause on Lovable and the fix.
Pick what you see
- Needs a fix
- Check it
- Usually fine
Needs a fix
The site is live but not in Google
Seen with a site: search in Google, or in Search Console.
What it means
Often nobody has verified it in Search Console or submitted a sitemap, the pages have few links pointing to them, or an older project serves crawlers less than it seems.
What I do about it
Verify the site in Search Console, submit a clean sitemap, check the rendered page in URL Inspection and link the pages that matter.
Seeing this on your Lovable site?
Check it
View source shows an almost empty page
Seen with View Source (Ctrl+U) on your live site.
What it means
Older Lovable projects built on React and Vite send browsers an empty shell. Lovable serves pre-rendered copies only to verified search engines and social preview bots, so other crawlers, including many AI crawlers, may see nothing.
What I do about it
Confirm what Google sees with URL Inspection, then move the project to TanStack Start, Lovable's documented upgrade to server rendering.
Seeing this on your Lovable site?
Needs a fix
Every page has the same title and description
Seen on your live Lovable site, in its page source or in Search Console.
What it means
The project only sets metadata once, so every page shares the homepage title. Google then has to guess what each page is for.
What I do about it
Give every route its own title, description, canonical and social image, written for the search it should win.
Seeing this on your Lovable site?
Needs a fix
Your forms look fine, but leads never arrive
Seen when you send a test enquiry and nothing reaches your inbox.
What it means
Generated forms often show a success message without saving or sending anything, or the email service was never connected.
What I do about it
Connect the form to a database and an email service, add spam protection, and test it end to end on the live site.
Seeing this on your Lovable site?
Check it
Stats, reviews or tools are placeholders
Seen across your live pages.
What it means
AI-generated designs often include invented numbers, sample testimonials or tools that only pretend to work. Visitors and Google both lose trust, and fake reviews can break consumer law.
What I do about it
Replace each one with real content, a real tool, or nothing at all.
Seeing this on your Lovable site?
Check it
Made-up URLs show the homepage
Seen when you open a made-up address on your site.
What it means
Some older projects answer every unknown address with the homepage and a success code, which Google treats as a soft 404.
What I do about it
Return a real 404 page for addresses that do not exist; TanStack Start projects do this by default.
Seeing this on your Lovable site?
Needs a fix
The site is slow on mobile
Seen in PageSpeed Insights, mobile results.
What it means
Large images, heavy animation libraries and pages that build themselves in the browser all add up on a phone.
What I do about it
Resize and compress images, load heavy parts only where they are used, and let the server render the page.
Seeing this on your Lovable site?
Usually fine
The www address redirects with a 302
Seen when you open the www version of your domain.
What it means
Lovable's documentation says non-primary domains, www included, redirect to the primary domain with a 302, and that this cannot be changed.
What I do about it
Nothing to fix. I make sure your custom domain is set as the primary, so Google settles on the right address.
Lovable audit areas
Six things every Lovable site needs right.
A Lovable site can look finished and still be invisible. The audit checks what crawlers actually receive, and whether every page, form and claim does its job.
02
Metadata
Each page needs to say what it is for.
- Titles and descriptions on every route
- Canonical URLs
- Social preview images
- Real 404s for missing pages
03
Indexing setup
Google needs to find and trust the site.
- Search Console verification
- A sitemap with real dates
- robots.txt rules
- Primary domain settings
04
Content truth
Invented content costs trust, and sometimes more.
- Placeholder stats and numbers
- Sample or invented testimonials
- Tools that only pretend to work
- Leftover demo copy
05
Lead capture
Traffic is worth little if enquiries go nowhere.
- Where each form actually sends data
- Email delivery to your inbox
- Spam protection
- Events for tracking leads
06
Speed
Phones show every heavy image and library.
- Image sizes and formats
- Fonts and animation libraries
- Core Web Vitals on mobile
- What loads on every page
Lovable report
Your Lovable report and page plan.
Within 5 business days: what crawlers really receive, what is missing, and which pages your site should have.
- 01
Where the site stands
One page on how search engines see your Lovable site and what to do first.
- 02
A rendering check
What browsers, Googlebot and AI crawlers each receive from your key pages, side by side.
- 03
Metadata, forms and content findings
Missing metadata, broken forms and placeholder content, each with where it is and how to fix it.
- 04
Changes for your repository
Ranked by impact and effort, written as the exact changes to make.
- 05
A page plan
The pages your site should have for the searches you want, with titles and addresses.
Build sprint
Two weeks of fixes in your repository.
I commit the changes to your GitHub, you publish, and I check the live site on mobile and desktop.
Server-rendered pages
Older projects moved to TanStack Start where needed, with every page tested afterwards.
Metadata on every route
Titles, descriptions, canonicals and social images written for each page.
Sitemap, robots.txt and schema
A sitemap with real dates, clear crawler rules and markup that matches each page.
Working lead forms
Forms saved to a database and emailed to you, with spam protection, tested end to end.
Real content in place of placeholders
Invented stats, sample reviews and fake tools replaced with real ones, or removed.
Launch checks
Search Console set up, sitemap submitted, and the live site checked on mobile and desktop.
From access to launch
From project access to a site that ranks, in four steps.
You see every change as a commit, and nothing goes live until you publish it.
- 01
Access
Day one
You connect the project to GitHub or invite me to it, and tell me the searches and enquiries you want.
- 02
Diagnose
Days one to four
I check what each crawler receives, every route's metadata, your forms and any placeholder content.
- 03
Report
Up to 5 business days
The Lovable report and page plan arrive, and I answer your questions about them for seven days.
- 04
Build and launch
Optional, 2 weeks
I make the changes in your repository, you publish, and I check the live site on mobile and desktop.
Lovable pricing
What Lovable SEO work costs.
The same published prices as every service, here covering rendering, metadata, forms and new pages.
Audit
$149
fixed price / 5 business days
See your Lovable site the way crawlers do.
- Rendering checked page by page
- Metadata reviewed on every route
- Forms tested end to end
- Placeholder content flagged
- A week of follow-up support
You end up with: A Lovable report with a rendering check and a page plan.
2-week sprint
Recommended$599
per service / 2 weeks
Fix it in your repository, ready to publish.
- Starts from the audit's change list
- Server rendering where needed
- Metadata, sitemap and schema
- Working lead forms
- Live checks after you publish
You end up with: Changes committed to your GitHub and a site crawlers can read.
Monthly
$399/mo
per month, from / ongoing, cancel monthly
Keep adding pages that bring in work.
- New pages or tools each month
- Search Console checked monthly
- Metadata kept right as pages change
- A monthly results summary
- Month by month, cancel before renewal
You end up with: A Lovable site that grows every month, with the results tracked.
Is this you?
Built for Lovable sites that should be bringing in work.
If one of these sounds like you, the audit shows what is holding your site back, and the sprint fixes it in your repository.
A strong fit if
- Your Lovable site is live but not in Google
- You built it yourself and want a second pair of eyes
- Your forms look fine but leads never arrive
- You want to move from WordPress to Lovable
- You want a lead-generation tool, not just pages
Built in your repository
Every change committed to your GitHub, so you can see, review or roll back anything.
Crawler view before and after
What crawlers receive before and after, and live checks on mobile and desktop.
Inside Lovable's documented setup
Server rendering and real content, the way Lovable documents it.
Yours from day one
Your code, your Lovable account and your domain. No contract.
My promise
I make your Lovable site readable to crawlers, properly described on every page and ready to capture leads, and I show you what changed. Rankings are Google's decision, and Google rewards pages it can read, understand and trust. That is exactly what I build.
When this is not the right fit
Not sure? Send the project link and I will tell you plainly.
Large web apps
Products with accounts, payments and dashboards are scoped separately after the audit.
No access to the project
Changes need the GitHub repository or an invite to the Lovable project.
Pages in bulk
Mass-generated pages and invented stats cost trust and rankings. I build fewer, real pages.
Lovable questions
Lovable SEO, answered.
What builders ask before giving someone access to their project.
Is Lovable good for SEO?
Yes, when it is set up properly. Projects created since 13 May 2026 use TanStack Start, which renders pages on the server so search engines and AI crawlers read them easily. Older projects, missing metadata and broken forms are where problems start, and all of them can be fixed.
Why does my site look empty in View Source?
Older Lovable projects built on React and Vite send browsers an empty shell and fill it with JavaScript. Lovable serves pre-rendered copies to verified search engines and social preview bots, so Google may see more than you do, but other crawlers may not. URL Inspection in Search Console shows exactly what Google receives.
Should I move my project to TanStack Start?
If it is an older React and Vite project and search matters to you, usually yes. It is Lovable's documented upgrade, it can be reverted from version history, and the live site only changes when you publish. Libraries that only work in the browser can break, so I test every page before you publish.
Can you move my WordPress site to Lovable without losing rankings?
Yes, with a URL map. Every old address is either kept or redirected to its new page, content and metadata carry over, and I crawl the site after launch to confirm nothing was lost.
Why does www redirect with a 302 instead of a 301?
Lovable's documentation says non-primary domains redirect to the primary with a 302 and that this cannot be changed. It is not something to fix. What matters is setting your custom domain as the primary, which I check.
Can you improve a Lovable project I already have?
Yes. I work in the project's GitHub repository, fix what is there and keep your design unless you want it changed.
What can be built in a 2-week sprint?
A focused marketing site or a single tool, such as a calculator, checker or set of directory pages. Bigger products are scoped separately after the audit.
Do I keep ownership of the code?
Yes. The code lives in your GitHub repository and your Lovable account, and every change is a commit you can see.
Also for Lovable sites
Useful next to a Lovable build.
Technical SEO
Once the pages render, technical SEO gets them indexed and ranking.
Generative Engine Optimization
Server-rendered pages are the first step to being cited in AI answers.
WordPress Speed and SEO Repair
Moving from WordPress? The old site's URLs and speed issues are checked first.
Send your project
Send your Lovable link. See what crawlers see.
Tell me what you want the site to do, from more enquiries to a new tool. I will check how crawlers see it before I reply and tell you where I would start.
- 1I check what crawlers receive from your site before I reply.
- 2You get my answer within one working day.
- 3Any paid work starts with a written scope and price.
Start with your project link
Just email, no sales call.