The MS Authority Execution System
From MS Resource Sheet architecture to a published, interlinked, citable page — every step, every prompt, every tool. Built for the team that must ship 2–3 assets a week without quality collapse.
Table of Contents
- Step 4 Manual SERP & Keyword Validation (No AI)
- Step 5 AI Keyword Expansion Inside the Cluster
- Step 6 Cannibalisation Check
- Step 6B Entity Verification (Knowledge Graph)
- Step 7 Semantic & PAA Expansion
- Step 8 Write the MS Brief (No Brief, No Page)
- Step 9 SERP & Competitor Analysis
- Step 10 Competitor Entity & Authority Analysis
- Step 11 Content Gap & Information Gain Lock
The Niche, the Voice and the Page Are Already Decided. Load Them Correctly.
AI has no memory of MS between chats. So Paste this first, every time in the beginning of Chat On Any Page.
- Open the MS Resource Sheet and the cluster map sheet.
- Go to Coda, and find your assign task, then select it from the MS Resource Sheet. It already has: Keyword, Topic Cluster, Search Intent, Global Volume, KD Level, CPC, Parent Topic, Recommended Content Type
- Copy that row into your working doc as Step 3 (1st Output) That row is your instruction set, and baseline.
- Search the primary keyword on Google, and Then Open Live Gemini
- Run The below prompt to collect the SERP analysis, GEO behavior.
Act as an SEO Strategist enforcing the MS-AES content format rules.
I am providing you with the primary keyword and the live top-10 Google search results (or a description of what dominates Page 1).
Analyze the search landscape and provide a definitive strategic playbook based on the MS matrix.
PRIMARY KEYWORD: [PASTE KEYWORD]
INTENT TYPE TARGETED BY TEAM: [e.g., Transactional/Service OR Informational/Blog]
LIVE PAGE 1 OBSERVATIONS (What kinds of pages are ranking? Are there tools like Ahrefs/HubSpot? Is there an AI Overview?):
[PASTE COPIED GOOGLE SEARCH RESULTS OR A 2-SENTENCE DESCRIPTION OF PAGE 1]
Evaluate the data and provide the following 4 tactical outputs:
- 1. INTENT MATCH: Does our targeted intent match what Google is serving? (e.g., If we want to build a service page but Page 1 is entirely long guides, state: “MISMATCHED INTENT – FLAGGED FOR ARCHITECTURE OWNER”).
- 2. AI OVERVIEW PLAN: Is an AI Overview present? (Yes/No). If Yes, remind me: “Write a strict 40-word answer-first block to be lifted.”
- 3. AUTHORITY BARRIER: Are massive players (Ahrefs, Semrush, Moz, HubSpot) dominating? If Yes, state: “HIGH BARRIER: Abandon breadth. Pivot strategy to proprietary data layers and specific hospitality proof.”
- 4. THE FORMAT VERDICT: State clearly what format this content MUST take to compete (e.g., Commercial Service Page, Deep Informational Guide, or Specific Case Study).
Validating the Assigned Keyword, Confirming the Cluster, and Finding What Nobody Else Has
- Google Autocomplete: Type the primary keyword. Record every suggestion. Then add a letter after it (“technical seo audit a”, “…b”) and collect more. This is live Google data.
- People Also Ask: Search the keyword. Expand every PAA question — more appear as you click. These become your H2s in Step 13. Copy every one.
- Related Searches: Bottom of the SERP. Copy all 8. Then search one of those and harvest its related searches too.
- Ahrefs or Semrush (ONE tool, ONE date): Pull volume, KD and CPC. Record the tool and date in the sheet header. Part 4 is explicit — one tool, one date, or the data is not comparable.
- Local volume column: Pull volume for MS’s actual target geography, not global. A 97,974-global-volume keyword MS cannot serve is a vanity metric.
You should finish with 30–50 manually sourced keywords and every PAA question for this page.
AI expands what you already proved with real data. The cluster lock is the constraint that makes it safe.
- Site search: Google
site:marketingscrappers.com [your primary keyword]. If an existing MS page already ranks for it, stop and escalate to the Architecture Owner. You are about to cannibalise.
Use AI as a second pair of eyes on overlap — but the site: search you ran above is the real evidence.
- Go to Google Knowledge Graph API Reference → “Try this API.”
- 🛠️ The Crucial Fields to Enter Value, as below guided:
- 1. limit (Highly Recommended) Type 5 or 10
- 2. types (Use for Intent Filtering) Leave it blank initially. If you get too much clutter, type a specific Schema.org type like Organization, Place, Person, or TechArticle.
- 3. languages: Type English: en Spanish: es French: fr German: de. Urdu: ur Persian: fa Arabic: ar
- 4. Query your primary keyword. Execute. Read the JSON.
- 5. Use this prompt with the JSON-LD Code as input with it: { Act as an expert SEO Entity & Knowledge Graph Engineer. I am going to provide you with a raw JSON payload from the Google Knowledge Graph Search API for an MS (Marketing/SEO) or hospitality optimization project. Your job is to cleanly parse the JSON and extract only the relevant semantic entity nodes, discarding any clutter. ### Extraction Rules: 1. Extract every entity from the `itemListElement` array. 2. For every entity, strictly capture: – Name (`result.name`) – Type (`result.@type` — list all schema types returned) – Machine ID (`result.@id`) – Confidence Score (`resultScore`) 3. Format the final output into a clean Markdown table sorted by `resultScore` from highest to lowest. ### Contextual Flagging: Highlight with a 🌟 star emoji if any of the extracted entities match or directly align with our core baseline stacks: – MS Stack: Google Search Console, Core Web Vitals, Schema.org, Ahrefs, Semrush, Screaming Frog, Lighthouse, PageSpeed Insights, Google Business Profile, WordPress, E-E-A-T, AI Overviews, Perplexity, ChatGPT. – Hospitality Stack: OTA, Booking.com, Expedia, Direct Booking, RevPAR, ADR. ### Content Mapping Guidance: Below the table, provide a quick 2-sentence summary of how the highest-scoring entities should dictate our heading hierarchy ($H2$/$H3$) or Schema markup. Do not hallucinate or guess fields not present in the JSON. Here is the raw JSON input: [PASTE YOUR JSON HERE] }
Feed it the entities you confirmed. It maps them to sections and finds what you missed.
This output IS your outline. Treat it as structural, not supplementary.
| Field | Rule |
|---|---|
| Working title | — |
| URL slug | Final. Never changed after publish. Lowercase, hyphens, 3–5 words, no stop words, no dates, no numbers. |
| Cluster | One of 5. No exceptions. |
| Parent pillar | The exact pillar URL. |
| Primary keyword | One. From the validated sheet. |
| Secondary entities | 5–10 from your Step 6B map. Entities, not keyword variants. |
| Search intent | One only. |
| Page type | Guide / How-to / Checklist / Comparison / Diagnostic / Data / Buyer Guide. |
| The one question this page answers | If you need two sentences, it is two pages. |
| 40-word answer | The most important field in the brief. Drafted now, at brief stage. From Step 7. |
| H2 question list | 6–12 questions. From Step 7. |
| MS proprietary angle | What does MS know, or have observed, that nobody else can write? If this field is empty, the article is a commodity and should be reconsidered. |
| Required links OUT | Pillar (1), siblings (2–3), service page (1+), industry page (0–1), glossary (1+). |
| Required links IN | Which EXISTING pages must be edited to link TO this page? Name them. This is how orphans are prevented. |
| Lead magnet / CTA | Exactly one. |
| Schema | BlogPosting + Breadcrumb (+ FAQPage / HowTo if applicable). |
| Author | Named human. Never “Admin.” |
| Publish date | Fixed. A Friday. |
Every prior step feeds this. AI assembles the brief; the Content Owner approves it.
- Google your primary keyword in a clean window.
- Open the top 3 organic results (skip ads).
- For each, record: length, structure, do they use tables, do they have FAQs, do they show real data or borrowed statistics, is there a named human author with credentials.
- The key question: is their evidence first-hand or aggregated? Almost always it is aggregated. That is the gap.
“What does this page contain that the top 3 results do NOT?”
Your answer must be one of these. Vagueness is a fail:
- A real observation from an MS client engagement or audit (“across the hotel sites we audited, X was broken in most of them”)
- An original framework or decision table MS uses internally
- A counter-argument the competitors avoid because it is commercially inconvenient
- Fresher or more specific data than the competitors have
- An honest admission that changes the reader’s decision (“in this situation, do not hire us — do this instead”)
If you cannot answer, do not proceed to writing. Go to Step 12B and get a real observation, or return the page to the Content Owner as a commodity.
Building the GEO Strategy, Extracting MS’s Proprietary Angle, and Writing the Draft
Part 8 is blunt: the internal links ARE the deliverable. Nothing else compounds this cheaply. Your page has a link quota by type, and it is a floor, not a target:
| Page Type | Min links OUT | Must link to | Min links IN |
|---|---|---|---|
| Service Page | 8 | Parent sub-hub, 3–4 siblings, 1–3 industries, 1 pillar, 2–3 supporting articles, 1 case study | 5 |
| Industry Page | 8 | Parent hub, 3–5 services, 1–2 case studies, 1–2 supporting articles | 4 |
| Pillar | 15+ | EVERY supporting article in its cluster, 3+ service pages, 2+ glossary terms, 1 case study | 6 |
| Supporting Article | 6 | Parent pillar (1), siblings (2–3), commercial page (1+), glossary (1+) | 2 |
| Case Study | 5 | The service it proves, the industry it belongs to, parent pillar, 2 related articles | 3 |
Below the floor = fails the Pre-Publish Gate. A service page with fewer than 8 outbound internal links is incomplete, not “lean.”
Before writing, you must contribute at least one of these to the page. Pull it from the sheets — do not invent it.
| Source Sheet (Part 9 s.1) | What you can pull | What it sounds like on the page |
|---|---|---|
| Audit Log | The 10 most common defects across audited sites; CWV scores before; indexation ratio; schema coverage | “Across the hotel sites we audited, the booking path was blocked from crawling on most of them.” |
| Client Baseline / Delta | Before/after rankings, traffic, speed, indexed pages | “A 40-room property went from LCP 6.1s to 1.9s. Here is exactly what we changed, in order.” |
| Experiment Log | Hypothesis → change → result → confidence | “We tested X on two properties. It worked on one. Here is why we think it failed on the other.” |
| AI Visibility Log | Which engines cited whom for a given query | “We ran this query across four AI engines monthly. Here is who got cited and what they had in common.” |
| Case Study Intake | Full before/after, timeframe, what worked, what did not | A named result with a real number and an honest caveat. |
- The contrarian take. The commercially inconvenient truth agencies avoid because it costs them a sale. MS’s voice permits this — in fact it requires it. Example: “Most ‘SEO audit’ offers are lead-generation forms with a PDF attached. If the audit does not tell you something that changes what you spend money on next month, it is not an audit.”
- The original contribution. Your real observation from Step 12B, written as one clear paragraph, with its number and its limitation.
- The real data asset. A screenshot from actual client work, a before/after table you built from real numbers, a decision table MS genuinely uses internally. Something that exists.
- One H1. Contains the primary keyword.
- Answer-first block directly under the H1: 40 words, before any other content.
- Every H2 is a real question, phrased the way a human would ask it — from your Step 7 question set.
- Under every H2: a 40-word answer. Self-contained. It must make sense lifted out of the page entirely, because it will be.
- At least one table. Tables are the most extractable format there is.
- Then elaboration, context, nuance.
Never build up to a point. Lead with it. Context comes second, always.
If you tell AI “write about technical SEO audits,” it writes what every other agency published. If you tell it who MS is, what the competitors lack, what MS observed in a real hotel audit, and hand it a validated outline — you get something that could only have come from MS.
This step is the difference between good and unusable. Send it as its own message. Do not combine it with the writing instruction.
AI writes the draft. AI does not write the final page. Part 7 assigns the Writer the research, outline and draft — and specifically says the Writer “owns the proprietary angle.” That part is human. The draft is a starting point that a human then makes true.
On-Page, Entity Coverage, Voice Repair, Schema — and the Gate That Stops Bad Pages
- Primary keyword in the H1
- Primary keyword in the URL (already locked at brief stage — never change it now)
- Primary keyword in the title tag
- Primary keyword in the first 100 words — naturally
- Every entity from the Step 6B map appears at least once
- Every H2 is a question, and every H2 has a 40-word answer under it
- The MS observation is present, with its real number and its limitation intact
- At least one table exists
- No keyword stuffing — it reads like a practitioner wrote it, not an optimiser
AI-assisted drafts leave patterns: uniform paragraph lengths, “Furthermore,” and “Moreover,” every section with exactly three bullets, headings all in the same grammatical shape, and a relentless neutral positivity that never commits to anything.
MS’s voice is the opposite of that. It is specific, blunt, and willing to say the inconvenient thing. This pass is not cosmetic humanisation — it is restoring the brand voice the model sanded off.
Title tag: under 60 characters, contains the primary keyword. Meta description: under 155 characters — and per Part 5, it contains the outcome and a differentiator, not a summary. Both written deliberately. Auto-generated metas fail the gate.
