Secure checkout via Square — all major cards accepted
You can copy this method and connect and audit the site yourself. Buy Now is Will doing the one-time setup: Application Password, REST API check, full inventory, and the baseline reports.
Site Connection and Audit is a service. Square lists it as a one-time setup at $297. It is the front door for every other SiteBoost SKU. The public vertical pages include it inside the pilot. Alone, it is how a site gets on the board without anyone rewriting a post yet.
Self-hosted WordPress only. REST API on (the default). Squarespace, Wix, and Webflow are not compatible. The /siteboost/ hub is blunt about that.
How Will connects a site
wp-connect is the gateway skill. Nothing else in the WordPress stack runs until this works. The 23-site stack article on tygartmedia.com puts a new site at about 20 minutes: Application Password, registry, first audit.
Confirm the site is self-hosted WordPress. Open /wp-json/wp/v2/ in a browser. You should see a JSON index, not a 404. If the REST API is blocked, stop and fix that before anyone shares a password.
In WordPress, go to Users → Profile (or Users → Application Passwords, depending on version). Create an Application Password for a user who can edit posts. Name it something you will recognize later, like “SiteBoost” or “REST audit.” Copy it once. This is not the login password. wp-connect will not use the login password.
Test the connection. GET https://yoursite.com/wp-json/wp/v2/users/me with HTTP Basic auth, username plus the Application Password. A 200 with your user object means you are in. A 401 means the password or user is wrong. A 403 often means a security plugin is blocking REST for that user.
Confirm you can list posts: GET /wp-json/wp/v2/posts?per_page=1&status=publish. If users/me works but posts 403, the user is missing the edit_posts capability.
Write down: site URL, WordPress version if you can see it, hosting (WP Engine, SiteGround, Flywheel, Kinsta, Cloudflare in front, or other), whether Yoast / Rank Math / AIOSEO is present, and who holds the Application Password. Do not put the password in a public doc.
The public SiteBoost pages name the hosts they have used this pattern on: WP Engine, Flywheel, SiteGround, Cloudflare-proxied sites, GCP Compute Engine, DigitalOcean, Kinsta, bare metal. The requirement is the REST API, not a specific host.
Do not install a plugin to “help” the connection. SiteBoost’s rule is no plugins added to the client site. Application Passwords are built into WordPress 5.6 and later.
What the audit checks
wp-site-audit is the skill that runs at the start of any new site. Fetch all published posts (per_page=100, walk pages). For each post, score the same fields:
Word count. Thin is under 500 words.
Title tag and slug quality.
Excerpt / meta description present, empty, or polluted (raw JSON or leftover code in the excerpt is a real pattern; wp-clean-meta exists to strip it).
Categories and tags. Uncategorized is a fail. wp-taxonomy-fix wants 1 to 2 categories and 5 to 10 tags.
Featured image present or not.
Internal links in (orphans: nothing points here) and internal links out (dead-end posts).
Schema present or not, and which types if you can see them (Article, FAQPage, HowTo, BreadcrumbList, Speakable).
FAQ section present or not.
Outbound source citations present or not.
Also roll up site-level numbers: total published posts, total pages (count them, do not edit them), taxonomy health (how many categories, how many unused tags, how many posts still Uncategorized).
The 60-point WordPress SEO Audit Template on tygartmedia.com is the longer human version of this, in six categories: Technical, On-Page, Content, Schema, Local, Analytics. Tools it wants open: Google Search Console, Bing Webmaster Tools, PageSpeed Insights, your SEO plugin, validator.schema.org, an incognito window. Order matters: Technical first, then On-Page, Content, Schema, Local, Analytics. A quick pass is the high-impact rows. A full pass is a few hours the first time. Re-audit quarterly, and after a redesign, a migration, or a plugin purge.
SiteBoost’s service audit, as sold, is the content-and-baseline cut of that: inventory, schema gaps, FAQ gaps, before numbers. It is not a Core Web Vitals engagement and it is not a local-pack rebuild. If you want the 60-point sheet as a Notion checklist, that is a different SKU (WordPress SEO Audit Template).
The four reports you should produce
The public SiteBoost pages name these deliverables. If you are doing this yourself, write the same four:
Content inventory. One row per published post. URL, title, date, word count, category, meta yes/no, FAQ yes/no, schema yes/no, internal links in/out, notes.
Schema gap report. Which posts have no JSON-LD. Which have plugin-bloated or invalid markup. Priority by page type (Article on posts, FAQPage where a FAQ exists or should, HowTo only on real procedures).
FAQ gap report. Which posts have no Q and A block and no FAQPage schema. Those are the AEO queue.
Before baseline. Search Console coverage and the queries / URLs you will watch. A short note on AI visibility for a handful of real questions in your market (do you show up in Perplexity or an AI Overview today?). Write the date. This is what a 60-day report compares to.
Priority the way wp-site-audit does: Critical (taxonomy / metadata), High (SEO / AEO / thin content), then optimization (links, expansion). The recommended next skills, if you are running Claude, are wp-taxonomy-fix, wp-content-expand, wp-schema-inject, wp-interlink, then the refresh stack.
What you do not do in this SKU
Do not rewrite posts. That is Existing Post Optimization or the Pilot.
Do not publish new articles. That is New Article Publishing.
Do not edit Pages, bios, or service templates unless the owner asked in writing. Toolbox rule: posts, not pages.
Do not leave the Application Password in chat logs or a public Notion page.
Do not claim results. You do not have a after yet. You have a before.
If you want Will to connect and audit
You can create the Application Password and fill a spreadsheet this afternoon. Buy Now is Will doing the connection and the four reports, then emailing you the baseline and the recommended ten. Same Square button at the top. $297, one time.
The Pilot Bundle includes this connection plus ten post optimizations and the 60-day report. The Monthly Retainer assumes the site is already connected. If you only want the skill files so your own Claude can connect and audit, that is the WordPress SEO Skill Pack (Starter has wp-connect, wp-post-fetch, and wp-site-audit).
Secure checkout via Square — all major cards accepted
You can copy this method and run the full three-layer stack yourself. Buy Now is the 14 packaged Claude skill files so your own Claude can do it on your WordPress site.
Pro is the middle tier of the WordPress SEO Skill Pack. $79. The live sales page lists 14 skills: everything in Starter, plus wp-aeo-refresh, wp-geo-refresh, wp-schema-inject, wp-taxonomy-fix, wp-interlink, wp-full-refresh, wp-content-pipeline, content-brief-builder, and content-quality-gate. That is the production sequence Tygart Media uses on a single post: SEO, then AEO, then GEO, then schema, then interlink.
Install and connect
Same requirements as Starter. Claude Pro / Max / Team. Self-hosted WordPress. Application Password. Drop the skill files into Claude Desktop (Cowork) or Claude Code. Say “connect to my WordPress site.” wp-connect tests /wp-json/wp/v2/users/me. Stop if that is not a 200.
The sales page’s operator line for this tier: “full refresh post 123.” That trigger is wp-full-refresh. It is the orchestrator. Do not start there on a site you have never audited.
The 14 skills, in the order you should actually use them
Foundation (from Starter)
wp-connect. Authenticate. Gateway.
wp-post-fetch. Load one post with context=edit.
wp-site-audit. Inventory, orphans, thin posts, missing meta, schema gaps. Run first on a new site.
wp-clean-meta. Strip excerpt pollution before you write new meta.
wp-seo-refresh. Title (about 60 characters), meta (about 155 to 160), slug, H2/H3, keyword in the first 100 words.
Taxonomy, before you interlink
wp-taxonomy-fix has two modes: one post, or site-wide. Design 3 to 7 top-level categories. Each post gets 1 to 2 categories (never Uncategorized) and 5 to 10 tags (topic, technology, use case, audience, format). Create missing terms via the API, assign, then normalize duplicate tags. Toolbox lists this as a prerequisite for wp-interlink. If categories are a junk drawer, your link graph will be a junk drawer.
The same skill can write two-layer descriptions on category and tag archives: a 140 to 160 character meta excerpt, then a 400 to 600 word hub body with internal links to the top posts in that cluster. PATCH /wp/v2/categories/{id} and /wp/v2/tags/{id} on the description field. Most themes print that above the post grid.
The three-layer refresh
wp-aeo-refresh. Direct-answer opening, question H2s, FAQ pairs, list-shaped answers, FAQPage schema. SiteBoost existing-post copy uses a 40 to 60 word definition box and 6 to 8 FAQs. The older publish skill used 3 to 5. Use the PAA list in front of you, not a fake number.
wp-geo-refresh. Entity saturation, factual density, context richness, source attribution, topical breadth, semantic clarity. Schema it adds: richer Article metadata, entity markup, Speakable. The citing-sources article is the house rule: name the organization, link the primary source, sources list at the bottom, visible last-updated, dateModified in schema. No fabricated stats.
wp-schema-inject. Detect the type the post actually is and inject JSON-LD. The schema injection sprint’s menu: FAQPage, Article, HowTo, Service, LocalBusiness, Speakable, BreadcrumbList. Validate with Google’s Rich Results Test. Fix failures. Do not leave plugin-bloated invalid markup in the body.
wp-interlink. Hub and spoke, orphan resolution, contextual links. The Copilot / cluster articles on tygartmedia.com use 3 to 5 related posts in the same topical group, descriptive anchors. Do this after the post has a real topic and a real category, not before.
wp-full-refresh. Runs SEO + AEO + GEO + schema + interlink in that sequence on one existing post. This is the “do everything to this post” skill. Use it when the audit already said the post is worth the pass.
New content, not just refreshes
content-brief-builder. Keyword research to a brief, before anyone writes. Feeds the pipeline. A brief that cannot name the query, the intent, the PAA list, and the internal-link targets is not a brief.
wp-content-pipeline. Draft to live: write → SEO → AEO → GEO → schema → taxonomy → interlink → publish. Toolbox order. Same six-step human workflow as the New Article Publishing page, encoded as a skill chain.
content-quality-gate. Pre-publish. Unsourced claims and fabricated numbers get flagged. Run this before any publish, batch or single. The operator guide’s failure mode is the same: fake density backfires when an AI system checks you.
A Pro session on one site
Connect. Audit. Clean polluted excerpts.
Fix taxonomy on the posts you are about to touch (and on the hub category if it has no description).
For each chosen existing post: wp-full-refresh, or the layers by hand in SEO → AEO → GEO → schema → interlink order.
For a new article: brief → pipeline → quality gate → publish.
IndexNow on every URL you created or updated. Confirm in Bing Webmaster Tools.
The operator guide’s weekly rhythm still applies if you are using Pro on a real site: Monday audit, Tuesday to Thursday execute, Friday verify. Pro is the toolkit. It is not a retainer.
What Pro still does not include
Agency adds three reference guides (SEO, AEO, GEO), wp-content-expand (deepen thin posts without overwriting), and wp-new-site-setup (client onboarding). If you are onboarding other people’s sites every week, that is the Agency door. If you want Will to run the posts instead of running skills, that is SiteBoost.
If you want the packaged files
You can run every layer above in the block editor with a checklist. Buy Now is the 14 .skill files delivered by email after checkout. Same Square button at the top. $79.
Starter is the five-skill on-page subset if you only need connect / audit / SEO refresh. Agency is this stack plus onboarding and expansion.
Secure checkout via Square — all major cards accepted
You can copy this method and run a ten-post pilot yourself. Buy Now is Will connecting the site, picking the ten, running the three-layer pass on each, and sending the 60-day impact report.
The Square catalog names this SKU “Connection + 10 Posts.” The /siteboost/ hub calls it the best-value door at $597. The public vertical pages (law firms and the rest of the cluster) spell out the same package: Site Connection and Audit, ten existing-post optimizations, and a 60-day impact report. They price the pieces at $767 if you bought them separate ($297 audit + 10 × $47). The bundle is the cheaper way to get a first measured pass.
What the pilot is, and is not
It is a retrofit of ten published posts. SEO + AEO + GEO + schema on each. Changes via the WordPress REST API. No plugin left behind. Results looked at around day 60. It is not a retainer, not a redesign, and not ten brand-new articles. New Article Publishing is a different SKU. The monthly retainer is the ongoing door after you like the pilot.
Self-hosted WordPress only. Squarespace, Wix, and Webflow are out. Posts, not Pages, unless you put a specific Page in writing.
How to run the pilot yourself
Week 0. Connect and baseline
Do the connection and audit first. The method is on the Site Connection and Audit page. Short version:
Create a WordPress Application Password (Users → Profile). Not the login password.
Test GET /wp-json/wp/v2/users/me with that user and app password. If that fails, stop. Nothing else will work.
Pull published posts (per_page=100, paginate if you have more). Inventory every post: title, slug, word count, excerpt/meta, categories, tags, featured image, internal links in, internal links out, schema present or not, FAQ present or not.
Write four artifacts and keep them. Content inventory. Schema gap report. FAQ gap report. Before baseline (the numbers you will compare at day 60: rankings and impressions you can actually see in Search Console, plus a note on AI visibility if you check Perplexity / ChatGPT / AI Overviews on a few queries).
wp-site-audit’s priority stack: Critical = taxonomy and metadata problems. High = SEO / AEO / content quality. Then link and expansion opportunities. Use that order when you pick the ten.
Pick the ten
Highest-opportunity existing articles, with your approval before anyone starts rewriting. That is the rule on the public SiteBoost pages. A practical pick list, from the same audit fields:
Posts that already get impressions but have empty meta, no FAQ, and no schema. Those move first.
Posts over 500 words that are still missing the AEO and GEO layer. Do not spend the pilot on stubs.
Posts that sit on a real query (you can name the keyword). Skip diary posts and leftover test content.
A mix across your actual topic pillars, not ten posts from one tag.
Write the ten URLs down. Get a yes. Then do not swap them mid-pilot unless a post is broken.
Weeks 1 to 3. Ten existing-post passes
For each of the ten, run the same method as Existing Post Optimization:
SEO: title 50 to 60, slug, meta 140 to 155, H2/H3, keyword in the first 100 words.
AEO: 40 to 60 word definition box, question H2s with 40 to 60 word answers, 6 to 8 FAQ pairs, FAQPage JSON-LD.
Article schema. Validate. Two to five internal links into the rest of the cluster. IndexNow on the update.
Sequence on a single post is SEO, then AEO, then GEO, then schema, then interlink. That is wp-full-refresh. Do not GEO a post whose title and meta are still empty.
If a chosen post is under 500 words, expand it first (append real sections, do not overwrite) or swap it for a thicker post on the same topic. Thin content wastes a slot.
Day 60. Impact report
The public pages measure three things: traditional rankings and impressions, People Also Ask / snippet placements, and AI citation visibility. Pull Search Console for the ten URLs (and the queries they were aimed at) versus the before baseline. Recheck the same AI prompts you wrote down in week 0. Do not invent a win. If nothing moved, say so. The report is the point of a pilot. You are deciding whether a retainer is worth it.
Traditional SEO on competitive terms is often 60 to 90 days. The same pages note that FAQPage / PAA and some AI crawlers can show sooner (they cite 2 to 4 weeks for PAA). Treat those as ranges from the public SiteBoost copy, not a guarantee.
What you should have on disk at the end
Connection notes (site URL, that an app password was created, who holds it).
The four audit artifacts from week 0.
The list of ten URLs and the before/after for each (title, meta, word count, FAQ count, schema types).
The 60-day comparison. What moved, what did not, what you would do next (more existing posts, new articles, or stop).
If you want Will to run the pilot
You can do every step above with an Application Password and a spreadsheet. Buy Now is the packaged pilot: Will connects, audits, agrees the ten with you, runs the three layers on each post, and sends the 60-day impact report. Same Square button at the top. $597.
After a pilot you like, the Monthly Retainer is 10 existing-post passes plus 4 new articles per month. If you only need the connection and the baseline, buy Site Connection and Audit. If you only need one post touched, buy Existing Post Optimization.
Secure checkout via Square — all major cards accepted
You can copy this method and publish the article yourself. Buy Now is Will researching, writing, optimizing, and publishing one new WordPress post for you.
SiteBoost New Article Publishing is a new post, not a refresh of something already live. The /siteboost/ hub prices it at $97 per article. The same three layers as an existing-post pass still apply. You just start from a brief instead of from a published URL.
The six-step workflow
This is the unified content workflow from the operator’s guide on tygartmedia.com. One draft. SEO, AEO, and GEO built in. Not three versions of the same piece.
1. Keyword and intent
Name the target query. Classify intent: informational, navigational, commercial, or transactional. Look at what already ranks and match the format Google is already rewarding. This step is ordinary SEO. Do not skip it because you are “writing for AI.”
2. Question landscape
Search the keyword. Collect People Also Ask questions, related searches, and autocomplete variants. Group them. Those groups become H2s and FAQ items. The operator guide budgets 15 to 20 minutes here. This is the AEO setup. If you skip it, you will write headings that feel like an outline and not like queries.
3. Write with the direct-answer pattern
Write the article once, with both SEO and AEO in the draft:
Primary keyword in the H1 and in the first 100 words.
Every major section is a question-shaped H2, then a 40 to 60 word answer, then the depth.
Internal links with descriptive anchors to posts that already exist on the site. If the site is new and there is nothing to link to, note the gaps. Do not invent destinations.
A 40 to 60 word definition box near the top.
The WordPress Publish skill’s quality bar before anything goes live: title 50 to 60 characters with the primary keyword, meta 140 to 160 characters, a unique H1, at least one direct-answer section, a FAQ with 3 to 5 Q and As on a new article (SiteBoost existing-post passes use 6 to 8; for a new article start at 3 to 5 and add more if the PAA list is real), Article JSON-LD, FAQPage JSON-LD, and at least one cited fact per major section.
4. GEO enhancement
After the draft exists, do a factual-density pass. The operator guide budgets 20 to 30 minutes on a 1,500-word article. For every claim: a number, a date, a named organization, or cut it. The citing-sources article is the house rule:
Name the organization in the text, not only in a hyperlink.
Link the primary source. If it is paywalled, link a credible secondary that cites it.
Put a sources list at the bottom.
Show a last-updated date near the byline.
Put datePublished and dateModified in Article schema.
Do not add fake statistics to look dense. The operator guide calls that out as a backfire when AI systems cross-check you.
5. Schema
Minimum on a new SiteBoost article: Article (or BlogPosting) plus FAQPage. Add HowTo if the piece is genuinely step-by-step. Add BreadcrumbList if the theme does not already emit it. Add Speakable on the definition box and one other self-contained block. JSON-LD in the post, validated with Google’s Rich Results Test. The schema injection sprint is the same sequence: pick the type, generate valid JSON-LD, inject, validate, fix failures.
SiteBoost content standards also embed an LLMS.txt HTML comment on the page. A short seed paragraph, not a second article.
6. Pre-publish audit, then publish
Run the three-layer checklist. Title, meta, headings, snippet readiness, factual density, schema validation, entity signals. Then publish as a post, not a page.
The production pipeline used on Tygart Media sites is: brief (content-brief-builder) to draft to SEO to AEO to GEO to schema to taxonomy to interlink to publish (wp-content-pipeline). content-quality-gate sits in front of publish and flags unsourced claims. You can do that as a human checklist if you are not running Claude skills.
Taxonomy and internal links
Assign 1 to 2 categories that are real content pillars, never Uncategorized. Assign 5 to 10 tags that cover topic, use case, audience, and format. That is the wp-taxonomy-fix rule. Then place 3 to 5 internal links to related posts in the same cluster, plus outbound links to the sources you named. Hub and spoke. The new post should not be an orphan on day one, and it should not be a dead end.
IndexNow
On publish, ping IndexNow. Official plugin, or Rank Math / Yoast Instant Indexing. Confirm the URL in Bing Webmaster Tools. New posts that sit in a sitemap waiting for a crawl waste the first week.
What “done” looks like on one new article
Brief: target keyword, intent, PAA list, existing internal-link targets, sources you will actually cite.
Draft written with definition box, question H2s, and sourced facts.
Title 50 to 60, meta 140 to 160, slug clean.
FAQ section + FAQPage schema. Article schema with both dates.
Categories and tags set. 3 to 5 internal links. Sources list.
Rich Results Test pass. IndexNow ping. Status = publish (or draft if you want a human read first).
Self-hosted WordPress only. Squarespace, Wix, and Webflow are not this SKU. Do not modify existing Pages to “make room” for the article. Publish a post.
If you want Will to write and publish it
You can run the six steps in your own editor. Buy Now is the packaged, done-for-you article: Will writes it, runs the three layers, publishes it to your site, and emails you the URL. Same Square button at the top. $97 per article.
A single new post next to a neglected library is a weak play. If the existing posts are empty of FAQ, schema, and meta, optimize those first (Existing Post Optimization, or the Pilot Bundle for ten). If the site is not connected yet, start with Site Connection and Audit.
Secure checkout via Square — all major cards accepted
You can copy this method and do it yourself on one published WordPress post. Buy Now is Will running the same three-layer pass on that post and pushing the changes live for you.
SiteBoost Existing Post Optimization is one post, already on your site. Not a new article. Not a redesign. The public SiteBoost pages call this the post-publish layer: SEO, then AEO, then GEO, written back through the WordPress REST API. No plugin install. Self-hosted WordPress only.
What you are optimizing
Pick one published post (post type post, not a Page). Fetch it. Read it as it sits today. Then run three passes in this order. The operator guide on tygartmedia.com is explicit: the layers are concentric, not three separate rewrites. One piece of content. Structure, density, and markup.
Pass 1. SEO
This is the foundation. Do not skip it to chase snippets or AI citations. The SiteBoost vertical pages and the wp-seo-refresh skill agree on the same fields:
Title tag. Primary keyword front-loaded. Target 50 to 60 characters. This is the H1 / browser title, not a clever headline that hides the query.
Slug. Lowercase, hyphenated, keyword-rich. Change it only if the current slug is junk. If the post already ranks on the old URL, leave the slug and add a redirect if you must change it.
Meta description. 140 to 155 characters on the SiteBoost sales pages, 155 to 160 in the wp-seo-refresh skill. Write a real sentence a human would click. Empty meta is the most common miss.
Heading structure. Real H2 / H3 hierarchy. No skipped levels. No H2 that is just a label with no answer under it.
Primary keyword in the first 100 words.
Note internal link opportunities. You will place them after the GEO pass, not while you are still rewriting the title.
Workflow from wp-seo-refresh: fetch the post with context=edit, analyze current on-page SEO, name the target keyword from the actual topic, generate the new title / meta / headings, write the post back, then report what changed.
Pass 2. AEO
Answer Engine Optimization. Same post. Restructure so a featured snippet or a People Also Ask box can lift a clean answer.
Add a 40 to 60 word definition box near the top. One sentence that answers “what is this?” without a wind-up.
Turn implied questions into H2s. Under each H2, put a 40 to 60 word direct answer, then the depth.
Add 6 to 8 FAQ pairs that match real People Also Ask questions for the topic. The older WordPress Publish skill used 3 to 5. The SiteBoost vertical pages use 6 to 8. Use 6 to 8 on a SiteBoost-style pass.
Add FAQPage JSON-LD for those pairs. Question and acceptedAnswer. Valid markup, not a plugin dump.
wp-aeo-refresh also looks for list-shaped answers and natural-language replies a voice result can read. If a section is a process, a numbered list beats a paragraph.
Pass 3. GEO
Generative Engine Optimization. Make the post citable by ChatGPT, Perplexity, Claude, Gemini, and Google AI Overviews.
Entity saturation. Name the real organizations, standards, statutes, places, and tools the topic depends on. Entity density, not keyword stuffing.
Factual density. Replace “many companies” and “studies show” with a named source and a number you can actually point to. If you cannot name the source, cut the claim. The citing-sources article on tygartmedia.com is the rule: name the organization in the text, link the primary source, put a sources list at the bottom.
Speakable blocks. Short, self-contained sentences an AI or a voice assistant can lift without the rest of the page.
LLMS.txt as an HTML comment. A seed paragraph the page can carry for LLM citation signals. SiteBoost content standards put this on every page.
Visible last-updated date near the byline, and dateModified in Article schema that matches a real edit. Do not bump the date without changing the content.
wp-geo-refresh also asks for context richness (define the term, do not just mention it) and semantic clarity (connect related concepts in the same section).
Schema and IndexNow
After the three passes, the post should carry Article JSON-LD (headline, author, publisher, datePublished, dateModified) plus FAQPage. BreadcrumbList if the theme does not already emit it. Validate with Google’s Rich Results Test before you walk away. The schema injection sprint on tygartmedia.com is the same rule: pick the type the content actually is, inject JSON-LD, validate, fix failures.
Then tell the engines the URL changed. IndexNow: official WordPress plugin, or the IndexNow / Instant Indexing toggle in Rank Math or Yoast. Confirm the ping in Bing Webmaster Tools. A publish or an update that nobody recrawls is a pass you did for yourself.
What you do not touch
Posts, not Pages. SiteBoost does not rewrite service pages, bios, or the homepage unless someone asked in writing. Do not install a plugin to do this. Do not empty the excerpt into raw JSON. If the excerpt is polluted, strip it (that is the wp-clean-meta job) and write a real meta description.
A honest one-post checklist
Current title, slug, meta, word count, FAQ count, schema present or not. Write those six lines down. That is your before.
SEO pass. Title, slug, meta, headings, first 100 words.
Two to five internal links to related posts on the same site, descriptive anchors, plus one or two outbound links to primary sources.
Validate schema. Ping IndexNow. Write the after: new title, new meta, new word count, FAQ count, schema types.
If the post is under 500 words, expand it before you call the SEO pass done. wp-content-expand’s rule: find H2s under 150 words, add 250 to 400 words of real section, append, do not overwrite. Thin posts do not earn the AEO or GEO layer.
If you want Will to do this post
You can run the three passes in the block editor this afternoon. Buy Now is the packaged, done-for-you version: Will connects, refreshes that one existing post through the REST API, and emails you what changed. Same Square button at the top of this page. $47 per post.
If you have ten posts that all need this, the Pilot Bundle is the volume door. If you do not have a connection or a baseline yet, start with Site Connection and Audit. This SKU assumes the post already exists and you already know which one.
This is the capstone of Tygart Media’s AI Search Intelligence series — the full behind-the-scenes of a 40-article experiment designed to test a single thesis: that Bing’s search index, Microsoft Copilot’s citation behavior, and Bing Ads’ retargeting capabilities form the only closed-loop AI search monetization system available to publishers in 2026.
Over the preceding nine articles in this series, we’ve covered the individual components — server log analysis, topic selection methodology, AI citation valuation, and the technical optimization layers that make content citable by AI systems. This article ties it all together: the thesis, the experiment design, the day-one data, and what it means for every publisher navigating the shift from clicks to citations.
The Thesis: Why Bing Is the Only Closed-Loop AI Monetization Platform
Why Bing is the closed-loop AI monetization platform.
The core thesis behind this entire experiment is straightforward, but its implications are enormous:
Bing powers Microsoft Copilot’s citations. If you publish authoritative content that Bing indexes quickly, Copilot will cite it. You can then retarget those AI-referred visitors with Bing Ads. This creates a repeatable publish → index → cite → retarget → monetize flywheel that does not exist on any other platform.
This is not speculation. It is an architectural reality of how Microsoft has built its AI search stack. Let’s break down why Bing — and only Bing — makes this possible.
Microsoft Copilot Uses Bing’s Index for Grounding
When a Microsoft 365 Copilot user asks a question in Teams, Word, or the Copilot sidebar, the system retrieves grounding information from Bing’s search index. This is not a separate AI index. It is the same Bing index that traditional search queries hit. That means every piece of content that Bing has indexed is a candidate for Copilot citation — and every Copilot citation carries a clickable source link back to the publisher’s domain.
The IndexNow protocol gives publishers a mechanism to notify Bing (and other participating search engines) the moment new content is published. Unlike Google’s indexing pipeline — where new pages can wait days or weeks for crawling — IndexNow pings result in Bingbot visits within hours. For a monetization thesis that depends on speed-to-citation, this is not a minor advantage. It is the enabling infrastructure.
Bing Ads Closes the Monetization Loop
Here is where the flywheel becomes unique. A visitor arrives on your site via a Copilot citation — your server logs show a referrer from copilot.microsoft.com. That visitor is now in your Bing Ads retargeting audience. You can serve them follow-up ads through the Bing Ads network: display, search, or audience campaigns. No other AI platform offers this. Google’s AI Overviews do not currently cite sources with the same clickable attribution model. ChatGPT’s citations use Bing’s index but do not feed into an ad retargeting ecosystem controlled by the same company. Only Microsoft owns every link in the chain: index → cite → retarget.
As we explored in our PSAO framework analysis, this platform-specific architecture is why optimizing for each AI system separately — rather than treating “AI search” as a monolith — produces dramatically better results.
The Flywheel Diagram
The system works in five steps:
Publish — Create authoritative, entity-rich content optimized for AI citation (SEO + AEO + GEO)
Index — Ping IndexNow to get Bing to crawl and index within hours
Cite — Copilot surfaces your content as a grounding citation when enterprise users ask relevant questions
Retarget — Visitors who arrive via Copilot citations enter your Bing Ads audience pools
Monetize — Serve targeted ads, capture leads, or nurture those visitors through your conversion funnel
Every step in this loop is controlled by Microsoft’s ecosystem. That is what makes it a closed loop — and that is what makes it testable.
The Experiment: 40 Articles Published in a Single Day
40 articles in a day — watch the crawlers respond.
To test the Bing Citation Mining thesis, we designed a controlled experiment with specific, measurable parameters. On June 22, 2026, Tygart Media published 40 articles on tygartmedia.com, all targeting enterprise Microsoft Copilot use cases. Here is the full architecture of the experiment.
Why 40 Articles?
The number was deliberate. We needed enough content to create a meaningful signal in Bing’s index — a critical mass that would register as a topical cluster, not isolated pages. Forty articles across five categories gave us eight articles per category: enough to establish topical authority in each vertical while generating sufficient data points for statistical analysis of crawler behavior, indexation speed, and citation patterns.
Why Enterprise B2B Topics?
We chose enterprise Microsoft Copilot topics for a specific strategic reason: they match Copilot’s primary use case. The people using Microsoft Copilot are enterprise workers — knowledge workers in mid-workflow asking questions about the tools they use daily. When someone asks Copilot “How do I set up DLP policies for Copilot?” or “What’s the ROI framework for Copilot adoption?”, the system reaches into Bing’s index for grounding. We wanted to be the content it found.
Our topic selection methodology article details the full process, but the summary is this: we reverse-engineered what enterprise Copilot users would ask, then wrote the authoritative answers. This is the discipline we call AI-citable topic selection.
The Five Strategic Categories
Each category was chosen to map to a distinct enterprise buyer persona and workflow context:
This five-category architecture was not arbitrary. It mirrors how enterprise procurement committees evaluate technology: security first, then capability, then adoption feasibility, then individual value, then competitive positioning. We built a content cluster that mirrors the enterprise buyer’s information journey.
The Optimization Stack Applied to Every Article
Every one of the 40 articles received a four-layer optimization stack — what we call the full SEO + AEO + GEO treatment. Our analysis of why the SEO vs. GEO vs. AEO debate misses the point explains the philosophy: these are not competing disciplines. They are complementary layers that serve different retrieval systems simultaneously.
Layer 1: SEO (Search Engine Optimization)
The traditional foundation. Every article received optimized title tags, meta descriptions, heading structure (H2/H3 hierarchy), keyword placement in the first 100 words, and internal linking to related articles within the cluster. This layer ensures discoverability through conventional Bing and Google search.
Layer 2: AEO (Answer Engine Optimization)
Structured to win featured snippets and direct answer placements. Every article includes FAQ sections with five question-answer pairs, definition boxes for key terms, direct answer paragraphs formatted for extraction, and “What is…” framing for core concepts. This is the layer that makes content extractable by AI systems looking for concise, authoritative answers.
Layer 3: GEO (Generative Engine Optimization)
The newest and most critical layer for AI citation. Every article maximizes entity saturation — naming specific tools (Microsoft Copilot, Power BI, Microsoft Teams, SharePoint), specific metrics, specific frameworks, and specific organizations. Factual density is deliberately high. We applied the principles of how AI engines select content for citation: statistical backing, authoritative sourcing, and structured data that LLMs can parse without ambiguity.
Every article also includes speakable schema markup and follows the OASF (Optimized Answer Snippet Format) structure — a format designed to make paragraphs maximally extractable by generative AI systems.
Layer 4: Schema Markup (JSON-LD)
Every article carries three JSON-LD schema blocks: Article (with headline, author, publisher, dates, and keywords), FAQPage (with five structured Q&A pairs), and BreadcrumbList (with proper site hierarchy). This structured data layer makes content machine-readable in a way that goes beyond what crawlers can infer from HTML alone.
Day-One Results: What the Server Logs Revealed
Day-one server logs reveal who actually showed up.
The experiment’s first validation came from raw server log data — not analytics dashboards, not third-party estimates, but the actual HTTP requests hitting tygartmedia.com’s origin server. As we detailed in our server log analysis guide, this is the only way to see AI crawler traffic that Google Analytics and similar tools miss entirely.
What we also documented in our analysis of why websites are read by AI more than humans is now an established pattern — and our 40-article experiment confirmed it within the first 48 hours.
The Traffic Split: AI vs. Traditional Crawlers
Within the first 48 hours of publishing all 40 articles, the server logs recorded:
Total AI crawler hits: 6,805
Total traditional crawler hits: 4,897
AI crawler advantage: 39% more AI traffic than traditional traffic
Source: Tygart Media server log analysis, June 2026
This is the headline number, and it is not subtle. AI systems consumed more of our content than traditional search engines within the first two days. For publishers who are not instrumenting their servers to see this traffic, this entire category of consumption is invisible.
Crawler-by-Crawler Breakdown
The AI crawler traffic was not uniform. Each system exhibited distinct crawling behavior:
ChatGPT-User: 3,404 hits — The dominant AI crawler by volume. ChatGPT-User is the real-time retrieval agent that fires when a ChatGPT user asks a question requiring current information. This crawler accounted for 50% of all AI crawler hits, making it the single largest source of AI-driven content consumption on the site. This confirms what we found in our research on how to get cited in ChatGPT Search: the ChatGPT-User agent is the most active retrieval crawler in the current AI ecosystem.
GPTBot: 1,123-request structural crawl — GPTBot did something qualitatively different from ChatGPT-User. Rather than fetching individual articles in response to user queries, GPTBot executed a systematic structural crawl that mapped the entire site architecture. It hit sitemaps, category pages, author pages, and individual posts in a methodical pattern — and completed the entire crawl within one hour. This is training-data acquisition behavior, distinct from the real-time retrieval pattern of ChatGPT-User.
Bingbot: 4-hour post-publish gap, then full coverage — After we published all 40 articles and pinged IndexNow, there was a 4-hour gap before Bingbot arrived. Once it started, it crawled all 40 articles. This confirms that IndexNow is fast — but not instant. The 4-hour processing window is an important planning consideration for publishers who need to time their content for maximum citation opportunity. Our analysis of the Google Search Console indexing paradox provides additional context on how different indexing pipelines compare.
Source: Tygart Media server log analysis, June 2026
The Citation Signal: 3 Confirmed Copilot Referrals
Within 48 hours of publishing, server logs recorded 3 confirmed referral visits from copilot.microsoft.com. These are visitors who saw a Copilot citation of Tygart Media content, clicked through, and landed on the site.
Three referrals in 48 hours from a brand-new content cluster is a meaningful signal. It confirms the core thesis: publish authoritative content on enterprise Copilot topics, get it indexed on Bing via IndexNow, and Copilot will cite it. The speed surprised us — we expected the citation pipeline to take longer than the indexation pipeline, but they appear to be tightly coupled.
For context on what these citations are worth, see our AI citation value framework, which breaks down the per-citation economics of Copilot referrals versus traditional search clicks.
Source: Tygart Media server log analysis, June 2026
Five Things That Surprised Us
Every experiment produces expected results and unexpected ones. These are the findings that challenged our assumptions.
1. The Speed of AI Crawler Response
We anticipated that AI crawlers would find the content within days. They found it within hours. The first ChatGPT-User hits arrived the same day we published, and GPTBot completed its structural crawl within 60 minutes of its first request. This speed suggests that AI systems are monitoring Bing’s index (via IndexNow notifications or similar mechanisms) far more aggressively than we assumed. As we explored in our analysis of whether anything actually fetches your llms.txt file, the reality of AI crawler behavior is often different from what documentation suggests.
2. ChatGPT-User Was the Dominant Crawler, Not GPTBot
Most industry commentary focuses on GPTBot as OpenAI’s primary crawler. Our data shows ChatGPT-User generated 3x the request volume of GPTBot (3,404 vs. 1,123). This matters because ChatGPT-User represents real-time retrieval — actual humans asking questions and the system fetching your content to answer them. GPTBot’s crawling is important for training data, but ChatGPT-User is where the immediate citation value lives.
3. GPTBot’s Crawl Was Structural, Not Content-Focused
GPTBot did not just crawl the 40 articles. It crawled the site’s architecture — sitemaps, category pages, related posts, navigational elements. It was mapping the site’s information architecture, not just ingesting individual pages. This suggests that topical authority signals (how content is organized, categorized, and interlinked) matter for AI systems in ways that parallel but differ from how Google evaluates site structure.
4. The Bingbot Gap Is Real but Manageable
The 4-hour gap between IndexNow ping and Bingbot’s first crawl is not a flaw — it is a processing window. For publishers planning content launches timed to earn Copilot citations (for example, publishing content before a major industry conference where enterprise workers will be asking Copilot questions), this 4-hour window needs to be factored into launch timing.
5. Copilot Citations Arrived Before Full Bing Ranking
The 3 Copilot citation referrals arrived within 48 hours — before the content had time to establish meaningful Bing search rankings. This is a critical insight. Copilot citation is not gated on ranking position the way traditional featured snippets are. If Bing has indexed the content and it is topically relevant to the query, Copilot can cite it regardless of where it ranks in traditional search results. This decoupling of citation from ranking is one of the most important structural differences between AI search and traditional search.
The Content Architecture: How Enterprise Topics Map to AI Citation Opportunity
The 40 articles were not written randomly within their categories. Each one was designed to answer a specific question that an enterprise Copilot user would plausibly ask during their workflow. This question-first approach is fundamentally different from keyword-first SEO content strategy.
Consider the difference:
Keyword-first approach: “microsoft copilot governance” has 1,200 monthly searches → write an article targeting that keyword
Question-first approach: “A CISO is deploying Copilot next quarter and asks Copilot itself, ‘What governance framework should I use for Microsoft 365 Copilot?’” → write the definitive answer to that question
The second approach optimizes for AI citability. The first optimizes for traditional search rankings. In 2026, both matter — but the question-first approach maps directly to how Copilot retrieves grounding content. As we analyzed in our comparison of writing for Google vs. Copilot vs. ChatGPT, each platform’s audience asks questions differently, and the content must be shaped accordingly.
Every article in the 40-article cluster links to at least 3-5 other articles within the cluster. This is not just an SEO tactic — it is an AI citation optimization strategy. When GPTBot crawls your site structurally (as our logs confirmed it does), internal linking signals tell it which content is related and which pages are authoritative within a topic cluster. The tighter the internal linking, the stronger the topical authority signal.
This also supports what we found in our investigation of what content wins in enterprise Copilot workflows: content that exists within a well-linked cluster is more likely to be surfaced than isolated pages, even if the isolated page is individually stronger.
What Happens After Day One: The Measurement Framework
Publishing 40 articles and measuring the first 48 hours is the beginning, not the end. The experiment’s real value will emerge over the next 30, 60, and 90 days as we track the following metrics:
Bing Indexation Rate
How many of the 40 articles reach full Bing indexation, and how quickly? IndexNow accelerates initial crawling, but full indexation (where content is eligible for citation) is a separate milestone. We are tracking this via Bing Webmaster Tools daily.
Copilot Citation Volume
The 3 citations in 48 hours are a baseline. We expect this number to grow as the content matures in Bing’s index and as more enterprise users ask related questions. Server logs will track every copilot.microsoft.com referral. Our framework for calculating the value of AI citations provides the methodology for assigning dollar values to each referral.
AI Crawler Return Frequency
How often do ChatGPT-User, GPTBot, and Bingbot return to recrawl the content? Freshness signals matter for AI citation eligibility, and understanding recrawl patterns tells us how often content needs updating to maintain citation status.
Traditional Search Performance
The SEO layer is not irrelevant. Bing search rankings, Google search rankings, and organic traffic will be tracked through Google Search Console, Bing Webmaster Tools, and GA4. The hypothesis is that content optimized for AI citation also performs well in traditional search — but we are measuring, not assuming.
Visitor Behavior Post-Citation
What do visitors who arrive via Copilot citations actually do on the site? Do they read one article and leave, or do they explore the cluster? Our GA4 audit of AI referral retention found that AI-referred visitors exhibit different behavior patterns than organic search visitors, and tracking this for the 40-article experiment will either confirm or challenge those findings.
This experiment was not designed to be a Tygart Media vanity project. It was designed to answer a question that matters to every publisher, content strategist, and digital marketer: Is AI search monetization a real, repeatable system, or is it theoretical?
The data says it is real. Here is what that means in practice.
AI Search Monetization Is Not Theoretical — It Is Happening Now
Three Copilot citations within 48 hours from a brand-new content cluster. Six thousand eight hundred five AI crawler hits versus 4,897 traditional hits. These are not projections. They are server log entries. The publish → index → cite loop works, and it works within days, not months. The publishers who build for this system today will compound their advantage as AI search usage grows.
Server Log Instrumentation Is Now a Competitive Necessity
If you are not parsing your server logs for AI crawler traffic, you are flying blind. Google Analytics does not show you ChatGPT-User hits. Your SEO dashboard does not show you GPTBot’s structural crawl. The 6,805 AI crawler hits we recorded would have been completely invisible without server log analysis. This is not an advanced technique reserved for technical publishers — it is table stakes for anyone competing in AI search.
Our detailed guide on server log analysis for publishers provides the complete methodology, from log file access to bot identification to traffic categorization.
Topic Selection for AI Citability Is a New Discipline
Traditional keyword research asks: “What are people searching for?” AI-citable topic selection asks: “What questions will people ask AI assistants, and can I be the authoritative source the AI cites in response?” These are related but distinct questions. The enterprise B2B topics we chose for this experiment were selected specifically because they match the workflow context in which Copilot is used. Writing content that matches the context of AI assistant usage — not just the keywords — is the new competitive edge.
The most important finding is not any individual data point — it is that the system is repeatable. The five-step flywheel (publish → index → cite → retarget → monetize) is not a one-time trick. It is an ongoing content operation. Publish more authoritative content. Ping IndexNow. Watch the AI crawlers arrive. Track the citations. Retarget the visitors. Measure the revenue. Repeat.
Every cycle compounds. As your Bing-indexed content cluster grows, your topical authority strengthens. As your topical authority strengthens, your citation rate increases. As your citation rate increases, your retargeting audience grows. As your retargeting audience grows, your monetization improves. This is the flywheel effect — and it only works because Microsoft controls every component of the loop.
The Full Series: Where to Go from Here
This capstone article is the synthesis, but the details live in the individual articles of the AI Search Intelligence series:
The Bing Citation Mining thesis holds that because Microsoft Copilot uses Bing’s search index for grounding and citations, publishers who get authoritative content indexed quickly on Bing can earn Copilot citations — and then retarget those AI-referred visitors through Bing Ads. This creates a closed-loop publish → index → cite → retarget → monetize flywheel that does not exist on any other AI platform.
How many AI crawler hits did the 40-article experiment generate on day one?
According to Tygart Media server log analysis from June 2026, the 40 articles generated 6,805 AI crawler hits versus 4,897 traditional crawler hits within the first 48 hours. AI crawlers outnumbered traditional crawlers by 39%. ChatGPT-User was the single largest crawler with 3,404 hits.
Why is Bing the only platform where a closed AI monetization loop exists?
Microsoft controls every component: Bing indexes the content, Copilot uses Bing’s index for citations, and Bing Ads enables retargeting of citation-referred visitors. Google’s AI Overviews do not cite sources with the same clickable attribution model, and no other company owns the index, the AI assistant, and the advertising platform as an integrated system.
How fast do AI crawlers respond to newly published content?
Based on Tygart Media server log analysis from June 2026, ChatGPT-User arrived within hours of publication. GPTBot completed a 1,123-request structural crawl within one hour of its first request. Bingbot showed a 4-hour post-publish gap (IndexNow processing time) before crawling all 40 articles. (Source: Tygart Media server log analysis, June 2026)
What optimization stack was applied to each article in the experiment?
Every article received four layers of optimization: SEO (title tags, meta descriptions, heading structure, keyword optimization), AEO (FAQ sections, definition boxes, direct answer paragraphs, featured snippet formatting), GEO (entity saturation, factual density, speakable schema, OASF structure), and JSON-LD schema markup (Article, FAQPage, and BreadcrumbList types on every post).
Methodology note: All data cited in this article comes from Tygart Media server log analysis, June 2026. Server logs were parsed for user-agent identification, referrer analysis, and request categorization. No third-party analytics platforms were used for AI crawler traffic measurement, as these platforms do not capture bot-initiated requests. Copilot referrals were identified by copilot.microsoft.com referrer strings in raw access logs.
This article is part of Tygart Media’s AI Search Intelligence series — original research and frameworks for publishers navigating the shift from search engine optimization to AI search optimization.
Paste your article. Get back the version built to win the featured snippet.
Who This Is For
Who the AEO content optimizer skill is for.
Built for site owners and content marketers who publish good content that never gets picked as the answer — no featured snippets, no People Also Ask placements, invisible in voice results and AI Overviews while thinner competitor pages take the box.
The Problem
Answer engines do not reward the best content — they reward the most extractable content. A page that buries its answer in paragraph six loses to a page that answers in the first 50 words under a question heading, formatted the way the snippet wants. Restructuring for extraction is mechanical, learnable work — and almost nobody does it. This skill does it on every piece you paste.
What It Does
What it does for featured snippets / AEO.
Performs answer-first surgery: a direct, self-contained 40–60 word answer placed immediately under each question heading
Converts topical headings into the question formats searchers actually use, mapped to real query variants
Matches the winning snippet format per query — paragraph, numbered list, or table — and rebuilds the block to fit
Builds a genuine FAQ section and generates the matching FAQPage JSON-LD (and warns about duplicate schema before you paste)
Runs a voice pass so direct answers survive a smart-speaker read
Returns a change log plus an honest note on what content is missing that the query demands
What You Get
What you get.
The aeo-content-optimizer.skill file — installs in claude.ai or Claude Code in about two minutes
README with installation steps and tested example prompts
Works on existing posts, new drafts, and competitor-gap rewrites
No. You paste your content and your target question. The skill restructures and returns paste-ready output, including the schema block.
Does it work for my niche?
Yes — the method is format-driven, not topic-driven. Local services, SaaS, e-commerce, professional services, and content sites all follow the same extraction rules.
Will it change my voice or facts?
It restructures; it does not genericize. Anything it cannot verify is flagged for you to supply rather than invented.
How is this delivered?
Within 24 hours of purchase via email from will@tygartmedia.com. Skill file and setup guide delivered as a ZIP download.
Does this require a paid Claude subscription?
Installing as a custom skill requires a paid Claude plan (Pro, $20/mo, or higher) with code execution enabled. Your download also includes a free-plan setup option — paste the skill into a Claude Project’s instructions — that works on any plan.
The Search Landscape of May 2026: Stop Chasing Traffic, Start Chasing Citations
The transition is complete. As of this month, Google’s AI Overviews (formerly SGE) appear for over 52% of all search queries. If you are looking at your Search Console and seeing a 30% drop in informational traffic compared to last year, you aren’t alone. You’re simply seeing the result of the “Zero-Click” era reaching its final form. For digital agency owners and systems architects, the old SEO playbook is a liability. If you are still optimizing for clicks on “What is…” or “How to…” keywords, you are effectively donating your intellectual property to train a model that will replace your visit.
The currency of search has shifted. We have moved from the era of link equity to the era of Source-Worthy Content. In this new reality, the goal isn’t to get the user to click through to read a basic definition; it is to ensure that your data, your unique perspective, or your proprietary methodology is the primary source cited by the Retrieval-Augmented Generation (RAG) systems powering Google, Perplexity, and OpenAI.
The Numbers Don’t Lie: The Death of the Click
By mid-2026, the data across our portfolio is clear. Informational query traffic—the top-of-funnel “educational” content that used to drive massive awareness—has cratered by 20-40% across most B2B and technical sectors. Users are getting their answers directly in the search interface. They don’t need to visit your site to learn “how to configure a headless CMS” if Gemini can pull the five essential steps from your documentation and present them in a neat bulleted list.
However, while traffic is down, the value of a single citation within an AI Overview has skyrocketed. We’ve found that being the primary citation in a RAG-driven answer drives higher-intent leads than the old-school organic #1 spot ever did. The users who do click through from an AI Overview have already been pre-qualified by the AI. They aren’t looking for a definition; they are looking for the operator who provided the insight. Optimizing for AI overviews is no longer a side project; it is the core of technical SEO.
Understanding RAG: How Google Picks Its Sources
To win in 2026, you have to understand the mechanics of Retrieval-Augmented Generation. Google’s AI isn’t just “hallucinating” answers based on its training data; it is actively searching the live web, retrieving specific “chunks” of information, and then synthesizing those chunks into a response. This is RAG optimization.
When an AI Overview is generated, Google’s system follows a three-step process:
Retrieval: It identifies the top-ranking traditional search results for the query. (This is why maintaining traditional page-one rankings is still a prerequisite for being a source).
Selection: It selects specific paragraphs, data tables, or unique insights from those top results that best satisfy the user’s intent.
Generation: It rewrites those insights into a cohesive answer, adding citations to the sources it used.
If your content is generic—if it says exactly what every other site says—the AI will synthesize the answer without citing you specifically, or it will cite a larger authority (like Wikipedia or a massive news outlet) that says the same thing. To be cited, your content must be source-worthy. It must provide something the AI cannot find elsewhere or synthesize from common knowledge.
Why Generic Content is Erased by AI
The era of “skyscraper” content—taking ten existing articles and making a longer one—is over. AI is better at that than you are. In fact, most of that generic content is now being flagged by LLMs as “low information gain.”
When we audit a site using the Gemini CLI, we look for “Information Gain” scores. If a paragraph doesn’t offer a new data point, a specific case study result, or a unique operator’s perspective, it’s invisible to the RAG process. Generic advice like “SEO requires good keywords” is discarded. Specific advice like “We saw a 12% lift in RAG citations by moving from 1,000-word articles to 400-word modular content blocks” is source-worthy.
The LLM wants to cite the originator. If you are just a curator, you are a middleman that the AI has successfully bypassed.
The ‘Source-Worthy’ SEO Framework
At Tygart Media, we’ve pivoted our Agency Playbook to focus on four pillars of source-worthy SEO. This is how we ensure our clients remain the “source of truth” in an AI-dominated search engine.
1. Proprietary Data and “Proof of Work”
The AI cannot hallucinate your internal data (yet). Original surveys, technical benchmarks, and project post-mortems are the most cited pieces of content in 2026. If you run a test on a new deployment pipeline and publish the raw numbers, Google’s AI Overview will cite your specific numbers. We’ve moved away from “opinion pieces” and toward “experiment logs.” Every article should contain at least one table or chart of data that didn’t exist on the internet before you published it.
2. The Operator’s Perspective (E-E-A-T)
Experience and Expertise are now the primary filters for RAG selection. Google is prioritizing content that shows “Proof of Effort.” Use first-person accounts. Instead of writing “How to use Claude Code,” write “What we learned after 500 hours using Claude Code to refactor a legacy Python monolith.” The specific failures and technical hurdles you describe are unique identifiers that the AI recognizes as authoritative.
3. Modular Content Architecture
Long-form, sprawling articles are difficult for RAG systems to “chunk” effectively. We are now building content in modular blocks. Each section of an article is designed to stand alone as a complete answer to a sub-query. We use <section> tags and specific ID attributes to make it easy for the crawler to identify and retrieve the exact block it needs. This is optimizing for AI overviews by making your content “consumable” for machines, not just humans.
4. Structured Data for RAG
Schema.org hasn’t gone away; it has become the metadata for AI. We use Dataset, HowTo, and Review schema more aggressively than ever. But more importantly, we are using Gemini CLI to auto-generate JSON-LD that specifically maps out the “Claims” made in our articles. By explicitly stating “Our claim: Informational traffic is down 30%,” we make it easier for the AI to attribute that fact to us.
Technical Execution: Modular E-E-A-T and Gemini CLI
The workflow for a modern agency operator involves high-level automation. We don’t manually audit 500 pages for “source-worthiness.” We use tools like Claude Code and Gemini CLI to process our content libraries.
Our current stack for RAG optimization looks like this:
Analysis: We pipe our top-performing URLs through a script that uses the Gemini API to compare our content against the current AI Overview for that keyword. The script identifies “content gaps”—information the AI is providing that isn’t on our page, or information we have that the AI is ignoring.
Refactoring: If a page is losing traffic but has high “Source Worthiness,” we use Claude Code to refactor the HTML into a more modular structure, adding Dataset schema to any tables.
Validation: we use Antigravity to simulate how a RAG system would “chunk” the page. If the chunks are incoherent, we rewrite the headers to be more explicit.
One failure we saw early in 2026 was attempting to “game” the AI by over-optimizing for specific keywords. The AI sees through keyword density. It is looking for semantic weight. When we tried to force-feed keywords, our RAG citation rate dropped. When we focused on “operator-restrained” technical clarity, the citations returned.
Case Study: The 40% Traffic Drop and the 15% Lead Increase
We recently worked with a systems architecture firm that saw their organic traffic from “cloud migration tips” fall by 40% in the google sge impact may 2026 rollout. Initially, there was panic. However, upon closer inspection, their “Request a Consultation” conversions were actually up by 15%.
What happened? Their generic “tips” were being swallowed by the AI Overview. But the AI Overview was citing their specific “Cloud Migration Cost Calculator” and their “2025 Migration Failure Report.” The traffic they lost was the “looky-loos” who just wanted a quick tip. The traffic they gained (via the AI citations) was from CTOs who saw their specific data cited as the authority and clicked through to hire them. This is the shift from “volume” to “value.”
Action Plan: What You’d Do Tomorrow
If you are managing a content library or an agency portfolio, don’t wait for your traffic to hit zero. Start the pivot to source-worthy SEO immediately. Here is the operator’s checklist for tomorrow morning:
Audit for “What is” Content: Use your preferred crawler to identify every page that targets a purely informational, definitional keyword. These are your “donor” pages. Decide whether to delete them, consolidate them, or upgrade them with proprietary data.
Inject Original Data: Find three pieces of internal data—even if they are small—and add them to your top 10 most important pages. Use tables. Add a “Methodology” section.
Modularize Your Headers: Ensure every H3 in your articles can stand alone as a question and every following paragraph as a direct, concise answer. Remove the “fluff” and the “introductory transitions.” The AI doesn’t need a “In this section, we will explore…” lead-in. It needs the facts.
Verify Citations: Perform a manual search for your primary keywords. Look at the AI Overview. If you are ranking #1-3 in organic but aren’t cited in the AI response, your content isn’t “Source-Worthy.” It’s too generic. Rewrite the top-ranking paragraph to offer a unique, data-backed perspective that the AI is currently missing.
Update Your Schema: Move beyond basic Article schema. Implement Speakable, Dataset, and ClaimReview schema where applicable. Use a tool like Gemini CLI to automate the generation of these blocks based on your existing text.
SEO isn’t dead; the middleman is dead. The search engine of 2026 doesn’t want to send users to a website; it wants to provide an answer. Your job is to be the only source that the answer cannot exist without. Build for the machine, provide for the human, and protect your intellectual property by making it too specific to be ignored.
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
How ChatGPT Search builds an answer.
ChatGPT Search runs a three-stage pipeline. Each stage kills most candidates.
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.
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.
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
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
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.
Perplexity does not “rank” pages the way Google does. It synthesizes an answer and then chooses which sources to attach to it. That distinction is the entire optimization problem. If your page cannot be cleanly extracted into a short, entity-clear passage, it will not be cited — no matter how strong its backlink profile is.
This guide is for SEOs and content directors who already know traditional on-page work and want the implementation layer Perplexity rewards. Skip the strategy posts. Here is what to change in the page itself.
The Three Things Perplexity Is Actually Doing
Three things Perplexity is actually doing.
When a user submits a query, Perplexity runs three operations in sequence:
Retrieval. Sonar (Perplexity’s underlying search system) pulls a candidate set of URLs from its index using hybrid semantic + keyword retrieval.
Extraction. It reads a bounded chunk of each candidate page. The Sonar API exposes this directly — max_tokens_per_page defaults to 4,096 tokens, which is roughly the first 3,000 words of clean body copy. Content past that window is invisible to the answer engine on most calls.
Synthesis with citation. The model writes the answer using passages it can attribute, then surfaces a small number of source links. Perplexity itself has stated the system uses hybrid search combined with LLM reranking and human feedback signals.
Three implications for your page:
The answer to the query must appear inside the extraction window. Buried answers do not get cited.
The passage must be self-contained enough to be quoted without surrounding context.
The source needs to look authoritative to the reranker.
The Extraction Window Test
Open any page you want to be cited. Strip the nav, sidebar, and footer mentally. Count the words from the first H1 to the point where you have answered the page’s primary question. If that number is over roughly 500 words, you are losing citations.
Industry guides reporting on Perplexity’s behavior consistently note that direct-answer formats outperform standard article structures by a wide margin in citation rates. The mechanism is mechanical, not editorial: a Q&A block fits inside the extraction window cleanly.
The Structured Pattern That Works
The structured pattern that works.
This is the structure to lift into any page you want Perplexity to cite. It is not a template for the whole article — it is the citation block that needs to appear in the first 500 words.
<section itemscope itemtype="https://schema.org/Question">
<h2 itemprop="name">What is generative engine optimization?</h2>
<div itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer">
<div itemprop="text">
<p><strong>Generative engine optimization (GEO)</strong> is the practice
of structuring web content so it is selected, extracted, and cited by
AI answer engines such as Perplexity, ChatGPT Search, and Google AI
Overviews. Unlike traditional SEO, which optimizes for ranking position
on a results page, GEO optimizes for inclusion inside a synthesized
answer.</p>
</div>
</div>
</section>
Three things this block does that a normal opening paragraph does not:
The <h2> is the literal query phrasing. The reranker can pattern-match a user question against your heading without rewriting it.
The first sentence is a complete definition with the entity in bold. Perplexity’s extractor favors passages that resolve an entity in a single sentence.
The schema (Question / Answer) is not strictly required for citation, but it makes the passage easier for any LLM-based retrieval pipeline — including Sonar — to identify as an answer unit.
Domain Authority Still Matters — But Differently
Authority signals influence Perplexity’s reranker, but the relationship is not the same as Google’s. A smaller, well-structured page on a moderate-authority domain can outcite a thin page on a high-authority domain because the reranker rewards passage quality alongside source quality. Practitioner reporting estimates domain authority drives roughly 15% of citation likelihood, with content relevance and structure carrying more weight.
The implication: do not skip technical authority work, but do not assume it carries you. A 500-word answer block on a DR 40 site, structured properly, will beat a 2,500-word essay on a DR 70 site that buries its answer.
Freshness Is a Real Decay Curve
Freshness is a real decay curve.
Perplexity re-indexes aggressively and prefers recent material for time-sensitive queries. Practitioner audits report citation visibility starts to fade roughly two to three months after publication if a page is not updated. The fix is mechanical: refresh the dateline, add a small “Updated” block with one new fact or example, and resubmit the sitemap. Pages with rolling updates hold citations longer than pages that ship and freeze.
The Implementation Checklist
For any page you want Perplexity to cite:
Answer the query in a self-contained 2–4 sentence block within the first 500 words.
Use the user’s query phrasing as an <h2>, not a clever headline.
Wrap the answer in Question / Answer schema, or at minimum FAQPage schema if there are multiple answer blocks.
Keep the page total under the extraction window for the primary answer — long-form content is fine, but the cited passage must sit early.
Update the page on a quarterly cadence at minimum, with a visible “Updated” marker.
Treat each H2 on the page as a candidate citation unit. Every H2 should be a question or a clean entity definition, followed by a passage that resolves it without referring backward in the article.
That last rule is the one most pages fail. Pages written for human readers chain ideas across sections. Pages written for Perplexity treat each section as an independent answer.
The Measurement Layer
You cannot optimize what you cannot see. Track Perplexity citations by querying your target keywords directly in Perplexity weekly, logging which URLs appear, and noting whether your domain is in the source list. Several visibility tools now scrape this data, but a manual weekly check on your top 10 target queries is sufficient to start. Pair this with a referrer log filter for perplexity.ai in GA4 to capture downstream traffic.
The optimization loop is short: structure the page, ship, query the target keyword in Perplexity, observe whether you were cited, refine the answer block. Most pages need two to three iterations on the lead block before they earn a steady citation.
