When I put my first site in production on a home server, I made the mistake of thinking Google would discover it on its own. It didn’t. After a week with no trace in search results, I understood that I needed to be more proactive. Here’s what I learned setting up Google Search Console from scratch.
Why you need Google Search Console#
Google Search Console is not optional. It’s your direct communication with Google about your site. It shows you indexing errors, security issues, and most importantly: it lets you tell Google exactly which pages to index and when.
Without it, you depend on Google’s bot discovering your site organically. With a new site on a home server, that can take weeks or months.
Step 1: Verify your domain#
Go to Google Search Console with your Google account. If you don’t have one, create one. It’s free.
Click on “Add property” and select the property type. You have two options:
- Domain: verifies the entire domain (recommended)
- URL prefix: verifies only a specific URL
I chose domain because I wanted to cover everything: example.com, www.example.com, and any future subdomain.
DNS verification#
Google will give you a TXT record to add to your domain provider. In my case I used Namecheap.
The record looks like this:
google-site-verification=ABC123XYZ...I accessed my registrar’s control panel, went to DNS settings, and added a new TXT record with that value. I waited a few minutes for it to propagate.
Go back to Google Search Console and click “Verify”. If everything is correct, you’ll see the confirmation message.
Tip: DNS verification is definitive. Google will detect it automatically in future properties on the same domain.
Step 2: Create and optimize your sitemap#
A sitemap is an XML file that lists all your pages. Google uses it to discover content it might otherwise miss.
If you use a CMS like WordPress, Astro, or Next.js, you probably already have a plugin or generator. In my case, with a static site, I generated it manually.
A basic sitemap looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2026-04-25</lastmod>
<changefreq>weekly</changefreq>
<priority>1.0</priority>
</url>
<url>
<loc>https://example.com/articulos/</loc>
<lastmod>2026-04-20</lastmod>
<changefreq>daily</changefreq>
<priority>0.8</priority>
</url>
</urlset>I saved the file as sitemap.xml in the root of the web server (in /var/www/html/ in my case).
Important note: include the <lastmod> tag with the actual date. Google uses this to know if your content changed.
Step 3: Submit the sitemap to Google#
Go back to Google Search Console, go to “Sitemaps” in the left menu, and paste the complete URL:
https://example.com/sitemap.xmlClick “Submit”. Google will process it within minutes.
You should see a “Success” status with the number of URLs found. If there are errors, Google will show them to you here.
Step 4: Optimize your robots.txt file#
While you’re here, make sure your robots.txt points to your sitemap:
User-agent: *
Allow: /
Disallow: /admin/
Disallow: /private/
Sitemap: https://example.com/sitemap.xmlThis tells Google where to find your sitemap without having to guess.
Results#
After submitting my sitemap, Google indexed 80% of my pages within 24 hours. Within a week they were all indexed. Searches started showing my articles.
It’s not magic, but it is effective. Google Search Console is a tool that every site owner must use, without exception.
Recommended equipment#
- Raspberry Pi 3 B+ — Lightweight low-power server to start your homelab
- Raspberry Pi 4 (4GB) — The perfect foundation for homelab, Docker and monitoring
Affiliate links. No extra cost to you.