Landing page not indexed: reading the Search Console coverage report and fixing it

A landing page that's been live for weeks, nowhere to be found even when searching its exact title on Google: the instinct is to conclude "Google just doesn't like the page". In reality, Search Console always gives a more precise explanation than that, in the form of a status in the Pages report (under the "Indexing" menu). Each status maps to a different technical cause, with a different fix — treating every non-indexing case the same way (usually by spamming the "Request indexing" button) treats a symptom without ever touching the cause.

The three statuses that most often keep a landing page out of the index

"Discovered - currently not indexed"

Google knows the URL exists — via the sitemap or an internal link — but hasn't taken the time to crawl it yet. This status is almost never a content problem: it's a priority problem. A young or low-authority site gets a limited crawl budget, and Google crawls the pages it judges most likely to be worth the trip first — a signal directly inherited from the founding principle of PageRank, described by Sergey Brin and Larry Page in their 1998 founding paper on Google's architecture: the number and quality of links pointing to a page serve as an approximation of its importance, including when deciding when — or whether — to crawl it. An isolated landing page with no internal link pointing to it sends exactly that signal: "probably not important, crawl it later". The most reliable fix stays internal linking — a link from a page that's already indexed and frequently recrawled (the homepage, a well-ranked blog post) speeds up discovery far more than a manual request ever does.

"Crawled - currently not indexed"

Here, Google did crawl the page — but deliberately chose not to add it to the index. This is the status most often misread as a "penalty", when it's really just a quality filter: content judged too thin or too close to a page already indexed, degraded load times, or an ad landing page that just rephrases an offer already present elsewhere on the site. Unlike the previous status, republishing the sitemap or piling up indexing requests changes nothing as long as the content itself doesn't offer something distinct — the "people-first" principle (a page should offer what can't be found elsewhere) applies here very literally: it's exactly what Google evaluates before refusing to index a page.

"Duplicate, Google chose different canonical than user"

This status hits ad-campaign landing pages especially hard, since they tend to multiply into near-identical variants (UTM parameters, one version per audience or city, a poorly isolated A/B test). Detecting these near-duplicates isn't some arbitrary algorithmic judgment call: the technique traces back to work by Andrei Broder and his co-authors at Digital Equipment, "Syntactic Clustering of the Web" (1997), which laid the groundwork for shingling — breaking a document into overlapping word sequences to measure its similarity to other pages across the web at scale. Two landing pages that only differ by a URL parameter or a hero photo are, to that kind of algorithm, near-identical: Google keeps just one in the index and ignores the rest, with no regard for which one was "supposed" to be the main one. The canonical tag exists precisely to take that choice back from the algorithm.

Statuses, causes and fixes at a glance

How to read the report correctly

1. Open Search Console → Indexing → Pages menu: the chart at the top splits indexed pages from non-indexed pages, and the table below lists each reason for non-indexing along with the number of URLs affected.
2. Click on a specific reason (e.g. "Crawled - currently not indexed") to get the exact list of affected URLs — never generalize from a single case, two landing pages can share the same status for different underlying reasons.
3. Use the URL Inspection tool (search bar at the top of Search Console) on a specific URL to see the version Googlebot actually fetched, the canonical it settled on, and the last crawl date.
4. Only request re-indexing once the cause on the page itself has been fixed — a repeated request on an unchanged page speeds up nothing, and can even read to the algorithm as excessive pinging.

The special case of ad landing pages

Pages built specifically for a Google Ads or Meta Ads campaign often stack two of the three causes at once: they're deliberately kept light on internal links (so as not to clutter the site's navigation) and they closely resemble a product page that already exists. In this specific case, the right answer isn't always to force indexing — a lot of these pages have no real reason to be indexed in the first place, since they only exist to receive already-targeted paid traffic. Explicitly choosing noindex on these pages avoids triggering the three statuses above for nothing, and lets the site's crawl budget focus on the pages that do need to show up in organic results.

Diagnosing a non-indexed landing page means reading the exact reason before acting, rather than repeating the same reflexes (republish, request indexing again, wait) on causes they don't actually fix. LanderKit's 10 templates generate static pages via generateStaticParams — each template, like the webinaire-masterclass template built for a one-off campaign, maps to a clean, unique URL with no duplicated variant by default, viewable on its live demo — but internal linking and avoiding redundant content remain, as with any site, the publisher's job. See also our article on the normal delay before a page shows up on Google if the page just went live, and our technical launch checklist to avoid these statuses in the first place.