How to Submit a Website to Google: A Step-by-Step Guide to Google Search Console

laptop screen showing google search console traffic stats

To submit a website to Google, add the website to Google Search Console, verify ownership and submit a sitemap listing your public pages. For an individual page, use the Request indexing option.

Google also finds websites automatically through links, so submission is optional. Search Console gives you a direct way to supply page addresses and check what happens afterwards. The service is free.

Three terms explain the process: crawling means Google visits a page, indexing means Google processes and stores information about the page and ranking concerns the page’s position for a particular search. Submitting an address does not guarantee indexing or a high position.

1. Prepare your account and website details

You need a Google account and access to either your domain’s DNS settings or your website’s verification settings or files. DNS settings are records managed through a domain provider or a separate DNS service.

If someone else manages the website, ask who controls the domain’s DNS records before starting verification, since the company selling your domain and the company managing those records are not always the same provider.

Open your public homepage and copy the full address from the browser. Note the https:// and any www prefix. For the examples below, replace example.com with your own domain.

If the website already has a Search Console owner, ask the owner to grant access through Settings > Users and permissions. For example, a previous developer’s existing setup does not require you to share a Google account.

2. Add your website to Search Console

  1. Open Google Search Console and sign in.
  2. For a first website, follow the initial setup screen. If another website is already selected, open the property selector near the top left and choose Add property.
  3. Choose Domain or URL prefix using the comparison below.
  4. Enter the domain or full website address and select Continue.

A property is Google’s name for the website or section tracked in Search Console.

Property type What to enter Coverage and verification
Domain example.com Covers subdomains and both HTTP and HTTPS. Requires DNS verification.
URL prefix https://www.example.com/ Covers addresses starting with this exact prefix. Offers several verification methods.

Choose Domain if you control DNS and want one view across the domain. Enter the domain without https://, www or a page path.

Choose URL prefix if website access makes verification easier. Copy the public homepage address precisely because https://example.com/ and https://www.example.com/ belong to different URL-prefix properties.

3. Verify ownership using one method

Verification proves you control the website before Google shares private search reports. Complete one suitable method below. You do not need to complete every method.

Domain verification through DNS

If Google offers an automatic connection to your provider, follow the sign-in prompts. Otherwise use the TXT record route:

  1. Copy the TXT verification value supplied by Search Console.
  2. Sign in to the service managing your domain’s DNS and open its DNS records.
  3. Add a TXT record. For the root domain, use the provider’s required Name or Host value, commonly @ or a blank field.
  4. Paste Google’s value into the Value or Content field and save.
  5. Return to Search Console and select Verify.

Leave the record in place after success. If verification fails, check the value and allow time for DNS updates. Google advises some manually added records take two or three days to become available.

URL-prefix verification with an HTML tag

  1. Choose HTML tag in the verification options.
  2. Copy Google’s supplied verification tag.
  3. Add the tag to the homepage’s HTML head section. This is a behind-the-scenes section rather than visible page content.
  4. Publish the change and select Verify in Search Console.

If your website platform provides a dedicated Google verification field, follow its instructions for entering the verification value instead of pasting the tag into a visible text block.

URL-prefix verification with an HTML file

  1. Choose HTML file and download Google’s verification file.
  2. Upload the unchanged file to the website location Google specifies.
  3. Open the supplied file address in a private browser window to confirm public access.
  4. Return to Search Console and select Verify.

Use this route if you have access to upload website files. Keep the verification file or HTML tag in place afterwards because Google periodically checks verification.

Google Analytics and Google Tag Manager verification are further options for websites already using those services with the required account permissions. Neither service is required for the routes above.

4. Find your website’s sitemap

A sitemap is a file listing page addresses for search engines. Many website platforms generate one automatically. Check your platform’s help pages or ask your website manager for the sitemap’s full public address.

A common location is https://example.com/sitemap.xml, though the actual filename varies. Open the supplied address in your browser and confirm a sitemap loads rather than a missing-page message or login screen.

Some websites use a sitemap index, which lists several smaller sitemap files instead of individual pages. Submit the index address if your platform supplies one, rather than copying every smaller file into Search Console separately.

For a small website whose pages are linked from the homepage, a sitemap is not compulsory. The submission process below still provides a useful record of Google’s ability to read the file.

5. Submit the sitemap to Google

  1. Select the correct website property in Search Console.
  2. Open Sitemaps in the left navigation.
  3. Find Add a new sitemap.
  4. Enter the sitemap address. If the field already displays your website prefix, enter only the remaining part without repeating the domain.
  5. Select Submit and check the status in the submitted sitemaps table.

Success means Google fetched and processed the sitemap. This status does not confirm every listed page has been indexed.

If the status reports a fetch or processing problem, select the sitemap row for details. Reopen the exact address you submitted and check for a typo, login requirement or unavailable file before asking your provider to investigate.

You are giving Google the file’s location on your website. You do not upload the sitemap file from your computer into Search Console.

6. Request indexing for your homepage or a new page

A sitemap supplies multiple addresses. Request indexing asks Google to consider a specific page, such as your homepage after launch or a service page following a substantial update.

  1. Copy the full public page address.
  2. Paste the address into the inspection bar at the top of Search Console and press Enter.
  3. Read the result. If Google has not indexed the page, review the stated reason.
  4. Select Test live URL if you need to check the page currently published.
  5. After resolving any blocking problem, select Request indexing and wait for confirmation of the submission.

An already indexed page also supports an indexing request after changes. Avoid requesting the same address repeatedly because repeated requests do not accelerate crawling.

Google advises crawling takes anywhere from a few days to a few weeks. Use a sitemap for many pages rather than attempting to submit every address individually.

7. Understand the tools you will use next

URL Inspection: check one page

The initial result shows Google’s stored information about the address. “URL is on Google” confirms indexing. “URL is not on Google” requires reading the accompanying explanation.

The live test checks the current page rather than Google’s earlier stored version, which is useful after fixing an access problem because the original report still reflects the previous crawl until Google processes the change.

After a successful live test, choose View tested page and open Screenshot to examine the rendered page. “Rendered” means the page after its content has loaded. Check the main text appears alongside the navigation and images.

A canonical URL is Google’s representative address for duplicate or similar pages. Find the Google-selected canonical in the stored inspection details rather than looking for an answer in the live test, since Google’s eventual choice is determined during indexing and is not predicted by this test.

Page indexing: review patterns across the website

Open Pages under Indexing to see indexed and non-indexed URLs. Select a reason in the non-indexed section to examine example addresses, then inspect an important affected page individually instead of assuming every exclusion represents the same problem.

  • Discovered – currently not indexed: Google knows the address but has not crawled the page.
  • Crawled – currently not indexed: Google visited without adding the page to its index.
  • Excluded by noindex: An instruction tells Google to exclude the page.
  • Page with redirect: The address sends visitors elsewhere. Inspect the destination if the redirect is intentional.

Focus on the homepage and important service or product pages. Duplicate addresses and deliberately removed pages do not all need indexing.

Performance: see appearances and clicks

Open Performance or Search results to review search visibility. Impressions count appearances in results. Clicks count clicks through to your website. CTR, meaning click-through rate, is clicks divided by impressions.

The Queries tab lists reported searches. Pages groups results by website address. Countries helps separate Irish and UK traffic. Select a date range before comparing figures, particularly when the website has only recently launched.

If your page receives impressions but few clicks, examine the searches generating those impressions before assuming Google has failed to index the page, since those recorded appearances already demonstrate some search visibility.

Average position summarises positions across the selected data rather than promising the same ranking for every searcher.

Manual Actions and Security Issues: investigate reported problems

Under Security & Manual Actions, open each report to check for Google’s findings. Manual actions concern human-reviewed policy violations. Security issues include detected hacking or harmful content. If either report lists a problem, open the details for affected pages and the required repair or review process.

When asking a website manager for help, send the page address, report name and exact message, plus the date you last changed the page. For a rendering problem, include the live-test screenshot so the investigation starts with the missing content Google saw.