Result set baseline · Information Gain

SERP consensus mapping shows where the result set lines up before MIRENA chooses the page opening.

MIRENA charts repeated definitions, heading order, explanation angles, entities, comparisons, examples, proof, questions, formats, and next steps. The map protects required baseline coverage while exposing crowded patterns, weak consensus, shared omissions, and useful openings.

Method by Kevin Maguire

Understand the distinction See how MIRENA runs it

6 consensus states6 MIRENA stages8 mapping dimensions6 production actions

Source setRelevant result pagesPages that define the visible pattern for the target query

ConsensusWhat repeats and how stronglyDefinitions, order, entities, examples, formats, and next steps

Open spaceWeak, buried, missing, or divergent patternsThe evidence for information gain

OutputA page decision mapKeep, compress, avoid, strengthen, change format, or route

Definition and research boundary

SERP consensus mapping creates the baseline for information gain without turning the result set into an outline.

The map records what the field expects, what it overuses, what it handles weakly, and where the current query produces mixed or incomplete result patterns.

Result set relevance

The source pages must serve the same query and page job

MIRENA filters out irrelevant page types, mixed intent results, and business competitors that do not shape the visible answer pattern.

Consensus strength

Frequency is not the same as usefulness

MIRENA records how often a pattern appears and whether it is strong, weak, shallow, buried, or misleading.

MIRENA rule

The map must become page decisions

Every repeated or missing pattern receives a keep, compress, avoid, strengthen, format, route, or review instruction.

Research boundary: Google’s public guidance emphasizes helpful, reliable, people focused, unique, and valuable content. Search intent and competitor analysis sources can help select relevant result pages, but MIRENA uses the result set as evidence to understand the baseline rather than a structure to copy.

Google helpful content guidance Google AI search guidance Ahrefs search intent guidance Surfer competitor analysis guidance

MIRENA internal workflow

MIRENA turns the visible result set into a six stage consensus and decision map.

The workflow prevents accidental copying, off topic differentiation, mixed intent source sets, and research notes that never change the brief.

Confirm query and intent

MIRENA fixes the query class, audience, page type, user task, source context, protected pages, and review boundary.

Select the relevant result set

MIRENA keeps the pages that define the visible answer pattern and marks mixed intent or irrelevant results.

Extract repeated elements

MIRENA records openings, heading order, explanation angles, entities, comparisons, examples, proof, questions, formats, and next actions.

Group the consensus layer

Repeated elements are clustered into essential baseline, crowded consensus, weak consensus, buried consensus, shared omission, and divergence.

Rate strength and open space

MIRENA records frequency, quality, depth, placement, missing support, reader value, and the opportunity created by each pattern.

Create the page decision map

The findings become keep, compress, avoid, strengthen, change format, route, page planning, review, or hold instructions.

Six consensus states

The repeated pattern can be required, crowded, weak, buried, missing, or unstable.

Essential baseline

Coverage the query and page type still need for clarity and completion.

Crowded consensus

A repeated angle, order, example, or format that appears across the result set and adds little differentiation.

Weak consensus

A commonly included point the field explains poorly, shallowly, or without enough support.

Buried consensus

A useful answer or distinction appears repeatedly but too late or in the wrong format.

Shared omission

Several relevant pages skip the same answer, attribute, relationship, proof block, decision, or next route.

Divergent result set

The leading pages serve different intents, formats, audiences, or page jobs and require a clearer intent decision.

Eight mapping dimensions

MIRENA maps the result set from opening answer to next action.

Opening definition or answer

What appears first and how directly the query is resolved.

Heading and section order

The repeated sequence used to develop the topic.

Explanation angle

The dominant frame, promise, perspective, or user level.

Entities and attributes

The main entities, supporting concepts, properties, and relationships the field repeats or misses.

Comparison logic

The criteria, tradeoffs, alternatives, and recommendation frames used across the result set.

Examples and proof

The scenarios, claims, evidence, screenshots, sources, and trust support.

Questions and formats

The repeated FAQ, list, table, process, answer block, or component pattern.

Next step and route

The conclusion, call to action, internal path, support route, or decision the field provides.

Six map fields

A useful consensus map records enough context to support a real page decision.

Common element

The repeated topic, answer, entity, example, component, or route.

Frequency

How many relevant result pages use the element.

Strength

Whether the element is clear, weak, shallow, buried, unsupported, or strong.

Gap note

What the result set still leaves thin, missing, confused, or hard to use.

Page decision

Keep, compress, avoid, strengthen, add, change format, route, or review.

Owner and next workflow

The section, page, writer, editor, map route, link route, or hold state responsible for the action.

Examples

The useful opening becomes clear when the weak pattern and production route are shown together.

Asset type Process query

Consensus pattern

The result set repeats a broad definition and generic step lists.

MIRENA decision

Keep the definition, then add gates, owners, evidence needs, failure points, and the next stage handoff.

Asset type Comparison query

Consensus pattern

The pages use the same feature table, pros, cons, and broad recommendation.

MIRENA decision

Keep the core criteria, then add user fit, workflow fit, limitations, switching conditions, evidence quality, and a decision rule.

Asset type Definition query

Consensus pattern

The answer appears after broad setup and uses vague language.

MIRENA decision

Give the working definition first, then explain the boundary, example, related concepts, and next route.

Asset type Older ranking page

Consensus pattern

The asset follows the field’s intro, order, examples, and conclusion.

Main job

Reviews the finished asset across seven useful difference categories.

Relationship

Checks whether the brief and draft retained the right baseline and opening.

Ownership and production decisions

MIRENA converts consensus into page actions rather than a copied outline.

Keep the baseline

Retain essential coverage the query and page type still require.

Compress the crowded pattern

Shorten repeated setup, definitions, examples, questions, or broad claims.

Avoid the repeated structure

Change the order, answer shape, example logic, or component sequence when it adds no value.

Strengthen the weak consensus

Add missing depth, attributes, relationships, proof, comparison, decision support, or continuation.

Common mistakes

Weak reviews expand the notes but fail to improve the page or workflow.

Copying the result set

Consensus mapping is observation. Reproducing the outline defeats the purpose.

Using irrelevant source pages

Mixed intent and mismatched page types create a false baseline.

Treating frequency as quality

A repeated element can still be weak, shallow, buried, or unsupported.

Removing required consensus

The reader still needs the baseline even when competitors also cover it.

Ignoring shared omissions

The strongest opening may sit inside the point every relevant page skips.

Stopping at the worksheet

The map is incomplete until each pattern has a page action, owner, and next workflow.

Every accepted, held, rejected, blocked, or review needed finding receives an owner and next workflow.

Review the route

Review SERP consensus Review novel subtopics Review query paths Review the scorecard method

Questions

SERP Consensus Mapping for SEO questions.

What is SERP consensus mapping?

It is the process of charting what the current result set repeats, where it aligns, where it diverges, and where it leaves gaps.

Is consensus mapping the same as copying the SERP?

No. It is an observation layer that protects required baseline coverage and exposes crowded, weak, buried, missing, or unstable patterns.

How does MIRENA choose the result pages?

MIRENA checks query intent, page type, audience, answer shape, and relevance before a source enters the consensus set.

Does every repeated element belong on the new asset?

No. Some are essential baseline. Others should be compressed, avoided, strengthened, reformatted, routed, or held.

Can consensus mapping improve an older page?

Yes. It can expose repeated intros, recycled section order, weak support, missing comparisons, thin entity coverage, and unclear next steps.

What does MIRENA return?

MIRENA can return the source record, consensus layer, weak consensus map, shared omissions, brief decisions, and final handoff.

Next route

Give MIRENA the query, source context, current asset, and relevant result pages. It returns the consensus layer, open space, page decisions, and handoff.

Use the Information Gain prompt library for consensus, redundancy, overlap, novel subtopics, query paths, brief decisions, scoring, and final handoff.

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.

Open MIRENA Browse Information Gain prompts