Google Search Console: Complete SEO Guide for 2026

Google Search Console (GSC) is the most underused free tool in SEO. Most site owners verify their property, check the total clicks number, and close the tab. What they miss: GSC contains direct data from Google's crawlers and indexing system — which pages are indexed, which are excluded and why, which queries generate impressions without clicks, and which pages have Core Web Vitals issues. No third-party SEO tool has this data because no third-party tool is Google. If you run a business website in India and want to improve your search visibility in 2026, GSC is where every analysis should begin.

Setting Up and Verifying Your Property

GSC offers two property types that serve different purposes. A Domain property covers all subdomains and protocols under a single root domain — it consolidates data from www and non-www versions, http and https, and any subdomains like blog.yourdomain.com. Verification requires adding a DNS TXT record through your domain registrar. This is the preferred option for any established Indian business website because you get a complete, unified view of your search performance without gaps.

A URL-prefix property tracks a specific URL pattern (for example, https://www.yourdomain.com/) and is easier to verify via HTML meta tag, HTML file upload, or Google Tag Manager. For most sites that already have GTM installed, the GTM verification method is the fastest path — GSC can verify your ownership instantly using the container ID without any DNS changes or file uploads. Once verified, data begins populating within 24–48 hours, though historical data is only retained for 16 months.

If you have multiple sites — separate domains for different locations or services — add each as a separate property. GSC does not aggregate data across unrelated domains under a single view.

The Performance Report — Your Most Valuable Data

The Performance report shows four metrics for every query your site appears for: clicks (users who clicked through to your site), impressions (how many times your page appeared in search results), CTR (click-through rate as a percentage), and average position. The default date range is three months — extend it to 12 months to spot seasonal trends in Indian search behaviour, which can be significant for categories like travel, festivals, real estate, and retail.

The highest-leverage action in GSC: sort queries by impressions descending and look for high-impression, low-CTR rows. A query with 2,000 impressions and 1.5% CTR means your page appears in search results but only 30 users click — the title tag and meta description are not compelling enough to earn the click. Rewriting these elements to be more specific, more benefit-oriented, or more relevant to the query intent can double your clicks without any ranking improvement whatsoever. This is free traffic you are currently leaving on the table.

Segment the Performance data to extract more useful insights:

• Country filter: Check how your India traffic compares to international impressions. If you serve Indian clients, India should account for the majority of your performance data. A high international impression share with low clicks often means you are ranking for queries that don't match your actual offering.
• Device filter: Indian users are mobile-first — a significant portion of searches happen on Android smartphones. Check mobile CTR separately from desktop. If your mobile CTR is materially lower than desktop, your page titles may be truncating poorly on small screens or your mobile experience is deterring clicks.
• Search type filter: Separate Web performance from Discover (Google's interest-based feed) and Image search. Discover traffic can be substantial for content-heavy sites, but it behaves differently — it spikes on publish and fades quickly, unlike search traffic which builds over time.

Index Coverage — Why Pages Get Excluded

The Coverage report (now called "Pages" in the updated GSC interface) shows the indexing status of every URL Google has found on your site. The categories that need your attention are in the Excluded section:

• Crawled - currently not indexed: Google crawled the page but chose not to index it. This is the most common issue for Indian content sites and usually indicates thin content (very few words of substantive information), near-duplicate content (multiple pages covering the same topic with slight variation), or low perceived value relative to other content on the web. This is not a penalty — it is a quality signal. Improving the content quality, adding unique data, or merging thin pages are the appropriate responses.
• Discovered - currently not indexed: Google found the URL (via sitemap or internal link) but has not yet crawled it. On large sites, this indicates a crawl budget issue — Googlebot is not allocating enough crawl capacity to reach all your pages. The fix is to reduce the number of low-value URLs (remove them from the sitemap, add noindex, or block via robots.txt) so Googlebot can focus on pages that matter.
• Duplicate without canonical tag: Two URL versions exist with identical or near-identical content, and neither has declared the canonical version. Common scenario: yourdomain.com/page and yourdomain.com/page?utm_source=newsletter both reach the same content. Add a self-referencing canonical tag to the preferred URL.
• Soft 404: The server returns a 200 (OK) HTTP status code but the page content signals an error or contains no meaningful content. Typical sources: empty category pages, template pages with no posts, search result pages accidentally indexed. Either add meaningful content or return a proper 404 status.

For multilingual Indian sites with regional language content: check whether pages in Malayalam, Tamil, or other Indian languages are being excluded. GSC sometimes deprioritises transliterated URLs where the page has thin content or where the language declaration (hreflang or lang attribute) is missing or incorrect.

Sitemaps — Submitting and Monitoring

Submit your sitemap at GSC > Sitemaps by entering your sitemap URL (typically yourdomain.com/sitemap.xml) and clicking Submit. GSC then shows two numbers: the count of submitted URLs and the count of indexed URLs. A large gap between these numbers is a diagnostic signal worth investigating — if you submitted 200 URLs and GSC shows 140 indexed, 60 pages are not being indexed despite being in your sitemap.

Common causes of submission-to-index gaps include: password-protected pages accidentally added to the sitemap; noindex directives on pages that were also submitted (contradictory signals); redirect chains where the final destination returns a 4xx error; thin or near-duplicate content pages; and pages blocked by robots.txt that should not be blocked.

After significant site updates — adding 50 or more new posts, restructuring URLs, migrating to a new domain — re-submit your sitemap and use the URL Inspection tool to request indexing for priority pages individually. GSC limits how many indexing requests you can make per day, so prioritise your highest-value content.

One important note specific to the robots.txt setup: only list actual XML sitemaps in the Sitemap directive in robots.txt. An llms.txt file or any non-XML resource should not be listed there — it creates crawl confusion without providing any benefit.

URL Inspection Tool — Per-Page Diagnostics

The URL Inspection tool gives you granular, page-level information that the aggregate reports cannot surface. Enter any URL from your verified property and GSC returns its current indexing status, the date Google last crawled it, the canonical URL Google has assigned, the referring sitemaps that pointed to it, and the rendered HTML Googlebot saw during the last crawl.

Three practical uses for Indian website owners:

1. After publishing new content: Inspect the URL and click "Request Indexing" to signal Google to crawl it sooner. This typically accelerates the crawl by 24–48 hours compared to waiting for Googlebot's natural crawl schedule. Use this for important service pages, location pages, and high-quality blog posts.
2. After fixing an excluded page: Inspect the URL after implementing your fix to confirm that the correction is visible to Googlebot. If the Coverage report showed "Crawled - currently not indexed," inspect after improving the content to see whether the rendered HTML reflects your changes.
3. Diagnosing JavaScript rendering issues: The "Test Live URL" feature shows the actual DOM Googlebot renders. For sites using JavaScript frameworks or heavy client-side rendering, content that is visible to a human visitor may not appear in the rendered HTML — meaning Googlebot cannot index it. URL Inspection is often the only way to confirm this without setting up a separate crawl environment.

Core Web Vitals Report

The Core Web Vitals report shows field data (real-user measurements from the Chrome User Experience Report) for three metrics: LCP (Largest Contentful Paint), INP (Interaction to Next Paint, which replaced First Input Delay in March 2024), and CLS (Cumulative Layout Shift). The thresholds Google defines as Good are: LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1.

For Indian websites, mobile performance is the priority. A majority of Indian users access websites on mid-range Android devices running on 4G connections, which are fast in urban areas but variable in tier-2 and tier-3 cities across Kerala and other states. A page that scores Good on a high-end device in an urban area may score Poor for a significant share of your actual audience.

The most common Core Web Vitals issues and their causes on Indian business sites:

• Poor LCP: Oversized hero images served without compression or modern formats (WebP); render-blocking Google Fonts CSS loaded synchronously in the document head; large above-the-fold background images without preload hints.
• Poor INP: Heavy JavaScript frameworks executing long tasks on the main thread; third-party scripts (chat widgets, marketing pixels) that fire on every interaction; unoptimised event listeners in custom scripts.
• Poor CLS: Images without explicit width and height attributes (browser cannot reserve space before the image loads); lazy-loaded above-the-fold images that shift content on load; dynamically injected banners or ad slots without reserved dimensions.

Address Core Web Vitals issues on your highest-traffic pages first — those are the pages where improvement will have the most impact on user experience and ranking.

Manual Actions and Security Issues

The Manual Actions report is where you find out whether a human reviewer at Google has applied a penalty to your site. Unlike algorithmic adjustments, Manual Actions are discrete decisions with specific reasons attached: thin content with little or no added value, user-generated spam (typically from contact forms or comment sections exploited by bots), structured data violations (marking up content that doesn't match your visible page content), or unnatural inbound or outbound links.

If you receive a Manual Action: read the description carefully, fix the specific issue cited, and submit a Reconsideration Request through GSC. The request should document what the problem was, what you changed, and why it will not recur. Google typically responds within a few weeks.

The Security Issues report covers hacked content, malware injections, and deceptive pages. Indian websites on shared hosting — particularly older WordPress installations with unmaintained plugins — are a common target for injection attacks. GSC is often the first notification a site owner receives that something has gone wrong. If a Security Issue appears, act immediately: engage your hosting provider, restore from a clean backup if possible, remove malicious code, and submit a Security Issue reconsideration request after confirming the site is clean.

Links Report — Backlink and Internal Link Data

The Links report in GSC is not a replacement for a dedicated backlink tool, but it provides a useful baseline view of your site's link profile directly from Google's perspective. The report shows:

• Top linked pages (external): Which of your pages receive the most links from other websites. These are your highest-authority pages — they are natural candidates for conversion optimisation and internal linking hubs.
• Top linking sites: Which external domains link to you most frequently. Review this list periodically for domains you do not recognise — unexpected linking domains can indicate link scheme participation, negative SEO, or scrapers that copied your content and linked back.
• Top linking text: The anchor text distribution of your inbound links. A heavily over-optimised anchor profile (90% of links using exact-match commercial keywords) can be a Manual Action risk. A natural profile includes a mix of branded, generic, and descriptive anchors.
• Internal links: Which pages receive the most internal links from elsewhere on your site. Pages with zero or very few internal links are functionally invisible to Googlebot — they may never be crawled frequently enough to maintain their index status. Review this list for important pages that need stronger internal linking from related content.

Use the internal links data alongside your Coverage report: if a page appears in "Crawled - currently not indexed" and also has very few internal links, adding contextual links from relevant pages is one of the first fixes to try before concluding the content itself needs a complete rewrite.

Frequently Asked Questions