Skip to content
← Back to Blog

Your Pricing Page Has Traffic. Google Never Indexed It.

Aug 29, 2026EventDash Team

TL;DR

  • Analytics visits and Search Console impressions are different stories—people can reach a page Google has not indexed.
  • "Crawled, currently not indexed," noindex tags, and stale crawl state are the usual reasons a live URL stays out of search.
  • Check URL match (www vs apex), coverage, a site: search, and internal links, then refresh the sitemap and Request indexing in Search Console.
  • EventDash's SEO tab puts product traffic next to weak indexation; inspect updates coverage—it does not queue the URL.

Two dashboards, two stories

EventDash says /pricing got visits this week.

Search Console says that URL has zero impressions — or “crawled, currently not indexed.”

Both can be true. Product analytics records people who already found you (ads, email, a bookmark, a teammate). Search Console records what Google showed in search. If the page is not in the index, organic search will not send that traffic.

The damage is quiet. You keep shipping the page. You keep measuring it. Google never treats it as a result.

Why a live page stays out of the index

Common, boring reasons:

  1. Google crawled it and declined. Coverage like “Crawled - currently not indexed” means the crawler saw the URL and did not add it. Thin or duplicate content, weak internal links, and a missing sitemap all show up here.
  2. The page blocks indexing. A noindex robots meta tag or X-Robots-Tag header tells Google not to list it. In EventDash this appears as BLOCKED_BY_META_TAG or BLOCKED_BY_HTTP_HEADER. INDEXING_ALLOWED only means there is no noindex — not that the URL is already indexed.
  3. Google does not have a recent opinion. INDEXING_STATE_UNSPECIFIED is “we don’t know yet,” often because the last crawl is stale. It is not a rejection.
  4. Discovery is slow. New URLs wait on links and sitemaps. Submitting /sitemap.xml in Search Console is the write API that actually exists.

There is no general “submit this URL to Google” API. The Indexing API is for JobPosting and BroadcastEvent. For a normal marketing page, Request indexing lives in Search Console.

What to check this week

  1. Confirm the URL in EventDash actually matches the property in Search Console (www vs apex, trailing slash).
  2. Open coverage: indexed, crawled-not-indexed, or excluded.
  3. Search for the page’s title or a unique sentence with site:yourdomain.com.
  4. Follow internal links from pages that already rank.
  5. Submit or refresh /sitemap.xml.
  6. If Google still omits it, open URL Inspection and click Request indexing there.

Give it time. After Google accepts a request, indexing can take up to 48 hours — often longer.

Analytics and Search Console in one tab

EventDash’s SEO tab (Standard and Professional) connects the Search Console property for the app domain. You get a Performance chart (clicks, impressions, CTR, position), a Needs attention list of pages with product traffic and weak indexation, inspect, and sitemap submit.

EventDash pageviews on that list are current to this hour. Search Console’s last 24 hours wait several hours, and daily clicks and impressions still lag about two days. That is the gap the tab is built for: you already have visits; Google’s report has not caught up.

Inspect updates coverage from Google. It does not queue the URL. Request indexing still opens Search Console.

If search is not the job, skip this tab. If /pricing converts in analytics and never appears in search, start there.

Related: