
Short answer: To submit your website to Google Search Console, sign in at search.google.com/search-console, add a property (a Domain property for the whole site, or a URL-prefix property for one address), verify ownership with a DNS TXT record, HTML file, HTML tag, Google Analytics or Tag Manager, then open Indexing > Sitemaps and submit your sitemap URL. Use URL Inspection to request indexing for your most important new pages.
This guide is for anyone with a new or existing website who wants Google to know it exists and wants the data to prove it: small business owners, bloggers, developers handing over a site, and people starting out in SEO. By the end you will have a verified property, a submitted sitemap, your key pages requested for indexing, and a short list of what to check in the first week. I have written it in the order I set Search Console up for every new client site.
What “submitting” to Search Console actually does
There is no form where you hand Google your website and wait for approval. Google finds most sites by following links and reading sitemaps. Submitting your site to Search Console means three things:
- Proving you own it, so Google will show you private data about how it crawls, indexes and ranks your pages.
- Telling Google where your pages are through a sitemap, which Google describes as a hint, not a command. It may or may not use it.
- Asking for specific URLs to be crawled with URL Inspection, which is useful for a handful of important pages, not a whole site.
None of this guarantees indexing or rankings. What it gives you is visibility into problems that would otherwise be invisible, such as pages blocked by robots.txt, a stray noindex tag, or a sitemap Google cannot fetch. If you are new to how discovery works, my explainer on crawling and indexing covers the background.
Before you start: what you need
- A Google account you will keep. Use a company account, not a freelancer’s personal Gmail, so access does not leave with them.
- Access to one of these: your domain’s DNS settings (registrar or hosting panel), the site’s files (FTP or cPanel File Manager), the site’s admin area (for a plugin), or admin access to the site’s Google Analytics or Tag Manager.
- A working sitemap URL. WordPress creates one at /wp-sitemap.xml, and Yoast SEO and Rank Math create /sitemap_index.xml. If you do not have one, my free XML sitemap generator builds one.
- A live site that returns a 200 status on its homepage, without a password, maintenance page or “coming soon” plugin blocking Google.
Rather have an expert do this for you?
Hand it over and get back to running your business.
Step 1: Choose the right property type
When you click “Add property”, Google asks you to choose between two types. This choice matters more than most guides admit, because it decides what data you see.
| Question | Domain property | URL-prefix property |
|---|---|---|
| What you type | example.com | https://www.example.com/ |
| What it covers | Every subdomain (www, shop, blog) and both http and https | Only URLs starting with that exact prefix |
| How you verify | DNS record only | HTML file, HTML tag, Analytics, Tag Manager or DNS |
| Best for | Site owners who can edit DNS; the complete picture | No DNS access, or tracking one section such as /blog/ or a country folder |
| Common catch | Waiting for DNS changes to take effect | Data missing because the site actually loads on a different version (www vs non-www) |
My default is a Domain property, plus extra URL-prefix properties for big sections I want to report on separately, such as a /uk/ folder on an international site. If you only have WordPress access today, start with URL-prefix (making sure you type the exact version your site redirects to) and add the Domain property later.
Step 2: Verify ownership
Google’s verification help page lists the methods. Pick the one that matches the access you have.
DNS TXT record (Domain property)
- Copy the TXT value Search Console shows you (it starts with
google-site-verification=). - In your registrar or hosting DNS panel, add a new TXT record. Leave the host/name as
@(or blank, depending on the panel) and paste the value. - Save, wait, then click Verify. Changes often apply within minutes but can take longer.
A practical point from sites I set up in Pakistan: many .pk and .com domains here are registered through one company but point their nameservers to a hosting provider. Add the TXT record wherever the nameservers point (often the cPanel Zone Editor), not at the registrar. Adding it in the wrong place is the most common reason DNS verification “does not work”. Google also says not to delete the record after verification succeeds, because verification is checked again over time.
HTML file upload
Download the file and upload it to the site’s root folder (public_html), so it opens at example.com/googleXXXX.html. Do not rename it. Google notes that removing the file later will cause you to lose verification.
HTML tag
Paste the meta tag into the <head> of your homepage. On WordPress, Yoast SEO, Rank Math and most themes have a field for the verification code, so you do not need to edit theme files. Clear any page cache before clicking Verify, otherwise Google sees the old cached homepage without the tag.
Google Analytics or Tag Manager
If the same Google account has edit rights on the site’s Analytics property or publish rights on its Tag Manager container, and the code sits in the homepage’s head section, verification is a single click.
A useful detail from Google’s documentation: data is collected for a property as soon as anyone adds it, even before verification succeeds, so a delay in verifying does not lose you data.
Step 3: Submit your sitemap
- In the left menu, open Indexing > Sitemaps.
- Type the sitemap path after your domain, for example
sitemap_index.xml, and click Submit. - Refresh after a while. The status should change to “Success” with a count of discovered pages. “Couldn’t fetch” or “Has errors” needs fixing (see below).
Submit the sitemap index if your plugin creates one; you do not need to submit each child sitemap. Google’s sitemap documentation also confirms that it ignores <priority> and <changefreq>, and only uses <lastmod> when it is consistently accurate, so do not waste time tuning priority values. Add a Sitemap: line to your robots.txt file as well, so other search engines find it too. My guide to XML sitemaps explains what belongs in one; the short version is only indexable, canonical URLs that return 200.
Worked example: what a clean WordPress setup looks like
An illustrative small business site on WordPress with Yoast SEO. Domain property verified by a TXT record in the hosting Zone Editor. Sitemap submitted as sitemap_index.xml, which lists post-sitemap.xml, page-sitemap.xml and category-sitemap.xml. Tag, author and attachment sitemaps are switched off in Yoast because those archives are noindexed. robots.txt contains Sitemap: https://www.example.com/sitemap_index.xml. The homepage, contact page and the five main service pages are requested for indexing through URL Inspection on day one. Nothing else is requested manually.
Step 4: Request indexing for your most important pages
Paste a full URL into the inspection bar at the top of Search Console. The report tells you whether the URL is on Google, which canonical Google chose, and when it was last crawled. Click Test live URL to check what Google can fetch right now, then Request indexing. I walk through the report in detail in the URL Inspection tool guide.
Use it for the pages that matter: the homepage, main service or category pages, and a newly published or heavily updated article. Google’s recrawl guidance says there is a quota for individual URL requests, that requesting the same URL several times will not get it crawled faster, and that a request does not guarantee inclusion at all. For bulk changes, the sitemap is the right tool.
Search Console setup checklist
- Use a company Google account: one the business will keep, with two-step verification on.
- Confirm the preferred URL: check that http, https, www and non-www all redirect to one version.
- Add a Domain property: and a URL-prefix property for any section you want to report on separately.
- Verify ownership: DNS TXT record where the nameservers point, or file, tag, Analytics or Tag Manager.
- Add a second owner: Settings > Users and permissions, so you are never locked out.
- Check robots.txt: it returns 200 and does not block pages or resources you want indexed.
- Submit the sitemap index: in Indexing > Sitemaps, and confirm it shows “Success”.
- Add the sitemap to robots.txt: with a full absolute URL.
- Inspect the homepage: test the live URL and check Google’s chosen canonical.
- Request indexing for key pages: homepage and main service or category pages only.
- Link Google Analytics: so you can see search queries alongside on-site behaviour.
- Add the site to Bing Webmaster Tools: it can import your verified Search Console sites.
- Diary a check in 7 days: Page indexing, Sitemaps and Manual actions.
Ticks are saved in your browser, so you can come back and carry on.
When verification or submission fails
| What you see | Likely cause | Fix |
|---|---|---|
| “Verification method failed” for an HTML tag | Page cache or CDN serving an old homepage; tag placed in the body | Purge cache, confirm the tag is in the head with View Source, verify again |
| DNS verification fails | TXT record added at the registrar while DNS is hosted elsewhere | Find the active nameservers with a DNS lookup and add the record there |
| HTML file not found | File uploaded to a subfolder or renamed; redirect to another domain | Upload to the root so it opens at the exact URL; keep it there |
| Sitemap “Couldn’t fetch” | Wrong path, sitemap blocked by robots.txt or a security plugin, or a firewall blocking Googlebot | Open the sitemap URL in a private window; check robots.txt and firewall rules |
| Sitemap “Has errors” | Invalid XML, URLs on another domain, or redirected and noindexed URLs listed | Validate it with a sitemap validator and regenerate |
| No data after verifying | New property or wrong URL-prefix version | Wait a few days; confirm the property matches the version your site loads on |
You can check where a domain’s nameservers point with my free DNS lookup tool before adding a TXT record.
What to check in your first week
- Page indexing report: look at “Why pages aren’t indexed”. Some exclusions are normal (redirects, alternate pages with a proper canonical). “Excluded by ‘noindex’ tag” on pages you want ranked is not; my guide to the robots meta tag shows how to find and remove it. The coverage report guide explains each status.
- Sitemaps: discovered page count roughly matches the number of pages you expect.
- Core Web Vitals and Enhancements: these fill slowly on small sites. When they do, they flag slow templates (see my Core Web Vitals guide) and invalid schema markup.
- Manual actions and Security issues: both should say no issues detected.
- Performance: it takes a few days to fill. Once it does, the Performance report shows the queries, pages and countries bringing clicks.
Mistakes I see when auditing Search Console setups
- Only the wrong URL-prefix property exists, for example http://example.com while the site runs on https://www., so the owner thinks they have no traffic.
- The agency or developer is the only owner. When the relationship ends, the business loses its history. Always keep yourself as a verified owner.
- Verification removed during a redesign because the new theme dropped the meta tag. DNS verification avoids this.
- Old sitemaps left in the report after a plugin change, pointing to URLs that now 404.
- Request indexing used for every page instead of fixing the reason pages are not being indexed, which is usually thin content, poor internal links or a technical block.
- Not adding the new domain after a migration. A domain move needs both properties and the Change of Address tool; my website migration checklist covers the order of work.
Frequently asked questions
Do I have to submit my website to Google for it to be indexed?
No. Google finds most sites through links and sitemaps without any submission. Setting up Search Console simply gives you a way to tell Google about your pages directly and, more importantly, to see what is stopping any of them from being indexed.
Is Google Search Console free?
Yes. Search Console is free for any site owner. You need a Google account and a way to prove you control the site.
How long does it take Google to index a site after submission?
Google says crawling can take from a few days to a few weeks, and submission does not guarantee indexing. New sites with few links usually take longer. If important pages are still missing after a few weeks, inspect them and check the Page indexing report for the reason.
Should I choose a Domain or URL-prefix property?
Choose a Domain property if you can add a DNS record, because it covers every subdomain and both http and https. Use a URL-prefix property if you cannot edit DNS, or in addition, when you want separate reports for a section such as a blog or country folder.
Can I submit a site to Search Console without access to DNS or files?
Yes, if you have edit access to the site’s Google Analytics property or publish access to its Tag Manager container, or if you can add a meta tag through a CMS setting or SEO plugin. All of these work for a URL-prefix property.
Do I need to resubmit my sitemap every time I publish?
No. Once submitted, Google rechecks the sitemap on its own schedule. Keep the sitemap accurate (your CMS or plugin usually updates it automatically) and resubmit only if its location changes.
Sources
- Google Search Console Help, “Verify your site ownership” (accessed 2026).
- Google Search Central, “Build and submit a sitemap” (accessed 2026).
- Google Search Central, “Ask Google to recrawl your URLs” (accessed 2026).
- HTTP Archive, “Web Almanac 2024: SEO chapter” (2024).
Once your property is verified and the sitemap shows “Success”, the real work is reading what Search Console tells you. If the Page indexing report is full of statuses you do not understand, my technical SEO services start with exactly that, or you can ask me a question.
Request received
Thank you! Saad will contact you within the next 24 hours.
Keep an eye on your phone and inbox.
