“My pages don’t show up in Google.” It’s the single most common question we hear from Dallas business owners on the first call, and 80% of the time the answer is sitting in their Google Search Console, completely unread.
Search Console is the only tool that tells you exactly what Google thinks of your website. It’s also the most intimidating dashboard most business owners ever see. Twenty-three reports. Cryptic statuses like “Discovered — currently not indexed.” A “Validate Fix” button that does almost nothing visible.
This tutorial demystifies the indexing report and walks you through fixing every common error, in the order that actually matters for traffic. By the end, you’ll know exactly why a page isn’t ranking — and what to do about it this week.
Indexing is the gate between your content and Google’s search results. A page must be crawled, then indexed, then ranked — and most pages stuck below page 10 are failing at step 2, not step 3. The Search Console Pages report shows exactly why. This guide covers the 8 indexing statuses you’ll see, how to fix each, and how long Google takes to re-index after you submit a fix.
What “Indexed” Actually Means
Indexing happens in three stages, and a failure at any stage prevents ranking:
- Discovery — Google finds your URL (via your sitemap, an internal link, or an external link).
- Crawling — Googlebot fetches the page’s HTML, CSS, and JavaScript.
- Indexing — Google parses the content, determines its quality, and decides whether to add it to the searchable index.
A page can be discovered but not crawled (resource limits). It can be crawled but not indexed (quality threshold). It can be indexed but never ranked (intent mismatch). Search Console’s Pages report tells you which stage each URL is stuck at.
Where to Find the Indexing Report in GSC
Log in to search.google.com/search-console. In the left sidebar, click Indexing → Pages (sometimes labeled “Page indexing”). You’ll see two summary cards: Indexed (green) and Not indexed (red). The interesting data is always under Not indexed.
Below the summary, you’ll see a table grouped by status. Each row is an indexing issue with a count of affected URLs. Click any row to see the specific URLs.
It’s normal to have 10–30% of your URLs in the “Not indexed” bucket — admin pages, paginated archives, tag pages, etc. The goal is to make sure every commercial URL (services, products, blog articles, location pages) is indexed. Filter the URL list by the categories below before panicking about totals.
The 8 Most Common Indexing Errors (And the Fix for Each)
In order of severity for revenue-driving pages:
1. Submitted URL Marked ‘noindex’
What it means: Your page has a <meta name="robots" content="noindex"> tag in its HTML, telling Google not to index it — but you submitted it via sitemap, suggesting you do want it indexed.
Why it happens: Inherited from a staging template, accidentally enabled in WordPress (Settings → Reading → “Discourage search engines”), or set via Yoast/RankMath SEO plugins on individual pages.
The fix: View page source, search for noindex. If present, remove it via your CMS or plugin. If using WordPress, check both global settings AND the per-page SEO panel. Resubmit to GSC.
2. Crawled — Currently Not Indexed
What it means: Google fetched the page successfully, evaluated its quality, and decided it’s not worth indexing right now.
Why it happens: Thin content (under 300 words), near-duplicate content with another indexed page, low topical authority of the domain, or pages with no internal links pointing to them.
The fix: Three options, in order of difficulty:
- Improve content depth — expand to 1,200+ words with original insights, examples, and data.
- Add internal links from indexed pages — build topical relevance signals. This is exactly the strategy we cover in internal linking architecture for topic clusters.
- Consolidate — if multiple thin pages target the same topic, merge them with a 301 redirect (see our 301 redirect guide).
3. Discovered — Currently Not Indexed
What it means: Google knows the URL exists but hasn’t fetched it yet. This is a crawl budget issue, not a content issue.
Why it happens: Site has too many URLs relative to its authority, server response times are slow, or the URL is buried 5+ clicks deep from the homepage.
The fix: Improve site speed (Core Web Vitals), add internal links from high-authority pages to the orphan URL, and prune low-value pages competing for crawl budget. Full deep-dive in our breakdown of crawl budget for internal pages.
The “Validate Fix” button only re-runs Google’s automated check — it doesn’t force a re-crawl. For pages with major changes, also submit the specific URL via the “URL Inspection” tool and click “Request Indexing.” This puts it in a priority queue for re-evaluation within 1–3 days.
4. Page with Redirect
What it means: Google followed a 301 or 302 from this URL to another. Often legitimate, but sometimes indicates a misconfigured redirect.
Why it happens: Intentional URL changes, accidental redirect loops, or old URLs that should be removed from your sitemap.
The fix: If intentional — remove the redirected URL from your sitemap.xml. If unintentional — trace the redirect chain with a tool like httpstatus.io and fix the offending rule. Make sure no redirects bounce through 2+ hops.
5. Soft 404
What it means: The page returns a 200 OK HTTP status, but Google’s algorithm determined the content looks like an error page (“not found,” “no results,” etc.).
Why it happens: Empty category pages, no-results search pages with HTTP 200 status, e-commerce out-of-stock pages, or thin pages with apologetic boilerplate.
The fix: Either make the page genuinely useful (add content, related products, alternatives) or return a real 404/410 status code. Don’t leave it in the “dead zone” of 200-but-empty.
6. Excluded by ‘noindex’ Tag
What it means: Same as #1 but for URLs you didn’t submit in your sitemap. Usually intentional (admin pages, cart, thank-you pages).
The fix: Verify these should be noindexed. If they should be public (e.g., a blog category accidentally tagged), remove the noindex tag.
7. Blocked by robots.txt
What it means: Your robots.txt file is telling Google not to crawl this URL.
Why it happens: Overly broad disallow rules, staging-site rules accidentally pushed to production, or WordPress/Shopify defaults blocking /wp-admin/ patterns that catch real URLs.
The fix: Visit yoursite.com/robots.txt. Use Google’s robots.txt Tester in GSC to verify which rule is blocking the URL. Edit the rule to exclude commercial pages.
User-agent: *
Disallow: /wp-admin/
Disallow: /cart/
Disallow: /checkout/
Allow: /wp-admin/admin-ajax.php
Sitemap: https://yoursite.com/sitemap.xml8. Server Error (5xx)
What it means: Your server returned a 500, 502, 503, or 504 when Googlebot tried to fetch the page.
Why it happens: Hosting downtime, plugin conflicts, database overload, or rate limiting that mistakes Googlebot for an attacker.
The fix: Check server logs for the time stamps shown in GSC. Identify the trigger (specific plugin, traffic spike, deploy). If using a CDN like Cloudflare, whitelist Googlebot in your firewall rules.
The Step-by-Step Diagnostic Workflow
For any single URL that won’t index, run this 5-step diagnostic:
- Step 1: Paste the URL into GSC’s URL Inspection tool. Read the result — it tells you the current index status, last crawl date, and any blocking issues.
- Step 2: Click Test Live URL. This crawls the page in real time and shows whether the current version can be indexed.
- Step 3: Check the “Coverage” details. Look for
noindex,robots.txtblocks, canonical conflicts, or render errors. - Step 4: View “Crawled page” tab — this is the HTML Google actually sees, after JavaScript renders. Verify your content is present.
- Step 5: Fix the issue at the source (CMS, plugin, server). Click Request Indexing to queue a fresh crawl.
Real Case: Plano Medical Practice Recovers 47 Pages from “Discovered Not Indexed”
In March 2026 we audited a Plano-area medical practice with 92 service-area landing pages (variations like “family dentist Frisco,” “pediatric dentist Allen,” etc.). Of those, 47 sat in “Discovered — currently not indexed” for 8+ months. The owner thought Google was penalizing local search.
The actual cause: 47 of those pages had identical 90% of content, with only the city name swapped. Google had crawled the first 45, recognized the pattern, and stopped crawling the rest because it didn’t see new value.
The fix:
- Rewrote each location page with genuinely local content: actual office hours for that location, parking instructions, local insurance providers accepted, photos of the specific building.
- Added internal links from 4 high-authority pillar pages to each location page.
- Submitted each URL individually via GSC’s URL Inspection → Request Indexing.
How Long Until Google Re-Indexes a Fixed Page
Realistic timelines based on observation:
| Action | Re-index time (typical) |
|---|---|
| Remove noindex tag + Request Indexing | 1–3 days |
| Fix robots.txt + resubmit sitemap | 3–7 days |
| Improve content quality (Crawled-not-indexed fix) | 2–6 weeks |
| Crawl budget improvements (Discovered-not-indexed) | 4–12 weeks |
| Brand-new low-authority domain | 2–6 months |
If a high-priority page hasn’t indexed within these windows, something is still blocking. Re-run the URL Inspection workflow and look for newly introduced issues from CMS or plugin updates.
Preventing Indexing Issues Going Forward
The single biggest predictor of indexing problems is uncontrolled site sprawl. As your site grows, follow these rules:
- Every commercial page gets internal links — no orphans.
- Audit your sitemap monthly — remove redirected and obsolete URLs.
- Use a staging environment with full
noindex— never let staging URLs leak into production. - Run a quarterly technical audit — our 35-point technical SEO checklist catches indexing risks before they become traffic losses.
- Monitor schema markup — broken JSON-LD can quietly remove pages from rich results even when they’re indexed. See how broken schema markup hides your business.
Frequently Asked Questions
Why does Google Search Console say my page is “Discovered” but won’t crawl it?
This is a crawl budget issue. Google has finite resources allocated to each site, and yours has either too many low-value URLs competing for attention, or slow server response times that limit how many URLs Googlebot fetches per visit. Fix by improving page speed, removing low-value URLs from your sitemap, and adding internal links from high-authority pages to the orphan URL.
How often should I check the GSC Pages report?
For active sites publishing weekly, check it weekly. For stable sites, monthly is enough. After any major change — migration, redesign, plugin update — check daily for 2 weeks. The report updates every 24–48 hours, so daily checking more often than that is wasted effort.
Will clicking “Request Indexing” on the same URL multiple times help?
No. The first request adds it to the priority crawl queue. Subsequent requests within 24 hours are ignored, and excessive requests can flag your account for “Quota exceeded” warnings. Submit once per URL, wait 3 days, then re-check the status before resubmitting.
My sitemap shows 200 URLs but GSC only indexed 140. Is that a problem?
Not necessarily. Many sites have 20–30% of URLs that Google legitimately doesn’t index (paginated archives, near-duplicate variants, low-traffic tags). The question is which URLs aren’t indexed. Filter your sitemap URLs by commercial value — service pages, product pages, blog articles — and verify those specifically are indexed. Long-tail or admin URLs not being indexed is fine.
Should I submit individual URLs via URL Inspection or rely on the sitemap?
Use both, strategically. Submit your sitemap once, then update it any time the URL list changes. Use URL Inspection’s “Request Indexing” for individual high-priority URLs after major content changes — like a new blog post you want indexed quickly, or a page you just fixed an issue on. Don’t use it for routine sitemap submissions; that’s what the sitemap is for.
Pages stuck in “Not Indexed” despite your best efforts?
We’ll run a deep GSC diagnostic, identify every blocker (server, schema, crawl, content), and deliver a prioritized fix list within 5 business days.
Get an Indexing Audit Explore Technical SEO Services