Lumen Metrics pricing (demo)

Target URL

https://lumenmetrics.example/pricing

Target query

“product analytics pricing” user-provided

Audit timestamp

2026-09-18 10:00 UTC

Search discovery

Found at position 6 in checked results

Fetch extraction

Content extracted

Browser verification

Skipped (no objective or turned off)

Actionable findings

7

Most important issue

Key query terms are largely absent from the extracted page

Recommended first action

State analytic, pricing explicitly in the title, H1 and the first paragraph, in natural language.

These results describe sampled retrieval evidence from 1 search request(s) and 1 fetch request(s) at one point in time. They are not guaranteed universal AI rankings.

Observed rows report something a tool returned. Inferred rows are conclusions drawn from absence and may need confirmation. “Not checked” means no evidence was collected, never that it passed.

1. F-001 Key query terms are largely absent from the extracted pageSeverity: HighConfidence: ●●○ medium confidence

   Deterministic checkObservedrelevance

   What the evidence shows

   Only 1 of 3 key terms from "product analytics pricing" appear in the extracted text. Missing: analytic, pricing.

   Evidence excerpt

   Plans | Lumenfrom ev_fetch_1

   Why it may matter

   Retrieval and ranking systems rely on the page stating what it is about in the words people use.

   Recommended fix

   State analytic, pricing explicitly in the title, H1 and the first paragraph, in natural language.

   Suggested replacement copy or code

   <title>product analytics pricing — lumenmetrics.example</title>
   <h1>product analytics pricing</h1>

   Expected outcome (no guarantee)

   The page's topic becomes unambiguous to extraction and ranking systems. Results may vary.

   How to verify

   Re-run the audit and check the Query coverage table.

   Evidence: ev_search_1ev_fetch_1 · Section: Visibility gap analysis

2. F-002 Meta description missing or outside typical lengthSeverity: MediumConfidence: ●●○ medium confidence

   Deterministic checkObservedmetadata

   What the evidence shows

   Fetch reported no meta description for this page. Fetch returns the description it detected; confirm in the page source.

   Evidence excerpt

   Fetch reported no meta description for this page.from ev_fetch_1

   Why it may matter

   Descriptions often seed the search snippet and give extractors a concise summary.

   Recommended fix

   Write a 120–160 character description that states what the page offers and for whom.

   Suggested replacement copy or code

   <meta name="description" content="What this page offers, for whom, and the key differentiator.">

   Expected outcome (no guarantee)

   A controllable summary is available to snippet generators; they may still choose other text.

   How to verify

   Re-run the audit.

   Evidence: ev_fetch_1 · Section: Technical checks

3. F-003 The page never says it is product analytics softwareSeverity: MediumConfidence: ●●○ medium confidence

   AI-interpretedObservedrelevance

   What the evidence shows

   Evidence suggests the page describes plans in terms of events and dashboards but never uses the phrase product analytics. The opening line says Lumen helps teams understand how people use their software.

   Evidence excerpt

   Lumen helps teams understand how people use their softwarefrom ev_fetch_1

   Why it may matter

   Searchers and retrieval tools match pages to queries by the words the page uses. A pricing page that does not name its category is harder to connect to a category query.

   Recommended fix

   Name the category in the title, H1 and the first sentence, then keep the plan details below it.

   Suggested replacement copy or code

   <title>Lumen Metrics pricing — product analytics plans</title>
   <h1>Product analytics pricing that scales with your team</h1>
   <p>Lumen is product analytics software for SaaS teams. Start free; upgrade when your event volume grows.</p>

   Expected outcome (no guarantee)

   The category is explicit to both people and extraction tools. Search results may or may not change.

   How to verify

   Re-run this audit and check that the query terms appear in the title and H1 rows of the coverage table.

   Evidence: ev_fetch_1ev_search_1 · Section: Visibility gap analysis

4. F-004 Plans are priced per event, but 'event' is never definedSeverity: MediumConfidence: ●●○ medium confidence

   AI-interpretedObservedcontent-gaps

   What the evidence shows

   Every plan is limited by events a month, and the FAQ discusses going over the plan, yet the page does not say what counts as an event.

   Evidence excerpt

   What happens if I go over my plan?from ev_fetch_1

   Why it may matter

   Competing results explain event-based billing in their snippets. A buyer comparing prices cannot compare quotas without the definition.

   Recommended fix

   Add a one-sentence definition of an event and an example of typical monthly usage under the plan table.

   Suggested replacement copy or code

   An event is any action you send to Lumen, such as a page view, a click or a purchase. A team of 20 typically sends 300,000 events a month.

   Expected outcome (no guarantee)

   Fewer unanswered questions on the page and a clearer excerpt for tools that summarise pricing.

   How to verify

   Check that the definition appears in the Fetch extraction.

   Evidence: ev_fetch_1ev_search_1 · Section: Visibility gap analysis

5. F-005 Title length may be suboptimalSeverity: LowConfidence: ●●○ medium confidence

   Deterministic checkObservedmetadata

   What the evidence shows

   "Plans | Lumen" (13 characters) Very short titles carry little information.

   Evidence excerpt

   "Plans | Lumen" (13 characters)from ev_fetch_1

   Why it may matter

   Overlong titles are truncated; very short ones carry little information.

   Recommended fix

   Aim for roughly 30–60 characters that lead with the main topic.

   Expected outcome (no guarantee)

   More complete display of the title in results.

   How to verify

   Re-run the audit.

   Evidence: ev_fetch_1 · Section: Technical checks

6. F-006 No canonical URL observedSeverity: LowConfidence: ●●○ medium confidence

   Deterministic checkObservedindexing

   What the evidence shows

   No canonical URL observed in page metadata.

   Evidence excerpt

   No canonical URL observed in page metadata.from ev_fetch_1

   Why it may matter

   Without a canonical, URL variants can compete with each other.

   Recommended fix

   Add a self-referencing canonical link.

   Suggested replacement copy or code

   <link rel="canonical" href="https://lumenmetrics.example/pricing">

   Expected outcome (no guarantee)

   Duplicate URL variants consolidate.

   How to verify

   Re-run the audit.

   Evidence: ev_fetch_1 · Section: Technical checks

7. F-007 Competing results emphasise terms this page never statesSeverity: LowConfidence: ●○○ low confidence

   Deterministic checkPotential issuecompetitor-comparison

   What the evidence shows

   At least two competing results mention: based (4), compare (2). None appear in the extracted page.

   No verbatim excerpt is attached to this finding.

   Why it may matter

   These may be expectations searchers associate with the query. They are hypotheses from a small sample, not requirements.

   Recommended fix

   Review whether any of these terms describe your offering truthfully and add them where relevant.

   Expected outcome (no guarantee)

   Better coverage of the vocabulary used for this query.

   How to verify

   Check against the competing pages in the Search evidence.

   Evidence: ev_search_1ev_fetch_1 · Section: Visibility gap analysis

Every finding and check cites these records. Records store normalized, sanitized data only: no keys, headers or credentials.

{
  "request": {
    "query": "product analytics pricing",
    "location": "US",
    "language": "en"
  },
  "metadata": {
    "demo": true
  }
}

{
  "query": "product analytics pricing",
  "page": 0,
  "totalResults": 7,
  "results": [
    {
      "position": 1,
      "title": "Beacon Analytics Pricing — event-based product analytics",
      "url": "https://beaconanalytics.example/pricing",
      "snippet": "Beacon Analytics pricing: a free plan, then event-based billing for product analytics teams. Compare Starter, Growth and Enterprise.",
      "siteName": "beaconanalytics.example"
    },
    {
      "position": 2,
      "title": "Flowpoint pricing | Product analytics for SaaS",
      "url": "https://flowpoint.example/pricing",
      "snippet": "Flowpoint product analytics pricing starts free. Event-based billing, unlimited dashboards and a free plan for early-stage teams.",
      "siteName": "flowpoint.example"
    },
    {
      "position": 3,
      "title": "Statmesh Pricing",
      "url": "https://statmesh.example/pricing",
      "snippet": "Statmesh pricing for product analytics: free plan, usage-based billing and SOC 2 reporting.",
      "siteName": "statmesh.example"
    },
    {
      "position": 4,
      "title": "Compare product analytics tools and pricing",
      "url": "https://toolsradar.example/product-analytics",
      "snippet": "Side-by-side product analytics pricing. Most vendors offer a free plan and bill per event.",
      "siteName": "toolsradar.example"
    },
    {
      "position": 5,
      "title": "Pathlight Analytics pricing",
      "url": "https://pathlight.example/pricing",
      "snippet": "Pathlight pricing: free plan, event-based billing and annual discounts for product analytics.",
      "siteName": "pathlight.example"
    },
    {
      "position": 6,
      "title": "Plans | Lumen",
      "url": "https://lumenmetrics.example/pricing",
      "snippet": "Plans that scale with you. Start free and upgrade when your team grows. Growth is $49/mo.",
      "siteName": "lumenmetrics.example"
    },
    {
      "position": 7,
      "title": "Quillboard pricing",
      "url": "https://quillboard.example/pricing",
      "snippet": "Quillboard pricing for teams that want session replay and product analytics.",
      "siteName": "quillboard.example"
    }
  ],
  "match": {
    "position": 6,
    "method": "exact",
    "url": "https://lumenmetrics.example/pricing"
  }
}

{
  "request": {
    "urls": [
      "https://lumenmetrics.example/pricing"
    ],
    "format": "markdown",
    "links": true,
    "page_metadata": true,
    "ttl": 0
  },
  "metadata": {
    "demo": true
  }
}

{
  "requestedUrl": "https://lumenmetrics.example/pricing",
  "finalUrl": "https://lumenmetrics.example/pricing",
  "title": "Plans | Lumen",
  "description": null,
  "language": "en",
  "author": null,
  "publishedDate": null,
  "textLength": 1569,
  "textTruncated": false,
  "pageMetadata": {
    "robots": "index, follow"
  },
  "links": [
    "https://lumenmetrics.example/",
    "https://lumenmetrics.example/docs",
    "https://lumenmetrics.example/signup",
    "https://github.com/lumenmetrics-example"
  ],
  "latencyMs": 640,
  "text": "# Plans that scale with you\n\nLumen helps teams understand how people use their software. Start free and upgrade when your team grows.\n\n## Free\n\n$0/mo. Includes 50,000 events a month and one dashboard. Community support.\n\n## Growth\n\n$49/mo. Growth includes 500,000 events a month, unlimited dashboards and funnels. Email support.\n\n## Scale\n\n$199/mo. Scale includes 5,000,000 events a month, SSO and a dedicated success manager.\n\n## Frequently asked questions\n\n### Can I change plans later?\n\nYes. You can upgrade or downgrade at any time and billing is prorated.\n\n### What happens if I go over my plan?\n\nWe email you first. Nothing is charged without your approval.\n\nLumen is built by a distributed tea… [869 more characters]"
}

{
  "request": {
    "url": "https://lumenmetrics.example/robots.txt"
  },
  "metadata": {
    "demo": true
  }
}

{
  "url": "https://lumenmetrics.example/robots.txt",
  "status": 200,
  "bodySample": "",
  "genericDisallowsPath": false,
  "aiBotDisallows": [],
  "sitemaps": [
    "https://lumenmetrics.example/sitemap.xml"
  ]
}

{
  "request": {
    "url": "https://lumenmetrics.example/sitemap.xml"
  },
  "metadata": {
    "demo": true
  }
}

{
  "url": "https://lumenmetrics.example/sitemap.xml",
  "status": 200,
  "isIndex": false,
  "listsTarget": true,
  "urlCount": 64
}

• Search is one request to TinyFish Search per query (one page of results). Position means order in that response, not a Google, Bing or universal AI ranking. A page missing from the sample is “Not found in checked results”, which does not mean “not indexed”.
• Fetch returns extracted Markdown plus metadata and links. HTTP status, response headers, JSON-LD and exact markup are not returned, so Sniffsite never infers them from text. TinyFish may serve a cached copy even when a live fetch is requested.
• Browser runs only with a concrete verification objective or when you enable it. It is one session from TinyFish’s network and may differ from what other visitors see.
• robots.txt and sitemap are read directly by Sniffsite from the public site. Directives are declared preferences; compliance depends on each crawler.
• Deterministic checks are computed only from observed data. AI-interpreted findings are produced by a language model from the collected evidence, validated against a schema, and any excerpt that is not verbatim in the cited evidence is discarded.
• Broken links are not tested. A successful Fetch does not prove a page is indexable or readable by every AI tool.
• Semantic analysis: used. API calls made: search 1, fetch 1, browser 0, Gemini 1.