DEV Community

amy5193111-svg
amy5193111-svg

Posted on

Site Is Not Indexed? Debug It in Search Console, Not With Backlinks

#seo #website #webdev

Your New Site Is Not Indexed? Debug It in Search Console, Not With Backlinks

I run a few small sites. Every time one of them goes live, someone eventually asks the same question: "Google still hasn't indexed it - should I buy backlinks?"

Usually, no. Most of the time the problem is visible in Google Search Console within ten minutes, and it is not about authority at all. This is the checklist I actually run, in this order.

1. Confirm the sitemap is a sitemap

Submitting a sitemap in GSC feels like a finish line. It is a starting line.

Check two things before you submit:

  • The URL returns real XML, not an HTML page. A very common failure: a reverse proxy or SPA fallback serves 200 OK with your homepage HTML at /sitemap.xml. GSC records this as "couldn't fetch" and you get nothing.
  • robots.txt lists the sitemap and doesn't block the paths inside it.

Quick check from a terminal:

curl -sI https://example.com/sitemap.xml | head -5
curl -s https://example.com/sitemap.xml | head -3
Enter fullscreen mode Exit fullscreen mode

If the first line of the body is <!doctype html>, you have your answer.

2. "Discovered - currently not indexed" is an internal-linking problem

This is the single most common status for new sites, and people misread it as a penalty. It means: Google knows the URL exists, but has no reason to spend crawl budget on it.

Crawl priority is mostly internal PageRank. If your important pages are only reachable from the sitemap - or from an archive page buried five clicks deep - they are effectively orphaned.

The fix is unglamorous and works:

  • Put your core pages on the homepage, in real <a href> links
  • Link between related articles with descriptive anchor text
  • Make sure your homepage isn't linking to URLs that redirect elsewhere

A quick audit: fetch your homepage and count how many links point at pages you actually want indexed.

curl -s https://example.com/ | grep -o 'href="https://example.com/[^"]*"' | sort | uniq -c
Enter fullscreen mode Exit fullscreen mode

3. "Crawled - currently not indexed" is usually a quality or duplication signal

Open URL Inspection -> Test Live URL -> View Crawled Page and look at what Googlebot actually received:

  • Garbled characters (encoding issues)
  • A blank shell (content rendered client-side only)
  • A 404 or a redirect chain
  • A server so slow that the crawler gave up

And the sneaky one: near-duplicate pages. If you have 50 articles that all say roughly the same thing, Google will index one and skip the rest. In that case consolidation is the answer - merge, then 301 the duplicates into the survivor.

4. Check for redirect chains and stale links

Internal links pointing at redirected URLs burn crawl budget on every pass. Crawl your homepage and archives, and update any link whose target returns a 301.

If you consolidated pages, also remove the retired URLs from your sitemap. Advertising URLs that only redirect is a signal you should not send.

5. No impressions? Check whether the query space exists

If pages are indexed but the Performance report is empty, you probably aren't ranking - or nobody searches the way you wrote. Look at Search Console -> Performance -> Queries. If you see impressions with a position around 10-20, that is a page worth improving rather than replacing. Add depth to what already half-ranks instead of publishing another article.

6. What actually moves the needle when everything technical is clean

Once the technical side is green and nothing is indexed, the remaining bottleneck is crawl demand - which comes from off-site signals and content uniqueness:

  • Get real links from pages Google already crawls
  • Publish something that changes (live data, pricing, benchmarks)
  • Cut the number of near-duplicate URLs on the site instead of adding more

Publishing five more articles a week while twenty URLs sit unindexed makes the ratio worse, not better. That was the mistake I made the first time.

7. IndexNow is free - use it

Google has no public instant-indexing API outside the (quota-limited) "Request Indexing" button, but Bing and Yandex support IndexNow: host a key file, POST your URLs, and you get crawled quickly. It won't help Google directly, but it's ten minutes of work.

I wrote up the longer, ordered version of this checklist - including how to read the "Discovered" drilldown and what to do per status - here: Google Search Console indexing troubleshooting

If you're debugging this while also wiring up an API integration, the config side of things lives at api.yushou.xyz/guide.

Top comments (0)