MORIS MEDIA / PROTOCOL 18

HTML Formatting & Visual Content

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 36–36

0036 | •	All H1, H2, Article Content and FAQ fields that require formatting must be clean, publication-ready HTML. Use semantic HTML, short paragraphs, selective bolding, descriptive crawlable links and clean responsive structures. Avoid unnecessary scripts or decorative code.

Binding source requirements: lines 826–831

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.

Binding source requirements: lines 878–947

0878 | 1. Understand the Article Before Writing FAQs
0879 | Before writing FAQs, understand the complete article subject, search intent, all 10 sections, audience, target keywords, geographic intent, evidence, services, user concerns and information gaps.
0880 | Every FAQ must be specifically written for that article. Do not reuse another article's FAQs by changing only the service, keyword or location.
0881 | 2. Mandatory FAQ Structure
0882 | The FAQ section must appear immediately after Section 10.
0883 | Every article must contain exactly:
0884 | 1 Frequently Asked Questions heading
0885 | 10 FAQ Questions
0886 | 10 FAQ Answers
0887 | Every FAQ question must be written in HTML.
0888 | Every FAQ answer must be written in HTML.
0889 | Every question and its corresponding answer must form 1 expandable FAQ unit.
0890 | The question remains visible and the answer expands only when the reader clicks the question.
0891 | 3. FAQ Question Protocol
0892 | Every question must:
0893 | Contain 45–75 visible characters including spaces
0894 | Target genuine search intent
0895 | Be directly relevant to the article subject
0896 | Be different from the other 9 questions
0897 | Be grammatically correct
0898 | Avoid keyword stuffing
0899 | Avoid AI buzzwords
0900 | Avoid unsupported guarantees
0901 | Be placed inside the expandable HTML question structure
0902 | The visible question should use Moris Media's Purple #6A287A, with numbering or accents using Pink #EE1D56.
0903 | 4. FAQ Answer Protocol
0904 | Before writing an answer, first understand exactly what the question is asking.
0905 | The answer must address the question first. Moris Media positioning should appear naturally after the informational answer.
0906 | Every answer must:
0907 | Contain 100–150 genuine readable words
0908 | Be written in third person
0909 | Contain the exact {year} variable
0910 | Contain exactly 2 relevant target keyword phrases
0911 | Be completely unique
0912 | Provide a direct and useful answer
0913 | Contain 1 contextual backlink
0914 | Contain 1 plain URL when required
0915 | Contain 1 unique Moris Media solution line
0916 | Use selective bold formatting where valuable
0917 | Contain exactly 1 CTA button
0918 | End with the CTA button
0919 | The answer must be contained inside the same expandable HTML block as its question.
0920 | 5. Mandatory Expandable HTML Requirement
0921 | Every FAQ must function as an expandable accordion.
0922 | The structure must follow this sequence:
0923 | Expandable FAQ Container
0924 | Question Number
0925 | FAQ Question
0926 | Expandable Answer Area
0927 | Answer Body
0928 | Contextual Backlink
0929 | Plain URL when required
0930 | Moris Media Solution Line
0931 | 1 CTA Button
0932 | The question must be visible before expansion.
0933 | When the question is clicked, the corresponding answer must expand directly underneath it.
0934 | The FAQ must work without requiring unnecessary scripts or external dependencies.
0935 | 6. Moris Media HTML Colour Protocol
0936 | Every FAQ question and answer must follow these colours:
0937 | Purple: #6A287A
0938 | Used for primary question text and CTA button background.
0939 | Pink: #EE1D56
0940 | Used for FAQ numbering, borders or important accents.
0941 | Yellow: #FDEC07
0942 | Used for the answer accent line.
0943 | Charcoal: #2B2B2B
0944 | Used for answer text.
0945 | White: #FFFFFF
0946 | Used for the main FAQ background.
0947 | The design must remain clean, professional, responsive and easy to read.

Binding source requirements: lines 1008–1030

1008 | Important facts
1009 | Important limitations
1010 | Moris Media solution positioning
1011 | Ranking/search-intent phrases
1012 | CTA wording
1013 | Do not bold the complete answer.
1014 | 13. AI Buzzwords Are Prohibited
1015 | Do not use:
1016 | Premier, Cutting-Edge, Game-Changing, Revolutionary, Unparalleled, Transformative, Next-Generation, Dynamic, Bespoke, Groundbreaking, Elevate, Unlock, Amplify, Seamless, Robust, Holistic, Powerhouse, Landscape, Empower, Harness, Leverage, Tailored, Navigate, Journey, Vibrant, Thriving or similar AI-style filler terminology.
1017 | Use specific, factual and useful language instead.
1018 | 14. FAQ Uniqueness Protocol
1019 | All 10 questions must be unique.
1020 | All 10 answers must be unique.
1021 | Do not repeat the same:
1022 | Question construction
1023 | Answer opening
1024 | Paragraph architecture
1025 | 2-keyword combination
1026 | Backlink sentence
1027 | Moris Media positioning line
1028 | Ranking construction
1029 | CTA wording
1030 | Closing construction

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.

Responsive HTML and accessibility

Use semantic tags, readable paragraphs, accessible contrast, meaningful link labels and responsive tables only when useful. Do not add external scripts for simple accordions. For expandable FAQs use native <details> and <summary> elements. Keep heading levels logical and do not use styling alone to simulate an H1 or H2.