Why your online store isn't showing up on Google: a diagnosis for Shopify, Tiendanube and WooCommerce

Why your online store isn't showing up on Google: the three states that all look the same from outside

When you think "my online store isn't showing up on Google," you could actually be describing three completely different situations, and all three feel identical from where you're standing: you search for your store and don't see it. But the cause, how you confirm it, and where you fix it are different in each case, and applying the wrong fix costs you weeks.

The first state is that your store simply isn't indexed: Google doesn't know about it yet, almost always because your platform ships with a block turned on that you never knew existed. The second is that it's indexed but only shows up when someone searches your brand name: Google knows your store fine, it just doesn't consider it relevant for generic searches for what you sell. The third is that it's indexed and does show up, but so far down the results that in practice nobody sees it — not even you, searching from your own phone.

Two things to rule out before going further. If what's missing isn't your website but your listing when someone searches nearby, that's a completely separate diagnosis: see the guide on why your Google Maps listing isn't showing up. And if your store used to rank well and dropped out overnight, that's not this case either — it's a drop triage, covered in the guide on what to do when a keyword that used to rank suddenly drops. This guide is for when you never showed up in the first place, or not in the way you expected.

The three tests to find out which state you're in (and how to check if your page is indexed on Google)

You don't need to guess. Three checks, run in this order, tell you exactly which of the three states your store is in today.

1. Test 1 · URL Inspection, inside Search Console itself

   Paste your homepage, one category page and three product pages into the URL Inspection tool inside Search Console itself (no external app runs this check). If the result says "URL is not on Google," look at the reason it gives you below — usually a noindex tag, a redirect, or simply that Google hasn't crawled it yet — and compare it against the platform block table further down. Once you've fixed the block, use "Test Live URL" and then "Request Indexing" once: asking more than once doesn't speed up the crawl, it just queues behind the first request.

2. Test 2 · Performance filtered by page

   In Search Console's own Performance report, filter by your homepage, a category page and three product pages, and look at the last 28 days. No impressions at all: you're still in state 1, or you just fixed it and Google hasn't caught up yet. Almost all impressions come from queries with your store's name: state 2. Impressions from product or category queries, but at an average position worse than 20: state 3. Rankiamos, with your Search Console account connected, doesn't filter by page — it shows clicks and impressions by query —, but for the same purpose there's the Search Console connection and site scan included in the Free plan, no payment method required.

3. Test 3 · Rank measured under fixed conditions

   Track 5 keywords (2 category terms, 3 product terms with a modifier — "women's running shoes," not just "shoes") always in the same city, the same device, the same day of the week. If a tool can't find your store within its measurement depth, write down "outside the top 30," not "not showing up" — those are different things, and confusing them makes you think you're still in state 1 when you've actually already moved to state 3.

The site: search operator gives you a quick read on what Google has indexed for your domain, but it doesn't replace any of the three tests: it can surface a weeks-old cached result, or hide pages that are indexed but look weak for that exact phrase. And it's worth being precise about what Rankiamos does and doesn't do here: the app does not run URL Inspection and can't tell you why Google skipped a page — only Search Console itself answers that. What the app confirms, once your account is connected, is whether those queries already have impressions in Performance (by query, not filtered by URL or page); and an empty site scan is a hint to go check state 1, not a formal diagnosis on its own.

The factory-default block on each platform

Before the platform-by-platform detail, here's the summary table. Double-check the exact menu names in your own dashboard, since platforms shuffle section names now and then.

Tiendanube store not showing up on Google: page under construction, domain and sitemap

If your Tiendanube store isn't showing up on Google, the first thing to rule out is the "Page Under Construction" mode. It's the number-one cause raised in Tiendanube's own community forum, and it makes sense why: many stores get set up with that mode on while products and prices are still being loaded, and then nobody remembers to turn it off on launch day. With that mode active, Google can't see anything in your catalog, not even the homepage — for all practical purposes, your store doesn't exist online.

You'll find it under Online Store → Page Under Construction, and turn it off by unchecking "Show page." Once it's off, double-check that the correct property is added in Search Console: if you use a custom domain connected to Tiendanube, the property should be that domain, not the generic Tiendanube subdomain you may have used before connecting it — if Search Console is verifying the wrong property, you'll be looking at data that has nothing to do with your actual store.

The last step is submitting your sitemap from Search Console → Sitemaps, at /sitemap.xml, following Tiendanube's own help articles on verifying your store with Google and submitting a sitemap. Tiendanube's own help center is upfront about timing: showing up in search results can take several weeks even once everything is configured correctly, so don't expect results the same day. Confirm the exact menu names in your own dashboard when you read this, since Tiendanube reorganizes them from time to time.

Shopify store not showing up on Google: the private mode that ships turned on

If you're asking why your Shopify store isn't showing up on Google, there's an answer that comes up in nearly every community thread: according to Shopify's own help center, when you sign up for a plan your store is set to private mode by default, protected by a password page. While that mode is on, neither visitors nor search engines can see anything past that screen — Google can't index what it can't read.

Turn it off from Online Store → Preferences, or from the "Private" icon that appears at the top of your dashboard while the mode is on, switching it to "Public." One thing worth confirming in your own dashboard before assuming anything: check whether your current plan, including a free trial if you're on one, already lets you remove password protection, since Shopify has moved this setting around between plans over time — your own dashboard is the safest place to check on the day you need it.

Everything else is the same as on any platform: confirm your domain is verified in Search Console and that your sitemap at /sitemap.xml is submitted and shows "Success." With the store public and the sitemap submitted, request indexing once from URL Inspection on the homepage, then let the crawl run its natural course.

WooCommerce: "Coming Soon" mode and the WordPress checkbox that blocks search engines

WooCommerce is the case with the most layers, because it inherits WordPress's settings on top of its own. New stores often default to "Coming Soon" mode: check it under WooCommerce → Settings → Site visibility, and switch it to "Live" once you're ready to launch. While it's on "Coming Soon," visitors see a holding page and Google sees none of your catalog.

On top of that, WordPress has its own separate checkbox under Settings → Reading: "Discourage search engines from indexing this site." Checking it makes WordPress insert a meta robots noindex, nofollow tag on every page, a behavior in place since version 5.3. This box is the classic trap in projects that moved from a staging environment to production: it gets turned on deliberately during development so Google doesn't index the test version, and it's easy to forget to uncheck once the site goes live on the real domain.

A third spot worth checking, specific to WooCommerce: if you're running an SEO plugin (Yoast, Rank Math or another), some of them mark individual products or categories as noindex during initial setup, without it being obvious at a glance. Finally, confirm your sitemap: WordPress ships a native one at /wp-sitemap.xml since version 5.5, or your SEO plugin generates its own if you have one active — submit whichever applies from Search Console → Sitemaps.

State 2: your store only shows up when someone searches your brand name

If you've already confirmed your store is indexed, but in Performance almost all your impressions come from queries that include your store's name, you don't have an indexing problem — you have a relevance problem. Google knows your store perfectly well; it just doesn't consider it the best answer when someone searches "running shoes" instead of "Acme Shoes running shoes."

In e-commerce, the causes repeat with almost boring consistency. Product titles that are just a supplier's internal SKU, with none of the words a real shopper would type. Category pages that are nothing more than a product grid, with no paragraph of text telling Google what that category is about. And product descriptions copied verbatim from the manufacturer's spec sheet — the same spec sheet already published on two or three marketplaces, where Google has to pick one version to show, and it's rarely yours, since you got there last.

(The filter to separate branded queries from non-branded ones already exists inside Search Console; if you have dozens of variants of your brand name to filter out one by one by hand, that gets tedious fast — there's a separate guide to regex for Search Console queries that solves exactly that.)

Don't try to fix your entire catalog in one sitting. Pick one category with real search volume and three products in it, rewrite the title, category text and description in your own words — thinking about what a shopper would type, not how your supplier names it — and measure those same generic searches under fixed conditions before and after. If a month from now the Performance impressions for those pages start coming from non-brand queries, the change is working and you can roll the same approach out across the rest of the catalog.

State 3: your store shows up, but so far down that nobody sees it

This is the state that trips up store owners the most, because the check they do instinctively — searching for their own product from their phone — almost never confirms or rules it out with any precision. You search from your phone, signed into your own Google account, in your own city, and see your store at position 3. The catch is that Google is showing you a personalized version of the results, tuned to your history and your exact location, which can look quite different from what a first-time shopper sees without that context — we cover the exact reason why in the guide on why searching for yourself doesn't tell you your real rank, not even in incognito mode.

To find your real position you need a tool that measures under neutral conditions: no personal session, no browsing history, a fixed city and device that you choose. If your store falls outside that tool's measurement depth, log it as "outside the top 30" — the app reads the first 30 organic results on Google, and from position 31 onward it shows "30+" instead of a specific number it doesn't actually have.

Two frequent causes of ranking far down deserve a quick mention, without going deep here, since each has its own guide. If the top 10 for your category is dominated by big marketplaces and large retailers, that's a specific scenario we'll cover separately in a guide on competing when marketplaces occupy your top 10. And if your store is new and simply hasn't had time to earn its ranking yet, that's a timing question we also cover in detail in a separate guide on how long it takes a new website to rank.

And a mobile-versus-desktop gap that goes beyond the Free-plan note above — for when the difference between devices is real and not just a quota question — gets its own treatment in the guide on the difference between mobile and desktop rankings.

What doesn't speed up anything: requesting indexing ten times, switching themes, or running ads

The same desperate moves come up over and over in community threads, and they're worth naming because none of them change the outcome, and some make it worse. Requesting indexing for the same URL multiple times in a row doesn't make Google crawl faster — the repeated request doesn't jump the queue, it just gets ignored if one is already pending. Reinstalling your theme doesn't touch indexing either — it changes the design, not whether Google can read your content. Deleting and recreating the same products is one of the worst moves: every new product gets a new URL, so instead of fixing the problem you pile the work of indexing brand-new URLs on top of it.

Migrating platforms out of pure impatience, without first running the three tests in this guide, sometimes fixes things by accident (because you happen to remove the block along the way) and in most cases just adds a broken-URL problem on top of the original problem you never diagnosed. And turning on Google Ads or Google Shopping hoping it "helps" your SEO doesn't work that way: they're paid systems entirely separate from organic ranking, and neither one improves your position without you paying for it continuously.

Finally, any service offering "guaranteed search engine submission" for a fee is selling you something you can do yourself, for free, from Search Console in ten minutes: verify your property and submit your sitemap. There is no legitimate shortcut that speeds up Google's crawl beyond that.

Getting your online store to show up on Google isn't a one-time trick, it's a protocol you repeat: week 0 sets your baseline, and from there you check three things every single week until you see the change you were after.

The Free plan's weekly automatic check is plenty for this protocol. It's worth moving to Pro once you've already fixed the indexing block and want to watch the change day by day, or once you need to track mobile and desktop together in the same quota unit. If you want the full picture of how Rankiamos tracks rankings, Search Console and site scans in one app, that's where to look.