Your product is live, it looks perfect in the store, and on Google it simply doesn’t exist. You search for its exact name and nothing comes up. It’s not a punishment or a mystery — it’s an indexing problem, and it almost always has one specific, nameable cause.
Crawling isn’t indexing
Google works in two phases: first it crawls (visits your URL and reads its content), then it decides whether to index it (stores it in its index so it can actually show it in results). A page can be crawled and still stay out of the index. And whatever isn’t in the index can’t appear in any search result — no matter how good your SEO is.
The usual suspects, from the dumbest to the subtlest
- Blocked in robots.txt — a leftover or badly written rule shuts the door on Google before it even starts.
- Meta noindex — the page itself is telling Google not to save it. Sometimes it’s just a tag forgotten there after a dev sprint.
- Canonical pointing to another URL — you’re telling Google “that other one is the real page”; it indexes that one, not this one.
- Missing from the sitemap — this doesn’t block indexing on its own, but if the URL also isn’t well linked internally, Google may take a long time to find it, or never find it at all.
- “Discovered, currently not indexed” — Google knows about the page and has decided to wait: thin content, manufacturer duplicate copy, or a store with weak overall signals. The most frustrating one, because there’s no technical error to fix.
Why this hits ecommerce harder
A catalog generates URLs at a rate no corporate website ever matches: new product pages, variants, filters, pagination, discontinued items. Google doesn’t index everything you throw at it — it selects. The more similar or weak URLs you feed it, the more likely your good pages end up queued behind the disposable ones.
Finding out by accident
You discover a product page isn’t indexed months later, while searching for it manually — by which point it’s already lost an entire selling season.
Auditing it systematically
You know which URLs in your catalog are indexed, which aren’t, and why — and you decide what to fix first.
💡 Half of these problems can be spotted without connecting anything: just by checking robots.txt, the sitemap, noindex tags, and canonicals. Here’s how, in the technical indexing audit for PrestaShop.
A lighthouse for your back office
Zeyvro Faro is built for exactly this: it tells you why your pages aren’t showing up on Google and what to fix first, right from the PrestaShop back office. Its technical audit checks robots.txt, sitemap, noindex, and canonicals against a live sample of your own store — with a traffic-light verdict and a concrete list of problem URLs and their cause. And with Search Console connected, it checks Google’s real coverage URL by URL, with AI-assisted diagnostics in plain language.
Frequently asked questions
How long does it take Google to index a new product?
There’s no guaranteed timeframe: it can range from hours to weeks, depending on your store’s authority, internal linking, and the quality of the product page. If weeks go by and it still hasn’t shown up, it’s time to find the cause — not keep waiting.
Does being in the sitemap guarantee indexing?
No. The sitemap is a suggestion, not an order: it helps Google discover your URLs, but the decision to index them is still Google’s alone.
How do I check whether a specific URL is indexed?
The reliable source is Search Console’s URL Inspection tool, which gives you the real status and the reason behind it. Searching “site:yourdomain.com/url” on Google is only a rough approximation.
What does “discovered, currently not indexed” mean?
Google knows about the URL but has decided not to index it for now — typical of thin or duplicate content, or stores with weak overall signals. The fix is improving the page and site structure, not technical tricks.
Stop wondering why you’re not showing up. Get the diagnosis right inside your back office.
Discover Zeyvro Faro →Zeyvro builds PrestaShop 8 modules from a real store running in production. Unobfuscated code.