Search Console is where you can see how Google discovers, indexes, and surfaces your site in Search. It is useful for a new microsite because it replaces guessing with evidence.
It does not guarantee indexing. Submitting a sitemap, inspecting a URL, or clicking “Request indexing” tells Google about a page. Google still decides whether and when to crawl, index, and rank it.
The useful mindset: Search Console is a diagnostic tool. When a page is not indexed, use the status to decide what to investigate instead of repeatedly resubmitting the same unchanged URL.
1. Add the property
Use a Domain property when you control DNS and want coverage across protocols and subdomains. Use a URL-prefix property when you need to verify only a specific address. Domain verification requires a DNS record.
2. Keep the verification method in place
If you verify with DNS, an HTML file, or a meta tag, leave it in place. Removing it can eventually remove your verified access.
3. Check the site before submitting anything
- The preferred HTTPS URL loads normally.
- Important pages return a normal success response.
- Pages you want indexed do not contain
noindex. - Canonical tags point to the intended URLs.
- Robots.txt is not blocking important pages.
- Every important article has a normal internal link from the site.
4. Submit a sitemap
A sitemap helps Google discover canonical URLs. It is especially useful for a new site with few external links. It is not an indexing order.
For a static site, automate sitemap generation when possible so published articles are added and scheduled drafts are not exposed early.
5. Use URL Inspection selectively
Inspect the homepage, cornerstone pages, and newly published or meaningfully updated articles. URL Inspection can show whether Google knows the URL, the selected canonical, and indexing information. Request indexing when there is a reason to recrawl the page, not as a daily ritual.
What does “Crawled - currently not indexed” actually mean?
It means Google visited the page but did not add it to the index at that time. The status does not tell you one single reason, and it is not proof that Google has issued a formal “quality penalty.”
For a small site, the useful response is to review both the technical page and the reason the page deserves to exist.
Our five-part check for a crawled but unindexed article
| Check | Questions to ask |
|---|---|
| Technical SEO | Is the canonical correct? Is the page crawlable? Does it return 200? Is it linked internally? Is it in the sitemap? |
| Search intent | What exact task or question does this page solve? Is that clear in the title, opening, and headings? |
| Query coverage | Does it answer the important follow-up questions that belong to the same task? |
| Original usefulness | What does this page contribute beyond the existing search results: a test, tool, example, framework, data, first-hand experience, or clearer decision process? |
| Human-writing audit | Does the page read like a useful explanation, or like a polished SEO template with generic takeaways, repeated conclusions, and predictable filler? |
What not to do
- Do not assume every non-indexed page has a technical bug.
- Do not keep requesting indexing for an unchanged page.
- Do not add hundreds of words merely to make it “more comprehensive.”
- Do not create several near-duplicate pages for keyword variations.
- Do not change the publication date simply to signal freshness.
Other common indexing statuses
Discovered - currently not indexed
Google knows the URL but has not crawled it yet. Internal linking, site quality, server capacity, and crawl prioritization can all be relevant. On a small site, first make sure the page is actually linked and worth crawling.
Duplicate / Google chose a different canonical
Check whether multiple URLs show substantially the same content and whether your canonical signals are consistent across HTML, redirects, sitemap entries, and internal links.
Page with redirect
A redirecting URL normally is not indexed as the final content page. Make sure internal links and sitemaps point directly to the preferred destination where possible.
Excluded by noindex or robots
If intentional, leave it alone. If accidental, fix the directive before requesting another crawl.
Use Performance data after pages begin appearing
Search Console can show queries, impressions, clicks, countries, devices, and average position. This is where keyword research becomes less hypothetical. You can see the language Google already associates with your page and decide whether the content answers those searches well.
Do not overreact to tiny samples. A new site may have too little data for strong conclusions.
A practical small-site routine
- Once a week, check Page indexing for new patterns rather than every individual exclusion.
- Inspect only priority URLs that are new, updated, or unexpectedly missing.
- Compare the page against its intended search task before requesting another crawl.
- Fix site-wide technical problems once rather than page by page.
- Use Performance data to find pages receiving impressions but weak clicks or mismatched queries.
Search Console and Analytics are different
Search Console tells you how Google Search is interacting with the site. Analytics tells you what measured visitors do after arriving. Neither one, by itself, explains why a page ranked or failed to rank.
For the second half of the picture, see the Google Analytics setup guide.
References
- Google Search Central. Ask Google to recrawl your URLs.
- Google Search Central. Sitemaps overview.
- Google Search Central. How Google Search works.
- Google Search Console Help. Verify site ownership.
Do not diagnose a niche from one indexing status
Use GetNicheIQ to think through the audience and business case, then use Search Console to test what Google actually discovers and surfaces.
Research a niche