Your Website Is Live, but Google Can't Find It? Here's What's Actually Going Wrong

You hit publish. The site loads fine on your phone, you've sent the link to a few friends, and one of them even said the design looks nice. Then you open Google, type in your site's name (or the title of your first post), and get nothing. Or you get somebody else's page. Or some result from five years ago that has nothing to do with you.

It stings, and almost everyone who has launched a website has been there. The good news is that the cause is usually on a short list, and you can check most of it in an afternoon with free tools. Some fixes take two minutes. A couple are about the content itself, and those take longer.

First, which kind of "can't find it" is this?

"Google can't find my site" covers three different situations, and each one needs a different fix.

1. Google doesn't have your page. It hasn't found it, or it found it and decided not to keep it. That's an indexing problem.

2. Google has your page, but it doesn't show up for the search you tried. That's a ranking problem, and it's much more common than people expect.

3. The site is simply new. Nothing is broken. Google just hasn't gotten around to you yet.

A little background makes the rest easier. When you search, Google isn't scanning the live internet. It searches its own stored copy of the web, called the index. Before your page can appear there, Google has to find it (crawling), read and render it, and then decide to add it. Any one of those steps can fail.

One more thing, because it trips people up: a successful deployment proves very little here. If your site loads after you push it to Vercel or Netlify, all that shows is that your server can deliver the page. Google's own documentation is clear that it doesn't promise to crawl, index, or show any particular page, even one that follows every guideline. So the realistic goal is to remove every obstacle you control, then give Google a reason to want you.

The five-minute check

Do this before you change anything. It tells you which problem you actually have.

Try a site: search. Type site:yourdomain.com into Google. If some of your pages show up, Google knows you exist. If nothing does, you likely have an indexing problem. Treat this as a rough hint only, since Google says the operator doesn't necessarily list every indexed URL.

Set up Google Search Console. It's free, and it's the one place where Google tells you directly what it thinks of your site. If you haven't added your site yet, do that first.

Inspect one specific URL. Paste the full address of a post into the URL Inspection bar at the top of Search Console. You'll see whether the page is on Google, when it was last crawled, whether indexing is allowed, and which version Google picked as the canonical (preferred) one. Use the exact version you care about, including https, www or not, and the trailing slash. A page can be indexed under one version of its address and missing under another.

Open the Pages report. The Page indexing report lists the pages that aren't indexed and gives a reason for each. We'll decode the common ones below.

Reason 1: You, or your platform, told Google to stay away

This one is a bit embarrassing because it's self-inflicted, but it's also the fastest to fix.

The WordPress checkbox. Under Settings → Reading, WordPress has an option that asks search engines not to index the site. It's meant for building in private, and people forget to untick it at launch. Google generally honors it. If you're on WordPress, check this before anything else. Also keep in mind that a physical robots.txt file in your site's root folder can take priority over WordPress's built-in setting, so a leftover file can keep blocking crawlers even after you've fixed the checkbox.

A noindex tag left over from staging. Developers often add noindex to a test copy of a site, and now and then it ships to the live one. In URL Inspection, look for a line saying indexing isn't allowed. Or open the page, view the source, and search for "noindex." It can also arrive as an X-Robots-Tag in the HTTP response headers, which you won't see in the page source at all.

A robots.txt that says Disallow: /. Visit yourdomain.com/robots.txt in your browser. If you see Disallow: / under a rule that applies to all crawlers, the entire site is off limits.

When the platform is the culprit. It isn't always your own mistake. In March 2026, a user on Figma's community forum (the Figma Community) reported that their Figma Sites page kept serving a noindex tag even after they'd turned off the "exclude from search engines" setting and republished twice. Search Console kept reporting the pages as excluded by noindex. A second member said they were hitting the same problem on their own domain. (The thread doesn't show a final resolution, so treat it as a warning, not a fix.) The lesson is useful whatever you build on: don't trust a settings toggle. Open the live page, view the source, and check the tag is actually gone.

There's a trap here that catches experienced people too. Robots.txt and noindex do different jobs. Robots.txt controls whether Google may crawl a page. Noindex controls whether Google may show it. If you block a page in robots.txt, Google can't read the noindex tag on it, and the bare URL can still appear in results (without a description) if other sites link to it. To keep a page out of Google, use noindex and leave the page crawlable. Google also doesn't support a noindex rule written inside robots.txt.

The reverse matters too. If you want a page indexed, don't rely on JavaScript to remove a noindex tag after the page loads. Google's guidance says not to put noindex in the original page code if you want the page indexed, because it may skip rendering in that case.

Once you've fixed any of this, Google still has to come back and notice. The Request Indexing button in URL Inspection can nudge things along, but expect days, not minutes.

Reason 2: Google was never properly introduced to your site

Googlebot finds a lot of new pages by following links from pages it already knows. A brand-new site with no links pointing at it and no sitemap can take longer to be noticed.

A few things help.

Submit a sitemap. Google describes a sitemap as an important way to discover URLs, and says it's especially useful right after a launch or a site move. Most CMS platforms and SEO plugins generate one automatically. Submit its address in Search Console. It helps Google discover your pages, but it can't force indexing.

Link to your pages from your own pages. A post that nothing else on your site links to is an orphan, and orphans are easy to overlook. Link new posts from your homepage, category pages, and related older posts, using ordinary links.

Request indexing for your most important URLs. In URL Inspection, use the Request Indexing button for a handful of key pages. Google says there's a quota on individual submissions, and asking again for the same URL won't make it get crawled sooner. Click once and move on.

Over time, a few real links from other legitimate sites also help. A genuine mention in a community you actually belong to is worth more than any shortcut.

Reason 3: The site is just new

Google says it can take anywhere from a few days to a few weeks for a page to be crawled after you request it. For a brand-new domain, many SEO practitioners report that it can take months before pages show up consistently for competitive searches. Nobody outside Google can give you an exact number, so be wary of anyone who does.

If Search Console says "URL is on Google," your technical job for that page is done. What's left is the slow part: building something worth ranking.

Reason 4: Search Console says "Discovered" or "Crawled – currently not indexed"

These two labels cause more panic than almost anything else in Search Console, and they mean different things. Here's a quick reference for the statuses you're most likely to meet.

• URL is on Google. The page is indexed. Next, look at rankings and queries in the Performance report.

• Discovered – currently not indexed. Google knows the URL but hasn't crawled it yet. Check internal links, your sitemap, and server speed.

• Crawled – currently not indexed. Google visited the page but chose not to index it for now. Check content quality and originality.

• Blocked by robots.txt. Crawling isn't allowed. Check your robots.txt file.

• Excluded by "noindex" tag. The page tells Google not to index it. Check the page's meta tags and headers.

• Duplicate or alternate page. Google picked a different version as the main one. Check canonical tags and redirects.

Two of these deserve a closer look.

Discovered – currently not indexed. Google's documentation says this usually happens when it wanted to crawl the page but expected that doing so might overload your site, so it rescheduled. On a small blog it often just means "not yet." If lots of pages sit here for weeks, check your server speed and make sure those pages are linked from elsewhere on your site.

Crawled – currently not indexed. Google read the page and chose not to store it, at least for now. Google says it may or may not be indexed later and that you don't need to resubmit it. Many SEOs read this status as a quality signal. If your setup is clean (nothing blocked, nothing broken), the content becomes the next suspect.

What this looks like in real life. A shop owner on the Shopify community forum, a few months into running a multi-product store, noticed more than 900 URLs sitting under "Crawled – currently not indexed." They asked whether there was a bulk way to request indexing. There wasn't one, and the replies shifted the question: just because Google crawled a page doesn't mean it should keep it, and the skipped pages are often ones with nothing unique compared to another version on the same site.

And the status isn't always a verdict on quality. The SEO agency Onely describes a case shared by freelancer Adam Gent, where a page landed in this bucket because Google judged it a duplicate of another page, even though he saw it differently. The same write-up notes that a page can be indexed, then dropped later if Google's evaluation changes, so "indexed once" isn't "indexed forever."

Reason 5: The content isn't giving Google a reason to include it

If the technical side is clean and your pages are crawled but not indexed, look hard at what's actually on them.

Google isn't trying to index every page on the internet. It wants an index full of pages people find useful. A page can be long, nicely formatted, and keyword-optimized, and still get skipped if it adds little that's original. Length isn't substance.

These patterns tend to get pages skipped:

• Posts that restate what the top five results already say, with nothing added.

• Near-duplicate pages, like the same article for ten cities with only the name swapped.

• Very short pages that don't fully answer the question.

• Lots of pages published quickly to make a site look busy. Google's spam policies specifically target mass-produced, low-value pages.

Ask yourself one blunt question: what does this page tell a reader that the current top results don't? Your own screenshots, a real example from something you did, a clearer explanation, a mistake you made and fixed, a comparison nobody else bothered to make. That's what earns a place in the index.

If you have a lot of weak pages, merging or rewriting them usually beats adding more. Experienced contributors on Google's own Search Central community say much the same: combine pages that compete for the same purpose into one stronger page, rather than publishing piles of near-copies for search engines. A smaller site with genuinely useful pages is usually a better foundation than a large site filled with thin, repetitive ones.

Reason 6: Google can't see your content because of JavaScript

If your site is built with React, Vue, Next.js, or something similar, pay attention to this one.

Google can run JavaScript. It queues pages and, when its resources allow, renders them with a headless Chromium browser, then reads the result. But if your key content only appears after a script runs, and that script is slow or fails, Google may see a nearly empty page. Google's documentation says content that isn't visible in the rendered HTML can't be indexed.

To check, use the live test in URL Inspection and look at the rendered HTML. Make sure your headings, text, and links are actually there. If they aren't, the usual fix is server-side rendering or static generation, so the content is already in the HTML that arrives from the server.

Two related traps:

• Links that aren't real links. If your navigation depends on click handlers instead of proper <a href> links, crawlers may not follow it.

• Wrong status codes in single-page apps. If a missing page shows a "not found" message but still returns a 200 (OK) status, Google may treat it as a real page. Google's rendering guidance flags this.

Reason 7: You're checking the wrong version of your site

A site can exist at http:// and https://, with and without www. If these don't redirect cleanly to one preferred version, or a canonical tag points somewhere unexpected, Google may index one version while you're looking at another.

URL Inspection shows both the canonical you declared and the one Google chose. If they differ and you didn't plan that, you've found your lead. Pick one version, redirect the others to it, and make sure your canonical tags and sitemap all agree.

Reason 8: A manual action or security problem

This is unlikely, but it takes ten seconds to rule out. In Search Console, open the Manual actions report and the Security issues report. A manual action means a human reviewer at Google decided that pages on your site break its spam policies. A security issue means the site may have been hacked or is serving something harmful. If both are clean, move on. If there's a flag, the report explains what to fix and lets you request a review afterward.

It's also worth knowing that Google itself sometimes gets it wrong. The Onely write-up mentioned above points to a case where Search Engine Land was deindexed because Google wrongly assumed the site had been hacked. Rare, but a good reminder to check the Security issues report instead of assuming the problem is always yours.

Reason 9: You're indexed, but searching for the wrong thing

This quietly explains a big share of "Google can't find my site" complaints.

Say you search "best email marketing tools" and your two-month-old blog isn't on page one. Nothing is broken. Established sites with years of links own those results. New sites are more likely to make progress with narrow, specific searches, especially long questions that bigger sites haven't answered well.

So test it. Search the exact title of one of your posts. If it shows up, you're indexed. Then open the Performance report in Search Console and look at impressions and queries to see what Google is actually showing you for. Often the real issue is that your target keyword is out of reach for now, and a smaller, more specific topic is a better first goal.

A sensible order to work through

1. Add your site to Google Search Console if you haven't.

2. Check for accidental blocks: the WordPress visibility checkbox, noindex tags (in the page and in headers), and Disallow: / in robots.txt.

3. Inspect one important URL and read what Google says about it.

4. Submit a sitemap and request indexing for a few key pages, once each.

5. Add internal links to any page that nothing else links to.

6. Open the Pages report. If pages are "crawled, not indexed," improve the content before anything else.

7. On a JavaScript framework, confirm the rendered HTML contains your content.

8. Check Manual actions and Security issues once.

9. Publish genuinely useful posts and check back in a few weeks.

Mistakes that make it worse

Mashing the Request Indexing button. It doesn't speed anything up, and there's a quota.

Blocking a page in robots.txt and adding noindex to it. Google can't read the noindex, so you get the opposite of what you wanted.

Publishing dozens of thin posts to look active. It can backfire. Fewer, better pages win.

Treating a status label as a verdict. "Discovered" and "Crawled" describe a moment in time. They aren't a final decision.

The short version

Most of the time, a site Google can't find has one of two problems. Either something is accidentally blocking it, or Google hasn't been given a good enough reason to include it. The first is a settings check. The second takes longer, because it means making pages that are worth finding.

Start with Search Console, rule out the boring stuff, then put your effort into one genuinely useful page at a time.

Sources and further reading

Official Google pages this article draws on:

• Ask Google to recrawl your URLs

• Introduction to robots.txt

• Block search indexing with noindex

• No page information in search results

• JavaScript SEO basics

• Manual actions report

Real-world cases referenced above:

• Figma community thread on a persistent noindex tag

• Shopify community thread on 900+ "Crawled – currently not indexed" pages

• Onely: How to fix "Crawled – currently not indexed"

• Google Search Central community guide on "Crawled – currently not indexed"