How to Get a New Website Indexed by Google: A Practical Checklist

You launched a new business website, typed its name into Google, and nothing came up. That is normal. A brand-new domain has no history, few or no links pointing to it, and Google has not yet decided which of its pages are worth storing. This checklist walks through what actually has to happen before a page can appear in search, and the specific checks you can run so nothing on your side is blocking it.

Discovery, crawling, indexing and ranking are four different steps

People often say “my site isn’t on Google” when they mean one of four separate problems. Knowing which one you have saves hours.

1. Discovery. Google has to learn that a URL exists. It finds URLs by following links from pages it already knows, from sitemaps you submit, and from URLs you inspect in Search Console.
2. Crawling. Googlebot requests the URL and downloads the HTML (and, where needed, renders JavaScript). If your server returns an error, redirects in a loop, or robots.txt disallows the path, crawling fails.
3. Indexing. Google analyses the page and decides whether to store it. Pages can be crawled but not indexed, for example when they carry a noindex tag, duplicate another page, or look too thin to be useful.
4. Ranking. Only indexed pages can rank. Where they rank depends on relevance, quality and competition. Being indexed does not mean you will get traffic.

Most of what you control sits in steps one to three. Ranking takes useful content and time.

Step 1: Verify your site in Google Search Console

Search Console is free and is the only place Google tells you directly how it sees your pages. Add a Domain property (it covers http, https, www and non-www together) and verify it with the DNS TXT record Google gives you. If you cannot edit DNS, a URL-prefix property verified with an HTML tag or file works too, but only covers that exact prefix.

Data does not appear instantly. Expect the Pages and Performance reports to stay mostly empty for the first days after verification.

Step 2: Check that your pages can actually be crawled and indexed

Before asking Google for anything, rule out the common self-inflicted blockers. Open each important page (home, main service pages, contact, blog) and check the following.

HTTP status

Each page should return 200 OK. In Chrome, open DevTools → Network, reload, and look at the first document request. A 301 to the right URL is fine; a 404, 500 or a chain of several redirects is not.

robots.txt

Visit yourdomain.com/robots.txt. A line like Disallow: / under User-agent: * blocks the whole site. Website builders sometimes add this while a site is “in development” and forget to remove it.

noindex

View the page source and search for noindex. A tag like <meta name="robots" content="noindex"> tells Google not to index the page. Many builders have a “hide from search engines” switch that adds it site-wide; check your SEO or privacy settings.

Canonical tag

Search the source for rel="canonical". It should point to the page itself, using your preferred version of the domain. Example: on https://www.example-plumbing.com/services/ the canonical should be that same URL, not the homepage and not the http version. A wrong canonical asks Google to index a different page instead.

Content in the HTML

If your main text only appears after JavaScript runs, Google usually renders it, but rendering can be delayed. Server-rendered or static HTML is the safest option for important pages.

Step 3: Create and submit an XML sitemap

A sitemap is a file listing the URLs you want indexed. It does not force indexing, but it helps Google discover pages, especially on a new site with few links. Most platforms (WordPress with an SEO plugin, Shopify, Wix, Squarespace) generate one automatically at /sitemap.xml. Google’s guide on how to build and submit a sitemap explains the format.

Check your sitemap before submitting it:

• It lists only canonical, indexable URLs that return 200.
• It does not include login, cart, admin or thank-you pages.
• URLs use the same protocol and host as your canonical tags.

Then add a line to robots.txt such as Sitemap: https://www.example-plumbing.com/sitemap.xml, and submit the sitemap URL in Search Console under Sitemaps. The report will show whether Google could read it and how many URLs it discovered.

Step 4: Use URL Inspection and request indexing

Paste a URL into the search bar at the top of Search Console. URL Inspection tells you whether the URL is on Google, which canonical Google chose, when it was last crawled and whether indexing is allowed.

1. Click Test live URL to see what Googlebot gets right now. Review the screenshot and the rendered HTML to confirm your content is visible.
2. If the live test passes, click Request indexing. This puts the URL in a priority crawl queue.
3. Do this for your most important pages only: the homepage and a handful of key service or product pages. There is a daily quota, and repeated requests for the same URL do not speed things up.

Requesting indexing is a request, not a guarantee. Google may still crawl later or decide not to index a page.

Step 5: Give Google reasons to come back

Discovery on a new site is mostly about links. Link every important page from your navigation or from other pages; an “orphan” page that nothing links to is easy to miss. Add your site to your Google Business Profile if you have one, to relevant industry or local directories, and to your social profiles. Publishing new, useful pages on a regular schedule also gives Googlebot a reason to revisit.

Google’s SEO Starter Guide is a good reference for the fundamentals behind this step.

Troubleshooting common Search Console statuses

• Discovered – currently not indexed: Google knows the URL but has not crawled it yet. Common on new sites. Improve internal links and wait.
• Crawled – currently not indexed: Google fetched it and chose not to index it for now. Make the page more substantial and clearly different from your other pages.
• Excluded by ‘noindex’ tag: remove the tag or turn off the builder’s “hide from search” option.
• Duplicate, Google chose different canonical: check your canonical tags and whether two URLs show the same content (for example with and without a trailing slash).
• Blocked by robots.txt: edit the Disallow rule, then use URL Inspection again.
• Server error (5xx) or Not found (404): fix the page or redirect it to the correct URL.

Validation checklist

• Search Console property verified (preferably a Domain property).
• Key pages return 200 and use one consistent domain version.
• No site-wide Disallow: / and no unintended noindex.
• Self-referencing canonical tags on every important page.
• Sitemap at /sitemap.xml, referenced in robots.txt and submitted in Search Console.
• Live URL test passes for the homepage and main pages; indexing requested once.
• Every page reachable through internal links.

A realistic note on timing

Nobody can promise when, or whether, Google will index a page. For many new sites the homepage appears within days to a few weeks once the checks above pass, but deeper pages can take longer, and some pages may never be indexed if Google does not see enough value in them. Use the Pages report in Search Console as your source of truth instead of searching for your site manually.

Once your site is indexed, the next question is what to publish. Our guide on how to find SEO blog topics customers actually search for covers that, and if you serve more than one country, read multilingual SEO for small businesses.