Why Search Console's live test shows a different page on Base44
On Base44, Search Console's Test live URL and the Rich Results Test get an auto-generated summary instead of your page. Why it happens and how to see what Googlebot got.
6 min read
On a Base44 site, Search Console’s Test live URL button and Google’s Rich Results Test don’t fetch your page the way Googlebot does. They use a user agent called Google-InspectionTool, and Base44 doesn’t pre-render for it. So the live test shows Base44’s hidden, auto-generated summary of your app, even when Googlebot receives the full rendered page. Read View crawled page on the indexed result instead.
What you’ll see
In the live test’s HTML view, a Base44 page looks roughly like this:
- A heading such as “Pricing | YourApp”.
- A sentence like “Pricing on YourApp.” followed by your app description.
- A “Pages” list with every page in your app.
That’s Base44’s seo-snapshot block, the fallback it serves when it isn’t pre-rendering. The snapshot guide explains where the text comes from.
Why it happens
Base44 decides whether to pre-render by user agent. In our tests on live Base44 pages, Googlebot’s user agent got the rendered page, and Google-InspectionTool’s user agent always got the summary, on the same pages, from the same address. GoogleOther, another Google user agent, got the summary too. The full split is in the crawler list.
How to read Search Console on a Base44 site
| Search Console view | Fetched by | On Base44, shows |
|---|---|---|
| Indexed result, View crawled page | Googlebot, at crawl time | What Googlebot stored: the render, or the summary if none was ready |
| Test live URL | Google-InspectionTool, now | The summary, every time |
| Rich Results Test (URL mode) | Google-InspectionTool, now | The summary, plus platform-injected JSON-LD |
So:
- Use the indexed result for what Google has. Open View crawled page → HTML and search for a sentence that only exists in your page’s real copy. Found: Googlebot got the render. Missing, with a “Pages” list instead: the crawl got the summary.
- Use the live test for other checks only, like whether the page is reachable, returns 200 and isn’t blocked by robots.txt.
- Use your own request to see what Base44 sends Googlebot right now:
curl -s -A 'Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)' \
https://yourdomain.com/pricing | grep -c 'id="seo-snapshot"'
# 0 = rendered page, 1 = summary
Validating structured data
The Rich Results Test’s URL mode has the same problem. Schema Base44 injects into the page head usually still shows, since it’s in every response. Schema your page adds after loading is only in the render. Test it this way:
curl -s -A 'Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)' \
https://yourdomain.com/product?id=abc > page.html
grep -c 'id="seo-snapshot"' page.html # make sure this prints 0
Then paste page.html into the Rich Results Test’s Code option.
What to do next
- Stop reading the live test’s HTML as Googlebot’s view.
- Check View crawled page on your five most important pages.
- If they show the summary, read the pre-rendering options.
Frequently asked questions
- Why does URL Inspection's live test show a summary of my Base44 app?
- The live test fetches with Google-InspectionTool, and Base44 doesn't pre-render for that user agent. It receives Base44's hidden summary block: a heading, a stock app description and a list of pages. Googlebot itself gets the rendered page once one exists.
- How do I see what Googlebot actually got from my Base44 page?
- Open URL Inspection for the page and use View crawled page on the indexed result, then check the HTML tab for a sentence from your real page copy. That shows the version Googlebot fetched and stored.
- Does the Rich Results Test work on Base44?
- Its URL mode uses Google-InspectionTool too, so it may miss structured data your page adds after loading. Fetch the page with Googlebot's user agent, save the HTML, and paste it into the test's Code option.
Read next
Keep going
-
Which crawlers Base44 pre-renders for, and which it skips
We tested 33 user agents against live Base44 pages. Googlebot, Bingbot, GPTBot, ClaudeBot and PerplexityBot get renders. Bravebot, Meta and Search Console's tester don't.
-
How to check what crawlers get from your Base44 app
Commands to test your Base44 pages as Googlebot, GPTBot and other crawlers: detect the seo-snapshot fallback, check renders, record pages, the sitemap and link previews.
-
Base44's seo-snapshot block: what it is, how to improve it
Every Base44 page ships a hidden seo-snapshot div that crawlers read when no render is ready. What it contains, where its text comes from, and how to make it better.
-
Pre-rendering Base44 apps: the complete guide
Does Base44 pre-render pages for Google and AI crawlers? Only from a cache. How Base44 pre-rendering works, where it leaves gaps, and every way to prerender a Base44 app.