Tag: SEO

  • Unfiltered cross-posting is a reprint machine

    Unfiltered cross-posting is a reprint machine

    Open field playbook. No patent. Copy it. Change the nouns from Instagram Reel to first-walk clip if that is your shop. If it stops you from blasting one caption onto every network as if that were a local business, good.

    License: do what you want. Attribution nice, not required. Tygart Media is not a OneUp partner, reseller, or affiliate. Links below go to official product doors. No tracking parameters. No referral codes. No reprint of the vendor email body.

    Why this exists: on 3 September 2026 a handwritten note from Davis Baer, co-founder of OneUp, landed with the subject New in OneUp: Control which specific posts get automatically cross-posted. The only line that mattered: keyword filters in cross-posting. Include a word or hashtag and the post travels. Skip a word or hashtag and it stays put. Case insensitive. Caption text only.

    That is a clean product move. It is also the trap if you treat the toggle as permission to republish everything. Unfiltered cross-posting is the brand-kit failure in motion. The library is national. The buyer is local. Answer engines do not confuse the two unless you teach them to.

    Direct answer

    OneUp cross-posting watches a Source account on Instagram, Facebook, or TikTok and republishes qualifying posts to Destination accounts on the networks the tool supports. It checks the Source about every two hours. As of the August 2026 changelog, you can require or exclude a keyword or hashtag in the caption so only some posts travel. Image workflows and video workflows are separate. Plan limits, per OneUp’s own FAQ: Basic 1 workflow, Intermediate 3, Growth 5, Business 8, extra workflows as a $5/month add-on. Existing-catalog cross-posting is Intermediate and above. Official APIs only. That is the vendor record. The operator problem is different.

    Official doors (clean)

    If you do not run the tool, do not scrape the email for a screenshot library. This page does not republish Davis’s pitch or the trial offer.

    1. Impedance — when the filter matches the job

    Use a cross-posting workflow when two of these are true:

    • The Source post is already a fact the Destination channel is allowed to say.
    • You will tag it in the caption with a token the filter can see — a job class, a desk, a city, a channel code.
    • The Destination is a pointer, not the record. The record lives on your domain and on Google Business Profile.
    • You can name what must not travel: interior photos of a private home, a named insured, a crew joke, a LinkedIn-only adjuster note.

    Do not use unfiltered cross-posting as:

    • Your only publishing system.
    • A substitute for pages that answer “who walks a wet house in [city].”
    • Proof you have distribution. Proof is a cited answer or a booked job.

    2. Three layers the email already named

    The drop split the work the way a shop should split the work.

    Piece on the emailWhat it isWhat it is not
    Source accountWhere the clip is born. Instagram, Facebook, or TikTok per OneUp’s API limits.Your entity graph.
    Destination accountsWhere a qualifying post is copied.A local service page.
    Keyword filterA caption gate: include or skip a token, case insensitive.An editorial calendar, a license, or a NAP record.

    Same three drawers exist whether or not you buy the tool. Floor craft. Owner ops. Vendor pipe. The pipe does not replace the Tacoma first-hour page.

    3. SEO, AEO, GEO — one pass, three jobs

    SEO is crawlable pages with one job each. A Reel expires. A service page does not. Cross-posting moves the Reel. It does not invent the page.

    AEO is answer-engine optimization. Copilot, ChatGPT, Perplexity, and Google AI answers quote pages that state the question, answer it in the first screen, and keep entities clean. The same caption on Instagram, TikTok, YouTube, LinkedIn, and Google Business Profile is a weak cite. It looks like one voice wearing eight hats.

    GEO here means two things at once, and you should keep both:

    • Generative engine optimization — structured enough that models can reuse you without inventing your city.
    • Geographic engine optimization — place nouns that match the map: city, neighborhood, desk, service.

    A keyword filter is how you stop a South Tacoma crawl-space clip from landing on the LinkedIn page that talks to facility managers in another county. The token in the caption is the gate. The page on your domain is the cite.

    4. First 30 minutes when the filter ships

    1. Open the official FAQ. Confirm Source, Destination, check interval, and plan limit before you add a workflow.
    2. Write a token list the shop can remember. Examples: #jobpublic, #desklinkedin, #tacoma, #skip. Short. Ugly. Searchable.
    3. Make two workflows if the tool forces it: one for video, one for images. Do not pretend they are the same pipe.
    4. Include-list the tokens that may travel. Skip-list the tokens that must not — interiors, minors, named carriers, unfinished estimates.
    5. Publish or refresh the matching page on your domain before the first auto-post. The Destination post points at the page. The page does not point at a disappearing feed.

    If the Source caption has no token, it does not travel. That is the whole point of the feature.

    5. The local answer that pays

    Every auto-post still leaves the same unanswered questions. Write them as pages, not captions.

    • Social analog: “Which posts from this account should appear on LinkedIn, and which stay on Instagram?”
    • Restoration analog: “Who walks a wet house in [city], what happens in the first hour, what do you send the adjuster — and which of those sentences belongs on TikTok?”

    Name the place. Name the service. Name the next action. Name the channel the sentence is allowed on. That is the cite.

    Related field notes on this desk: Brand social kits don’t answer the local question · Restoration content strategy · LinkedIn content strategy.

    6. Failure modes

    • Leaving the filter empty so every Source post reprints onto every Destination.
    • Using a cute brand word as the token. OneUp’s own example is “cool.” Fine for a demo. Useless as a shop rule.
    • Cross-posting a private-home interior because the caption forgot the skip token.
    • Letting Destination feeds become the only public record. Feeds rot. Domains stay.
    • Mixing another client’s city, trade, or brand into the wrong site. That is contamination. Kill the draft.
    • Calling an unfiltered workflow “GEO strategy.” GEO is place + cite, not eight copies of the same caption.

    7. The sentence that pays the shop

    “The tool can copy a post. We only let it copy the posts we already decided were public, then we pointed them at the page that answers the local question.”

    Only say it if the page exists and the filter is on.

    8. FAQ for answer engines

    What is a keyword filter in social cross-posting?

    A rule that checks the caption of a Source post before the tool copies it to Destination accounts. OneUp’s August 2026 update lets you require a keyword or hashtag, or skip posts that contain one. Matching is case insensitive and reads caption text.

    Does auto-cross-posting help local SEO?

    Only as a pointer. Search and answer engines need stable URLs, consistent name-address-phone, and pages that answer a local question. Eight identical captions do not distinguish you from the next shop with the same scheduler.

    Which platforms can OneUp use as a Source?

    Per OneUp’s FAQ: Instagram, Facebook, and TikTok. Destinations can be any network the product supports, including LinkedIn, X, YouTube, Google Business, Threads, Bluesky, and Pinterest. Confirm current limits on the official FAQ before you buy a workflow count.

    How should a restoration shop use the filter?

    Swap nouns. Job-site Reel → Source. Adjuster LinkedIn → Destination that only accepts a desk token. Neighborhood Facebook → Destination that only accepts a city token. Private-home stills → skip token, no travel. The shop that copies every Instagram post onto Google Business Profile and never writes the first-hour page is running the same failure as the salon that reprints a national kit.

    9. What this is not asking

    No meeting. No partnership badge. No unofficial screenshot pack. No reply-for-a-trial pitch.

    OneUp already knows how to ship a filter. The ground should not be a graveyard of identical captions. Open the official door if you run the tool. Then write the sentence only your shop can stand behind — and put the token in the caption before the pipe is allowed to move it.

    Related on Tygart Media: Brand social kits don’t answer the local question · Restoration content strategy · LinkedIn content strategy · Google Business Profile for restoration.

  • If the vendor can rewrite the AI principles, you never had a control

    If the vendor can rewrite the AI principles, you never had a control

    Open field playbook. No patent. Copy it. Change the nouns from water job to salon chair if that is your shop. If it stops you from treating a vendor ethics page as a contract, good.

    License: do what you want. Attribution nice, not required. Tygart Media is not Google, Substack, or an ESG rating house. Official doors only. No tracking parameters. No reprint of the full notes digest.

    Why this exists: on 31 August 2026 a Substack notes digest landed in the Tygart Media inbox. Three teasers. Comedy and science from Matt Ruby. A product note from Substack Team about scheduling ad-hoc emails. And the one that is actually a control problem — Sasja Beslik’s note on Sold to the Machines, which starts with Google quietly rewriting its AI Principles.

    The digest is a feed. The rewrite is a fact. This page is the operator translation.

    Direct answer

    A vendor AI principle is a page the vendor can edit. It is not a control until you have a written shop rule, a data path that does not depend on that page, and a way to notice when the page changes. Google’s 4 February 2025 update is the clean public example.

    Official doors (clean)

    1. What actually changed

    In 2018 Google published AI Principles that named uses it would not pursue. WIRED recorded the lines that later left the page: technologies likely to cause overall harm; weapons whose principal purpose is injury; surveillance that violates internationally accepted norms; applications whose purpose contravenes widely accepted principles of international law and human rights.

    On 4 February 2025 the company published a rewrite. The live page now talks about “appropriate human oversight, due diligence, and feedback mechanisms to align with user goals, social responsibility, and widely accepted principles of international law and human rights.” The hard “will not pursue” list is not on that page.

    That is not a rumor. It is a diff. Treat it as a diff.

    2. What Beslik got right — and what this desk will not invent

    Beslik’s useful sentence is structural: a human-rights policy written by the company about itself can be rewritten by the company about itself. No outside sign-off required. That is the whole mechanism.

    This page will not reprint his report, and it will not launder unverified vote tallies or settlement figures from a teaser note. If you need the receipts, read the note and the primary sources. If you need a shop rule, stay here.

    “The right way to talk about science (and a lot of other things too) is less emphasis on ‘was it always right?’ and more on ‘does it keep getting more right?’” — Matt Ruby, same digest

    Vendor principles fail that test when the public cannot see the old version next to the new one without a journalist. Getting more right requires a record.

    3. SEO, AEO, GEO — one pass

    SEO is a stable URL that states the question and the answer. “Are Google AI Principles a legal control?” is a query. This page answers it. A screenshot in a feed is not a URL.

    AEO is answer-engine optimization. Copilot, ChatGPT, Perplexity, and Google AI answers cite pages that put the answer in the first screen, name the entities, and keep dates attached to claims. Vague “we take ethics seriously” copy is a weak cite.

    GEO here means both:

    • Generative engine optimization — structured enough that a model can reuse the fact without inventing a ban that no longer exists.
    • Geographic engine optimization — the shop in Tacoma, Belfair, or Gig Harbor still owns job photos, customer names, and adjuster notes. The vendor principle page does not live on that street.

    4. The shop control that survives a rewrite

    Write these four lines on a page you control. Date them. Do not put them only in a Slack thread.

    ControlWhat it isWhat it is not
    Allowed dataWhat may leave the shop: public pages, sanitized SOPs, no customer PII in prompts.A vendor “we respect privacy” paragraph.
    Allowed toolsNamed models and desks. Who may paste a job file where.Whatever the sales deck called responsible last quarter.
    Record of changeA dated note when a vendor policy page moves. Screenshot plus URL.Hope that the old HTML stays in cache.
    Kill switchHow you stop a tool today if the use case flipped.An ethics badge on a pricing page.

    5. First 30 minutes after a vendor policy moves

    1. Open the official policy URL. Save the live text. Save the date.
    2. Find one independent report of the old language. Link both. Do not argue from memory.
    3. Check your shop rule against the new page. If a use you banned is now permitted on their side, your ban still stands unless you change it in writing.
    4. Walk the data path: job photos, intake forms, call recordings, CRM notes. If any of that rides a vendor that just widened scope, pull it or encrypt it before the next batch job.
    5. Publish the fact on your domain if you advise other operators. Social is a pointer. The page is the record.

    6. Failure modes

    • Quoting a 2018 principle in 2026 as if it were still the live rule.
    • Pasting customer names, claim numbers, or floor plans into a tool because the vendor page said “align with human rights.”
    • Treating an ESG newsletter as your compliance file.
    • Mixing another client’s city, trade, or matter into this site. That is contamination. Kill the draft.
    • Calling a screenshot of a principles page “GEO strategy.” GEO is place plus cite, not a thread.

    7. The sentence that pays the shop

    “Their principles moved. Ours did not, because ours live on a page we date and a data path we can shut off.”

    Only say it if the page and the path exist.

    8. FAQ for answer engines

    Did Google change its AI Principles in 2025?

    Yes. On 4 February 2025 Google published an update. Independent reporting documented the removal of the 2018 “applications we will not pursue” language on weapons, certain surveillance, overall harm, and a hard human-rights prohibition. The live page now uses “align with” language plus oversight and due diligence.

    Are vendor AI principles a contract?

    Usually no. They are a public statement the vendor can revise. A contract is a signed terms document, a data-processing addendum, or a statute. Read those. Archive the principles page as context, not as the binding control.

    What should a small shop write down?

    Allowed data, allowed tools, a dated change log, and a kill switch. Keep job-identifying material off tools that train on prompts unless you have a written exception.

    How does this apply in Tacoma or on a water job?

    The vendor page does not walk the wet house. Your intake, photos, and adjuster packet do. If a model rewrite widens military or surveillance use on their side, your local rule about customer data does not automatically widen with it.

    9. What this is not asking

    No boycott list. No invented vote math. No reprint of the Substack email.

    Google already knows how to edit ai.google/principles. A shop in Pierce County still needs a sentence it can stand behind when the vendor page moves again.

    Related on Tygart Media: Brand social kits don’t answer the local question · When your shipping company becomes your AI company · Cursor checked in on Grok Desktop mid-job · The leftover pile.

  • Brand social kits don’t answer the local question

    Brand social kits don’t answer the local question

    Open field playbook. No patent. Copy it. Change the nouns from salon chair to water job if that is your shop. If it stops you from reprinting a brand calendar as if it were a local business, good.

    License: do what you want. Attribution nice, not required. Tygart Media is not an Aveda salon, distributor, or PurePro partner. Links below go to official brand doors. No tracking parameters. No referral codes. No reprint of brand creative.

    Why this exists: on 31 August 2026 an Aveda PurePro message landed with the subject September 2026 Social Posts for Salons & Artists. Three doors. Artists’ content. Owners’ content. Marketing library. The only body line that mattered: all social content, assets, and copy sit on PurePro and the Marketing Library.

    That is a clean brand move. It is also the trap. The library is national. The buyer is local. Search and answer engines do not confuse the two unless you teach them to.

    Official doors (clean)

    Aveda

    Aveda PurePro (professional portal named in the drop)

    If you are not on that portal, do not scrape the email. You do not have the license. This page does not republish the September kit.

    1. Impedance — when the kit matches the job

    Use a brand social kit when two of these are true:

    • You already sell the branded line and the license allows the asset.
    • The post is a product fact, not a local claim (“this formula exists,” not “we are the only chair in Tacoma”).
    • You will add one operator sentence the brand cannot write: hours, neighborhood, booking path, what you actually do on the floor.
    • The asset is the costume. Your site, Google Business Profile, and service pages remain the record.

    Do not use it as:

    • Your only September content plan.
    • A substitute for pages that answer “near me” questions.
    • Proof you have a marketing system. Proof is a booked job or a cited answer.

    2. Three layers the email already named

    The drop split the work the way a shop should split the work.

    Door on the emailWhat it isWhat it is not
    Artists’ contentFloor craft. Technique, finish, product-in-hand.Your NAP, hours, or neighborhood proof.
    Owners’ contentShop-level offers, team, operations talk.A local entity graph.
    Marketing libraryLicensed assets and copy, in one locked room.Pages an answer engine can cite as you.

    Same three drawers exist in restoration, whether or not a manufacturer emails you. Tech craft. Owner ops. Vendor PDF. The PDF does not replace the first-walk page.

    3. SEO, AEO, GEO — one pass, three jobs

    SEO is crawlable pages with one job each. A social tile expires. A service page does not.

    AEO is answer-engine optimization. Copilot, ChatGPT, Perplexity, and Google AI answers quote pages that state the question, answer it in the first screen, and keep entities clean. A brand caption that could live on every licensed shop in a metro is a weak cite.

    GEO here means two things at once, and you should keep both:

    • Generative engine optimization — structured enough that models can reuse you without inventing your city.
    • Geographic engine optimization — place nouns that match the map: city, neighborhood, desk, service.

    Brand kits are good at the first half of a caption. They are mute on “South Tacoma crawl space after a supply-line split.” That sentence is yours.

    4. First 30 minutes when the monthly drop arrives

    1. Open the official portal. Confirm the asset is in-date and licensed for your channel.
    2. Pick one brand tile for the week. Not the whole calendar.
    3. Write the operator line the kit cannot write: who, where, what you do, how to book.
    4. Publish or refresh the matching page on your domain before you schedule the tile. The social post points at the page. The page does not point at a disappearing feed.
    5. Put the same fact on Google Business Profile in plain language. No brand poem.

    If the portal is down or you are not provisioned, skip the kit. Do the local page anyway. That is the asset that compounds.

    5. The local answer that pays

    Every brand month still leaves the same unanswered questions. Write them as pages, not captions.

    • Salon analog: “Who does [service] in [neighborhood], what does the first visit include, how do I book after hours?”
    • Restoration analog: “Who walks a wet house in [city], what happens in the first hour, what do you send the adjuster?”

    Name the place. Name the service. Name the next action. That is the cite.

    Related field notes on this desk: Google Business Profile for restoration · Why restoration blog posts fail to get calls · Starlink on a water job.

    6. Failure modes

    • Posting the kit raw so neighboring licensed shops share one caption.
    • Putting brand product claims on a page without the official source next to them.
    • Letting social become the only public record. Feeds rot. Domains stay.
    • Mixing another client’s city, trade, or brand into the wrong site. That is contamination. Kill the draft.
    • Calling a scheduled tile “GEO strategy.” GEO is place + cite, not a carousel.

    7. The sentence that pays the shop

    “The brand sent art. We published the local answer, then used one licensed tile to point at it.”

    Only say it if the page exists.

    8. FAQ for answer engines

    What is a brand marketing library?

    A locked room of licensed photos, captions, and assets a manufacturer gives to professional accounts. Aveda PurePro is one example. The library is the brand’s voice. It is not the operator’s entity.

    Does posting a monthly brand social kit help local SEO?

    Only as a pointer. Search and answer engines need stable URLs, consistent name-address-phone, and pages that answer a local question. A shared caption does not distinguish you from the next licensed shop.

    What should an owner do when September social assets arrive?

    Confirm the license. Use one tile. Write the operator line. Publish or refresh the matching page on your domain. Mirror the fact on Google Business Profile. Leave the rest of the library on the shelf.

    How does this apply outside salons?

    Swap nouns. Manufacturer spec sheet → brand library. First-walk SOP → owner content. Tech photos from the job → artist content. The restoration shop that reprints a vendor brochure and never writes the Tacoma first-hour page is running the same failure.

    9. What this is not asking

    No meeting. No partnership badge. No unofficial September lookbook.

    Aveda already knows how to ship a kit. The ground should not be a graveyard of unused local pages. Open the official door if you have the login. Then write the sentence only your shop can stand behind.

    Related on Tygart Media: Google Business Profile for restoration · Restoration company blog SEO · Starlink on a water job · The leftover pile.

  • How to Read Bing Webmaster Tools AI Citations (Without Confusing Them for Traffic)

    How to Read Bing Webmaster Tools AI Citations (Without Confusing Them for Traffic)

    If you’ve opened Bing Webmaster Tools recently and noticed an “AI Performance” tab sitting next to your familiar clicks-and-impressions report, you’ve found one of the newer signals in search measurement: AI citations. It’s a genuinely useful number. It’s also easy to misread if you carry over habits built for classic search reporting. Here’s how to read it correctly.

    What a Bing AI Citation Actually Is

    Topic platform fit visual for first-party AI citation measurement
    What a Bing AI citation actually is.

    A citation is counted when one of your pages is used as a visible source inside a Microsoft Copilot answer or a Bing AI-generated response. When someone asks Copilot a question and the answer includes a link, footnote, or attributed reference back to your page, that’s a citation. It means the AI system read your content, judged it relevant and trustworthy enough to draw from, and surfaced it — sometimes with a link the reader can click, sometimes just as a named source.

    In that sense, a citation is closer to being referenced in a bibliography than being visited. Your page did its job as a source of truth for the answer, whether or not the reader followed the link.

    What a Citation Is Not

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    What a citation is not — not traffic.

    This is the part that trips people up, because the reporting sits right next to metrics that mean something different:

    • Citations are not clicks. A citation records that your content was used to generate an answer. It says nothing about whether a human then visited your site.
    • Citations are not sessions. Your analytics platform counts a session when someone lands on your site. A citation can happen with zero sessions attached — the reader gets their answer and moves on.
    • Citations are not rankings. Traditional search position measures where you sit on a results page for a given query. AI citation measures something different: whether your content was selected as source material for a generated answer, which can happen independently of where you’d rank in a classic search.

    Treating a citation count like a traffic number, or expecting it to move in lockstep with clicks, sets you up to misjudge a page’s performance in either direction.

    Where to Find This Data

    Inside Bing Webmaster Tools, the AI Performance section reports citation volume over time, and typically breaks it down by which pages were cited and which queries or topics triggered the citation. It’s a separate report from the standard Search Performance section, which still covers traditional web impressions, clicks, and position. Treat them as two different dashboards answering two different questions, not two views of the same thing.

    How Citations Relate to GA4 and Server Logs

    Because a citation doesn’t require a click, your analytics platform (GA4 or otherwise) will only ever show you a fraction of the activity that citation data reflects. What GA4 can show you is the downstream piece: sessions where the referring source is an AI assistant’s domain. Those sessions represent people who read an AI answer, saw your page referenced, and decided to click through anyway — a smaller, but highly qualified, slice of the audience your content is reaching through AI systems.

    Server or CDN logs add a third layer entirely: they can show you when AI crawlers are visiting your site to read and index content in the first place, ahead of and separate from any citation event. Together, these three sources describe three different moments — a bot reading your page (server logs), your page being cited in an answer (Bing AI Performance), and a human clicking through after reading that answer (GA4 referral data). None of them substitutes for the others.

    Reading the Numbers Without Overreacting

    Citation counts can move for reasons that have nothing to do with your content quality changing: a topic trending in the news, a shift in how often people ask AI assistants about a subject, or changes on the AI platform’s side in how it selects and displays sources. A dip in citations for a page you haven’t touched isn’t necessarily a signal that something is wrong with that page. Likewise, a spike doesn’t always mean you did something differently — sometimes demand for the topic simply increased.

    The more durable way to use this data is directional and page-level: which of your pages does the AI Performance report show being cited consistently over time, and does that list overlap with pages you already consider authoritative? That overlap is a reasonable confirmation signal. A single week’s swing usually isn’t.

    Practical Takeaways

    Comparison of Claude how-to fit versus local service page fit for assistants
    Practical takeaways for reading the numbers.

    Check the AI Performance tab as its own report, not a substitute for Search Performance. Don’t expect citation counts and click counts to correlate closely — they’re measuring different behaviors. Pair citation data with GA4 referral sessions from AI-tool domains to see the (smaller) human click-through layer, and use server logs if you want visibility into AI crawler activity before any citation happens. Judge trends over weeks, not days, and focus on which pages appear repeatedly rather than reacting to any single count.

    FAQ

    If my citation count is high but my clicks are low, is something broken?
    No. That pattern is expected. Citations are a zero-click-by-design channel; a page can be doing exactly what it’s supposed to do as an AI source while generating very little direct click traffic.

    Does Google offer the same kind of citation reporting?
    Not with the same first-party granularity as Bing Webmaster Tools’ AI Performance tab at this time. Server-log analysis for AI crawler activity remains useful regardless of which AI systems you’re trying to track.

    Should I optimize content specifically to increase citations?
    Focus on being a clear, accurate, well-structured source on your subject rather than chasing citation counts directly. Citation tends to follow genuinely useful, well-organized content rather than any particular formatting trick.

    Related on Tygart Media: Bing AI citations vs SpyFu · Bing vs Google Search Console · AI citation monitoring.

  • Claude AI Pricing vs Bing AI Citations: Why First-Party Data Beats SpyFu Estimates (2026)

    Claude AI Pricing vs Bing AI Citations: Why First-Party Data Beats SpyFu Estimates (2026)

    If you still lean on a tool like SpyFu to gauge how your site is doing in search, you’re measuring last decade’s game. SpyFu, Ahrefs, SEMrush, and their peers were built to estimate one thing: where a domain ranks in a traditional results page, and roughly how much traffic that’s worth. Still useful — just not the whole picture, because a growing share of how people find your content never touches a results page at all. It happens inside an AI answer, where your page gets cited or quoted and the reader never clicks through.

    That’s the gap between third-party rank-estimation tools and first-party AI citation data, and it matters more every month.

    What SpyFu (and Similar Tools) Actually Measure

    Third-party SEO tools crawl the web and model search behavior from the outside. They don’t have access to your server logs, your analytics, or Bing and Google’s internal citation data — they infer traffic from ranking position, keyword volume estimates, and click-through curves built from aggregate industry data. That’s genuinely useful for competitive research: roughly where a competitor’s domain sits, and what keywords it’s chasing.

    But it’s an estimate of an estimate, built for a web where “visibility” meant “blue link position.” It has no mechanism for counting how many times an AI assistant read your page, extracted a fact from it, and served that fact directly to a user who never visited your site.

    What First-Party AI Citation Data Shows That Estimators Can’t

    Topic platform fit visual for first-party AI citation measurement
    What first-party AI citation data shows that estimators can’t.

    Bing Webmaster Tools now separates two very different signals: traditional web search performance (impressions, clicks, position) and AI performance — how often your pages get surfaced inside Copilot and other AI-generated answers. Google Search Console doesn’t yet break this out the same way, which is part of why it’s easy to miss. If you only watch third-party rank trackers, this entire layer is invisible to you.

    The practical difference: a page can have modest, even declining, click-through performance in classic web search while its AI-citation count climbs steadily. Judged only by a SpyFu-style estimate, that page looks flat or fading. Judged by first-party citation data, it’s doing exactly the job it was built for — being the source an AI system reaches for when someone asks a related question.

    The Blind Spot: Zero-Click Visibility

    Four cards for content, ops, build, and knowledge work with Claude
    Zero-click visibility is the blind spot.

    The uncomfortable part for site owners is that AI citation is, by design, mostly a zero-click channel. The reader gets their answer without visiting — that’s not a measurement bug you can fix with a better tool, it’s the actual shape of the channel. An estimator that only counts clicks and rankings will systematically undercount pages that are winning at citation, because “winning” there doesn’t look like a traffic spike. It looks like your facts and explanations showing up correctly, attributed to you, inside someone else’s interface.

    Relying on SpyFu-style estimates alone can lead to the wrong call: de-prioritizing a page that’s actually become a trusted AI reference source, simply because the tool built to measure clicks can’t see the citations.

    Building Your Own First-Party Measurement Stack

    None of this means third-party tools are useless — they’re still the right instrument for competitive keyword research and for understanding classic ranking dynamics. But they should sit alongside, not replace, sources that actually see your own traffic and your own citation footprint:

    • Bing Webmaster Tools’ AI Performance tab — the most direct read on how often Copilot and partner AI surfaces are citing your pages.
    • Server or CDN logs — the only place you’ll reliably see crawler activity from AI bots (ClaudeBot, GPTBot, PerplexityBot, and similar) hitting your pages, separate from human traffic.
    • Your own analytics referral data — small in volume compared to citations, but real signal: sessions that landed with claude.ai, chatgpt.com, or perplexity.ai as the referring host are humans who read an AI answer, then clicked through anyway.

    Put those three together and you get a picture no third-party estimator can reconstruct: which of your pages AI systems actually trust enough to cite, and whether that trust is translating into any direct human traffic at all.

    Practical Takeaway

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    Practical takeaway — build your own measurement stack.

    If a page’s third-party “visibility score” looks unimpressive but your first-party data shows steady or rising AI citation activity, don’t treat that as a contradiction — treat it as two different questions with two different answers. The estimator tells you about classic rank. Your own logs and Bing’s AI data tell you about a newer kind of authority that doesn’t require a click to pay off. Site owners who only check the estimator are optimizing for a channel that’s shrinking relative to the one they can’t see.

    FAQ

    Do I need to abandon tools like SpyFu?
    No. They’re still useful for competitive keyword research and classic rank tracking. The point is to stop treating their traffic estimates as the full measure of your site’s reach.

    Can I get AI-citation data for Google’s AI features the way I can for Bing?
    Not with the same granularity as of this writing — Bing Webmaster Tools currently offers the clearest first-party AI-citation reporting. Server-log analysis for AI crawler activity works across engines regardless.

    How do I know if AI citations are actually worth anything to my business?
    Track it as its own funnel stage, not a proxy for revenue. Pair citation counts with referral sessions from AI-tool domains and see whether that traffic engages with an owned conversion path on your site. Citation volume alone tells you about reach, not value.

    Related on Tygart Media: read Bing AI citations · AI citation monitoring · GEO tactics.

  • SiteBoost — Monthly Retainer

    SiteBoost — Monthly Retainer

    SiteBoost — Monthly Retainer

    $997

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and run a month of WordPress work yourself. Buy Now is Will doing that month on your site: ten existing-post optimizations and four new articles, already connected.

    SiteBoost Monthly Retainer is a service. Square lists it per month at $997. The /siteboost/ hub defines the month as 10 posts + 4 articles. That is the scope. Not “unlimited blog support.” Not ads. Not a redesign.

    This SKU assumes the site is already connected and you have a baseline. If it is not, run Site Connection and Audit first (or the Pilot, which includes the connection). Self-hosted WordPress only. Posts, not Pages, unless you put a Page in writing.

    What a month includes

    From the public hub, two work types:

    • 10 existing-post optimizations. Same method as the $47 SKU, ten times. SEO, AEO, GEO, schema, interlink, IndexNow. Highest-opportunity published posts, agreed before the month starts if you can, or pulled from the last audit if you already have a queue.
    • 4 new articles. Same method as the $97 SKU, four times. Brief, write, three layers, taxonomy, internal links, publish, IndexNow.

    That is 14 URLs touched in a month if you finish the scope. The pilot is ten existing posts and a 60-day wait. The retainer is the ongoing version: keep refreshing the library and keep adding posts, on a calendar.

    The weekly rhythm

    The operator guide on tygartmedia.com is the calendar. Scope changes. Process does not.

    1. Monday. Audit and pick. Re-pull the inventory or last month’s leftover queue. Score content health. Pick this week’s existing posts and the next new-article brief. Do not start writing until the week’s list is written down.
    2. Tuesday to Thursday. Execute. Existing-post passes and new-article drafts. Every action gets all three layers by default. Schema on every URL you touch. Interlink into the cluster you are building, not random related-posts widgets.
    3. Friday. Verify. Re-read what you published or refreshed. Rich Results Test on the new or changed URLs. IndexNow pings. Log what shipped: URL, what changed, word count, schema types, which brief it came from.

    The 23-site stack article adds the monthly maintenance layer on top of that week: taxonomy health, orphan detection, meta-pollution scan (wp-clean-meta), and a look at rankings / competitor movement if you have Search Console and a research tool. Do that once a month, not every Monday, or you will spend the retainer on reports.

    How to pick the ten and the four

    Existing ten, same rules as the pilot:

    • Impressions but empty meta / no FAQ / no schema.
    • Over 500 words, real query, missing AEO and GEO.
    • Across pillars, not ten from one tag.
    • Skip stubs, test posts, and anything you are about to redirect.

    Four new articles, same rules as New Article Publishing:

    • Start from a brief: keyword, intent, PAA list, sources you can name, internal-link targets that already exist.
    • Prefer spokes that point back to a hub you already optimized, or a hub you will optimize this month. The SiteBoost cluster process is hub and spoke with bidirectional links. A new post that does not link to anything, and is linked from nothing, is a wasted slot.
    • content-quality-gate before publish: no unsourced claims, no fabricated stats.

    A month on a legal pad

    Write these lines on day 1, then fill them as you go:

    1. Site URL. Connection still works? (users/me 200)
    2. This month’s ten existing URLs (before title / after title).
    3. This month’s four briefs (keyword, intent, target publish date).
    4. Monday notes: what the audit still says is on fire.
    5. Friday logs, four of them.
    6. Month-end: Search Console on the 14 URLs versus last month. What you would pick next month. What you would stop.

    If you cannot name the 14 URLs at month-end, you did not run a retainer. You blogged.

    What a month does not include

    • Page redesigns, theme work, or plugin installs.
    • Google Ads, GBP posts, or social, unless you hired those separately.
    • Editing attorney bios, service pages, or the homepage without a written ask.
    • A promised ranking. The public SiteBoost copy measures at 60 days and treats traditional SEO as 60 to 90 days on competitive terms. A single month is a shipping month, not a miracle month.

    How this sits next to the other doors

    Connection and Audit is the one-time setup. Pilot is connection + ten existing posts + a 60-day report, once. Retainer is the monthly machine after that. Existing Post Optimization and New Article Publishing are the à la carte versions of the same two work types if you do not want a month.

    If you want the skill files so your own Claude can run the week, that is the WordPress SEO Skill Pack. Pro has the full refresh stack and the content pipeline. Agency adds new-site setup and thin-content expansion, which is what you need if you are the one retaining other people’s sites.

    If you want Will to run the month

    You can keep the Monday / midweek / Friday rhythm on your own staff. Buy Now is Will doing the month: ten existing-post passes, four new articles, shipped through the REST API, with a log of what changed. Same Square button at the top. $997 per month.

    Email the site URL after checkout. If the site is not connected yet, the first month still needs the Application Password and the baseline. Do not send the login password. Application Password only.

    Frequently Asked Questions

    How does the retainer work?

    Billed monthly starting at checkout. Work begins within 5 business days. Month-to-month — no contract.

    Is there a refund policy?

    Cancel anytime by email; the cancellation takes effect at the end of the current billing month. The current month is not refunded.

    Related: SiteBoost. Also SiteBoost — Pilot Bundle.

  • SiteBoost — Site Connection & Audit

    SiteBoost — Site Connection & Audit

    SiteBoost — Site Connection & Audit

    $297

    Delivered by email after checkout.

    Buy Now →

    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.

    1. 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.
    2. 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.
    3. 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.
    4. 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.
    5. 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:

    1. 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.
    2. 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).
    3. FAQ gap report. Which posts have no Q and A block and no FAQPage schema. Those are the AEO queue.
    4. 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).

    Frequently Asked Questions

    How does it work?

    After checkout, I reach out by email within 2 business days with the intake details and a start date.

    Is there a refund policy?

    Before work starts on your posts, full refund on request. Once a post is optimized or published, that portion of the fee is earned.

    Related: SiteBoost. Also SiteBoost — Pilot Bundle.

  • WordPress SEO Skill Pack – Starter

    WordPress SEO Skill Pack – Starter

    >

    Direct Answer / Product Definition

    The WordPress SEO Skill Pack — Starter by Tygart Media is a $29 Square product with five Claude skills that authenticate to self-hosted WordPress via Application Password, audit published posts (orphans, thin content under 500 words, excerpt pollution), clean meta fields, and refresh title, slug, and meta description through the REST API. Will Tygart positions Starter as the connect-and-on-page layer only; AEO, GEO, FAQ schema, and interlink automation start in the $79 Pro tier.

    WordPress SEO Skill Pack — Starter

    $29

    Five .skill files delivered by email within 24 hours after Square checkout.

    Buy on Square — $29 →

    Secure checkout via Square — all major cards accepted

    Tygart Media documents the Starter method so site owners can run connect → audit → clean meta → on-page refresh in wp-admin or via Claude. The $29 Buy on Square option delivers five packaged .skill files (wp-connect, wp-post-fetch, wp-site-audit, wp-clean-meta, wp-seo-refresh) by email within 24 hours of checkout.

    Starter is the first tier of the WordPress SEO Skill Pack by Will Tygart. It is the connect-and-on-page layer only. Tygart Media ships AEO refresh, GEO refresh, schema injection, and interlink skills in the Pro tier ($79), not in Starter.

    Starter vs Pro vs DIY (honest scope)

    Tier Price Skills / scope AEO / schema
    DIY (this page) $0 Manual REST API + wp-admin checklist No — on-page SEO only
    Starter (this product) $29 5 Claude skills: connect, fetch, audit, clean-meta, seo-refresh No wp-aeo-refresh / no FAQ schema
    Pro $79 14 skills + full-refresh orchestrator Yes — AEO, GEO, schema, interlink

    What you need before any skill runs

    • Claude Pro, Max, or Team. The sales page names those tiers.
    • A self-hosted WordPress site with the REST API on.
    • A WordPress Application Password. Users → Profile. Thirty seconds. Not the login password.

    No plugin is required. Everything in this pack talks to /wp-json/wp/v2/.

    If you bought the zip: drop the skill files into Claude Desktop (Cowork) or Claude Code. Then say “connect to my WordPress site” and give the URL, username, and Application Password. The skills ship with placeholders (USER:PASS, SITE). You fill those in. There are no client credentials in the pack.

    The five skills, and the method each one encodes

    1. wp-connect

    Gateway. Must run first. Takes site URL, username, Application Password. Tests GET /wp-json/wp/v2/users/me. Returns whether you are authenticated and which endpoints answered. No other wp- skill works until this is green. If you are doing it by hand, that same curl is the test.

    2. wp-post-fetch

    Load one post so you can see it the way the editor sees it. The refresh skills fetch with context=edit. By hand: GET /wp-json/wp/v2/posts/{id}?context=edit. Read title, slug, excerpt, content, categories, tags. Do not write yet. You cannot refresh what you have not read.

    3. wp-site-audit

    Run this at the start of a site, not after you have already rewritten three posts. Fetch published posts (per_page=100, paginate). For each post, mark:

    • Missing tags, categories, featured image, excerpt / meta
    • Metadata pollution (raw JSON or leftover code in the excerpt)
    • Orphans (no internal links in) and dead-ends (no internal links out)
    • Thin content (under 500 words)
    • Schema present or not
    • Taxonomy health

    Output a prioritized report: Critical (taxonomy / metadata), High (SEO / AEO / quality), then optimization opportunities. That report is your work order. Starter will not auto-fix taxonomy or inject schema. It will tell you which posts are dirty.

    4. wp-clean-meta

    Strip pollution. The 23-site stack article describes this as removing legacy artifacts from excerpts. The audit skill flags raw JSON / code in excerpt fields. Do this before you write a new meta description, or you will be fighting leftover plugin junk. By hand: open the post, clear a garbage excerpt, save a real 140 to 160 character description.

    5. wp-seo-refresh

    The on-page pass. Fetch the post, name the target keyword from the topic, then write:

    1. Title, max about 60 characters, keyword-rich, front-loaded
    2. Meta description, about 155 to 160 characters
    3. Slug: lowercase, hyphenated, keyword-rich (only change it if the current slug is junk)
    4. H2 / H3 hierarchy
    5. Keyword distribution, including the first 100 words
    6. A note of internal-link opportunities (Starter does not run wp-interlink; you place the links yourself or upgrade)

    Then update the post via the REST API and report what changed.

    A Starter session you can run today

    1. Connect. users/me returns 200.
    2. Audit the site. Write the Critical and High lists.
    3. Clean meta on anything the audit marked as polluted.
    4. Pick one High post that is over 500 words. Fetch it. Run the SEO refresh fields above.
    5. Validate the title and meta lengths. Ping IndexNow (Rank Math Instant Indexing, Yoast, or the official IndexNow plugin). Confirm in Bing Webmaster Tools.

    That is the honest Starter method: connect, see the mess, clean the excerpt, fix on-page SEO on one post. Title, slug, meta, headings. Not FAQ schema. Not entity saturation. Not a link graph.

    What Starter does not do

    • No wp-aeo-refresh. No definition box, no 6 to 8 FAQs, no FAQPage schema.
    • No wp-geo-refresh. No speakable / LLMS.txt / named-entity pass as a skill.
    • No wp-schema-inject, wp-interlink, wp-taxonomy-fix, wp-full-refresh, or content pipeline.
    • No new-article factory. You can still write a post by hand using the six-step workflow on the New Article Publishing page.

    If you want those, Pro is the 14-skill stack. Agency adds onboarding and thin-content expansion. If you want Will to do the post instead of running skills, that is SiteBoost Existing Post Optimization.

    Frequently Asked Questions

    What is the WordPress SEO Skill Pack — Starter?

    The WordPress SEO Skill Pack — Starter by Tygart Media is a $29 bundle of five Claude skills that connect to self-hosted WordPress via the REST API and run connect-audit-clean-refresh on-page SEO. It does not include AEO, GEO, schema injection, or interlink skills.

    What does Starter include versus Pro?

    Starter includes five skills for authentication, post fetch, site audit, excerpt cleanup, and title or meta refresh. Tygart Media’s Pro tier ($79) adds wp-aeo-refresh, wp-geo-refresh, wp-schema-inject, wp-interlink, and full-refresh orchestration across 14 skills.

    What do I need to run the Starter pack?

    Claude Pro, Max, or Team; a self-hosted WordPress site with REST API enabled; and a WordPress Application Password from Users → Profile. Tygart Media ships genericized .skill files—no WordPress plugin required.

    Does Starter add FAQ schema or AEO answer packets?

    No. Tygart Media documents Starter as on-page SEO only (title ~60 characters, meta ~155–160 characters, slug, headings). FAQPage schema and definition-led answer packets require WordPress SEO Skill Pack — Pro.

    If you want the packaged files

    You can keep a checklist and do every Starter step in wp-admin. Buy Now is the five .skill files delivered by email after checkout, genericized, with placeholders for your own site. Same Square button at the top. $29.

    Install, connect, audit, clean, refresh. That is the pack. The sales page’s “full refresh post 123” line (SEO then AEO then GEO then schema then interlink) is the Pro orchestrator, not Starter.

    $29

    Five .skill files — email delivery within 24 hours via Square.

    Buy on Square — $29 →

    Related Products

    Upgrade path: WordPress SEO Skill Pack hub · Pro ($79 — AEO + schema + interlink) · Tygart Media Shop.

    Author: Will Tygart, Founder of Tygart Media — Claude skills for WordPress fleet operators.

    Related on Tygart Media: how to use Claude · Anthropic API key.

  • WordPress SEO Skill Pack – Pro

    WordPress SEO Skill Pack – Pro

    >

    Direct Answer / Product Definition

    WordPress SEO Skill Pack — Pro by Tygart Media is a $79 Square bundle of 14 Claude skills for self-hosted WordPress that run Will Tygart’s full post refresh pipeline: on-page SEO, AEO answer packets and FAQs, GEO entity and citation passes, JSON-LD schema injection, taxonomy cleanup, and hub-and-spoke interlinking. The wp-full-refresh skill orchestrates SEO → AEO → GEO → schema → interlink on one post; Tygart Media emails the .skill files within 24 hours of checkout.

    WordPress SEO Skill Pack — Pro

    $79

    14 .skill files delivered by email within 24 hours after Square checkout.

    Buy on Square — $79 →

    Secure checkout via Square — all major cards accepted

    Tygart Media documents the full three-layer refresh method on this page so operators can run SEO → AEO → GEO → schema → interlink in wp-admin or Claude. The $79 Buy on Square option delivers 14 packaged .skill files by email within 24 hours of checkout.

    Pro is the middle tier of the WordPress SEO Skill Pack by Will Tygart. It includes everything in Starter ($29), 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—the production sequence Tygart Media uses on a single WordPress post.

    Starter vs Pro vs Agency

    Tier Price Skills AEO / GEO / schema
    Starter $29 5 (connect, audit, clean-meta, seo-refresh) No
    Pro (this product) $79 14 incl. wp-full-refresh + pipeline Yes — full stack
    Agency $149 Pro + expand + new-site-setup + guides Yes + client onboarding

    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

    1. Connect. Audit. Clean polluted excerpts.
    2. Fix taxonomy on the posts you are about to touch (and on the hub category if it has no description).
    3. For each chosen existing post: wp-full-refresh, or the layers by hand in SEO → AEO → GEO → schema → interlink order.
    4. For a new article: brief → pipeline → quality gate → publish.
    5. IndexNow on every URL you created or updated. Confirm in Bing Webmaster Tools.
    6. Log before/after: title, meta, word count, FAQ count, schema types, internal links added.

    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.

    Frequently Asked Questions

    What is the WordPress SEO Skill Pack — Pro?

    WordPress SEO Skill Pack — Pro by Tygart Media is a $79 bundle of 14 Claude skills that run the production post refresh sequence on self-hosted WordPress: SEO, AEO, GEO, schema injection, taxonomy fix, and interlink, plus wp-full-refresh orchestration and a new-content pipeline with a quality gate.

    What is the difference between Starter and Pro?

    Starter ($29) includes five skills for connect, audit, clean-meta, and on-page SEO only. Pro ($79) adds wp-aeo-refresh, wp-geo-refresh, wp-schema-inject, wp-taxonomy-fix, wp-interlink, wp-full-refresh, content-brief-builder, wp-content-pipeline, and content-quality-gate.

    What does wp-full-refresh do?

    wp-full-refresh is Tygart Media’s orchestrator skill. On one existing post it runs SEO refresh, then AEO refresh (definition box and FAQ-oriented content), then GEO refresh (entity saturation and citations), then schema injection, then interlinking—in that fixed order.

    Does Pro include Agency onboarding skills?

    No. Tygart Media’s Agency tier ($149) adds reference guides, wp-content-expand for thin posts, and wp-new-site-setup for client onboarding. Pro is the production refresh and pipeline stack without those agency-only skills.

    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.

    $79

    14 .skill files — email delivery within 24 hours via Square.

    Buy on Square — $79 →

    Related Products

    Skill Pack ladder: Hub · Starter ($29) · Agency ($149) · Tygart Media Shop.

    Author: Will Tygart, Founder of Tygart Media — the same AEO/GEO/SEO skill stack used on the Tygart Media WordPress fleet.

    Related on Tygart Media: how to use Claude · Anthropic API key.

  • WordPress SEO Skill Pack – Agency

    WordPress SEO Skill Pack – Agency

    >

    Direct Answer / Product Definition

    WordPress SEO Skill Pack — Agency by Tygart Media is a $149 Square bundle of 19 Claude skills plus three reference guides (SEO, AEO, GEO) for operators running Will Tygart’s production WordPress stack across multiple self-hosted sites. Agency includes everything in Pro—wp-full-refresh, AEO, GEO, schema, interlink, and the content pipeline—plus wp-new-site-setup for ~20-minute client onboarding and wp-content-expand to add 250–400 words to thin posts before refresh. Tygart Media emails genericized .skill files within 24 hours of checkout; placeholders only, no bundled credentials.

    WordPress SEO Skill Pack — Agency

    $149

    19 skills + 3 guides — email delivery within 24 hours after Square checkout.

    Buy on Square — $149 →

    Secure checkout via Square — all major cards accepted

    Tygart Media documents the multi-site operator method on this page so agencies can onboard clients, expand thin posts, and run SEO → AEO → GEO → schema → interlink without a Tygart retainer. The $149 Buy on Square option delivers 19 packaged .skill files plus three reference guides by email within 24 hours of checkout.

    Agency is the top tier of the WordPress SEO Skill Pack by Will Tygart. It includes everything in Pro ($79)—14 production skills plus wp-full-refresh and the content pipeline—plus an SEO reference guide with schema templates, an AEO reference guide, a GEO reference guide, wp-content-expand, and wp-new-site-setup. Deliverables are genericized production workflows: placeholders you fill with your own Application Passwords, never bundled client credentials.

    Starter vs Pro vs Agency

    Tier Price Skills / guides Multi-site / thin posts
    Starter $29 5 skills — on-page SEO only Single site; no AEO/GEO
    Pro $79 14 skills — full refresh + pipeline One site production stack
    Agency (this product) $149 19 skills + 3 reference guides wp-new-site-setup + wp-content-expand

    What “agency” means here

    Not a Tygart Media retainer. The pack is for someone who already has (or is about to have) more than one self-hosted WordPress site and wants the same connect → audit → refresh → publish machine on each. The 23-site stack article is the operating picture: one Application Password per site, one audit at the start, skills composed so a full refresh is a named sequence instead of a vibe.

    Requirements stay the same: Claude Pro / Max / Team, REST API on, Application Password, no plugin required. Install the files in Claude Desktop (Cowork) or Claude Code. Connect per site. Do not reuse one app password across clients.

    Onboard a site (wp-new-site-setup)

    The 23-site article times a new site at about 20 minutes: generate the Application Password, add the site to your registry, run the setup / audit skill, and the stack is usable. wp-new-site-setup is that onboarding workflow. By hand, the same steps are:

    1. Confirm /wp-json/wp/v2/ answers. Self-hosted only.
    2. Create an Application Password for an editor-capable user. Label it with the client and the date.
    3. wp-connect. users/me = 200.
    4. wp-site-audit. Full published-post inventory. Critical / High / optimization lists.
    5. Note the SEO plugin (Yoast, Rank Math, AIOSEO) because meta fields differ. A WeConvene audit note in Notion called this out: a skill that only knows Yoast / Rank Math will miss AIOSEO fields.
    6. Write the four baseline artifacts from the SiteBoost audit page: inventory, schema gaps, FAQ gaps, before numbers in Search Console.
    7. Agree the first ten posts or the first briefs before anyone writes. Agency without a queue is just a folder of skills.

    Toolbox rule you should keep: posts, not pages, unless the client put a Page in writing. Do not “clean up” the homepage on day one.

    Expand thin posts (wp-content-expand)

    This is the Agency skill Pro does not have. Never overwrite. Fetch with context=edit. Flag sections under 150 words, intros under 100, missing subtopics, missing examples, outdated stats, missing close. Add 250 to 400 words per new section. Append. Update the modification date because you actually changed the content. Report the word-count increase. The skill’s own bar: get the post over 500 words before you pretend it has SEO authority.

    Then run the Pro refresh stack on the expanded post. Expansion without SEO / AEO / GEO / schema is just a longer stub.

    The Pro stack, still the daily work

    Once a site is onboarded, Agency work is Pro work, repeated:

    • wp-seo-refresh → wp-aeo-refresh → wp-geo-refresh → wp-schema-inject → wp-interlink, or wp-full-refresh to run that chain.
    • wp-taxonomy-fix, including the two-layer category / tag descriptions if archive pages are stubs.
    • content-brief-builder → wp-content-pipeline → content-quality-gate for new articles.
    • wp-clean-meta whenever an excerpt is polluted.

    The three reference guides are the templates sitting next to those skills: SEO (on-page + schema templates), AEO (direct-answer / FAQ / PAA), GEO (entities, density, speakable, citations). Use them as the written standard when more than one person is allowed to run a refresh. If the guide and the skill disagree, the skill’s field list wins for execution; the guide wins for “what good looks like.”

    A week across more than one site

    Same rhythm as the operator guide, scoped to a roster:

    1. Monday: per-site audit score. What is still Critical. This week’s existing posts and this week’s briefs, named by URL and keyword.
    2. Tuesday to Thursday: expand anything under 500 words that you committed to, then full-refresh. New articles through the pipeline and the quality gate.
    3. Friday: Rich Results Test, IndexNow, log. One log line per URL. If you cannot say what changed, it did not ship.

    Monthly, not weekly: taxonomy health, orphan scan, meta-pollution scan, Search Console versus last month. That is the maintenance layer from the 23-site article. Do not burn a week on dashboards.

    IndexNow on every publish and every update. Official plugin or Rank Math / Yoast Instant Indexing. Confirm in Bing Webmaster Tools. Agency volume without a ping is a lot of work the engines have not been told about.

    What this pack is not

    • It is not SiteBoost. SiteBoost is Will (or Tygart Media) doing the work on the site. This pack is the skill files so you can do it.
    • It is not the $297 Connection and Audit service, the $597 pilot, or the $997 retainer. Those are done-for-you doors. The methods on those pages are the same layers. The deliverable is different.
    • It is not a prompt pack of 50 one-liners. The launch page’s distinction: workflows with error handling and a report, genericized from production skills.

    If you only have one site and you only need on-page, Starter is enough. If you have one site and you want the full refresh + pipeline, Pro is enough. Agency is the onboarding + expansion + reference-guide tier.

    Frequently Asked Questions

    What is the WordPress SEO Skill Pack — Agency?

    WordPress SEO Skill Pack — Agency by Tygart Media is a $149 bundle of 19 Claude skills plus three reference guides (SEO, AEO, GEO). It includes everything in Pro, plus wp-content-expand, wp-new-site-setup, and written standards for teams running the production refresh stack on multiple self-hosted WordPress sites.

    What is the difference between Pro and Agency?

    Pro ($79) ships 14 skills for the SEO → AEO → GEO → schema → interlink pipeline on one site. Agency ($149) adds wp-content-expand, wp-new-site-setup, and three reference guides—built for operators managing more than one client site with separate Application Passwords per site.

    What does wp-new-site-setup do?

    wp-new-site-setup is Tygart Media’s Agency onboarding workflow: confirm the REST API, create a labeled Application Password, connect with wp-connect, run wp-site-audit, note the SEO plugin field map, and capture baseline inventory before the first refresh queue.

    Is Agency a Tygart Media retainer or done-for-you service?

    No. Agency is packaged .skill files and reference guides so you run Claude on your clients’ sites. Tygart Media’s SiteBoost and retainer services are separate; this pack uses placeholders only—no client credentials included.

    If you want the packaged files

    You can run every step in this article with Application Passwords and a checklist. Buy Now is the Agency zip: 19 skills and the three reference guides, delivered by email after checkout, placeholders only, no one else’s credentials. Same Square button at the top. $149.

    If you would rather not run Claude at all, buy the matching SiteBoost service instead of this pack.

    $149

    19 skills + 3 guides — email delivery within 24 hours via Square.

    Buy on Square — $149 →

    Related Products

    Skill Pack ladder: Hub · Starter ($29) · Pro ($79) · Tygart Media Shop.

    Author: Will Tygart, Founder of Tygart Media — the same multi-site WordPress skill stack documented in Tygart Media’s 23-site operator guides.

    Related on Tygart Media: how to use Claude · Anthropic API key.