Why Your Website Is Not Showing Up on Google (and How to Get Indexed)

Three different problems that produce the same symptom

Not indexed means Google does not have the page, so no amount of content work will help until the block is cleared. Not ranking means Google has the page but prefers others. A manual action means Google has penalized the site and named the reason. Each has its own fix, and applying the wrong one wastes the budget.

The reason this matters commercially is that the three problems have wildly different costs. Clearing an indexing block is often a single line of code and free. Improving a ranking position is months of content, technical work and earned links. Recovering from a manual action is a specific remediation and a reconsideration request. An agency that sells you the second when you have the first is charging you for a year of work that a five-minute fix would have solved.

Search Console draws these lines for you rather than leaving them to interpretation, reporting each URL under a named status such as "Page is indexed", "URL marked noindex" or "Discovered - currently not indexed"⁴. Owners almost always assume they have the ranking problem, because that is the version everyone talks about. In practice, on a site that is genuinely invisible rather than merely low, the indexing explanation is far more common, and it is also the one nobody checks first. The order below is deliberate: rule out the cheap explanation before you buy the expensive one.

One clarification worth making early. Being absent for your own business name is a very different signal from being absent for a competitive service term. If searching your exact business name plus your city does not return your site, that points hard at indexing. If your name works but "roofing contractor Naples" does not, you are indexed and you have a ranking problem.

How to check whether Google has indexed your site

Use the URL Inspection tool in Google Search Console. It reports the current index status of a specific page, lets you test the live URL, and lets you request a crawl. A site: search is a quick rough signal that something exists, but it will not tell you why a page is missing.

Google's Search Console documentation points to the URL Inspection tool as the way to see the current index status of a page and to debug page-level indexing issues³. That is the check worth running, because it does something a search never does: it names the reason. There is a real difference between knowing a page is absent and knowing it is absent because a noindex header is being served.

A site: search still has a place as a thirty-second sanity check. If it returns nothing at all for your domain, you have a serious, site-wide problem and you can stop guessing. What it cannot do is explain anything, and it is not the check Google's own documentation points to, so treat it as a smoke alarm rather than a diagnosis.

The report that gives you the whole picture is the Page indexing report, which groups every URL by status. Google names the statuses precisely, including "Discovered - currently not indexed", "Crawled - currently not indexed", "URL blocked by robots.txt", "URL marked noindex", "Soft 404", "Duplicate, Google chose different canonical than user", and the revealing "Indexed, though blocked by robots.txt"⁴. Read the status before forming a theory. The status is the theory.

1. Search your exact business name plus your city. If your own site does not appear for its own name, this is an indexing or penalty problem, not a ranking one.
2. Open Search Console and inspect a specific URL. The URL Inspection tool reports the current index status and the reason a page is not indexed.
3. Read the Page indexing report. Group your URLs by status. The status name tells you which of the three problems you have.
4. Check for a manual action. Search Console reports manual actions explicitly, with the reason. No entry means no penalty.
5. View source on a key page. Confirm the headings and body copy exist in the raw HTML rather than being assembled in the browser.

If you do not have Search Console set up, that is the first job and it is free. If you would rather see the whole technical picture in one pass, our free SEO audit fetches your pages the way a crawler does and reports what came back, and our technical SEO services cover the remediation when something is genuinely broken.

New-site delay, indexing block, or penalty: telling them apart

A new site that is discovered but uncrawled is usually waiting rather than broken. A block is a specific directive Search Console names. A penalty appears as a manual action with a stated reason. Search Console distinguishes all three for you, which is why guessing is never necessary.

Start with the delay, because it is the least alarming and the most misdiagnosed. Google describes "Discovered - currently not indexed" as a URL it has found but not yet crawled, and notes that it may have rescheduled a crawl that was expected to overload the site⁴. The industry has turned this status into shorthand for thin content, and Google's own description points at crawl scheduling and server capacity at least as often. Google states no action is required.

"Crawled - currently not indexed" is a genuinely different signal. Google fetched the page and chose not to index it, and the report says it may or may not be indexed later, with no need to resubmit⁴. This one is worth taking as feedback about the page rather than the server. It is where content quality, duplication and near-identical templated pages actually show up.

A block is unambiguous, which is the good news. If the status reads "URL marked noindex" or "URL blocked by robots.txt", you are not waiting on anything, and the fix is in your own codebase. A manual action is equally unambiguous: Search Console names it and states the reason, and there is a documented reconsideration path once you have fixed the cause. If there is no manual action listed, you do not have a penalty, no matter what a cold-calling agency told you.

The practical triage order is delay, block, penalty, then ranking. Work it in that sequence and you will spend the least money, because it moves from free to expensive, and the free explanations are the more common ones.

The blocks that keep sites out of the index

Four causes account for most genuinely invisible sites: a noindex rule left over from staging, a robots.txt disallow, a canonical tag pointing somewhere else, and content assembled in the browser. The first two are frequently combined in a way that guarantees the outcome nobody wanted.

The stray noindex is the classic. A site is built on staging with a site-wide noindex to keep it out of search, then goes live and the rule ships with it. The site looks perfect, the business launches, and it is invisible for months because nobody thinks to view the source. It costs one line to fix and it is the single most expensive line of code in this industry.

Now the part that catches even careful teams. Google is explicit that for a noindex rule to be effective, the page must not be blocked by robots.txt and must otherwise be accessible to the crawler⁵. Block the URL in robots.txt and the crawler never fetches the page, never sees the noindex, and the URL can still appear in results if other pages link to it. Doing both feels like belt and braces. It is closer to locking the door and posting the key through it.

That leads to the misconception underneath all of this. Robots.txt is not a way to keep a page out of Google. Google states it directly and adds that the URL and information such as anchor text from links can still appear in search results⁶. There is even a Search Console status for exactly this outcome, "Indexed, though blocked by robots.txt"⁴. If you want a page out of search, Google names the alternatives: a noindex rule on a crawlable page, password protection, or removing the page.

The fourth cause is rendering. If your content is assembled in the browser rather than delivered in the server response, crawlers that do not execute JavaScript receive very little. Googlebot does render, in a queued phase after crawling⁷, which is why this shows up as slow or partial indexing on Google and near-total absence elsewhere. We covered the full test and the fixes in why AI search engines cannot read a JavaScript website.

• Check view-source for noindex on your live site, not your staging site.
• Never combine a noindex rule with a robots.txt disallow on the same URL.
• Confirm canonical tags point at the page itself, not at the homepage or a staging domain.
• Confirm your headings and body copy exist in the raw HTML.
• Re-run these checks after every redesign, migration or platform change.

How to get your pages indexed

Clear the block first, because nothing else matters while a directive is telling Google to stay away. Then make the pages easy to find: a working sitemap, internal links from pages that are already indexed, and a request through the URL Inspection tool for the pages that matter most.

Order matters more than effort here. Requesting indexing on a page that still carries a noindex rule achieves nothing, and it is the most common wasted afternoon in this whole topic. Fix the directive, confirm the fix in view-source on the live URL, and only then ask Google to look again.

Internal links do more work than owners expect. A page with no links pointing at it is a page Google has little reason to prioritize, which is often what sits behind a "Discovered" status. Link new pages from pages that are already indexed and already get crawled, which usually means your homepage, your main service pages and your most-visited posts. This costs nothing and it is more reliable than resubmitting a sitemap.

Set expectations honestly on timing. Google publishes no indexing timeframe, and for "Discovered - currently not indexed" it explicitly says no action is required and gives no schedule⁴. Anyone offering guaranteed indexing within a set number of days is describing something Google does not commit to. What you control is removing every reason not to index, and then making the page genuinely worth indexing.

1. Remove the block. Delete the noindex rule, the robots.txt disallow, or the wrong canonical. Verify on the live URL, not locally.
2. Confirm the page returns 200 and contains its content. Check the raw HTML has the headings and body copy, not just the shell.
3. Submit an accurate sitemap. It should list only canonical, indexable URLs. A sitemap full of noindexed pages sends a confusing signal.
4. Add internal links from indexed pages. Link the new page from your homepage or a strong service page so it is discoverable by crawling, not just by sitemap.
5. Request indexing for the priority URLs. Use URL Inspection for the handful of pages that matter commercially. Do not bulk-submit the whole site.
6. Re-check the status in a week. Read the Page indexing report again and confirm the status has changed rather than assuming it has.

Indexed but still not ranking is a different problem

If Search Console says your pages are indexed, the technical work is done and the remaining problem is competitive. No amount of resubmitting, sitemap editing or indexing requests changes a ranking position. What changes it is relevance, authority and the specific surface you are trying to appear on.

This is the point where a lot of money gets spent on the wrong thing. Once a page is indexed, Google is willing to show it and has decided other pages serve the query better. That is a judgment about relevance and prominence, not a technical fault, and the fixes look nothing like the ones above.

What the fixes actually are depends on the surface. For map results, the factors are local and the work is your profile, proximity and prominence, which we cover in why a Naples business fails to appear in the map pack. For organic results it is relevance and authority built over months. For speed-sensitive gains, site speed and Core Web Vitals is the measurable lever.

One honest caveat about expectations. A young domain with few referring domains is not being penalized, it is simply unestablished, and the SE Ranking data on domains under 2,500 referring domains reflects how much that shortfall costs across surfaces². That is a reason to be patient with a correct strategy, not a reason to keep re-running technical fixes on a site that is already indexed and already fine.