Tag: GEO

  • 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

    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.

  • Zero-Click Marketing: How to Optimize Yo (2026)

    Zero-Click Marketing: How to Optimize Yo (2026)

    Last refreshed: August 2026

    68% of U.S. Google searches end without a click in 2026. When AI Overviews appear, that rate hits 83%. The question for content-driven businesses is no longer how to rank — it’s how to be cited inside the answer that replaced the click.

    This is a practical guide to structuring content, managing brand entity signals, and measuring visibility in a world where users get their answer before they ever reach your site.


    What Zero-Click Actually Means for Content Businesses

    Two cards: answer shown in overview versus optional click
    What zero-click actually means for content businesses.

    Zero-click doesn’t mean zero value. Brands cited inside AI Overviews earn 35% more organic clicks than uncited brands on the same query. The traffic goes to the cited brand — not to the site that ranks #1 but isn’t cited.

    The data that reframes zero-click as a competition problem, not a traffic problem:

    • 68% of U.S. Google searches are zero-click in 2026 (SparkToro/Similarweb)
    • When AI Overviews appear, zero-click rate hits 83%
    • Organic CTR for position #1 drops up to 58% when AI Overviews are present (Ahrefs, December 2025)
    • Brands cited in AI Overviews earn 35% more organic clicks and 91% more paid clicks versus uncited brands
    • AI-referred visitors convert at 4.4x the rate of traditional organic visitors (Semrush)
    • The overlap between top-10 rankings and AI Overview citations: 17–38% in early 2026, down from 75% in mid-2025

    The conclusion: ranking is no longer sufficient for visibility. A site can rank #1 and not be cited in the AI Overview that answers the query. The two need to be optimized separately.


    How AI Overviews Decide What to Cite

    Comparison of Claude how-to fit versus local service page fit for assistants
    How AI overviews decide what to cite.

    Google’s AI Overview system retrieves web pages in real time, synthesizes a 3–5 sentence answer, and cites 3–6 source pages. The selection criteria weight answer extractability, entity authority, freshness, and structured data — not just ranking position.

    The signals that influence AI Overview citation:

    Answer extractability: The answer to the query must appear in the first 200 words of the page, stated directly. Pages that build toward the answer, providing extensive context before the conclusion, are retrieved for topic relevance but can’t be cited because the extractable answer isn’t there.

    Entity authority: Consistent, factually accurate information about the brand entity across the web — site, LinkedIn, social profiles, third-party mentions — signals that the source is authoritative on the topic. AI systems treat entities with strong external corroboration as more trustworthy.

    Freshness: For fast-changing topics (Claude pricing, AI model capabilities, regulatory changes), recency is a significant weight. A page last updated in 2024 competes poorly against one updated in August 2026 on a query about current Claude pricing.

    Structured data: FAQPage, HowTo, and Article schema markup signals to Google that content is formatted for extraction. Pages with properly implemented schema see measurably higher AI Overview inclusion.

    E-E-A-T signals: Experience, expertise, authoritativeness, trustworthiness. An article written by a named author with a consistent byline and external presence outperforms anonymous content on contested or technical topics.


    Strategy 1: Structure Every Page for Extraction

    Four cards for content, ops, build, and knowledge work with Claude
    Structure every page for extraction.

    Answer-first structure is the single highest-leverage change for AI citation rates. The first paragraph of every article should directly and completely answer the likely query.

    The structure AI systems can extract from:

    H1: [Specific, query-answering title]
    
    [Bold one-sentence direct answer to the query implied by the title]
    
    [Supporting detail — the why, the how, the context]
    
    H2: [First subtopic as a question]
    [Bold answer sentence to the H2 question]
    [Elaboration]
    

    What this means in practice for tygartmedia.com content:

    Every article about Claude pricing, model capabilities, or Anthropic history should open with the factual answer — not a framing sentence, not background, not “in this article we’ll cover.” The answer, stated directly, in the first two sentences.

    The reason this matters beyond GEO: it’s also better for users. Answer-first structure is a discipline that makes content more useful and more likely to be cited. The SEO and GEO benefits are secondary to the writing quality improvement.


    Strategy 2: Build and Maintain the Brand Entity

    AI systems treat brands as entities — named things with verifiable, consistent information across multiple authoritative sources. Building entity authority means making sure that information is consistent, correct, and present everywhere crawlers look.

    Entity checklist for tygartmedia.com:

    On-site signals:

    • Organization schema on every page (name, URL, description, logo, founder, sameAs links)
    • Consistent author byline (“Will Tygart”) on every article
    • Author bio that establishes expertise consistently across all articles
    • Contact and about page with complete, factual business information

    Off-site signals:

    • LinkedIn Company Page with consistent description matching the website
    • Google Business Profile (if applicable) with consistent NAP (name, address, phone)
    • Third-party mentions and citations on authoritative sites in the AI/tech space
    • Social profiles with consistent handles and descriptions

    The consistency requirement: AI systems cross-reference. If the description on LinkedIn says “AI infrastructure for operators” and the website says something different, that inconsistency weakens the entity signal. Everything should say the same thing about the same thing.


    Strategy 3: Implement Structured Data

    FAQPage, Article, and Organization schema markup signals to AI Overviews that content is formatted for extraction. This is not optional in 2026 for sites that depend on search visibility.

    Minimum structured data implementation:

    FAQPage schema on every article with a FAQ section:

    {
      "@context": "https://schema.org",
      "@type": "FAQPage",
      "mainEntity": [{
        "@type": "Question",
        "name": "What is Metricool pricing?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Metricool has a free plan and paid plans starting at the Starter tier. API access requires the Advanced plan or above. Pricing is per brand, not per connected social account."
        }
      }]
    }
    

    Article schema on all editorial content (author, published date, modified date, headline).

    Organization schema site-wide (name, URL, logo, founder, sameAs).

    In Rank Math (the plugin on tygartmedia.com): FAQ blocks in the WordPress editor generate FAQPage schema automatically. Use the Rank Math FAQ block for all FAQ sections rather than plain text. Article schema is enabled site-wide in Rank Math settings.


    Strategy 4: Keep Content Current

    AI retrieval systems weight freshness heavily for fast-changing topics. For any site publishing Claude pricing, model capabilities, or AI tool features, stale content is not just less useful — it actively loses citation ground to fresher sources.

    Freshness implementation:

    • “Last refreshed” date at the top of every article — visible to users and read by crawlers as a freshness signal
    • “What’s new” section in evergreen articles covering frequently updated topics (Claude pricing, model capabilities, Metricool features)
    • Update the modified date in Article schema whenever content is refreshed — not just the publication date
    • Monitor Search Console for queries where the site appears in AI Overviews — freshness issues show up as drops in citation before they show up as ranking drops

    Trigger list for mandatory refreshes on tygartmedia.com:

    • Any Anthropic pricing change
    • Any new Claude model release or deprecation
    • Any Metricool feature update
    • Any change to Anthropic’s Enterprise product structure

    Strategy 5: Earn Third-Party Citations

    AI systems give extra weight to content cited by other authoritative sources. Being linked to or mentioned by other sites publishing on Claude, Anthropic, and AI infrastructure strengthens the entity signals for all related queries.

    Practical approaches:

    Original data and research: Content with specific numbers, benchmarks, and original findings gets cited by others. The Claude pricing breakdowns, benchmark comparisons, and API cost calculations on tygartmedia.com are exactly the type of content other AI publications cite.

    First-mover coverage: Publishing accurate, detailed coverage of Anthropic announcements before or alongside other publications builds a citation pattern over time.

    Expertise-signal content: Content that can only be written from operational experience — running 24 brands in Metricool, building vector DB systems for business documents — earns citations because it’s not replicable from Anthropic’s documentation alone.


    Measuring Zero-Click Performance

    Standard click and session metrics are insufficient for measuring zero-click visibility. The right metrics are AI citation rate, branded search volume trend, and AI-referred conversion rate.

    Measurement framework:

    MetricToolWhat It Measures
    AI Overview appearancesGoogle Search Console (AIO report)Queries where site is cited
    CTR on AIO queriesGSC, filter by AI Overview queriesWhether citations drive clicks
    AI-referred trafficGA4 source filter (ChatGPT, Perplexity)Direct traffic from AI citations
    Branded search volumeGSC, filter by brand termsAwareness from zero-click exposure
    Conversion rate from AI sourcesGA4 segmented by sourceValue of AI citation traffic

    Manual testing protocol: Monthly, ask ChatGPT, Perplexity, and Claude the questions your audience asks — “what is Claude Enterprise pricing,” “how does Metricool API work,” “what is the history of Anthropic” — and record whether tygartmedia.com is cited. This is the most direct feedback loop available and costs nothing.

    If branded search volume is growing while organic clicks are flat or declining, the site is appearing in AI summaries and building awareness without receiving credit in standard traffic metrics. That’s the zero-click pattern working in favor of the brand — and the signal that citation strategy is working.


    Frequently Asked Questions

    What is zero-click search?

    Zero-click search is a search that ends on the results page itself — the user gets their answer from an AI Overview, featured snippet, or knowledge panel and doesn’t click through to any website. In 2026, 68% of U.S. Google searches are zero-click.

    Does zero-click hurt all websites equally?

    No. Sites cited inside AI Overviews and featured snippets earn 35% more organic clicks than uncited sites on the same query. Zero-click hurts uncited sites and benefits cited ones. The competition shifts from ranking to citation.

    What is the difference between GEO and zero-click optimization?

    GEO (Generative Engine Optimization) is the discipline of getting cited inside AI-generated answers from ChatGPT, Perplexity, Gemini, and Claude. Zero-click optimization is specifically about Google search — being cited in AI Overviews and featured snippets. They use the same underlying tactics (answer-first structure, entity signals, structured data, freshness) applied to different surfaces.

    How long does it take to see results from zero-click optimization?

    Plan for 3–6 months of consistent effort before citation rates change meaningfully. AI systems update their citation patterns as they re-index updated content. The fastest wins come from freshness updates on existing high-traffic pages and FAQ schema implementation on pages that already rank.

    Do clicks from AI citations convert differently?

    Yes — significantly. AI search visitors convert at approximately 4.4x the rate of traditional organic visitors (Semrush). The mechanism is intent: users who get a specific answer from an AI Overview and then click through to the cited source are further along in their decision process than typical organic visitors.


    What to Read Next

    Generative Engine Optimization (GEO): 5 Ways to Ensure Your Content Is Cited by AI Overviews 

    History of Anthropic

    Claude AI Pricing — All Plans and API Rates

     Metricool Review 2026: The Social Media Tool for Multi-Brand Operations

  • Generative Engine Optimization (GEO): 5 Ways to Ensure Y (2026)

    Generative Engine Optimization (GEO): 5 Ways to Ensure Y (2026)

    Last refreshed: August 2026

    GEO — Generative Engine Optimization — is the practice of structuring content so that AI answer engines (ChatGPT, Perplexity, Google AI Overviews, Gemini, and Claude) cite it in the answers they generate. In 2026, 68% of U.S. Google searches end without a click. Being cited in the answer that appears is now as important as ranking in the links below it.

    This guide covers what GEO is, how it differs from traditional SEO, and five specific tactics that move citation rates — with particular relevance for sites publishing Claude and AI authority content.


    Why GEO Matters in 2026

    Comparison of Claude how-to fit versus local service page fit for assistants
    Why GEO matters — citations are the new first page.

    AI Overviews reduce organic click-through rate for the #1 ranked result by up to 58% (Ahrefs, December 2025) — but brands cited as sources within AI Overviews earn 35% more organic clicks than uncited brands on the same query.

    The counterintuitive finding: zero-click is bad for uncited sites and good for cited ones. The goal is not to fight AI Overviews — it’s to be inside them.

    The market data context:

    • 68% of U.S. Google searches are zero-click in 2026, up from 60% in 2024
    • When AI Overviews appear, the zero-click rate jumps to 83%
    • Visitors arriving from AI citations convert at 4.4x the rate of traditional organic visitors
    • The GEO market is projected at $365M in 2026, growing at 42.9% CAGR

    The mechanism: AI search users arrive with specific, researched queries and a pre-formed shortlist. That intent profile makes them higher-converting even when the total count is smaller.


    How GEO Differs From Traditional SEO

    Side-by-side SEO rank/click versus GEO citation/answer-first
    How GEO differs from traditional SEO.

    Traditional SEO optimizes for ranking position in a list of links. GEO optimizes for inclusion in the synthesized answer above those links. The signals overlap significantly, but GEO adds specific requirements around answer-first structure, data richness, and citation-friendliness.

    DimensionTraditional SEOGEO
    GoalRank in top 10Be cited in the AI answer
    Key signalBacklinks, E-E-A-T, technical SEOAnswer-first structure, data richness, entity authority
    MeasurementOrganic clicks, ranking positionAI citation rate, brand mentions, branded search volume
    Content structureTopic depth, keyword distributionDirect answer in first 200 words, FAQ schema
    Success statePosition 1Cited source in AI Overview

    Important: the overlap between ranking in Google’s top 10 and being cited in AI Overviews collapsed from roughly 75% in mid-2025 to 17–38% in early 2026. Ranking well no longer guarantees AI citation. Both need to be optimized for separately.


    Tactic 1: Answer First, Always

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    Answer first, always — then prove it with specifics.

    AI retrieval systems that use real-time web access evaluate a page’s relevance primarily on its opening content. The first 200 words of any article must directly and completely answer the primary query — not build up to the answer.

    The structure that gets cited:

    [H1 Title]
    [Bold one-sentence direct answer in first paragraph]
    [Supporting context and detail]
    

    The structure that doesn’t:

    [H1 Title]
    [Background context]
    [History of the topic]
    [Eventually getting to the answer]
    

    AI Overviews synthesize their answers from the opening of retrieved pages. A page that buries its answer 500 words in gets retrieved for its topic relevance and then can’t be cited because the direct answer isn’t extractable. The answer-first structure serves both GEO and usability simultaneously.

    For AI authority content specifically: every article about a Claude feature, pricing tier, or model capability should open with the factual answer to the likely query, stated plainly in the first sentence or two.


    Tactic 2: Add Original Data and Specific Numbers

    AI systems and search engines treat original data, specific statistics, and citable figures as high-value content. Content with precise numbers gets cited more than content with generalizations.

    The practical application:

    • “Claude Enterprise typically costs $60–250+/user/month depending on usage intensity” is more citable than “Claude Enterprise is expensive for some teams”
    • “68% of U.S. Google searches are zero-click in 2026” is citable; “most searches end without a click” is not
    • “Claude Sonnet scores approximately 77% on SWE-bench Verified” is citable; “Claude is good at coding” is not

    For tygartmedia.com content specifically: articles that include specific pricing numbers, benchmark scores, token counts, and performance figures will outperform articles that describe capabilities in qualitative terms. The Claude reference cluster (pricing, models, console) already does this well.

    Attribution rule: Cite where specific numbers came from — a benchmark, a study, Anthropic’s official documentation. “According to Anthropic’s pricing page” or “per SWE-bench Verified benchmarks” tells AI systems the claim is grounded, not asserted.


    Tactic 3: Use FAQ Schema

    FAQ schema (FAQPage structured data) formats content explicitly as question-and-answer pairs, which is the format AI answer engines are built to extract and synthesize from. Pages with FAQ schema see measurably higher AI Overview inclusion.

    Implementation in JSON-LD:

    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "What is Claude Enterprise pricing?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Claude Enterprise starts at approximately $20/user/month for access, with token usage billed separately at API rates. Real total cost typically runs $60–250+/user/month depending on usage intensity."
          }
        },
        {
          "@type": "Question",
          "name": "Is Claude Enterprise worth it?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "For teams with compliance mandates (SSO, SCIM, audit logs) or more than 150 users, yes. For smaller teams without governance requirements, Claude Team is more predictable and usually sufficient."
          }
        }
      ]
    }
    </script>
    

    In Rank Math (the plugin on tygartmedia.com): FAQ blocks in the WordPress editor automatically generate FAQPage schema without manual JSON-LD implementation. Add FAQ sections to every article and use the Rank Math FAQ block type.


    Tactic 4: Build Entity Authority

    AI systems and search engines treat entities — specific named things with consistent, verifiable information across the web — as more citable than generic topical content. Building entity authority for tygartmedia.com means consistent name, description, and factual claims across every surface the crawlers read.

    Entity authority checklist:

    • Organization schema on every page: Name, URL, description, logo, founder, same-as links to LinkedIn, social profiles
    • Consistent author byline: “Will Tygart” as the author on every article, with a consistent bio that establishes expertise
    • External mentions: Being cited by other authoritative sites on the same topics creates the external validation AI systems look for
    • Wikipedia/Wikidata presence: Not always achievable, but having factually consistent information across third-party sites (LinkedIn, Crunchbase, social profiles) strengthens entity recognition

    For an AI authority site specifically: the entity is “Tygart Media” and its associated expertise is Claude, Anthropic, and AI infrastructure for operators. Every article that earns an external link or citation strengthens that entity signal for all related queries.


    Tactic 5: Freshness Signals

    AI retrieval systems weight recency heavily for fast-moving topics. Claude pricing, model capabilities, and Anthropic’s roadmap change frequently. Articles with stale information get displaced by fresher sources even when the URL has more backlink authority.

    Freshness tactics:

    • “Last refreshed” date at the top of every article — signals to both users and crawlers that the information is current
    • Add a “What’s new” or “What changed” section for evergreen articles that cover frequently updated topics
    • Update timestamps when content changes — not just publishing dates, but explicit refreshed dates
    • Track in Google Search Console which queries trigger AI Overviews and whether the site is cited in them — freshness issues often show up as sudden drops in AI citation before they show up as ranking drops

    For Claude-related content: any article covering pricing, models, or features needs a refresh trigger whenever Anthropic makes changes. The May 2026 dispatch for timestamp refreshes on Fable 5-related pricing content is the right pattern.


    Measuring GEO Performance

    Standard GA4 and Search Console metrics don’t capture AI citation performance. The metrics that matter for GEO are AI citation rate, branded search volume, and assisted conversions from AI-referred traffic.

    What to track:

    MetricHow to measureWhat it indicates
    AI-referred trafficGA4 source filter for ChatGPT, Perplexity referralsDirect AI citation traffic
    Branded search volumeGoogle Search Console, “tygartmedia” queriesBrand awareness from AI citations
    AI Overview appearancesGSC AIO reportQueries where the site is cited
    CTR on AIO queriesGSC, filter by queries with AI OverviewsWhether citations drive clicks
    Conversion rate from AI referralsGA4 segmented by sourceValue of AI citation traffic

    Manual testing: monthly, ask ChatGPT, Perplexity, and Claude the questions your audience asks — “what is Claude Enterprise pricing,” “how does Metricool API work,” “what is Anthropic’s history” — and see whether tygartmedia.com is cited. This is the most direct GEO feedback loop available.


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

    Frequently Asked Questions

    What is Generative Engine Optimization (GEO)?

    GEO is the practice of structuring content and managing online presence so that AI answer engines — ChatGPT, Perplexity, Google AI Overviews, Gemini, and Claude — cite it in the answers they generate. It’s distinct from traditional SEO, which optimizes for ranking positions in link lists.

    How is GEO different from SEO?

    Traditional SEO optimizes for ranking position. GEO optimizes for citation inside AI-generated answers. The overlap between top-10 rankings and AI Overview citations has collapsed from 75% in 2025 to 17–38% in early 2026 — ranking well no longer guarantees AI citation. Both need to be optimized independently.

    Does GEO replace SEO?

    No. Traditional SEO fundamentals (E-E-A-T, backlinks, technical health) still power AI citations. GEO is an additional layer on top of a solid SEO foundation, not a replacement for it. Brands that excel at GEO in 2026 typically have strong traditional SEO as well.

    How long does GEO take to work?

    Plan for 3–6 months of consistent effort before seeing meaningful citation rate changes. Unlike traditional SEO ranking changes, which can be tracked daily, AI citation frequency changes slowly as crawlers re-index updated content and AI systems update their knowledge bases.

    What is the conversion rate from AI-cited traffic?

    AI search visitors convert at significantly higher rates than traditional organic visitors — roughly 4.4x according to Semrush data. The mechanism is intent: AI search users arrive with specific, researched queries and a pre-formed shortlist, which translates to higher purchase and contact intent.


    What to Read Next

    History of Anthropic 

    Claude AI Pricing — All Plans and API Rates

     Anthropic Console: API Keys and the Workbench

    Current Claude Model Version Tracker

  • WordPress SEO Skill Pack – Pro

    WordPress SEO Skill Pack – Pro

    WordPress SEO Skill Pack – Pro

    $79

    Delivered by email after checkout.

    Buy Now →

    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

    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.

    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.

    Related: WordPress SEO Skill Pack. Also WordPress SEO Skill Pack — Starter.

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

  • SiteBoost — Pilot Bundle (Best Value)

    SiteBoost — Pilot Bundle (Best Value)

    SiteBoost — Pilot Bundle (Best Value)

    $597

    Delivered by email after checkout.

    Buy Now →

    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:

    1. Create a WordPress Application Password (Users → Profile). Not the login password.
    2. Test GET /wp-json/wp/v2/users/me with that user and app password. If that fails, stop. Nothing else will work.
    3. 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.
    4. 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:

    1. SEO: title 50 to 60, slug, meta 140 to 155, H2/H3, keyword in the first 100 words.
    2. AEO: 40 to 60 word definition box, question H2s with 40 to 60 word answers, 6 to 8 FAQ pairs, FAQPage JSON-LD.
    3. GEO: named entities, sourced facts, speakable blocks, LLMS.txt comment, last-updated + dateModified.
    4. 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.

    Related: SiteBoost. Also SiteBoost — Site Connection & Audit.

  • SiteBoost — New Article Publishing

    SiteBoost — New Article Publishing

    SiteBoost — New Article Publishing

    $97

    Delivered by email after checkout.

    Buy Now →

    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:

    1. Name the organization in the text, not only in a hyperlink.
    2. Link the primary source. If it is paywalled, link a credible secondary that cites it.
    3. Put a sources list at the bottom.
    4. Show a last-updated date near the byline.
    5. 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

    1. Brief: target keyword, intent, PAA list, existing internal-link targets, sources you will actually cite.
    2. Draft written with definition box, question H2s, and sourced facts.
    3. Title 50 to 60, meta 140 to 160, slug clean.
    4. FAQ section + FAQPage schema. Article schema with both dates.
    5. Categories and tags set. 3 to 5 internal links. Sources list.
    6. 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.

    Related: SiteBoost. Also SiteBoost — Existing Post Optimization.

  • SiteBoost — Existing Post Optimization

    SiteBoost — Existing Post Optimization

    SiteBoost — Existing Post Optimization

    $47

    Delivered by email after checkout.

    Buy Now →

    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:

    1. 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.
    2. 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.
    3. 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.
    4. Heading structure. Real H2 / H3 hierarchy. No skipped levels. No H2 that is just a label with no answer under it.
    5. Primary keyword in the first 100 words.
    6. 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.

    1. Add a 40 to 60 word definition box near the top. One sentence that answers “what is this?” without a wind-up.
    2. Turn implied questions into H2s. Under each H2, put a 40 to 60 word direct answer, then the depth.
    3. 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.
    4. 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.

    1. Entity saturation. Name the real organizations, standards, statutes, places, and tools the topic depends on. Entity density, not keyword stuffing.
    2. 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.
    3. Speakable blocks. Short, self-contained sentences an AI or a voice assistant can lift without the rest of the page.
    4. 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.
    5. 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

    1. Current title, slug, meta, word count, FAQ count, schema present or not. Write those six lines down. That is your before.
    2. SEO pass. Title, slug, meta, headings, first 100 words.
    3. AEO pass. Definition box, question H2s, 6 to 8 FAQs, FAQPage schema.
    4. GEO pass. Named entities, sourced facts, speakable lines, LLMS.txt comment, last-updated + dateModified.
    5. Two to five internal links to related posts on the same site, descriptive anchors, plus one or two outbound links to primary sources.
    6. 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.

    Related: SiteBoost. Also SiteBoost — New Article Publishing.

  • Bing Webmaster Tools vs Google Search Console: What Each Tells Yo

    Bing Webmaster Tools vs Google Search Console: What Each Tells Yo

    Here’s the number that reorganized how we think about search: ~84% of our organic traffic comes from Bing. Not Google. Bing — and the Copilot and ChatGPT surfaces that draw on Bing’s index. Yet for a long time, like nearly everyone, we watched only Google Search Console and treated Bing as an afterthought.

    That’s the blind spot this article is about. Short answer: use both consoles, but if Bing drives your traffic, stop treating Bing Webmaster Tools as optional — it has data, indexing controls, and an AI-insights surface that Google Search Console doesn’t, and it’s reporting on the search engine that’s actually sending you readers.

    This is the side-by-side from running both consoles on the same media property: what each one tells you, where Bing is quietly ahead, and how we wired the Bing Webmaster Tools API into our editorial calendar.

    The core reporting — query, position, CTR

    Topic platform fit visual for first-party AI citation measurement
    Core reporting: query, position, CTR.

    At the surface, the two consoles look like twins. Both give you queries, impressions, clicks, average position, and CTR. The differences are in coverage and freshness.

    How we do it

    Job Bing Webmaster Tools Google Search Console Verdict
    Query / position / CTR Yes, per query and page Yes, per query and page Tie on the basics
    Data freshness Often faster to update ~2-3 day lag Bing edges ahead
    Historical window Generous 16 months Toss-up
    API access Full API: position + CTR per query/page Search Analytics API Bing — the API is the underrated weapon
    AI / Copilot insights Dedicated AI-traffic insights No equivalent surface yet Bing, clearly
    Market it reports on Bing + Copilot + ChatGPT-via-Bing Google only Depends on your traffic mix

    The honest read: for the basic dashboard, they’re close enough that you’d never switch for the UI. The reasons to take Bing seriously are whose traffic it reports on and what it lets you do about it — the AI insights tab and the API.

    Indexing: IndexNow vs crawl-when-it-feels-like-it

    Three cards for Google cautious, Bing speed, OpenAI aggressive crawl styles
    Indexing: IndexNow vs crawl-when-it-feels-like-it.

    This is the most concrete operational difference, and it’s lopsided.

    How we do it

    Job Bing Webmaster Tools Google Search Console Verdict
    Tell it about a new URL IndexNow — push, indexed near-instantly URL Inspection → “Request indexing” (queued) Bing — push beats poll
    Bulk submission IndexNow ping + sitemap Sitemap, then wait Bing
    Control over crawl Crawl control, block/allow Limited crawl controls Bing — more knobs
    Re-crawl on edit Re-ping IndexNow Hope, or re-request Bing

    IndexNow is the standout. Instead of submitting a sitemap and waiting for a crawler to wander by, you push a URL the moment it changes and it’s picked up almost immediately — and because IndexNow is a shared protocol, one ping notifies participating engines. Google’s model is still largely “request indexing and wait.” For a content site that publishes and edits constantly, push beats poll every time. We ping IndexNow on publish and on every meaningful edit.

    The AI / Copilot insights tab

    Comparison of Claude how-to fit versus local service page fit for assistants
    The AI insights tab is the differentiator.

    Google Search Console has no real equivalent here yet. Bing Webmaster Tools surfaces AI-traffic insights — visibility into how your content shows up across Bing’s AI-powered and Copilot surfaces. Given that those surfaces (and ChatGPT’s web results, which draw on Bing) are an increasing share of how people find answers, this is the single console feature most aligned with where discovery is heading. If you care about GEO at all, it’s the dashboard that tells you whether the AI assistants are actually pulling you in.

    Wiring the BWT API into the editorial calendar

    The Bing Webmaster Tools API is the part most sites never touch, and it’s the most actionable. It returns position and CTR per query and per page — which is a ready-made content-optimization loop:

    1. Pull query/position/CTR from the BWT API on a schedule.
    2. Find pages ranking on page one with weak CTR (good position, bad headline/meta) — fast wins.
    3. Find queries where we rank position 5-15 with real impressions — the “one good edit from page one” list.
    4. Feed both lists straight into the editorial calendar as prioritized rewrites.

    Because Bing drives most of our traffic, this loop is pointed at the engine that actually moves our numbers. Running the same loop off Google Search Console’s API would optimize for the 16% of traffic, not the 84%.

    What surprised us

    • Bing’s data is often fresher than Google’s. We frequently see new queries in Bing Webmaster Tools before they show up in Search Console.
    • IndexNow is faster than anything Google offers — and it’s free and standard. The gap between “push and it’s indexed” and “request and wait” is real and daily.
    • The AI insights tab has no GSC counterpart. For a site doing GEO, that’s the most forward-looking surface either console offers.
    • Almost nobody verifies their site in Bing Webmaster Tools. You can import directly from Google Search Console in a couple of clicks, so the only reason most sites skip it is that they’ve never looked at where their traffic comes from.

    The takeaway

    This was never a “pick one” — it’s “stop ignoring one.” Google Search Console is still essential; Google isn’t going anywhere. But running only GSC is a bet that Google’s view of your site is the only one that matters, and our traffic data says that bet is wrong by a factor of five.

    Use both. Watch Google Search Console for the Google slice. But if a large share of your organic traffic comes from Bing — and a surprising number of content sites are in exactly that position without checking — then Bing Webmaster Tools is your primary console: fresher data, IndexNow for instant indexing, the AI/Copilot insights surface, and an API you can wire straight into your editorial calendar.

    The 84% lesson is simple: measure where your readers actually come from, then watch the console that reports on it. For us, that meant promoting Bing from afterthought to the dashboard we open first.

    This is part of our “Two Clouds, One Site” series — we run the same media property on Azure and Google Cloud, on the free tiers, and report what watching both ecosystems actually teaches us. The lab lives on tygart.media; the findings publish here.

    Related on Tygart Media: Bing vs GSC (companion) · read Bing AI citations · AI citation monitoring.

    Frequently asked questions

    Should I use Bing Webmaster Tools if I already use Google Search Console? Yes — they report on different search engines, so using only Google Search Console hides all of your Bing performance. If any meaningful share of your traffic comes from Bing, Copilot, or ChatGPT’s Bing-powered results, Bing Webmaster Tools shows data and offers indexing controls that Search Console doesn’t. You can import your site from Search Console in a couple of clicks.

    What is IndexNow and is it faster than Google indexing? IndexNow is a protocol that lets you push a URL to search engines the moment it’s published or changed, instead of waiting for a crawler. It’s typically much faster than Google’s “request indexing and wait” model, and because it’s a shared standard, one ping notifies participating engines. For sites that publish or edit frequently, it’s a meaningful indexing-speed advantage.

    Does Bing Webmaster Tools have an API? Yes. The Bing Webmaster Tools API exposes per-query and per-page data including position and CTR, plus URL submission. That makes it practical to pull your search performance on a schedule and feed it into a content-optimization loop — for example, flagging page-one results with weak CTR or near-miss rankings to prioritize for rewrites.

    What does the Bing Webmaster Tools AI insights tab show? It surfaces how your content appears across Bing’s AI-powered and Copilot surfaces, giving visibility into AI-driven discovery that Google Search Console has no direct equivalent for yet. For sites focused on Generative Engine Optimization, it’s the most forward-looking view either console offers into whether AI assistants are pulling in your content.

    Why would a site get most of its traffic from Bing instead of Google? It’s more common than people assume, especially for niche or B2B content, sites strong in Bing-heavy regions or browsers, and content that surfaces well in Copilot and ChatGPT’s Bing-powered results. The lesson is to measure your actual referral mix rather than assume Google dominates — many sites only discover their Bing share once they verify in Bing Webmaster Tools.