Hardik Dewra

3 min read

Why your landing page is not showing up on Google

Missing from Google usually means the page is not indexed. The Search Console statuses that name the cause, and the order to check them in.

When your landing page is not showing up on Google, the cause is usually indexing rather than ranking, and it usually sits in a setting on your own site. Open Search Console, run URL Inspection on the exact URL, and read the status it gives you. That single screen tells you whether Google holds the page at all.

Two reasons a landing page is not showing up on Google

Searching your own headline in an incognito window proves nothing. Use URL Inspection in Search Console instead. It tells you one of two things: the URL is on Google, or it is not. If it is on Google and still invisible for your terms, you have a ranking problem, which comes down to content and links and takes a long time to solve. If it is not on Google at all, keep reading, because most of the causes below are fixable in an afternoon.

The statuses that mean you blocked it yourself

The Google page indexing report uses precise labels, and each label points at a different mistake. "URL marked 'noindex'" means a robots meta tag or an X-Robots-Tag header is telling Google to stay out, which happens constantly when a staging setting ships to production. "URL blocked by robots.txt" means the crawler never got through the door. "Alternate page with proper canonical tag" and "Duplicate without user-selected canonical" both mean Google decided some other URL is the real version of this content.

noindex and robots.txt cancel each other out

This one catches experienced people. Google is explicit about it: for the noindex rule to be effective, the page must not be blocked by robots.txt and must otherwise be reachable by the crawler. If Googlebot cannot fetch the page, it never sees the noindex, and the URL can still turn up in search results. Blocking a page in robots.txt to keep it out of Google does the opposite of what you intended. Let the crawler in and use noindex, or let it in and let it index.

Discovered and crawled are not the same status

"Discovered - currently not indexed" means Google knows the URL exists, usually from a sitemap or a link, and has not fetched it yet. That points at crawl scheduling and weak internal linking. "Crawled - currently not indexed" is the harsher one. Google fetched the page, read it, and chose to leave it out. On a landing page that usually means thin content, near duplicate content, or a page that reads like an ad with nothing else on it. Speed will not rescue that status. Google states there is no single page experience signal, and that good Core Web Vitals numbers do not guarantee good rankings. The fix is more substance on the page. A lighter hero image will not do it.

Landing pages generate duplicates by design

You build one page, then a variant for a second audience, then a third for another city, and the copy runs 90% identical across all three. Google picks one and quietly drops the rest. Either make the pages genuinely different or point a canonical at the version you want indexed. Check the boring causes too: a trailing slash version and a non-slash version both live, ad parameters creating separate URLs, and a staging domain that is still public and still indexable.

Some of your pages should not be indexed at all

A paid traffic page for one campaign, with an offer that expires in three weeks, does not need to be in the index. It gets its visitors from the ad. Indexing it adds a thin page to your site and hands Google another near duplicate to sort through. Decide page by page. Evergreen pages that answer a real search go in the sitemap. Campaign pages, thank you pages and gated asset pages get noindex and stay out.

The order to check things in

Run URL Inspection first. Then view source and search the HTML for noindex. Open yoursite.com/robots.txt next and read the whole file. Confirm the canonical tag points at the page itself. Check that the URL sits in your sitemap and that the sitemap is submitted. Then click Request Indexing once, and only once, because queuing it repeatedly changes nothing. Give it a week. If the page is still missing after that, the problem is the page and not the plumbing.