A source context template is a structured input document that tells MIRENA what the site is, who it serves, what it offers, which entities are important, which topics are excluded, and what workflow output is needed.

Use it before generating topical maps, entity maps, content briefs, rewrites, information gain audits, internal link maps, SERP feature briefs, or semantic optimization outputs.

The goal is simple.

MIRENA should not have to guess the site goal, audience, offer, entities, boundaries, or next output.

A strong source context gives the workflow a controlled starting point.

What Is a Source Context Template?

A source context template is a structured input document for SEO workflows.

It defines the site, audience, offer, entities, exclusions, existing pages, internal links, and requested output before MIRENA creates maps, briefs, rewrites, audits, or optimization recommendations.

Source context works as the input control layer for MIRENA.

It helps answer important setup questions:

• What is the site about?
• Who is the audience?
• What does the site offer?
• Which entities should be prioritized?
• Which topics are allowed?
• Which topics should be excluded?
• Which pages already exist?
• Which workflow output is needed?
• Which pages should receive internal link support?
• Which commercial route should the output support?

A source context template is not a generic brand strategy document.

It is a practical SEO input file that prepares MIRENA to generate stronger downstream outputs.

If you are preparing a project for the first time, the MIRENA input documentation should be used alongside this template so the workflow starts with clear input signals.

Why MIRENA Needs Source Context Before Generating Outputs

Weak input creates weak SEO output.

A keyword without business context can produce a generic brief.

A sitemap without a conversion goal can produce shallow map decisions.

A draft without page purpose can produce cleaner wording while leaving weak structure in place.

A topical map request with no boundaries can drift into content the site should never publish.

MIRENA needs source context because SEO workflows depend on more than the target keyword.

The system needs to understand:

• the site goal
• the audience
• the offer
• the business model
• the allowed topic areas
• the excluded topic areas
• the existing URLs
• the main entities
• the commercial route
• the requested workflow output

For example, source context should be prepared before using the topical map generator because a topical map needs scope, page roles, entities, and exclusions before it can become a useful site plan.

Source context also improves the content brief generator because briefs need audience, page purpose, entity targets, internal links, and conversion direction before writers start drafting.

Without source context, the workflow may still produce text.

With source context, the workflow can produce controlled SEO outputs that fit the site.

What the Source Context Template Includes

The template groups the information MIRENA needs before creating SEO outputs.

It should include:

• site summary
• product or service summary
• audience details
• geography and language
• business goal
• primary and supporting entities
• excluded topics
• existing page inventory
• competitor references
• internal link targets
• proof assets
• brand voice notes
• workflow goal
• requested output type

Each section has a role.

The site summary defines the project.

The offer summary explains what is being sold or promoted.

The audience fields shape vocabulary, depth, and page examples.

The entity fields guide semantic structure.

The exclusions protect topical focus.

The page inventory prevents duplicate work.

The internal link fields help MIRENA connect new outputs to existing pages.

The workflow goal tells MIRENA what to produce.

That final field is important because the same source context can support different outputs. It can become a topical map, entity map, content brief, rewrite brief, information gain audit, internal link map, SERP feature brief, or semantic optimization report.

How to Fill Out a Source Context Template

The source context should be specific enough to guide the workflow without becoming a long brand document.

Use direct, practical detail.

Step 1: Define the Site and Offer

Start with the site name, domain, business type, and primary offer.

MIRENA needs to know what the site does before it can map, brief, rewrite, or audit content.

Weak input:

SEO website

Better input:

Semantec SEO is a semantic SEO workflow site built around MIRENA, an AI SEO system for topical maps, content briefs, rewrites, entity maps, internal link maps, SERP feature briefs, and semantic optimization.

Step 2: Name the Primary Audience

Define who the site serves.

Avoid vague audience labels like “business owners” or “marketers” if the site serves a narrower group.

Better audience detail might include:

• SEO consultants
• agencies
• in-house SEO teams
• founders
• content strategists
• editorial leads
• SaaS teams
• publishers

Audience clarity affects language, examples, depth, and CTA direction.

Step 3: Add Region and Language

Region and language help MIRENA control localization, spelling, phrasing, and regional modifiers.

For example:

Region: United States
Language: English

or:

Region: Ireland and United Kingdom
Language: English

This becomes more important for local service pages, ecommerce categories, and regional content plans.

Step 4: List Primary and Supporting Entities

Entities help MIRENA understand meaning.

A source context for Semantec SEO might include:

• MIRENA
• semantic SEO
• topical maps
• content briefs
• entity SEO
• information gain
• internal linking
• SERP features
• SEO rewrites
• schema
• source context

Those entities help MIRENA build stronger maps, briefs, and optimization outputs.

The entity map generator becomes more accurate when source context already separates important entities from low-priority concepts.

Step 5: Add Excluded Topics

Exclusions are just as important as inclusions.

They stop the workflow from expanding into topics that do not support the site.

For Semantec SEO, exclusions may include:

• generic digital marketing
• paid ads
• social media management
• email marketing
• generic AI productivity
• generic copywriting
• unrelated business software
• beginner blogging advice

Exclusions protect topical focus.

They also reduce irrelevant entity expansion.

Step 6: Add Existing URLs

Existing pages are part of source context.

MIRENA should know which pages already exist before recommending new ones.

Include:

• hub pages
• commercial pages
• docs pages
• proof pages
• support pages
• comparison pages
• pages to protect
• pages to rewrite
• pages to merge

This helps avoid duplicate pages and weak internal link routing.

Step 7: Add Internal Link Targets

Source context should include pages that need support.

For example:

• pricing page
• product page
• main use case pages
• core hubs
• templates
• proof pages
• docs pages

This helps the internal link map generator build routes from context instead of treating links as a late cleanup task.

Step 8: Choose the MIRENA Workflow Output

State the requested output clearly.

Choose one primary workflow goal first:

• generate a topical map
• generate an entity map
• generate a content brief
• generate a rewrite brief
• run an information gain audit
• create an internal link map
• create a SERP feature brief
• optimize semantic content

The workflow goal changes how MIRENA uses the same source context.

A topical map request needs more emphasis on clusters and page roles.

A rewrite request needs more emphasis on existing pages and repair priorities.

A SERP feature brief needs more emphasis on query intent, answer formats, and page structure.

Step 9: Add Proof or Examples

Proof assets help MIRENA create stronger commercial and trust sections.

Include:

• examples
• case notes
• screenshots
• before and after pages
• testimonials
• internal data
• customer objections
• product notes

This helps outputs move beyond generic SEO recommendations.

Step 10: Review for Scope Drift

Before using the source context, remove anything that does not support the workflow.

The document should guide MIRENA, not distract it.

Ask:

• Does this context define the site clearly?
• Does it identify the audience?
• Does it explain the offer?
• Does it include entities?
• Does it include exclusions?
• Does it include existing pages?
• Does it define the workflow output?
• Does it point toward the commercial route?

A concise, specific source context is better than a long vague one.

Site, Audience, Offer, and Region Fields

These fields tell MIRENA who the site serves and what the workflow should support.

Use this section to define the business context.

Site name:
Domain:
Primary offer:
Secondary offer:
Audience:
Audience skill level:
Region:
Language:
Commercial goal:
Primary conversion path:

Here is what each field does.

Site name tells MIRENA which brand or project the output belongs to.

Domain helps connect the context to page inventory, internal links, and URL planning.

Primary offer defines the main product, service, or workflow being promoted.

Secondary offer helps identify supporting services, templates, docs, or use cases.

Audience shapes vocabulary, examples, and assumptions.

Audience skill level helps control technical depth.

Region affects local modifiers, examples, compliance references, and market language.

Language controls spelling, terminology, and phrasing.

Commercial goal helps MIRENA route pages toward the right outcome.

Primary conversion path tells the workflow which destination should receive support.

For example, if the commercial path is pricing, then informational pages should eventually route users toward MIRENA pricing through natural contextual links.

Entity, Topic, and Exclusion Fields

These fields protect semantic focus.

They tell MIRENA what to include, what to prioritize, and what to avoid.

Primary entities:
Secondary entities:
Supporting concepts:
Entity exclusions:
Allowed topic areas:
Excluded topic areas:
Topics that need caution:
Competitor entities:
Brand entities:

Primary entities are the concepts the site needs to own.

Secondary entities support the main topics.

Supporting concepts add depth and explain adjacent ideas.

Entity exclusions block irrelevant concepts.

Allowed topic areas define safe expansion zones.

Excluded topic areas prevent drift.

Topics that need caution mark ideas that may be relevant only in limited contexts.

Competitor entities help comparison pages and positioning.

Brand entities reinforce product, author, company, and offer clarity.

These fields help MIRENA create more accurate entity maps, briefs, rewrites, and internal link routes.

For example, entity mapping from source context becomes stronger when the source context already states which entities belong in the site and which should be excluded.

Page Inventory and Internal Link Fields

Existing URLs belong in source context.

MIRENA needs to know what already exists before it recommends new pages, rewrites, briefs, or internal link routes.

Use this section:

Existing URLs:
Important hub pages:
Commercial pages:
Docs pages:
Proof pages:
Pages to protect:
Pages to merge:
Pages to rewrite:
Internal link targets:
Pages needing support:

Existing URLs give MIRENA the current site structure.

Important hub pages show which pages organize major clusters.

Commercial pages show where qualified users should go next.

Docs pages support product education.

Proof pages support trust.

Pages to protect should not be merged or replaced without review.

Pages to merge may overlap with nearby pages.

Pages to rewrite need repair.

Internal link targets show destination URLs that need support.

Pages needing support highlight weak or isolated pages.

These fields improve the internal link map from source context because link routes can be planned from the page inventory instead of guessed later.

They also improve rewrites because the SEO rewrite generator can use source context to understand which pages should be kept, repaired, merged, or routed toward a different destination.

Workflow Goal Fields

The same source context can support many workflows.

The requested output tells MIRENA what to produce.

Use this section:

Requested MIRENA output:
Primary workflow goal:
Secondary workflow goal:
Publishing priority:
Review requirements:
Known constraints:

Choose one primary requested output first.

The source context can be used to generate:

• a topical map
• an entity map
• a content brief
• an SEO rewrite
• an information gain audit
• an internal link map
• a SERP feature brief
• a semantic optimization report

The workflow goal controls the output structure.

For example, if the requested output is a topical map, MIRENA should focus on cluster structure, page roles, topic boundaries, and publishing order.

If the requested output is a content brief, MIRENA should focus on page purpose, search intent, entities, section structure, SERP features, internal links, and writer instructions.

If the requested output is a rewrite, MIRENA should focus on page repair, semantic drift, structure, internal links, and conversion path.

How Source Context Improves MIRENA Outputs

Source context improves the decisions MIRENA makes downstream.

It does not just add background detail.

It changes output quality.

It Improves Topical Map Scope

MIRENA can separate allowed topic areas from excluded ones before building a page plan.

This helps prevent oversized maps, weak clusters, and irrelevant pages.

It Improves Entity Selection

The system can prioritize brand, product, topic, audience, and workflow entities instead of pulling in unrelated concepts.

That helps entity maps, content briefs, rewrites, and semantic optimization outputs stay focused.

It Improves Page Role Decisions

Source context helps MIRENA decide which pages should act as hubs, spokes, support pages, bridge pages, proof pages, docs pages, or commercial pages.

This is important for topical maps and internal link plans.

It Improves Content Brief Quality

Briefs become stronger when page purpose, audience, entities, internal links, and conversion paths are defined before drafting.

The content brief generator can use source context to create clearer writer instructions instead of generic heading lists.

It Improves Rewrite Direction

Rewrites become more useful when MIRENA knows what the page should keep, remove, strengthen, merge, or route toward.

The SEO rewrite generator can use source context to repair pages according to the current site structure instead of only editing the old copy.

It Improves Information Gain Findings

An information gain audit becomes sharper when MIRENA knows the site’s boundaries, proof assets, audience, and workflow target.

The information gain audit can then focus on useful differentiation instead of unrelated novelty.

It Improves SERP Feature Recommendations

SERP feature recommendations become stronger when MIRENA knows the page purpose and workflow goal.

The SERP feature brief generator can then recommend paragraph snippets, lists, FAQs, tables, and answer blocks that fit the page.

It Improves Semantic Optimization

Semantic optimization becomes more accurate when MIRENA knows which entities, relationships, and exclusions matter.

The semantic content optimizer can use source context to improve meaning, entity salience, internal links, and information gain before publishing or during refreshes.

After source context is prepared, users can compare deliverables inside the MIRENA output types documentation.

Copyable Source Context Template

Copy this template and fill in the fields before generating a MIRENA output.

SITE CONTEXT

Site name:
Domain:
Business type:
Primary offer:
Secondary offers:
Main audience:
Secondary audiences:
Audience skill level:
Region:
Language:
Primary conversion goal:
Secondary conversion goal:


PRODUCT OR SERVICE CONTEXT

Product or service name:
What it does:
Who it helps:
Main use cases:
Key differentiators:
Pricing or commercial model:
Proof assets:
Customer objections:


ENTITY CONTEXT

Primary entities:
Secondary entities:
Supporting concepts:
Brand entities:
Competitor entities:
Entity exclusions:
Topics to avoid:
Topics to include:
Topics requiring caution:


CONTENT CONTEXT

Existing hub pages:
Existing support pages:
Existing commercial pages:
Existing docs pages:
Existing proof pages:
Pages to protect:
Pages to rewrite:
Pages to merge:
Pages to noindex:
Known content gaps:


INTERNAL LINK CONTEXT

Important destination URLs:
Pages needing internal links:
Commercial pages needing support:
Hub pages:
Bridge pages:
Support pages:
Preferred anchor direction:
Anchors to avoid:


SERP AND FORMAT CONTEXT

Target search intent:
SERP features to target:
FAQ needs:
PAA needs:
Table needs:
Comparison needs:
How-to needs:
Schema cues:


WORKFLOW GOAL

Requested MIRENA output:
Topical map / entity map / content brief / rewrite brief / information gain audit / internal link map / SERP feature brief / semantic optimization

Primary workflow goal:
Secondary workflow goal:
Publishing priority:
Review requirements:
Known constraints:

Source Context Template Example

This partial example shows how the template can be filled for a semantic SEO software site.

Site name:
Semantec SEO

Domain:
https://semantecseo.com/

Primary offer:
MIRENA, an AI SEO workflow system for topical maps, content briefs, rewrites, entity maps, internal links, SERP feature briefs, and semantic optimization.

Audience:
SEO consultants, agencies, founders, in-house SEO teams, and content strategists.

Audience skill level:
Intermediate to advanced SEO operators.

Region:
United States, United Kingdom, Ireland, and English-language markets.

Language:
English.

Primary conversion goal:
Move users from educational pages into MIRENA use cases and pricing.

Core entities:
MIRENA, semantic SEO, topical maps, content briefs, entity SEO, information gain, internal linking, SERP features, SEO rewrites, schema, source context.

Excluded topics:
Generic digital marketing, social media management, paid ads, email marketing, generic AI productivity, generic copywriting.

Existing commercial pages:
MIRENA Pricing

https://semantecseo.com/use-cases/topical-map-generator/
Content Brief Generator for SEO

SEO Rewrite Generator


Workflow goal:
Generate a processed topical map and prioritize new acquisition pages.

Requested MIRENA output:
Topical map with page roles, priority order, internal link direction, and content brief targets.

This example gives MIRENA enough context to understand the offer, audience, entities, exclusions, URLs, and requested output.

It is specific without becoming too long.

Source Context Mistakes to Avoid

Poor source context creates generic or misaligned output.

The most common mistakes are missing boundaries, vague goals, and incomplete page inventory.

Avoid these mistakes:

• using vague audience descriptions
• leaving out the offer
• giving only keywords
• failing to list exclusions
• ignoring existing pages
• mixing several business models
• skipping conversion goals
• omitting region or language
• requesting output with no workflow goal
• adding irrelevant competitor topics
• listing entities with no priorities
• hiding important commercial pages
• failing to name proof assets
• using broad terms that create drift

A weak source context makes MIRENA guess.

A strong source context controls the workflow.

Prepare Source Context, Then Run It Through MIRENA

Use the template to define the site, audience, offer, entities, exclusions, page inventory, internal links, and workflow goal before generating MIRENA outputs.

That preparation improves maps, briefs, rewrites, audits, internal link plans, SERP feature briefs, and semantic optimization reports.

If you are ready to use source context inside MIRENA, review MIRENA pricing. If you want to start with site planning, turn source context into a processed topical map or review the MIRENA output types before choosing a workflow.

FAQs About Source Context Templates

What is a source context template?

A source context template is a structured input document that defines the site, audience, offer, entities, exclusions, existing pages, and requested SEO workflow output.

Why does MIRENA need source context?

MIRENA uses source context to keep maps, briefs, rewrites, audits, internal links, and optimization outputs aligned with the site goal, audience, entities, and content boundaries.

What should source context include?

Source context should include site details, audience, offer, region, primary entities, excluded topics, existing URLs, internal link targets, proof assets, and the requested workflow output.

Can I use source context for topical maps?

Yes.

Source context helps MIRENA build topical maps with clearer scope, page roles, entity priorities, exclusions, and commercial routing.

Can I use source context for content briefs?

Yes.

Source context helps content briefs include stronger audience direction, page purpose, entity targets, internal links, SERP formats, and exclusions.

Can source context improve rewrites?

Yes.

Source context helps rewrites repair pages according to the current site goal, topical structure, internal link plan, entity priorities, and conversion path.

Should source context include existing URLs?

Yes.

Existing URLs help MIRENA avoid duplicate pages, identify rewrite needs, plan internal links, and understand the current site structure.

Should source context include excluded topics?

Yes.

Excluded topics help prevent topical drift, irrelevant entity expansion, and outputs that move outside the site’s intended scope.

How long should source context be?

Source context should be long enough to define the site, audience, offer, entities, exclusions, pages, and goal clearly.

A concise but specific document is better than a long vague one.

What happens after I fill out the source context template?

After source context is prepared, it can be used to generate topical maps, entity maps, content briefs, rewrite briefs, internal link maps, information gain audits, SERP feature briefs, or semantic optimization reports.