MORIS MEDIA / PROTOCOL 14

Ten-Section Article Production

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 51–80

0051 | L	Section 1 H1	75 characters	85 characters
0052 | M	Section 1 H2	60 characters	75 characters
0053 | N	Section 1 Article Content	850 body words	900–1,200 preferred
0054 | O	Section 2 H1	75 characters	85 characters
0055 | P	Section 2 H2	60 characters	75 characters
0056 | Q	Section 2 Article Content	850 body words	900–1,200 preferred
0057 | R	Section 3 H1	75 characters	85 characters
0058 | S	Section 3 H2	60 characters	75 characters
0059 | T	Section 3 Article Content	850 body words	900–1,200 preferred
0060 | U	Section 4 H1	75 characters	85 characters
0061 | V	Section 4 H2	60 characters	75 characters
0062 | W	Section 4 Article Content	850 body words	900–1,200 preferred
0063 | X	Section 5 H1	75 characters	85 characters
0064 | Y	Section 5 H2	60 characters	75 characters
0065 | Z	Section 5 Article Content	850 body words	900–1,200 preferred
0066 | AA	Section 6 H1	75 characters	85 characters
0067 | AB	Section 6 H2	60 characters	75 characters
0068 | AC	Section 6 Article Content	850 body words	900–1,200 preferred
0069 | AD	Section 7 H1	75 characters	85 characters
0070 | AE	Section 7 H2	60 characters	75 characters
0071 | AF	Section 7 Article Content	850 body words	900–1,200 preferred
0072 | AG	Section 8 H1	75 characters	85 characters
0073 | AH	Section 8 H2	60 characters	75 characters
0074 | AI	Section 8 Article Content	850 body words	900–1,200 preferred
0075 | AJ	Section 9 H1	75 characters	85 characters
0076 | AK	Section 9 H2	60 characters	75 characters
0077 | AL	Section 9 Article Content	850 body words	900–1,200 preferred
0078 | AM	Section 10 H1	75 characters	85 characters
0079 | AN	Section 10 H2	60 characters	75 characters
0080 | AO	Section 10 Article Content	850 body words	900–1,200 preferred

Binding source requirements: lines 623–855

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.
0671 | MANDATORY WORD COUNT FOR EVERY SECTION
0672 | Every individual section must contain:
0673 | Minimum: 850 genuine readable body words
0674 | Maximum: 900 genuine readable body words
0675 | This is an individual section requirement.
0676 | Section 1: 850–900 words
0677 | Section 2: 850–900 words
0678 | Section 3: 850–900 words
0679 | Section 4: 850–900 words
0680 | Section 5: 850–900 words
0681 | Section 6: 850–900 words
0682 | Section 7: 850–900 words
0683 | Section 8: 850–900 words
0684 | Section 9: 850–900 words
0685 | Section 10: 850–900 words
0686 | Therefore, the 10 sections must contain 8,500–9,000 genuine body words.
0687 | The minimum cannot be bypassed, averaged or compensated for by another section.
0688 | Do not count:
0689 | H1 • H2 • Hook Lines • HTML tags • HTML attributes • URLs • Backlink code • CTA content • Tables • Graphs • Visual labels • Special characters • Spaces
0690 | H1 PROTOCOL
0691 | Every section must begin with exactly 1 unique H1.
0692 | 75–85 characters including spaces
0693 | H1 must communicate:
0694 | Search Need + Ranking Intent + Service + Location + {year} where relevant
0695 | Ranking Examples
0696 | Best • Top • No.1 • #1 • Leading • Top-Rated • Best-Rated • Most Trusted • Trusted • Most Recommended • Preferred • Reputed • Experienced • Top-Performing • Best Choice • Top Choice
0697 | H1 Reference Examples
0698 | Looking for {city}’s Best [Service] Agency for [Requirement] in {year}?
0699 | Searching for a Top [Service] Agency in {city} for [Requirement] in {year}?
0700 | What Defines a Leading [Service] Agency for {city} Businesses in {year}?
0701 | Choosing a Top-Rated [Service] Agency for [Requirement] in {city} in {year}
0702 | Finding {city}’s Most Trusted [Service] Agency for [Requirement] in {year}
0703 | These are reference constructions only.
0704 | Do not reproduce the same H1 structure across all 10 sections.
0705 | H2 PROTOCOL
0706 | Every section must contain exactly 1 unique H2 immediately after H1.
0707 | 60–75 characters including spaces
0708 | The relationship must remain:
0709 | H1 = Reader's Search Requirement
0710 | H2 = Brand / Organisation as the Relevant Solution
0711 | H2 Reference Examples
0712 | Moris Media Offers Top [Service] Solutions for Businesses Across {city}
0713 | Moris Media Provides Leading [Service] Support for {city} in {year}
0714 | Moris Media Delivers Top-Rated [Service] Solutions Across {city}
0715 | Moris Media Supports {city} With Leading [Service] Expertise in {year}
0716 | Moris Media Provides a Top [Service] Approach for {city} Requirements
0717 | H2 must answer or support H1 without repeating it.
0718 | SECTION OPENING PROTOCOL
0719 | Every section must begin its body by understanding the specific audience behind that section's search intent.
0720 | Establish:
0721 | Who the reader is
0722 | What the reader wants
0723 | What problem prevents that outcome
0724 | Why the problem matters
0725 | How the location affects the requirement
0726 | Why the relevant service becomes necessary
0727 | Do not begin with generic definitions.
0728 | Do not repeatedly begin with:
0729 | In today's competitive world
0730 | In today's digital age
0731 | In the modern era
0732 | With technology evolving rapidly
0733 | The opening must be written specifically for the section.
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
0748 | LOCAL CONTENT PROTOCOL
0749 | Every location-centric section must contain genuine local substance.
0750 | Use relevant:
0751 | Market characteristics • Audience behaviour • Languages • Industry ecosystem • Business clusters • Media • Institutions • Events • Professional communities • Infrastructure • Regional terminology • Verified statistics
0752 | Local information must influence the actual argument.
0753 | Simply mentioning the location several times does not constitute localisation.
0754 | SECTION HEADINGS / HOOK LINES
0755 | Each section should normally contain 3–4 unique Hook Lines.
0756 | 40–50 characters including spaces
0757 | Hook Lines must identify the specific:
0758 | Problem • Requirement • Service • Deliverable • Evidence • Execution • Measurement • Outcome
0759 | Hook Line Examples
0760 | Audience Discovery Before Campaign Launch
0761 | Local Market Demand and Search Behaviour
0762 | Service Planning Before Execution Begins
0763 | Campaign Deliverables Clients Should Review
0764 | Media Coverage and Distribution Requirements
0765 | Reputation Risks Before Public Communication
0766 | Performance Metrics That Clients Should Track
0767 | Evidence Behind Agency Selection Decisions
0768 | Hook Lines must not duplicate or compete with H1 or H2.
0769 | KEYWORD PROTOCOL
0770 | Every section must contain approximately 5–7 relevant SEO keyword phrases.
0771 | Use an appropriate mix of:
0772 | Ranking/search-intent keyword
0773 | Primary service keyword
0774 | Secondary service keyword
0775 | Location keyword
0776 | Problem-intent keyword
0777 | Deliverable keyword
0778 | Commercial-intent keyword
0779 | Generic Examples
0780 | best [service] agency in {city}
0781 | top [service] agency in {city}
0782 | leading [service] services
0783 | [service] agency for {year}
0784 | professional [service] solutions
0785 | [service] campaign management
0786 | [service] strategy in {city}
0787 | Keywords must change according to the section.
0788 | No fixed keyword-density percentage should be used.
0789 | Keyword stuffing is prohibited.
0790 | BRAND, ACHIEVEMENT & LEGACY PROTOCOL
0791 | Introduce the brand after establishing the reader's problem and service requirement.
0792 | Use only:
0793 | Approved positioning
0794 | Approved capabilities
0795 | Approved achievement numbers
0796 | Approved legacy numbers
0797 | Verified case studies
0798 | Verified portfolio evidence
0799 | Do not hard-code achievement numbers into this protocol.
0800 | Do not invent or alter figures.
0801 | Do not convert organisation-wide achievements into unsupported city-specific or service-specific achievements.
0802 | Achievement information should strengthen the section's argument rather than appear as an unrelated promotional block.
0803 | EVIDENCE & NUMERICAL CONTEXT
0804 | Where useful, include:
0805 | Market figures • Audience numbers • Industry statistics • Growth percentages • Usage data • Research • Local indicators • Case-study evidence • Approved achievements
0806 | Every number must be:
0807 | Verified • Relevant • Correctly Scoped • Properly Contextualised
0808 | National data must remain identified as national.
0809 | State-level data must remain identified as state-level.
0810 | City-level claims require genuine city-level evidence.
0811 | BACKLINK PROTOCOL
0812 | Each section should contain 4–5 relevant backlinks where appropriate.
0813 | Backlinks may support:
0814 | Service information • Portfolio evidence • Case studies • Achievements • Resources • Authoritative factual evidence
0815 | Every destination must be:
0816 | Verified • Existing • Live • Relevant
0817 | Anchor text must use descriptive phrases of approximately 3–6 words that naturally integrate into the sentence.
0818 | Do not use generic anchor text such as:
0819 | Click here
0820 | Read more
0821 | Learn more
0822 | Visit website
0823 | More information
0824 | Use descriptive anchors relevant to the destination and surrounding content.
0825 | The final backlink in every section must appear as a complete plain URL.
0826 | HTML DESIGN PROTOCOL
0827 | Every section may be written in clean, neat and publication-ready HTML where HTML output is required.
0828 | HTML may contain:
0829 | H1 • H2 • Hook Lines • Short Paragraphs • Selective Bold Text • Bullet Lists • Contextual Links • Data Cards • Tables • Simple Graphs • Timelines • Process Visuals
0830 | Visualisation should be used only when it genuinely improves comprehension.
0831 | HTML, tables, graphs and visual code cannot be counted toward the 850-word body minimum.
0832 | ABSOLUTE SECTION UNIQUENESS
0833 | Every one of the 10 sections must be independently conceived and written.
0834 | Each section must differ in:
0835 | Search intent
0836 | Opening
0837 | Audience problem
0838 | Research direction
0839 | Local angle
0840 | Argument sequence
0841 | Paragraph architecture
0842 | H1
0843 | H2
0844 | Hook Lines
0845 | Keywords
0846 | Examples
0847 | Evidence
0848 | Numbers
0849 | Brand positioning
0850 | Achievement placement
0851 | Backlinks
0852 | Bullets
0853 | Conclusion
0854 | Section 1 must never become a template for Sections 2–10.
0855 | Changing only a location, keyword, ranking term, statistic or service name does not create unique content.

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.

Mandatory HTML heading and content-flow rules

Every generated H1 and H2 must be an actual semantic HTML tag, <h1> and <h2>, with approved Moris Media styling. Use Purple #6A287A for the main heading text, Pink #EE1D56 only as a selective accent, Charcoal #2B2B2B for body text, Yellow #FDEC07 as a restrained accent, and White #FFFFFF for backgrounds. Example: <h1 style="color:#6A287A">...</h1> and <h2 style="color:#6A287A">...</h2>. Count visible characters only, excluding HTML tags and attributes.

Do not place a short heading or hook line immediately alongside an H1 or H2. The sequence is H1, H2, then a substantial topic-specific paragraph; only after that paragraph may a relevant hook line or short subheading appear. Subsequent hooks must also introduce genuine paragraphs. Do not substitute a hook for meaningful body content or create heading-only blocks. A hook must not duplicate the H1 or H2. Use valid HTML nesting and maintain a readable hierarchy.

Section drafting sequence

For each of the 10 sections: identify the approved responsibility; research the local service need; draft H1 and H2 in styled HTML; write an original substantive opening paragraph; add a hook only after that paragraph; develop distinct analysis and examples; integrate relevant evidence and verified links; count genuine readable body words; check for duplication and banned language. Do not average section lengths. Aim for 850–900 genuine body words under the conservative range until the conflicting maximum is formally resolved.