Why Is My Website Not Showing on Google? 6 Causes
Not on Google yet? Check time, noindex, robots.txt, canonicals, access errors and content quality, with Google's own wording for each Search Console status.
Elmrank editorial5 min readLast reviewed
On this page
On September 30, someone told r/SEO that a product page on their site had been "stuck on discovered – currently not indexed since early August". Search Console showed "Last crawled: N/A," and the page had internal links pointing to it. The top replies said to click Request Indexing. The owner answered: "I've requested indexing several times, but it's still stuck." Requesting indexing is often the first thing people try, and Google says plainly that "Submitting a request does not guarantee that the page will appear in the Google Index." Finding the cause works better.
The two-minute check
Search Google for site:yoursite.com. Google's own getting-started page suggests this query to "see if your pages are already indexed." If nothing comes back, the whole site has a problem. If some pages show and one doesn't, the problem is on that page.
Then open Search Console, paste the page's URL into the search bar at the top and read the status. That status tells you which of the causes below you're dealing with. If you haven't set up Search Console, that's the first job; you need to verify that you own the site before it shows anything.
What each Search Console status means
The wording in the middle column is Google's, from the Page indexing report help page.
| Status | What Google says | What to do |
|---|---|---|
| Discovered - currently not indexed | "Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl." | Check server speed and internal links; wait |
| Crawled - currently not indexed | "It may or may not be indexed in the future; no need to resubmit this URL for crawling." | Improve the page; don't keep resubmitting |
| URL marked 'noindex' | "If you do want this page to be indexed, you should remove the 'noindex' directive." | Remove the tag or header |
| Blocked by robots.txt | "Note that this does not guarantee that the page won't be indexed through some other means." | Fix the robots.txt rule if the page should show |
| Duplicate, Google chose different canonical than user | "A duplicate page must be similar to the canonical." | Compare the pages; fix the canonical tag or make the page distinct |
| Blocked due to access forbidden (403) | "Googlebot never provides credentials, so your server is returning this error incorrectly." | Allow Googlebot through your host or firewall |
| Soft 404 | The page "returns a user-friendly 'not found' message but not a 404 HTTP response code." | Return a real 404, or add real content |
The six causes, one by one
1. Time
Google's getting-started page says "It can take a few weeks for Google to notice a new site, or any changes in your existing site." If your site went live last week, waiting is a legitimate answer. Submitting a sitemap and linking to the new pages from pages that are already indexed helps Google find them.
2. A noindex tag
A noindex tag in the page's HTML, or an X-Robots-Tag header, tells Google to leave the page out. A common way it happens: a noindex set while the site was being built is still there after launch. URL Inspection shows it under "Indexing allowed?". Run "Test live URL" after you remove it, because the report shows what Google saw on its last crawl.
3. Blocked access
robots.txt can stop Googlebot from crawling a page, and a login wall, a 401 or 403 response or a firewall rule can stop it from loading one. Google's getting-started page suggests a simple test: "Make sure that you can access your site in an incognito window."
4. Canonical and duplicate pages
If two URLs show the same content, Google picks one. For the other it says: "Google has chosen the other page as the canonical for this page, and so will not serve this page in Search." That's correct behaviour when the pages really are duplicates. When they aren't, as with two products on the same template and short descriptions, make each page clearly its own.
5. Content quality
Google's guide to how Search works lists "The quality of the content on page is low" among the common indexing issues, and says "Indexing isn't guaranteed; not every page that Google processes will be indexed." For "Crawled - currently not indexed", the Page indexing report's help says only this: "The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling." Google doesn't give a reason for each page. Our reading is that content quality is the usual one when the page is crawlable and nothing technical blocks it, so that's where we'd look first. Google's getting-started page puts the test as a question: "Think about what makes your site unique, valuable, or engaging."
6. Nothing links to it
Google's first reason for missing a site is "Your site isn't linked to by other sites on the web." The same applies inside your site: a page that no menu, category or article links to is hard to find. In the r/SEO thread, one reply ran through the same list: noindex, whether the page is "orphaned", whether it's in the XML sitemap, and whether it's similar to other products, "you might be facing some canonical weirdness." The owner had ruled out the first three. For a page that's discovered but never crawled, Google's own explanation is a rescheduled crawl to avoid overloading the site, which points at the server and the crawl rather than the words on the page.
What our own sites show about timing
On the three sites we run, the first impression in Search Console came within two days of each property's first day of data, and the first click within five. We haven't confirmed each site's launch date, so read that as "days from when Search Console started counting," not days from launch. A new domain with no history may take longer, which is what Google's "a few weeks" allows for.
How we handle indexing
Indexing is part of the technical work in our plan. In the first month ($500) we audit the site and fix what blocks it: noindex and robots.txt rules, canonicals, speed, schema and site structure. From then on ($300 a month) we watch the Page indexing report, fix what new pages or updates break, and the monthly report shows your Search Console clicks and impressions. The technical SEO page has the details.
How we know this
Written by Elmrank editorial. Every source below was read on the date shown; the page was last reviewed on Oct 14, 2026.
- Google Search Central, Get your website on Google, accessed Oct 14, 2026
- Google Search Central, In-depth guide to how Google Search works, accessed Oct 14, 2026
- Search Console Help, Page indexing report, accessed Oct 14, 2026
- Search Console Help, URL Inspection tool, accessed Oct 14, 2026
- r/SEO, Product page stuck on "Discovered – currently not indexed" (comments by u/CaPpedDoG, u/Tomdv2), accessed Oct 14, 2026
- Elmrank, Search Console data for three sites we run (web search, final data, snapshot Oct 13, 2026), accessed Oct 14, 2026
Email us your site.
We reply within 12 hours with what we'd fix first. Then we run it for you, technical SEO and content: $500 for the first month, then $300 a month for up to 30 articles. You don't need any technical knowledge, and you can cancel any time.