AEO & AI Search - Tygart Media

Category: AEO & AI Search

The next customer may arrive through a ChatGPT answer, a Perplexity citation, or a Google AI Overview. AEO is how a company shows up there.

  • They Say GEO Isn’t Real. Watch a Website Answer Questions About Itself.

    They Say GEO Isn’t Real. Watch a Website Answer Questions About Itself.

    People keep telling me AEO and GEO are the new snake oil. Acronyms invented to sell audits. “SEO is SEO,” they say, “and the rest is conference talk.”

    Fine. Let me show you the thing itself, on a site I run, with nobody’s hands on the scale.

    What you’re watching

    That’s Healthcare Facility Hub — a site for people who run hospital facilities. In the corner of every page sits an AI that knows one thing: the site itself. It’s trained on the site’s own content and nothing else. No open internet. No general model knowledge doing the heavy lifting. If the answer isn’t in the site’s pages, the AI doesn’t have it.

    I spent five minutes asking it questions on camera. Three things happened, and they’re the whole argument.

    First: it answers like the content is a database

    Ask it what an infection control risk assessment requires and it doesn’t write an essay. It returns the site’s own material as structure — the risk classes, the types, and then, when I push on negative air pressure, the actual working numbers: the target pressure, the alarm setpoints, the HEPA specs a facilities team would use on a job.

    That’s not a chatbot being clever. That’s what happens when every page is built as a clean, standalone record — one question, one complete answer, the facts in the open — instead of a pile of marketing prose with keywords folded in. The AI can pull from it because the page was built to be pulled from.

    Second: ask it something the site doesn’t have, and it says so

    I asked it for stories about Chicago. It said: we don’t have any content or stories about Chicago in our current site resources.

    Sit with that for a second. The big chatbots, asked the same question, would give you Chicago stories — real, invented, blended, who knows. This one refused, because its world ends at the edge of the site’s content, and it knows where the edge is.

    That’s not a limitation of the demo. That IS the demo. An answer engine is only ever as good as the corpus it can draw on. When the corpus is disciplined, the answers are disciplined. When there’s nothing there, an honest system says nothing’s there — and a visitor, or an engine deciding what to cite, can trust everything it did say.

    Third: the answer ends at an asset

    Follow the thread to the end of the video and I’m not reading a blog post. I’m opening a one-page field sheet — the article distilled into a printable PDF with a QR code, made to be carried onto a hospital job site.

    That’s the shape of the whole thing. A question gets asked. The structured content answers it. The answer hands you something usable. Search used to end at a blue link and a hope. This ends at a tool in a facility manager’s hand.

    Why this is what the engines are doing to you

    ChatGPT, Perplexity, Copilot, Google’s AI — different companies, same basic move. They read corpora, they extract answers, they cite the sources that could answer. Your website is either a corpus they can extract from, or it’s a brochure they skim past on the way to somebody else’s.

    We measure this instead of arguing about it. We run a fixed battery of questions a buyer would actually ask, score what our sites’ AI answers from their own content, and log where it has nothing — those gaps become the next pages we write. This morning, on a sibling site in a different industry, that battery came back 24 passes out of 36, with the misses itemized as a content list. The scoreboard is not a vibe. It’s a work queue.

    And the citation side gets measured too — which engines cite which sites, on which questions, over a trailing thirty days. When the numbers move, we know why, because we know what we published and what it answered.

    The part nobody wants to hear

    None of this is a trick you bolt onto an existing site. The AI on that page answers well because the site underneath it was rebuilt to be a knowledge base — treated like a headless database that happens to have pages attached. Every article answers one real question, in the words the asker would use, with the numbers in the text where an extractor can find them.

    If an AI trained only on your own website can’t answer your customers’ questions, the big engines can’t either. They’ll answer from a competitor whose site can. That’s not a threat I’m selling. It’s arithmetic you can run on your own site this afternoon — most sites have a chat box or a search bar you can interrogate. Ask it your customers’ five best questions. Count what it actually knows.

    We already know how that count comes out for most sites. It’s why the phone rings here.

    The recording is unedited screen capture from healthcarefacilityhub.org, October 22, 2026 — the site’s own AI, its own content, my own questions. Narration on the video is Glint, my AI. This is the work, on tape.

    Run the count on your own site

    The AI Citation Quick-Scan asks ten homeowner prompts — the questions your buyers actually put to ChatGPT, Perplexity, and Copilot — and shows you whether your business is the answer, and if not, who is. It is the same interrogation I ran on camera, pointed at your market: the AI Citation Quick-Scan, $97 — and the $97 comes off the package price if you move forward.

  • Can a Vendor’s Own “Best Tools” List Earn AI Citations If It Discloses Who Wrote It?

    Can a Vendor’s Own “Best Tools” List Earn AI Citations If It Discloses Who Wrote It?

    Disclosure, up front — because that is the subject of this article. Tygart Media sells AI search visibility work. We publish our own tool pricing and comparison pages, and this site is a vendor in the category this article examines. Every number below comes from one named study, with its method stated, so you can check it the way we did.

    The short answer is yes. A disclosed vendor comparison can earn AI citations, because the engines are barely scoring authorship at all. In the largest count anyone has published, between a third and a half of the “best tools” lists cited in AI answers were written by a vendor selling in that category. The traits that measurably raise a page’s citation odds are a comparison table and a stated selection method — not who published the page.

    What got counted

    In August 2026, the agencies Minuttia and Convex Works asked 18,084 software-buying questions across six platforms — Google Search, AI Overviews, ChatGPT, Gemini, Claude, and Perplexity. They then read all 311,766 pages those platforms cited and labelled each one by who published it and what kind of page it is. It is the first count of vendor-written lists in AI answers that works from the cited pages themselves rather than from opinion about them.

    The study’s own caveats deserve the same prominence as its findings. Every share it reports is a floor, because pages its team could not read were counted as not self-promotional. And the results are a snapshot, not a standing: when the researchers re-asked Perplexity 2,000 of the questions a month later, only 28% of the pages in the new answers had been there in August. Citations churn. Anyone measuring them from a single screenshot is reading weather and calling it climate.

    How much of the answer is a vendor grading its own homework

    For “best alternatives to X” questions, 34% to 47% of the listicles the platforms cited were a vendor’s own list, depending on the platform — 47% on Google and Gemini, 34% on ChatGPT. For “how do X and Y compare” questions, the vendor-written share rises to between 56% and 65%. Across every category and question type, 43% of cited listicles are self-promotional.

    The spread by category is wider than the average suggests, running from 12% in audio production to 76% in AI security operations. AI visibility — the category this site sells in — sits at 65%, one of the most self-promotional categories measured. If you buy or sell in a software category, the honest working assumption is that a large share of the “best tools” content the machines quote was written by someone ranked in it.

    The lists themselves behave the way you would expect. Of the vendor-written lists the platforms cited, 93% highlight the vendor’s own product, 87% rank it first, and 90% criticise competitors. Only 16% clearly disclose that the vendor wrote the page. The typical cited list, in other words, is an undisclosed advertisement that puts its author first — and the engines cite it anyway.

    Each engine shops differently

    ChatGPT searches the way a buyer going straight to the source would. In 71% of the searches it ran before answering, it named exactly one product, and 92% of its site-limited searches pointed at a vendor’s own website. On alternatives questions, vendors’ own sites made up 42% of ChatGPT’s citations, against 1% to 6% on the other platforms. For ChatGPT, the vendor’s own pages are not a contamination of the research — they are a primary input to it.

    Perplexity works more like an editor with a pile of candidates. A typical answer finds about 20 pages and cites 9 of them, and which pages survive depends first on where they sat in its search results. Here is the finding that reframes the whole question: of the pages Perplexity found, vendor-written listicles were cited 58% of the time — the highest citation rate of any page type it found, ahead of independent listicles at 44% and review sites at 36%.

    There is no single shelf to win, either. Only 21% to 28% of the citations from AI Overviews, Gemini, Perplexity, and Claude also appear in Google’s top 10 results for the same question. Each engine assembles its own evidence, which means a page earns its place engine by engine, on traits each engine can see.

    The traits that actually move a citation

    Perplexity is the one platform where the study could watch the selection happen — every page found, then which ones got cited. Holding search position equal, here is how often a found listicle was cited with and without each trait:

    Trait Cited with it Cited without it
    Has a comparison table 70% 60%
    Says how the tools were picked 69% 61%
    Longer than the typical list 68% 62%
    Year in the title 68% 63%
    Written by a vendor in the category 64% 68%
    Promotional tone 64% 69%
    Ranks its own product first 64% 65%

    Read the table from the bottom up and the story tells itself. Ranking your own product first — the move that looks most like cheating — costs about one point. A promotional tone costs about five. Being a vendor at all costs about four. Now read the top: a comparison table is worth ten points, and stating how the tools were selected is worth eight. The penalties for self-interest are small and the rewards for being genuinely useful are larger, on the same scale, in the same measurement.

    One honesty note about this article’s own title: the study never isolated disclosure itself as a citation trait, so no one can honestly claim a measured disclosure bonus. What the study did measure is disclosure’s closest cousin — a page that says how its tools were picked gets cited more, not less. Nothing in the data shows an engine detecting a disclosure line and punishing it, and the 84% of vendor lists that hide their authorship are not winning because they hide. They are winning in spite of it, on tables, method, length, and position.

    So why disclose, if the machines don’t make you

    Because the citation is only half the transaction. The other half is the human who clicks through from the answer and decides whether to trust the page in front of them. A list that hides its author converts every citation it earns into a small liability: the reader who discovers the trick discounts not just the list but everything else the vendor says. Disclosure costs no measurable citation share, and it is the only version of the page that survives both readers — the machine counting traits and the person counting on you.

    This is also a game a small operator can actually win. Vendor-written lists that earn citations come from smaller sites than the independent lists they compete with — a median domain rank of 49 against 63 — and the field is fragmented: the 20 most-cited vendors together hold only 6% of the citations. There is no incumbent wall here. There is a craft bar, and it is published in the table above.

    The rules we publish by

    • Disclose at the top, not in the footer. If a page compares a category we sell in, the first screen says so. A disclosure a reader has to hunt for is a hiding place with better manners.
    • State the selection method. How the tools were picked is a measured citation trait, not just an ethical nicety. Write the method before the rankings, and let the rankings follow from it.
    • Put the comparison in a real table. Rows a machine can parse and a person can scan. The table is worth more citation share than any headline about yourself.
    • Earn first place or don’t take it. Ranking yourself first costs almost nothing in citations and almost everything in credibility when the method on the same page doesn’t support it.
    • Date it and keep it current. A year in the title is itself a small citation trait, and a stale list quietly stops being evidence. Lists are maintained assets or they are litter.
    • Publish the data behind the claims. Minuttia released the data behind every chart in its study so competitors could check the work. Checkable beats confident, with machines and with people.
    • Measure citations as a 30-day rate. A quarter of the cited pages turn over in a month. A rate over time is the only reading that distinguishes a page that earns its place from a page that got lucky once.

    The engines have already decided the underlying question: vendor lists are sources now, cited at rates no one can opt out of by refusing to write them. The live question is narrower and more useful — whether your list reads as evidence or as advertising when it gets there. The disclosed list, with its method stated and its comparison in a table, is the one built to be both.

    Study: Minuttia × Convex Works, “Self-Promotional Content Data Study” (August 2026 data), self-promotional-content-data-study.minuttia.com — full data published with the study. Coverage: Digital Market Reports, October 22, 2026.

    AI Citation Quick-Scan — $97

    This article is about whether your pages earn citations. The Quick-Scan runs that test on your company: ten real homeowner prompts across the major AI answer engines, with a written report — and the $97 comes off the package price if you go further. Built for restoration contractors.

    Get the Quick-Scan — $97

  • Move the Design System Before December 14 — the Chat Does Not Come With It

    Move the Design System Before December 14 — the Chat Does Not Come With It

    The standalone Claude Design site at claude.ai/design closes on December 14, 2026. After that date, the address opens Claude. Anthropic’s announcement gives the reason in one sentence: “Running two versions slows down fixes for both, so we’re folding the standalone site into Claude.”

    The migration that Anthropic offers moves design systems. It does not move projects. And the parts of your work that live only in the standalone product — the chats, the comments, the originals — have a deletion date, not a transfer path. This is the procedure for a team that has brand systems and client one-pagers in there, in the order the steps have to happen.

    What gets deleted, exactly

    Anthropic’s migration guide names the deletion list in two bullets: “Your chats with Claude” and “Comments on your projects and design systems.” Those stay in the standalone version and are deleted after it closes, per Anthropic’s data retention practices.

    Your originals are a separate statement, in the guide’s FAQ: they keep working in the standalone version until it closes on December 14, 2026, and “after that, they’re deleted.” A design system you migrate leaves its original behind in the standalone product, unchanged — and that original is on the same clock.

    Public links to standalone projects are a third outcome, and the guide words it differently on purpose: they “will no longer work after it closes.” Not deleted — dead. Every client you sent a public project link to holds a URL with an expiry date.

    The instruction Anthropic prints is the whole strategy for this section: save anything you need from your chats and comments before the standalone version closes. No fetched Anthropic page documents an export for chats or comments. The capture that matches the documentation is a screenshot of each comment thread and a copy of the chat text, done by hand.

    The dangerous sentence: “You don’t need to do anything with your projects yet”

    That sentence is in the migration guide, and it is true — your projects keep working in the standalone version until the close. It is also the sentence that will get client work deleted, because projects are the files with no migration path and a deadline.

    The Artifacts page in Claude lists up to 60 of your standalone projects, and they open in the standalone version. That list is a directory back into the product that is closing. It is not a move, and it is not a complete inventory if your team has made more than 60 projects. Anthropic’s position, in the guide’s words: “More details about moving your projects to Claude are coming soon.” Soon is doing a lot of work in that sentence, and December 14 is 56 days out.

    So the inventory step happens in the standalone product itself, not on the Artifacts list. Walk the standalone library for every client one-pager, deck, and brand system — including everything past the first 60 the Artifacts page shows.

    Before anyone clicks Migrate: the sharing problem

    One migration brings over every design system in your organization, including other people’s. It only needs to be started once — and anyone who can use Claude Design can start it, not just the organization’s owners. On individual plans there is no confirmation step at all: click, and it starts.

    The consequence that matters for a shop holding more than one client’s brand: “Published design systems that aren’t private will be shared with everyone in your organization and appear in their design system menu.” A system you published so your own projects would use it becomes an entry in every teammate’s menu the moment anyone runs the migration. On individual plans, nothing is shared — this is a team and organization trap, not a solo one.

    The precaution has to happen before the first click, because undoing it is not documented. In the standalone product, the setup guide names the Published toggle as the control that makes a system the organization’s working system. For every design system that should not appear in the whole organization’s menu, turn that toggle off first. A second migration is not a way back: a later run leaves an unchanged system alone and skips one that has changed inside Claude, so neither pass pulls a system out of the menu.

    Two kinds of systems do not migrate at all, no matter who clicks: “Empty design systems aren’t migrated, and neither are ones made from a built-in starter theme, even if you’ve edited them.” If your house brand began life as a starter theme you customized, the migration will silently leave it behind. There is no documented design-system export to fall back on. Copy the source assets out by hand before December 14.

    The export drill: one project, one zip

    There is no bulk download. Anthropic’s FAQ is blunt: “Not all at once. You can download them one at a time.” Open the project in the standalone version, click Share, choose “Project HTML” — for a slide deck, that item hides under “More formats and apps” — keep “Project archive” selected, and click Export.

    You get a .zip file with every file in the project. It is free and does not count toward your usage limits. Repeat it for every client one-pager and deck you cannot afford to lose, and store the zips outside Claude.

    Know what the zip is not. It is documented as every file in the project. Chats are on the deletion list, and no Anthropic page says the conversation comes along inside the archive. The zip preserves the files. The reasoning your team talked through in chat, and the client’s comments on the work, survive only if you captured them in the previous step.

    Enterprise: three switches, and one hard stop

    On Enterprise plans the migration is gated by settings that are easy to flatten into one wrong sentence, so take them separately. Artifacts themselves must be on — if they are off, people cannot migrate anything and will not even see the “Claude Design lives here now” banner.

    Design systems are a separate template switch: on for Team plans, off for Enterprise until an owner turns on Design systems in Organization settings > Artifacts. That is a different switch from Design and Slides, which Anthropic’s pages say were set to turn on by default on October 15, 2026 — a date that has now passed, with the help text still printing the scheduled sentence, so check your own settings rather than assuming either state. On plans with custom roles, each role also needs the Artifacts permissions, and a design system cannot be migrated if its owner’s role does not include design systems.

    The hard stop: “Organizations with zero data retention (ZDR) can’t turn on artifacts, so they can’t migrate.” If that is your organization, the migration procedure does not exist for you. The guide’s path is the per-project download, done before the close, one zip at a time.

    One more setting that does not do what an admin might hope: the Enterprise custom-retention article states that custom retention periods “do not apply to Claude Design.” The retention dial your organization already configured is not the instrument that keeps or deletes standalone chats, comments, or originals. The closure is.

    After it lands

    A migrated design system keeps its files as they were, and it cannot be hand-edited on its page yet. Its editors see the note: “Migrated from the standalone version. Ask Claude to make changes.” The editing model for a migrated brand system is a conversation, not a settings page.

    If someone edits a migrated system inside Claude and you later run the migration again, that system is listed under Skipped — “changed on claude.ai, left as they are” — so your edits are not overwritten. Replacing it with a fresh copy is a deliberate act: duplicate it first if the Claude-side changes matter, delete it in Claude, then migrate again.

    New design work lives in three doors now: any chat (ask for a design, or Output > Design in the message box), the Artifacts tab, and Claude Code, with /design to create, edit, and sync designs and /design-sync to pull in your design system. All of it draws on the same usage pool as the rest of Claude, including Claude Code — the separate weekly Claude Design allowance the product launched with is already gone, per the get-started guide.

    Two gaps in the new home are worth knowing before you move the team: Claude Design does not have version history yet, and inline comments there occasionally fail to appear on the page — Anthropic’s own workaround is to paste the feedback into the chat instead. The standalone product’s comment threads, the ones being deleted in December, are still the reliable record until you screenshot them.

    The order is the procedure

    Inventory in the standalone product. Turn off Published on anything that must not become an organization-wide menu entry. Mark the empty and starter-theme systems the migration will refuse, and copy their assets out by hand. Export every project that matters, one zip at a time. Screenshot the comments and copy the chats. Only then — owners having turned on Artifacts, Design systems, and the role permissions — does one person click Migrate, read the results window, and fix any failed system in the standalone product before running it again.

    Do those steps in that order and December 14 is a non-event: the address starts opening Claude, and everything you cared about is already there or already saved. Do them out of order — migrate first, inventory later — and the button will happily move the systems while the projects, comments, and originals sit in a product with 56 days left on it. We track vendor surface changes like this one on the desk because the procedure is always in the help pages; it is just never in the announcement. The announcement for this closure said chats and comments “won’t be available.” The help center is the text that says deleted.

    Sources: Anthropic’s migration guide, Migrate from standalone Claude Design to Claude, and the get-started guide, Get started with Claude Design, both read in full on October 19, 2026. A related surface change, worked the same way: Cursor’s shareable canvases, and how we check a vendor’s what’s-new claims in What’s New in Cursor Is a Claim.

  • Six in Seven AI Answers Never Look Anything Up

    Six in Seven AI Answers Never Look Anything Up

    Most of what an AI answer says about your business was never looked up. It was remembered — or invented in the shape of a memory. Ahrefs put a number on that in a study published October 12, 2026: across 66.6 million free, logged-out ChatGPT responses from August and September 2026, a web search ran in only 14.4% of them. Six in seven answers were written without checking anything.

    That single fact reorganizes the work. If the answer usually comes from what the model already carries, then being findable is only half the game. The other half is being known — and, for the one answer in seven where the engine does go looking, having the fact it needs sitting in plain text on your own domain, where it looks first.

    The search, when it happens, is narrow

    The same study logged 15 million fan-out queries — the searches ChatGPT issues behind an answer when it decides to search at all. A searching response ran about 1.6 of them on average. This is not a research department fanning out across the open web. It is a quick, targeted check, and the targeting is the story.

    6.8% of those fan-out queries used a site: operator to search one specific website, spread across roughly 116,000 domains. Among the most common of those targeted searches, 75.9% pointed at a brand’s own site — not a retailer, not a forum, not a review aggregator. When the engine wants a price or a specification, it goes to the company that sells the thing.

    The vocabulary inside the queries leans the same way. The word “official” appeared in 13.1% of English fan-out queries in September 2026, up from 10.1% in August. “Price” climbed from 6.04% to 8.88% of fan-outs in the same month — a relative rise of nearly half. The engine is increasingly searching for the authoritative version of a fact, and the facts it most wants are commercial ones: what it costs, what it includes, what the official page says.

    Facts go home; comparisons wander

    Ahrefs paired the fan-out data with a separate test of 20,000 US prompts, and the split inside it is worth keeping separate in your head, because it is a different instrument from the 66.6 million. In that test, 84.4% of factual questions — pricing, product features, company details — cited at least one official source. For factual questions, 63.4% of all citations pointed at official websites. For comparison questions (“A vs B,” “which is cheaper”), the official share fell to 46.4%: most citations went somewhere else.

    Read together, the two datasets describe one behavior with two modes. Asked for a fact, the engine goes home to the source. Asked to judge, it goes out to the crowd. An operator cannot control the judging mode. The fact mode is entirely winnable: it is won by having the fact, in the open, on the domain the engine already searches by name.

    The playbook that follows

    Publish the price, the spec, and the support fact in plain text on your own domain. Not in a PDF the crawler has to excavate, not inside a configurator, not implied by a sales page’s adjectives. The fan-out query literally contains the words “official” and “price” — it is asking for a page that states the number. Whoever states it cleanly gets cited for it.

    Publish the pages only you can publish. Your measured results, your actual process, your own numbers with dates on them. A summary of somebody else’s facts competes with the original; the original is what the engine is learning to prefer (the citation movement below shows how far that preference has already moved).

    Treat fan-out queries as an instrument of their own. The queries an engine issues about your category — which words it adds, which domains it targets, how that shifts month to month — are a measurement channel separate from citation counts. Watch them separately. We grade the flight recorder, not just the answer, for the same reason: the queries show the intent; the answer only shows the outcome.

    Never blend two dashboards into one story. The 14.4% comes from 66.6 million free logged-out responses. The 84.4% comes from a different, 20,000-prompt test. The citation movements in the next section come from a third cut again. Each number is true inside its own denominator and misleading outside it. This is the same discipline we run on our own visibility work: being cited is not being chosen, and being measured is not being measured the same way twice. Our running instrument for the citation side is the Citation Pulse.

    The second movement: summarizers are losing

    Ahrefs’ Brand Radar citation data for the US — 2.4 million ChatGPT answers in March 2026 against 3.8 million in September, a different dataset from the fan-out study above — shows where the citations went. Reddit fell from roughly one citation in every five answers in March to about one in 43 by late September. Wikipedia fell from one in seven to one in 35. The share those summarizers and forums lost moved to research bodies, regulators, brand and support pages, and hands-on testers. On a matched set of about 25,000 prompts present in both months, every tracked site moved in the same direction, so the shift is not an artifact of new questions entering the sample.

    For an operator, that is the durable part of the whole study. The memory answers reward whoever the model already knows. The searching answers reward whoever publishes the primary fact. The citation trend rewards the originator over the summarizer. All three roads end at the same address: your own domain, carrying your own facts, in plain text.

    The same citation movement, read for hospitals and the firms that build for them — why clinical and facility specifications now have to live as primary documents — is on Healthcare Facility Hub: The Citation List Is Moving Toward the Source Document.

    Sources: Ahrefs, “How ChatGPT Does Query Fan-Out” (October 12, 2026) — fan-out dataset (66.6M responses, 15M queries, Aug–Sep 2026), the 20,000-prompt official-source test reported in the same article, and the Brand Radar US citation comparison (2.4M answers March 2026; 3.8M September 2026). Each figure above is stated with the dataset it came from; the three are not interchangeable.

  • Which AI SEO services are right for a small business?

    The right AI SEO services for a small business are the ones matched to where your customers actually ask questions. For most local service businesses, that means three things, in order: a business profile the machines can read, answer pages on your own website written the way customers ask, and a scheduled check that shows who the machines name.

    What are AI SEO services?

    AI SEO services are services that make a business readable to AI answer engines. A traditional search engine returns a list of links; an AI assistant returns an answer, and it names the businesses it can read clearly. AI SEO is the work of giving those systems clean material — profiles, pages, and consistent facts — to name you from.

    The category is new enough that the label covers very different work. One provider’s “AI SEO” is a rebuilt Google Business Profile and a page of real answers. Another’s is a software subscription and a monthly PDF. The sections below separate the kinds, so you can buy the work instead of the label.

    What kinds of AI SEO services are there?

    AI SEO services come in five kinds: listing and profile work, answer-page writing, citation cleanup across directories, one-time audits that measure where you stand, and ongoing retainers that bundle all of it. Most small businesses need the first three once, the audit before and after, and a retainer only when the market moves fast.

    • Profile work builds the listings machines read first: Google Business Profile on Google’s side, Bing Places on Microsoft’s — the listing Copilot and the assistants built on Bing read from.
    • Answer-page writing puts pages on your own website that answer customer questions in customer language, in passages short and plain enough to be quoted.
    • Citation cleanup makes your name, address, phone, and services agree across directories and aggregators — Yelp, Foursquare, Apple Maps, Angi, and the data feeds behind them.
    • Audits and scans measure the starting point: a fixed set of questions, asked before the work and after, with the answers kept.
    • Retainers bundle the above into monthly work. They fit businesses in fast-moving markets; they are a poor fit for one-time fixes billed forever.

    How is AI SEO different from traditional SEO?

    Traditional SEO earns a position on a list of links; AI SEO earns a mention inside an answer. The list rewards the page; the answer rewards the clearest source. Both run on the same foundations — a readable website, consistent business facts, reviews, and real expertise — but the AI layer reads quotable passages, not just pages.

    That difference changes what good work looks like. A page stuffed with keywords can rank and still never be quoted, because there is no clean passage to lift. A plainly written answer — the question as the heading, the answer first, the detail after — gives an assistant something it can repeat word for word. Traditional SEO is not replaced by this; it is the floor it stands on.

    What should a small business buy first?

    A small business should buy in the order a customer asks. First, the profile a machine reads when someone asks for your trade nearby — your Google Business Profile and your Bing Places listing. Second, answer pages on your own site. Third, a measurement check. Software subscriptions and content volume come last, if at all.

    The order matters because the surfaces compound. An assistant answering “who does this work near me” starts from profiles and listings, then checks what your website says. A beautiful website behind an empty profile is invisible at the first step. A strong profile pointing at a website with no answers gives the machine nothing to quote. Buy the chain in order and each link makes the next one worth more.

    How much do AI SEO services cost?

    AI SEO services are sold three ways: one-time builds, monthly retainers, and small diagnostics. The honest difference is not the label but what you can hold afterward — a finished profile and pages you own, or a report you can re-run. Any price is too high for work you cannot inspect when it is done.

    Price follows scope: number of locations, number of services, number of towns you serve. What should make you careful is shape, not size. One-time work — a profile build, an answer page, a listing cleanup — should carry a one-time price. Monthly money should buy monthly work you can name: new questions tested, new answers written, changes logged. If a provider cannot tell you which of your dollars are one-time and which recur, that is the answer to whether to sign.

    What questions should I ask an AI SEO provider before I pay?

    Ask an AI SEO provider five questions before you pay: What exactly will exist when you are done? Which questions will you test, and can I see the answers before and after? What do you not control? What does the work cost once, and what recurs? Who owns the pages and profiles afterward? Ask us the same five.

    Each question has a tell. “What will exist” should produce a list, not adjectives. “Which questions” should produce your customers’ actual questions, written down. “What do you not control” is the honesty test — no provider controls which businesses an assistant names, and one who promises a ranking is telling you how the rest of the engagement will go. Ownership is the quiet one: profiles and pages built on your accounts, in your name, stay yours if you leave. Anything else is rent.

    What proof should an AI SEO service show me?

    An AI SEO service should show you a named report, a date range, and the questions it tested — not a screenshot of a ranking. On our own site, the proof habit looks like this: our Bing AI Performance report for tygartmedia.com, covering six months of Microsoft Copilots and partners, shows 1.5M total citations across an average of 164 cited pages.

    Read those numbers the way we do. They are our own footprint on one measured surface — evidence that the measurement exists and that we live under it — not a promise about your business. AI answers also churn: the same question asked next month can name different businesses, which is why honest proof is a before-and-after on your questions, re-asked on a schedule, with the raw answers kept. A provider who shows you their own numbers should be just as willing to show you yours.

    Can I do AI SEO myself?

    Yes — the free layer of AI SEO is real work any owner can do: claim and complete your Google Business Profile and Bing Places listing, write your services in plain language, and answer your customers’ common questions on your own site. What you pay a provider for is the audit discipline, the writing time, and the measurement habit.

    Be honest with yourself about which of those three you will actually do. The profile most businesses already “have” is a name, a pin, and hope — claimed years ago and never finished. The knowledge is not the scarce part; the finished, checked, written-down work is. If you will do it yourself, the sections above are the whole recipe, in order, and they will work the same for you as for us.

    Where does our own offer fit?

    If you want to know where you stand first, our AI Citation Quick-Scan runs 10 prompts about your service line and returns a scored report within 7 days — $97, one time. If you want the build done, the Ask Maps Protocol is our version: $450, one time — a mobile-first audit of how your listing actually renders, your Google Business Profile rebuilt for answers, an FAQ answer page on your website, your Bing Places listing claimed and matched, and a 30-day proof check.

    Which lines the platforms lift is their call. We build the material they lift from — and then we measure what they did.

  • All My Reviews Just Say ‘Great Service’ — Do the Words in My Reviews Matter to AI?

    Short answer: Yes — the words matter more than the stars. When someone asks for “a reliable plumber who handles emergency leaks,” the AI recommends the business whose reviews keep saying “quick response” and “emergency repair” — not the one with fifty generic five-stars. Review text is the evidence the bot quotes. A wall of “great service” gives it nothing to quote.

    How the bot actually uses your reviews

    Think about what the AI is doing when it answers “who should I call.” It’s matching the words in the question to evidence it can find. If the question asks for emergency leak help, it looks for businesses with evidence of emergency leak help. And the richest source of that evidence isn’t your website copy — it’s your customers describing what you did, in their own words.

    One analysis of business profiles in AI search put it directly: “If a user asks for a ‘reliable plumber who handles emergency leaks,’ the AI will likely recommend a business whose reviews frequently mention ‘quick response’ and ’emergency repair’ over a business that simply has those terms in its meta description.” Businesses with specific, keyword-rich testimonials get cited more often than businesses with generic five-star ratings and no text.

    A review-industry breakdown this month named vague reviews as one of the three mistakes sending customers to competitors: “great service” instead of “same-day AC repair in Phoenix.” And review audits keep finding the same thing — AI answers quote review text verbatim. Your customers’ words become the bot’s answer.

    The star-rating trap

    Most owners chase stars. Stars are visible, countable, and feel like the scoreboard. But a five-star rating with no text tells the AI almost nothing — it’s a number without a story. Forty detailed reviews at 4.8 stars will beat a hundred empty five-stars, because the detailed reviews give the bot something to match against the question and something to quote in the answer.

    This is also why review platforms matter less than review content here. The question isn’t just where your reviews live — it’s whether the words in them describe the work you actually want to be recommended for.

    The review-request script (free, repeatable)

    You can’t write your own reviews. But you can ask for better ones — and most owners never do. After a job, when the customer is happy, ask them to mention two things: what you did and where. That’s it.

    “If you have a minute to leave a review, it really helps when folks mention the job — like the water heater swap — and the town. Just a sentence is perfect.”

    That’s the whole script. You’re not scripting fake reviews or stuffing keywords — you’re asking real customers to include the specifics they’d naturally mention anyway. “Mike replaced our water heater the same day it died, here in Mesa” is a quotable piece of evidence. “Great service!!” is not.

    What to actually do about it

    • Read your last twenty reviews. Count how many mention a specific job or a specific town. If the answer is “almost none,” you have the generic-review problem.
    • Start the two-thing ask this week. What you did, and where. Every finished job, every happy customer. It compounds.
    • Don’t neglect the unhappy ones. A detailed critical review is still evidence the bot reads — respond to it well, and the response becomes part of the record too.
    • Keep it honest. Never write reviews yourself, never pay for them, never hand customers pre-written text. The specifics have to be real — fabricated detail is both against every platform’s rules and, increasingly, detectable.

    What’s actually known — and what’s not

    Known: AI answers quote review text verbatim, and businesses whose reviews describe specific jobs in specific places get cited more often than businesses with generic ratings. The review-request script — ask for the job and the town — is a free, ownable fix no competitor can block.

    Not known: nobody has published a controlled test measuring naming rate against review-text specificity for trades businesses — the evidence is observational and mechanism-level, not a measured curve. What’s missing is someone running the test: same market, similar star counts, specific-text versus generic-text reviews, measured naming rates. That’s a test worth running.

  • Do I Have to Get on Those ‘Best Plumber in [City]’ Lists for ChatGPT to Recommend Me?

    Do I Have to Get on Those ‘Best Plumber in [City]’ Lists for ChatGPT to Recommend Me?

    Short answer: You don’t have to pay the directories — but you do have to be mentioned. When someone asks ChatGPT “who should I call,” the pages it reads are mostly the ones that rank for that question, and those are usually “best of” listicles. Businesses that show up in the two or three listicles ranking on Bing for their trade and city get named. Businesses with no mentions anywhere get named in only 2.8% of relevant answers.

    The numbers behind the listicles

    This isn’t a hunch — it’s measured:

    • “Best of” list articles account for roughly 21% of all AI citations (arXiv 2606.20065).
    • Brands with no citations on their own site and no mentions elsewhere were named in only 2.8% of relevant ChatGPT answers — across a 34,960-prompt study (arXiv 2609.23162).
    • One agency’s check of ChatGPT answers found 95% pointed to a directory as the source.

    A Bend, Oregon owner’s check this month put it in plain terms: the pages ChatGPT reads are “mostly the ones that rank for the query and the ones that list or compare providers.” A Bend plumber sitting in the two or three “best plumbers in Bend” lists that rank on Bing is far more likely to be named than one whose only mention is their own homepage.

    Why this feels unfair (and partly is)

    Contractors resent listicles and directories as pay-to-play machines, and they’re not wrong to be suspicious. The directories sell placement, sell leads, and sell ads against the very searches you want to win. Being told “the bot reads the listicle” can sound like being told to feed the beast.

    But there’s a difference between paying the directories and being listed on them. Most “best of” pages have free listing paths. The bot doesn’t know or care whether you paid — it cares whether your name, trade, and town appear on a page that ranks for the question being asked.

    The misfire side: listicles can get you wrong

    A Plant City plumber’s owner-written FAQ documents the other edge of this: “A ‘serves Plant City’ line on a directory can mean a truck that drives over from another metro when the board has a gap.” His shop is headquartered in Plant City; the listicles hand the town to whoever bought the line. If you’re not watching your directory listings, the listicle isn’t just ignoring you — it may be actively mislocating you.

    What to actually do about it

    • Find your two or three. On Bing, search “best [your trade] in [your city]” the way a homeowner would. The listicles that rank are the ones the bot reads. That’s your list — not fifty directories, just the two or three that actually rank.
    • Get listed on the free path. Claim or create the free listing on each. Fill it out completely: services, service area, phone number, website.
    • Keep your facts identical everywhere. Same business name, same phone number, same towns on every listing and your own site. Conflicting facts are how you get skipped — or misdescribed.
    • Fix wrong information. If a listicle has your old phone number, the wrong town, or a competitor’s truck on your line, correct it. The bot quotes what’s there.
    • You don’t need the ads. Paid placement on a directory is a separate purchase from being listed. The citation evidence comes from the listing, not the ad spend.

    What’s actually known — and what’s not

    Known: listicles and directories are a major citation source for AI answers — roughly a fifth of citations, and near-total absence from them collapses your naming rate to single digits. The fix is getting accurately listed on the few that rank, not buying your way onto all of them.

    Not known: exactly which listicles any given engine prefers for any given trade and city — that shifts with rankings. Nobody has published a per-market map of “these three listicles decide the plumber answers in Phoenix.” The practical move is checking your own market’s rankings directly, because that’s what the bot is reading today.

  • I Don’t Do Bing — Am I Invisible to ChatGPT?

    I Don’t Do Bing — Am I Invisible to ChatGPT?

    Short answer: Mostly, yes. When ChatGPT goes looking for live information on the web, it searches through Bing’s index — not Google’s. If your business isn’t indexed by Bing and isn’t claimed on Bing Places, ChatGPT’s live-search layer has no way to find you. Everything you built on Google — your rankings, your reviews, your Google Business Profile — doesn’t transfer to that layer.

    Why your Google work doesn’t carry over

    This is the part that stings. You spent years — maybe money, too — getting your Google presence right. Then a homeowner asks ChatGPT who to call, and none of it counts. That’s because ChatGPT reaches the open web through Microsoft’s Bing search infrastructure, not Google’s. One agency put it bluntly in a widely syndicated piece this year: “It Runs on Bing, Not Google.” A contractor who invested everything into Google rankings and ignored Bing Places is, in their words, essentially invisible to ChatGPT’s search layer.

    An SEO vendor’s FAQ answers the owner version of this question directly: “Should I optimize for Bing if I already rank well on Google? Yes, ChatGPT uses Bing’s index when browsing the web. If you’re not indexed in Bing and listed in Bing Places, ChatGPT cannot find your business.”

    What it looks like in practice

    A Vienna-based test from October 2026 ran the scenario end to end: someone asked ChatGPT to recommend an installer in Vienna. ChatGPT searched live via Bing, returned three competitors — and marked the tester’s own firm “NICHT DABEI” (not there). The firm wasn’t failing at marketing. It was failing at being in the index the bot actually reads.

    A Bend, Oregon owner’s check the same month found the same shape: the competitor who gets named is the one who ranks on Bing for the question being asked. Your Google position never enters the picture.

    The “my SEO guy says we’re covered” myth

    If your SEO provider tells you your Google work covers you for AI search, ask them one question: when did you last check my Bing presence? Google-only SEO is a real thing — plenty of shops do excellent Google work and never touch Bing, because for a decade that was a defensible call. It isn’t anymore. The AI layer that now sits between the homeowner and the phone call reads a different index, and “we’re covered” without a Bing check is a guess.

    What to actually do about it

    The good news: this is a five-minute fix, not a six-month project.

    • Claim your Bing Places listing. It’s free, it’s separate from your Google Business Profile, and it’s a real listing that feeds ChatGPT’s search layer. Most contractors have never claimed theirs.
    • Check whether Bing has indexed your site. Search site:yourwebsite.com on Bing. If nothing comes up, Bing doesn’t know your site exists — and neither does ChatGPT’s browsing layer.
    • Set up Bing Webmaster Tools. Free, takes minutes, and shows you exactly what Bing sees (or doesn’t).
    • Keep your facts identical everywhere. Same business name, same phone number, same service area on your site, Bing Places, and Google Business Profile. Mismatched facts are how businesses get misdescribed or skipped.

    What’s actually known — and what’s not

    Known: ChatGPT’s live web browsing runs on Bing’s search infrastructure. Bing Places is a real business listing that feeds that layer — unlike the mythical “ChatGPT business registry,” which doesn’t exist. Contractors who are Google-only are structurally invisible to ChatGPT’s search layer until they fix their Bing presence.

    Not known: exactly how much weight Bing Places carries versus organic Bing rankings in any given answer, or how often the underlying data refreshes. Nobody has published a controlled test of “claimed Bing Places on this date, started appearing on that date” for trades businesses. The mechanism is well-evidenced; the precise timing isn’t.

  • The Mailbox Is a Trigger. It Is Not a Topic.

    The Mailbox Is a Trigger. It Is Not a Topic.

    Short answer: a mailbox can start a publish job. It cannot choose the topic. If the incoming message is a digest, a rumor chain, or a subject line that would embarrass the brand, the correct article is not a reprint. The correct article is the gate.

    Tygart Media sits in Tacoma, Washington. The public site is an operator desk for AI-native content systems, restoration operations, and the search surfaces that now sit between a shop and a buyer. Those surfaces include classic Google results (SEO), answer engines that quote a paragraph as evidence (AEO), and generative engines that assemble a local picture of who you are (GEO). None of them are helped by publishing whatever landed in will@tygartmedia.com at 7:44 p.m.

    What is a source-fit gate?

    A source-fit gate is the first checklist in an inbox-triggered pipeline. It asks one question before outline, slug, schema, or Rank Math title: does this source belong on this domain?

    The test is not “is the subject loud.” The test is whether a contractor in Everett, a facility manager in Tacoma, or an answer engine citing tygartmedia.com would be right to treat the page as evidence. If the source is a third-party digest of celebrity gossip, political rumor, medical anecdotes, and crime blurbs, the source fails. Publishing it as news would contaminate the entity the site has spent years teaching search systems to recognize.

    That is the same instinct behind the $5 filter: would anyone pay to pipe this feed into an assistant as a trusted source? A mailbox firehose would fail that filter on most nights. The gate exists so the firehose does not become the catalog.

    What Sunday night’s mailbox actually contained

    The trigger for this piece was a Quora Digest addressed to the work inbox. The subject line led with a political rumor. The body mixed entertainment questions, relationship advice, medical anecdotes, a crime blurb, and other off-desk topics. None of that is Tygart Media’s beat. None of it is restoration operations. None of it is a first-party number we can stand behind.

    So the digest is not the article. The digest is the proof that an automation without a source-fit step will try to hang the wrong page. The human-readable rule is the same one already on this site: draft-only is the first verb, and publish stays a seat a human can refuse. The machine may open the envelope. It may not inherit the subject line as the H1.

    The six checks before anyone writes

    Run these in order. Stop at the first fail. Do not “find an angle” to rescue a bad source.

    • Domain fit. Would this page still make sense if the logo, the About page, and the $97 restoration kit sat next to it? If not, fail.
    • First-party or primary source. Can you name a dated public document, a product note, a field observation, or a number you measured? A digest snippet is not a source. Fail.
    • Identity lock. No client names, no secrets, no mail IDs, no thread IDs, no app passwords. The Quality Gate exists because a client name once leaked into live posts. That failure mode is still live.
    • Number lock. No invented click-through rates, ranking jumps, or “X% more citations.” If a figure is not on the page you can point to, leave it out.
    • Duplicate lock. Search the live site before you mint a slug. If the argument already exists, update that page or stop.
    • Place lock (GEO). If the piece claims a geography, name a real one the operator actually works — Tacoma, Puget Sound, Everett, Snohomish County — and do not stuff NAP into a thought-leadership body.

    Only after those six pass do AEO, SEO, and GEO get to work. Optimization is not a pardon for a bad source.

    How AEO, SEO, and GEO attach after the gate

    AEO — write the answer first

    Answer engines quote short, stable sentences. Lead with the claim a model can lift without inventing the rest of the page. Then explain. Then put the same claim in an FAQ block using the questions people actually type: what is a source-fit gate, should every email become a post, who owns Publish.

    SEO — one slug, one job

    Pick a slug that names the method, not the digest subject. Title tag under 60 characters. Meta description that restates the answer. Canonical on the live URL. Rank Math on this stack writes the title and robots fields; it does not invent the argument. Internal links go to pages that already carry the doctrine — the $5 filter, the draft-only desk, the afternoon where five drafts still needed a human tap.

    GEO — teach the place, don’t spray it

    Generative engines build a local picture from repeated, consistent facts. Tygart Media is a Tacoma agency. Restoration work in this network is often packed around Everett and Snohomish County. Say that when place is part of the method. Do not turn a content-ops essay into a fake service-area page. GEO is entity clarity, not a city list glued to the footer of every paragraph.

    What to publish when the source fails

    Three honest exits, in order of preference:

    1. Write the gate. If the failure mode is the news — an inbox automation almost reprinted a digest — the operator article is the checklist. That is this page.
    2. Hang nothing. An empty-delta night is a successful night. Silence is cheaper than a correction.
    3. Keep a receipt. Log the fail in the Command Center so the next run does not “try the digest again.” The receipt is not the public URL.

    What you do not do is launder the digest into a “roundup,” a “what people are asking,” or a thin news recap with a restoration sentence taped on the end. That is how a site teaches answer engines the wrong entity.

    What this desk will not do with a digest

    • Reprint political rumor, crime blurbs, or medical anecdotes as Tygart Media reporting.
    • Quote tracking URLs, message IDs, or unsubscribe tokens from the envelope.
    • Invent a percentage that makes the pipeline look smarter than it is.
    • IndexNow a thin title-price door, or ping Bing before the body exists.
    • Hand Publish to the same process that opened Gmail.

    The machine can fetch the letter. The machine can draft. The machine can stage images and fill Rank Math fields. The tap is still human.

    FAQ

    What is a source-fit gate in content operations?

    It is the pre-outline check that asks whether an incoming source belongs on this domain. Domain fit, primary source, identity lock, number lock, duplicate lock, and place lock. Fail any one and you do not draft the obvious article from the subject line.

    Should every incoming email become a WordPress post?

    No. Mailbox events are triggers. Product notes, first-party incident numbers, and field observations can become posts. Digests and rumor chains should not.

    How do AEO, SEO, and GEO fit after the gate?

    AEO wants an answer-first opening and an FAQ a model can quote. SEO wants one slug, a clean title and meta, and internal links to the doctrine pages. GEO wants consistent place facts — Tacoma for the agency, Everett and Snohomish County when the method is local restoration — without turning every essay into a service-area page.

    Where does Tygart Media apply this?

    On tygartmedia.com first. The same gate belongs on any site in the network before an inbox automation is allowed to mint a URL. The Command Center keeps the receipt. The public page keeps the method.

    If you want the restoration operating system this desk actually sells, the front door is the Complete Restoration Operations Kit. The method on that page is copyable. The checkout is on the page. The mailbox is still not the editor.

  • 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.