ShipworkSite inspection
Checks

Crawlability

PaginationAre paginated pages set up right?Internal searchIs site search eating crawl budget?URL parametersAre parameters creating duplicates?Log analyserWhat does Googlebot actually crawl?Robots builderNeed a robots.txt file?Soft 404sAre pages “not found” but returning 200?JavaScriptCan crawlers see it without running JS?FreshnessIs my site quietly going stale?Robots.txtDoes robots.txt say what I think?

Indexing

Sitemap lastmodAre my sitemap dates valid?SitemapIs my sitemap actually fetchable?IndexingIs Google allowed to index my pages?CanonicalsIs Google indexing the wrong URL?Index signalsDo sitemap and index signals agree?Sitemap generatorNeed a sitemap.xml for my site?Bulk URL statusWhere does each of these URLs really land?Redirect builderNeed the redirect rules?RedirectsAre my URLs answering directly, over HTTPS?

On-page

Keyword ideasWhat are people searching for?SERP previewHow does my page look in Google?Content qualityAre your pages too thin or too alike?Image weightAre images slowing the page?CannibalizationAre pages competing with each other?On-page checkDoes the page use its target phrase?ImagesAre my images accessible and loading?Meta tag builderWhat should my title and share tags say?DuplicatesDo my pages compete for one query?

Links

Orphan pagesWhich pages can no link reach?Link graphHow deep do your pages sit?Anchor textDo links say what they point at?Outbound linksAre external links still alive?Broken linksAre internal links sending visitors nowhere?

Structured data

Rich resultsIs my markup eligible for a rich result?Structured dataIs my product schema valid?Schema coverageDo my key pages carry structured data?Social previewHow does my page look when shared?Schema vs pageDoes markup match the page price?Schema builderNeed valid JSON-LD?

International

Hreflang sitemapDo page and sitemap hreflang agree?HreflangDo my language versions link back?Hreflang builderNeed the hreflang tags?Page DoctorWhy is this page not doing well?Redirect planMy site has dead links — what redirects do I write?Sitemap diffIs anything missing from my sitemap?Robots simulatorWhat does my robots.txt actually block?Can Googlebot?Can Googlebot fetch this URL?
Every error, explainedGuides
Pricing Learn Error guides Run free audit

+1 free check

Welcome to Shipwork

Sign in free and your next check this month is on us.

Continue with GoogleContinue with email

We email you a 6-digit code. No password.

No card needed. Reports and watches follow you to any device.

How to find the noindex or block that keeps pages out of Google

You publish, you wait, and Search Console says "Discovered - currently not indexed" or the page simply never appears. Nothing on the site changed, nothing looks broken. Indexation fails silently more than any other SEO failure, because the causes are all invisible in your own browser: a noindex tag from a plugin, a header your host adds, a crawler block, or a page that answers an outside request with an error. Here is how to find which one you have.

ALLOWEDCrawled and allowedBLOCKEDNoindexed: excluded
One instruction decides: indexed or invisible.

What "not indexed" actually means

Search Console's page-report statuses form a pipeline, and each failure point has a different fix. Discovered - currently not indexed means Google knows the URL exists but has not scheduled a crawl: usually a crawl-budget or quality signal problem. Crawled - currently not indexed means Google fetched the page and decided not to index it: thin content, duplicate, or a quality judgment. Excluded by noindex tag and Blocked by robots.txt are instructions you sent, deliberately or not. The first two are Google's decisions; the last two are yours to fix, and they are the ones this article is about, because they are the ones nobody remembers setting.

StatusWho decidedWhere to look
Discovered - not indexedGoogle (crawl scheduling)Crawl budget, internal links, site quality
Crawled - not indexedGoogle (quality)Thin or duplicate content, canonicals
Excluded by noindexYou (page instruction)Meta robots tag, CMS settings, SEO plugin
Blocked by robots.txtYou (file instruction)robots.txt rules, hosting defaults

The four silent causes

  • A noindex meta tag left by a plugin or template. SEO plugins, staging-to-production migrations and " discourage search engines" checkboxes left flipped are the classic sources. The page renders perfectly; the tag sits one line into the head where nobody looks.
  • An X-Robots-Tag HTTP header. The same instruction delivered in the response header instead of the HTML: set by a CDN rule, a hosting default or a security plugin. View-source never shows it; only a header inspection does. Follow the X-Robots-Tag response-header walkthrough to inspect GET and HEAD responses and trace the rule adding it.
  • A robots.txt rule that swallows real pages. A staging leftover like Disallow: / under a named agent, or an over-broad prefix that catches /products along with /search. Shopify stores get extra risk from apps that edit the template.
  • The page errors for crawlers. A 403 from bot protection or a 500 on a cold code path reads to Google as an unusable page, which is indistinguishable from an instruction not to index.
Your browser cannot see any of these

A noindex tag, a response header and a crawler block are all invisible to a logged-in visitor on their own network. Every one of them is obvious to a cold outside request, which is exactly what the check does.

"Discovered - currently not indexed"

This status deserves its own paragraph because the advice around it is mostly wrong. It does not mean Google dislikes the page; it means the URL is known but the crawl is not scheduled yet. On a new or small site it is usually crawl-budget triage: Google allocates attention based on how many links point at a URL and how the whole site performs. The practical fixes are internal linking (orphans and deep pages suffer most), pruning near-empty pages out of the crawl, and patience: not resubmitting the same URL repeatedly, which changes nothing.

How to find your blocker in a minute

Search Console tells you the status per URL but not the mechanism. The fast path: run the free indexing check. Paste your address and Shipwork fetches a set of your key pages from outside your network, reading the same signals a crawler reads first: the raw HTML meta robots, the X-Robots-Tag header, robots.txt rules, and the response status each page returns. It reports which pages are told not to index, which are blocked, and which error out, so you know whether to fix a tag, a header, the file or the firewall. Free, no signup, nothing stored.

Related: Shopify robots.txt, line by line · crawl budget on Shopify · sitemap fetch errors

Find out if this is happening to you

Shipwork fetches your key pages from outside your network and reads the exact signals a crawler reads first: meta robots, X-Robots-Tag, robots.txt rules and response status, then names which page is blocked by what. Free, no account, no signup. Paste your store address.

Check my indexing

Questions

How do I check if a page is indexed?
Search for the exact URL, or use the URL Inspection tool in Search Console. Both tell you the current state; neither tells you why. That is what the signals in the page source and headers are for.
What is the difference between crawled and discovered, not indexed?
Discovered means Google knows the URL but has not crawled it yet: a scheduling and budget signal. Crawled means Google read the page and chose not to index it: a quality or duplicate-content judgment.
Does noindex pass PageRank?
A noindex page is eventually dropped from the index, and its links stop counting the way links to indexed pages do. Remove noindex from pages you want ranking, or remove the pages entirely.
Can robots.txt cause "Discovered - not indexed"?
Not directly. Robots.txt prevents crawling, which shows as "Blocked by robots.txt" instead. But heavy blocking elsewhere on the site can shape crawl-budget decisions overall.

Keep reading