Verify your site, submit your sitemap, and use Search Console as a content strategy tool.
⬡ What you'll build
Google Search Console is a free tool that tells you exactly how Google sees your site: what pages it has indexed, what search queries bring visitors, what errors it found during crawling, and how your pages perform in results.
It's the most direct feedback loop between your site and Google. Every content business needs it set up from day one.
Before covering what it does, clarify what it isn't:
It is not a live analytics tool. It shows search performance data with a 2–3 day delay. For live traffic, use Plausible Analytics or Google Analytics.
It is not a ranking tracker. It shows average position in search results over a date range, not your exact rank for a specific query on a specific day.
It is not a keyword research tool. It shows what you're already ranking for, not what you should target. Keyword research happens before you write.
What it is: the authoritative source for how Google sees and indexes your site.
yourdomain.com (no www, no https)Google needs proof you own the domain before showing you data.
Recommended method: DNS TXT record
google-site-verification=xxxxxxxxxxx@ (root domain)DNS TXT records propagate within minutes to a few hours. If verification fails immediately, wait 30 minutes and try again.
Why DNS over other methods? DNS verification is persistent — it doesn't break if you change themes, frameworks, or hosting providers. HTML file and meta tag methods break when you change your site structure.
A sitemap is a file that lists all your pages so Google doesn't have to discover them by crawling links.
https://yourdomain.com/sitemap.xml (if you've implemented app/sitemap.ts)https://yourdomain.com/sitemap_index.xmlhttps://yourdomain.com/sitemap_index.xmlVerify the URL exists by opening it in a browser. You should see XML content listing your pages.
sitemap.xml)Google will show the sitemap status — how many URLs it found and whether any errors occurred.
Expected timeline: Google starts crawling submitted pages within 24–72 hours. Full indexing of a new site typically takes 2–6 weeks. This is normal. New domains don't get indexed instantly.
What it shows: Which queries bring impressions and clicks to your site, which pages rank, and what position they rank at.
How to use it:
Open this report after your site has been live for at least 4 weeks. Look for:
High impressions, low clicks: Your page appears in search results but users aren't clicking. Check the title and meta description — they may not be compelling enough.
Low position (11–20): Pages ranking on page 2. These are the best candidates for improvement — a small quality upgrade can push them to page 1.
Unexpected queries: Sometimes your content ranks for queries you didn't target. These are opportunities to write dedicated content for those topics.
What it shows: How many pages are indexed vs. not indexed, and why non-indexed pages were excluded.
Why pages might not be indexed:
noindex tag — intentional (e.g., admin pages). Check this is only on pages you meant to exclude.If important pages show as "Crawled - currently not indexed," the content may need to be more substantive and specific.
What it shows: Status of submitted sitemaps — whether they were processed successfully and how many URLs were found.
Check here after submission to confirm Google accepted your sitemap. A success state means Google is aware of your pages.
What it shows: Whether your pages pass Google's performance thresholds (Largest Contentful Paint, Cumulative Layout Shift, Interaction to Next Paint).
For a new site: check this after 4+ weeks when you have enough data. If pages fail, it's typically one of:
For a Next.js site on Vercel: you'll typically pass LCP and CLS by default. For WordPress on Hostinger: LiteSpeed Cache resolves most issues.
After 6–8 weeks of live content, the Search Results report becomes a content strategy tool.
The process:
These are topics where Google thinks your content is relevant, but hasn't given it top placement yet. They're your existing footholds.
For each:
This data is more reliable than keyword tool estimates because it shows actual Google behavior on your actual site.
Search Console can email you when it detects issues:
A manual action (Google penalizing your site for policy violations) is rare but important to catch immediately. Security issues (malware detected) also need immediate attention. Enable these alerts.
| Timeline | Expected State |
|---|---|
| Day 1 | Property verified, sitemap submitted |
| Week 1 | Some pages discovered (not all indexed yet) |
| Week 2–4 | Most pages indexed; zero to minimal traffic data |
| Week 4–8 | First queries appearing in Performance report |
| Month 3–6 | Pattern of which content is gaining traction |
| Month 6–12 | Enough data to make confident content strategy decisions |
New sites take time to earn trust in Google's index. This is not a bug in the system. A new domain with high-quality content will consistently gain traction over 6–12 months. The search data becomes actionable around month 4–6.
⚠The common mistake with Search Console data
Looking at the data too early and concluding "SEO doesn't work." If you publish content and check Search Console after 2 weeks, you'll see almost nothing — and that's correct. New domains don't rank quickly. Check back at 6 weeks, then 3 months. The compound effect of organic traffic is a medium-term outcome, not a 2-week outcome.
ℹSearch Console vs Google Analytics
They measure different things. Search Console shows data from Google's crawlers and search index: impressions, click-through rate, index status. Google Analytics shows what users do on your site after arriving: page views, session duration, bounce rate. You need both. Search Console tells you how people find you. Analytics tells you what they do when they arrive.
If you set up Google Analytics 4, you can link it to Search Console for combined reporting:
After linking, Google Analytics shows Search Console data alongside behavior data — you can see which search queries lead to which on-site actions.
Implementation Checkpoint