MORIS MEDIA / PROTOCOL 19

FAQ Content & Accordion Protocol

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 81–101

0081 | AP	FAQ Common Heading	40 characters	75 characters
0082 | AQ	FAQ 1 Question	8 words / 45 chars	20 words / 75 chars
0083 | AR	FAQ 1 Answer	100 body words	120–160 preferred; 150 max if FAQ protocol controls
0084 | AS	FAQ 2 Question	8 words / 45 chars	20 words / 75 chars
0085 | AT	FAQ 2 Answer	100 body words	120–160 preferred; 150 max if FAQ protocol controls
0086 | AU	FAQ 3 Question	8 words / 45 chars	20 words / 75 chars
0087 | AV	FAQ 3 Answer	100 body words	120–160 preferred; 150 max if FAQ protocol controls
0088 | AW	FAQ 4 Question	8 words / 45 chars	20 words / 75 chars
0089 | AX	FAQ 4 Answer	100 body words	120–160 preferred; 150 max if FAQ protocol controls
0090 | AY	FAQ 5 Question	8 words / 45 chars	20 words / 75 chars
0091 | AZ	FAQ 5 Answer	100 body words	120–160 preferred; 150 max if FAQ protocol controls
0092 | BA	FAQ 6 Question	8 words / 45 chars	20 words / 75 chars
0093 | BB	FAQ 6 Answer	100 body words	120–160 preferred; 150 max if FAQ protocol controls
0094 | BC	FAQ 7 Question	8 words / 45 chars	20 words / 75 chars
0095 | BD	FAQ 7 Answer	100 body words	120–160 preferred; 150 max if FAQ protocol controls
0096 | BE	FAQ 8 Question	8 words / 45 chars	20 words / 75 chars
0097 | BF	FAQ 8 Answer	100 body words	120–160 preferred; 150 max if FAQ protocol controls
0098 | BG	FAQ 9 Question	8 words / 45 chars	20 words / 75 chars
0099 | BH	FAQ 9 Answer	100 body words	120–160 preferred; 150 max if FAQ protocol controls
0100 | BI	FAQ 10 Question	8 words / 45 chars	20 words / 75 chars
0101 | BJ	FAQ 10 Answer	100 body words	120–160 preferred; 150 max if FAQ protocol controls

Binding source requirements: lines 878–1035

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.
0948 | 7. Exactly 2 Keywords Per Answer
0949 | Every answer must contain exactly 2 target keyword phrases.
0950 | Both keywords must be selected after understanding the specific question.
0951 | They must:
0952 | Match the article subject
0953 | Match the FAQ intent
0954 | Appear naturally
0955 | Not be keyword-stuffed
0956 | Not be mechanically repeated
0957 | The keyword combination should vary across the 10 answers.
0958 | 8. {year} Variable Protocol
0959 | Every FAQ answer must contain:
0960 | {year}
0961 | Never manually write an actual year.
0962 | Correct:
0963 | for {year}
0964 | Incorrect:
0965 | for 2026
0966 | The variable must remain exactly:
0967 | {year}
0968 | 9. Moris Media Ranking & Solution Positioning
0969 | After directly answering the question, every answer must naturally position Moris Media as a relevant solution.
0970 | Where appropriate, use ranking/search-intent language such as:
0971 | {city}'s No.1 [Agency Type]
0972 | Top [Agency Type] in {city}
0973 | Best [Agency Type] in {city}
0974 | Leading [Agency Type] in {city}
0975 | Top-Rated [Agency Type] in {city}
0976 | Example:
0977 | For organisations comparing {city}'s No.1 [Agency Type] for {year}, Moris Media can be evaluated for its [Keyword 1] and [Keyword 2] capabilities against the required scope and evidence.
0978 | Another example:
0979 | Moris Media positions its services around the standards expected when clients search for a Top [Agency Type] in {city} for {year}.
0980 | Every solution line must be different.
0981 | Ranking language must remain marketing/search-intent positioning unless supported by an independent ranking.
0982 | 10. Mandatory CTA Button
0983 | Every FAQ answer must contain exactly 1 CTA button.
0984 | The CTA button must always link to:
0985 | https://www.morismedia.in/time-slot/schedule-a-call-digital-doctors
0986 | The CTA must relate to the question and article subject.
0987 | Examples:
0988 | Want to Hire {city}'s No.1 [Agency Type]? Schedule a Call
0989 | Looking for a Top [Agency Type] in {city}? Schedule a Call
0990 | Need a Leading [Agency Type] in {city}? Book a Consultation
0991 | Searching for the Best [Agency Type] in {city}? Schedule a Digital Doctors Call
0992 | Want to Discuss [Service Type] for {year}? Book a Strategy Call
0993 | The CTA wording should vary across the 10 answers, but every CTA must link to the same approved scheduling URL.
0994 | 11. Contextual Backlink Protocol
0995 | Every FAQ answer must contain 1 contextual backlink relevant to the question.
0996 | The destination must be:
0997 | Existing
0998 | Verified
0999 | Relevant
1000 | Useful to the reader
1001 | Do not invent URLs.
1002 | Do not add unrelated backlinks simply to satisfy the link requirement.
1003 | A plain-text URL may also be included where required by the publishing specification.
1004 | 12. Bold Formatting Protocol
1005 | Use bold formatting where it improves readability, particularly for:
1006 | Keyword 1
1007 | Keyword 2
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
1031 | Different articles must also receive independently written FAQs.
1032 | 15. Mandatory HTML Construction
1033 | Every FAQ must follow the exact functional pattern below:
1034 | Opening expandable FAQ container
1035 | Clickable HTML question

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.

FAQ markup reference

<details style="border:1px solid #EE1D56;background:#FFFFFF">
  <summary style="color:#6A287A">[Verified question]</summary>
  <div style="color:#2B2B2B;border-left:3px solid #FDEC07">
    <p>[100–150 genuine answer words, including {year}]</p>
    <a href="[verified relevant URL]">[descriptive anchor]</a>
    <a style="background:#6A287A;color:#FFFFFF" href="https://www.morismedia.in/time-slot/schedule-a-call-digital-doctors">SCHEDULE A CALL</a>
  </div>
</details>

Produce exactly 10 distinct accordion items. Each answer requires exactly 2 natural target keyword phrases, 1 verified contextual backlink, 1 specific Moris Media solution line, the exact literal {year} and 1 final CTA. Questions must have 45–75 visible characters. Answer word counts exclude HTML and CTA labels.