CARBON — Engineering ConfidenceUser Guide
CHAPTER 20 / 60 Pro

/carbon-geo

Evaluate GEO (generative engine optimization) and AI-search SEO for a webpage or site: crawl/indexing eligibility, answer usefulness, entity and source credibility, structured-data truth, and evidence-qualified AI citations or visibility. Produce prioritized fixes and a branded GEO report; use carbon-agentic instead for agents operating UI or APIs.

Yuki · Landing pagesExperience & accessibility

When to use it

You want to improve the evidence a search or answer system can find.

Before you start

Inspect crawl eligibility, semantic text, entity clarity, source credibility and structured-data truth. Separate observed citations from readiness suggestions; do not promise rankings.

Try this in your coding agent.

/carbon-geo Review the public product page for clear AI-search discovery and source attribution.

Replace sample paths with your project. Slash names are shorthand; your host may use a plugin prefix or a skill picker. Invocation help →

ILLUSTRATIVE WALKTHROUGH

Product discovery

An expanded teaching example, not a recorded or live execution. The report stays visible while the replay explains how to read it.

  1. 01Read context
  2. 02Investigate
  3. 03Show evidence
  4. 04Report

Coding-agent conversation

Read context

I’m reviewing product discovery. I’ll keep the scope and permissions explicit.

Investigate

Follow the weakest evidence link and record what remains blocked.

Show evidence

Here is the evidence trail to inspect: Rendered page vs semantic document: pricing and supported hosts only inside a graphic.

Report

Key product facts are absent from crawlable page text. No guaranteed search ranking or AI citation.

CARBON

Example report

Illustration
Meaning, price and presentation
Meaning, price and presentation — TestBucks teaching screen

TestBucks course screen with illustrative analysis. The screenshot supplies context; the demo does not establish a newly observed bug.

  1. User intent
  2. Visible content
  3. Meaning / consistency

Illustrated outcome

Key product facts are absent from crawlable page text.

Evidence to inspect

Rendered page vs semantic document: pricing and supported hosts only inside a graphic.

Still untested / not established

No guaranteed search ranking or AI citation.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

For product discovery, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.

An inspectable trail

Rendered page vs semantic document: pricing and supported hosts only inside a graphic. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

No guaranteed search ranking or AI citation.

The next decision

Decide whether the evidence calls for a focused check, a reviewed fix or more context. Do not convert a plausible example into a verified finding.

Adapt the example to your project

  1. Replace product discovery with a real feature, path or decision in your project.
  2. State the expected rule and its source. Include safe fixtures, constraints and a budget where appropriate.
  3. Ask for exact evidence and remaining gaps. Approve consequential actions separately.
/jay Review the /carbon-geo result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/carbon-content →/carbon-agentic →

Content checked against the local command definition: skills/carbon-geo/SKILL.md. Examples adapted from the homepage’s TestBucks walkthroughs. Availability is edition- and host-dependent.