Add Your Website to Google: Search Console, Step by Step

You add a website to Google by publishing it and letting Googlebot find it, then, optionally, verifying it in Google Search Console so you can submit a sitemap and ask Google to crawl specific pages. Google has no registry of web pages and no form that guarantees a place in its index: it finds new sites mainly by following links from pages it already knows and by reading sitemaps. Our take: do the Search Console steps anyway, because they take twenty minutes and turn “I hope Google found my site” into something you can see, but do not pay anyone to “submit your site to Google,” because Google says it does not accept payment to crawl a site more often or to rank it higher.

For a small business this usually comes right after setting up a Google Business Profile, and the two are easy to confuse. This guide covers how Google finds a new site, how to verify it, how to submit a sitemap, what “Request indexing” really does (with Google’s own limits), and how to check what is indexed. Every claim comes from Google’s documentation at developers.google.com/search and support.google.com/webmasters, as it read in November 2026.

How Google finds a new website

Google’s explanation of how Search works describes three stages: crawling (downloading text, images and video from pages it has found), indexing (analyzing and storing them in the Google index) and serving results. Not every page makes it through all three.

On discovery, Google says it has no central registry of web pages, so it keeps looking for new and updated ones. It finds URLs by following links from pages it already knows, such as a category page that links to a new post, and from sitemaps site owners submit. Googlebot decides which sites to crawl, how often and how many pages to fetch from each, and it renders pages with a recent version of Chrome, so content loaded by JavaScript can be seen.

Three things in that description matter for a new site:

• Links are the main road in. Google’s SEO starter guide says it mainly finds pages through links from pages it has already crawled, often links from other websites. A brand-new site with no links pointing to it and no sitemap gives Googlebot nothing to follow.
• It is slow and not guaranteed. Google’s get on Google guide says it can take a few weeks for Google to notice a new site, or changes to an existing one. Google’s URL Inspection help adds that submitting an indexing request “does not guarantee that the page will appear in the Google Index.”
• You can be blocked by accident. Pages behind a login may not be accessible to Googlebot, and robots.txt rules can block crawling. The get-on-Google guide lists reasons a site can be missed, such as being built with specialized technology that is hard to crawl, blocking Google for some reason, or having a login page, and suggests checking that you can open your site in an incognito window.

Step 1: check whether your website is already on Google

Before you do anything, search for site:yourdomain.com (use your own domain). If pages appear, Google has indexed some of them. Google’s own caveat is that the site: operator does not necessarily return every indexed URL, so a short list does not prove the rest is missing. If nothing appears and the site is more than a few weeks old, move on to the steps below, and look at the common blockers near the end.

Step 2: add your website to Google Search Console

Search Console is Google’s tool for seeing how your site appears in Search. Google’s property help page lists the steps: open the property selector (or the welcome page), choose Add property, pick a property type, then pick a verification method. You can choose “Verify later” and finish another day. Adding a property starts data collection even before it is verified, and data usually appears within a few days.

The decision that confuses most people is the property type:

	Domain property	URL-prefix property
What you enter	Your domain, such as example.com	The full prefix, such as https://example.com/
What it covers	Per Google, all protocol (http/https) and subdomain variations	The URLs under the exact prefix you enter
Verification	DNS record only	Several methods
Best for	Seeing the whole site in one place	When you cannot edit DNS, or you only manage part of a site

Our take: use a Domain property if you can reach your domain’s DNS settings, because one property then covers http, https, www and any subdomain, and you will not wonder why your numbers are split across four properties. If you cannot (some website builders and agency-managed domains make this hard), a URL-prefix property for the exact address your site uses works fine.

How to verify ownership

Google’s verification help page is explicit about what works where:

Method	Domain property	URL-prefix property
DNS record at your domain name provider	Yes (the only way)	Yes
HTML file upload	No	Yes
HTML tag in your home page	No	Yes
Google Analytics tracking code	No	Yes
Google Tag Manager container snippet	No	Yes

Some details save you a repeat visit. Verification lasts only as long as Search Console can keep confirming your token: it periodically checks that the token is still present and valid, and if a problem is not fixed your permissions expire after a grace period. For DNS verification, do not remove the record after it succeeds, or you may lose verification. Removing the HTML file cancels verification. You can add more than one verification method (our suggestion: do, so a template change that drops a tag does not lock you out), and verifying a URL-prefix property through the domain name provider method also auto-verifies the Domain property. Several people can verify the same property, and if every verified owner loses access, all users lose access, so we would keep at least two owners for a business.

Step 3: submit a sitemap

A sitemap is a file that lists the URLs on your site that you care about. Google’s sitemap overview is honest that you may not need one: a site of roughly 500 pages or fewer that you want in results, thoroughly linked internally so crawlers can reach every important page from the home page, likely does not need one. You might need one if your site is new with few external links, or is large. Google also says a sitemap “doesn’t guarantee that all the items in your sitemap will be crawled and indexed.” If you use WordPress, Wix or Blogger, your platform may already generate one.

The format facts from Google’s sitemap build guide:

• Google supports XML, RSS/Atom and plain text (one URL per line).
• One sitemap can hold up to 50 MB uncompressed or 50,000 URLs; larger sites split them and use a sitemap index.
• Use fully qualified, absolute URLs for the canonical pages you want in results, and host the file in the site root.

To submit it, follow the Sitemaps report help:

1. Post the sitemap on your site, ideally at the root.
2. Test it with a live URL inspection and confirm that Page fetch says Successful.
3. Open the Sitemaps report, paste the sitemap URL into Add a new sitemap and submit it. You cannot upload a sitemap file directly to Google, and you need owner permissions on the property to use the report.

If you do not have owner permissions, Google says you can list the sitemap in your robots.txt file instead. The report shows one of three statuses: Success (fetched and processed with no errors), Has errors (fetched, but some errors occurred; URLs that parsed without errors are queued for crawling) or Couldn’t fetch (possible causes include a robots.txt block, a 404, a temporary server problem or low crawl demand). Google is explicit that “there is no guarantee that a page URL discovered in a sitemap has been or will be crawled or indexed.”

Step 4: use URL Inspection and Request indexing, within Google’s limits

For one important page, such as a new home page or a service page, the URL Inspection tool is the faster route. It shows Google’s indexed version of a URL, and a live test fetches the page in real time. If the result is “URL is on Google,” the page is eligible to appear in Search, though Google says that is not guaranteed. If it says “URL is not on Google,” Google says the URL won’t appear in Search results. Google also notes that the live test only confirms that Google’s inspection crawler can access the page for indexing, and that no test can guarantee a page will be included in the index.

Request indexing asks Google to crawl the inspected URL. Google’s recrawl page and the tool’s help page set the limits:

• You must be an owner or full user of the property, and you can only request URLs you manage.
• Google enforces a quota: the help page says there is a daily limit of inspection requests for each property that you own. The pages we read do not give the number.
• Submitting the same URL repeatedly does not make it crawl faster.
• You cannot request indexing if the page is considered non-indexable in the live test (per the URL Inspection help page).
• Crawling can take “a few days to a few weeks,” indexing “typically takes only a day or so, but can take much longer in some cases,” and a request does not guarantee the page will appear in results, quickly or at all.

For many pages, Google recommends a sitemap (with <lastmod> dates) over request-by-request submission. And if you use a hosted platform such as WordPress or Blogger, Google’s recrawl page says that in most cases the platform submits new content to search engines automatically, so check the platform’s support articles before you spend your daily quota.

Why a page does not show up: the common blockers

When Search Console says a page is not indexed, read the reason before you re-submit. Google’s Page indexing report says “not indexed” is not necessarily bad, and that you should not expect every URL to be indexed. The reasons you will see most:

• Discovered, currently not indexed. Google found the URL but has not crawled it yet.
• Crawled, currently not indexed. Google crawled it and chose not to index it. Google says this is common and does not necessarily indicate a problem, and for an important page it suggests using URL Inspection to look for issues.
• URL marked noindex. The page tells Google not to index it. Fine if intended, a disaster if a staging setting survived the launch. Remove the directive if you want the page indexed.
• Blocked by robots.txt. Google’s robots.txt introduction says robots.txt controls which URLs crawlers may fetch and is “not a mechanism for keeping a web page out of Google,” and its noindex guide adds that if a page is blocked in robots.txt, the crawler never sees a noindex rule on it.

Duplicate pages are another reason: Google’s report says it does not serve duplicate pages, and that is working as intended, not an error.

What a Google Business Profile does not do for your website

This is the part local business owners get wrong. A Business Profile is a listing for Search and Maps with your name, address or service area, hours and reviews. A website is indexed through crawling. They are separate systems, and Google’s get-on-Google guide treats them as separate things: it says “Consider claiming your Business Profile” as its own suggestion, apart from its advice on making sure your site can be crawled.

None of the Google pages we read says that adding a website link to a profile gets that website indexed, so do not count on it. What the profile and the site do share is data: the name, address and phone on your site, your Business Profile website link and your directory listings should agree, and LocalBusiness schema markup is one way to state those details on the page in a form machines read. Our free NAP checker shows what the open web says about them. For what to do on the page itself, see on-page local SEO.

Google’s Business Profile ranking help also states that there is no way to request or pay for a better local ranking on Google, so no listing or service can buy the website a shortcut. And if you are asking whether AI assistants can read your site, that is a different question from whether Google Search has indexed it; our free AI visibility checker looks at robots.txt and crawler access for that.

A 20-minute checklist

• Make sure the site is public: no login wall, no noindex tag left over from staging, no blanket Disallow in robots.txt.
• Search site:yourdomain.com to see what is already indexed.
• Add a Domain property in Search Console (or a URL-prefix property if you cannot edit DNS) and verify it, keeping the DNS record or file in place.
• Generate a sitemap (many platforms do it for you), test it, and submit it in the Sitemaps report.
• Inspect your home page and your top service page, and request indexing for each once.
• Link to the site from places you control: your Business Profile, your social profiles and your directory listings.
• Check the Page indexing report in a week or two, and read the reasons before you re-submit anything.

Google may change any of these tools, quotas and limits, so if a screen no longer matches this guide, trust Google’s current help page over ours.