Blog

Your Netlify site loads but Google shows nothing. Usually a preview URL's noindex, an SPA fallback faking 200s, or an empty HTML shell. Find yours fast.

Your GitHub Pages site loads but Google shows nothing. Usually Jekyll eating _next/, the 404.html SPA trick, or base-path 404s. Find your cause fast.

Your Bubble app loads but Google shows nothing. Usually an empty HTML shell, default metadata, or a version-test URL. Find your cause in 60 seconds.

Your Figma site loads fine but Google shows nothing. Usually the noindex setting, homepage canonicals, or a Make app with no title tag. Find yours fast.

Cloudflare can block Googlebot at five layers: custom rules, bot modes, Under Attack, rate limits. Find the one acting in Security Events and fix it fast.

Your Lovable site loads but Google shows nothing. Usually a client-rendered shell plus a missing sitemap and canonicals. Find your cause in 60 seconds.

Your Bolt site loads but Google shows nothing. Usually one hidden setting — SEO Boost — plus a few publishing slips. Find your exact cause in 60 seconds.

Your Vercel deploy works but Google shows nothing. 8 causes from the preview noindex header to an empty HTML shell, each with a 30-second check and fix.

Your Framer site loads fine but Google shows nothing. Framer's defaults are clean; the cause is a page noindex, a domain split, or patience. Check yours.

Your Base44 app loads fine but Google shows nothing. We fetched live Base44 apps the way Googlebot does and got a 1.8 KB empty shell. Find yours fast.

Your Replit app loads but Google shows nothing. Usually an empty HTML shell, a private deployment, or a dead replit.app URL. Find your cause fast.

Your site is indexed on Bing but not Google. Rule out a real block with URL Inspection in two minutes, then fix the version fold, robots rule, or lag.

Search Console says noindex is in your X-Robots-Tag header but your code is clean. Check the header and hunt the source: previews, plugins, config, CDN.

Your SEO tool reports 403 or 429 errors but the site loads fine. Usually your firewall blocked the tool, not Google. Two checks settle it in minutes.

Discovered - currently not indexed means Google found your URL but has not crawled it. It is a crawl-priority issue, not quality. Here is how to fix it.

Search Console says Couldn't fetch but your Next.js sitemap loads fine in the browser. Read the Last read date, test like a crawler, fix the real cause.

Search Console says Success but Discovered pages shows 0. Usually the count lags the last read, or your sitemap serves zero URLs. Two checks settle it.

Search Console says URL is unknown to Google. Google has never seen that exact URL. Check the variant you inspected, your sitemap, and internal links.

Neither www nor non-www ranks better. Duplicate live versions, temporary redirects, and SSL errors do the damage. Test all four variants in 30 seconds.

An XML sitemap is the list of pages you want Google to crawl. A missing, invalid, or client-side rendered one hides your site. Check yours in 60 seconds.

No, Google has no 60-character limit. Titles are cut by pixel width, and titles over 60 characters get rewritten 76% of the time. The 30-second check.

A canonical tag tells Google which URL is the real one. Point every page at the homepage and Google drops the rest. Test yours with one curl command.

A soft 404 is a missing page that returns 200 instead of 404, so Google crawls junk and drops real pages. Test yours with one curl command and fix it.

Your Next.js route sends Cache-Control: no-store and Vercel shows MISS on every request. What puts it there, what it costs, and why it won't de-index you.

Your link preview shows no image on X, LinkedIn, or Slack. Usually og:image is missing, relative, a dead URL, or the wrong format. Find and fix it.

The real story of game-scout's first Google clicks: not the homepage, not a trick — one specific niche page and the long-tail search that found it.

Add the TrafficTriage MCP server to Claude or Cursor and ask your assistant why your site isn't on Google: the 8 checks and one verdict, in chat.

The managed route, step by step: connect Google Search Console to Claude or Cursor with the TrafficTriage MCP server - 6 checks, read-only, in chat.

Connect an SEO MCP server to ChatGPT on the free plan: Developer mode, the New Plugin form, and the OAuth scope that breaks it when Claude works fine.

A real morning on a 67,000-impression site: the 7am Search Console report, the page that ranks and earns nothing, and how I pick what to write next.

Most SEO MCP servers are built for agencies with data plans. Here's which ones fit an indie hacker at zero, and the one job each of them does best.