How to submit a website to Google (2026 guide)

Submitting a website to Google is the process of verifying the site in Google Search Console and giving Google a sitemap of the URLs you want crawled. It is optional. Google's own documentation says the vast majority of pages in its results are found by its crawlers, not submitted by hand. A brand-new domain is the exception that makes submission worth doing: nothing links to it yet, so a sitemap is the clearest way to tell Google the site exists.

This guide covers a whole new site, from property setup to what to expect afterward. Every Google rule below was checked against Google Search Central and Search Console Help in September 2026. Two numbers to keep in mind: one sitemap file holds at most 50,000 URLs or 50MB uncompressed, and Google says crawling "can take anywhere from a few days to a few weeks."

Do you need to submit your website to Google at all?

No, you don't strictly need to submit your website to Google, because Google discovers most pages on its own. Google describes three ways it learns about a URL: it has crawled the page before, it follows a link from a page it already knows, or it reads a sitemap you gave it. A new domain fails the first test and usually the second. That leaves the sitemap.

If your site runs on a hosted platform such as Blogger or WordPress, Google notes that in most cases the platform submits new content to search engines automatically. Check your platform's help pages before you duplicate the work.

We'd set up Search Console on every new site anyway. Submission is the smaller benefit. The bigger one is seeing whether Google could fetch your sitemap and which pages made it into the index. Without it you are guessing.

What happens after Google finds your site?

After Google finds your site, each URL moves through three stages, and not every page makes it through all of them. Crawling is Googlebot downloading and rendering the page, JavaScript included. Indexing is Google analyzing the content, picking a canonical URL among duplicates and storing the result. Serving is Google returning the most relevant indexed pages at search time.

Submission only touches the first stage. A sitemap helps Google discover URLs and schedule crawls; it has no say in whether a page is indexed or where it ranks. Google also paces its crawling to avoid overloading a server, and it treats HTTP 500 errors as a signal to slow down. A new site on unreliable hosting gets crawled more slowly, however many times you submit it.

Which Search Console property should you create for a new site?

Create a Domain property if you can edit your domain's DNS records, and a URL-prefix property if you can't. The two types cover different sets of URLs.

A Domain property is entered as the bare domain, such as example.com, with no protocol and no www. It covers every subdomain plus http and https, and it is verified by DNS record only (Blogger and Google Sites excepted).
A URL-prefix property is entered as a full prefix such as https://example.com/. It covers only URLs starting with exactly that string, so https://www.example.com/ is excluded. It accepts several verification methods.

Our view: the Domain property is the right default. It puts every protocol and subdomain in one report, and you won't find out months later that your data was split across four properties. If you want separate numbers for a folder later, add URL-prefix properties on top. Google allows up to 1,000 properties per account.

To add one, open the property selector, choose Add property and pick the type. Google's help page says adding a property doesn't change how your site appears in Google Search, and an unfinished setup won't hurt the site.

How do you verify that you own the site?

You verify ownership by placing a token from Search Console somewhere only the owner could put it: a DNS record, a file on the server, a meta tag on the homepage, or an Analytics or Tag Manager snippet you control.

Method	Property type	What you need	Watch out for
DNS record (TXT or CNAME)	Domain (its only method); also works on URL-prefix	Login to the company you bought the domain from	Manually added records can take up to two or three days to be served. Leave the record in place afterward.
HTML file upload	URL-prefix only	Ability to upload a file to the site root	The file must load without a login. Don't rename or edit it.
HTML tag	URL-prefix only	Ability to edit the homepage `<head>`	The tag must sit within the first 2MB of the page. The homepage can't require a login.
Google Analytics	URL-prefix only	Edit rights on the Analytics property, same Google account as Search Console	The analytics.js or gtag.js snippet must be in the `<head>`. Older snippets aren't supported.
Google Tag Manager	URL-prefix only	Publish or Admin permission on the container, same Google account	The `<noscript>` part must come immediately after the opening `<body>` tag.
Google Sites or Blogger	Set by the platform	A Google Sites or Blogger account	Use the method Google recommends for that platform.

On WordPress, Wix, Squarespace or Shopify, search your host's documentation first, because your platform may offer a setting or plugin that verifies for you. Google names Site Kit for WordPress as the only plugin it officially sponsors.

One annoyance: Google's help page contradicts itself on the HTML file, saying first that Search Console doesn't follow redirects to it, then that same-domain redirects are followed. Don't test which is true. Serve the file at the exact URL Search Console gives you.

Once verified, add a second method from the property's settings. Search Console re-checks your token periodically, and Google's own example of a failure is an Analytics tag that disappears when someone edits a template. If every verified owner loses access, every user does. A backup costs almost nothing.

How do you build a sitemap Google will accept?

A sitemap Google will accept is a UTF-8 file in XML, RSS or Atom, or plain-text format that lists absolute, canonical URLs, with no more than 50,000 URLs or 50MB uncompressed per file.

Check whether you already have one. According to Google, a WordPress, Wix or Blogger site has probably made one available. Below a few dozen URLs, a text editor will do. Anything bigger should come from your website software. A minimal XML sitemap looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.example.com/services/</loc>
    <lastmod>2026-09-01</lastmod>
  </url>
</urlset>

Four rules from Google's documentation worth checking:

Use full URLs (https://www.example.com/page.html), never relative paths like /page.html.
List only the canonical version of each page, the one you want shown in results.
Post the sitemap at the site root. Unless you submit it in Search Console, a sitemap only affects URLs under its own directory.
Over the limit? Split it, and optionally submit one sitemap index file that points to the pieces.

Skip <priority> and <changefreq>, which Google ignores. It does use <lastmod>, but only when the dates are consistently accurate and mark significant changes to the main text, structured data or links. A copyright-year update doesn't count. A sitemap that stamps every page with today's date teaches Google to stop trusting your dates.

How do you submit a sitemap to Google?

You submit a sitemap by telling Google where the file lives; you can't upload the file itself. Google documents three routes:

The Sitemaps report in Search Console. You need owner permission. Run a live URL inspection on the sitemap address and confirm the page fetch is "Successful," then paste the URL into Add a new sitemap and click Submit. The sitemap should be fetched immediately.
A line in robots.txt. Add Sitemap: https://www.example.com/sitemap.xml anywhere in the file. Google finds it the next time it crawls robots.txt. There's no limit on sitemap lines, and no Search Console access is needed.
The Search Console API. Useful if you manage many sites or deploy sitemaps from code.

Do the first two. The Sitemaps report shows only sitemaps submitted through the report or the API, not ones found in robots.txt, so submitting there is how you get error tracking. The robots.txt line keeps the file discoverable by other engines that follow the sitemaps protocol.

Then read the status column. "Couldn't fetch" and "Sitemap had X errors" need fixing, because Google retries a failed sitemap for a few days and then stops. Even on Success, Google warns that crawling the listed URLs takes time and not all of them may be crawled.

What should robots.txt say before you submit?

Before you submit, robots.txt should allow crawling of every page you want indexed and point to your sitemap. For most new sites, this is enough:

User-agent: *
Allow: /

Sitemap: https://www.example.com/sitemap.xml

The file lives at the root of the host, and it applies only to the protocol, host and port it's served on.

The rule that ruins launches is User-agent: * followed by Disallow: /, which blocks every crawler that obeys robots.txt (Google's AdsBot crawlers are the exception, since they must be named explicitly). If your staging site used it to stay out of search, confirm it didn't ship with the live site. Check for leftover noindex tags too. And don't use robots.txt to hide pages: Google can still index a blocked URL that other sites link to. Use noindex or a password instead.

To test, open robots.txt in a private browser window, then check the robots.txt report in Search Console. If you're pushing a batch of launch URLs through Bulk Indexer, it runs a similar pre-flight check on every URL: redirects are followed and the final URL is submitted, while 404s, noindex (meta tag or X-Robots-Tag) and robots.txt blocks are caught and not charged. It is not a rare problem: of the 190,687 URLs in our September 2025 to September 2026 submission data that came back with an HTTP status, 21% either returned a 4xx or 5xx error or redirected somewhere else, which means about one URL in five would have been a wasted request.

Can you request indexing for individual pages?

Yes, you can request indexing for individual pages with the URL Inspection tool in Search Console, and Google recommends it for a few URLs, with a sitemap for anything larger. You need owner or full-user access, there's a quota on individual requests, and Google says asking repeatedly for the same URL won't get it crawled faster. For the full process and what to do when a request fails, read our guide on how to submit a URL to Google.

How long does it take Google to index a new site?

Google says crawling can take anywhere from a few days to a few weeks after you request it, and it gives no separate timeline for indexing. The setup steps add small delays of their own:

A manually added DNS verification record can take up to two or three days before your provider serves it.
Search Console collects data from the moment a property is added, but it takes a few days to accrue.
A sitemap submitted in the Sitemaps report is fetched right away. Its URLs are crawled later, depending on site size, activity and traffic.

Google's recrawl guide adds that its systems "prioritize the fast inclusion of high quality, useful content," so a site full of thin placeholder pages shouldn't expect to be first in line. A link from a page Google already knows also helps, since that is one of the three ways Google finds URLs. The easiest one to get is from another site you run.

If a few weeks pass with nothing indexed, stop waiting and start checking. Google's own window has closed by then.

Does submitting your site guarantee indexing or rankings?

No. Google states that it doesn't guarantee it will crawl, index or serve any page, even one that follows its Search Essentials, and that requesting a crawl doesn't guarantee inclusion "instantly or even at all."

Indexed and ranked are different outcomes. Search Console can report a page as indexed while you never see it in results, and Google gives three reasons: the content isn't relevant to users' queries, the quality is low, or robots meta rules prevent serving. Google also says it doesn't accept payment to crawl a site more often or rank it higher.

Why doesn't the Google sitemap ping URL work anymore?

The sitemap ping URL stopped working because Google retired it. In a Search Central blog post dated June 26, 2023, Google announced the deprecation and said the endpoint "will stop functioning in 6 months." The post now carries a note that the deprecation is complete.

Google's reasoning was that unauthenticated pings weren't very useful and, for Google Search, the vast majority led to spam. Pings now return a 404. Old plugins that still ping won't cause problems for Google Search, the post says, but they don't do anything useful either.

Old tutorials keep the method alive because the sitemaps protocol at sitemaps.org still lists an HTTP request as one way to notify search engines. For Google, that route is closed.

What about Bing and other search engines?

Bing and other search engines need their own setup, because Search Console covers Google only. Your robots.txt sitemap line does part of the job already: sitemaps.org says the protocol has support from Google, Yahoo! and Microsoft. Bing has its own Bing Webmaster Tools; add your site there separately.

You'll also hear about IndexNow. Indexnow.org lists support from Microsoft Bing, Naver, Seznam.cz, Yandex and Yep; Google isn't on that list. Our IndexNow guide covers it.

What is the launch-day checklist, in order?

Run the launch-day checklist for a new website in this order:

Confirm the live site has no blanket Disallow: / and no leftover noindex tags.
Add a Domain property in Search Console, or a URL-prefix property if you can't edit DNS.
Verify ownership, then add a backup verification method.
Find or generate the sitemap, with absolute canonical URLs, under 50,000 URLs and 50MB per file.
Add the Sitemap: line to robots.txt.
Submit the sitemap in the Sitemaps report and confirm it reads Success.
Add the site to Bing Webmaster Tools.
Give it time, then check the Index Status report.

Once the sitemap reads Success, the waiting starts. If you have launch URLs or new backlinks you want in front of search engines sooner, Bulk Indexer submits your links through multiple indexing channels. Standard indexing is $15 per 1,000 links, processed within about 24 hours, and a $1 trial gives you 50 credits that never expire. No service can guarantee indexing, ours included, so start with a small batch. See pricing.

Frequently asked questions

Why isn't my site showing up on Google after I submitted it?

Your site may not show up yet because Google's crawl window runs to weeks, and submission guarantees nothing. After that, check sitemap status, robots.txt, noindex tags and server errors. If Search Console says a page is indexed but you can't find it, the cause is relevance, quality or a robots meta rule, not submission.

Do I need a sitemap if my site only has a few pages?

You don't strictly need a sitemap for a few pages, since Google can follow your internal links. For a new domain we'd still make one. A sitemap of a few dozen URLs can be written by hand, so it costs you very little.

Can I submit my website to Google without a Google account?

You can point Google to your sitemap without an account by adding a Sitemap: line to robots.txt. Search Console itself requires signing in, and its verification tokens are tied to your Google account.

How do I check whether Google has indexed my site?

A site:example.com search gives a rough check, but Google says the operator doesn't return every indexed URL. For a specific page, use the URL Inspection tool. For the whole site, use the Index Status report that Google's recrawl guide points to.

Is Fetch as Google still available?

Fetch as Google doesn't appear in Google's current recrawl documentation, which points to URL Inspection and sitemaps instead. If a tutorial tells you to use Fetch as Google, treat the rest of it as out of date too.

Does resubmitting my sitemap speed up indexing?

Resubmitting an unchanged sitemap doesn't speed anything up, because Google already recrawls sitemaps it has read at its own pace. Resubmit after big changes, or after fixing an error that stopped Google from reading the file.

Sources

Every statement attributed to Google in this guide comes from Google's own documentation, checked on September 29, 2026:

How to submit a website to Google: Search Console, verification and sitemaps