`, each logical section in `

`, and supplementary blocks (Not For You, callouts, sidebar context) in `

`. Use `

` for the primary content area. Do not use `

` for content regions that have a semantic equivalent. Google's crawler uses these elements to identify the Main Content zone for passage ranking and AI extraction. A page built with semantic containers gives the crawler explicit signals about which content to weight highest. ### Proof-Term Proximity The specific numbers, entity names, and operational details that support a claim must appear in the same 500-token chunk as the H2 they support -- not separated by other sections. A proof term three sections away from its heading does not strengthen that heading's embedding signal. BERT and Neural Matching evaluate relevance within the passage window, not page-wide. If the supporting evidence for a claim cannot fit in the same chunk, split the topic into two headings, each with its own evidence block. Never orphan a proof term from its context heading. ### The RDFa Hack LLMs often ignore JSON-LD in the header. Embed semantic data directly inline using RDFa or Microdata (`` tags). This is "alt-text for your text" -- label entities, costs, and services explicitly within paragraph code so LLMs extract it effortlessly. ### Required Schema Per Page Type: - **FAQPage:** Wrap every question-based H2 + answer pair - **HowTo:** Any step-by-step booking or pickup process - **Product/Offer:** Pricing tables and service options - **LocalBusiness:** For facilities or lots listed - **BreadcrumbList:** Site navigation context See `references/schema-patterns.md` in the skill root for JSON-LD templates. Read it with: `cat "${SKILL_ROOT}/references/schema-patterns.md"` ### Schema Serves 3 Independent Functions: | Function | What It Does | Why It Matters | |----------|-------------|----------------| | Searchable (recall) | Can AI find you? | FAQPage surfaces Q&A in rich results and AI Overviews | | Indexable (filtering) | How you rank in structured results | Product/Offer enables price/rating filtering | | Retrievable (citation) | What AI can directly quote or display | Tables, FAQ markup, HowTo steps become citable | --- ## 7. VERIFICATION & TAGGING SYSTEM You are forbidden from inventing fake studies, statistics, or pricing. Use auditable tags for human editors. | Tag | When to Use | Format | |-----|-------------|--------| | `{{VERIFY}}` | Any specific price, rate, capacity, schedule, distance, or operational claim | `{{VERIFY: Garage daily rate $20 \| County Parking Rates PDF}}` | | `{{RESEARCH NEEDED}}` | A section that needs hard data you could not find or confirm | `{{RESEARCH NEEDED: Garage total capacity \| check master plan PDF}}` | | `{{SOURCE NEEDED}}` | A claim that needs a traceable citation before publish | `{{SOURCE NEEDED: shuttle frequency \| check ground transportation page}}` | ### Forensic EMQ Check -- Competitor Optimization Ratio The standing rule (Section 3) is: never put exact match keyword in H2/H3/H4. That rule holds in most niches. Exception: if the top 3 ranking pages ALL have the exact match keyword in their H1, the niche is over-optimized and EMQ in H1 is now a required signal, not a penalty risk. **How to check:** 1. From research data, inspect the H1 tags of the top 3 organic results 2. If 2 out of 3 contain the exact target keyword verbatim in H1: flag as `EMQ_REQUIRED: true` 3. If 1 or 0 contain EMQ: flag as `EMQ_REQUIRED: false` -- use entity-based headings per standard rules 4. Tag the finding in the brief: `{{VERIFY: Competitor H1 EMQ status | research SERP data}}` **Rule:** Do not apply EMQ to H2/H3/H4 regardless of competitor behavior. The H1 exception applies only when competitor ratio is 2/3 or higher. ### Source Citation Rules: **Do not cite vaguely.** Never write "official airport website" or "government data." Instead cite specifically: - "Broward County Aviation Department -- FLL Parking Rates (broward.org/airport/parking)" - "FLL Airport Master Plan, 2024 update, Section 4.2" - "FDOT Traffic Count Station 0934, I-595 at US-1 interchange" --- ## 8. REQUIRED PAGE STRUCTURE Use this structure unless the brief explicitly requires something else. ### 0. AI Summary Nugget (mandatory, first element after frontmatter) Every page must open with a 200-character (max) fact-dense summary block designed for LLM scrapers to cite as a consensus source. This block sits above the H1 as a `

` or equivalent. **Format:** One to two sentences. Pure facts, no marketing language. Include the primary entity, the key number, and the core distinction. Example: > FLL airport parking: $20/day long-term, $36/day short-term, $10/day overflow (peak only). Off-site lots start at ~$6/day with shuttle. Rates effective Nov 2024. **Why:** Perplexity, Gemini, and ChatGPT extract the highest-confidence, shortest factual passage as their "answer nugget." A pre-built nugget at position zero gives them exactly what they need, increasing your citation probability. ### 1. Title + URL Title: Clear, includes the main topic naturally, not overstuffed, promises a concrete outcome. The exact match keyword should appear in the title. URL: Streamline to feature the target keyword with no unnecessary extra words. Adding filler words into the URL hurts rankings. Example: `/airports/fll` not `/airports/fort-lauderdale-fll-airport-parking-guide-2026`. ### 2. Opening Answer Block (first 100-150 words) Answer the main query directly. Explain what makes this page useful or different. Preview the most important distinctions. ### 3. Fast-Scan Summary (immediately after opening) One of: bullet summary (3-5 bullets max, each with a concrete fact), key takeaways box, comparison table, or quick decision matrix. **Not optional.** Every page needs a scannable extraction target near the top. ### 4. Main Body with Distinct Sections Every section must do one unique job: explain, compare, quantify, define, rank, warn, price, or instruct. No filler sections. Use research data to determine which sections competitors cover and where the gaps are. ### 5. Comparison Table Real HTML `