AI Domination Stack

Place a complete TL;DR answer above the fold, use short paragraphs and lists, add Key Takeaways, and format answers to match question structure for direct extraction.

• Place complete standalone answer in the first 80 to 100 words as a TL;DR
• Use short paragraphs of three to four sentences with bold key claims, lists, and tables
• Add a Key Takeaways or Quick Answer box at the top of every high-intent page
• Include author name, last-updated date, and inline citations on every claim
• Format answers to match question structure with a direct definition for what is queries
• Write self-contained 40 to 60 word answer paragraphs that work as extracted snippets
• Add Question and Answer schema where genuinely applicable

Lead with original stats and research, write authoritative third-person language, embed expert sections, and pair every claim with a verifiable source link.

• Lead with unique statistics, original research, or comparison data in the first 300 words
• Use authoritative fluent language and avoid hedging like might or could
• Add Expert Perspective or From Our Research subsections with credentialed authors
• Maintain high factual density so every paragraph contains at least one citable fact
• Use third-person factual statements that LLMs can directly quote
• Include Why It Matters framing that explains stakes and context
• Pair every key claim with a verifiable source link

Write in Q&A format with conversational H2s, second-person tone, follow-up sections, and prompt starter suggestions optimized for chatbot retrieval.

• Write in natural Q and A format with H2s phrased as actual user questions
• Create dedicated follow-up question sections at the bottom of each topic
• Use conversational H2s like What is X, How do I Y, and Why does Z happen
• Match exact phrasing from voice search queries and chatbot prompts
• Write in second person with a direct, helpful tone
• Add a Related Questions section that mirrors PAA structure from Google
• Include conversation starter prompts users could paste into ChatGPT

Structure content into self-contained 200 to 400 word chunks led by topic sentences, use semantic boundaries with id attributes, and avoid cross-chunk references.

• Structure content into self-contained chunks of 200 to 400 words that stand alone
• Each chunk leads with a topic sentence summarizing the entire section
• Add semantic chunk boundaries via section and article tags with id attributes
• Avoid mid-paragraph references like as mentioned above so chunks stand alone
• Include enough context per chunk that a retrieval system can return it as a complete answer
• Use descriptive H2 and H3 headings that act as chunk titles
• Test chunk extraction by copying any single section and confirming it stands alone

Identify common AI prompts in your niche, build dedicated answer pages, match expected response formats, anticipate follow-ups, and weekly-test prompt visibility.

• Identify common prompt patterns users send to ChatGPT, Claude, and Perplexity in your niche
• Build dedicated answer pages for each prompt pattern
• Match content structure to expected AI response format like comparison tables and ranked lists
• Anticipate follow-up prompts and pre-answer them on the same page
• Use prompt-style headings like Compare X vs Y or Best X for use case
• Include a section telling users how to ask AI about your content
• Test target prompts weekly across major AI engines

Add consistent Organization and Person schema with stable @id URIs, build an entity hub, link external sources, and maintain attribute completeness.

• Add consistent Organization and Person schema on every page with stable @id URIs
• Build a central entity hub at /entity/ or /about/ with full markup
• Link to authoritative external entity sources via sameAs
• Use the exact entity name consistently across all pages with no variations
• Cross-reference entities across schemas like Organization to founder Person to Articles
• Add additionalType to specify subtype precisely
• Maintain entity attributes including founding date, founders, products, services, and awards

Submit Organization plus sameAs JSON-LD, claim Knowledge Panel, build entity attributes, link to Wikidata Q-ID, and monitor for inaccuracies.

• Submit complete Organization and sameAs array in JSON-LD on homepage and About
• Build relationships with related entities via parentOrganization and memberOf
• Claim and complete Google Knowledge Panel via Search Console verification
• Build out entity attributes including founding date, founders, awards, and headquarters
• Cross-link to Wikidata Q-ID via sameAs so Google connects to its knowledge graph
• Monitor Knowledge Panel for inaccuracies and submit corrections
• Add Person knowledge graph for founders with full sameAs network

Publish a JSON brand-language feed with official facts, version timestamps, robots and llms.txt references, and human-readable mirror pages.

• Create a public JSON file at /brand-language-feed.json with official brand facts
• Include name, alternate names, values, product specs, positioning, and key messaging
• Add lastUpdated timestamp and version field for AI freshness validation
• Reference the feed from robots.txt and llms.txt so AI crawlers discover it
• Update quarterly via CMS export script automated through webhooks
• Mirror feed contents in a human-readable /brand/ page
• Provide downloadable JSON, YAML, and markdown formats

Build the Wikidata entry first, populate properties, reference Q-ID via sameAs, and build a neutral Wikipedia article only via experienced editors.

• Build the Wikidata entry first because the notability bar is lower than Wikipedia
• Add structured Wikidata properties including instance of, founders, headquarters, and industry
• Reference Wikidata Q-ID across all Person and Organization schema via sameAs
• Build a neutral, well-sourced Wikipedia article via an experienced editor and never self-edit
• Maintain consistent facts between Wikidata, Wikipedia, your site, and authoritative sources
• Link Wikidata entry to LinkedIn, Crunchbase, GitHub, and other authority profiles
• Monitor for vandalism or inaccuracies on Wikipedia and Wikidata quarterly

Pair text with image, video, and audio assets, add ImageObject, VideoObject, and AudioObject schema, and embed transcripts and chapter markers.

• Pair every key content section with a relevant image, video, or diagram
• Add descriptive alt text, captions, and ImageObject or VideoObject schema
• Optimize images for Google Lens and Gemini multimodal recognition
• Include VideoObject with transcript, thumbnail, uploadDate, duration, and embed URL
• Add transcripts and chapter markers for all videos
• Use AudioObject schema for podcasts with full transcript embedded
• Cross-reference media across schema like Article to image to ImageObject

Add HowTo, SoftwareApplication, and structured function descriptions for tools, document parameters, and publish OpenAPI specs for agentic invocation.

• Add structured function descriptions in JSON-LD for tools, calculators, and processes
• Use HowTo schema for procedural content with full HowToStep markup
• Include a How to Use This section with clear inputs, outputs, and expected results
• Document parameters, prerequisites, and edge cases for AI agents
• Add SoftwareApplication schema with applicationCategory and operatingSystem
• Build agent-friendly descriptions including when to use and what is returned
• Document API endpoints in OpenAPI spec so AI agents may call them directly

Cluster related concepts, use consistent terminology, define key terms once, group related sections cleanly, and test cosine similarity to target queries.

• Structure content so semantically related concepts cluster naturally in embedding space
• Use consistent terminology within a topic and avoid mixing synonyms
• Define key terms once then use them consistently throughout the page
• Group related content into clearly bounded sections
• Avoid topical drift within a page so each maps to one tight embedding region
• Use OpenAI or Cohere embedding APIs to test page similarity to target queries
• Maintain semantic distinctness between competing pages on your site

Decide allow/disallow per AI bot, add explicit user-agent rules, monitor server logs, and document the bot allowlist for audit transparency.

• Decide allow or disallow strategy per AI bot defaulting to allow for citation visibility
• Add explicit rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and OAI-SearchBot
• Configure separate rules for training crawlers vs answer crawlers
• Monitor server logs for AI bot traffic and identify rogue bots
• Block bad-actor scrapers that mimic AI bots via user-agent verification at the WAF
• Add Cloudflare AI Audit or equivalent edge rules for granular bot control
• Maintain bot allowlist documentation for client transparency

Tailor signals per platform — ChatGPT, Perplexity, Claude, Gemini, Copilot, Grok — and test priority queries weekly across all six.

• Optimize for ChatGPT with direct answers, structured data, and OAI-SearchBot allowed
• Optimize for Perplexity with citation-rich content and PerplexityBot allowed
• Optimize for Claude with nuanced reasoning and ClaudeBot allowed
• Optimize for Gemini with strong E-E-A-T signals and a claimed Knowledge Panel
• Optimize for Copilot via Bing visibility, IndexNow, and Bing Webmaster Tools
• Optimize for Grok via real-time relevance, X presence, and current event tie-ins
• Test priority queries weekly across all platforms and document appearances

Run daily citation tracking via Profound, Otterly, AthenaHQ, or Rankability, track share of voice and accuracy, and feedback-loop poor performers.

• Set up daily citation tracking via Profound, Otterly, AthenaHQ, or Rankability
• Track citation rate per AI engine across ChatGPT, Perplexity, Claude, Gemini, Copilot, and Grok
• Monitor share of voice on relevant queries vs competitors
• Track citation accuracy whether AI quotes you correctly or incorrectly
• Document citation trend lines per page and per topic cluster monthly
• Build a feedback loop where uncited pages get audited and re-optimized
• Set monthly KPI targets per engine for citation count, share of voice, and accuracy

Build template-driven page systems with originality checks, auto-generate per-page schema and metadata, validate against thin-content thresholds, and monitor indexation.

• Build a template-driven page system for scalable answer pages with originality checks
• Auto-generate unique meta titles, descriptions, and schema per programmatic page
• Inject location, product, or attribute variables into deterministic content templates
• Add E-E-A-T elements per template including byline, last-updated, citations, and trust signals
• Validate every generated page passes thin-content checks before publishing
• Implement deduplication logic to prevent near-duplicate pages from indexing
• Monitor programmatic page indexation in Search Console weekly

Use SSR and edge personalization, ship modular blocks, add noscript fallbacks, and test as Googlebot and GPTBot to confirm static parity.

• Use edge or server-side rendering to personalize based on referrer, geo, or device
• Create modular, parseable content blocks AI engines can extract independently
• Add noscript fallbacks for any JS-rendered content
• Use SSR plus hydration so initial HTML contains full content for crawlers
• Test dynamic variants with Googlebot and GPTBot user-agents
• Implement A/B testing with proper rel canonical handling
• Avoid client-side-only personalization for SEO-critical content blocks

Cite every claim with clickable sources, use ClaimReview where applicable, list primary sources, date-stamp time-sensitive facts, and provide downloadable data.

• Every factual claim must have a clickable source link or inline citation
• Use Claim and ClaimReview schema for fact-check-eligible content
• Add citation property to Article schema listing primary sources
• Maintain a sources or references section at the bottom of every long-form article
• Cite primary sources like research papers and government data
• Date-stamp every claim with as of date for time-sensitive facts
• Add author byline with credentials for every claim-heavy article
• Provide CSV or JSON data files for proprietary research findings

Run brand queries across AI engines monthly, document descriptions and sentiment, counter inaccuracies via authoritative content, and update Wikipedia and Wikidata.

• Run brand queries across AI engines monthly like What is brand and Is brand reliable
• Document AI-generated brand descriptions, ratings, and sentiment per platform
• Identify outdated or incorrect AI claims and prioritize correction
• Counter inaccurate AI claims by publishing corrective authoritative content
• Update Wikipedia and Wikidata when AI engines pull from outdated entries
• Track AI sentiment drift over time
• Use AI audit tools like Profound, AthenaHQ, or Otterly to automate sentiment tracking

Update dateModified on real refreshes, show Last Updated banners, year-stamp titles, refresh stats and pricing quarterly, and rebuild stale competitive pages.

• Update dateModified in Article schema on every meaningful refresh
• Add a visible Last Updated banner at the top of every article
• Include current year in titles where relevant
• Refresh statistics, pricing, and time-sensitive claims quarterly
• Rebuild stale pages over 12 months old that target competitive keywords
• Set up Google Alerts on key topics to surface refresh-worthy news
• Build an editorial calendar with refresh slots, not just new content slots
• Add datePublished and dateModified so AI engines weight recency appropriately