Answers

Why your new site is not indexed (and how to fix it)

A brand new site is not indexed for one of three reasons: Google has not discovered the pages yet, something on the site is actively telling Google to stay out, or the site is too new and too thin for Google to commit it to the index. The single most common cause is a leftover noindex instruction carried over from the staging environment that quietly suppresses every page after launch.

Indexing is not automatic and it is not instant. Google has to find your URLs, fetch them, render them, and then decide they are worth storing. A new domain with no inbound links and no submitted sitemap can sit invisible for days or weeks before the first crawl even happens.

Discovery, crawling, and indexing are three different steps

Most people asking why is my new site not indexed treat indexing as a single switch. It is three separate steps, and a new site can stall at any one of them.

• Discovery. Google learns a URL exists, usually from a sitemap, an internal link, or a link from another site that already gets crawled.
• Crawling. Googlebot fetches the page, reads its HTML, and follows any instructions it finds in the markup or the response headers.
• Indexing. Google renders the page, judges whether it is useful and distinct, and decides whether to store it at all.

If you skip discovery, nothing else happens. If crawling is blocked, Google never reads the content. If the content is thin, Google may crawl it and still decline to index it. Each failure looks identical from the outside: you search for your own pages and find nothing.

The usual culprits, in the order we check them

A leftover noindex tag

Staging sites are almost always set to block search engines so half-built pages do not leak into results. When the site goes live, that block is supposed to come off. Often it does not. A single noindex meta tag in the head, or an X-Robots-Tag in the HTTP response, will keep an otherwise perfect site out of the index entirely, and a normal visitor will never see it.

A blocking robots.txt

A robots.txt file that disallows crawling stops Googlebot before it reads a word. This is common when a developer copies a staging configuration into production without changing it. The pages can still show as discovered but never get fetched.

No sitemap and no verified property

A new domain has no reputation and nothing linking to it, so Google has no trail to follow. Without a submitted sitemap in Google Search Console, discovery depends on Google stumbling across your site on its own, which is slow. The sitemap is how you hand Google the full list of your URLs on day one instead of waiting.

Thin or duplicated content

If Google crawls a page and files it under Discovered, currently not indexed or Crawled, currently not indexed, the problem is rarely technical. Google found the page and chose not to keep it. That usually means the page is thin, nearly identical to other pages on the site, or offers nothing a reader could not get elsewhere.

Bad canonicals and rendering

A canonical tag pointing at the wrong URL tells Google to index a different page instead of this one. Content that only loads after JavaScript runs can also be missed if the page does not render cleanly for the crawler. Both are easy to introduce by accident and invisible unless you inspect the rendered HTML, not just the source.

How to diagnose it yourself

You do not need expensive tools to find the cause. You need Google Search Console and a few minutes.

• Open the URL Inspection tool in Search Console and paste a page that is missing. It will tell you whether the URL is on Google and, if not, why.
• Read the exact status. Blocked by robots.txt, Excluded by noindex tag, and Discovered currently not indexed each point to a completely different fix.
• View the page source and search for the word noindex. Then open your robots.txt at the site root and look for a Disallow line that blocks crawling.
• Confirm a sitemap is submitted and that it returns the real URLs you expect, not a redirect, a login wall, or an error.

If the status is a hard block, removing the block and requesting indexing usually resolves it quickly once Google recrawls. If the status is a quality judgment, no button fixes it. The page has to earn its place in the index.

When to wait and when to act

Patience is a real part of the answer. A site that launched this week and shows no indexing errors in Search Console is often just early. Google crawls new domains cautiously, and the first full pass can take time even when everything is set up correctly.

Acting makes sense the moment the diagnosis shows a block, a missing sitemap, a wrong canonical, or a page Google crawled and rejected. Those are not waiting problems. Waiting longer on a noindex tag changes nothing at all.

How we handle indexing on sites we build

Because Ninetyfifth Marketing only does SEO on sites we build ourselves, indexing is not an afterthought we inherit from someone else. We launch with a correct robots.txt, a clean sitemap submitted to Search Console, no stray noindex from staging, and self-canonicalizing pages. We verify each core page in the URL Inspection tool rather than assuming the launch worked.

That does not promise a result, and no honest agency can. It removes the self-inflicted reasons a new site stays invisible, so the only remaining variable is whether the content itself deserves to be indexed. If you want the commercial details, read /services/seo/ and /pricing/.