You launch, submit your sitemap, and open Search Console the next morning. The Performance report is empty. A few days later the Page indexing report fills with “Discovered – currently not indexed,” and the temptation is to click “Request indexing” on every URL, every day.
Google’s own documentation says that won’t help. Crawling “can take anywhere from a few days to a few weeks,” and requesting a recrawl several times for the same URL “won’t get it crawled any faster” (Google Search Central, checked November 9, 2026).
This guide is a 30-day plan for the period when there’s almost no data: what to set up on day 1, what each report can and can’t tell you yet, what the two “not indexed” statuses mean, and which first queries are worth acting on. It uses LeverSolo’s setup (an Astro static site on Cloudflare Pages with a sitemap-index.xml) as the running example. The steps work for any site.
The short answer
- Day 1: add a Domain property verified by a DNS TXT record, and submit your sitemap.
- Days 1–3: use URL Inspection on your homepage and 5 to 10 key pages, and request indexing once for each.
- Day 2: import the site into Bing Webmaster Tools from Search Console.
- Week 1–2: check that the sitemap reads “Success” and that robots.txt fetches. Expect indexing statuses to move slowly.
- Weeks 2–4: strengthen internal links to pages stuck in “Discovered” or “Crawled – currently not indexed,” and improve the pages themselves. Don’t mass-request.
- Weeks 3–4: watch queries in positions 8 to 20. They’re your first real content leads.
Before day 1: four things to have ready
Search Console can only report on what Google can reach. Check these before you add the property:
- The site is live on its final domain. Not a staging URL or a
*.pages.devpreview address. - robots.txt allows crawling and lists your sitemap. LeverSolo’s is three lines:
User-agent: *,Allow: /, and aSitemap:line pointing tohttps://leversolo.com/sitemap-index.xml. - The sitemap exists and lists only canonical URLs. Astro’s sitemap integration writes
sitemap-index.xml, which points to one or more numbered sitemap files. Open it in a browser and check that the URLs use your real domain. - Preview copies are kept out of the index. Cloudflare Pages gives every deployment a public
*.pages.devaddress. LeverSolo’s_headersfile sendsX-Robots-Tag: noindexon those hosts so Google doesn’t find duplicates of the real site.
Day 1: Add a Domain property
Use a Domain property unless you have a specific reason not to. It covers every subdomain and protocol in one view, and Google says it automatically includes both www and non-www (Search Console Help, checked November 9, 2026).
| Domain property | URL-prefix property | |
|---|---|---|
| You enter | example.com |
https://example.com/ |
| Covers | All subdomains, http and https, all paths | Only URLs starting with that exact prefix |
| Verification | DNS record only | Several methods (HTML file, meta tag, DNS, and others) |
| Best for | Your main view of the whole site | Tracking one section separately, or when you can’t edit DNS |
You can have both. A Domain property for the site, plus a URL-prefix property later for a section you want to track separately, is a common setup.
Verify with a DNS TXT record
- In Search Console, add a property and choose Domain. Enter your bare domain.
- Copy the TXT record value Search Console shows you.
- In your DNS provider (on Cloudflare: your domain, then DNS, then Records), add a TXT record. Leave the name as
@(the root) and paste the value. - Back in Search Console, click Verify.
Per Google’s verification help (checked November 9, 2026), a manually added record can take two or three days before your provider serves it. If verification fails, wait a day and try again. Once verified, leave the record in place. Removing it un-verifies you.
One useful detail from the same page: data is collected for a property as soon as anyone adds it, even before verification succeeds. It still takes a few days for data to start showing up.
Day 1: Submit your sitemap
Open Sitemaps in the left menu, enter the sitemap path, and submit. For an Astro site that’s sitemap-index.xml. Submit the index and Google reads the sitemaps it lists.
What the statuses mean, per the Sitemaps report help (checked November 9, 2026):
| Status | Meaning | What to do |
|---|---|---|
| Success | Fetched and processed with no errors | Nothing |
| Has errors | Fetched, but one or more errors inside | Open the report, fix the listed errors |
| Couldn’t fetch | Google couldn’t retrieve it | Open the URL yourself, fix the cause, resubmit |
Google is clear that a sitemap is a hint. There’s “no guarantee” a URL listed in it will be crawled or indexed. Resubmit after big changes or after fixing a fetch error. Resubmitting an unchanged sitemap every day does nothing.
Days 1–3: URL Inspection for a handful of pages
Pick your homepage, your main hub or pillar pages, and your 5 to 10 strongest articles. For each:
- Paste the full URL into the inspection bar at the top of Search Console.
- Click Test live URL to confirm Google can fetch and render it now.
- If the live test passes and the page isn’t indexed, click Request indexing once.
Know what the tool is showing you. The default view is the version Google last indexed, not the live page. A live test fetches the page in real time. And “URL is on Google” means the page is eligible to appear, not that it ranks for anything (URL Inspection help, checked November 9, 2026).
There’s a daily limit on indexing requests per property. Google doesn’t publish the number, so don’t plan around one you read on a forum. Google says a request doesn’t guarantee indexing, and that indexing can take up to a week or two. That’s why the list stays short: requests are for pages that matter, and your sitemap and internal links handle the rest.
Day 2: Import the site into Bing Webmaster Tools
Bing is the fastest second search engine to set up, because it can import straight from Search Console. Sign in to Bing Webmaster Tools, choose the Google Search Console import, and approve access. Bing brings over your verified sites and their sitemaps and verifies the imported sites automatically (Bing Webmaster Blog, originally September 13, 2019, updated June 2025, checked November 9, 2026).
Notes from the same post:
- Up to 100 sites per import.
- Traffic data for newly verified sites can take up to 48 hours to appear.
- Bing checks ownership periodically through the Search Console connection. If you revoke that access later, you’ll need to verify another way, such as a DNS record.
After importing, open Bing’s Sitemaps page and confirm your sitemap is listed. If it isn’t, submit it there.
Bing has another reason to matter in 2026. Microsoft says Copilot can fetch information from Bing’s search service to ground its answers, and Bing Webmaster Tools now has an AI Performance report (public preview) showing citations in Copilot and Bing’s AI summaries. Getting cited there is covered in how to get your articles cited in AI Overviews and ChatGPT.
Week 1: Confirm the plumbing
Spend 15 minutes, twice this week, checking three things:
- Sitemaps: status reads “Success” and the discovered page count roughly matches your number of published pages.
- robots.txt report (under Settings): Google fetched your robots.txt recently and shows no errors. If you fixed a robots.txt mistake, this report lets you request a recrawl of the file (robots.txt report help).
- Page indexing: the first numbers appear. Don’t read anything into them yet.
Don’t expect the Performance report to say much this week. A new property “takes a few days” for data to accrue, and the newest data is preliminary and can change over the next few hours. The 24-hour view in the Performance reports shows recent data “with a delay of only a few hours” (Google Search Central Blog, December 12, 2024), so first impressions show up fast once they exist. On a brand-new site they usually just don’t exist yet.
Weeks 2–3: Read the indexing statuses
By week two the Page indexing report shows which URLs are indexed and which aren’t, with a reason for each. Two reasons cause most of the worry on a new site. Here is what Google’s Page indexing report help says about them (checked November 9, 2026), and a sensible response:
| Status | Google’s meaning | What to do | What not to do |
|---|---|---|---|
| Discovered – currently not indexed | Google found the URL but hasn’t crawled it yet. Typically it wanted to, but expected that crawling then would overload the site, so it rescheduled. | Link to the page from your homepage, its hub page, and 2 or 3 related articles. Check it’s in the sitemap. Wait. | Request indexing on all of them daily |
| Crawled – currently not indexed | Google crawled the page and chose not to index it. Google notes it doesn’t index every page, and calls this a common message. | Check the page with URL Inspection for technical problems first. Then improve it: does it add something the pages already ranking don’t? Merge thin pages into stronger ones. | Resubmit it unchanged, or rewrite the title only |
The same help page makes a point worth remembering on a new site: not every URL needs to be indexed. Tag archives, near-duplicates, and thin pages can sit outside the index without hurting you. Focus on the pages you’d want a stranger to land on.
If you fix a real problem across many URLs, use Validate fix in the report. Google says validation typically takes up to about two weeks, and sometimes much longer.
Internal links do more than requests
On a site with ten or twenty pages, Google’s main signals about which pages matter are your sitemap and your internal links. If a new article is linked only from a “latest posts” list, it’s one click from the homepage today and three clicks away next month. Give every important article at least two permanent links: one from its hub or pillar page, and one from a related article. That’s the work the content system’s cluster step builds in from the start.
Weeks 3–4: The first queries to watch
When impressions start, the Performance report becomes your best source of what to write next. Open Performance → Search results, switch on Average position, and look at the Queries tab.
Average position for a query is the average position of your topmost result for it (Performance report help). On a new site, the useful band is roughly positions 8 to 20: Google already connects the page to that query but shows it near the bottom of page one or on page two.
For each query in that band:
- Check which page ranks for it (click the query, then the Pages tab).
- Read that page as someone who typed the query. Is the answer in the first screen?
- If the query is a sub-question the page skips, add a section that answers it directly, with its answer in the first two or three sentences.
- If it’s a different topic entirely, note it as a candidate for a new article that links to the existing one.
A rule of thumb for small numbers (our assumption, not a Google threshold): don’t act on a query with fewer than about 20 impressions in 28 days. Below that, one person’s searches can move the average position by several places.
Also note pages with impressions and almost no clicks. Their title or description isn’t earning the click. That’s a cheap fix, but give a rewrite a few weeks before judging it.
What not to do in the first 30 days
- Don’t mass-request indexing. There’s a daily limit, and Google says repeat requests don’t speed crawling.
- Don’t resubmit an unchanged sitemap every day or every week.
- Don’t delete and re-add the property to “reset” it. Google collects data for a property whether or not you’re verified, and removing it changes nothing about how your site is crawled.
- Don’t remove the DNS TXT record after verification.
- Don’t publish 50 thin pages to “build authority.” More pages of little value give Google more URLs to decline, and pages made mainly to manipulate rankings fall under its scaled content abuse policy.
- Don’t judge a page on its first 10 days. A page that isn’t in the Performance report yet hasn’t failed. It hasn’t been tested.
The 30-day checklist
DAY 0 (before launch)
[ ] Site live on final domain, https
[ ] robots.txt allows crawling and lists the sitemap
[ ] sitemap-index.xml opens and lists only canonical URLs
[ ] Preview/staging hosts send noindex
DAY 1
[ ] Domain property added; DNS TXT record created at the root (@)
[ ] Verified (retry after 24h if it fails; records can take 2-3 days)
[ ] Sitemap submitted (sitemap-index.xml)
DAYS 1-3
[ ] URL Inspection + live test: homepage, pillar/hub pages, 5-10 key articles
[ ] Request indexing ONCE for each of those that isn't indexed
DAY 2
[ ] Bing Webmaster Tools: import from Search Console
[ ] Sitemap visible in Bing (submit there if not)
WEEK 1
[ ] Sitemap status = Success; discovered count ~ published pages
[ ] robots.txt report: fetched, no errors
WEEKS 2-3
[ ] Page indexing: list "Discovered" and "Crawled - currently not indexed" URLs
[ ] Each important one: 2+ permanent internal links, in sitemap
[ ] "Crawled - not indexed": technical check, then improve or merge
WEEKS 3-4
[ ] Performance: queries in positions 8-20 with 20+ impressions
[ ] Add answer-first sections or note new article ideas
[ ] Pages with impressions and ~0 clicks: rewrite title/description once
[ ] Note date of every change, to compare in 4 weeksWho this is for
It fits you if you’ve just launched a content or affiliate site, you have fewer than a few hundred pages, and you want to know which signals mean something in month one.
It doesn’t fit you if you’re migrating an established site to a new domain. That needs Search Console’s Change of Address tool and redirect mapping, which this guide doesn’t cover. If you haven’t launched yet, start with how LeverSolo runs on Astro and Cloudflare for $0 hosting.
Quick answers
How long does it take Google to index a new site? Google gives ranges, not promises: crawling can take a few days to a few weeks, and indexing after a request can take up to a week or two. Some pages may never be indexed, and that’s normal for thin or duplicate URLs.
Should I use a Domain property or a URL-prefix property? A Domain property, if you can add a DNS record. It covers http, https, www, and every subdomain in one view. Add a URL-prefix property later if you want a separate view of one section.
How many times a day can I click “Request indexing”? Google says there’s a daily limit per property but doesn’t publish the number. Use it once for each of your most important pages and let the sitemap and internal links cover the rest.
More in AI for Content & SEO. Next, turn your first queries into articles with the AI content system for solo sites, or make your indexed pages easier for AI answers to quote with how to get cited in AI Overviews and ChatGPT.