If your Lovable site is missing from Google, start with one published page. Open the exact URL while signed out, then inspect it in Google Search Console if you have access. A page that fails to load, a page that Google has yet to index, and an indexed page that rarely appears in searches each call for a different next step.
The checklist below works on your own site. The four examples are hypothetical and show how to interpret common findings. Lovable and Google documentation was checked on November 10, 2026.
Where does the page stop?
Pick one page that a customer should be able to find, such as a service page. Save its full address, including the hostname and path. A working homepage tells you little about whether a specific service page is available to Google.
| Stage | Question to answer |
|---|---|
| Publication | Does the intended page open from a signed-out browser? |
| Discovery and crawling | Can Google learn about the URL from a link or sitemap and fetch its content? |
| Indexing | Does Google include this page in its index, and which address did it choose for it? |
| Visibility | Does the indexed page appear for relevant searches, and do people click it? |
Google discovers URLs, fetches pages, processes their content for possible inclusion in its index, and selects results when someone searches. A page can pass one stage and still need work at the next. Check in that order so you spend time on the first issue you can substantiate. How Google Search works
Confirm where the site is hosted
If you published through Lovable, check the address that visitors actually use. Publishing creates a live snapshot. When a fix appears in the editor, publish the updated version and check the visitor's address again. Check which address is primary if you use both a Lovable address and your own domain. Lovable documents that workspace-branded addresses of the form app.workspace.lovable.app are excluded from search indexing. Lovable publishing, Lovable SEO documentation
The framework and host determine what HTML a visitor or crawler receives.
| Published setup | What to verify |
|---|---|
| TanStack Start on Lovable | Lovable documents server-side rendering (SSR). The server prepares the page HTML for visitors and crawlers. Check the specific route and whether its important content is present. |
| Older React and Vite project on Lovable | On public deployments, Lovable pre-renders pages on demand for verified crawlers. A normal browser or scanner can receive the JavaScript app first. Check the tested page in Search Console where available, especially if important content loads later. |
| Code deployed to another host | Confirm the framework and what that deployment serves. The external deployment determines whether it returns rendered HTML. Use the final public URL for every check. |
If the stack is unclear, check the project or ask whoever manages the deployment. Let the evidence from the live URL determine the next step. Lovable's rendering and hosting notes
Run five checks on the public URL
1. Open the page while signed out
Use a private browser window. Confirm that you land on the intended page and can read its main content. Record the final address and any redirect. A redirect from an old address to the equivalent new page can be intentional. A redirect to sign-in, or a missing service page that silently lands on the homepage, points to a different problem.
For a closer look, open the browser's developer tools, choose Network, and reload. Select the document request and check its status and response headers. A 200 is a successful response. Read the page as well, since an app can return 200 and display an error or the wrong content. If the public route fails, check the publishing or hosting setup before changing its SEO settings. Keep pages meant for staff or signed-in users behind their intended access controls. Google's technical requirements
2. Check crawl access and indexing directives
Open /robots.txt on the same hostname. Look for a rule that applies to the crawler and path you care about. A Disallow rule governs what the crawler may fetch. Use the specific path when checking it, since a rule for a private section can be entirely appropriate.
In the developer tools, search the Elements or Inspector panel for noindex in the page's robots meta tags. Also look for it in the document response's X-Robots-Tag header under Network. Either can tell Google to exclude the page from its index. Google must be able to fetch the page to read that instruction. If the browser response and Google's reported result differ, use the live inspection to see what Google's test can fetch now. Google's noindex guidance
3. Read the title, description, and main content
Read the page as a first-time visitor. The browser tab title, main heading, and opening text should identify the page's subject. Check for a relevant meta description and readable text that explains the offer or answers the question. A generic title shared by every route is a reason to inspect the page template and the actual deployment.
Check the content after the browser finishes loading. If it appears only after an interaction, such as clicking a tab that fetches the service details, verify whether Google's rendered view contains the important text. Treat a normal browser render as a check of the visitor experience. Use the available Google test to investigate what the inspection tool receives. Google's JavaScript SEO guide
4. Confirm the preferred address
Search the page's <head> in the inspector for a canonical link (rel="canonical"). It signals the preferred address when the same or similar page has several URLs. Compare that address with the final address in your browser and with the URL you want customers to find.
For example, a tracking URL can legitimately declare the clean version as canonical. A service page that declares an unrelated homepage deserves closer review. Where you have Search Console access, compare your declared canonical with the one Google selected in its index data. Google makes its own selection using signals including redirects, canonical links, and sitemap entries. Keep those signals consistent once you know the intended address. Google's canonical URL guidance
5. Check how the page can be discovered
Find a normal link to the page from another public page, such as the services list. Follow it while signed out. Then check the site's sitemap, if one exists. Its location may be listed in robots.txt. Many sites use /sitemap.xml. Open the actual sitemap and look for the preferred URL. If it lists several child sitemaps, check the one for that page type.
Lovable can flag a missing or stale sitemap. If you use one, check that it lists your preferred public addresses and reflects what you have published. An internal link and a sitemap entry give Google ways to find the page. Indexing remains a separate decision. Google's sitemap overview
Use the Lovable review and Search Console for different questions
Use Lovable to find project issues
In the Lovable editor, the current documentation places the SEO & AI tab under More → Analytics. Open the SEO and AI search review and use Scan project or Scan again when offered. The review can flag issues such as missing metadata, inconsistent canonicals, and sitemap or crawl problems. A publicly published site gets additional checks. Use the finding for the correct project and live address, and check when the review last ran if you have just changed the site. Lovable's SEO and AI search review
Work through one finding at a time. If a scan flags a crawl block, read the rule for the affected route and decide whether it is intentional. If you change it, check the published response and run the relevant check again. This connects a project finding to an observable change on the public page.
Use Search Console to check the exact URL
Open a verified Search Console property that includes the full address. Paste the URL you want Google to use into URL Inspection. If you are investigating a redirect, keep a record of both addresses and inspect the destination separately. Google's URL Inspection help
| View | What you can learn |
|---|---|
| Google Index, the initial inspection result | Google's recorded status. Review the indexing reason, last crawl date, and Google-selected canonical where shown. These fields describe the information Google already has. |
| Test live URL | Whether Google's inspection tool can fetch and analyze the current page for certain indexing conditions. Review the tested page details and rendered view when available. A passing test leaves the indexing decision open. |
For a change made today, record the date before comparing the two views. The live test may show a fixed response while the indexed information still reflects an earlier crawl. If you only have the public URL, record the results of the public checks and mark the Google index status as unknown until you can see the inspection result.
If an important new page is ready, or you corrected a specific problem and confirmed the live result, an owner or full user of the property can use Request indexing where appropriate. Use one request for the ready URL and recheck after Google has had time to process it. Google gives a range of days to weeks for crawling and decides whether to include the page. Google's recrawl guidance
Four findings and what to do next
These situations use studio.example, a fictional workshop. Each starts with an observation you could record for your own page.
| What you find | Next action |
|---|---|
| The page is unavailable or a rule blocks access or indexing unexpectedly | Confirm which response or rule applies to that route. Correct the unintended condition and retest the public page. |
| The URL redirects or Google has selected an unexpected canonical | Compare the final, declared, and selected addresses. Decide which page should represent the content and align conflicting signals. |
| The live test passes but the URL is absent from the index | Read the recorded reason and crawl date where shown. Check discovery and the page itself before choosing a fix, a recrawl request, or a later check. |
| The URL is indexed and has few impressions | Review the page, date range, and query data in Search Console. Check whether the page answers what potential customers search for. |
The public service page carries an unexpected rule
Suppose studio.example/services opens correctly while signed out. Its response contains X-Robots-Tag: noindex, and the owner wants this page in search. The header gives you a concrete condition to investigate. Find which application or hosting rule adds it to that route, then adjust the rule for the public page. Reload the final address, check the header again, and run the live test if available. Keep access controls on private routes.
Google chose the old address after a move
Suppose the intended page is now studio.example/work, but its declared canonical points to the equivalent page at the old address. The sitemap still lists that old URL and Search Console shows it as Google's choice. First confirm that the move is intentional. Update the canonical, public links, and sitemap to agree on the new address.
For a retired equivalent page, a permanent redirect helps signal the move if the old host supports it. Lovable's primary-domain setting uses temporary redirects between connected domains, so check the response the old address actually returns. Recheck the live configuration and later compare Google's selected address. If you intended to keep the old address as primary, the observed choice may be correct. Lovable's custom domain guidance
A newly published page passes the live test
Suppose studio.example/pricing passes the live test and the index report says Discovered - currently not indexed. Google knows the URL and has yet to crawl it in the recorded data. Check that the current page has a normal link from the site and that the sitemap, if used, includes the preferred URL. Confirm that the page contains useful pricing information a customer can read. If those checks pass, record today's state and plan a later check. A request for indexing is an option for the ready page if you have permission. Google's Page indexing report guide
An indexed page rarely appears in search
Suppose studio.example/custom-shelves is indexed and has few impressions. In Search Console's Performance report, filter to the page and choose a useful date range. Review the available queries and distinguish impressions from clicks. If the page mainly appears for the workshop's name and the page title just says “Services,” try describing the actual shelving service and adding details a customer needs, such as available materials and what installation includes. Compare the same page over comparable periods after the change. Google's Performance report guide
Keep a record for the next check
Copy this checklist for one URL. Record an unknown when you lack access or a result is unavailable. Pick the action that addresses the first confirmed issue.
- URL and date. Record the requested address, final address, date, and what you expect visitors to see.
- Public response. Record the status, redirect if any, and whether the correct content opens while signed out.
- Crawl and discovery. Record the applicable robots rule, any
noindex, the declared canonical, and the internal link or sitemap entry. - Google's evidence. Record the indexed status and last crawl date where shown. Write the live test result and its date separately. Use Performance data when you are investigating visibility.
- One action and a follow-up. State what you will change or recheck, which result would confirm it, and when you will look again.
If you are still shaping the page's offer and visitor action, see the guide to building a lead-generation landing page. For planning the domain and hosting together, see the cost guide for building with AI.
The RianVibe course covers how to connect technical search checks with search intent, useful content, and measurement. Explore SEO and AI Marketing
