A promise with context
Design can put an offer, a qualifier, and the next action in one visual relationship.
Offer + condition + actionProduct page audit for AI search
Make your product understandable to AI search, agents, and humans.
JIG-ME audits product pages, source evidence, and structured data so the information you publish carries clear facts, conditions, and next actions.
A guided service led by Jigme, built on SMA and supported by Product Atlas.
- One source of truth for your product
- Base avatars and contextual modes grounded in shared facts
- An editable product graph
- JSON, CSV, and a Neo4j import package
BREATHmg / Product Atlas
Captured sampleYour product, connected.
Switch avatar views. Explore the facts relevant to each context.
BASE AVATAR
CONTEXTUAL MODE
AvatarContextual modeProductCanonical facts
01 / The problem
Your page is more than the words a crawler can lift from it.
People use layout, proximity, and context to understand an offer. Retrieval systems may take text, structured data, selected chunks, or a rendered page. A condition on a different page can disappear from the answer.
Pieces retrieved separately
Headings, snippets, metadata, and outside descriptions can travel without the relationship that made them accurate.
Context can be separatedConfident, incomplete answers
A system can find a true phrase and still miss who qualifies, what is included, or what changed.
A true fragment, an incomplete offerBREATHmg / Case evidence
What the source said. What the test could read.
The original homepage had Organization and WebSite JSON-LD, yet Google's Rich Results Test found no eligible items. After Product and Offer markup was published, the same test reported one valid Product snippet item and one valid Merchant listing item.
BEFORE PUBLICATIONGoogle Rich Results Test
0 eligible itemsNo eligible rich-result items
The page crawled successfully. Organization and WebSite data were present in the source, but did not produce an eligible item in this test.
AFTER PUBLICATIONPublished Product / Offer markup
2 valid categoriesProduct and Merchant listing items
Google's parser reported one valid Product snippet item and one valid Merchant listing item. Optional field warnings remained.
This establishes parser eligibility after publication. It does not prove search display, indexing, rankings, sales, or a causal change in AI answers. Read the BREATHmg evidence ↗
02 / The method
Settle the meaning once. Express it where it matters.
SMA, Signal, Meaning, Action, is the method behind JIG-ME Product Atlas. It links a published claim to its source, conditions, owner decision, audience context, and destination. Your team remains in control of what is approved.
Map priority paths
Identify the entry points that matter and inspect the pages supplying their meaning.
Entry points + dependenciesApprove canonical facts
Your team reviews each consequential claim with qualifications, evidence, and status beside it.
Evidence + owner decisionsPrepare useful outputs
Explore connected facts in a product graph, then prepare page copy and selected data formats for destinations you name.
Formats follow the destinationCheck after publication
Repeat relevant page and answer checks, then hand off the source and files.
Documented checks + handoffExperience the workspace
JIG-ME Product Atlas
The full journey starts here. Explore the BREATHmg project overview, then open any stage to inspect evidence, edit facts and audience contexts, and prepare your exports.
BREATHmg / Captured project overviewOpen the complete demo ↗
This is the actual Atlas Overview content. Select a stage to open it in the full demo. Edits in the demo stay in your browser.
The person behind the work
Jigme / Product designer
I work across strategy, interface design, and implementation, bringing a UX and product design lens to the audit and your team's decisions.
Experience across developer platforms and enterprise healthcare, including Neo4j and Anthem.
More about my background ↗The service
Start with the product paths that matter.
I map your priority entry points and supporting pages, audit what they communicate, resolve consequential facts with your team in Product Atlas, and prepare changes and tests for the agreed destinations.
- Scope the product paths and buyer decisions.
- Audit source evidence and compare claims.
- Walk through findings and the Atlas workspace together.
- Let your team edit and approve the facts.
- Review, implement, verify, and hand off.
Common questions
What your team needs to know.
Is JIG-ME a service or a software tool?
It is a guided service supported by Product Atlas. I audit what your site communicates, explain the findings through a UX and product design lens, and guide your team through the workspace so you can resolve the facts together.
Will this guarantee search rankings or accurate AI answers?
This work improves the information a system can encounter. It does not promise that a search provider will index it, display a rich result, or use it in an AI answer. Each publication check is documented with what it establishes.
What does my team receive?
The source record and selected implementation files. Product Atlas includes an editable product graph and can preview canonical JSON, page HTML, JSON-LD, Markdown, XML, CSV, and YAML. Graph exports include Graph JSON, a Neo4j import package, and RDF Turtle. The engagement produces the formats named in the agreed implementation, not a pile of files with nowhere to go.
What does a typical first engagement cover?
Some clients start with one priority page. Others have several connected entry points that need to be understood together. The assessment sets a useful scope for the audit, Atlas work, implementation, and testing. Monitoring is scoped separately.
Bring your product. We will map the work.
Book a free 15-minute assessment ↗