MORIS MEDIA / PROTOCOL 05

Topics & Approved Section Breakdowns

Mandatory publication and execution protocol. The source instructions below retain their original wording, with line references to the supplied master prompt. All relevant requirements are binding; overlaps with other pages are intentional.

Execution instruction

Read all source requirements on this page and apply them to the approved topic, geographic level, workbook, and content fields. Never substitute a summary for a binding requirement. Consult the master execution overrides for precedence and the final validation protocol before export.

Binding source requirements: lines 8–28

0008 | 
0009 | 
0010 | 
0011 | 
0012 | 
0013 | 
0014 | Note:
0015 | Each geographic level must have its own independently developed section architecture.
0016 | •	Country-Centric: Use only the approved Country-Centric topics and their specifically developed Country-Centric section breakdowns.
0017 | •	State-Centric: Create independently researched State-Centric section breakdowns. Do not reuse, copy, adapt, or simply replace {country} with {State} in Country-Centric sections.
0018 | •	City-Centric: Create independently researched City-Centric section breakdowns. Do not reuse Country-Centric or State-Centric section breakdowns, and do not simply replace {country} or {State} with {city}.
0019 | Every topic at every geographic level must have 10 independently developed sections based on its own search intent, geographic context, audience problems, market conditions, service requirements, Moris Media positioning, keywords, evidence requirements, and backlink strategy.
0020 | Country sections must remain exclusive to Country-Centric articles. State sections must remain exclusive to State-Centric articles. City sections must remain exclusive to City-Centric articles.
0021 | Changing only the geographic variable, location name, ranking terminology, or topic wording does not constitute a unique section breakdown.
0022 | 
0023 | Approved Matrix
0024 | The following is the approved matrix that may be used during content writing on a section-by-section basis. Use only the matrix elements that are directly relevant to the specific topic, section responsibility, search intent, geographic context, audience requirement, problem, solution, and Moris Media positioning. Do not force, insert, or reference any matrix element that is irrelevant to the section.
0025 | Approved Matrix Placeholder:
0026 | {APPROVED_SECTION_WISE_MATRIX}
0027 | 
0028 | 

Binding source requirements: lines 29–33

0029 | MASTER EXECUTION OVERRIDES
0030 | •	The approved topic-wise section breakdown is controlling. If a section purpose has already been supplied, follow it exactly. Do not replace it with a generic section structure.
0031 | •	Across the 10 sections, vary search intent naturally: Sections 1–3 should normally support informational/problem-recognition intent; Sections 4–7 commercial/evaluation intent; Sections 8–10 transactional/vendor-selection and execution intent. This funnel treatment must never override an approved section responsibility.
0032 | •	Every article and every section must be independently researched, structured and written. Changing only a location, keyword, ranking term, statistic, example, heading or CTA does not create unique content.
0033 | •	Programmatic SEO may standardize the 62-column schema, HTML design system and validation workflow, but it must never spin body copy.

Binding source requirements: lines 623–670

0623 | 10-SECTION ARTICLE CONTENT & 850–900 WORD SECTION PROTOCOL
0624 | ARTICLE & SECTION UNDERSTANDING
0625 | Before writing any section, understand the complete:
0626 | {Topic} • Service • Target Audience • Search Intent • Target Location • Reader Problem • Commercial Intent • Local Market • Required Solution
0627 | Every article must contain exactly 10 independently written sections.
0628 | If a section breakdown has already been supplied, follow that breakdown exactly. The approved purpose of each section becomes the controlling instruction.
0629 | If no section breakdown has been supplied, analyse the {Topic} and create 10 distinct, non-overlapping sections based on genuine user search requirements.
0630 | Every section must have a unique:
0631 | Purpose • Search Intent • H1 • H2 • Opening • Research Angle • Local Context • Hook Lines • Keywords • Evidence • Examples • Brand Positioning • Backlinks • Conclusion
0632 | SEARCH INTENT VARIATION ACROSS THE 10 SECTIONS
0633 | The 10 sections must not target the same search intent.
0634 | The article should move naturally through the reader's decision process.
0635 | Sections 1–3: Informational / Problem Recognition
0636 | These sections should help readers understand:
0637 | The problem
0638 | Why the service matters
0639 | Local market relevance
0640 | Audience requirements
0641 | Industry conditions
0642 | Common challenges
0643 | What the service actually involves
0644 | The reader may still be researching rather than actively choosing a provider.
0645 | Sections 4–7: Commercial / Evaluation of Options
0646 | These sections should help readers compare:
0647 | Service approaches
0648 | Strategy
0649 | Execution
0650 | Deliverables
0651 | Capabilities
0652 | Experience
0653 | Evidence
0654 | Approved achievements
0655 | Risks
0656 | Quality standards
0657 | What separates stronger providers from weaker options
0658 | Sections 8–10: Transactional / Vendor Selection & Execution
0659 | These sections should help readers evaluate:
0660 | Provider suitability
0661 | Measurement
0662 | Engagement requirements
0663 | Implementation
0664 | Commercial considerations
0665 | Selection criteria
0666 | Execution readiness
0667 | Evidence to request
0668 | Final decision factors
0669 | The exact section responsibilities must still follow any previously approved section breakdown.
0670 | The funnel structure controls search intent, not the subject of an already approved section.

Binding source requirements: lines 734–747

0734 | SECTION BREAKDOWN GOVERNANCE
0735 | Where an approved breakdown exists, follow it exactly.
0736 | If the approved instruction says:
0737 | Section 1: Market Introduction and Search Intent
0738 | Section 1 must remain focused on market introduction and search intent.
0739 | If it says:
0740 | Section 4: Strategy and Execution
0741 | Section 4 must remain focused on strategy and execution.
0742 | If it says:
0743 | Section 8: Search Visibility and Long-Term Discovery
0744 | Section 8 must remain focused on that responsibility.
0745 | Do not substitute generic section responsibilities simply to maintain the funnel.
0746 | Instead:
0747 | Approved Section Responsibility + Appropriate Funnel Intent = Final Section Direction

Expanded global production requirements

Universal geographic scope and application

This protocol applies to approved service articles for any country, state, province, territory, region, city, or comparable administrative area. Examples involving India are illustrative only. No Indian city, law, currency, language, ranking claim, media market, or business environment may be presumed to apply to other countries. Research each location independently and use its actual administrative terminology.

Input geographic tokens are {country}, {State}, {city}, and {year}. When geographic context needs 2 levels, use {State}, {country} or {city}, {country} or {city}, {State}, according to the page's approved scope. Never put {city} and {State} on the same line unless the approved assignment explicitly requires that pair; when it does, do not add {country} to that line. Never stack all 3 geographic levels in a heading. In location-first headings prefer only the primary geographic level. Country-level pages use {country} alone. State-level pages may use {State} with {country} for essential clarification. City-level pages may use {city} with either {State} or {country}, but not both.

In metadata fields Meta Title, Meta Description, and Meta Keywords, no curly-brace variable is permitted, including {country}, {State}, {city}, {Location}, {Agency_type}, or {year}. Populate those fields with researched literal location names and approved facts before export. The other article fields may contain permitted template variables only when the assignment explicitly requests template output; for publication-ready geographic rows, replace geographic placeholders with actual target values. Preserve {year} literally wherever approved outside metadata.

Digits, numeric claims and measurement

Write numeric quantities as digits, not spelled-out number words, in publication output: use 10 sections, 62 columns, 850 words, 5 examples, 12 years, and 4.5 rating. Retain natural fixed names and quoted official titles when spelling is part of a verified proper noun. Numeric evidence must be traceable, scoped to the correct geography and date, and supported by a credible source. Never turn an estimate into a verified result. Keep units, currencies, dates and percentages clear.

Topic and section approval check

Load the approved topic list and the 10 named section responsibilities for the selected geographic level. Treat blank topic placeholders as missing input, not permission to invent an approved list. Country, state and city architectures must be independently planned. Keep each section aligned with its exact approved subject, not a generic content funnel. Before drafting, record the topic, target location, target level, section responsibility and evidence needs for each of the 10 sections.