Measurement
Query bank expanded to 31 queries
Added commercial, vertical, and infrastructure queries across branded and unbranded intent — tier breakdown on dashboard.
Transparency · In progress
Still being forged.
LuminaForge launched luminaforge.ai in May 2026. This dashboard is live while we collect baselines — Search Console Generative AI access, citation snapshots, performance checks, and schema coverage — the same reporting model every Search & AI Visibility engagement receives. Numbers below are early; we publish them anyway.
Last updated · Baseline collection since
Still being forged
We are collecting baselines — not polishing a vanity score.
LuminaForge went live recently. Google AI impressions (Search Console), LLM citations, and entity authority compound over weeks — not on launch day. This page logs what we measure, what we see today, and how it changes over time.
- Dashboard live since
- Generative SoV baseline
- 0%
- Query bank
- 41 queries · 3 engines
expected early — tracking anyway
last run 2026-07-13
- Google path: Search Console Generative AI reports when the property is in Google's rollout cohort
- Multi-engine path: citation checks across Gemini, Grok, and Perplexity — raw results published, not cherry-picked
- Performance and schema sections reflect what is verifiable now (PageSpeed Insights + CrUX field data + live route audit)
Early snapshots are the point. Radical transparency means showing the work before the numbers look impressive.
Performance targets are verified separately below — see Core Web Vitals and live PSI source links.
Forge log
What we shipped to earn citations
Decision-level transparency — actions taken each week, not vanity metrics. Updated as we ship.
- Measurement
Early-phase transparency reframe
Dashboard copy now leads with baseline collection and readiness scorecard — honest 0% while entity authority compounds.
- Infrastructure
Gemini refresh quota cap
Refresh script caps at 19 Gemini calls per run on free tier and skips remaining checks after quota exhaustion.
- Entity
Directory submissions prepared
Clutch, G2, and DesignRush submission targets documented — profile URLs will flip readiness scorecard when live.
- Content
GEO pillar content shipped
Published GEO agency pricing guide and home-services GEO pillar with FAQPage schema and internal links to case studies.
- Entity
Founder Person schema + LinkedIn sameAs
Nick Hennemann entity wired on /about with Person JSON-LD, CEO title, and LinkedIn profile in Organization sameAs.
- MeasurementMilestone
First citation snapshot archived
Initial Gemini + Grok baseline run committed to data/transparency/current.json with weekly GitHub Action refresh.
- MeasurementMilestone
Transparency dashboard live
Published /transparency with citation tracking, PageSpeed Insights snapshots, and schema coverage — same reporting model client engagements receive.
Readiness scorecard
What we can prove today — 4/7
Citations compound over weeks. These infrastructure signals are verifiable now while the citation baseline builds.
Search Console Generative AI report
PendingRolling out in Search Console 2026 — Performance → AI Overviews & AI Mode.
VerifyAI crawlers allowed
ReadyGPTBot, PerplexityBot, ClaudeBot, Google-Extended, and others allowed in robots.ts.
VerifyClutch / G2 / DesignRush profiles
PendingSubmission targets prepared — profiles pending.
0 of 123 engine checks cited · 0/41 queries
3 engines
Entity confusion: 2%
Trend
Snapshot history
10 snapshots from 2026-05-25 to 2026-07-13.
Citation rate
0%
+0 pts since first snapshot
LCP (mobile lab)
2.3 s
PageSpeed Insights
Performance
Core Web Vitals on the reference build
Lab scores from PageSpeed Insights mobile (Slow 4G, Moto G Power) — not desktop. Verifiable now, independent of citation baselines.
Schema coverage
Structured data deployed across luminaforge.ai
Computed from the live route map — infrastructure we can verify today while citations compound.
- Organization + WebSite
- 1/1
- FAQPage
- 30/30
- BreadcrumbList
- 42/42
- Article
- 31/31
- Service
- 4/4
pages with valid JSON-LD
pages with valid JSON-LD
pages with valid JSON-LD
pages with valid JSON-LD
pages with valid JSON-LD
Query tiers
Citation rate by intent
One blended rate hides the story — branded, commercial, and vertical queries are tracked separately.
Branded
0%
3 queries · Does AI know LuminaForge exists?
Definitional
0%
5 queries · Unbranded education queries — GEO/AEO category ownership.
Commercial
0%
8 queries · Money queries — agency selection and pricing intent.
Location
0%
10 queries · Metro-intent queries — city hubs and near-me agency selection.
Vertical
0%
9 queries · Industry-specific GEO — home services, SaaS, B2B.
Comparison
0%
3 queries · Decision-stage queries — SEO vs GEO vs AEO.
Infrastructure
0%
3 queries · Technical GEO signals — llms.txt, schema, crawlers.
Citation log
No LLM citations yet — we are logging the query bank anyway
LuminaForge launched days ago. Tracked engines have not returned luminaforge.ai as a cited source so far. That is expected. The table below shows every check — including the zeros.
Alternative sources
Who appeared when LuminaForge was not cited
Aggregated from engine source lists on not-cited checks — including wrong-entity matches we are actively disambiguating.
| Domain | Appearances | Engines | Example query |
|---|---|---|---|
| searchenginejournal.com | 26 | Grok | What is Generative Engine Optimization? |
| perplexity.ai | 11 | Grok | What is Generative Engine Optimization? |
| semrush.com | 11 | Grok | What is Generative Engine Optimization? |
| searchengineland.com | 8 | Grok | What is Answer Engine Optimization? |
| moz.com | 7 | Grok | What is Answer Engine Optimization? |
| developers.google.com | 7 | Grok | What is the difference between SEO, GEO, and AEO? |
| brightedge.com | 7 | Grok | Answer engine optimization for contractors |
| luminaforge.comEntity confusion | 6 | Grok | LuminaForge GEO agency |
| originality.ai | 6 | Grok | What is Generative Engine Optimization? |
| surferseo.com | 6 | Grok | Generative Engine Optimization agency llms.txt |
Baseline collection
41 queries · 3 engines · logging 0% today
Snapshots from Gemini, Grok, and Perplexity when API keys are set. Expand any cell to see what each engine returned — including when LuminaForge was not cited.
Showing 5 commercial queries — expand for the full 41-query bank.
| Query | Gemini | Grok | Perplexity |
|---|---|---|---|
| How much does GEO cost | Not cited May 28, 2026, 3:49 PM UTC | Not cited May 28, 2026, 3:49 PM UTC | Pending |
| GEO agency pricing | Not cited May 28, 2026, 3:49 PM UTC | Not cited May 28, 2026, 3:49 PM UTC | Pending |
| Best GEO agency 2026 | Not cited May 28, 2026, 3:49 PM UTC | Not cited May 28, 2026, 3:49 PM UTC | Pending |
| Generative Engine Optimization agency United States | Not cited May 28, 2026, 3:49 PM UTC | Not cited May 28, 2026, 3:49 PM UTC | Pending |
| What does a GEO agency do | Pending | Not cited May 28, 2026, 3:49 PM UTC | Pending |
AI crawler policy
Access policy is part of GEO
GEO is not only schema and blog posts — it is whether AI systems can access and cite your site. LuminaForge publishes its crawler policy and measures citations publicly.
What LuminaForge allows
We invite AI crawlers on the public marketing site. Admin routes and gated client previews stay blocked — everything else is readable for citation checks.
- GPTBot
- OAI-SearchBot
- ChatGPT-User
- ClaudeBot
- Claude-Web
- PerplexityBot
- Perplexity-User
- Google-Extended
- Applebot-Extended
- CCBot
- Bytespider
- Amazonbot
Signals vs full blocks
Many sites mix Content-Signal lines with Disallow rules. They are not the same thing — and GEO agencies should know the difference.
| Signal / rule | Means |
|---|---|
| search=yes | Search and retrieval OK Content may be indexed and used to answer queries — similar to how search engines build an index for results and AI summaries. |
| ai-train=no | Training opt-out (when supported) Signals that content should not be used to train foundation models. Emerging standard — not every crawler honors Content-Signal yet. |
| Disallow: / | Full block for that bot The crawler cannot fetch your pages at all — which usually prevents real-time citation in RAG, not just training. Stronger than ai-train=no. |
Methodology
How we measure — and what we do not claim
01What counts as cited (multi-engine snapshots)
An engine check is marked cited when luminaforge.ai appears in the ordered source URL list for that response, or when the answer text names our domain with enough context to resolve a URL. Position #1 means our link was first in the source list — not a Google rank or Search Console impression.
02Google Search Console (primary for Google AI)
Google Search Console Generative AI performance reports show impressions when your URLs appear in AI Overviews, AI Mode, and generative Discover features. The report is rolling out to a subset of properties in 2026 — export from Search Console when the AI Overviews & AI Mode tab appears. At launch, impressions are available; click and query breakdowns may be limited. Pair with GA4 AI Assistant channel where configured. Official docs: https://developers.google.com/search/blog/2026/06/gen-ai-performance-reports
03How we evaluate third-party SEO advice
LuminaForge aligns Search & AI Visibility with Google's official guidance: foundational SEO for Google Search and generative AI features, Search Console as first-party measurement, and honest labeling of third-party citation snapshots. Source: https://developers.google.com/search/docs/fundamentals/third-party-seo
04One run is not truth
Third-party AI answers are non-deterministic — the same query asked twice can return different sources. We publish snapshot baselines on a weekly cadence and compare deltas over time, not single-run vanity scores.
05Third-party engines tracked
Supplementary snapshots: Gemini (when API key set), Grok, and Perplexity. These do not replace Search Console for Google AI Overviews or AI Mode. Roadmap: ChatGPT browse checks.
06Gemini free-tier cap
Gemini free tier allows roughly 20 requests per day. Our refresh script caps live Gemini checks at 19 per run and carries forward previous results when quota is exhausted. Enable AI Studio billing for full same-day coverage.
07PSI lab data vs CrUX field data
PageSpeed Insights reflects lab conditions on a throttled mobile profile — good for regression testing. CrUX field data reflects real Chrome users over 28 days (good / needs improvement / poor distributions). We publish both when available.
08Entity confusion
Wrong-domain lumina* sources (unrelated GitHub repos, luminaforge.com, etc.) are tracked separately as entity confusion — a leading indicator that our brand entity is not yet disambiguated in AI retrieval.
09Generative share of voice (SoV)
SoV (%) = (engine checks where luminaforge.ai is cited ÷ total engine checks in the query bank) × 100. One query tested across three engines counts as three checks. This is a supplementary multi-engine baseline — not a substitute for Search Console Generative AI impressions.
10llms.txt (non-Google)
Optional compact AI brief at /llms.txt for crawlers that choose to read it. Google Search does not use llms.txt for ranking or generative AI features — we ship it for other AI systems, with that disclaimer published per Google's AI optimization guide.
11AI crawler access
Third-party AI crawlers (GPTBot, ClaudeBot, PerplexityBot) are explicitly allowed for non-Google citation paths. Google AI Overviews and AI Mode use the Search index via Googlebot — not a separate GEO crawler hack. See robots.txt on this site.
FAQ
Questions about the dashboard while we collect baselines.
6 answer-ready questions — semantic markup and FAQPage schema for search and AI assistants.
6 Q&As · FAQPage schema
What does the LuminaForge transparency dashboard show?
Citation snapshots across Gemini, Grok, and Perplexity for a defined query bank, Core Web Vitals from PageSpeed Insights, CrUX field data when available, and structured-data coverage computed from the live route map. LuminaForge launched in May 2026 — numbers are early baselines. Client engagements receive the same reporting model.
Why is the citation rate 0%?
LuminaForge.ai launched recently. LLM citations compound from entity authority, named experts, third-party directories, and time in market — not from schema markup alone. We publish 0% while we collect baselines so the dashboard stays honest. When citations appear, they will show here first.
Why does Grok show the wrong LuminaForge?
LuminaForge.ai launched recently. AI engines often conflate similar names — unrelated GitHub repos, luminaforge.com, or other Lumina-branded projects. We track these as entity confusion in the alternative sources panel and resolve them with named founder entity, sameAs profiles, directory listings, and consistent NAP — not schema alone.
How often is citation data updated?
LuminaForge runs the conversational query bank on a weekly refresh cycle (Mondays UTC via GitHub Action), publishes snapshot deltas, and expands the bank as new content ships.
Can I get this dashboard for my own website?
Yes. Every LuminaForge SEO, GEO, and AEO retainer includes citation tracking and performance reporting — including the early baseline period while numbers compound.
Why publish performance and citation data publicly?
LuminaForge dogfoods its own methodology. Public dashboards make every claim auditable — including before the citation numbers look good. The same standard applies to client work.
Ready to forge?
Let's build the site that becomes the answer.
Tell us about your project. We respond within one business day and book the first call inside a week.