Identify the entity and panel
MIRENA records the entity type, query, market, visible facts, and date.
Search feature reference
Knowledge panels: what they are and how MIRENA uses the signal
A knowledge panel is an automatically generated information box for an entity in Google's Knowledge Graph, based on Google's understanding of information available across the web.
Knowledge panels are not created by one asset, one schema type, or one publisher action. MIRENA uses panel observations to review entity identity, source consistency, attribute coverage, official URLs, conflicting facts, and feedback or maintenance routes.
Informational reference
Reference intent
Five internal stages
One owned handoff
Asset job
Explain how panels are generated, what publishers can and cannot influence, and which entity support workflows act on the signal.
The user task controls the format.
First stage
Identify the entity and panel
Evidence comes before content changes.
Primary output
Reference definition
Every decision keeps its reason.
Search boundary
No display promise
Search systems decide the result presentation.
Ring position
Knowledge Panels belongs to the search feature reference route.
Role inside the ring
Explain what the search presentation is, what publishers can observe, and which MIRENA workflow acts on the signal. The asset receives evidence from the hub and returns approved work, reference notes, or an owned next route.
When MIRENA uses the asset
Start from the visible need rather than a generic feature request.
- A brand, person, place, organisation, or product has a panel.
- A panel contains missing or conflicting facts.
- A team wants to understand panel sources.
- Entity support content needs a realistic expectation boundary.
Internal MIRENA process
Five stages move the evidence into a controlled handoff.
The stages stay sequential. MIRENA stops when page ownership, intent, proof, technical access, current platform support, or approval is missing.
Compare official identity
Panel facts are compared with approved official records and URLs.
Map source consistency
Internal and external references are reviewed for conflicts and missing attributes.
Choose the operational route
Support content, identity repair, feedback, claim review, or monitoring receives the finding.
Maintain the record
Owners, sources, conflicts, and review dates remain visible.
Acceptance checks
The asset is reviewed against the user task and current platform rules.
Entity match
The observed panel belongs to the intended entity.
Official facts
Approved identity records are current.
Source consistency
Core names, descriptions, dates, and relationships agree.
Conflict visibility
Disagreements are recorded rather than smoothed over.
Product distinction
Knowledge panels and Business Profiles are not conflated.
Expectation
Automatic generation and limited publisher control are explicit.
Failure patterns
MIRENA blocks shortcuts that create weak content or false search expectations.
Panel button myth
One markup change is presented as a panel trigger.
Entity collision
Two similar entities are merged.
Unsupported correction
A preferred fact is published without strong evidence.
No maintenance
The panel is observed once with no owner or review date.
Reference handoff
Use the signal to choose an operational workflow.
The informational intent does not benefit from a standalone prompt. MIRENA consumes the observation through the related planning, writing, formatting, entity, or audit workflow.
Reference intent
No standalone prompt is needed for the reference asset.
The job is to explain the search presentation accurately, record what can be observed, and send actual production or audit work into an operational MIRENA workflow.
MIRENA handoff
The result leaves with evidence, ownership, blockers, and a next route.
Reference definition
MIRENA records the source, confidence, owner, blocker, approval state, and next route.
Panel observation record
MIRENA records the source, confidence, owner, blocker, approval state, and next route.
Identity and conflict notes
MIRENA records the source, confidence, owner, blocker, approval state, and next route.
Publisher control boundary
MIRENA records the source, confidence, owner, blocker, approval state, and next route.
Route to support content, feedback, or monitoring
MIRENA records the source, confidence, owner, blocker, approval state, and next route.
Current platform sources
Official documentation sets the search presentation boundary.
MIRENA treats platform documentation as current evidence. The visible content should still help the reader when no enhanced search presentation appears.
Google knowledge panel help
MIRENA uses the current documentation as the platform boundary for the workflow.
Read the official sourceQuestions
Knowledge Panels questions.
Who creates knowledge panels?
Google states that knowledge panels are generated automatically from information across the web.
Can an entity suggest changes?
Verified entities can provide feedback and suggest edits, while other users can use the panel feedback route.
Is a Business Profile a knowledge panel?
No. They can look similar, but Business Profiles are specific to businesses that serve customers at a location or service area.
Which MIRENA workflow acts on the signal?
Use Knowledge Panel Support Content for identity, sources, conflicts, asset roles, links, and maintenance.
Next route
Use the reference to choose an operational MIRENA workflow.
Record the current search observation, keep the no control boundary visible, and send the finding into the relevant planning, writing, formatting, entity, or audit route.
Founder access is €20 per 30 days excluding VAT for one seat and one active MIRENA instance. OpenAI account rules and usage limits remain separate.