Quick answer: Add your site to Google Search Console, submit a sitemap, and review the Index Coverage report. The report tells you which pages Google could index, which were blocked, and why. Fix the identified issues and then resubmit the sitemap; monitor the report until the important pages are indexed.
Launching a website is exciting, but you also need to make sure search engines can see the pages you want customers to find. This guide walks you through the process of verifying a new site in Google Search Console, interpreting the Index Coverage report, and applying practical fixes that suit Indian businesses.
Why index coverage matters right after launch
When a site goes live, search engines start crawling it based on the signals they receive. If key pages are missing from the index, users searching for your products or services may never land on your site. This can delay traffic, leads, and sales, especially for small businesses that rely heavily on organic search.
Consider a boutique in Delhi that launched an online catalog. Within a week, the owner noticed no new enquiries. Checking the Index Coverage report revealed that the product pages were listed under Excluded because the folder was blocked in robots.txt. After unblocking, the pages appeared in search results and enquiries rose.
Adding and verifying your new site in Google Search Console
You only need a Google account to start. Follow the numbered steps below; each step includes a short tip to avoid common hiccups.
- Sign in to Google Search Console and click Add property.
- Choose the Domain option for full‑site coverage. Type your domain without the protocol prefix.
- Google will ask you to add a DNS TXT record at your domain registrar. Log in to the registrar, create a new TXT record with the value Google provides, and save.
- Return to Search Console and click Verify. Verification typically completes quickly, but may take a few minutes.
- After verification, open the left‑hand menu and select Sitemaps. Enter the URL of your sitemap and click Submit.
- Wait up to several hours for Google to process the sitemap; the status line will show the number of URLs discovered when processing completes.
- If you prefer not to edit DNS, you can verify using an HTML file upload or a meta tag. Choose the method that matches your hosting setup.
Tip: Keep a copy of the verification file or meta tag in a safe place. If you later move the site to a new host, you may need to re‑verify.
Reading the Index Coverage report
The Index Coverage report is found in the Coverage section under the Index area of Search Console. It groups URLs into four main buckets: Error, Valid with warnings, Valid, and Excluded. Understanding each bucket helps you decide what to fix first.
What each bucket means
- Error – Google could not index the page at all. Typical causes are server errors, DNS failures, or blocked resources.
- Valid with warnings – The page is indexed, but Google found something that may affect visibility, such as a mismatched canonical tag.
- Valid – The page is successfully indexed and can appear in search results.
- Excluded – Google deliberately left the page out, often because of noindex directives, duplicate content, or a robots.txt block.
Common warnings you will encounter
- Submitted URL not indexed – The URL appears in your sitemap but Google could not crawl it, possibly due to a temporary timeout.
- Crawled – currently not indexed – Google fetched the page but decided not to add it yet; this can happen with thin or low‑value content.
- Duplicate, submitted URL not selected as canonical – Multiple pages have similar content; Google chose a different page as the primary version.
Fixing typical coverage issues for Indian businesses
Below are the most frequent problems you may meet after launching a site, together with concrete actions you can take today.
- Server errors – Check your hosting provider’s status page or contact support. Restarting the web server or fixing a misconfigured file often resolves the issue.
- Blocked by robots.txt – Open the robots.txt file and ensure you are not disallowing important sections. Adjust the rules to allow only the specific folders you want crawled.
- Missing alt text on images – Add descriptive alt attributes to every product image. This improves accessibility and gives Google more context about the page.
- Incorrect canonical tags – Verify that the canonical tag points to the preferred URL, not to a staging version or a duplicate page.
- Accidental noindex meta tag – Search your HTML for the noindex tag. Remove it from any page that should appear in search.
- Slow page load – Use a content delivery network or compress images. Very slow pages may be deprioritised by Google.
Real‑world illustrations
- A tailor in Jaipur uploaded a new catalogue but had a block in robots.txt. Google listed the pages as Blocked. After editing robots.txt to allow the folder, the pages moved to Valid.
- A bakery in Pune launched an online order form but left a noindex tag on the checkout page. Customers could not find the form via Google until the tag was removed.
- An NGO in Mysore used a sub‑domain for event registration. The DNS record for the sub‑domain was missing, causing a server error entry. Adding the DNS entry cleared the error.
Adding extra signals to help Google crawl faster
While the sitemap is the primary guide, you can reinforce crawling with a few additional steps.
- Internal linking – Ensure that every important page is linked from at least one other page on your site. A clear navigation menu helps Google discover pages organically.
- URL Inspection – In Search Console, use the URL Inspection tool to request indexing for a specific page. This is useful for new blog posts or product pages you want to appear quickly.
- Structured data – Adding basic schema markup does not affect index coverage directly, but it can improve how Google understands the page and may encourage faster indexing.
When to ask a professional
If you encounter persistent errors, need a custom sitemap for a large e‑commerce catalog, or want a full technical audit, professional help can save time and reduce risk. Ebenezer Digital offers SEO services that include comprehensive coverage audits, and its web development services can implement technical fixes efficiently.
Practical checklist before you go live
- Verify site ownership in Google Search Console.
- Submit an up‑to‑date sitemap.
- Review the Error and Warning sections in the Index Coverage report.
- Ensure robots.txt does not block important pages.
- Remove any accidental noindex meta tags.
- Confirm canonical tags point to the preferred URL.
- Test page speed with a free tool and optimise images if needed.
- Use the URL Inspection tool for any newly added pages.
- Check that internal links lead to all key pages.
- Monitor the report for 48 hours after launch and address new issues promptly.
Frequently asked questions
Does Google need a sitemap for every new site?
A sitemap is not mandatory, but it speeds up discovery and gives you a clear view of what Google should crawl. For sites with many pages, a sitemap is strongly recommended.
How long does it take for a page to move from Error to Valid?
Usually a few hours after the underlying issue is fixed, but it can take up to a day for Google to re‑process the sitemap and update the status.
Can I use the mobile‑friendly test instead of Search Console?
The mobile‑friendly test checks how a page renders on phones, not index coverage. Both tools serve different purposes and should be used together.
What if my site is on a sub‑directory of a larger domain?
Use the URL‑prefix option to add the sub‑directory directly as a property. Verify ownership with the same methods you would for a full domain.
Will fixing coverage issues improve my rankings instantly?
Fixes remove obstacles for Google to see your content. Rankings may improve over time as Google re‑evaluates the pages, but there is no immediate boost.
Summary
- Add and verify your domain in Google Search Console, then submit a sitemap.
- Use the Index Coverage report to identify errors, warnings, and exclusions.
- Apply quick fixes: adjust robots.txt, remove noindex, correct canonicals, and resolve server errors.
- Run a short pre‑launch checklist to avoid common pitfalls.
- Seek professional help for large or complex sites, using Ebenezer Digital’s SEO or web development services.