Guide
Why isn't Google indexing my website?
If Google isn't indexing your site, the cause is usually one of a short list: the site is new and simply hasn't been crawled yet, something is telling Google not to index it, technical problems are blocking the crawl, or the pages exist but Google has judged them not worth indexing. The fix starts with one search and one free tool, both below.
By Tyakiyon · Updated June 12, 2026 · 4 min read
Step one: confirm what's actually happening
Search Google for site:yourdomain.com. If results appear, you're indexed and your real problem is ranking, which is a different article, our SEO cost guide is the relevant one. If nothing appears, you have an indexing problem, and the next stop is Google Search Console, which is free and tells you most of what's wrong in plain-ish language.
In Search Console, paste your homepage into the URL Inspection tool. It will say whether the page is indexed, and if not, usually why: not crawled yet, blocked, redirected, or crawled but not selected. That one sentence narrows everything that follows.
If the site is just new
New domains wait. Google has to discover the site, crawl it, and decide to include it, and for a brand-new domain with no links pointing at it, that can take days to a few weeks. This is the most common 'problem' and it isn't one.
You can shorten the wait: verify the site in Search Console, submit a sitemap, and request indexing for your most important pages. Links from anywhere real, your Google Business Profile, a supplier's directory, a local association, give Google more doors to find you through. After that, patience is the tool, frustrating as that is to hear.
If something is telling Google to stay out
Three switches commonly get left in the wrong position. A noindex tag in the page's code, sometimes left over from development, tells Google to skip the page even when it crawls fine. The robots.txt file can block crawling of pages or the whole site, the same way it's meant to block private sections. And site platforms often have a 'discourage search engines' checkbox that someone ticked during the build and forgot.
These produce a distinctive symptom: Search Console says 'blocked' or 'excluded by noindex' explicitly. The fix is flipping the switch, then requesting indexing again. If your site was built by someone else and you can't check, this exact situation is a thing our free website audit catches quickly.
If Google crawled your pages and skipped them anyway
Search Console's 'Crawled, currently not indexed' status is the frustrating one: Google saw the page and chose not to keep it. This usually signals a value judgment. Pages with very little text, pages duplicated from other pages, or templated pages that differ only by a city name in the title commonly get this treatment, especially on newer sites that haven't earned trust yet.
The honest fix is making the pages worth keeping: real content that answers something, consolidated instead of duplicated, on a site that's accumulating signals of being a real business. There's no submit button for that part, and providers who promise instant indexing for skipped pages are selling around a judgment that has to be earned back.
The checklist, in order
Run these in sequence and stop when one explains your situation:
| Check | Where | If it's the problem |
|---|---|---|
| site:yourdomain.com shows results? | You're indexed; this is a ranking question instead | |
| Search Console verified, sitemap submitted? | search.google.com/search-console | Do both; they're free and prerequisite to everything else |
| URL Inspection verdict on key pages | Search Console | The verdict text points at the matching section above |
| noindex tags or robots.txt blocks? | Page source, yourdomain.com/robots.txt | Remove, then request indexing |
| Platform privacy or discourage setting? | Your site builder's settings | Untick, republish, request indexing |
| Thin or duplicated pages skipped? | Search Console page report | Improve or consolidate the content; wait |
Where we can help
Want a straight answer for your case?
Tell us where you are. We reply the same day with numbers, not a pitch.
FAQ
Quick answers.
The short versions, for the questions this guide gets asked most.
Anywhere from a couple of days to a few weeks, with a verified Search Console and a submitted sitemap pulling the timeline toward the short end. Months of nothing means something is blocking, not waiting.
No. Ads and the organic index are separate systems, and ad spend buys no indexing favors. The free tools, Search Console and a sitemap, are the actual levers.
New pages on an established site usually index within days if they're linked from existing pages and in the sitemap. Orphan pages, linked from nowhere, can wait indefinitely; give every page a parent.
Extreme slowness or frequent downtime can reduce how much Google crawls, though it more often hurts ranking than indexing outright. Either way it's worth fixing for the humans.
No. Indexed means you're in the library; ranking decides which shelf. Most sites that fix indexing then begin the longer ranking conversation, which is what SEO actually is.
Most indexing blocks are an hour of work for someone who's seen them before. It's part of what [our SEO service](/services/seo/) covers, and the audit will tell you if your case is the easy kind.