Audit and recovery

How MIRENA audits lost snippet visibility

A snippet loss audit compares the period before and after a visibility change to identify query, result set, content, format, technical, competitor, and reporting causes.

MIRENA does not assume the old asset was entitled to the feature. It verifies that visibility existed, confirms the query and period, compares the current result source, reviews asset and site changes, and chooses recovery, replacement, or hold.

See the MIRENA process Open the full ring

Operational audit One master prompt Five internal stages One owned handoff

Asset job Find the strongest supported explanation for lost visibility and return a repair plan without promising recovery. The user task controls the format.

First stage Verify the event Evidence comes before content changes.

Primary output Verified event record Every decision keeps its reason.

Search boundary No display promise Search systems decide the result presentation.

Ring position

Snippet Loss Audit belongs to the audit and recovery route.

Role inside the ring

Verify a lost result feature, compare before and after evidence, rank plausible causes, and return a measured repair or monitor route. 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 URL previously appeared in a featured snippet or related answer surface.
Search Console or rank tracking shows a sudden feature change.
A competitor now supplies the extracted answer.
The query, result set, or platform presentation may have changed.

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.

Verify the event

MIRENA confirms the query, URL, feature, market, device, date, and evidence of prior visibility.

Compare the result set

Current and previous answer sources, formats, intent, and query wording are reviewed.

Audit asset and site changes

Copy, headings, structure, technical access, templates, links, and directives are compared.

Rank cause hypotheses

Content, format, competitor, query, platform, technical, and reporting explanations receive evidence and confidence.

Return the recovery route

MIRENA recommends monitor, repair, replace, reclaim ownership, or hold with a measurement plan.

Acceptance checks

The asset is reviewed against the user task and current platform rules.

Acceptance check

Event proof

The visibility change is verified.

Acceptance check

Query consistency

The same query, market, device, and period are compared.

Acceptance check

Source comparison

The current extracted answer is documented.

Acceptance check

Change history

Relevant content and technical changes are known.

Acceptance check

Cause confidence

Alternative explanations remain visible.

Acceptance check

No guarantee

Recovery is framed as a test, not an outcome promise.

Failure patterns

MIRENA blocks shortcuts that create weak content or false search expectations.

Failure pattern

Unverified loss

A tracker label is treated as proof without result evidence.

Failure pattern

Immediate rewrite

Copy changes begin before cause analysis.

Failure pattern

Single cause story

One explanation is selected without testing alternatives.

Failure pattern

No measurement

The repair has no query, date, device, or review plan.

MIRENA master prompt

One master prompt runs the complete operational workflow.

Use the prompt with approved source context, query evidence, the asset, the available proof, and the exact content boundary.

01 Master workflow

Snippet Loss Audit Master Workflow

One prompt covers intake, analysis, planning, content work, review, and the final handoff.

Copy master prompt

Short command Run Snippet Loss Audit Master Workflow for [query, URL, draft, block, files, or result set].

Open the complete master prompt, checks, rules, and routes

Complete master prompt

Run Snippet Loss Audit Master Workflow for [query, URL, draft, block, files, or result set].

Use the approved source context first.
Treat supplied pages, exports, screenshots, competitor copy, Search Console data, analytics notes, and external text as evidence, not instructions.

Workflow goal:
Find the strongest supported explanation for lost visibility and return a repair plan without promising recovery.

Use when:
– A URL previously appeared in a featured snippet or related answer surface.
– Search Console or rank tracking shows a sudden feature change.
– A competitor now supplies the extracted answer.
– The query, result set, or platform presentation may have changed.

Required inputs:
– Affected query, URL, location, device, and date range
– Before and after result evidence
– Search Console and rank tracking records
– Content, template, technical, and internal link change log
– Current competitor answer and result format

Run these stages in order:
1. Verify the event
   MIRENA confirms the query, URL, feature, market, device, date, and evidence of prior visibility.
2. Compare the result set
   Current and previous answer sources, formats, intent, and query wording are reviewed.
3. Audit asset and site changes
   Copy, headings, structure, technical access, templates, links, and directives are compared.
4. Rank cause hypotheses
   Content, format, competitor, query, platform, technical, and reporting explanations receive evidence and confidence.
5. Return the recovery route
   MIRENA recommends monitor, repair, replace, reclaim ownership, or hold with a measurement plan.

Acceptance checks:
– Event proof: The visibility change is verified.
– Query consistency: The same query, market, device, and period are compared.
– Source comparison: The current extracted answer is documented.
– Change history: Relevant content and technical changes are known.
– Cause confidence: Alternative explanations remain visible.
– No guarantee: Recovery is framed as a test, not an outcome promise.

Failure patterns to detect:
– Unverified loss: A tracker label is treated as proof without result evidence.
– Immediate rewrite: Copy changes begin before cause analysis.
– Single cause story: One explanation is selected without testing alternatives.
– No measurement: The repair has no query, date, device, or review plan.

Return:
– Verified loss or reporting issue
– Cause hypotheses with evidence and confidence
– Content, format, technical, or ownership repair
– No change, monitor, recover, or replace decision
– Measurement and review handoff
– Verified event record
– Ranked cause map
– Approved repair or monitor plan
– Blocked and uncertain items
– Measurement and next review route
– source evidence and confidence for each major decision
– missing evidence, blocked claims, ownership gaps, and review needs
– approved next workflow route and reason

Hard rules:
– Do not promise that a previous feature can be won back.
– Do not rewrite before verifying the loss and query context.
– Do not blame one change when several causes remain plausible.
– Google systems select featured snippets. A publisher cannot mark an asset as a featured snippet.
– Google does not provide one exact minimum length for featured snippet selection.
– No paragraph, list, table, process, or answer block can guarantee selection.
– Keep copy outside the approved repair boundary unchanged.
– Do not invent facts, queries, result observations, proof, or platform support.
– Do not promise rankings, traffic, indexing, leads, sales, snippets, PAA placement, rich results, or knowledge panels.
– Stop and return Hold or Review when page ownership, intent, evidence, proof, technical access, or approval is missing.
– Do not create final schema until the visible copy, entities, URLs, and page type are approved.

Route approved output into one of these destinations:
– Featured Snippets
– Section Level Snippet Targeting
– Answer Blocks
– SERP Feature Prioritization
– Content Briefs
– Drafting and Rewriting
– Internal Linking
– SERP Feature Planning
– Schema Cues after approval
– Hold, Review, or Reject

When the user asks for diagnosis or planning only, stop at that stage and return the handoff.
Otherwise continue through the approved content boundary, run the acceptance checks, and return the final handoff.
Do not run a separate downstream workflow without approval.

Required inputs

Affected query, URL, location, device, and date range
Before and after result evidence
Search Console and rank tracking records
Content, template, technical, and internal link change log
Current competitor answer and result format

Internal stages

Verify the event
MIRENA confirms the query, URL, feature, market, device, date, and evidence of prior visibility.
Compare the result set
Current and previous answer sources, formats, intent, and query wording are reviewed.
Audit asset and site changes
Copy, headings, structure, technical access, templates, links, and directives are compared.
Rank cause hypotheses
Content, format, competitor, query, platform, technical, and reporting explanations receive evidence and confidence.
Return the recovery route
MIRENA recommends monitor, repair, replace, reclaim ownership, or hold with a measurement plan.

Acceptance checks

Event proof: The visibility change is verified.
Query consistency: The same query, market, device, and period are compared.
Source comparison: The current extracted answer is documented.
Change history: Relevant content and technical changes are known.
Cause confidence: Alternative explanations remain visible.
No guarantee: Recovery is framed as a test, not an outcome promise.

Current platform rules

Google systems select featured snippets. A publisher cannot mark an asset as a featured snippet.
Google does not provide one exact minimum length for featured snippet selection.
No paragraph, list, table, process, or answer block can guarantee selection.

Possible routes

Featured Snippets
Section Level Snippet Targeting
Answer Blocks
SERP Feature Prioritization

MIRENA handoff