Skip to main content

Why do valid pages appear in the 'Excluded' section of GSC, and what should be your next step?

Valid pages can appear in the “Excluded” section of Google Search Console (GSC) for several reasons, even if they are live and accessible. The “Excluded” category means Google is aware of the page but has chosen not to index it, or can't index it due to specific conditions.

Why do valid pages appear in the 'Excluded' section of GSC, and what should be your next step?

🔍 Common Reasons Valid Pages Are 'Excluded'

1. Crawled - Currently Not Indexed

  • Google crawled the page but decided not to index it yet.

  • Common for:

    • Thin content

    • Duplicate or low-quality pages

    • New or recently updated content

Next step: Improve content quality and usefulness; then request reindexing.

2. Discovered – Currently Not Indexed

  • Google knows about the page (e.g., from a sitemap or internal link) but hasn’t crawled it yet.

  • Often due to:

    • Crawl budget limits

    • New websites or large sitemaps

Next step: Build internal links to the page and monitor crawl activity.

3. Alternate Page with Proper Canonical Tag

  • The page is marked with a canonical pointing to another URL.

  • Google chooses to index the canonical page, not the alternate.

Next step: Check if the canonical is correct and intentional.

4. Duplicate Without User-Selected Canonical

  • Google detected it as a duplicate, even if you didn’t set a canonical.

  • It picked a different URL to index.

Next step: Set a canonical tag explicitly to control which version is indexed.

5. Excluded by ‘noindex’ Tag

  • The page has a <meta name="robots" content="noindex">.

Next step: Remove the noindex tag if you want the page indexed.

6. Blocked by robots.txt

  • Page is disallowed from crawling, so it can’t be indexed.

Next step: Update robots.txt to allow crawling if you want it indexed.

7. Soft 404

  • Page returns content, but Google considers it "empty" or not useful enough.

Next step: Add meaningful content and ensure proper status codes.

✅ What Should Be Your Next Step?

🛠 Use the URL Inspection Tool

  • Inspect the excluded URL to see:

    • Crawlability

    • Indexing decision

    • Canonical URL

    • Live test result

✅ Decide Intent

  • Ask: Should this page be indexed?

    • If yes: Fix issues (e.g., improve content, fix canonical/noindex/robots).

    • If no: You can safely ignore it.

📤 Request Indexing (After Fixes)

Popular posts from this blog

How does BGP prevent routing loops? Explain AS_PATH and loop prevention mechanisms.

 In Border Gateway Protocol (BGP), preventing routing loops is critical — especially because BGP is the inter-domain routing protocol used to connect Autonomous Systems (ASes) on the internet. 🔄 How BGP Prevents Routing Loops The main mechanism BGP uses is the AS_PATH attribute . 🔍 What is AS_PATH? AS_PATH is a BGP path attribute that lists the sequence of Autonomous Systems (AS numbers) a route has traversed. Each time a route is advertised across an AS boundary, the local AS number is prepended to the AS_PATH. Example: If AS 65001 → AS 65002 → AS 65003 is the route a prefix has taken, the AS_PATH will look like: makefile AS_PATH: 65003 65002 65001 It’s prepended in reverse order — so the last AS is first . 🚫 Loop Prevention Using AS_PATH ✅ Core Mechanism: BGP routers reject any route advertisement that contains their own AS number in the AS_PATH. 🔁 Why It Works: If a route makes its way back to an AS that’s already in the AS_PATH , that AS kno...
Read more

Explain the Angular compilation process: View Engine vs. Ivy.

 The Angular compilation process transforms your Angular templates and components into efficient JavaScript code that the browser can execute. Over time, Angular has evolved from the View Engine compiler to a newer, more efficient system called Ivy . Here's a breakdown of the differences between View Engine and Ivy , and how each affects the compilation process: 🔧 1. What Is Angular Compilation? Angular templates ( HTML inside components) are not regular HTML—they include Angular-specific syntax like *ngIf , {{ }} interpolation, and custom directives. The compiler translates these templates into JavaScript instructions that render and update the DOM. Angular uses Ahead-of-Time (AOT) or Just-in-Time (JIT) compilation modes: JIT : Compiles in the browser at runtime (used in development). AOT : Compiles at build time into efficient JS (used in production). 🧱 2. View Engine (Legacy Compiler) ➤ Used in Angular versions < 9 🔍 How It Works: Compiles templat...
Read more

What is Zone.js, and why does Angular rely on it?

Zone.js is a library that Angular relies on to manage asynchronous operations and automatically trigger change detection when necessary. Think of it as a wrapper around JavaScript’s async APIs (like setTimeout , Promise , addEventListener , etc.) that helps Angular know when your app's state might have changed. 🔍 What is Zone.js? Zone.js creates an execution context called a "Zone" that persists across async tasks. It tracks when tasks are scheduled and completed—something JavaScript doesn't do natively. Without Zone.js, Angular wouldn’t automatically know when user interactions or async events (like an HTTP response) occur. You’d have to manually tell Angular to update the UI. ⚙️ Why Angular Uses Zone.js ✅ 1. Automatic Change Detection Zone.js lets Angular detect when an async task finishes and automatically run change detection to update the UI accordingly. Example: ts setTimeout ( () => { this . value = 'Updated!' ; // Angular know...
Read more