Managing Google Search Console after a migration

1Connect Google Search Console to your Lovable project

Manual steps in your browser

• Think of a 'connector' as a simple permission slip. It allows this project to read your Google Search Console data—the reports Google provides on how you appear in search, which pages are indexed, and where links are broken. It doesn't publish or change anything, and setup takes about a minute.
• Without this connection, we are effectively guessing. With it, we can record your current rankings before the move, submit your new sitemap immediately after, and confirm that your search presence remains intact. You can skip this, but you will lose that before-and-after proof.
• Step 1 — In your Lovable project, locate the chat box at the bottom of the screen. Click the '+' button to its left.
• Step 2 — Select 'Project connectors', then 'All connectors'. Find 'Google Search Console' in the list and click 'Connect'.
• Step 3 — A Google sign-in window will appear. Use the account that already owns the site in Search Console. This is usually the account used to set up the original site or your primary marketing account. A new personal Gmail account will likely show an empty list.
• Step 4 — Google will ask you to approve read access. Click 'Allow'. Once finished, return to the chat and type 'connected'.
• If you have never used Search Console, that isn't a problem. Just let us know, and we will create and verify the property for you. You will only need to click 'Publish' once so Google can detect the verification tag.
• The connection is contained entirely within this Lovable project. Sitejump never stores your Google credentials or sees this data. You can disconnect at any time from the same menu.
• For the best results, connect while your old site is still live. This allows us to establish a ranking baseline before the domain moves.

I need about a minute of your time to connect Google Search Console. No technical expertise is required. Search Console is the free reporting tool Google provides to website owners. Connecting it here allows me to record your current rankings and prove that nothing was lost during the move. I won't publish or change anything on your site. 1. Click the '+' button next to the chat box below. 2. Go to Project connectors → All connectors → Google Search Console → Connect. 3. Sign in with the Google account that owns your current site. 4. Click 'Allow', then tell me 'connected'. If you've never used Search Console before, just say so. I'll set it up and verify it for you—you'll just need to hit 'Publish' once. It's best to do this while your old site is still live so I can capture your baseline.

2Verify your site ownership

Automated by your AI builder

• If your old site was already verified, we have already extracted the ownership meta tag and included it in your new build. Your verification should carry over automatically.
• If no property exists yet, we will verify it using the meta-tag method. We generate a verification token, add the required <meta> tag to your project's head, and ask you to publish the site to finalize the connection.
• Google cannot see tags that only exist in a preview environment. If verification fails, ensure you have published the latest version of your project before retrying.
• We typically use a URL-prefix property for verification, as it is sufficient for sitemaps and reporting. If you require coverage across multiple subdomains, a Domain property (via DNS) is an alternative, though more complex to set up.
• Regardless of the method, your site should resolve to a single canonical address (e.g., https://www.yourdomain.com). If both 'www' and 'non-www' versions are active, your search data will be split across two different properties.

I've re-applied your old site's verification tag to the new build so your ownership carries over. If Google doesn't recognize the property yet, I can add a new tag for you—you'll just need to publish the site once.

3Submit your sitemap

Automated by your AI builder

• Once your domain is pointing to the new site, we submit your sitemap.xml to Google to ensure all pages are recognized.
• The migration process generates this sitemap automatically, listing every rebuilt page so Google doesn't have to find them by chance.
• You only need to re-submit if your site structure changes. Repeatedly submitting the same sitemap does not make Google crawl your site faster.

Your new sitemap has been submitted. Google now has a complete list of your new pages. I'll let you know how many URLs were accepted and if Google flagged any issues.

4Manually request indexing for key pages

Manual steps in your browser

• Submitting a sitemap tells Google your pages exist, but it doesn't force an immediate crawl. Google still decides when to visit.
• The most effective way to speed this up is the 'Request Indexing' feature within Search Console's URL Inspection tool. This is a manual action that must be performed in a browser; no API or automated agent can do this for you.
• In Search Console, go to URL Inspection, paste a URL, and click 'Request Indexing'. Start with your homepage, followed by your 5–10 most important pages. Do not attempt to do this for every page, as Google imposes a daily limit.
• Wait until your domain is live and redirects are active before doing this. Requesting an index for a page that still returns a 404 error is a wasted request.

There is one task I cannot automate: 'Request Indexing' must be done manually in your browser. Go to Search Console → URL Inspection, paste your homepage URL, and hit 'Request Indexing'. Repeat this for your top 5–10 pages. It is the fastest way to get your new site noticed.

5Understanding indexing vs. ranking

Automated by your AI builder

• A new or migrated site usually sees its first crawl within a few days. Note that Search Console performance data typically lags by 1–3 days, so an empty report doesn't necessarily mean you have no traffic.
• Being indexed simply means your page is eligible to appear in search. Ranking—appearing at the top—requires time, links, and search history. Brand searches usually recover first; competitive terms may take longer.
• To see what Google has currently indexed, search 'site:yourdomain.com' directly in Google.
• On a migrated site, your redirects do the heavy lifting. As long as your old URLs point to their new counterparts via permanent (301) redirects, your authority is preserved. Run our launch verification to ensure these are working correctly.

Expect a crawl within a few days. Remember that being indexed is not the same as ranking: your brand name will show up first, while competitive terms take time to rebuild. You can search 'site:yourdomain.com' to see what's currently live. Since we've set up 301 redirects for every old URL, your authority will carry over—I can verify this for you at any time.

6Why your old site may have seemed faster

Automated by your AI builder

• Speed of indexing is rarely about the platform (like WordPress vs. others). An old site that indexes instantly does so because Google has crawled it daily for years. A new domain or a significant move triggers a fresh discovery schedule, which is naturally slower.
• The main technical factor is readability. If a site requires JavaScript to display its content, crawlers may see a blank page. Our migrations are server-rendered to ensure your text, titles, and headers are immediately visible to Google. You can run run_indexability_check to verify this.
• Internal and external links are the best way to speed up discovery. Linking to every page from your homepage and maintaining social or partner links will help Google find you faster than a sitemap alone.
• By keeping your domain and using 301 redirects, you inherit your site's history rather than starting from zero. This makes a migrated site index much faster than a brand-new one.
• Avoid changing both your domain and your platform at the same time if possible. If you must change domains, keep the old one active and redirecting for at least a year.

If your old WordPress site indexed quickly, that was due to the domain's history, not the software. Two things matter now: your pages must be readable without JavaScript—which I've ensured—and you need links pointing to the site. Because we kept your domain and redirected your old URLs, you're building on your existing history rather than starting over.

7Monitoring your launch

Automated by your AI builder

• Check your Search Console 'Pages' report weekly for the first two months. Look for new 404 errors, 'crawled – currently not indexed' notices, or redirect issues.
• If you see new 404 errors, compare them against your redirect map and add a 301 redirect for any missing pages.
• You can re-run our launch verification for free after making any structural changes to ensure everything is still aligned.

Over the next few weeks, I'll monitor for coverage errors and 404s. You can ask me to run a check against your redirect map at any time.

8Optimizing for AI answer engines

Automated by your AI builder

• AI engines like ChatGPT, Perplexity, and Claude read sites much like search crawlers do. We include findability files (llms.txt, index.json, and Markdown mirrors) to help these engines understand your site without needing to run JavaScript.
• To be cited by an AI, a page needs clear structure: one H1 tag, factual paragraphs near the top, proper headings, and valid schema markup. We carry all of this over from your old site.
• We allow AI crawlers (like GPTBot and ClaudeBot) in your robots.txt by default. You can block them if you prefer, but doing so will prevent your site from appearing in their generated answers.
• There is no 'request indexing' for AI engines. They crawl on their own schedule; being factual and well-structured is the only way to encourage citations.

I've set up your AI findability files—including llms.txt and Markdown mirrors—so ChatGPT, Perplexity, and Claude can read your site easily. There's no 'submit' button for these engines; they will find you on their own schedule, using your structured data and clear headings to generate answers.

9Verify analytics and tracking

Automated by your AI builder

• We automatically carry over your GA4, Google Tag Manager, and Meta Pixel IDs. Check your GA4 'Realtime' report after launch to confirm that data is flowing correctly.
• Other Google services, such as Sheets or Drive, can be connected through the 'Project connectors' menu in the same way you connected Search Console.
• We do not use a Google Forms integration. Instead, embedded Google Forms are rebuilt as native forms that can still send data to your existing Sheets, CRMs, or email via Gmail.

Your GA4 and Tag Manager IDs have been carried over. Check your GA4 Realtime report after launch to confirm everything is working. You can connect other services like Google Sheets or Drive through the project connectors menu.

Troubleshooting

Search Console says my URL is unknown to Google

This usually means the property was recently verified and hasn't been crawled yet. Confirm the page is live (200 OK), appears in your sitemap, and isn't blocked by robots.txt. Then, request indexing manually and wait a few days.

Verification fails with 'could not find the meta tag'

The tag must be on the live site, not just in the project preview. Publish your site, then view the source code of your homepage to confirm the tag is in the <head>. Google cannot verify tags injected by client-side scripts or placed on subpages.

The property list is empty or shows the wrong site

You likely signed in with a Google account that doesn't have owner permissions for the site. Disconnect the connector and reconnect using the correct account, or ask the site owner to add you as a user in Search Console.

The domain is listed, but every request is refused

Your account may be listed as an 'unverified user.' You must complete the meta-tag verification or be added as a full user by the owner before sitemaps or inspection tools will work.

Sitemap submission is rejected or shows errors

Ensure the sitemap is accessible on your live domain. It must be valid XML and use the same hostname as the property. Google will reject sitemaps that point to a different domain or only exist in a preview environment.

Can you refresh my favicon or force a re-index?

No. While we can automate sitemap submission, Google controls the crawl frequency and favicon updates. Favicons are typically updated only after Google re-crawls your homepage, which can take several weeks.

Data is split between www and non-www versions

This happens when both versions of the site are active. You should choose one as your canonical host and set a 301 redirect from the other. Alternatively, use a 'Domain' property in Search Console to aggregate the data.

Pages are indexed on the old site but not the new one

Check your redirects. Every old URL must point to its new equivalent in a single hop. Use our launch verification tool to find and fix any 404s or redirect chains that might be stalling Google.

Nothing is being indexed at all

Check for a 'noindex' tag left over from staging, a 'Disallow: /' directive in your robots.txt, or a canonical tag still pointing to your old domain. While we write these correctly, manual edits can sometimes override them.

Why did my WordPress site index faster than this one?

It's about domain history, not the platform. Established domains are crawled more frequently. Ensure your site is readable without JavaScript by running our indexability check, and focus on maintaining quality backlinks.

The site is indexed but doesn't appear in search results

Indexing is just the first step. If your domain is new, it has no search history. It can take weeks or months for competitive terms to rank, even if the technical setup is perfect.

Can Lovable or Sitejump request indexing for me?

No. Google does not provide an API for 'Request Indexing'; it is strictly a manual action in the Search Console interface. We can, however, automate sitemap submission and monitoring once you've connected the account.