Author: William Tygart

  • Boeing Everett & SPEEA 2026: Contracts, Production Lines & Jobs

    Boeing Everett & SPEEA 2026: Contracts, Production Lines & Jobs

    Last verified: September 2026. October is the month everything converges in Everett: the SPEEA contract expires on October 6, production lines are shifting, and a 5,200-worker shortage has handed aerospace workers rare leverage. Eight deep dives, one hub — the contract, the lines, and what it means for your job.

    The contract: SPEEA 2026, expiring October 6

    Three guides, one deadline. The SPEEA 2026 contract with Boeing expires October 6 — days from now — covering Everett’s 17,000 aerospace engineers and technicians. The core bargaining issues: PTO, retirement, raise pools, and on-call compensation. Four core priorities, one expiring clock.

    → SPEEA 2026 Contract: Guide for Boeing Everett Engineers — the complete bargaining guide: PTO, retirement, raise pools.

    → SPEEA Boeing Contract 2026: Engineers & Tech Outlook — the four core bargaining priorities for 17,000 engineers and technicians.

    → SPEEA 2026 Boeing Contract: Salary & Labor Priorities — what engineers want: salary, PTO, retirement, on-call pay.

    The production lines: eras ending, targets rising

    May 2026 saw the final Boeing 767 freighter delivery to FedEx — the end of an era for the Everett widebody workforce, with the 767 commercial line closing in 2027. Meanwhile Renton is maxed out at 47 jets a month, making the new Everett 737 North Line Boeing’s only path to its crucial 2026 target of rate 53. And the pending 777F exemption decision hangs over Paine Field and the 777-8F transition.

    → Boeing 767 Freighter: Final FedEx Delivery & Everett Impact — the end of the 767 era and what follows for the widebody workforce.

    → Everett 737 North Line: Boeing’s Only Path to Rate 53 — why rate 53 runs through Everett.

    → KC-46 Tanker Line: Paine Field Jobs After 767 Closes — job stability and internal transfer options as the 767 line winds down.

    → Boeing 777F Exemption: What It Means for Paine Field Jobs — the exemption decision, job security, and the 777-8F transition.

    Your leverage: the 5,200-worker shortage

    A 5,200-person aerospace worker shortage means hiring leverage is on the worker’s side — massive leverage, per the source piece. WATR and the Machinists Institute can fast-track a Snohomish County aerospace career. Read the contract guides above, then read this one.

    → Aerospace Worker Shortage: Snohomish County Career Guide — how to convert the shortage into your offer letter.


    Eight deep dives, one hub. The SPEEA contract expiring October 6, the production lines shifting underneath it, and worker shortage handing you the leverage.

  • Your Laptop Is Already an AI PC: The Local AI Stack Guide

    Your Laptop Is Already an AI PC: The Local AI Stack Guide

    Last verified: September 2026. The AI-laptop wave is here — Copilot+ PCs, NPUs, “AI-ready” stickers on everything. Here’s the part the marketing skips: the laptop you already own can run a serious local AI stack today. No new hardware, no cloud bill, no subscription treadmill. This guide is the proof, the money math, and the build instructions — nine deep dives, one hub.

    The proof: a $400 laptop that rivals a Copilot+ PC

    Start here. A $400 budget laptop, no NPU, turned into a private AI operator rig that rivals a Copilot+ PC — command by command. This is the article that makes the whole premise undeniable: the hardware barrier is mostly marketing.

    → Local AI Without NPU: Turn a $400 Laptop Into an AI PC — the full command-by-command build.

    Will’s note: Ollama can also offload part of the compute to your GPU through its settings — we tried that route. We never really stuck with local, honestly; we like our CLIs backed by cloud compute. But if you want the full local path, the GPU setting is worth knowing about.

    The money: replacing a $12K/month tool budget

    The stack isn’t just a hobby project — it replaced $12,000 a month in expensive SaaS tools. Open-source models, Python, and PowerShell automation doing the work the subscriptions used to do. Read this one with your accounting hat on.

    → Local AI Stack: How We Replaced a $12K/Mo Tool Budget — what got replaced, with what, and how.

    Your files, answerable: 468 documents, one laptop

    Using Ollama’s nomic-embed-text model and ChromaDB, a local RAG system was built that indexes every skill file, session transcript, and project doc on the machine — 468 files — and answers natural-language questions about the operation. Your laptop becomes the expert on your own business.

    → I Indexed 468 Files Into a Local Vector Database. Now My Laptop Answers Questions About My Business — the build: embeddings, database, queries.

    The business version: index, query with Claude, measure ROI

    The production-grade take: indexing business documents into a local vector database and querying them with Claude — architecture, code, production lessons, and real ROI numbers. This is the one to hand your skeptical partner.

    → How to Index Business Files Into a Local Vector Database (2026) — architecture, code, and the ROI math.

    The agent army: zero cloud cost

    Enterprise AI costs are spiraling — GPT-4 API calls at scale run hundreds or thousands of dollars a month. The alternative: a free agent army built with Ollama and Claude. Zero cloud cost. This is the flagship piece of the stack.

    → How We Built a Free AI Agent Army With Ollama and Claude — the zero-cloud-cost AI stack.

    Triage agents: routing work at scale

    AI triage agents eliminate manual bottlenecks by automating task routing, intent detection, and urgency scoring across business lines. Not a chatbot — infrastructure that decides where work goes.

    → AI Triage Agents: How to Automate Task Routing at Scale — routing, intent detection, urgency scoring.

    The $0 marketing stack

    An enterprise marketing stack for $0: open-source AI, free API tiers, and Google Cloud credits. Exactly what’s used, spelled out.

    → The $0 Marketing Stack: Open Source AI, Free APIs, and Cloud Credits — the full stack, item by item.

    Scheduled tasks: automating the 40-hour week

    Scheduled tasks, webhooks, and AI automating manual work — the goal is reclaiming the 40-hour work week for strategic growth instead of busywork. This is where the stack stops being a demo and starts being operations.

    → Scheduled Tasks: How to Automate Your 40-Hour Work Week — tasks, webhooks, and AI automation patterns.

    The vision: the AI-native business operating system

    The end state: an AI-native business operating system that replaces static workflows with autonomous infrastructure, scaling the company with programmatic governance. Everything above is a component of this.

    → AI-Native Business Operating System: Autonomous Scaling — the architecture of the whole thing.


    Nine deep dives, one hub. The $400 laptop proves it, the $12K/mo replacement pays for it, the 468-file index and the agent army run on it — and the AI-native OS is where it all leads.

  • Claude Code: Setup, Pricing, Limits & Picking Your Dev Tool

    Claude Code: Setup, Pricing, Limits & Picking Your Dev Tool

    Last verified: September 2026. Claude Code is Anthropic's terminal coding tool — it lives where developers live, in the command line. Around it has grown a small universe: install paths, seat pricing, credit pools, rate limits, and three sibling agent surfaces that people constantly confuse with it. This guide is the map.

    Installing it: two minutes, pick your path

    On Windows, it's PowerShell, one command, no Node.js required — the native install path, verified against the May 2026 installer, including the five errors you’ll hit and the exact fix for each. For the general path, it's the one-line npm CLI install plus the Desktop app, done in under two minutes, with the common errors covered.

    → Install Claude Code on Windows: 2026 Step-by-Step — the Windows path: one command, five errors, five fixes.

    → Install Claude Code: Complete Desktop & CLI Setup Guide — the general path: npm one-liner, Desktop app, troubleshooting.

    What it costs: seats, tiers, and the API meter

    Claude Code rides on your existing seat — Pro ($20/month), Max ($100 or $200/month), Team, or Enterprise. The API path is a separate console meter, not drawn from your seat. If you're deciding between Pro and Max for dev work, the question is usage volume: Max is for the people who live in the terminal all day.

    → Claude Code Pricing in 2026: Pro vs Max vs API Costs Explained — seats vs API, verified September 2026, with current token rates on the pricing hub.

    → Claude Code Pricing 2026: Pro, Max, and API Limits — the tier comparison for dev workflows, including Opus 4.7 API rates.

    How the billing actually works: subscriptions vs credit pools

    This is the part that surprises people. Interactive terminal use draws on your Pro/Max subscription — it's part of the seat. But since June 15, 2026, Agent SDK and headless (claude -p) usage moved to separate monthly billing. Same tool, two meters, depending on how you invoke it. Know which one you're on before the invoice teaches you.

    → Claude Code Billing & Monthly Credit Pools (2026) — subscription draw vs separate Agent billing, and how the credit pools work.

    The limits: two clocks

    Claude Code meters two clocks: a rolling 5-hour session window and a weekly bucket. The +50% weekly promo ended September 13, 2026 — what replaced it is a permanent +25% on the weekly limits. Note the model gating: Fable 5.1 is included only on Max and premium seats.

    → Claude Code Limits (September 2026) — both clocks explained, what's permanent, and where Fable 5.1 is available.

    Picking your surface: Cowork vs Code vs Agent SDK vs Managed Agents

    Anthropic now has four agent surfaces and they are not interchangeable: Claude Code, Claude Cowork, the Agent SDK, and Managed Agents. Interactive vs autonomous is the real dividing line — which surface fits depends on who's driving and how much autonomy the job needs.

    → Claude Cowork vs Code vs Agent SDK vs Managed Agents (2026) — the decision matrix: who each surface is for and where each runs.

    Cowork in action: the daily briefing

    The canonical Cowork workflow: connect your calendar, email, and tasks, write the right prompt, and schedule it to run automatically every morning. A briefing that builds itself before you've had coffee. It's the clearest demo of what the non-code surface is for.

    → Claude Cowork: Daily Briefing & Automated Sync (2026) — setup, prompt design, and scheduling.


    Eight deep dives, one hub. Install it, price it, learn the billing and limits, then pick the right surface for the job.

  • The Microsoft 365 Copilot Guide: Shortcuts, Workflows, Compliance & Migration

    The Microsoft 365 Copilot Guide: Shortcuts, Workflows, Compliance & Migration

    Last verified: September 2026. Microsoft 365 Copilot lives inside the apps your company already pays for — Outlook, Teams, Word, Excel, PowerPoint — which is exactly why it's confusing. It's not one product with one manual; it's a layer across everything. This guide is the map: the fast lane for power users, the daily workflows, the compliance side your IT department cares about, and the migration path if you're coming from ChatGPT Enterprise.

    The fast lane: shortcuts and power tips

    Copilot rewards the people who learn its keys. The September 2026 shortcut table: Alt+C on Windows, Cmd+Control+I on Mac, F6 just about everywhere. In Word and Excel, Alt+I is the in-canvas draft key — not the side pane, the document itself. These are the difference between “I tried Copilot once” and actually living in it.

    → Microsoft 365 Copilot Shortcuts & Power Tips (2026) — the full shortcut table plus the hidden features most users never find.

    The daily workflows: Outlook, Teams, Word, PowerPoint, OneNote

    Shortcuts get you in the door; workflows are what you do all day. The guide walks a full workday: the Copilot morning routine, then cross-app workflows spanning Outlook, Teams, Word, PowerPoint, and OneNote — work that starts in one app and finishes in another.

    → The Complete Microsoft 365 Copilot Productivity Guide (2026) — the day-in-the-life walkthrough across all five apps, with the cross-app workflows spelled out.

    The compliance side: audit logs, Purview, and eDiscovery

    Here's the part individual users skip and IT departments can't: every Copilot interaction is a data event, and in a regulated or litigation-prone company, those events need an audit trail. Microsoft Purview is where it happens — Activity Explorer for monitoring Copilot usage, eDiscovery workflows that cover Copilot conversations, retention policies that decide what survives and for how long. If your company is rolling out Copilot without this configured, that's a gap, not a phase two.

    → Microsoft Copilot Audit Logs & eDiscovery Guide (2026) — Purview setup, Activity Explorer, eDiscovery coverage, and retention policy design.

    Switching: from ChatGPT Enterprise to Copilot

    The consolidation math is what's driving migrations: organizations moving from ChatGPT Enterprise to Microsoft Copilot save roughly $20–30 per user per month. The catch is that it's not a license swap — it's a workflow migration, covered in the guide workflow by workflow, challenges included.

    → Migrate ChatGPT Enterprise to Copilot: 2026 Guide — the workflow-by-workflow migration playbook.


    Four deep dives, one hub. The shortcuts table for speed, the productivity guide for the workday, the audit guide for the compliance file, and migration guide for the switch.

  • Claude Pricing, Plans & Limits: The Complete 2026 Guide

    Claude Pricing, Plans & Limits: The Complete 2026 Guide

    Last verified: September 2026. Claude's pricing moves fast — new models, new tiers, new limits every few months. This guide is the map: the direct answer up front, then every deep dive we've published, organized so you can find exactly the piece you need. For today's exact numbers, the linked tracker pages stay current.

    The short answer: what does Claude cost?

    As of September 2026, Claude's lineup is: Free ($0), Pro ($20/month, or $17/month billed annually), Max (from $100/month), Team (Standard $20–$25/seat/month, Premium $100–$125/seat/month depending on billing, 2–150 seats), and Enterprise (custom, starting around $20/seat/month). API pricing is separate from chat seats — a Pro subscription does not include API credits.

    That's the shape of it. Everything below is the detail — pick your question and follow the link.

    The plans, side by side

    Five tiers, five different buyers. Free is the trial. Pro is the individual power user. Max is for people who live in Claude all day. Team is per-seat collaboration with admin controls. Enterprise is custom contracts with security review.

    → Claude Pricing Tiers: Free vs Pro vs Max vs Team vs Enterprise — the full side-by-side: costs, features, and API rates at every tier, including current per-token pricing.

    → Claude Pricing (September 2026): Every Plan, Seat and API Rate — the master pricing page. If you only bookmark one page in this guide, make it this one.

    Team plans: Standard vs Premium seats

    This is where buyers get confused, because the two seat types look similar and cost very differently. Standard seats run roughly $20–$25 per seat per month; Premium seats run roughly $100–$125. The difference is usage allowance and admin controls — Premium is for the people on your team who burn through a Standard seat's limits by lunch.

    → Claude Team Pricing: Standard vs Premium Seats (2026) — feature-by-feature breakdown and guidance on which seats to buy for which roles.

    Rate limits and usage limits: the frustration chapter

    Rate limits are the number-one Claude complaint, and the number-one thing buyers underestimate. Every plan has them, they differ between chat and API, and Team plan limits doubled in May 2026 after Anthropic's compute deal with SpaceX's Colossus 1 — except the Free plan, which was left out.

    → Claude Rate Limits: Every Plan & API Tier (2026) — exactly what the limits are at every tier, plus the workarounds that actually work.

    → Claude Team Plan Usage Limits & Pricing (2026) — what changed in the May 2026 doubling, and what it means per seat.

    Token limits and context windows, in plain English

    Context window is how much Claude can hold in its head at once; output limit is how much it can write in one response. As of late 2026: Fable 5, Opus 4.8, and Sonnet 4.6 carry a 1M-token context window; Haiku 4.5 carries 200K. Maximum output runs to 128K tokens on the big models. In practice: 1M tokens is roughly a shelf of books in one conversation.

    → Claude Token Limit: Context Windows, Output Limits, and What They Mean in Practice — per-model limits and what they mean for real workloads.

    Which model: Haiku vs Sonnet vs Opus

    Three model families, three jobs. Haiku is fast and cheap — the one you call a thousand times a day. Sonnet is the daily default, the balance of smarts and speed. Opus is the flagship — the one you reach for when the problem is hard and the answer matters. Fable sits above them as the current top-tier model.

    → Claude Models Explained: Haiku vs Sonnet vs Opus (September 2026) — pricing, context, speed, and which model to use for coding, writing, and API work.

    What's current: the model tracker and release history

    The lineup as of September 8, 2026: Fable 5.1 (top), Opus 5 (flagship daily driver, Max default), Sonnet 5 (Free/Pro default), Haiku 4.5 (fast). Recent history: Fable 5.1 and Mythos 5.1 landed September 1, Opus 5 on July 24, Sonnet 5 on June 30, Fable 5 on June 9.

    → Current Claude Model Version (September 2026 Tracker) — the living tracker. Check this before you cite a version number anywhere.

    → Claude Release History: Claude 1 to Fable 5.1 — the full timeline from Claude 1 to today.

    Getting started: API keys and the Console

    Two doors into Claude: the chat app (claude.ai) and the API (console.anthropic.com). Getting an API key takes about five minutes — create an account, add a payment method, generate the key. The Console is also where you watch your API spend burn, which you should do early and often.

    → How to Get an Anthropic API Key (2026 Quick Guide) — the five-minute setup, step by step.

    → Anthropic Console: Setup, API Keys & Billing (2026) — keys, credits, billing, and burn monitoring in one place.

    Students and education pricing

    The honest answer first: there is no public Claude Pro student coupon. The student path runs through partner universities — free premium access via your school email through Claude for Education. Note the naming trap: “Claude for Teachers” is the K-12 program, not the campus one.

    → Claude Student Discount & Education Pricing (2026) — what's real, what's rumor, and how the university path works.

    Background: the company behind the pricing

    Anthropic's pricing makes more sense once you know the company's shape — an AI research company whose compute deals (like the SpaceX Colossus 1 agreement) directly move what you pay.

    → History of Anthropic: Founders, Origins & AI Evolution — from the founders' early vision to the company setting prices today.


    This guide links thirteen deep dives, all verified against September 2026 pricing. Claude's lineup changes fast — when in doubt, the pricing tracker and model tracker carry the current numbers.

  • Your knowledge base isn’t the citation

    Your knowledge base isn’t the citation

    I built tygartmedia.com as a knowledge base. Over 3,300 posts, and the point was never vanity traffic — it was so I could pull answers from my own site. If I wrote it down, it's mine, it's findable, and I can stand behind it.

    The data says that instinct is pointed at the wrong surface.

    McKinsey's “New Front Door to the Internet” report puts it plainly: a brand's own content — the company blog, the branded pages, the carefully worded site — accounts for only 5 to 10 percent of the sources AI models reference when they talk about that brand. The other 90 to 95 percent is external: forums, reviews, affiliates, creator content. On McKinsey's own podcast, discussing the same research (25 brands, 2.6 million LLM citations over six months), the number for brand websites specifically came out at about 1 percent. One percent of what AI says about you comes from your site.

    And yet a third of marketers still believe their brand website carries the most weight in how AI describes them. That's from Later's survey of 487 marketers — a real panel, ±4.4% margin, self-reported, so read it as what marketers believe, not what the systems do. Kaleigh Moore, who got early access to Later's Creator AEO playbook, reads that gap as the industry spending its AI-search budget on the surface that matters least: the company blog. That's her inference, not a surveyed budget line — but the direction of the disconnect is hard to argue with.

    So what is AI actually reaching for? Later's campaign data — their own measurements, so treat these as directional — says as many as 1 in 3 AI answers cite creator content, and 57% of the YouTube videos AI cites come from channels with fewer than 100,000 followers. The marketers in the survey already sense this: asked which creator types matter most for AI search, they ranked everyday product users first at 39%, then specialists and reviewers. High-reach social influencers came in last. The roster built for reach is not the roster that gets cited.

    The YouTube piece checks out independently. Ahrefs' tracking of the 50 most-cited domains in Google AI Overviews puts YouTube at number one with a 22.9% mention share, ahead of Reddit at 18.5% and Wikipedia at 4.0%. In a separate Ahrefs study, AI Overviews cited YouTube more than encyclopedic sources. Video and community threads are getting pulled into AI answers at a rate plain blog posts aren't matching — which is a real shift in what “authoritative source” means to these systems.

    Moore's playbook has an anecdote that makes it concrete. Carly Baron, chief commercial officer at Advantice Health, searched anything related to one of their brands and watched the same dermatologist surface again and again. Different queries, same person. They had never worked with her. No contract, no brief, no relationship. Her narrative was shaping what their brand looked like in AI search, and they only found out by going and looking. Every brand has a version of that dermatologist — someone the models have decided is the voice on the topic. The question is whether you've found yours, and whether you have a relationship with them.

    Now here's the honest tension, because this piece shouldn't pretend the knowledge-base instinct is dead. It isn't — it just isn't the citation. Later's own Cameron Miskho puts it well: the creator content should ladder into what the brand is already saying on its owned channels. Your site becomes the reference layer — the source of truth the third-party voices draw on when they draw on anything at all. And buyers still verify: coverage of a Spotlight analysis notes that between 45 and 71% of AI-using buyers go to the vendor's own website afterward to check pricing, documentation, and case studies. The knowledge base isn't the citation. It's what the citation points at, on the days it bothers to point.

    That distinction matters more every quarter, because the citation is becoming the whole visit. Ahrefs analyzed 300,000 keywords and found the top-ranking page lost 34.5% of its clickthrough when an AI Overview sat above it. The follow-up — published February 2026, using data through December 2025 — put the loss at 58%. More than half of the searchers who used to click the top result now never scroll down. If the answer is the visit, then being in the answer is the entire game, and the answer is assembled from other people's voices.

    For the restoration world, this is bluntly practical. Nobody is asking ChatGPT about your company blog. They're asking who to call when the basement floods, and the answer is built from Google reviews, a YouTube walkthrough shot by a real tech, a Reddit thread, a local news mention. Earned third-party mentions — reviews, local publishers, creator videos, forums — are what actually get cited. Owned content is the foundation; it just doesn't do the talking.

    Later's starting framework is worth stealing even if you never hire a creator: pick one engine, build a working list of 10 to 20 prompts across buying intent, competitor comparisons, features, and broad category questions, then check where your brand actually shows up and whether the mention comes with a citation. Where the owned pages those citations lean on are stale, update them. Where a video lives only on Instagram behind a crawler wall, pull the transcript and put it somewhere the models can read. And sort any creator relationships by authority and specificity, not follower count — the 4,000-follower specialist with a detailed, data-backed opinion keeps beating the 400,000-follower generalist.

    Moore's closing line is the one I'd keep: you don't get to opt out of third-party voices defining your brand. You only get to decide whether you have a relationship with them.

  • Job Posting Schema for Restoration Shops: How Google Reads a Vacancy

    Job Posting Schema for Restoration Shops: How Google Reads a Vacancy

    Last verified: October 2, 2026 against Google’s Job posting structured data (docs last updated September 8, 2026) and AIOSEO’s 4.9.9 announcement.

    Direct answer: JobPosting schema is structured data that labels a single open role — title, employer, work location, description, posted date — so Google can treat the page as a vacancy instead of a brochure. Done correctly, the listing becomes eligible for Google for Jobs. Eligibility is not placement. Google still decides. The markup must match what a candidate can read on the page.

    Tech documenting a water loss on a tablet
    A careers page on your domain is the object Google can attach JobPosting schema to. The board is optional.

    Trigger for this desk: All in One SEO emailed Tygart Media on September 25, 2026 that Job Posting schema (and Event schema) now ships on every paid AIOSEO plan starting with Basic, as of AIOSEO 4.9.9. That is a product-access change, not a ranking promise. tygartmedia.com runs Rank Math. The schema type is the same either way. The plugin is a generator. Google’s Job posting structured data spec (docs last updated September 8, 2026) is the rulebook.

    Why a restoration shop should care

    Related: Schema Markup for AI Search: The New Meta Description · Your Google Profile Is Your New Front Door

    Most restoration companies hire the way they market: on someone else’s board. Indeed, Facebook, a text to a former tech. That works until storm season, and then the shop needs a water tech in Everett, a project manager in Lynnwood, or an estimator who already knows Snohomish County adjusters. If the only public copy of the role lives on a job board, Google indexes the board. Your domain does not own the vacancy.

    A careers page on your site is the durable object. JobPosting schema is the label on that object. Answer engines and Google for Jobs both prefer a page that states the role in plain sentences and then repeats the same facts in JSON-LD. That is AEO and GEO in one hang: the page answers “who is hiring water mitigation technicians in Everett, WA,” and the markup gives the city, employer, and dates without forcing the model to guess.

    What Google requires

    Google’s required JobPosting properties, from Search Central:

    • title — the job title only. “Water Mitigation Technician,” not “Water Mitigation Technician — $28/hr — Everett — Apply Now!!!”
    • description — the full description in HTML. Duties, qualifications, hours, education, experience. A teaser fails.
    • hiringOrganization — the company, not the branch nickname. Name plus a sameAs URL to the official site.
    • jobLocation — where the person reports. PostalAddress with addressCountry. For a 100% remote role, use jobLocationType TELECOMMUTE plus applicantLocationRequirements instead.
    • datePosted — original post date in ISO 8601. Do not refresh it to fake newness.

    Recommended properties that matter for a restoration hire: validThrough (when the listing dies), employmentType (FULL_TIME, PART_TIME, CONTRACTOR, TEMPORARY, PER_DIEM), baseSalary as a MonetaryAmount with currency and unit (HOUR / YEAR), and identifier so you do not duplicate the same role across reprints.

    AIOSEO’s walkthrough (updated August 21, 2026) maps those fields into a Schema Generator: title, description, employment type, location, hiring organization, salary, requirements, publish date, expiration date. Rank Math exposes the same JobPosting type. Fill the fields from the visible page. Do not invent a salary in schema that is missing on the page.

    GEO: mark the city the truck leaves from

    Local service hiring is geographic. A candidate searching “water damage technician jobs Everett WA” or “IICRC tech hiring Lynnwood” is not looking at a national career hub. Put the reporting city in the visible copy and in jobLocation.addressLocality / addressRegion / postalCode / addressCountry.

    Worked example for a shop that stages out of Everett and runs the Lynnwood–Mukilteo–Mill Creek pack:

    • Title on the page and in schema: Water Mitigation Technician
    • hiringOrganization.name: the legal company name, not “Everett Crew”
    • jobLocation: Everett, WA, United States, with the real street if that is where they report
    • description: names the pack — Everett, Lynnwood, Mukilteo, Mill Creek — as service area, not as four fake job locations
    • employmentType: FULL_TIME or PER_DIEM, whichever is true
    • validThrough: a real close date, then take the page down or set the date in the past when the seat is filled

    Do not stamp four JobPosting graphs on one page for four cities unless there are four distinct open seats. Google wants one job per leaf URL. A list page of “all openings” is the wrong surface.

    AEO: write the vacancy so an engine can quote it

    Schema does not rescue thin copy. Open the careers page with the answer a model can lift:

    We are hiring a full-time water mitigation technician based in Everett, Washington. The role reports to our Everett shop and runs losses across Snohomish County. Pay is listed on this page. Apply on this page.

    Then the body: first-day duties, IICRC or in-house training, on-call expectations, what “storm mode” means, whether the truck is assigned. That paragraph is the description field. If ChatGPT or Gemini is asked “who is hiring restoration technicians near Everett,” the engine needs a quotable sentence plus an organization it can attach to a maps entity. JobPosting is the attachment point. The sentence still has to exist in public HTML.

    How to hang it in WordPress

    1. Create one WordPress post or page per open seat. Slug like /careers/water-mitigation-technician-everett/.
    2. Write the full vacancy on the page first. Salary, city, dates, how to apply.
    3. In Rank Math (this site) or AIOSEO Schema Generator (if that is the client stack), add schema type JobPosting. Map every field to visible text.
    4. Validate with Google’s Rich Results Test. Fix errors before you call it done.
    5. When the seat fills: set validThrough to a past date, or 404/410 the URL. Do not leave a live JobPosting on a closed role.

    AIOSEO 4.9.9 made that generator available on Basic instead of reserving it for higher tiers. If a client already pays for AIOSEO, they do not need an upgrade to mark up jobs. If they are on Rank Math, they already had the type. Do not switch plugins to chase a newsletter.

    What gets a listing dropped

    • Markup on a jobs index that lists many roles
    • Title or salary in schema that the page does not show
    • Expired jobs still marked active
    • No way to apply on the page
    • jobLocation missing addressCountry, or a “remote” job that is not actually remote
    • Keyword stuffing in the title (“#1 BEST WATER TECH JOBS SEATTLE EVERETT TACOMA”)

    Google can issue a manual action for job spam. Fake seats used as lead magnets are not a grey area. If you are not hiring, do not hang JobPosting.

    The line to remember

    A careers page without JobPosting is a flyer. JobPosting without a real, dated, city-true vacancy is spam. Host the seat on your domain, mark the five required fields, expire it when the truck is staffed, and let Google decide whether it belongs in the job experience.

    FAQ

    Q: Does JobPosting schema guarantee a listing in Google for Jobs?
    A: No. It makes a qualifying page eligible. Google still applies content and spam policies. The official spec is explicit on that point.

    Q: We only hire on Indeed. Should we still put jobs on our site?
    A: If you want the vacancy attached to your entity — maps profile, site, AI answers — yes. The board can stay as an apply path. The leaf page on your domain is what you can mark up.

    Q: Can one page cover Everett, Tacoma, and Belfair?
    A: One page can describe a service area. Schema jobLocation should be the report-to city. Separate open seats in separate cities need separate URLs.

    Q: Is this an AIOSEO-only feature?
    A: No. AIOSEO expanded plan access in 4.9.9 (announced July 13, 2026). Rank Math and hand-written JSON-LD can emit the same type. Use the generator you already pay for.

    Q: What if we do not publish pay?
    A: baseSalary is recommended, not required. Do not invent a number in JSON-LD. Leave it out until the page states pay.

  • The Best Tax Product Reads the Notice Against the Roll

    The Best Tax Product Reads the Notice Against the Roll

    The county already published the roll. The owner still pays on a number that may not match the sales next door. That gap is the product.

    Listen to this essay. https://drive.google.com/file/d/1wVsHeFtnR0uHMDh4-JeqJcwD6X9tt0Qu/view?usp=drivesdk

    The idea mills keep minting a tax chatbot, an appeal-letter filler, and a “save on property tax” micro-SaaS. Three names. One object. A line on a notice that does not sit next to the comps the assessor used, or claimed to use.

    The notice is not the file

    Most owners treat the proposed-value postcard as weather. It arrives. They groan. They pay. The public record underneath it is larger than the card: parcel attributes, last sale, neighborhood sales, exemptions, and the protest calendar.

    In August 2026 the National Bureau of Economic Research posted Working Paper 35632, “Taxpayer Behavior in the Age of AI,” by Justin E. Holz, Ricardo Perez-Truglia, Andrew Simon, and Alejandro Zentner. Dallas County mailed 45,200 postcards and studied 645 owner-occupied households who actually opened a site built for the 2026 protest window. Proposed values dropped April 14. The deadline was May 15. Half the visitors got the same evidence pack plus a chatbot. Seventy-eight percent of that half started a conversation. Filing a direct appeal, without a paid agent, rose from 41.4 percent to 50.5 percent — 9.1 points.

    That is not a vibe. That is a field experiment on a real calendar, with a real county roll, in a year when the average bill in the study setting sat near $7,900. A prior mailed-guide intervention in the same market (Nathan and coauthors, 2025) moved filing by about five points. The chatbot almost doubled that lift. It did not file for anyone. It helped people judge the packet they already had.

    Who files, who does not

    The gap is not “people hate taxes.” The gap is who can assemble the file before the window closes.

    Forbes, writing in June 2026 on Cook County’s assessment cycle and citing the treasurer’s office, put commercial appeal rates at 64 percent and homeowner appeal rates at 27 percent. In some lawyered pockets the rate ran to 92 percent. In poorer neighborhoods it sank near 5 percent. A 2025 University of Chicago Center for Municipal Finance evaluation of Cook County’s 2019–2024 residential work found the assessor had cut the old regressivity. Appeals on the commercial side still shift 3 to 4 percent of the tax base onto houses every year.

    Park City agent Wayne Levinson told the Park Record in March 2026 he used AI to screen Summit County parcels and help secure $13.9 million in assessed-value cuts in the 2025 window — then a person still filed, still sat the hearing, still took a contingency. That is the split this shop already runs: the model drafts. A named human owns the send.

    Do not build “AI for assessors” or “AI for tax agents.” Those slogans die in a demo. The customer is holding a notice. They want to know if the number is high relative to recent sales of like parcels, wrong on square footage or condition, or fine.

    Two primitives, one wedge

    Primitive one is photo-and-PDF review. The mills have been shipping receipt readers for months. The input here is the notice of appraised value, the assessment card, or the protest packet. Parcel ID in the header. Proposed market value in the box. Exemption lines underneath.

    Primitive two is the public roll. Counties already publish parcel data and, in most large metros, a comparable-sales extract or an open GIS layer. The checker does not invent a value. It joins the notice to the roll and to sales that closed near the valuation date, or it says the join failed and why.

    The first action a stranger will take this week is upload. Phone photo of the notice on the kitchen table. No account required to see the first verdict: high, in band, or roll too thin to judge. If it is in band, you still captured a labeled pair. If it is high, you draft the protest the owner signs.

    That is the only honest offer on day one. Do not ask them to connect a county API. Do not ask an assessor to install anything. Do not scrape the whole state before you have watched a hundred notices fail a join.

    The chatbot is a flag, not the company

    Holz and coauthors are careful. The lift was smaller among less-educated owners, lower-valued homes, and minority households — suggestive, not a clean three-way slam. A product that only talks will recreate the old lawyer gap in cheaper clothes. The wedge is the labeled join, not another chat pane on top of a PDF.

    British Columbia’s Property Assessment Appeal Board already had to write an AI disclosure rule after filings cited case law that did not exist. CBC reported the Vancouver file in late 2025. Hallucinated precedent is how this category gets banned from the hearing room. Cite the roll. Cite the sale. Do not cite a case the model dreamed.

    Douglas County, Colorado, spent August 2026 warning residents about a viral video inventing a federal “Senior Homeowner Tax Review Request.” There is no such form. A checker that points at the county’s real protest page is useful. A checker that invents a federal program is a scam adjacent.

    What compounds

    The first useful output is a three-line verdict. The business is the labeled corpus.

    After a few thousand notices you know which neighborhoods the mass-appraisal model overshoots after a sale year, which condition codes drift, which exemption lines get dropped when ownership changes, which counties publish a roll you can join and which publish a PDF theater. That map is what a property manager, a small landlord book, a union housing desk, or a county watchdog will pay for. Not another portal. A ranked list of tracts where posted value and nearby sales refuse to meet.

    Do not sell the map first. Close real questions on real notices. The dashboard of “possible savings” is how this idea dies in a pitch.

    Irreversible steps stay human

    A model can draft the protest. It can pull three comps and write the condition paragraph. It can calendar the hearing. A person owns the send. An appeal moves the tax base and creates a record the county will treat as a claim. Same rule we use on every filing in this shop: the model drafts, a named human signs.

    Do not let the product call itself an agent of record. Do not let it submit the protest, accept a contingency check, or speak at the appraisal review board. Those are seats, not features. Charge after the join shows a mismatch, or do not charge.

    What not to build

    Do not build a nationwide assessment platform in month one. You will drown in homestead rules, freeze provisions, and county file formats.

    Do not scrape every roll on day one and call it a marketplace. Most of the files will fail a join. Your first hundred uploads teach you which columns actually exist.

    Do not brand this as an agentic tax copilot. The sentence attracts the wrong first ten users and the wrong first ten deputy assessors.

    A build order that will survive contact

    • Week 1–2: one checker. Photo or PDF in. High, in band, or roll too thin. No account for the first answer. One county.
    • Week 3–4: a draft protest pack with a human signer. Comps, condition notes, exemption check. Contingency or a cheap per-letter fee only after the first free verdict.
    • Month 2: add the prior-year notice as a second document type for the same parcel. Keep one metro until the join rate is honest.
    • Month 3: publish the first ugly internal scoreboard. Tracts, mismatch rates, win rates on human-filed protests. That scoreboard is the seed of the B2B SKU.

    If you cannot get a stranger to photograph one notice this week, you do not have a company. You have a policy thread.

    Why this cut, not the last one

    The leakage essay was tariffs, seats, and subscriptions. The rebate essay was a nameplate. The recall essay was a label. The short-pay essay was a contractor packet. The bill essay was an EOB against a hospital file. This one is the property version of the same primitive pair: a document the customer already holds, plus a public file the institution was forced to publish, joined before the protest window closes.

    The noticing used to require a tax agent and a weekend. It now requires a model that can read the page and a person who will sign the form. Recovery still works because the first check costs the owner almost nothing. Charge them after the roll proves a mismatch, or do not charge them.

    Someone will own the labeled map of noticed versus sold. The mills will keep proposing a new .ai name for each county form. Ignore the names. Join the line. Keep the map.

    Will Tygart — Tygart Media.

    This is the idea-mill series.

  • Storm Updates: Southern High Plains Flood Slight, Quiet Severe Day — Friday, September 25, 2026 (Morning)

    This is a live Friday morning snapshot of local storm-type events across the United States as of the morning of Friday, September 25, 2026. The organized desk is still water on the southern High Plains, not a national wind outbreak. The Storm Prediction Center 1300 UTC Day 1 Convective Outlook, valid 251300Z–261200Z, carries no severe thunderstorm areas. Summary language from Norman: organized severe thunderstorms are not expected today. The Weather Prediction Center 12Z Day 1 Excessive Rainfall Outlook, valid 12Z Friday through 12Z Saturday, holds a Slight Risk of excessive rainfall across portions of the southern High Plains — southeast New Mexico into the Texas Panhandle and parts of West Texas.

    These are county- and ZIP-scale thunderstorms and leftover runoff, not a U.S. mainland hurricane landfall. Restoration exposure this morning is water already in low crossings and buildings from last night’s New Mexico–west Texas MCS, plus isolated heavy rain if cells redevelop this afternoon. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.

    What is live this morning

    No tornado or severe thunderstorm watches are current. The SPC watch page, updated 1300 UTC Friday, states no watches are valid. The last issued convective watch on the board is Watch 674, already expired. Yesterday evening’s 0100 UTC Day 1 outlook had carried a Marginal Risk over parts of the Texas Panhandle; that window closed overnight. Today’s 1300 UTC package dropped categorical severe probabilities entirely.

    Overnight flash-flood warnings from Midland/Odessa, Albuquerque, and El Paso/Santa Teresa covered northwestern Eddy County, southwestern Chaves County, and central Otero County in New Mexico, plus southeastern El Paso County and parts of Hudspeth County in western Texas. Those products were valid into the predawn hours — Eddy and Chaves until 530 AM MDT, Otero until 730 AM MDT, El Paso extensions into 330–445 AM MDT. By this morning desk they have expired. That is the just-hit pile, not a live warning overlay.

    Hotspot 1 — Southeast New Mexico into the Texas Panhandle and West Texas

    This is today’s flood ticket, trimmed from Thursday’s Moderate. WPC’s 410 AM EDT Friday discussion keeps a Slight Risk from southeastern New Mexico to the southern Panhandle and extends it south into parts of West Texas, where 3-hour flash-flood guidance is under an inch. Overnight activity over eastern New Mexico and the Texas Panhandle can still produce additional flooding concerns into mid to late morning. Guidance then has storms diminishing as the shortwave and deeper moisture lift northeast. Afternoon cells over West Texas can still dump 1–2 inches locally on already wet ground.

    SPC’s Day 1 discussion notes a convectively modified disturbance over eastern New Mexico lifting toward the central High Plains, mid- and high-level clouds over western Oklahoma, and only a low-probability severe gust if a stronger storm develops late this afternoon in western Oklahoma. Southern New Mexico, in the wake of the early-day MCS, may see a couple of stronger cells with some hail risk, but confidence in a severe-caliber threat is low. That is why there is no categorical severe area this morning.

    Cities and counties to watch: Artesia, Hope, Lakewood, and Brantley Lake in Eddy County; Dunken and Elk in southwestern Chaves; Sacramento, Mayhill, and Weed in Otero; Tornillo, Hueco Tanks, and rural east-central El Paso and Hudspeth Counties. Streams named in overnight warning text include the Rio Penasco, Bluewater Creek, and Agua Chiquita Creek.

    Restoration read: water first. Extraction and drying on structures that took overnight runoff. Low-water crossings and rural roads in the Sacramento Mountains and Pecos Valley stay a drive-around, not a drive-through. Stage pumps where last night’s warnings sat. Do not treat this as a wind event.

    Hotspot 2 — Western Oklahoma scatter

    SPC leaves the door cracked for a stronger storm or two late this afternoon over western Oklahoma under modest mid-level lapse rates and up to about 1500 J/kg MLCAPE, with a low-probability severe gust. Cloud cover from the departing MCS and tropical-origin moisture aloft will limit heating. This is not a watch candidate at 1300 UTC. Treat it as isolated outflow and lightning, not a Plains outbreak.

    Hotspot 3 — Hurricane Nolo, Big Island of Hawaii

    The National Hurricane Center and Central Pacific Hurricane Center are issuing advisories on Hurricane Nolo. As of the 200 AM HST Friday advisory, Nolo was near 15.8°N 155.6°W, moving north-northeast at 5 mph, with maximum sustained winds of 85 mph and a minimum pressure of 980 mb. Headline language: catastrophic and life-threatening flash flooding possible on the Big Island of Hawaii into the weekend. Local NWS Honolulu products own the island warning suite. This is a Hawaii County flood-and-wind desk, not a CONUS landfall. Fay and Gonzalo in the Atlantic and Odalys and Polo in the eastern Pacific are not U.S. mainland land threats this morning.

    Just hit

    SPC today’s storm reports for the 1200 UTC September 24 through 1159 UTC September 25 window show no tornado reports and no hail reports as of this desk. One preliminary wind report: 60 mph at Memphis in Hall County, Texas, at 1758 UTC Thursday, relayed by NWS Lubbock. That is yesterday afternoon’s High Plains Marginal, not a new overnight severe pile.

    The overnight work that did verify is water. NWS Midland issued a flash-flood warning for northwestern Eddy County until 530 AM MDT covering Artesia, Hope, Seven Rivers, Brantley Lake, Dayton, Lakewood, and Atoka. Albuquerque warned southwestern Chaves County until 530 AM MDT for Dunken and Elk, with considerable damage-threat language on the Rio Penasco and Bluewater Creek. El Paso/Santa Teresa warned central Otero County until 730 AM MDT for Sacramento, Mayhill, Weed, and several canyons, and separately warned pieces of El Paso and Hudspeth Counties where 1 to 3 inches had already fallen. Those warnings are expired this morning. Survey and extraction replace the warning overlay.

    Pulse table

    RegionMain threatsSPC / NWS / WPC levelStatus this morning
    SE NM / TX Panhandle / West TexasFlash flood, leftover runoff, isolated heavy rainWPC Slight excessive rainfallOvernight FFWs expired; Slight still live
    Western OK / southern NM cellsIsolated gust or hail, low confidenceSPC 1300 UTC: no categorical areaAfternoon scatter only
    Hall County, TX (Memphis)60 mph wind Thursday afternoonYesterday Marginal LSRJust-hit / closed
    Big Island, HawaiiFlash flood, tropical windHurricane Nolo, 85 mphLive Hawaii desk
    CONUS severe watchesNoneNo watches valid; last was 674Quiet

    What this means for restoration teams

    Friday is a Quiet Pulse on the severe side and a water desk on the southern High Plains. Overnight flash flooding in Eddy, Chaves, Otero, El Paso, and Hudspeth Counties is the work that already happened. Interior water starts a 24–48 hour mold clock. Photograph in daylight if it is safe. Do not drive flooded crossings in the Sacramento Mountains or the Pecos Valley.

    Western Oklahoma and southern New Mexico may still fire isolated strong cells this afternoon. Staff that as local lightning and a possible isolated gust or hail stone, not a regional wind swath. Hawaii County is a separate tropical-flood ticket under Nolo. Do not mix that crew map with the New Mexico overnight pile.

    What this is not

    This is not a regional derecho and not a U.S. mainland hurricane landfall. SPC has no Day 1 severe area. No convective watch is up. Thursday’s Moderate flood risk over southeast New Mexico has been stepped down to a Slight. The work this morning is leftover water and a trimmed rainfall overlay. That is the local-storm pattern this desk should staff.

    Looking ahead

    The SPC 0600 UTC Day 2 Convective Outlook, valid 261200Z–271200Z Saturday, carries a Marginal Risk of severe thunderstorms for portions of the central and southern Plains. Summary: isolated hail and damaging winds may accompany a few strong to severe thunderstorms Saturday from parts of Kansas into western Texas and Oklahoma, including the Wichita-to-Lubbock corridor. Watch the afternoon Storm Tracker rather than treating Friday’s quiet severe map as the weekend map.

    Sources and how to verify

    Primary sources: NOAA Storm Prediction Center 1300 UTC Day 1 Convective Outlook for Friday, September 25, 2026; SPC current watch page (no watches valid; last issued Watch 674); SPC storm reports for 1200 UTC September 24 through 1159 UTC September 25; Weather Prediction Center Day 1 Excessive Rainfall Outlook discussion issued 410 AM EDT Friday; National Weather Service flash-flood warning text from Midland/Odessa, Albuquerque, and El Paso/Santa Teresa overnight; National Hurricane Center / Central Pacific Hurricane Center advisory on Hurricane Nolo at 200 AM HST Friday.

    Check weather.gov for the county warning, spc.noaa.gov for the outlook, watch, and LSRs, and WPC excessive rainfall for the flood overlay. Prior desk: Thursday afternoon, September 24 storm updates.

    Informational only — not an official weather warning. Follow local authorities and the National Weather Service. Turn around, don’t drown.

  • We Retired the Living Leaderboard. Date Your AI Comparison Pages.

    We Retired the Living Leaderboard. Date Your AI Comparison Pages.

    Direct answer: a living AI model leaderboard rots. On the public Claude 4.6 vs GPT-5 leaderboard we replaced the promise that standings were “continuously updated by our autonomous tracker” with a September 2026 editor’s note. The table stayed. The date stayed. The page is now a snapshot of the race on 30 May 2026 — not a live scoreboard.

    If an answer engine cites an undated comparison as current, it will be wrong within a release cycle. Date the page. Point prices at a desk you actually re-verify. Leave last season’s Elo alone unless you re-measured it.

    What changed on the public pages

    Three live URLs now say the same thing in different words:

    • Claude 4.6 vs GPT-5: The 2026 Leaderboard — editor’s note that the autonomous tracker retired after the 30 May 2026 update. The LMSYS box still reads Last Updated: 2026-05-30, with Claude 4.6 Sonnet (Elo 1345), GPT-5 Early Preview (Elo 1338), and Claude 4.6 Haiku (Elo 1312). Those numbers were not rewritten this month.
    • Claude 4.6 Roadmap: Guide for Technical Founders — September 2026 editor’s note at the top of the body: the roadmap is a May 2026 generation snapshot. Stop 2 now points at the leaderboard snapshot for where Claude 4.6 stood against GPT-5 in May 2026.
    • Anthropic Slashes Claude 4.6 Haiku API Pricing by 40% — September 2026 outcome note. The phrase “verified Claude pricing page” goes to the live desk at /claude-ai-pricing/, not to a second rate card buried in the old post.

    Titles and slugs did not move. The old URLs are the record.

    Why a “living” leaderboard fails the reader

    Model names, list prices, and context windows moved several times between that May snapshot and late September 2026. The live Claude desk we keep — last verified 23 September 2026 against Anthropic’s own pages — is a different document from a May Elo box. Mixing them on one URL trains both humans and models to treat last season’s table as this week’s answer.

    That is an AEO problem and a GEO problem. Answer engines prefer a short, dated sentence they can lift. Generative engines prefer a page that does not contradict the next page in your cluster. A tracker you cannot staff is worse than a snapshot you labeled.

    The method: snapshot the race, live-link the meter

    1. Put the as-of date in the first screen. “Last Updated: 2026-05-30” in the box. “Editor’s note (September 2026)” above it. Two dates, two jobs: when the numbers were taken, when you admitted they froze.
    2. Do not invent a new leaderboard you did not run. We did not scrape LMSYS tonight. We did not publish a September Elo column. If the measurement is not in the room, the number does not go on the page.
    3. Send current prices to one desk. Token rates and seats live on Claude Pricing (September 2026). The Haiku cut post now points there. A short companion on the 22 September Opus list sits at Claude Opus 5.5 Cuts Token Price 20% — $4 / $20 List. Quote the desk. Do not fork a third table.
    4. Keep the historical URL. Changing the slug of a comparison page that already earned links and citations throws the evidence away. Date the body. Leave the address.
    5. Say what the page is not. A May snapshot is not a buying guide for today’s default model. A 40% Haiku headline from an earlier cycle is not the live list. The pricing desk is the live list.

    What we would not claim

    • We would not claim a September 2026 LMSYS or Arena ranking. We did not pull one for this note.
    • We would not claim Claude 4.6 is still the current default. The live desk names current Opus, Sonnet, Haiku, and Fable lines separately. Read that page for names and rates.
    • We would not restated a full rate card here. Rates move. The desk is dated 23 September 2026 and cites claude.com/pricing and platform.claude.com.
    • We would not describe internal work orders, agents, or edit packets. Those are not the public record. The public record is the three URLs above.

    How to write the editor’s note so an answer engine can use it

    Keep the note to one sentence that answers “is this current?” Then link the current desk.

    Pattern we used: Editor’s note (Month Year): the living tracker was retired after [snapshot date] — the standings below are preserved as a snapshot of the race at that point.

    That sentence is the AEO payload. It is short. It names the freeze date. It tells a model not to treat the table as live. GEO follows if the rest of the cluster agrees: founder roadmap says snapshot, pricing post says “go to the desk,” desk says last verified.

    FAQ

    Q: Should I delete an old model comparison?
    A: No, if the URL already has links or citations. Label it a snapshot, keep the slug, and point current buyers at the live desk.

    Q: When does a snapshot need a new page instead of an editor’s note?
    A: When the question changed. “Where did Claude 4.6 sit vs GPT-5 in May 2026?” is a history question. “What does Claude cost this week?” is a desk question. Different questions get different URLs.

    Q: Can I keep a living tracker?
    A: Only if someone re-measures on a published cadence and the page shows the last run date. A tracker you do not run is a lie with a progress spinner.

    Q: Where are current Claude prices?
    A: tygartmedia.com/claude-ai-pricing/, last verified 23 September 2026 against Anthropic’s public pricing pages. Confirm Anthropic before you quote a customer.

    Q: Does this mean the May Elo numbers were wrong?
    A: It means they are dated. They remain the numbers printed on that page for 30 May 2026. They are not a September 2026 ranking.

    Sources

    • Live pages on tygartmedia.com, read 24 September 2026: leaderboard snapshot, founder roadmap snapshot note, Haiku pricing outcome note, Claude pricing desk (desk last verified 23 September 2026).
    • Official Anthropic seats and API tables linked from the pricing desk: claude.com/pricing and platform.claude.com pricing.

    Related on Tygart Media: May 2026 leaderboard snapshot · founder roadmap snapshot · Haiku pricing note · live Claude pricing desk · Opus 5.5 list-price note · the site has to be the answer.

    I write pages like this so AI search cites a dated sentence instead of last season’s table — then I do the same for operators who publish. That’s what Tygart Media does.