Tygart Media

Tag: ChatGPT

  • How to Get Cited in ChatGPT Search in 2026: The Bing Index, OAI-SearchBot, and the 15% Citation Cliff

    How to Get Cited in ChatGPT Search in 2026: The Bing Index, OAI-SearchBot, and the 15% Citation Cliff

    ChatGPT Search cites 15% of the pages it retrieves. The other 85% get pulled into the model’s context window, evaluated, and silently discarded — no visibility, no referral, no trace. If you are doing GEO work and your pages keep getting retrieved but never quoted, you are losing at the second filter, not the first.

    This is the 2026 implementation guide for surviving both filters: getting retrieved by ChatGPT Search, then getting cited once you are there.

    How ChatGPT Search Actually Builds an Answer

    ChatGPT Search runs a three-stage pipeline. Each stage kills most candidates.

    1. Retrieval — ChatGPT Search is powered by Bing’s index for real-time web retrieval. Seer Interactive’s analysis found 87% of SearchGPT citations match Bing’s top results, with the bulk in positions one through ten and a long tail in positions eleven through twenty. AirOps research separately put ChatGPT-to-Bing overlap at 73%. If you are not in Bing’s top 20 for a query, you almost certainly are not in ChatGPT’s candidate set.
    2. Crawlability check — OpenAI’s OAI-SearchBot is the user agent that builds the index used for ChatGPT’s search features. It is separate from GPTBot (training) and ChatGPT-User (browsing). Block OAI-SearchBot in robots.txt and you remove yourself from ChatGPT Search entirely, even if Bing has you ranked.
    3. Citation selection — Of the pages retrieved, AirOps found ChatGPT cites only 15%. The model picks what to quote based on structure, freshness, authority signals, and whether the page directly answers the query.

    Step 1: Verify You Are Indexed by Bing

    Most sites optimized for Google have never logged into Bing Webmaster Tools. Fix that first. Three checks before anything else:

    • site:yourdomain.com in Bing — confirms basic indexing.
    • Bing Webmaster Tools → URL Inspection — confirms the specific pages you want cited are indexed and have no crawl errors.
    • Bing rankings for your target queries — if you are not in the top 20 in Bing, ChatGPT will not see you.

    If pages are missing, submit a sitemap via Bing Webmaster Tools and request URL inspection on any priority page. Bing typically reflects changes within 24–72 hours, faster than Google.

    Step 2: Allow OAI-SearchBot in robots.txt

    The single most-skipped step in GEO work. Add this block to your robots.txt:

    # Allow ChatGPT Search to retrieve and cite this site
User-agent: OAI-SearchBot
Allow: /

# Optional: allow on-demand browsing for ChatGPT users
User-agent: ChatGPT-User
Allow: /

# Optional: block training crawler if you want retrieval without training
User-agent: GPTBot
Disallow: /

    OpenAI publishes these three user agents and treats each independently. You can allow OAI-SearchBot for ChatGPT Search visibility and still disallow GPTBot from using your content for model training. The settings do not conflict. OpenAI’s systems typically recognize robots.txt changes within 24 hours.

    Step 3: Structure Pages for the Citation Filter

    Retrieval is necessary but not sufficient. Once your page is in the candidate set, the model decides whether to quote it. Pages that get quoted share a structural pattern.

    Direct answers in the first 100 words

    ChatGPT cites sources that answer the question fully. Partial answers lose to complete ones. Lead each page with a clean direct-answer paragraph: question implied or stated, answer in the next sentence, supporting detail after. This is the same pattern that wins featured snippets, which is not a coincidence — answer engines and snippet engines reward the same structure.

    JSON-LD schema

    An AirOps study of 548,534 pages found pages with JSON-LD markup posted a 38.5% citation rate versus 32.0% without it. Article, FAQPage, and HowTo schema are the highest-leverage types. Add them.

    Word count: 500–2,000

    Pages between 500 and 2,000 words performed best in the same AirOps study. Pages longer than 5,000 words were cited less often than pages under 500. The mechanism is mechanical: long pages overflow the retrieval context window, and the model defaults to shorter, denser sources it can quote in full.

    Freshness

    Content updated within 30 days received 3.2x more citations than older material. The fix is not faked freshness — it is genuine updates: a new stat, a new case, a corrected claim. Update the date when you update the content, not before.

    Step 4: Build the Authority Layer

    Structure gets you cited once. Authority gets you cited repeatedly. AirOps found sites with over 32,000 referring domains are 3.5x more likely to be cited by ChatGPT than sites with fewer than 200. You do not need 32,000 — you need to be in the upper band of your topical neighborhood.

    ChatGPT’s citation pattern leans heavily on Wikipedia (roughly 48% of top citations in multiple studies) and large news/media properties. The practitioner read on that: ChatGPT favors sources with multi-source third-party validation. Build the kind of citations on the open web that Wikipedia editors accept — peer-reviewed studies, primary sources, named author attribution, transparent methodology.

    Step 5: Track Your Citation Footprint

    You cannot manage what you do not measure. The minimum tracking stack for 2026:

    • Server log monitoring for OAI-SearchBot user agent — confirms OpenAI is actually crawling. If you allowed the bot in robots.txt three weeks ago and there are zero OAI-SearchBot hits in your logs, something is wrong (CDN block, IP firewall, misconfigured allow rule).
    • Manual citation audits — pick 10 priority queries, run them in ChatGPT with the Search toggle on, log which domains get cited. Repeat weekly. A spreadsheet beats no tracking.
    • Bing position tracking — because ChatGPT pulls from the Bing index, Bing rankings are a leading indicator. If your Bing position drops, ChatGPT visibility drops behind it.

    The Practitioner Summary

    Ranking in ChatGPT in 2026 is not mysterious. It is a four-gate funnel: Bing index → OAI-SearchBot crawl access → retrieval into the candidate set → citation selection. Most sites fail at gate one (not indexed in Bing) or gate two (OAI-SearchBot blocked or not addressed). Sites that clear those two gates and write pages that answer the question fully, with schema and a 500–2,000-word range, will land in the 15% that get quoted.

    Treat ChatGPT Search like a separate search engine that happens to share an index with Bing. Optimize for the index. Allow the crawler. Write the page. The rest follows.

  • How to Measure LLM Visibility in 2026: The GA4 + Response-Side Stack

    How to Measure LLM Visibility in 2026: The GA4 + Response-Side Stack

    Traditional analytics platforms can’t see the most important impression you’re making in 2026. When a user asks ChatGPT, Perplexity, Gemini, or Claude about your category, your brand either shows up in the answer or it doesn’t — and your GA4 dashboard has no idea either way. This is the measurement blind spot at the center of generative engine optimization. If you can’t measure LLM visibility, you can’t optimize for it.

    This guide walks through the measurement stack that actually works in 2026: the GA4 channel grouping that catches AI referral traffic, the manual verification protocol that costs nothing, and the dedicated LLM visibility platforms that automate prompt monitoring at scale. By the end, you’ll have a measurement framework you can run starting today.

    Why GA4 alone is not enough

    Standard web analytics measures what happens after the click. LLM visibility is what happens before the click — or instead of one. According to widely cited industry reporting, a large share of AI search sessions end without the user ever clicking through to a source, which means the brand impression inside the AI response is often the only impression you get. GA4 cannot see that impression. It cannot see when ChatGPT recommends you in a comparison. It cannot see when Perplexity cites your article as a source for an answer.

    You still need GA4 — AI referral traffic is real, growing, and converts well — but you need it as one layer of a two-layer stack. Layer one is referral-side measurement, which captures the users who actually click through from AI platforms. Layer two is response-side measurement, which monitors what AI platforms are saying about you whether anyone clicks or not.

    Layer one: catching AI referrals in GA4

    GA4 does not have a built-in “AI” channel. By default, traffic from ChatGPT, Perplexity, Claude, and Gemini gets bucketed into the generic Referral channel, where it disappears next to social and partner sites. The fix is a custom channel group that uses a referrer regex to peel AI traffic out into its own bucket.

    In GA4, go to Admin → Data Settings → Channel Groups, create a custom channel group, and add a new rule above the default Referral rule. Set the conditions to Source matches regex and use a pattern like this:

    chatgpt\.com|openai\.com|perplexity\.ai|claude\.ai|anthropic\.com|gemini\.google\.com|copilot\.microsoft\.com|deepseek\.com|you\.com|meta\.ai|poe\.com

    The order matters. Your AI Traffic rule must sit above the Referral rule in the priority list, or AI traffic will be captured by Referral first and never reach your custom channel. Once the rule is live, you can build Explorations that segment AI traffic by source, page, conversion rate, and engagement time — and compare that segment against organic, direct, and social.

    The referrer attribution gap

    One caveat: not every AI click passes a referrer. ChatGPT’s free tier in particular has been reported to strip referrer headers in many configurations, meaning a meaningful share of ChatGPT traffic shows up as Direct in GA4 rather than as a chatgpt.com referral. This is a known limitation across the industry. Treat your AI referral numbers as a floor, not a ceiling, and use response-side monitoring to fill in the gap.

    Layer two: response-side monitoring

    This is the measurement that traditional SEO never needed. You’re no longer just asking “did anyone visit?” — you’re asking “what is the AI saying about me?” There are two ways to answer that question.

    The manual verification protocol

    The free, no-tool approach is a structured query log. Build a list of 15 to 25 prompts that a buyer in your category would realistically type into an AI assistant. Be specific. “Best CRM for small B2B teams” is a prompt. “What is a CRM” is not — that’s a research query, not a buyer query.

    Once a week, run every prompt through each AI platform you care about — typically ChatGPT, Perplexity, Gemini, and Claude — and record three things per query: whether your brand was mentioned, whether your domain was cited as a source, and what position your brand appeared in if it was named alongside competitors. A simple spreadsheet with prompt, date, platform, mention (yes/no), citation (yes/no), and position is enough to start. Week-over-week deltas on this sheet will tell you whether your GEO and AEO work is moving the needle.

    This is slow and manual but it’s the only method that gives you ground truth. The dedicated platforms below are essentially automating this protocol — running the same kind of prompt log against the same APIs on a daily schedule. If you’re under $1,000/month in marketing spend, run it manually. If you’re past that, automate it.

    Dedicated LLM visibility platforms

    A new category of tools emerged in 2025 and matured in 2026 specifically to monitor LLM responses. They all do roughly the same thing — run your target prompts daily across multiple AI engines, score visibility, track which sources the AIs cite, and surface competitor gaps — but they segment by price point.

    At the budget end, Otterly.AI offers monitoring plans starting around $29/month, with a Share of AI Voice metric and time-to-first-data of under ten minutes after signup. It’s the simplest entry point for teams that just want a citation-frequency dashboard. In the mid-market, Peec AI starts around €89/month and emphasizes multilingual coverage and actionable recommendations — it doesn’t just tell you you’re invisible, it suggests what to change. At the enterprise tier, Profound starts around $499/month and adds Prompt Volumes, which estimates real AI search demand by topic with demographic breakdowns. SOC 2 compliance and dedicated onboarding generally start at the $1,000+ enterprise tiers across this category.

    Other platforms in active use this year include Semrush’s AI Toolkit, SE Ranking’s SE Visible, Goodie AI, Rankscale, Nightwatch, AirOps, and Searchable. The category is moving fast — pricing and features change quarterly — so verify the current state of any platform before committing.

    The six KPIs to track

    Whatever measurement stack you use, the same handful of metrics will tell you whether GEO is working. Organize them into leading and lagging indicators:

    Leading indicators (response-side, change first):

    • Mention Rate — the percentage of monitored prompts where AI responses mention your brand name. This is the broadest signal.
    • Citation Rate — the percentage of monitored prompts where your domain is cited as a source, not just named. Citation is stronger than mention because it implies the AI is treating your content as authoritative.
    • Position — when your brand is named alongside competitors, where in the list does it appear. First-named brands get disproportionate attention.

    Lagging indicators (referral and revenue-side, change later):

    • AI Referral Sessions — total sessions from your AI Traffic channel group in GA4.
    • AI Referral Engagement — engagement rate and average engagement time for the AI segment, compared to organic. Strong AI referral traffic typically engages longer because the user arrived with intent already framed by the AI.
    • AI-Influenced Conversions — conversions where AI was part of the attribution path, even if not the last touch.

    Tier-one metrics move first because content changes affect what AIs say within days to weeks. Tier-two metrics lag because they require enough traffic to be statistically meaningful, which can take a quarter or more to develop.

    The minimum viable setup

    If you do nothing else this week, do these three things:

    1. Add the AI Traffic channel group to GA4 using the regex above and move it above Referral in priority.
    2. Build a 15-prompt spreadsheet of buyer-intent queries for your category and run them once across ChatGPT, Perplexity, Gemini, and Claude. Record mention, citation, and position.
    3. Set a calendar reminder to repeat step two every Friday for four weeks. After four weeks you’ll have a real trendline.

    That setup costs nothing and produces the measurement layer that lets you tell whether your GEO, AEO, and LLMs.txt work is actually compounding — or whether you’re guessing. Once the trendline is stable, evaluate whether automating with Otterly, Peec, or Profound is worth the spend. For most operators, the manual protocol gets you 80% of the insight at 0% of the budget.

    Frequently Asked Questions

    What is LLM visibility?

    LLM visibility is the measurement of how often, and how prominently, a brand or website appears in responses generated by large language models like ChatGPT, Perplexity, Gemini, and Claude. It is the response-side counterpart to traditional search ranking — instead of measuring where you appear in a results page, you’re measuring whether AI assistants mention or cite you when answering questions in your category.

    Can GA4 track AI traffic from ChatGPT and Perplexity?

    GA4 can track AI referral clicks if you create a custom channel group with a referrer regex matching AI domains and place it above the default Referral rule. It cannot track impressions inside AI responses where the user doesn’t click through, and ChatGPT’s free tier often strips referrers entirely, so a portion of AI traffic still lands in Direct. Treat GA4 numbers as a floor.

    What is the difference between mention rate and citation rate?

    Mention rate measures the percentage of monitored AI prompts where your brand name appears anywhere in the response. Citation rate measures the percentage where your specific domain or URL is referenced as a source. Citation is a stronger signal because it indicates the AI is treating your content as authoritative, not just naming you in passing.

    Which LLM visibility tool should I use in 2026?

    For budget-conscious teams, Otterly.AI starts around $29/month and gets you to first data in minutes. For mid-market needs with multilingual coverage and recommendations, Peec AI starts around €89/month. For enterprise teams that need prompt-volume demand data and SOC 2 compliance, Profound starts around $499/month. Verify current pricing before purchasing — the category moves quickly.

    How often should I check my LLM visibility?

    For manual tracking, weekly is the right cadence — frequent enough to catch movement, infrequent enough to avoid noise. Dedicated platforms typically run automated checks daily and let you review weekly. Don’t expect day-to-day stability; AI responses have inherent variance, so look at week-over-week and month-over-month trends rather than single data points.

  • OpenAI’s Everything App: Why Behavior Is a Better Moat Than Infrastructure

    OpenAI’s Everything App: Why Behavior Is a Better Moat Than Infrastructure

    Microsoft has LinkedIn and enterprise distribution. Google has the native stack. Notion has the database architecture. OpenAI has something none of them have: 500 million people who already open ChatGPT when they want to get something done. That’s not a product advantage. That’s a behavior advantage. And behavior is the hardest moat to breach.

    Where OpenAI Sits in This Series This is the fifth piece examining who builds the everything app. We’ve covered Microsoft, Google, Notion, and the everything database frame. OpenAI’s path is the most unusual: they’re not building from infrastructure up. They’re building from user behavior down.

    The Model Reality First — Get This Right

    Before the strategy discussion, the model facts — because the landscape shifted significantly in early 2026 and the marketing doesn’t always match what’s actually deployed.

    As of mid-2026, OpenAI’s current flagship is GPT-5.5, which powers ChatGPT Enterprise (unlimited messages) and is the reasoning backbone of the unified super-assistant experience. The o-series — o3 and o4-mini — are the thinking models, trained to reason longer before responding. o3 is the deep-reasoning flagship; o4-mini is the high-throughput option that outperforms o3-mini on non-STEM tasks and data science, with higher usage limits.

    Notably, GPT-4o, GPT-4.1, and GPT-4.1 mini were retired from ChatGPT as of February 13, 2026. Enterprise customers retained GPT-4o access until April 3, 2026. If you’re referencing these models in your stack — in tutorials, in documentation, in integrations — those references are now stale. The current tier is GPT-5.5 Instant / Thinking and the o3/o4-mini reasoning models.

    One more significant infrastructure move: the Assistants API is being deprecated, with sunset on August 26, 2026. OpenAI is replacing it with the Responses API — a new primitive that combines Chat Completions simplicity with Assistants-style tool use, supporting web search, file search, and computer use natively. If you built on the Assistants API, migration planning should already be underway.

    OpenAI’s Everything App Bet: Behavior Over Infrastructure

    Microsoft’s everything app bet is infrastructure — they own the OS, the enterprise software stack, and a professional network. Google’s bet is native stack — they own search, email, calendar, and mobile. Both are building from the platform up.

    OpenAI is doing the opposite. They’re starting from where people already go to get things done, and expanding outward from that behavioral beachhead. ChatGPT’s 500 million monthly users don’t use it because it owns their email. They use it because it’s the fastest path from question to answer, from idea to draft, from problem to solution.

    The everything app doesn’t have to own your data. It just has to be the place you go first. OpenAI is betting that if they can make ChatGPT good enough at enough things — and fast enough at integrating with the tools you already use — the behavioral habit becomes the moat. You stop going to Google first. You stop opening a new app. You open ChatGPT.

    The Pieces OpenAI Has Assembled

    The consolidation has been quieter than Microsoft’s marketing machine or Google’s Cloud Next announcements, but the pieces are substantial.

    Operator — the computer-using agent — launched as a research preview in early 2025 and integrated fully into ChatGPT by mid-year. It browses, clicks, fills forms, and manages logins autonomously. GPT-5.5’s score on OSWorld-Verified — the standard benchmark for computer-use agents — is 78.7%. The human baseline on the same benchmark is 72.4%. That’s not a lab result. That’s production-grade desktop and browser automation beating human performance on standardized tasks.

    Projects and Memory — launched through 2025 — give ChatGPT persistent context across sessions. Projects (November 2025) let you organize work by context. Project Memory (August 2025) lets ChatGPT learn your preferences, communication style, and working patterns over time. This is the foundational layer for the everything app: an AI that knows you, not just your current prompt.

    Workspace Agents for Enterprise — launched April 22, 2026 — let enterprise teams create, share, and manage AI agents for workflow automation. Powered by Codex, these agents handle reporting, coding, and messaging tasks autonomously. This is OpenAI’s direct enterprise play, competing with Microsoft’s Agent 365 and Google’s Workspace Studio on their home turf.

    Sora 2 — released September 2025 — moved AI video from novelty to production-grade. It’s available both as a standalone app and deeply integrated within ChatGPT. Video generation, image creation, voice, code execution, deep research, file analysis — all inside one interface. The surface area of what ChatGPT can do has expanded faster than most people have tracked.

    The Apps SDK and MCP support — announced in 2025 — let developers build UIs alongside MCP servers, defining both logic and interactive interface of applications that run inside ChatGPT. OpenAI is building a developer ecosystem where third-party tools surface inside ChatGPT natively, not as links out to other apps.

    The Honest Strategic Weakness: OpenAI Doesn’t Own the Data Layer

    Here’s the structural problem with OpenAI’s everything-app path that doesn’t get enough attention.

    Microsoft owns the calendar data, the email data, the document data, the professional network data. Google owns the same stack natively. Notion owns the database architecture where your operational data lives. OpenAI owns a conversation history and whatever files you’ve uploaded to Projects.

    That’s a meaningful gap. When you ask Microsoft Copilot “what happened in last week’s client meeting?” it can actually answer — because it has the calendar event, the Teams recording transcript, and the follow-up email thread. When you ask ChatGPT the same question, the answer is only as good as what you’ve explicitly provided.

    OpenAI’s answer to this is Operator and the connector ecosystem — let ChatGPT reach into your existing tools and pull the data it needs. That works, but it creates a dependency chain that Microsoft and Google don’t have. Every integration is a point of failure. Every API change is a breakage risk. Every permission prompt is friction that erodes the behavioral habit.

    The Responses API — replacing the Assistants API in August 2026 — is designed to close some of this gap with native web search, file search, and computer use built in. But native search is not the same as owning the inbox. And computer use, for all its benchmark performance, is still slower and less reliable than a dedicated integration.

    Where OpenAI Wins: The Consumer and Creator Layer

    The enterprise everything-app race may go to Microsoft or Google by default — too much infrastructure, too many IT relationships, too much compliance architecture for a newcomer to overcome in 18 months.

    But the consumer and creator layer is wide open. And that’s where OpenAI’s behavioral moat matters most.

    For freelancers, solopreneurs, content creators, small agencies, and knowledge workers who aren’t tied to an enterprise IT environment, ChatGPT is already the everything app. It drafts your emails, edits your copy, analyzes your data, generates your images, browses for research, and runs your automations. The question isn’t whether they’ll adopt it — they already have. The question is whether OpenAI deepens that relationship fast enough to make switching costly before Microsoft and Google catch up on the consumer side.

    Memory is the weapon here. The longer a user runs their work through ChatGPT Projects with memory enabled, the more context OpenAI accumulates about how that person thinks, works, and communicates. That context is genuinely hard to transfer to a competing platform. It’s not data in a database — it’s learned behavioral preference. The switching cost compounds with every session.

    The Operator Economy: OpenAI’s Wildcard

    The most underrated piece of OpenAI’s everything-app strategy isn’t ChatGPT itself — it’s the operator ecosystem.

    An “operator” in OpenAI’s framework is any business that deploys ChatGPT capabilities inside their own product. Every company building on the OpenAI API — embedding ChatGPT into their CRM, their help desk, their e-commerce platform, their internal tools — is an operator. Every one of those deployments is a surface where OpenAI’s models become the intelligence layer of someone else’s everything app.

    Microsoft has Copilot. Google has Gemini. But neither of them has the sheer number of third-party applications already running on their models that OpenAI has accumulated. The operator ecosystem means OpenAI doesn’t have to build every surface themselves. They just have to remain the model that operators trust most — and as long as GPT-5.5 and the o-series stay at the frontier of capability, that trust is relatively durable.

    The Workspace Agents launch, combined with the Apps SDK and MCP support, is OpenAI formalizing this operator model for enterprise. They’re saying: we won’t replace your enterprise software stack. We’ll become the reasoning layer that sits across all of it.

    What This Means for Your Stack Right Now

    If you’re building on OpenAI’s API or running workflows through ChatGPT, three immediate action items:

    • Audit your Assistants API usage now. August 26, 2026 sunset is closer than it looks. The Responses API migration path is documented — start the evaluation before you’re forced into a rushed migration.
    • Enable Projects and Memory for your team’s ChatGPT accounts. The compounding advantage of memory only builds if you start using it. Teams that have six months of Project memory by Q4 2026 will have a materially different AI experience than teams starting fresh.
    • Think about where ChatGPT sits relative to your Notion database. OpenAI’s operator model and MCP support mean ChatGPT can connect to your Notion everything database via the Notion Public API. The everything database frame doesn’t require you to choose between Notion and ChatGPT — it lets you use both, with Notion as the structured data layer and ChatGPT as the reasoning and action surface on top of it.

    The everything app race isn’t over. OpenAI has the behavior moat, the operator ecosystem, and the fastest-moving model roadmap of any company in this field. What they don’t have is the data infrastructure that Microsoft and Google own by default. How they close that gap — through connectors, through Operator’s computer-use capabilities, through the Responses API — will determine whether ChatGPT becomes the everything app or the everything layer sitting on top of someone else’s everything app.

    Both outcomes are valuable. Only one of them wins the race.

    Frequently Asked Questions

    What is OpenAI’s current flagship model in 2026?

    As of mid-2026, GPT-5.5 is OpenAI’s primary model powering ChatGPT Enterprise. The o3 and o4-mini models handle deep reasoning tasks. GPT-4o, GPT-4.1, and GPT-4.1 mini were retired from ChatGPT on February 13, 2026. The Assistants API sunsets August 26, 2026, being replaced by the Responses API.

    What is the OpenAI Responses API?

    The Responses API is OpenAI’s replacement for the Assistants API (sunset August 26, 2026). It combines Chat Completions simplicity with Assistants-style tool use, supporting built-in web search, file search, and computer use. It’s the new primitive for building agents on OpenAI’s platform.

    What are OpenAI Workspace Agents?

    Launched April 22, 2026, Workspace Agents let enterprise teams create, share, and manage AI agents for workflow automation inside ChatGPT. Powered by Codex, they handle reporting, coding, and messaging tasks autonomously — OpenAI’s direct enterprise play against Microsoft Agent 365 and Google Workspace Studio.

    How does ChatGPT Operator work?

    Operator is OpenAI’s computer-using agent — it browses, clicks, fills forms, and manages logins autonomously. GPT-5.5 scores 78.7% on the OSWorld-Verified benchmark for computer-use tasks, above the 72.4% human baseline. It’s integrated directly into the ChatGPT interface for eligible plans.

    Can ChatGPT connect to a Notion database?

    Yes. Via the Notion Public API and OpenAI’s MCP support and connector ecosystem, ChatGPT can read from and interact with Notion databases. This makes the “everything database” architecture viable with OpenAI as the reasoning surface — Notion holds the structured data, ChatGPT reasons and acts on it.

  • Notion AI vs ChatGPT for Daily Knowledge Work

    Notion AI vs ChatGPT for Daily Knowledge Work

    Notion AI vs ChatGPT for Daily Knowledge Work

    The 60-second version

    This isn’t a winner-take-all comparison. Notion AI and ChatGPT are different categories of tool that get incorrectly compared because they both use the word “AI.” Notion AI knows your workspace. ChatGPT knows the open web. The right operator stack uses both. The question isn’t which to pick; it’s how to route work between them.

    When Notion AI wins

    • Anything that requires knowing your specific content
    • Synthesis across your databases, pages, and connected sources
    • Document work where the doc lives in your workspace
    • Recurring tasks that benefit from agent automation
    • Mobile use where seamless integration matters

    When ChatGPT wins

    • Open-web research
    • Brainstorming on topics outside your workspace
    • Code generation (currently ChatGPT and Claude lead here)
    • General-purpose Q&A
    • Conversational exploration of ideas

    How they stack

    The pattern that works for most operators: ChatGPT for “thinking out loud” and external research; Notion AI for everything that touches your actual work. Use ChatGPT to draft an idea, then move the polished version into Notion where it joins your actual workspace and Notion AI takes over.

    What ChatGPT does that Notion doesn’t (yet)

    • Image generation
    • Voice conversations as a primary mode
    • Custom GPT marketplace
    • Data analysis on uploaded files at scale

    What Notion AI does that ChatGPT doesn’t

    • Persistent context across your workspace
    • Database manipulation and Autofill
    • Custom Agents running on schedules
    • Workers for code execution
    • Native integration with Slack, Mail, Calendar at the workspace level

    The pricing reality

    ChatGPT Plus is $20/month per user. Notion Business is $20/user/month annually with separate Custom Agent credits ($10/1000) starting May 4. For a team using both heavily, the combined cost is meaningful.

    Where comparisons go wrong

    1. Asking “which is smarter.” They use overlapping models. Raw model intelligence is similar; what differs is integration depth.
    2. Trying to pick one. The right answer is usually both, with clear use-case routing.
    3. Treating ChatGPT memory as equivalent to Notion’s workspace context. ChatGPT memory is conversational. Notion’s context is structured workspace data. Different categories.

    What to read next

    Notion AI vs Claude Projects, Notion AI vs Gemini, Editorial Surface Area, Auto Model Selection.

  • Why Your GA4 Engagement Rate Lies to You — and What AI Referral Data Reveals About Your Real Audience

    Why Your GA4 Engagement Rate Lies to You — and What AI Referral Data Reveals About Your Real Audience

    Your GA4 engagement rate is one number. But it is not one audience. It is three audiences — and they behave so differently from each other that the aggregate number actively misleads you about how your content is performing.

    Here is what most GA4 users see: a site-wide engagement rate of 35%, an average session duration of 90 seconds, and a top channel list led by Organic Search. What most GA4 users miss: within that same 35% number, three AI platforms are sending traffic with engagement rates of 21%, 46%, and 64% respectively — from the exact same pages, to users with completely different intent profiles.

    The AI Referral Split Nobody Is Looking At

    ChatGPT, Claude, and Copilot all send referral traffic to content sites. But they do not send the same user. ChatGPT users arrive, scan for a quick answer, and leave in under 30 seconds — engagement rate around 21%, well below the organic search average. Claude users arrive with research intent, read deeply, and stay for 3-4 minutes — engagement rate above 64%. Copilot users are somewhere between, arriving in planning mode, spending 1-2 minutes on civic and services content.

    If you blend these three into your site-wide engagement rate, you get a number that does not represent any of your actual users. You get a mathematical average of behaviors that have nothing in common.

    Why Your Engagement Rate Lies

    The problem is not your content. The problem is that engagement rate without source segmentation is noise. A 35% site-wide engagement rate could mean you have excellent content reaching the wrong distribution channels. It could mean you have mediocre content propped up by one high-engagement source. It could mean your AI referral traffic is dramatically outperforming your social traffic and you have no idea.

    The only way to know which is true is to break the number open by source and look at what each channel is actually delivering in terms of engaged session quality — not just volume.

    The Four-Question Audit

    Before you make any content or distribution decisions based on your GA4 engagement rate, ask these four questions.

    Which channel sends the most engaged users — not the most users? The answer is almost never the channel driving the highest session count. In most content sites we have audited, the highest-engagement channel is sending between 8 and 40 sessions per month, not 400.

    What is the engagement rate for each AI referral source individually? Blending ChatGPT and Claude traffic treats them as equivalent. They are not. One is a fact-checking audience. The other is a research audience. The content structure that serves one actively fails the other.

    Which pages produce satisfied exits versus abandoned exits? A 90% exit rate with a 3-minute duration is a success. A 90% exit rate with a 4-second duration is a dead end. Engagement rate alone does not tell you which you have.

    Is your engagement rate rising or falling week-over-week from AI sources? AI referral traffic is growing on most content sites in 2026. If yours is flat or declining, you are losing ground in a channel that is becoming structurally important.

    What This Reveals About Your Real Audience

    When you segment your GA4 engagement rate by source and run the AI referral breakdown specifically, a picture emerges that the aggregate number completely hides. Your real audience — the people actually reading and acting on your content — is smaller and more specific than your total traffic suggests. It is concentrated in a few sources, a few content types, and in the case of Claude traffic specifically, a few geographic clusters that reflect the academic and professional demographics of that user base.

    This is not a problem. It is a targeting signal. It tells you where to invest content development effort and which audience to write for on every new piece.

    The Methodology Behind This Analysis

    The behavioral profiles in this article come from five live sessions using Claude-in-Chrome to interrogate Google’s Analytics Advisor inside GA4 on a real property. The query architecture — the specific sequence of questions and the capture protocol — is packaged as the Books for Bots: GA4 AI Referral Audit Kit.

    It runs in four sessions, requires no SQL, no BigQuery access, and no data analyst. You need Claude-in-Chrome, Editor access to a GA4 property with Analytics Advisor enabled, and approximately 90 minutes. The output is a complete per-AI behavioral profile of your traffic and a content variant framework for acting on it.

    Learn more about the GA4 AI Referral Audit Kit →

  • Books for Bots: What Happens When You Let Claude Interrogate Your GA4 Data

    Books for Bots: What Happens When You Let Claude Interrogate Your GA4 Data

    For the past several weeks I have been running a live experiment on helpnewyork.com: using Claude-in-Chrome to interrogate Google’s Analytics Advisor inside GA4, session by session, until I had a complete behavioral profile of every AI platform sending traffic to the site.

    What came out of it is not what I expected. I expected traffic data. I got a content strategy.

    The Setup

    Claude-in-Chrome is Anthropic’s browser extension that lets Claude operate directly inside your browser — reading pages, clicking elements, filling inputs, capturing output. Analytics Advisor is Google’s Gemini-powered chat interface built into GA4, available to English-language accounts since December 2025. It answers natural language questions about your property data with charts, tables, and narrative interpretation.

    The combination is unusual. You are using one AI (Claude) to systematically interrogate another AI (Gemini) about your site’s data, then synthesizing what comes back into strategy. The token budget for the heavy data reasoning stays inside Google’s infrastructure. Claude handles the query architecture, the capture protocol, and the synthesis.

    I ran four structured sessions across two sittings, using a specific sequence of queries built to extract progressively deeper signal. Session 1 established baseline traffic. Session 2 closed gaps and confirmed AI referral data existed. Session 3 was the AI deep dive. Session 4 was velocity and geography.

    What the Data Showed

    Three AI platforms were sending meaningful traffic to helpnewyork.com during the 28-day window: ChatGPT, Claude, and Copilot. The behavioral profiles were so different from each other that treating them as a single “AI traffic” segment would have produced wrong conclusions.

    Claude.ai traffic showed a 64% engagement rate and an average session duration of over 3 minutes. The dominant landing page was an NYC Summer Internships guide, accounting for over 60% of all Claude sessions. Geographic concentration was academic: Ithaca (Cornell), State College (Penn State), Washington DC. The users arriving from Claude were reading to act — they needed specific information, they found it, they stayed.

    ChatGPT traffic showed a 21% engagement rate and an average session of 24 seconds. The top landing page was a cherry blossom guide. The users were fact-grabbing: they asked ChatGPT where to see cherry blossoms in New York, got a citation, clicked through, confirmed the location, and left. The content served its purpose in under half a minute.

    Copilot traffic was between the two: 46% engagement, roughly 2-minute sessions, desktop-heavy, concentrated in New York’s suburbs. The top pages were civic services — SNAP benefits, tenant rights, transit discounts. These users were in planning mode, researching before they decided or applied.

    The Finding That Reframes GEO

    The cross-AI page overlap query was the most important one in the entire four-session arc. I asked Analytics Advisor which pages appeared in the top landing pages for more than one AI source. Only one real content page appeared in all three: the cherry blossom guide.

    The obvious interpretation is that the cherry blossom guide was “AI-optimized.” The actual interpretation, once you look at the full traffic breakdown, is the opposite. Bing drove 59 sessions to that page. Yahoo drove 16 at 75% engagement and a 3-minute 46-second average session. DuckDuckGo drove 35. The combined AI traffic to that page was 32 sessions — 17% of total. The AI platforms were citing it because traditional search engines had already validated it as the highest-quality answer in the index.

    AI citations are downstream of search quality, not upstream. The path to getting cited by ChatGPT, Claude, and Copilot is not to optimize for AI retrieval patterns. It is to build pages that win on Bing and Yahoo with enough depth that AI models treat them as authoritative sources. The GEO play is a traditional SEO play with better content.

    The Content Strategy That Follows

    Once you have the per-AI behavioral profiles, you have a content variant framework. The same article can be written in three structural architectures, each tuned to how one AI model retrieves and presents information.

    The Claude variant is dense and process-oriented. Headers, eligibility criteria, numbered steps, official program names. Built for the student or researcher who arrived with a specific question and needs a complete answer they can act on.

    The ChatGPT variant is a scannable list. Named items, one specific detail per item, direct answer in the first two sentences. Built for the user who will spend 24 seconds on the page and needs the answer immediately or they’re gone.

    The Copilot variant is comparison and planning framing. What to know before you go, Option A versus Option B, cost context, logistics. Built for the desktop user doing research before they make a decision.

    The core article is the same. The architecture is different. The AI that cites you depends on which structure you used.

    The Methodology Is the Product

    The query sequence I developed across these four sessions is a repeatable extraction methodology. It works on any GA4 property with Analytics Advisor enabled. The intelligence it produces — per-AI audience profiles, geographic signals, velocity trends, cross-AI content overlap — is not available through DataForSEO, SpyFu, or GSC. It requires Gemini’s reasoning layer operating on top of your property data, orchestrated by a structured query architecture.

    I have packaged the complete methodology as a downloadable kit: the full query architecture across all four sessions, the capture protocol, the content variant framework, and the flags to escalate before your next content sprint. It is called Books for Bots: GA4 AI Referral Audit Kit.

    The free version covers Session 3 alone — the AI deep dive queries that surface your ChatGPT, Claude, and Copilot traffic split. That alone will show you something most site owners have never seen: which AI is sending them traffic, to which pages, and how engaged those users actually are.

    The full kit covers all four sessions and includes the content variant framework that translates the behavioral data into a writing system.

    Both are available at tygartmedia.com. What you do with the data after that is yours.

  • Claude Sent Us 63 Readers Last Month: The First Measurable AI-Referral Channel for Publishers

    Claude Sent Us 63 Readers Last Month: The First Measurable AI-Referral Channel for Publishers

    Short version: In the last 29 days, Claude, ChatGPT, Perplexity, Microsoft Copilot, Gemini, NotebookLM, and Kagi collectively sent at least 94 new readers to tygartmedia.com — a site whose #1 content vertical is explaining Claude. AI assistants are now our #4 traffic source, ahead of Facebook, ahead of LinkedIn, ahead of every search engine except Google and Bing. The product is citing the publication that covers the product. That’s the loop. Here is what it looks like when you can actually measure it.

    The finding that made me stop scrolling

    I built a Claude-powered browser agent to poke around our GA4 account and surface “interesting stuff” a human analyst would miss. One of the first things it flagged was our Source/Medium report. Here is the top of the list, unedited:

    RankSource / MediumNew Users (29 days)Notes
    1(direct) / (none)738Mystery bucket
    2google / organic289Standard Google SEO
    3bing / organic701m 20s average session — high intent
    4claude.ai / referral63Claude itself
    5m.facebook.com43Mostly 4-second bounces
    6duckduckgo / organic411m 02s average
    13chatgpt.com / referral9ChatGPT
    15perplexity.ai / referral5Perplexity
    21copilot.com3Microsoft Copilot
    24gemini.google.com2Google Gemini
    28notebooklm.google.com1Google NotebookLM
    35kagi.com1Kagi AI results

    Add up everything with an AI-assistant referrer and the combined count is at least 94 new users in 29 days — roughly 6.7% of all new users on the site. Claude alone, at 63 referred users, is our #4 traffic source. It is ahead of Facebook. It is ahead of LinkedIn. It is ahead of every search engine except Google and Bing. And we have been cited, at least once, by every major AI surface in the English-speaking internet: Claude, ChatGPT, Perplexity, Microsoft Copilot, Gemini, NotebookLM, and Kagi.

    Why this is different from “we show up in Google”

    Generative Engine Optimization (GEO) is the practice of structuring content so that large language models cite it as a source inside their answers. It is the younger, messier cousin of SEO. Most publishers cannot yet prove it is working. The feedback loop is long, the data is hidden inside a chat window, and the traffic that does leak through often lands in a “(direct)” bucket with no attribution at all.

    We can see ours. GA4, for reasons that are probably accidental, already records claude.ai, chatgpt.com, perplexity.ai, copilot.com, gemini.google.com, notebooklm.google.com, and kagi.com as discrete referral sources when a user clicks a citation link. That means AI-assistant traffic is measurable as a first-class channel right now, today, with the free version of Google Analytics, on any site that happens to get cited.

    The poetic layer of what we are looking at: Claude is the top AI referrer to a website whose #1 content vertical is explaining Claude. The product is sending readers to the publication that covers the product. If that is not a GEO moat, I do not know what one looks like.

    These are not bounced visitors. They are readers.

    The single biggest worry with any new traffic source is that it might be garbage — bots, previews, accidental clicks. The engagement data says the opposite. Users arriving from claude.ai spend 23 seconds on average and produce 0.56 engaged sessions per user. ChatGPT referrals average 21 seconds and 0.44 engaged sessions per user. For context, the site-wide average engagement time is dragged down hard by in-app social browsers; the Facebook mobile webview, for example, sits at about 14 seconds with 4-second bounces.

    People arriving from an AI assistant are not scrolling past. They clicked the citation because the AI told them this was the primary source, and when they got here they read. That is a qualitatively different kind of traffic than Facebook or a random Google search. These are the highest-intent non-search users we have.

    The secondary finding: Seattle is reading for three minutes

    The same GA4 pass surfaced a city-level pattern we were not expecting. Seattle readers — 61 of them in 29 days — spent an average of 3 minutes and 6 seconds on site at a 61.3% engagement rate. The site-wide average session is roughly 40 seconds. Seattle readers are spending about 4–5x longer on the page than the typical visitor, at nearly twice the engagement rate.

    CityActive UsersEngagement RateAverage Time
    Seattle6161.3%3m 06s
    The Dalles, OR310%1s
    Shelton, WA2627.6%15s
    Des Moines2437.5%10s
    Beijing316.5%0s
    Singapore2821.4%5s

    A few things jump out. The Dalles, Oregon at 31 users / 0% engagement / 1 second is almost certainly Google’s data center there returning preview requests — ignore it. Shelton, Washington is a real Mason County hyperlocal beachhead; 26 actual humans in our home county in 29 days is a legitimate foothold for the local desk. Beijing at 31 users / 0 seconds has the classic signature of cloud-hosted scrapers. And Seattle at 3 minutes is the single most valuable city in our data and it is not close.

    The browser split confirms an unusually technical audience

    BrowserUsersEngagement Rate
    Chrome850 (60%)31.3%
    Safari232 (16%)32.7%
    Edge99 (7%)62.3%
    Firefox33 (2.3%)60.5%

    Edge at 62.3% engagement and Firefox at 60.5% engagement are not normal consumer numbers. A typical general-interest site sees those two browsers hovering in the 5–15% range. Microsoft Edge is the default on corporate-managed Windows machines. Firefox is the dev-preferred privacy browser. The combination of high Edge engagement, high Firefox engagement, and a Claude-heavy referral list all point at the same audience: developers and technical professionals at real companies, reading on managed workstations.

    How to measure AI-assistant referrals in your own GA4

    If you publish anything technical and want to see your own version of this number, the fastest path is a custom GA4 exploration with one segment. Open GA4 → Explore → Free Form. Add a segment with this condition:

    Session source contains one of:
  claude.ai
  chatgpt.com
  perplexity.ai
  perplexity
  copilot.com
  gemini.google.com
  notebooklm.google.com
  kagi.com
  you.com
  phind.com

    Break it down by landing page, engagement rate, and average engagement time. That is your AI-Referral dashboard. Watch it weekly. A non-trivial number of sites will discover they already have measurable AI traffic and never bothered to look.

    Frequently asked questions

    What is a GEO referral?

    A GEO referral, or AI-assistant referral, is a visit to your site from a user who clicked a citation link inside an answer generated by a large language model such as Claude, ChatGPT, Perplexity, Microsoft Copilot, Gemini, NotebookLM, or Kagi. In Google Analytics 4 these visits appear as referral traffic from the assistant’s domain — for example claude.ai / referral or chatgpt.com / referral.

    How many AI-referred users did tygartmedia.com receive in 29 days?

    At least 94 new users across seven distinct AI assistants: 63 from Claude, 14 from ChatGPT (9 attributed + 5 unassigned), 10 from Perplexity (5 attributed + 5 unassigned), 3 from Microsoft Copilot, 2 from Gemini, 1 from NotebookLM, and 1 from Kagi. That is roughly 6.7% of all new users on the site for the period.

    Are AI-assistant referrals real readers or bots?

    Real readers. Average engagement time from claude.ai is 23 seconds and from chatgpt.com is 21 seconds, with engagement rates of 0.56 and 0.44 engaged sessions per user respectively. Those numbers are qualitatively higher than in-app social browser traffic (Facebook mobile webview averages about 14 seconds) and indicate a deliberate click-through from an AI citation, not a scraper.

    Can any publisher measure AI-assistant referrals in GA4?

    Yes. GA4 records visits from claude.ai, chatgpt.com, perplexity.ai, copilot.com, gemini.google.com, notebooklm.google.com, and kagi.com as discrete referral sources by default. Build a Free Form exploration with a segment that filters Session source on those domains and you will see the channel immediately if it exists for your site.

    What is GEO in marketing?

    GEO stands for Generative Engine Optimization. It is the practice of structuring web content, schema markup, and publishing signals so that large language models cite the content as a source inside AI-generated answers. GEO is to AI assistants what SEO is to search engines — the discipline of being the answer the machine hands to the reader.

    The loop, and why it matters

    The most interesting thing about this data is not the traffic. It is the feedback structure. Tygart Media publishes explainers about Claude. Claude crawls and cites those explainers. Readers click through from Claude’s answer back to tygartmedia.com. We publish more. Claude cites more. The site becomes, in effect, training data and a recommended source for the next iteration of the product it covers. That is the recursive loop that makes AI-native publishing a different business than search-era publishing.

    I do not think every site can build this loop. It requires a narrow, technically-defensible topic — something an AI assistant would rather cite than paraphrase — and the patience to publish at a cadence LLMs reward. What I do think is that any publisher can check, today, whether the loop has quietly started forming underneath them. Most have not bothered. This post is partly a flex and partly an invitation: go look.

    What happens next at Tygart Media

    Three things. We are standing up a permanent AI-Referral channel in our GA4 so the number can be watched weekly instead of rediscovered quarterly. We are writing the playbook — the one this post hints at — for publishers who want to do the same. And we are building the browser agent that found this in the first place into a repeatable audit any publisher can run against their own GA4 in an afternoon. If that last one sounds useful, the newsletter is the place to follow along.

    Claude sent us 63 readers last month. It will send more next month. We will be counting.

  • Claude, ChatGPT, and Perplexity Cite Totally Different Pages: The Per-Model AI Citation Playbook

    Claude, ChatGPT, and Perplexity Cite Totally Different Pages: The Per-Model AI Citation Playbook

    Part 2 of 2. In the first post I showed that Claude, ChatGPT, Perplexity, Copilot, Gemini, NotebookLM, and Kagi collectively sent tygartmedia.com at least 94 new readers in 29 days — and that Claude alone is our #4 traffic source. That is the headline. What follows is the interesting part: when you filter the landing-page report one AI model at a time, the three major assistants cite completely different kinds of pages, and the pattern is actionable.

    Claude cites a small number of pages, a lot of times

    Claude.ai sent 79 sessions across 63 users to 16 distinct pages. Two pages ate more than half of it:

    #PageSessions% of Claude trafficAvg Time
    1/claude-student-discount2227.9%35s
    2/anthropic-console2126.6%11s
    3(not set)1316.5%5s
    4/claude-edu45.1%6s
    5/claude-pro-vs-chatgpt-plus45.1%7s
    6/claude-code-on-vertex-ai-gcp33.8%3s
    7/claude-desktop22.5%40s
    8/how-to-install-claude-code22.5%2s
    9/claude-4-deprecation11.3%1m 07s
    10/claude-managed-agents-pricing-cost-analysis11.3%1m 38s

    The two biggest pages, /claude-student-discount and /anthropic-console, are 54.5% of all Claude-referred traffic to the site. Those are extremely specific query shapes — “how do students get Claude Pro free” and “how do I access the Anthropic Console” — and Claude has apparently decided our pages are the canonical answer for both.

    The engagement twist is worth staring at. The two biggest Claude-referred pages have the worst time-on-page: 35 seconds and 11 seconds. The two pages that got a single Claude visit each — /claude-managed-agents-pricing-cost-analysis and /claude-4-deprecation — got 1 minute 38 seconds and 1 minute 7 seconds of real read time. The pattern is clean. When Claude can extract the answer directly into its chat window, users click through briefly to verify and leave. When the answer is deeper than Claude can summarize, readers stay to actually read. Both behaviors are valuable and both are measurable.

    ChatGPT cites broadly, favors “X vs Y” content, and (oddly) sends geographic traffic

    ChatGPT’s footprint is shaped differently. 16 sessions across 14 users to 13 distinct pages — almost every page received exactly one visit, which is the signature of a model citing a wide range of sources once each rather than reaching for a favorite.

    PageSessionsAvg Time
    /claude-student-discount315s
    /claude-computer-use-tutorial12m 07s
    /grok-vs-claude115s
    /opus-4-7-vs-gpt-5-4-vs-gemini-3-1-pro10s
    /claude-pro-vs-chatgpt-plus(cross-model)—
    /claude-for-nonprofits130s
    /everett-waterfront-visitor-guide…10s
    /hood-canal-shellfish-season-2026…10s
    /rakuten-claude-managed-agents-enterprise-deployment10s

    Two patterns in that list. First, ChatGPT appears to cite us disproportionately for model comparisons — grok-vs-claude, opus-4-7-vs-gpt-5-4-vs-gemini-3-1-pro, and the cross-model claude-pro-vs-chatgpt-plus page. Second, and stranger, ChatGPT sent visits to two hyperlocal Pacific Northwest pages: an Everett waterfront guide and a Hood Canal shellfish season page. That is ChatGPT using our site as a reference source for geographic queries, which is not a pattern any other model shows.

    The hidden gem: /claude-computer-use-tutorial received one ChatGPT referral and that referral stayed for 2 minutes 7 seconds. ChatGPT appears willing to cite long-form technical tutorials in a way Claude does not.

    Perplexity treats us like a research database

    Perplexity sent 12 sessions across 10 users to 9 pages — the most evenly distributed of the three and the only model that cites people, founders, and company-history content.

    PageSessionsAvg Time
    /anthropic-founders-2217s
    /claude-code-on-vertex-ai-gcp254s
    /claude-student-discount20s
    /claude-desktop14s
    /claude-team-plan10s
    /how-to-install-claude-code10s
    /restoration-team-training-claude-cowork10s

    Perplexity is the only model that pulled visits on /anthropic-founders-2, which implies Perplexity is fielding a different query shape — something closer to “who founded Anthropic” than “how do I use Claude.” Perplexity is also the only model that surfaced the very niche B2B page /restoration-team-training-claude-cowork. That is a long-tail, vertical-specific query and Perplexity cited us as the source. That is exactly the behavior you would hope for from a research-flavored assistant.

    The three models have completely different citation personalities

    Once you lay the three patterns side by side, the strategy falls out of the page.

    • Claude.ai favors short, factual, access-related pages. Product info, pricing, how-to-access. If you want more Claude citations, write more narrow “how do I do this one specific thing” pages.
    • ChatGPT favors comparisons and long-tail references. X vs Y, alternatives, and — unexpectedly — some geographic content. If you want more ChatGPT citations, write more “X vs Y” posts with tight comparison tables.
    • Perplexity favors people, history, and niche research. Founders, company background, domain-specific tutorials. If you want more Perplexity citations, write more research-flavored background pieces.

    This is the single most practical insight in the data set. Most people talk about “AI SEO” as if it is one thing. It is three things, at minimum, and the content shape that wins one model will not automatically win the other two.

    The crown jewel: one page, 17% of all AI-referred traffic

    The clearest cross-model winner on the site is /claude-student-discount. Claude sent 22 sessions. ChatGPT sent 3. Perplexity sent 2. Combined that is 27 sessions — roughly 17% of all AI-referred traffic we received in 29 days, from a single URL. No other page on the site is cited by all three major LLMs in meaningful volume.

    There is a playbook inside that one data point. The page works because the query “how do I get Claude for free as a student” is an extremely high-frequency question across every chat surface, and the page happens to be structured the way LLMs like to cite: a short, direct answer near the top, specific eligibility rules in a scannable block, and no wall of context before the reader gets to the fact. That structural recipe — front-load the answer, make the facts liftable, keep the page narrow — is repeatable.

    The bigger finding: 90% of our Claude content is invisible to AI

    tygartmedia.com has more than 250 Claude-related articles. Exactly 25 of them show up in the AI-referral data set at all. The 90% that do not get cited are not low-quality — several of them have strong engagement from regular search traffic:

    • /claude-managed-agents-complete-pricing-guide-2026 — 17 sessions at ~1 minute from search, zero AI citations
    • /notion-knowledge-base-for-claude — 10 sessions at 1m 23s, uncited
    • /claude-rate-limits — classic FAQ shape, 6 sessions, not cited
    • /claude-md-playbook — 1 session at 2m 33s, zero AI pickup
    • The full /claude-cowork-* family of 12+ pages, almost entirely invisible to every model

    The difference between an AI-cited page and an AI-invisible page is rarely the quality of the content. It is the shape. Pages that get cited have an early summary, short headings, bulleted facts, and a quotable direct-answer sentence. Pages that do not get cited tend to open with context, build up to the answer, and bury the quotable line in paragraph 9.

    The content-cluster scorecard

    ClusterApprox. PagesApprox. SessionsEngagementAI Citations
    Claude pricing & access~10~160MixedHigh
    Claude managed agents~12~130Strong (25s–1m)Low
    Claude Code~8~60High (18s–3m)Moderate
    Model comparisons (X vs Y)~10~45Very high (1–7 min)Moderate
    Anthropic people/company~8~30MediumModerate
    Claude how-to / tutorials~20~50MediumLow
    Claude Cowork family~15~40Very low (0–10s)Almost none

    Two clusters deserve action. The Claude Cowork family is a content swamp — 15 pages, low traffic, no AI citations, and 0–10 second engagement on the traffic that does land. That cluster should be consolidated into two or three flagship posts and the rest redirected. The model comparisons cluster is the opposite: low volume but 1–7 minutes of engagement and cross-model citations. One well-researched comparison post outperforms ten mediocre explainers on every metric that matters here.

    The playbook, in one list

    • Write more narrow single-answer pages. Candidates I would ship next: /claude-web-search, /claude-api-keys, /claude-max-plan-vs-pro, /how-to-cancel-claude, /claude-mobile-app, /claude-desktop-vs-web, /claude-subscription-refund. Each is ~600 words, answer-first, scannable. That is the shape Claude cites.
    • Add a Quick Answer block to the top of every long-form piece. Two or three sentences. Quotable. That alone moves a real share of our invisible content into AI-citation range.
    • Invest in comparison posts for ChatGPT pickup. We already know ChatGPT cites our existing X-vs-Y content. Ship more of them, with tight tables.
    • Write more founder/history/background pieces for Perplexity pickup. Research-flavored. Dates, names, primary sources.
    • Consolidate the Cowork cluster. Two or three flagship pages, everything else redirected.
    • Ship a permanent AI-Referral dashboard in GA4. Segment on all seven assistant domains. Watch it weekly. This is now a first-class channel.

    Frequently asked questions

    What kinds of pages does Claude.ai cite most often?

    Based on the tygartmedia.com data, Claude.ai disproportionately cites short, factual, access-related pages — product info, pricing, how-to-access, and eligibility details. On our site, two pages (/claude-student-discount and /anthropic-console) accounted for 54.5% of all Claude-referred traffic in a 29-day window.

    What kinds of pages does ChatGPT cite most often?

    ChatGPT’s citation pattern favors comparison and long-tail reference pages — “X vs Y” posts like Grok vs Claude, model-to-model comparisons, and, surprisingly, some geographic and local content. ChatGPT tends to cite many pages once each rather than concentrating on a small set.

    What kinds of pages does Perplexity cite most often?

    Perplexity cites research-flavored content — founders and company history, domain-specific tutorials, and niche B2B pages. It is the only major AI assistant that sent traffic to our Anthropic founders page and to a vertical-specific training page in our data set.

    Why does the same page get different citation volume from different AI models?

    Because each assistant is answering a slightly different distribution of queries. Claude is most often used for “how do I use this product” questions and favors narrow how-to pages. ChatGPT receives more comparison and alternative-seeking queries. Perplexity skews toward research and background questions. A page that is the best answer for one query type will not automatically be the best answer for another.

    How do I structure a page to get cited by AI assistants?

    Lead with a direct, quotable answer in the first paragraph. Use short scannable headings. Keep facts in bulleted or tabular form. Include an explicit FAQ block with question-shaped subheadings. Keep the page narrow — one topic, one canonical answer — rather than a sprawling multi-topic explainer.

    The bigger picture

    The meta-insight worth sitting with: we are currently being cited inside Claude’s internal answer graph for “Claude student discount” because a human sat down and wrote a clear, narrow page about it. That is almost the entire game for publishers for the next three years. Most of the web has not noticed yet. We noticed, and now we have a measurement stack to act on what we noticed.

    If you are a publisher, the thing to do this week is boring and powerful: segment your GA4 on the seven AI-assistant domains from Part 1, sort your landing pages by AI-referral volume, and look at the pages that are winning. They will have a shape. Copy it.

    — If you missed it, Part 1 is here.

  • GEO Visibility Checker — Claude AI Skill for AI Search Optimization

    GEO Visibility Checker — Claude AI Skill for AI Search Optimization

    Find out exactly why AI systems are not citing your content — and what to change.

    Who This Is For

    Built for content marketers, SEO practitioners, and website owners who are publishing good content but not appearing in AI-generated answers on ChatGPT, Perplexity, or Google AI Overviews.

    The Problem

    AI search citation is not random. It follows patterns: entity density, factual specificity, direct-answer structure, authoritative framing, speakable content, and OASF formatting. Most content fails on two or three of these signals — not all of them — which means the fixes are targeted and manageable. The problem is knowing which signals are failing. This skill evaluates your page against all of them and tells you exactly what to change.

    What It Does

    • Evaluates entity density — how many named entities your page references and whether they are specific enough to be useful to AI systems
    • Assesses factual specificity — the ratio of specific, verifiable claims to vague generalizations
    • Checks for direct-answer structure and speakable schema markers
    • Evaluates OASF formatting — the structure that makes content citation-friendly to generative engines
    • Identifies the 3 to 5 highest-leverage changes that would most improve AI citation probability

    What You Get

    The complete skill file in Claude-compatible format, a prompt library specific to the use case, and a setup guide that gets you running in under five minutes. After purchase, everything downloads instantly.

    GEO Visibility Checker — Claude AI Skill for AI Search Optimization

    $47

    Delivered to your inbox within 24 hours — skill file, prompt library, and setup guide

    Buy Now →

    Secure checkout via Square — all major cards accepted

    Want a custom version built specifically for your business? Email will@tygartmedia.com

    Frequently Asked Questions

    What is GEO and how is it different from SEO?

    SEO optimizes for search engine rankings. GEO — Generative Engine Optimization — optimizes for AI citation: getting your content surfaced as a source when ChatGPT, Perplexity, or Google AI Overviews answers a question. The signals are related but distinct.

    Can this guarantee my content will be cited by AI systems?

    No — AI citation is probabilistic, not deterministic. What this skill does is identify and address the specific signals that correlate with AI citation, increasing your probability of being cited.

    Does this work for any type of content?

    Yes. The skill evaluates any page — blog posts, service pages, product pages, and landing pages all have GEO optimization opportunities.

    How is this delivered?

    Within 24 hours of purchase via email from will@tygartmedia.com. Skill file, prompt library, and setup guide delivered as a ZIP download.

    Does this require a paid Claude subscription?

    A Claude account is required. The free tier works for light use. Claude Pro ($20/mo) is recommended for regular use. The skill works with both.

    Can I get a custom version built for my specific business?

    Yes. Email will@tygartmedia.com with a description of your business and workflows. Custom skill builds are available as part of The Fitting service.

  • Is Your Site AI-Ready? Self-Assessment — 47-Point Checklist

    Is Your Site AI-Ready? Self-Assessment — 47-Point Checklist

    Find out exactly what is keeping your website invisible to AI systems — and what to fix first.

    The Shift That Changed Everything

    For two decades, ranking on Google was the game. Then something changed. ChatGPT, Perplexity, Google AI Overviews, and a dozen other AI-powered platforms became the first place an increasingly large share of buyers go when they are researching. These systems do not rank your website. They either cite it or they do not. And whether they cite it depends on signals that are completely different from traditional SEO.

    Most websites — including most professionally built ones — are invisible to these systems. Not because the content is bad, but because the structure is wrong. Missing schema. No entity architecture. Content formatted for humans but not for machines. No speakable blocks. No LLMS.txt signal. Problems that take hours to fix once you know what they are, but that are completely invisible until someone shows you the checklist.

    This is that checklist.

    What’s Inside

    • 47 checkpoints organized across 5 categories: schema markup, entity structure, content format, technical signals, and GEO optimization
    • Scoring guide: calculate your AI readiness score and see what tier your site is in
    • Priority fix matrix: each gap ranked by how much it hurts you and how fast it is to fix — so you know where to start
    • Plain-language explanations for every checkpoint — no jargon, no assumed technical knowledge
    • Delivered as a Notion workspace you can run against any site, any time, and save your results

    Who This Is For

    Business owners who have heard about AI search and want to know where they actually stand. Marketing managers who need a structured framework for evaluating and improving AI visibility. WordPress site owners who want to understand what the SEO plugins are not covering. Anyone who has wondered why their site does not show up when people ask AI assistants about their category.

    What Happens After

    The self-assessment tells you what to fix. If you want help fixing it, every item on the checklist maps to a service we offer — from the $29 WordPress Schema Starter to a full SiteBoost engagement. But the checklist is genuinely useful on its own. Most of the fixes are things any site owner can implement with basic WordPress access and thirty minutes.

    Frequently Asked Questions

    Does this require technical knowledge?

    No. Every checkpoint has a plain-language explanation. The scoring guide tells you whether each item is a DIY fix, a developer task, or something you can handle with a plugin. You do not need to know what schema markup is before you start — you will understand it by the time you finish the first section.

    How long does it take to run?

    About 90 minutes for a thorough first pass on a site you know well. Faster if you are already familiar with your site’s technical setup. The Notion format lets you save your work and return to it.

    Does this work for sites that aren’t on WordPress?

    Yes. Most checkpoints are platform-agnostic. A few reference WordPress-specific tools but note alternatives for other platforms.

    Is Your Site AI-Ready? Self-Assessment

    $19

    Delivered to your inbox within 24 hours — no shipping, no waiting

    Buy Now →

    Secure checkout via Square — all major cards accepted