MORIS MEDIA / PROTOCOL 02

Master Execution Overrides

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.

Conflict register: approval required

The source contains inconsistent targets: section word count 850–900 versus 900–1,200 preferred; banner description 30–60 words versus 110 characters; 3–5 versus 3–4 hook lines; 3–4 versus 5–7 section keywords; universal geography versus the final India-specific 10-article assignment. Do not silently resolve these. Minimum 850 body words and exactly 62 columns are consistently mandatory. Obtain approved precedence for incompatible upper bounds.

Binding source requirements: lines 29–37

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.
0034 | •	Every proposed Moris Media Page URL must be checked against the live Moris Media website before assignment. If the proposed URL already exists for another page, create a different SEO-friendly slug. Never invent, overwrite or duplicate a live page URL.
0035 | •	Use only the approved legacy and achievement numbers pasted into the approved achievement placeholder. Do not invent, alter, inflate, transfer or localize an unrelated achievement.
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.
0037 | •	Every article must satisfy Search Intent, E-E-A-T, technical on-page SEO, URL/slug quality, content usefulness, local entity relevance, anti-over-optimization, character-count governance, keyword naturalness and programmatic SEO uniqueness before export.

Binding source requirements: lines 102–115

0102 | COLUMN-SPECIFIC EXECUTION NOTES
0103 | Meta Title: 50–60 visible characters. Unique, location-specific, service/topic-specific, natural search intent. Never use {year}.
0104 | Meta Description: 150–160 visible characters. Explain service/topic, location, useful value and differentiator without stuffing.
0105 | Meta Keywords: 9–10 natural phrases combining primary service, ranking, location, commercial, deliverable and semantic intent.
0106 | Page URL: Lowercase, hyphen-separated, concise, topic/location relevant, no tracking parameters or fixed year. Check live-site existence before use.
0107 | Banner Heading: 35–70 visible characters. Ranking/search intent + service/topic + location where natural.
0108 | Banner Subheading: 50–110 visible characters. Distinct capability/deliverable/value; do not repeat Banner Heading.
0109 | Banner Description: 30–60 words. Specific service value, not a slogan.
0110 | Banner CTA: Exactly 1 HTML CTA linked to https://www.morismedia.in/time-slot/schedule-a-call-digital-doctors using Moris Media Purple #6A287A and White #FFFFFF.
0111 | H1: Exactly 1 per section, HTML, 75–85 visible characters. Search need + ranking intent + service + one location + {year} where relevant.
0112 | H2: Exactly 1 per section, HTML, 60–75 visible characters. Must answer/support H1 and position Moris Media as the relevant solution.
0113 | Hook Lines: 3–5 inside each Article Content cell, HTML, 40–50 visible characters each. Must describe actual problem, deliverable, evidence, execution or outcome.
0114 | Article Content: Minimum 850 genuine body words in every individual section. Preferred 900–1,200. Word count cannot be averaged across sections.
0115 | FAQs: Exactly 10 expandable HTML FAQ units after Section 10. Questions 45–75 visible characters. Answers 100–150 genuine words, third person, {year}, exactly 2 keywords, 1 contextual backlink, unique Moris Media solution line, exactly 1 CTA.

Binding source requirements: lines 1140–1162

1140 | Keywords: Each section must contain its supplied section-specific keywords naturally. Mechanical keyword blocks, truncated phrases and keyword stuffing are prohibited.
1141 | Backlinks: Each section’s backlinks must be selected according to that section’s subject. The same backlinks cannot be mechanically repeated across all 100 sections. All Moris Media links must be checked as existing before use. Contextual links must use descriptive anchor text. Where the protocol requires a final plain URL, it must be a verified existing and relevant Moris Media page.
1142 | FAQs: Every article requires 10 independently written FAQs. Therefore all 100 questions and 100 answers must respond to their actual topic and question. The same FAQ bank cannot be copied across all 10 articles. Each answer must follow the approved HTML, keyword, {year}, third-person, backlink and CTA protocols.
1143 | 62-column structure remains locked: I will not add, remove, rename, reorder or merge columns. The corrected workbook remains exactly A–BJ, 62 columns, 1 worksheet, 10 India article rows.
1144 | Final uniqueness validation: Before delivery, I will compare the 10 articles against one another for duplicate or near-duplicate Meta Titles, Meta Descriptions, Meta Keywords, Banner fields, H1s, H2s, section paragraphs, hook lines, FAQs and backlink patterns. Any content that is essentially the same with substituted keywords will be rewritten before export.
1145 | Most importantly, “unique” will mean a different search intent, editorial argument, research direction, evidence sequence, wording and decision value, not merely different words.
1146 | 
1147 | FINAL NON-NEGOTIABLE VALIDATION
1148 | •	Exactly 62 columns from A to BJ; no renamed, reordered, merged, deleted or additional columns.
1149 | •	One single worksheet containing all completed articles.
1150 | •	One row equals one complete Topic × Target Location article.
1151 | •	Exactly 10 H1 fields, 10 H2 fields and 10 Article Content fields per row.
1152 | •	Every Article Content cell contains at least 850 genuine readable body words after exclusions.
1153 | •	Every H1 contains 75–85 visible characters; every H2 contains 60–75; every hook heading contains 40–50.
1154 | •	Every article contains exactly 1 FAQ Common Heading, 10 FAQ Questions and 10 FAQ Answers.
1155 | •	Every FAQ answer satisfies the approved HTML, word-count, keyword, {year}, backlink, third-person and CTA rules.
1156 | •	Every URL is SEO-friendly, verified and non-conflicting with an existing Moris Media page.
1157 | •	Every article and every section is independently written and locally researched.
1158 | •	No first-person or second-person language.
1159 | •	No em dash, prohibited AI buzzwords, filler transitions, keyword stuffing, fabricated evidence, unsupported guarantees or location-swapped copy.
1160 | •	Only approved achievement and legacy numbers are used, with correct service and geographic scope.
1161 | •	All mandatory HTML is clean, semantic and publication-ready.
1162 | •	Do not export until every validation rule passes.

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.

Controlling precedence

Apply explicit assignment scope first, then approved topic-specific breakdowns, then approved protocol overrides, then field-specific validation, then style examples. Where a conflict remains unresolved, flag it before producing the affected fields. The approved global revision makes the protocol applicable to all countries. The revised 30–60 word banner description controls over the older 110-character example. The minimum 850 genuine section body words remains mandatory. The 850–900 range is the conservative default until a wider maximum is explicitly approved.