Add Your Site to Google Search Console

Why add your site to Google Search Console

Without Search Console you are flying blind. Google may index you, but you cannot see which queries work, which pages are excluded, or when a deploy broke crawlability.

Index coverage: which URLs are in Google's index, which are excluded, and why (noindex, canonical, soft 404, blocked by robots.txt, and more).
Performance: impressions, clicks, average position and CTR by query, page, country and device.
Sitemaps: a direct channel to tell Google which URLs matter.
URL Inspection: live crawl test, rendered HTML check, and manual "Request indexing" for important new or updated pages.
Experience: Core Web Vitals and HTTPS reports.
Enhancements: structured data validity for Article, FAQ, Product and other rich result types.
Security and manual actions: malware, hacking, or rare manual penalties surface here first.

It is free, official, and the single most useful data source for organic search. Every serious SEO workflow starts here.

SEO audit scorecard style report representing the kind of visibility Search Console unlocks — Search Console is the foundation for any honest technical or content audit.

Step 1: Add your property

Go to search.google.com/search-console and sign in with a Google account you control long-term, preferably a company email and not a personal one that will leave with an employee.
Click Add property.
Choose the property type carefully:
- Domain (recommended when you control DNS) covers https://, http://, www and non-www, and all subdomains under one property. Verification is via DNS TXT (or CNAME) record.
- URL prefix covers only the exact prefix you enter, for example https://www.example.com/. Easier if you only have access to the CMS or HTML, not DNS. You may need separate properties for http/https and www/non-www unless redirects already funnel everything to one canonical host.

If your site already redirects all variants to one HTTPS host (as it should), a Domain property is cleaner. If you are on a shared host or managed CMS without DNS access, use URL prefix with the final canonical URL.

Step 2: Verify ownership

Google must confirm you control the site. Pick one method and complete it fully before switching.

Domain property: DNS record

Copy the TXT (or CNAME) value Google shows.
In your DNS provider (Cloudflare, Route 53, registrar panel, and so on), add a TXT record on the root host (@ or blank) with that value.
Wait for propagation, often minutes but it can take up to 48 hours. Then click Verify in Search Console.

URL prefix: HTML tag, HTML file, or Google Analytics / Tag Manager

HTML tag: paste the meta tag Google gives you into the <head> of your homepage (or the global layout). Deploy, then verify.
HTML file: download the file and upload it to the site root so it is reachable at https://yoursite.com/google...html.
Google Analytics / Tag Manager: works if the same Google account already has admin access to a GA4 property or GTM container installed site-wide.

After a successful verify, do not remove the tag or DNS record. Google re-checks periodically and an unverified property stops reporting.

Step 3: Create a sitemap.xml

A sitemap is an XML file that lists the URLs you want Google to know about. It does not guarantee indexing, but it speeds discovery and helps with large or deeply nested sites.

Minimal valid format

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

<loc> must be absolute HTTPS URLs of the canonical host.
<lastmod> is optional but useful. Use real modification dates, not "today" on every URL, or Google learns to ignore the signal.
One file: max about 50,000 URLs or 50 MB uncompressed. Larger sites use a sitemap index that points to several child sitemaps.
Only include 200/canonical URLs you want indexed. No login pages, no thin parameter variants.

Prompt you can give an AI or developer

Paste something like this into ChatGPT, Claude, or your internal tooling when you already have a list of public routes:

Build a valid XML sitemap (sitemaps.org protocol 0.9) for these absolute URLs. Use HTTPS only, the canonical host www.example.com, and ISO dates for lastmod where I provide them. Exclude any URL with query parameters, /admin, or draft in the path. Output only the XML, no markdown fences. If there are more than 45,000 URLs, split into multiple sitemap files and add a sitemap index file.

Many frameworks generate this automatically (Next.js, WordPress plugins, TanStack Start scripts, and so on). Whether you generate it at build time or maintain it by hand, the rule is the same: lastmod has to reflect real content changes.

Host the file at a stable path such as https://www.example.com/sitemap.xml (or /sitemap-index.xml). Reference it in robots.txt:

User-agent: *
Allow: /

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

Step 4: Submit the sitemap in Search Console

Open your property, then Sitemaps in the left menu.
On a URL-prefix property the host is prefilled, so you enter only the path (for example sitemap.xml). On a Domain property, which can span several hosts, enter the full URL including the hostname. Then click Submit.
Status should move to "Success" after Google fetches it. "Couldn't fetch" usually means a wrong path, a 404, or a robots block.

Re-submit only when the file URL changes or after major structural updates. Routine content updates do not require a new submit if lastmod is maintained and the same sitemap URL is already known.

Step 5: URL Inspection, live test, and request indexing

The top search bar in Search Console is URL Inspection. Paste any full URL of your property.

What you will see

URL is on Google or URL is not on Google: current index status.
Last crawl time, crawl allowed, indexing allowed, and the canonical Google selected.
Test live URL: Google fetches the page now, not the last crawl. Use this after a fix to confirm the live response, robots rules, and rendered HTML.
Request indexing: queues the URL for a priority crawl. Use it for new money pages, major updates, or after fixing a blocking issue, not for every blog post every day.

Core Web Vitals gauges and crawler inspecting a sitemap tree — Live testing and index requests work best after technical blockers are fixed.

Daily limits and realistic expectations

Request indexing is capped at roughly 10 to 12 URLs per day per property. Google does not publish the exact number and it varies with account history and site size. The quota is tied to the property, not the user, so switching accounts or browsers does not reset it. Once you hit it, the button greys out for about 24 hours.
Indexing is not instant. New URLs commonly take a few days to about ten, and low-authority sites can take longer. Requesting indexing is a nudge, not a guarantee.
Do not spam requests for the same URL. Fix the underlying issue (soft 404, noindex, blocked resource, thin content) first, then request once.
Sitemaps can list tens of thousands of URLs, and they are the right tool at scale. Google still decides crawl budget and indexation based on quality and site signals.

What to monitor after setup

Pages / Indexing (coverage)

Watch "Why pages aren't indexed" and the "Indexed pages" trend. Investigate spikes in excluded reasons: Crawled - currently not indexed, Discovered - currently not indexed, duplicate without user-selected canonical, blocked by robots.txt, and not found (404).

Performance

Filter by query, page, country and device. Export CSV for deeper analysis. Look for high impression and low CTR titles, and pages that rank but do not match the intent behind the query.

Experience

Core Web Vitals and HTTPS are the two reports that remain here. Google retired the Mobile Usability report, the Mobile-Friendly Test and its API in December 2023, so check mobile rendering with Lighthouse or PageSpeed Insights instead. Mobile usability still matters for rankings, it just is not reported inside Search Console any more.

Enhancements

Structured data (FAQ, Product, Article, and others). Invalid items here mean rich results may not show even if the page ranks.

Settings and users

Add teammates as Full or Restricted users under Settings, then Users and permissions. Prefer company Google accounts. Keep the verification method intact.

A practical weekly rhythm: open Performance (28 days), scan Indexing for new exclusion reasons, and inspect any URL you shipped or fixed that week.

Frequently asked questions

Do I need Search Console if I already use Google Analytics?

Yes. Analytics shows behavior on your site after someone arrives. Search Console shows how you appear in Google Search before the click: queries, index status, crawl issues. They complement each other, and linking them is optional but useful.

Domain or URL-prefix property, which should I pick?

Domain if you can add a DNS record, because one property then covers all protocols and subdomains. URL prefix if you only control HTML or a single host path. Many teams run both during a migration, then keep Domain long term.

My sitemap submitted successfully but pages are still Discovered, currently not indexed. Why?

That is common on newer or low-authority sites. Improve internal links to those URLs, strengthen content uniqueness, earn a few relevant mentions, and make sure there are no soft 404s or thin templates. Re-request indexing only after meaningful changes.

Can I request indexing for thousands of URLs?

Not with the button. The URL Inspection tool caps manual requests at roughly 10 to 12 URLs per property per day. For scale, use a clean sitemap, strong internal linking and steady publishing. Automated bulk requests through the interface are against Google's terms.

How long until I see Performance data?

Often within a few days of verification, once the site receives impressions. New sites may show sparse data until Google crawls and ranks more pages.

Next steps

Verify the property, ship a clean sitemap, inspect your homepage and top money URLs, then set a weekly review of Indexing and Performance. When you are ready for a deeper read of the same data, meaning priorities, content gaps and link opportunities, a structured audit turns Search Console from a dashboard into an action list.

For international sites, pair this setup with correct hreflang and separate performance views by country. That is covered in our international SEO consulting work and technical engagements.

How to Add Your Website to Google Search Console (Step-by-Step)