CrushPress.AI

Tag: AI Transparency

  • AI Slop Detection: Prove Quality With Content Provenance

    AI Slop Detection: Prove Quality With Content Provenance

    You ran a page through an AI detector. It returned a high probability of machine-generated text. Now you have to decide whether to rewrite the page, remove it, disclose AI use, or ignore the score.

    Do not make that decision from the score alone. AI detection, slop detection, content quality, and provenance answer different questions. Treating them as interchangeable can make you discard useful work, preserve polished nonsense, or spend hours rewriting text without improving what readers receive.

    Stop asking one detector to answer four different questions

    The first step is to separate four concepts that are often collapsed into one label:

    • AI detection estimates whether a model may have generated or transformed text. It does not determine whether the text is accurate, useful, original, or fit to publish.
    • Watermark detection looks for a signal deliberately introduced during generation. A positive result indicates that a participating system likely touched the output. It does not reveal how much was generated, what was edited, or whether a qualified person approved it.
    • Slop detection is an attempt to identify low-value, repetitive, manipulative, or mass-produced material. Slop is an outcome, not an authorship category. Humans produced commodity content long before generative AI existed.
    • Content provenance is the evidence trail behind a published asset: where its claims came from, who created and changed it, what automation did, how it was checked, and who accepted responsibility for publication.

    These distinctions matter because the signals are imperfect. Text-watermark detectors generally need enough material to observe a pattern. Published benchmarks put the workable floor at roughly 100 tokens in favorable conditions, while SynthID evaluations truncate samples to 200 tokens. Short comments, titles, summaries, and rewritten excerpts may fall below that floor.

    Editing creates another limitation. Paraphrasing, translation, model chaining, and combining marked output with other text can weaken or remove a watermark. A paraphrasing attack presented at ICML 2025 achieved nearly 100% success against seven watermarking methods at a reported cost of $0.88 per million tokens. Open-weight models add a more fundamental gap: watermarking is applied by the sampling pipeline, so someone running a model independently can omit that step.

    This produces two dangerous errors. A false positive can send a strong page into unnecessary rewrites. A false negative can give weak or fabricated material an undeserved pass. Even a system reported at 94% accuracy can make consequential mistakes when it operates across enormous volumes, especially when you do not know the evaluation set, class balance, or error distribution.

    Use detection as a routing signal. A high score can send a page to closer editorial review, but it should never be the reason the page fails. Make the final decision with four questions: Is the page accurate? Does it contribute something distinct? Can its important claims be traced? Is a named person accountable for it?

    Distribution systems are reacting to low-value supply

    Generative tools have made production cheap. They have not made attention abundant. When thousands of interchangeable assets can be produced in the time previously required for one, distribution systems become stricter selectors.

    Platforms are responding at several points in that supply chain:

    The implementations differ, but the operational lesson is consistent: publishing more units does not guarantee more distribution. A system may label an asset, suppress it, remove its monetization, filter it from recommendations, or delete it as spam. The marginal cost of production may approach zero while the cost of selection keeps rising.

    None of this proves that search engines or frontier models apply a universal penalty to anything touched by AI. It shows that platforms increasingly act against repetition, manipulation, undisclosed synthetic media, and low-value supply. Do not turn that observation into an imaginary ranking factor. Turn it into a stricter publishing standard.

    A page deserves publication when it performs a specific job that another page on your site does not already perform. It should resolve the promised question, support material claims, make uncertainty visible, and give the reader a usable next step. If you cannot name its distinct contribution in one sentence, producing another variation will increase inventory without increasing value.

    Run a slop audit that measures usefulness, not writing style

    An editor reviews an unmarked digital page beside source documents, a balance scale, a toolbox, and a tray of duplicate sheets.

    Most detector-led cleanups begin at the wrong end. Teams scan thousands of URLs, sort by an AI probability, and rewrite whatever appears most synthetic. That process optimizes the detector’s reaction. It does not tell you whether the revised page deserves attention.

    Use the following audit instead.

    1. Write down the page’s job. Record the intended reader, the question or decision that brought them there, and the action they should be able to take afterward. If the job is unclear, the page cannot be evaluated coherently.
    2. Identify the distinct contribution. Look for an original observation, a precise definition, a decision rule, a useful constraint, a first-party example, a sourced fact, or a synthesis that removes work for the reader. A topic is not a contribution. Neither is a fresh arrangement of familiar sentences.
    3. Check every consequential claim. Mark statistics, dates, product behavior, legal obligations, quotations, named entities, and strong causal statements. Each one needs an appropriate basis. If the evidence cannot be recovered, soften the claim, replace it, or remove it.
    4. Inspect the page as part of a collection. Compare it with assets targeting adjacent intents. Repeated introductions, interchangeable sections, overlapping target queries, and multiple pages with no independent purpose are stronger slop indicators than a model’s preferred punctuation.
    5. Assign an accountable owner. A byline is not enough if no one checked the substance. Record who drafted, edited, verified, and approved the page. One person may fill several roles, but responsibility should still be explicit.
    6. Choose a disposition. Keep, improve, consolidate, or withdraw the page based on reader value and evidence. Do not add a fifth category called rewrite until the detector turns green.

    Your audit sheet only needs a small set of fields: URL, intended query or task, audience, distinct contribution, consequential claims, evidence status, overlap, owner, reviewer, last substantive update, and disposition. Add the detector result in a separate field if you use one. Keeping it separate prevents the score from masquerading as an editorial verdict.

    Apply the dispositions consistently:

    • Keep a page when it is accurate, distinct, appropriately supported, and still fulfills its intended job. An AI flag alone is not a reason to disturb it.
    • Improve a page when it has a useful core but withholds the information needed to act. Replace generic explanation with evidence, constraints, examples, decision criteria, or a clearer sequence.
    • Consolidate pages that repeat the same answer without serving meaningfully different intents. Preserve the strongest material, select one primary destination, and map the old URLs deliberately rather than creating another near-duplicate.
    • Withdraw material that is wrong, untraceable, misleading, or functionally empty. Preserve a recoverable copy before a bulk removal and assess redirects, inbound links, and downstream references so cleanup does not create avoidable breakage.

    The fastest diagnostic is subtraction. Remove the throat-clearing, generic benefits, predictable transition paragraphs, and unsourced superlatives. If nothing meaningful remains, the problem is not that the text sounds like AI. The problem is that the asset has no information payload.

    When something useful does remain, edit around that value. Put the direct answer near the top. Attach evidence to the claim it supports. State who the advice is for, where it stops applying, and what could change the decision. This improves the page for readers, search systems, and answer engines without trying to reverse-engineer a detector.

    Build provenance into publishing instead of adding it later

    A connected publishing workflow links research, review, version checkpoints, and a finished page with a continuous provenance chain.

    Provenance is strongest when it is captured during creation. Reconstructing it months later usually produces a folder of broken links, missing approvals, and vague memories about what the model did.

    Keep a private production record

    Create one record for each publishable asset. It can live in your content system, project tracker, or repository, but it should stay connected to a stable content ID or canonical URL.

    • Purpose: the audience, target task, search intent, and expected reader outcome.
    • People: the drafter, subject reviewer, editor, fact checker where applicable, and final approver.
    • Evidence: the sources used for consequential claims, access dates where they matter, first-party data inputs, and any unresolved uncertainty.
    • AI role: whether a model was used for ideation, outlining, drafting, transformation, extraction, classification, proofreading, or another defined task.
    • Verification: what a human checked, which claims were changed, and what could not be independently confirmed.
    • Version history: the published version, substantive updates, correction reasons, and approval status.

    Record the model’s role at a useful level of detail. AI-assisted proofreading and unsupervised generation of product specifications present different risks. A single yes-or-no field hides that difference. At the same time, do not retain raw prompts or uploaded material indiscriminately. They may contain confidential information, personal data, unpublished strategy, or licensed text. Apply the same access and retention controls you would use for other production records.

    A watermark can complement this record, but it cannot replace it. Anthropic announced machine-readable watermarks for Claude text and file output across its model access routes. Article 50 of the EU AI Act is a major reason model providers are moving toward machine-readable marking. That obligation concerns providers of generative systems; it does not make a marketer’s detector result a legal finding. If your organization provides or deploys a covered system in the EU, have qualified counsel assess the actual duty instead of relying on a content-scoring tool.

    Publish the evidence a reader can use

    Your private record establishes accountability. The public page should expose the parts that help a reader evaluate it:

    • A real byline connected to a useful author profile, not an unexplained house persona.
    • An accurate publication date and a modified date when the substance changes.
    • A concise change note when an update corrects, replaces, or materially qualifies earlier information.
    • Inline citations placed beside the claims they support.
    • A methodology note for first-party tests, calculations, surveys, or datasets.
    • An AI-use disclosure when the role of automation is material to interpretation, trust, rights, or platform policy.

    Disclosure and provenance are not synonyms. A sentence saying that AI was used is disclosure. The chain showing what it did, which evidence informed the result, who reviewed it, and what changed is provenance. You may need both, but one cannot stand in for the other.

    Structured data should mirror that visible evidence. On an Article or BlogPosting page, properties such as author, publisher, datePublished, and dateModified can make the stated identity and timing easier for machines to parse. They do not authenticate a weak byline, prove that a review happened, or turn an invented citation into evidence. Do not place claims in JSON-LD that the visible page does not support, and do not invent non-standard properties for internal provenance fields.

    This is where provenance supports AI search without becoming schema theater. A frontier model or answer engine still needs a reason to select the page. Give it compact, attributable claim-and-evidence pairs; stable names for people, organizations, products, and concepts; a direct answer before elaboration; and a visible record of substantive updates. Consolidate interchangeable pages so the strongest evidence is not scattered across thin variants.

    Provenance cannot guarantee rankings, citations, or inclusion in an AI-generated answer. It makes a more defensible asset available for selection. That is the useful goal: not proving that no machine ever touched the words, but showing why the result deserves to be trusted and distributed.

    Key takeaways

    • An AI score estimates origin patterns; it does not measure truth, usefulness, originality, or accountability.
    • Watermarks can indicate that a participating model touched enough text, but editing, paraphrasing, translation, short samples, and unmarked open-weight pipelines limit what they can prove.
    • Use detectors to prioritize human review, never as automatic publish-or-delete gates.
    • Audit each page for a defined reader job, a distinct contribution, traceable claims, collection-level overlap, and a named owner.
    • Capture sources, AI involvement, verification, approvals, and substantive changes while the asset is being produced.
    • Keep visible content and JSON-LD consistent. Structured data exposes claims to machines; it does not create provenance by itself.

    Start with five pages that matter to your business. Write down each page’s job, identify its unique contribution, trace its consequential claims, and assign an owner. You will learn more from that exercise than from rescoring your entire site, and you will have the beginnings of a provenance system that can survive the next detector, watermark, and distribution-policy change.

    References

    crushpress.ai community screenshot
  • AI-Generated Images in Google Search: A Publisher Playbook

    AI-Generated Images in Google Search: A Publisher Playbook

    If you publish recipes, tutorials, or any page that depends on original visuals, the immediate question is practical: can Google generate an image that answers the query before your work earns a visit?

    Do not cancel an image shoot or replace your library with synthetic assets based on one search experiment. Google stopped the recipe-image test that triggered this concern. The useful response is to make your visuals stronger as evidence, connect them cleanly to your content, and measure whether a generated answer actually changes user behavior.

    What Google tested, and what it did not establish

    Google tested AI-generated illustrations inside AI Overviews for recipe results. The generated visual compressed the cooking process from preparation to the finished dish. Google subsequently said the small experiment was no longer running.

    The company also distinguished that experiment from Nano Banana, an image-generation feature announced in July that activates when a user explicitly asks to create an image. That distinction matters. An automatically generated visual inserted into a search answer is a different product behavior from an image a user deliberately requests.

    The narrow reading is the reliable one:

    • Google is willing to test generated visuals within the search-results experience.
    • The recipe experiment described here has ended.
    • The test does not establish a general rollout for generated images in AI Overviews.
    • It does not establish how Google ranks AI-generated images published on your own site.
    • It provides no measured traffic-loss figure that you can apply to your pages.

    That last point should guide your budget decisions. A generated answer could reduce the need to click, but a stopped experiment cannot tell you how large that effect would be. Treat displacement as a hypothesis to measure, not a loss percentage to assume.

    Separate the three image questions people keep mixing together

    A three-part illustration shows an original cooking photograph, image thumbnails organized for search, and visual fragments forming a newly generated dish image.

    “AI-generated images in Google Search” can describe three different situations. Confusing them leads to bad SEO decisions.

    QuestionWhat the recipe test tells youYour decision
    Will Google generate a visual inside the result?Google tested this in recipe AI Overviews and then stopped the experiment.Monitor the search surface for your important queries instead of assuming a permanent rollout.
    Will Google show or cite an image from my page?The stopped test does not answer that broader visibility question.Keep original images accessible, useful, and clearly associated with the visible page content.
    Can I publish an AI-generated image on my site?The event establishes no general ranking treatment for publisher-created AI images.Judge the asset by accuracy, transparency, reader value, and your content standards rather than an assumed SEO advantage.

    The most immediate concern is the first situation: Google owns the generated visual, while publisher citations may appear nearby. A recipe publisher affected by the experiment warned that users could mistake nearby citations for credit for the illustrations. That concern is plausible, but it should not be inflated into a claim that every AI Overview misattributes images.

    When you inspect a result, ask two separate questions: “Where did the factual instructions come from?” and “Who created this visual?” If the interface makes only the first answer clear, a citation does not necessarily give you visual attribution.

    Make original images carry evidence a summary cannot preserve

    An overhead workspace shows a creator photographing measured ingredients, dough stages, and the interior of a finished loaf as a consistent visual sequence.

    Your strongest response is not to publish more decorative images. It is to make each original visual communicate something a simplified reconstruction could omit, blur, or invent.

    • Give every image a defined job. Show a decision, condition, comparison, or outcome that the surrounding prose cannot communicate as quickly.
    • Capture consequential stages. For a recipe, that might be texture, color, consistency, assembly, or the difference between an intermediate stage and the finished result. For a repair tutorial, it might be component orientation or correct tool placement.
    • Keep the visual and written sequences aligned. If the text changes order during editing, update the image order and captions at the same time. A polished image attached to the wrong step is worse than no image.
    • Write captions that interpret the evidence. Name the stage and tell the reader what to notice. “Mixture after folding, with visible streaks remaining” is more useful than “Step three.”
    • Use accurate alt text. Describe the relevant content and purpose of the image. Do not turn alt text into a list of target keywords.
    • Keep credits in visible page context. If the photographer, illustrator, tester, or organization matters, identify that contributor where readers can see it rather than relying only on the file name.
    • Align structured data with the page. If you use Recipe or ImageObject markup, reference an image that represents the visible content. JSON-LD is a consistency layer; it is not proof of authorship or a guarantee that an image will appear in search.

    This changes the role of image production. A generic hero image decorates a page. A well-captioned process image documents a claim. When Google or another answer engine compresses the page, the second asset gives the system and the reader a clearer reason to preserve the connection to your work.

    If the image itself was generated

    An AI-generated image can be an illustration without being evidence that you performed a process, tested a product, or produced the depicted result. Keep that boundary explicit.

    • Check every depicted step against the instructions a reader will follow.
    • Look for invented ingredients, tools, components, labels, textures, and transitions.
    • Do not present a generated process scene as documentary photography.
    • Label the image’s role when the difference between illustration and documentation could affect trust.
    • Have a human editor verify the final asset in the context of the page, not only as a standalone image.
    • Replace the asset when an error could lead the reader to perform the process incorrectly; a disclaimer does not repair a misleading instruction.

    For image-led instructional content, consistency matters more than visual polish. If the prose says one thing and the image shows another, the page has an accuracy problem regardless of whether a camera, design tool, or generative model produced the asset.

    Measure exposure before changing your production budget

    A sitewide traffic change cannot tell you whether a generated image displaced a click. You need query-level evidence that the search feature appeared and page-level evidence that behavior changed.

    1. Define the exposed content group. Start with pages whose value can be compressed into a visual sequence: recipes, assembly instructions, repairs, demonstrations, comparisons, and other image-led tutorials.
    2. Record the actual result. For each important query, save the query wording, generated visual, visible citations, search language, location context, device context, and date observed. Search interfaces change, so the screenshot is part of your evidence.
    3. Annotate the first observation. Add it to the same change log you use for site releases, content updates, and search-feature changes. Without that marker, later traffic comparisons become guesswork.
    4. Compare the affected pages and queries. Use Google Search Console to review impressions, clicks, and click-through rate. Use analytics to examine entrances and the business actions that follow those visits. If your reporting does not identify the generated feature directly, pair performance data with the search-result captures.
    5. Use a relevant comparison group. Compare image-led pages where you observed the feature with similar pages where you did not. Do not use unrelated sitewide traffic as the only baseline.
    6. Inspect attribution and accuracy separately. A citation can be present while the generated visual remains confusing. Record whether the source of the instructions and the creator of the visual are each clear.
    7. Change strategy only when the pattern repeats. A generated visual appearing alongside a decline isolated to the same queries is more informative than a single screenshot or a broad organic fluctuation.

    If impressions remain stable but clicks decline only where the generated visual appears, the displacement hypothesis becomes more credible. If no such visual appears, or the decline affects unrelated pages, look for another explanation before changing your image workflow.

    Also separate visibility from value. A page can receive fewer visits without losing the same proportion of conversions, subscriptions, or qualified inquiries. Conversely, a visible citation can look positive while contributing little meaningful traffic. Track both search presence and the outcome you actually need.

    When you find an inaccurate or confusing generated visual, capture the evidence before the interface changes. Preserve the query, complete visual, citations, and relevant landing pages. Use any feedback or reporting control available in the result, then check whether ambiguity on your own page contributed to the problem. Correct your page when it is unclear, but do not rewrite accurate instructions merely to match a generated mistake.

    Key takeaways

    • Google stopped the small recipe experiment that automatically generated process illustrations inside AI Overviews.
    • The experiment was separate from image generation triggered by an explicit user request.
    • A Google-generated search visual, a publisher image shown in search, and an AI image published on your site are three different SEO questions.
    • The stopped test does not establish a general ranking penalty or benefit for AI-generated images on publisher sites.
    • Original visuals become more defensible when they document meaningful stages, match the instructions, include precise captions, and align with structured data.
    • Do not infer traffic loss from the feature’s existence. Record the result and compare affected queries and pages before changing your production strategy.

    Start with your highest-value image-led template. Audit the relationship among its instructions, visuals, captions, credits, alt text, and structured data, then establish a performance annotation you can use if generated visuals reappear. The next experiment may take a different form, but clear evidence and clean measurement will leave you in a position to respond without guessing.

    References

    crushpress.ai community screenshot
  • Claude AI Text Watermarking: What Content Teams Should Do

    Claude AI Text Watermarking: What Content Teams Should Do

    If Claude touches your copy anywhere between the first draft and publication, you now need a better answer than simply saying that AI was or was not used. A machine-readable watermark may remain in the text, but that signal cannot tell a client, reviewer, regulator, or editor who supplied the ideas or how much human work followed.

    The practical response is not to avoid Claude or scramble to remove the mark. It is to record how Claude was used, keep disclosure decisions separate from detector results, and make sure your team does not treat a provenance clue as an authorship verdict.

    A Claude watermark is a provenance clue, not an authorship verdict

    When a supported Claude model generates text, it embeds an imperceptible, machine-readable watermark in the response. The signal is part of the text rather than a visible label attached to the interface. Anthropic says it does not alter the meaning, quality, or readability of the output.

    That distinction matters. A person reading the copy will not necessarily notice anything different. Detection requires a tool designed to recognize the embedded signal. Anthropic has said that detection tools and technical documentation will be released, so teams should verify which detector, model, and content version are involved before relying on a result.

    Most importantly, a detected watermark only indicates that the text may have been processed by Claude. It does not prove that Claude originated the ideas, wrote the first draft, or produced every sentence. Claude could have rewritten a human draft, shortened existing copy, adjusted its tone, or performed another transformation. The signal does not reconstruct that history.

    Detector resultDefensible conclusionConclusion to avoid
    A Claude watermark is detectedThe tested text may have been processed by a supported Claude model.Claude necessarily originated the text, ideas, or claims.
    No Claude watermark is detectedThe detector did not find a detectable mark in the version tested.The text was written entirely by a human or never involved AI.

    The second row is easy to overlook. An absent watermark does not rule out AI use. The text may come from an older or unsupported model, may have been heavily edited, or may have passed through a process that made the signal undetectable. A detector can contribute evidence, but it cannot close the case by itself.

    Coverage depends on the model, not the Claude interface

    Blank document sheets from different abstract processing cores pass through one shared glass portal, with a glowing particle trail visible in only one sheet.

    Anthropic is implementing watermarking at the model level. For supported models, the watermark is intended to appear whether the output comes through Claude, the Claude API, Claude Code, Claude Cowork, or Claude Tag. The change is tied to commitments under the European Union’s AI Act transparency code, but the rollout applies worldwide rather than only in Europe.

    Do not turn that into the broader claim that every piece of text associated with Claude must contain a detectable mark. The initial coverage concerns supported new models, and Anthropic also plans to extend watermarking to models released earlier during the transition period. Outputs can therefore differ by model even when the team informally describes all of them as Claude copy.

    If watermark status matters to a client policy, contract, or compliance process, capture the exact model identifier whenever the product exposes it. Also record the Claude surface used and the date of the interaction. A brand-level note such as AI assisted is useful context, but it is not detailed enough to explain why one output tests differently from another.

    Text and images use different provenance mechanisms

    Claude’s text watermark travels within the generated text and can remain when that text is copied and pasted. Supported PNG, JPG, and SVG files use a different mechanism: signed C2PA provenance metadata.

    Treat these as separate evidence paths. Copying text into a content management system is different from exporting, compressing, or reprocessing an image. File metadata can be stripped, so preserve the original exported asset when provenance matters. Do not assume that a derivative image will retain the same detectable record.

    Editing can change detectability without changing authorship

    The text watermark may survive some editing, but heavy revision can make it undetectable. That creates an important operational problem: the draft tested by an editor may produce a different result from the version that was first generated or eventually published.

    Always attach a detector result to the exact revision that was tested. Preserve that revision if the result could lead to a contractual dispute, disciplinary decision, or public claim. A screenshot of a detector score without the underlying text, model context, and test date is not a reliable audit record.

    Build provenance into your editorial workflow

    A content team organizes blank manuscript pages across an AI processing device, a human review station, and a locked archive connected by illuminated paths.

    Watermark detection should be a backstop, not your primary record of AI use. A small provenance log will answer questions that the watermark cannot: what Claude received, what it returned, what role it played, and what a human changed before publication.

    Before publication

    1. Inventory every Claude touchpoint. Include direct chats, API calls, coding workflows, and automated content pipelines. Claude may transform copy inside a system even when the final editor never opens the Claude interface.
    2. Record the role, not just the tool. Use specific labels such as outline generation, first draft, headline options, summarization, translation, tone editing, or final copyediting. The statement Claude was used is too broad to explain authorship.
    3. Capture the model and surface when available. Model-level implementation means this detail can explain why one output contains a watermark and another does not.
    4. Keep the human review trail. Identify who checked the facts, approved the claims, and accepted the final wording. A watermark does not establish whether anyone verified the content.
    5. Apply disclosure rules independently. Decide whether disclosure is required by your contract, internal policy, platform rules, or applicable law. Do not let the presence or absence of a detectable mark make that decision for you.
    6. Retain the relevant versions. Keep the input, raw Claude output, materially revised draft, and published copy when the stakes justify an audit trail. For supported images, retain the original file containing its provenance metadata.

    You do not need to retain every brainstorming exchange forever. Match the record to the risk. A disposable list of headline ideas needs less documentation than regulated copy, a signed client deliverable, or a page containing consequential claims. What matters is that your retention policy is deliberate and consistent.

    When a detector flags published copy

    1. Preserve the exact text and result. Do not begin rewriting before you know which revision produced the detection.
    2. Confirm what the tool actually detected. A generic AI-likelihood score is not automatically evidence of a Claude-specific watermark. Check the detector’s stated capability and supporting documentation.
    3. Compare the result with your provenance log. Identify the model, workflow, source draft, and human edits associated with that content.
    4. Describe the role precisely. If Claude edited human-written copy, say that. If it produced a draft that a person later verified and rewrote, say that instead. Avoid the unsupported extremes that Claude wrote everything or that the content was wholly human-made.
    5. Escalate before making a consequential accusation. If the result could trigger a contract dispute, employment action, regulatory issue, or public correction, involve the appropriate legal or compliance professional. A watermark result alone does not establish who authored the work or whether a rule was broken.

    This process also protects the person reviewing the content. It replaces an argument over an opaque detector result with a documented account of what the tool did and what people did afterward.

    Do not confuse watermarking with SEO, AEO, or schema

    Claude watermarking is a transparency and provenance feature. Nothing in its stated purpose establishes it as a Google ranking signal, an AI-search citation factor, a spam label, or an automatic content penalty. Do not launch a rewrite project simply because supported Claude output may carry the mark.

    The watermark also is not JSON-LD. It does not describe your organization, author, product, article, or cited entities to a crawler. Adding structured data will not erase it, and removing structured data will not address it. Maintain schema because it accurately represents the visible page and its entities, not because a watermark was found.

    For SEO, AEO, and GEO work, keep the content review focused on questions the watermark cannot answer:

    • Are the factual claims correct and supported?
    • Does the page answer the reader’s actual question directly?
    • Are authorship and editorial responsibility represented accurately?
    • Do citations lead to evidence that supports the adjacent claims?
    • Does the structured data match what users can see on the page?
    • Does the final copy satisfy the organization’s disclosure policy?

    A detected mark does not make weak content trustworthy, and an undetected mark does not make strong content deceptive. Content quality, provenance, and policy compliance are related review areas, but they are not interchangeable scores.

    Key takeaways

    • A detected Claude watermark means the tested text may have been processed by a supported Claude model. It does not prove who originated the ideas or wrote the first draft.
    • No detectable watermark does not prove human authorship. Older models, unsupported models, heavy editing, and stripped file metadata can leave no detectable signal.
    • Coverage is implemented at the model level across supported Claude products, including the Claude API and Claude Code.
    • Text uses an embedded machine-readable watermark, while supported PNG, JPG, and SVG files receive signed C2PA provenance metadata.
    • Record Claude’s exact role, the model when available, the human review, and the relevant revisions instead of relying on detection as your audit trail.
    • Do not treat the watermark as a ranking factor, a content-quality score, a substitute for disclosure policy, or a form of structured data.

    Start by adding one field to your editorial record: Claude’s role in the content. Once that field is consistently completed, add the model, surface, reviewer, and retained versions needed for your risk level. That record will remain useful even when editing changes the watermark or detection tools improve.

    References

    crushpress.ai community screenshot
  • AI Watermarking in SEO and GEO: What Publishers Should Do

    AI Watermarking in SEO and GEO: What Publishers Should Do

    If your publishing workflow includes Gemini, Claude, or ChatGPT, the practical question is whether a machine-readable marker could affect Google rankings or citations in AI-generated answers. You need an answer that protects visibility without forcing your team into an unnecessary ban on useful tools.

    The defensible response is to treat watermarking as a measurable risk variable, not as proof of an AI-content penalty. Early B2B evidence shows a meaningful performance gap, but it does not separate the watermark from differences in authorship, judgment, and content quality. Audit what your tools actually mark, strengthen the editorial process, and test your own publishing workflow before changing it at scale.

    The performance gap is a warning, not proof of a penalty

    A controlled August 2026 comparison tracked 1,682 pages across 139 websites in four B2B industries. The unwatermarked group reached an average Google position of 6, while AI-created, watermarked content averaged position 11. The corresponding AI citation rates were 12% and 7%.

    Visibility measureUnwatermarked contentWatermarked, AI-created contentWhat was counted
    Average Google position611Position for the target keyword within three days of publication
    AI citation rate12%7%Share of pages cited for at least one target query in Google AI Overview, ChatGPT, or Claude

    Those are commercially relevant gaps. Five positions can separate prominent first-page visibility from a much weaker result, while a five-percentage-point citation difference matters when only a small portion of eligible pages earns a citation at all. The direction was also consistent across B2B SaaS, manufacturing, financial services, and healthcare.

    But the comparison cannot establish that a watermark caused either gap. Four limitations should control how you use these numbers:

    • Production method and watermark status moved together. The 1,060 watermarked pages were created with AI tools; the 622 unwatermarked pages were produced without AI. There was no otherwise identical set of pages in which only the watermark changed.
    • Content quality was not controlled through a common objective measure beyond the publisher’s professional standards. Human-created pages may have received more original judgment, better reasoning, or more careful treatment even when the AI output was reviewed.
    • Google positions were measured within three days of publication. That makes the result useful for examining early visibility, but it does not establish a durable ranking effect after indexing settles and longer-term signals accumulate.
    • The sample covered four B2B industries. It does not establish the same effect for ecommerce product pages, local service pages, news, consumer publishing, or other formats.

    This is enough evidence to add provenance to your SEO and GEO monitoring. It is not enough to tell clients that Google has confirmed an AI-watermark penalty, to rewrite an entire content library, or to attribute every weak page to its generation tool.

    A watermark is not one universal signal

    Several scanning devices examine one translucent digital document and reveal different abstract particle, color, mesh, and block layers.

    Watermarking is an umbrella term for several machine-readable mechanisms. Treating them as interchangeable will produce a bad audit because the relevant signal depends on the platform and the type of output.

    A statistical text watermark, an image-pixel signal, and signed provenance metadata are not the same artifact. A generic AI-detector score is different again: it is an inference about how text looks, not proof that a cryptographic credential or an official platform watermark is present. Copying text into a CMS, uploading an image through a media library, or seeing a low detector score does not tell you which machine-readable signal survived publication.

    Build your inventory at the output level rather than assigning one AI-generated flag to a whole URL:

    1. Record the exact generator and modality: Gemini text, Claude text, ChatGPT image, or another defined output. Note which parts of the page were human-created, AI-assisted, or directly generated.
    2. Retain the original generated file or output with its provenance information. Once an asset has passed through several editors and export tools, reconstructing its origin becomes much harder.
    3. Fetch the public version of each image after the CMS and CDN have processed it. Inspect that served asset with a verifier that supports the relevant credential rather than assuming the uploaded and delivered files are identical.
    4. For text, record the generating platform and workflow. Do not substitute the verdict of a general-purpose AI detector for platform-specific watermark evidence.
    5. Keep a private provenance log connected to the URL, author or reviewer, publication date, material revisions, and disclosure decision. This gives SEO, editorial, legal, and compliance teams one consistent record.

    This audit tells you what you are actually testing. Without it, a performance report may combine text patterns, image credentials, different levels of human involvement, and ordinary editorial quality under one label.

    Strengthen the page instead of laundering its provenance

    Removing metadata to make synthetic material appear human-created is a poor SEO strategy. It attacks a suspected signal before the causal mechanism has been established, does nothing to improve weak reasoning, and may remove useful provenance. A text-level statistical pattern may also be unrelated to the metadata attached to an image, so changing one does not neutralize the other.

    Google, Anthropic, and OpenAI have described their adoption of watermarking as a response to disclosure requirements such as Article 50 of the EU Artificial Intelligence Act and to concerns about undisclosed synthetic media. If those obligations may apply to your organization, market, or content type, obtain qualified legal guidance before removing credentials or changing disclosures. The safe operational choice is to preserve provenance while legal applicability is being assessed.

    For pages expected to rank, convert, or earn AI citations, apply a review that improves the factors obscured by the watermark comparison:

    • Assign an accountable human editor who can verify every material claim, resolve contradictions, and approve publication. A name added after the fact is not a review process.
    • Answer the target question near the relevant heading before expanding into qualifications. AI answer systems need a passage they can extract, while readers need a direct answer before supporting detail.
    • Maintain a claim ledger for statistics, product behavior, dates, named standards, and legal assertions. Each consequential claim should map to a real reference that supports that exact statement.
    • Add original examples, experience, internal data, or expert judgment only when they genuinely exist and can be defended. Never fabricate first-hand evidence to make generated copy look distinctive.
    • Remove generic transitions, repeated conclusions, unsupported superlatives, and sections that merely rephrase the query. These are quality failures regardless of whether a machine can identify their origin.
    • Check that visible authorship, publisher information, publication dates, revision dates, and primary images agree with the page’s JSON-LD. Structured data should describe what a reader can verify, not create a false provenance story.

    Schema cannot wash away an embedded signal. Use properties such as author, publisher, datePublished, dateModified, and image only when the corresponding facts are visible and accurate. Do not create a fictional human author, mislabel generated material, or change a modification date without a material revision.

    These controls do not guarantee rankings or citations. They address the largest unresolved variable in the available evidence: watermarked pages and human-created pages may have differed in thoughtfulness and judgment as well as provenance. A disciplined edit gives you better content and a cleaner test.

    Test your publishing workflow without fooling yourself

    Two matching digital manuscript workflows run in parallel through review modules, with one lane passing through an additional glowing sensor.

    If AI-assisted publishing is material to your operation, run a prospective workflow test on representative, low-risk content. The goal is to find out whether your normal AI workflow is associated with different visibility on your site. Unless a platform provides an official watermark control, the test will not isolate the watermark as the sole cause.

    1. Choose comparable queries within the same site, topic area, search intent, page type, and publishing period. Comparing an established product page on a strong domain with a new informational page on a weaker domain will tell you very little.
    2. Assign the workflow before drafting. Use a fully human-created cohort and a cohort produced through your normal AI-assisted process. Do not move difficult topics into one group after seeing the briefs.
    3. Give both cohorts the same editorial requirements: comparable briefs, claim verification, subject-matter review, internal-link treatment, template, and publication approval. Keep the standard high enough that you would be comfortable publishing either group.
    4. Log generator, modality, human contribution, reviewer, asset credentials, publication time, indexing state, internal links, later backlinks, and material revisions. These annotations help explain a gap that is not actually caused by provenance.
    5. Measure each target keyword at the same early checkpoint used in the 2026 comparison – within three days – and continue at consistent later checkpoints. Record the actual position and indexing status rather than reducing every result to page one or page two.
    6. Measure GEO separately. Enter the same target queries into Google AI Overview, ChatGPT, and Claude, then record the date, locale, account state, cited URL, and whether your page was cited at least once. AI answers can vary, so keep the measurement setup consistent across cohorts and checkpoints.
    7. Define the decision rule before reviewing the outcome. Decide which metric matters, what operational change a repeatable gap would justify, and which confounders require a retest. This prevents one surprising URL from becoming company policy.

    Interpret the result in layers. If no repeatable gap appears, retain the workflow and continue monitoring instead of treating external averages as your own. If a gap disappears after stricter editing, quality is a more plausible explanation than watermark status. If it persists across matched content and checkpoints, route the most commercially important pages through a more human-led process, preserve the provenance record, and test again. Even then, describe what you found as a workflow association rather than a confirmed algorithmic penalty.

    Do not blend SEO and GEO into one success score. Ranking position shows where a page appears in conventional results. Citation rate shows whether an answer surface selected the page as supporting material. A workflow can perform differently on those outcomes, and each failure points to a different investigation.

    Key takeaways

    • Early B2B evidence found unwatermarked content averaging Google position 6 versus position 11 for watermarked, AI-created content.
    • The same comparison found AI citation rates of 12% for unwatermarked pages and 7% for watermarked pages.
    • Those differences show correlation, not causation, because watermark status, AI involvement, and possible quality differences were not independently controlled.
    • Text watermarks, image-pixel signals, C2PA credentials, and generic AI-detector scores are different things. Audit the exact platform, modality, and delivered asset.
    • Do not strip provenance as a speculative SEO fix. Preserve credentials, check disclosure obligations, and improve the page’s evidence, accountability, directness, and structured-data accuracy.
    • Use matched cohorts and separate SEO ranking from GEO citation measurements. Your test should evaluate your real workflow, not claim to prove a universal watermark penalty.

    Start with your next planned content cluster. Add a provenance field to the brief, require a named reviewer, verify the live assets, and record early rankings and AI citations separately. That gives you evidence you can act on without hiding how the content was made or letting one preliminary correlation dictate your entire strategy.

    References

    crushpress.ai community screenshot
  • Google Ad Automation Updates: What Teams Should Change Now

    Google Ad Automation Updates: What Teams Should Change Now

    You are losing some control over how paid listings may be explained to shoppers at the same time that Google is adding more machine-readable controls behind the scenes. The mistake is to treat both changes as one vague wave of “more AI.” They require different responses.

    For Shopping and Product ads, your immediate job is to make the product information you control difficult to misinterpret and to document any AI-generated wording you observe. For Display & Video 360, the job is more concrete: move bulk workflows to Structured Data Files v10.1 and test every dependent parser, template and validation rule.

    Key takeaways

    • AI-generated descriptions in Shopping and Product ads remain an experiment, not a confirmed universal feature. Do not redesign an entire account around an isolated appearance.
    • Because advertisers do not directly write the generated description, product-feed accuracy, landing-page consistency and evidence capture become more important.
    • Structured Data Files v10.1 is generally available in Display & Video 360. Versions earlier than v10 have been deprecated, so bulk-management workflows need a planned migration.
    • The new SDF field for AI transparency applies to whether a YouTube video asset was created or edited using AI. It is not a control for the AI-generated descriptions being tested in paid search placements.
    • Separate release management from experiment monitoring: migrate the confirmed file format now, while observing generated ad context without making unsupported causal claims about performance.

    Separate the shipped release from the ad-copy experiment

    A specialist examines a solid automated data pipeline beside a separate translucent experiment involving an unbranded product.

    Two Google advertising changes can contain AI and still have completely different operational status.

    Structured Data Files v10.1 is generally available to Display & Video 360 users. It changes a documented bulk-management format, adds fields and resource support, and deprecates older versions. If your systems import or export SDF files, this is release-management work with identifiable dependencies.

    AI-generated descriptions beside Shopping and Product ads are different. Their appearance indicates that Google may be extending a limited Search ads experiment into Shopping placements, but Google has not announced a broad rollout. The stated purpose of the earlier experiment was to test whether extra generated context helps people make more informed decisions.

    This distinction should determine your response. A generally available file version belongs in your implementation queue. A partially observed interface experiment belongs in your monitoring log. If you reverse those priorities, you may spend days reacting to generated copy that most customers never see while leaving production bulk jobs exposed to a deprecated format.

    Make AI-generated ad context easier to get right

    An unbranded shoe is surrounded by organized product attributes that flow through an automated system into consistent shopping ad layouts.

    Shopping advertisers traditionally shape the listing through product titles, descriptions, images and related product data. An AI-generated description inserts wording that the advertiser does not directly approve. You cannot govern that output like a conventional text asset, so govern the information surrounding it.

    Start with products where inaccurate compression would have the highest consequence: items with variants, compatibility requirements, conditional promotions, subscriptions, bundles or material exclusions. The practical question is not whether the feed contains enough keywords. It is whether a short generated explanation could preserve the product’s important distinctions.

    • Resolve contradictions across controlled assets. A title, product description and landing page should not describe the same variant in materially different ways. If a promotion has conditions, keep those conditions visible wherever the offer appears.
    • Put decisive facts near the product itself. Do not depend on a shopper inferring compatibility, quantity, included components or eligibility from an image alone. State the fact plainly in the appropriate product information and on the destination page.
    • Remove stale claims before polishing prose. An elegant description cannot compensate for an expired offer, obsolete specification or mismatched landing page. Accuracy comes before style.
    • Preserve product identity. Keep identifiers and variant distinctions consistent enough that your team can connect a generated description to the exact item that triggered it.
    • Define an escalation threshold. A harmless paraphrase and a material misrepresentation are not the same incident. Prioritise wording that changes price conditions, compatibility, quantity, availability or what the customer receives.

    Do not rewrite a whole catalogue after one screenshot. The feature is still experimental, and an isolated observation does not reveal how often it appears or how Google selected that presentation. Correct clear defects in your owned data, but keep speculative changes small and reversible.

    <!– wp:heading {
    crushpress.ai community screenshot
  • AI-Generated Creatives in Google Ads: A Practical Control Plan

    AI-Generated Creatives in Google Ads: A Practical Control Plan

    You turned on AI-generated assets to cover more searches without writing every headline and description by hand. The hard part is not getting Google to produce usable copy. It is giving the system enough freedom to improve relevance without letting it invent an offer, weaken an audience qualifier, or claim credit for conversions that merely moved from another campaign.

    Treat AI creative as controlled production, not unattended optimization. Start where automation has a clear job, encode the claims it must not make, review what it produces, and judge the result at account level. That operating model gives you useful scale without making brand safety and performance impossible to audit.

    Give AI creative a narrow job before expanding it

    Your best-managed campaigns are rarely the safest place to begin. Their assets may reflect years of query analysis, qualification language, pinning decisions and offer testing. Replacing that accumulated control with generated variants creates a high bar: the automation must outperform deliberate human work without disrupting traffic elsewhere.

    A better starting point is a long-tail campaign that performs acceptably in aggregate but receives less creative attention. In an evaluation spanning ecommerce, B2B lead generation and B2C lead generation, AI text customization was less effective than human asset management in highly optimized campaigns but useful in the less-attended long tail. That is directional evidence, not a universal promise, but it gives you a sensible placement rule: use automation first where the alternative is limited human coverage, not where your team already has a refined message.

    The scale of that evaluation matters. Its selected campaigns were nonbrand, spent at least $20,000 per month and contained at least 100 ad groups. Those were eligibility conditions, not minimum requirements for using AI Max. If your account is smaller, do not assume the same behavior or copy those thresholds as a prescription.

    1. Select a nonbrand campaign with a stable conversion setup. Brand traffic can hide weak creative because the searcher already knows what they want.
    2. Prefer a long-tail campaign with a real coverage gap. Define that gap explicitly, such as neglected ad groups or repetitive assets that do not reflect query themes.
    3. Avoid a first test in campaigns that depend heavily on pinning. Pinning often protects message order, legal language or audience qualification. If it is essential, do not remove it merely to make the test easier.
    4. Keep final URL expansion off during the initial creative test. If copy and destinations change together, you will not know which intervention caused the result.
    5. Write down the permitted scope. Name the campaign, ad groups, markets, offers and landing pages included. Anything not listed remains outside the test.
    6. Define the stopping conditions before launch. Pause or narrow the test if generated copy misstates the offer, attracts the wrong audience, shifts valuable traffic from established campaigns or reduces account-level business results.

    Do not enable every automation in the same experiment. A test that changes copy, query matching and landing-page selection at once may produce a result, but it will not produce a useful decision.

    Turn brand policy into enforceable messaging restrictions

    Abstract advertising asset cards pass through policy gates, while noncompliant cards are diverted into a separate review bin.

    AI Max text customization can tailor assets to the keywords in each ad group. That flexibility is also the risk: auto-created assets can promote products, services or promotions that the advertiser does not offer. A general instruction to follow the brand voice is too vague to prevent that failure.

    Messaging restrictions should translate your approval policy into explicit boundaries. The fastest way to find those boundaries is to make the model fail deliberately before Google writes on your behalf.

    1. Build an approved-claims inventory. List the products and services you sell, the audiences you serve, the promotions currently available, the geographic limits and any wording that must appear.
    2. Generate ordinary sample ads. Use Gemini to produce initial assets from the approved inventory. Mark anything that is factually wrong, commercially misleading or off-brand.
    3. Red-team the message. Prompt the model to become overly promotional, make stronger promises, broaden the audience and invent adjacent offers. The goal is to expose plausible copy that your team would reject.
    4. Convert each failure pattern into a restriction. Write a direct rule for the category, not just the rejected sentence. For example: do not imply guaranteed outcomes; do not mention discounts unless an approved promotion is supplied; do not advertise services outside the approved list.
    5. Run the hostile prompts again. Keep refining the restrictions until the generated set remains within your approved boundaries, including when the prompt pressures the model to overstate the offer.
    6. Assign an owner and version the restrictions. Record who approved them and which campaigns use them. When the offer or brand policy changes, update the restrictions before expanding automation.

    Audience qualification deserves its own rules. A B2B ad often needs to discourage consumers while attracting business buyers. If phrases such as “for businesses,” an industry requirement or another qualifier are essential and accurate, protect them. A higher conversion count is not an improvement if the generated copy removes the language that kept unsuitable leads out.

    Restrictions are preventive controls, not approvals. They reduce the range of unacceptable output, but every generated asset can still fail in a way you did not anticipate. That is why the next layer is asset-level review.

    Review every asset, then measure the whole account

    Inspect generated copy before it earns material delivery

    Generated assets can be easy to miss in the interface. When looking for them, change the default filters so the ad is included; that option is not selected by default. Review newly created assets repeatedly while the test is active and remove unacceptable variants before they collect substantial impressions.

    This is not a ceremonial check. In the monitored ecommerce and B2C activity, excluding the B2B result, reviewers removed approximately 19% of auto-created assets. That percentage should not be treated as an industry benchmark, but it demonstrates why an enabled feature cannot also be an assumed approval.

    • Offer accuracy: Does the company sell exactly what the asset promises?
    • Claim support: Could the team substantiate every benefit, comparison and outcome?
    • Promotion validity: Is the price, discount or time-sensitive offer real and currently available?
    • Audience fit: Does the wording retain the qualifiers that separate suitable buyers from unsuitable clicks?
    • Destination alignment: Can the landing page fulfil the expectation created by the ad without making the visitor search again?
    • Brand acceptability: Would the team approve this language if a person had written it?
    • Disclosure status: If the asset is an AI-generated or AI-modified image or video, has its provenance and required labelling been recorded?

    Separate campaign performance from incremental growth

    A successful-looking automated campaign can be a redistribution mechanism. In the ecommerce evaluation, AI Max initially appeared highly successful, but deeper analysis found that it was taking impressions, clicks and conversions from other campaigns while total account revenue declined. The local dashboard improved while the business result worsened.

    Review levelWhat to inspectWarning signResponse
    AssetGenerated headlines and descriptionsUnsupported claims, invalid offers or lost qualifiersRemove the asset and strengthen the matching restriction
    Search termQueries receiving impressions, clicks and conversionsValuable intent moves from a controlled campaign into the automated oneImprove query routing with keywords and negatives
    Campaign familyResults across the test campaign and campaigns serving similar demandThe test gains while established campaigns lose comparable volumeTreat the gain as possible cannibalization and narrow the scope
    AccountTotal revenue or qualified lead outcomesThe automated campaign improves while the account declinesDo not declare a win; correct routing and rerun the test

    When search-term overlap appears, use the observed data to restore control. In the ecommerce account, the response was to add relevant search terms as keywords, introduce more negative keywords and use audience lists to slow cannibalization before rerunning the test. Those controls are not a guaranteed recipe for every account. They illustrate the right sequence: diagnose where demand moved, change routing, and then test again rather than accepting campaign-level attribution at face value.

    For ecommerce, keep account revenue in view. For lead generation, inspect qualification and downstream outcomes, not just submitted forms. In both cases, ask the decisive counterfactual: did the AI creative create additional business, or did Google move existing demand into a campaign that could claim it?

    Make AI disclosure a workflow, not a last-minute badge

    Two marketers review blank creative cards at a light table as approved assets are linked to provenance markers and campaign containers.

    Creative governance now includes provenance. Google is gradually rolling out AI content labelling across Google Ads, Display & Video 360, Campaign Manager 360, Merchant Center and Google Ads Editor. Advertisers can add text or visual disclosures to eligible image and video creatives or use the platform’s AI label setting. Labelled assets display an AI disclosure icon where they appear.

    Google may also label certain assets created with its own AI tools automatically. Those platform-applied disclosures do not violate the existing creative policies that prohibit text overlays or watermarks. Neither point means that every AI-assisted asset will be identified for you, especially while availability is rolling out gradually.

    1. Record the asset’s origin. Mark each image and video as human-created, AI-generated or AI-modified.
    2. Record the production path. Keep the tool, responsible owner and approval status with the asset so the team can answer how it was made.
    3. Map where it will run. List the campaigns and markets using the asset; disclosure obligations can vary by jurisdiction.
    4. Apply the relevant label. Use the built-in setting or an eligible text or visual disclosure as appropriate, then verify the status in the available AI Label field and the rendered ad.
    5. Retain the approval record. If an asset is revised, update its provenance and reassess whether its disclosure status changed.

    The built-in control is not a legal safe harbor. It was designed to help advertisers address emerging transparency requirements in markets including the European Union, India and New York, but using Google’s AI label setting alone does not guarantee compliance. If your campaigns create regulatory exposure, obtain jurisdiction-specific legal guidance instead of treating a platform toggle as the final interpretation of the rules.

    Keep the four controls separate. A disclosure explains that AI was involved. A messaging restriction limits what the system may say. Human review decides whether a particular asset is acceptable. Account-level measurement decides whether the automation creates incremental value. None can substitute for the others.

    Key takeaways

    • Start AI-generated copy in a nonbrand, long-tail campaign where creative coverage is limited, not in the account’s most carefully optimized campaign.
    • Test creative separately from final URL expansion so you can attribute the result to the asset change.
    • Red-team your own offer, then convert every unacceptable claim, promotion and audience expansion into a messaging restriction.
    • Review auto-created assets explicitly and measure search-term movement, related campaigns and total account outcomes before calling the test successful.
    • Track the provenance of AI-generated and AI-modified images and videos; use Google’s labels where applicable, but verify legal requirements separately.

    Your next move is small: choose one bounded long-tail campaign, write its prohibited claims and audience rules, and record the account-level outcome that must improve. Do not expand AI creative until the generated assets pass review and the account shows genuine additional value rather than rearranged attribution.

    References

    crushpress.ai community screenshot
  • AI Ad Products Are Expanding Faster Than Disclosure Rules

    AI Ad Products Are Expanding Faster Than Disclosure Rules

    AI advertising is developing along two connected tracks: platforms are adding tools that make campaigns easier to create and manage, while also deciding how much people should be told about the technology behind an ad.

    Google’s creative-origin disclosures and OpenAI’s expanding ChatGPT Ads product show why transparency cannot be reduced to a single label. Users need to recognize paid placements, understand when AI shaped the creative, and know who remains responsible for the resulting claims.

    Key takeaways

    • Google is adding a “How this ad was made” section to My Ad Center for ads across Search, YouTube, and Discover, according to CrushPress.AI’s coverage.
    • Google will automatically disclose the use of its own generative AI ad tools, but advertisers using third-party AI tools will have control over disclosure, subject to local requirements.
    • ChatGPT Ads is adding audience, reporting, draft, and format capabilities, while its suggested ad drafts reportedly reuse website metadata rather than generating new copy or images with AI.
    • Effective transparency needs to distinguish the presence of an ad, the origin of its creative assets, and responsibility for its content.

    Advertising transparency now has two separate jobs

    A digital ad card is shown between symbols for paid placement and AI-assisted creation, with a human advertiser standing behind it.

    The first job is placement transparency: making it apparent that a recommendation, card, or other interface element is advertising. CrushPress.AI reported that OpenAI’s refreshed static ChatGPT ad card uses a clearer “Ad” badge, a more readable presentation, and larger visuals. That addresses the commercial status of the content rather than how it was produced.

    The second job is production transparency: explaining whether generative AI created or modified the ad creative. According to CrushPress.AI’s Google coverage, users will be able to open the three-dot menu or information icon on an ad and find a dedicated “How this ad was made” section inside My Ad Center. The disclosure is expected to cover ads on Search, YouTube, and Discover.

    These signals answer different questions. An ad badge tells a person why content is being shown commercially. A creative-origin disclosure explains something about how that content came into existence. A platform can provide one without fully providing the other, so treating either signal as complete transparency would leave an important gap.

    Google’s disclosure model mixes automation and advertiser choice

    Google’s reported approach creates two disclosure paths. When an advertiser uses Google’s own generative AI advertising tools, Google will automatically place the relevant information in My Ad Center. Because the platform can observe the use of its own creation tools directly, disclosure can be built into the workflow.

    The process is less uniform when creative comes from elsewhere. CrushPress.AI reported that advertisers using third-party AI tools will control whether to disclose that use. Depending on local requirements, an AI label may also appear on the ad itself, either automatically or after the advertiser uses the available control.

    This split reveals a central difficulty for AI ad governance: platforms have stronger evidence about activity within their own systems than about assets imported from outside. A dependable program therefore needs both technical detection or provenance signals and accurate declarations from advertisers.

    Google already embeds imperceptible signals, including SynthID, in material created with its generative AI tools, according to the same coverage. The source also noted that Google has required election advertisers to disclose synthetic or digitally altered content in political ads under a policy introduced in 2023. Those measures offer context for the new My Ad Center information, but they do not make all disclosure scenarios identical.

    Product automation does not always mean generative creation

    OpenAI’s reported suggested-ad workflow illustrates why precise language matters. When a campaign needs broader content coverage, ChatGPT Ads Manager may offer an “Add new ad” option that prefills an image, title, and description from existing website metadata. The advertiser can then review, edit, and assign the draft to a campaign and ad group.

    CrushPress.AI emphasized OpenAI’s statement that this feature does not generate new copy or imagery with AI. It is automated assembly, according to the description, rather than generative production. Labeling every automated advertising workflow as “AI-generated” would therefore obscure meaningful differences in how assets are sourced and transformed.

    That distinction becomes more important as the product develops. The reported ChatGPT Ads updates also include an overview tab for account health, recommended tasks and performance trends; audience-list uploads containing at least 25,000 users; audience inclusion or suppression; and ad-group bid multipliers. These are campaign-management capabilities, not evidence that the visible creative was generated by AI.

    The same report said ChatGPT Ads had expanded to Japan and South Korea. As an advertising system reaches more markets and adds targeting and optimization controls, transparency must cover the entire experience without collapsing targeting, workflow automation, generative creation, and sponsored placement into one ambiguous category.

    A practical transparency standard for advertisers

    A marketing professional reviews an advertisement through transparent layers representing sponsorship, AI involvement, and human approval.

    Advertisers can prepare for this environment by maintaining an internal record of where each asset originated, which tools materially changed it, who approved it, and which platform disclosures were selected. That record is a general operational safeguard rather than a platform-specific requirement, but it can support consistent decisions when rules differ by market, format, or creation tool.

    Teams should also separate three reviews. The first confirms that a placement is visibly identified as an ad. The second determines whether the creative requires an AI-origin disclosure. The third checks the underlying claims, identity, and offer for accuracy. Google’s existing prohibition on misleading or deceptive advertising still applies regardless of whether AI was involved, according to CrushPress.AI’s report; provenance information does not validate an ad’s message.

    Clear terminology will be as important as the controls themselves. “AI-assisted,” “AI-generated,” “AI-modified,” and “assembled from existing metadata” describe different processes. Platforms that make those distinctions understandable can give users useful context without implying that automation alone determines whether an advertisement is trustworthy.

    As AI advertising products mature, the strongest transparency systems will connect visible ad identification, reliable creative provenance, and continuing advertiser accountability. The next test is whether those elements remain coherent as more creation tools, formats, and markets enter the workflow.

    References

  • How to Evaluate AI Marketing Tools Before You Commit

    How to Evaluate AI Marketing Tools Before You Commit

    An AI marketing tool can look persuasive in a demonstration and still fail in day-to-day use. A sound evaluation therefore has to connect the product to a defined business problem, credible evidence, acceptable data practices and the team’s actual capacity to adopt it.

    The most useful approach is a staged decision process. Each stage should eliminate a different kind of risk before price or novelty turns an interesting product into an expensive commitment.

    Turn the business need into a testable decision

    Evaluation should begin with the marketing problem rather than the product’s feature list. The source article recommends asking vendors to explain the challenge their tool addresses and how solving it affects a business outcome. If that connection remains vague, a sophisticated set of AI capabilities does not establish that the product is useful.

    Before meeting a vendor, the buying team can create a short decision brief describing the current workflow, its most important constraint, the people affected and the result that should improve. That result might concern output, troubleshooting or another outcome already important to the organization. The purpose is not to manufacture a justification for buying software; it is to establish a baseline against which the tool can be judged.

    Claims about saving time require an additional question: what will the organization do with the recovered capacity? The source cautions that time savings are not automatically valuable. They become meaningful when the team can redirect that time toward work that advances an existing objective.

    This framing also exposes unnecessary purchases. If the problem can be resolved through a process change, better use of an existing platform or clearer ownership, adding another tool may increase complexity without addressing the underlying constraint.

    Match the evidence standard to the vendor’s maturity

    A glowing software module passes through a sequence of visual testing gates in a modern evaluation lab.

    A relevant case study is more informative than a broad success claim. According to the source, buyers should look for evidence involving organizations with a comparable size, market, vertical or use case, along with concrete results. The closer the operating conditions are to the buyer’s own environment, the easier it is to determine whether the evidence transfers.

    Evidence should also extend beyond customer logos. A credible vendor needs sufficient domain understanding to explain how marketers perform the work, where the recurring friction occurs and why the product was designed in its present form. The source notes that deep subject expertise does not have to reside with every salesperson, but a serious prospective customer should be able to reach someone who has it.

    Vendor maturity changes the appropriate test. An established provider can reasonably be expected to show repeatable results from relevant customers. An early-stage provider may not have that record, so transparency becomes part of the evidence: the vendor should identify where the product is unproven, explain what has been observed in other settings and define what the early partnership would require.

    Being an early adopter can offer an advantage, but the source also identifies added exposure to bugs, feedback demands and uncertain performance. Contract flexibility should reflect that imbalance. A newer vendor that expects the customer to absorb experimentation risk while offering no corresponding flexibility presents a weak partnership proposition.

    Treat data terms as part of the product

    Data governance is not a secondary legal review to perform after a product has been selected. It is part of the product evaluation because access to marketing, campaign or customer information can determine the consequences of a poor choice.

    The source recommends obtaining clear answers about who owns the customer’s data, where it is stored, how long it is retained, whether it is used for model training and what happens when the relationship ends. Any training of shared or third-party models should require explicit consent. If training is permitted only for a customer’s own instance, that limitation should be stated precisely.

    Verbal assurances are not enough. The source treats inconsistencies between a sales explanation and the terms of service as a warning sign and argues that material commitments belong in the contract. The practical evaluation standard is therefore documentary: can the vendor’s claims be located in binding terms, and do those terms cover the complete data lifecycle?

    This review also tests vendor quality. Clear, consistent answers suggest that the provider understands its own systems and customer obligations. Deflection or ambiguity leaves the buyer unable to assess exposure, regardless of how compelling the product appears.

    Calculate adoption cost, not just subscription cost

    A marketing team handles system setup, data preparation, training and workflow changes beside a simple subscription token.

    The commercial price is only one component of an AI tool’s cost. The source highlights implementation time, internal effort, integrations, training, quality assurance and possible disruption to the existing marketing technology stack. A product can be affordable on paper yet uneconomic if it consumes resources the organization cannot reliably provide.

    A useful implementation review follows the proposed tool through the real workflow. It identifies who will configure it, which systems must connect to it, who will review its outputs, how exceptions will be handled and what ongoing maintenance the vendor expects from the customer. This makes hidden dependencies visible before a contract creates pressure to proceed.

    Adoption is also a trust problem. As the source observes, a product that people cannot understand, trust or fit into their routines will not produce its promised value. The evaluation should therefore include the intended users, not only procurement leaders or executives. Their experience can reveal whether the tool removes friction or merely relocates it.

    A limited pilot can combine these questions into one decision. It should start with the predefined problem, use agreed evidence of success, operate under acceptable data terms and expose the actual workload imposed on the team. The decision at the end should account for both the result and the effort required to produce it.

    Key takeaways

    • Define the business problem and intended outcome before reviewing product features.
    • Demand evidence relevant to the organization’s size, market, vertical or use case.
    • Adjust expectations for vendor maturity, but require transparency and risk-sharing from early-stage providers.
    • Verify ownership, storage, retention, training and deletion terms in binding documents.
    • Evaluate implementation effort, workflow fit and user trust alongside the subscription price.

    As AI products continue to multiply, disciplined evaluation will matter more than rapid purchasing. Teams that document the problem, evidence threshold, governance requirements and adoption burden in advance will be better positioned to recognize tools that deserve a durable place in the marketing stack.

    References

  • How AI Advertising Changes Measurement and Experimentation

    How AI Advertising Changes Measurement and Experimentation

    AI-driven advertising is making campaign delivery more adaptive while making performance harder to interpret. When platforms choose audiences, placements and combinations of creative, a conversion report can show what happened without revealing whether automation created additional demand, captured demand that already existed or simply shifted credit between channels.

    The useful response is not another all-purpose attribution metric. Advertisers need a layered measurement system that combines behavioral signals, downstream outcomes, controlled experiments and creative-quality checks. The source reports collectively show platforms moving in that direction, although each covers a different part of the problem.

    AI shifts the question from attribution to evidence

    Traditional attribution asks which interaction receives credit for a result. AI-driven campaigns create a broader question: what evidence shows that the campaign changed customer behavior? That distinction matters because an automated system may optimize successfully against its assigned conversion signal while producing little incremental value for the wider business.

    The reported expansion of YouTube measurement illustrates the shift. CrushPress.AI’s article on YouTube measurement said Google added Shorts Ad Actions to the budget optimization and reporting available for eligible Video View Campaigns. It also reported the global availability of Attributed Branded Searches, a Google Ads metric intended to identify branded Google searches following exposure to or a view of a YouTube ad.

    Those signals occupy different positions in the customer journey. A Shorts interaction describes behavior around the ad itself, while a subsequent branded search suggests that exposure may have influenced active interest. Neither is equivalent to a sale, but together they can provide a more informative path from attention to intent.

    The article relayed Google’s claim that Shorts ads associated with more than 10 seconds of watch time and a like delivered 15% higher brand consideration and 20% higher brand favourability. It also relayed Google’s statement that each additional branded search generated was associated, on average, with a $31 sales increase. These are reported platform findings and associations, not universal forecasts or proof that every additional search causes the stated sales gain.

    Signals form a measurement ladder, not a single score

    Four connected translucent platforms rise from behavioral signals to outcomes, a controlled test apparatus, and a verified decision beacon.

    AI advertising environments increasingly expose early indicators that are useful before a direct conversion occurs. The appropriate interpretation depends on how close each signal sits to the desired business outcome.

    Interaction signals diagnose relevance

    Ad dismissal is one example. CrushPress.AI’s report on ChatGPT advertising said OpenAI reported a 50% decline in dismissals after launching its advertising business and presented that change as evidence of improving relevance. A lower dismissal rate may indicate that ads feel less intrusive or more useful in a conversational setting, but it does not by itself establish incremental sales, profit or retention.

    This makes dismissal a diagnostic metric rather than a final business verdict. It can help determine whether an ad fits the user’s task and context. The same principle applies to watch time, likes and other engagement actions: they can reveal whether the experience is resonating, while stronger evidence is still required to justify budget.

    Intent and cross-channel outcomes strengthen the case

    Branded search can bridge the gap between engagement and conversion because people do not always respond through the channel that introduced them to a brand. The paid-social measurement article described a common pattern in which social advertising creates awareness and paid search later captures the visit or conversion. It recommended examining branded search activity, search click-through rate, conversion rate, lead quality, cost per acquisition and revenue-related outcomes before, during and after meaningful social changes.

    These comparisons are directional because public relations, email, influencers, product launches, seasonality and organic activity can also affect search behavior. Their value is in identifying a plausible relationship that deserves stronger testing. When branded search, search engagement and conversion efficiency move together after a campaign change, the combined pattern is more informative than any one metric viewed alone.

    Experiments are becoming the control plane for automation

    Two matched campaign environments run in parallel with one controlled variation, and their results feed back into an automation engine.

    Controlled experiments address the central weakness of observational reporting: the absence of a credible counterfactual. Instead of asking only how an AI campaign performed, an experiment asks what would likely have happened without the campaign or without the proposed change.

    Microsoft’s reported Performance Max experiment expansion separates two useful decisions. Uplift experiments compare Performance Max activity with a control group to assess incremental impact. Upgrade experiments compare an existing campaign with an upgraded Performance Max version before a broader rollout. The first tests whether the automated campaign adds value; the second tests whether changing the operating model improves results.

    Google’s Ads API v24.2 adds another level of experimental granularity. According to the source article, its COMPARE_CAMPAIGNS workflow can compare multiple campaigns or campaign types across as many as five experiment arms, including custom Performance Max experiments. A separate experiment can divide traffic within one Performance Max campaign to test text customization and final URL expansion.

    Together, these options point to three distinct testing jobs. Incrementality tests evaluate whether advertising creates additional outcomes. Upgrade tests evaluate whether a new automated campaign structure outperforms the current approach. Component tests isolate a feature or configuration inside the system. Treating these as separate questions prevents a successful feature test from being mistaken for proof that the entire campaign is incremental.

    Where platform-native experiments are unavailable, the cross-channel measurement article proposed geotargeted holdouts: paid social runs in selected test markets and is withheld from comparable control markets, with search and business outcomes compared across the groups. It also noted that this approach generally requires suitable markets, sufficient budget and enough time, while smaller advertisers may need to begin with carefully controlled pre- and post-campaign analysis.

    Creative and delivery must be measured as one system

    Automation changes what creative does. In broad-targeting systems such as Performance Max, Advantage+ and TikTok’s automated expansion, the creative does more than persuade a predefined audience. Its language, visuals, opening hook and call to action help people self-select and generate behavioral signals that influence future delivery.

    The source on creative qualification argued that specificity is therefore a performance control. A message that clearly states the relevant need, prerequisite or use case can discourage unqualified engagement while attracting people for whom the offer is appropriate. That can improve lead quality and reduce the noisy conversion data fed back into an automated system. A generic message may achieve inexpensive engagement while teaching the system to find more of the wrong response.

    Measurement should consequently connect asset-level engagement with qualified outcomes. High watch time or click-through rate is encouraging only when the same creative also contributes to appropriate leads, sales or other defined business results. Creative tests should preserve the qualifying elements that identify the intended customer, rather than optimizing hooks in isolation.

    Placement visibility is part of the same diagnosis. The Google Ads API v24.2 article reported that Performance Max placement views can be segmented by ad_network_type, providing more visibility into where performance occurs across Search, Display and partner networks. That does not remove every limitation of automated delivery, but it can help teams determine whether an apparent creative result is actually concentrated in a particular network or context.

    Build decisions around an evidence hierarchy

    A practical operating model begins by assigning each metric a job. Interaction metrics diagnose relevance, branded search and cross-channel efficiency indicate possible demand creation, and holdouts or platform experiments provide the strongest available evidence of incrementality. Business outcomes remain the decision target against which the other layers are judged.

    Key takeaways

    • Define the business outcome before choosing the platform optimization signal; the two should be connected but should not be treated as interchangeable.
    • Use dismissals, watch time, likes and clicks to diagnose relevance, not as stand-alone proof of commercial value.
    • Monitor branded search and paid-search efficiency to detect demand that an upper-funnel or social campaign may have created elsewhere.
    • Match the experiment to the decision: uplift for incrementality, upgrade tests for campaign migration and component tests for individual automation features.
    • Evaluate creative as both a persuasion mechanism and an audience qualifier, with lead quality or customer value checked alongside engagement.
    • Document delivery context, placement mix and AI-generated asset status so that experiment results remain interpretable and governable.

    The final point extends beyond performance reporting. The Google Ads API article also reported new fields for synthetic-content information and attestation. Such disclosures do not measure effectiveness, but they become important experiment metadata: teams need to know which assets were AI-generated, which controls were active and what changed between variants if they want results that can be audited and repeated.

    As automated platforms assume more control over delivery, measurement will need to become more deliberate rather than more passive. The teams best positioned for the next generation of ad products will be those that can connect useful early signals to cross-channel behavior, then challenge the apparent result with a credible control.

    References

  • AI Brand Accuracy Is Becoming a Trust and Governance Test

    AI Brand Accuracy Is Becoming a Trust and Governance Test

    AI can misrepresent a brand without inventing an obvious falsehood. A technically correct description can still become misleading when an answer adds an unsolicited comparison, repeats an outdated assumption, or presents an opinion as settled fact.

    That makes AI brand accuracy more than a visibility problem. The sources point to an interconnected challenge involving representation, consumer trust, source provenance, editorial controls, and responsibility for harmful outputs. Brands need a system that addresses all five.

    Accuracy includes framing, not just factual correctness

    The same unbranded object appears through three transparent frames that emphasize different contexts and perspectives.

    Traditional fact-checking asks whether an individual claim is true. AI search requires a wider test: whether the complete answer represents the brand fairly and in the context of the user’s question.

    A Profound article reported an analysis of 50,000 prompts across seven industries and said nearly half of the AI responses contained comparisons, opinions, or recommendations that users had not requested. The significance is not merely that models sometimes make errors. It is that they can change the meaning of an answer by deciding which competitors, attributes, or judgments belong beside a brand.

    This creates at least three forms of accuracy risk. A claim may be factually wrong, such as an incorrect product capability. It may be stale, reflecting information that was once accurate but is no longer current. Or it may be contextually distorted: individual statements remain defensible, but the selection and framing leave users with the wrong overall impression.

    Profound’s FactCheck announcement approaches the issue as a measurement problem. It describes a way to evaluate brand claims at scale, identify inaccurate statements, and examine the sources associated with those errors. As a product announcement, it does not independently establish how well the tool performs. It does, however, highlight an important operational principle: a useful accuracy program must connect problematic outputs to the evidence influencing them. Counting brand mentions alone cannot reveal whether those mentions help or harm understanding.

    Rising use does not mean brands inherit rising trust

    The consumer research reported by Search Engine Land shows why representation quality matters even as AI search expands. In a Fractl and Search Engine Land survey of 1,008 U.S. consumers and 150 marketers, 70% of consumers said they were using AI tools for search more than a year earlier. Yet the share describing AI-powered search as more helpful than traditional search reportedly fell from 82% to 54% between the 2025 and 2026 studies.

    Those findings describe a convenience-trust gap. People may continue using a fast, accessible channel while becoming more cautious about its answers. A brand appearing prominently in that environment therefore gains exposure, but not an automatic endorsement. Accuracy, credible sourcing, and consistency across platforms become the conditions that determine whether visibility turns into confidence.

    The same survey found that the average consumer consulted 2.4 platforms before a purchase decision. Google was reportedly the first destination for 39% of respondents, compared with 15% for Reddit and 14% for AI tools. This suggests that buyers can encounter an AI-generated brand narrative and then test it against search results, community discussion, reviews, or other sources. Contradictions that once remained isolated are easier to expose when the journey crosses several platforms.

    Trust concerns also extend to brands’ own use of AI. The reported share of consumers who said heavy AI use would reduce trust in a brand rose from 20% to 39%. More than 80% wanted AI-generated material labeled across each content format measured, including 84% for written content and 91% for video. These figures do not show that audiences reject all AI-assisted work. They indicate that undisclosed volume and weak quality controls can become reputation signals in their own right.

    Accountability is moving closer to the publisher of the answer

    A separate Search Engine Land article reported that a German court held Google responsible for content in an AI Overview and rejected the proposition that a general warning placed the fact-checking burden entirely on users. According to that account, the court treated newly generated claims as Google’s content rather than merely a repetition of third-party material.

    One reported ruling should not be treated as a universal legal standard, and the supplied source does not establish how other courts or jurisdictions will decide comparable cases. Its practical lesson is nevertheless relevant to any organization deploying AI: a disclaimer is not a substitute for controls proportionate to the possible harm.

    The responsibility question changes depending on where an output appears. An inaccurate public article can damage readers or another company’s reputation. A faulty support response can misdirect a customer. An invented statement in an internal report can alter a decision even if it is never published. In every case, the organization receives the productivity benefit, selects the workflow, and decides whether a person reviews the result.

    The consumer study suggests many organizations have started adding safeguards, but their coverage is uneven. It reported that roughly three in four organizations conduct human editorial review before publishing AI-generated content. Among the specific checks, 62% reviewed brand voice, 54% checked facts, 42% performed legal or compliance review, and 27% evaluated bias. Brand consistency was therefore checked more often than factual accuracy, while bias received substantially less attention. That ordering can produce polished material that still contains consequential problems.

    A practical control system connects monitoring, evidence, and ownership

    An isometric control room connects AI answer monitoring, source evidence review, escalation, approval, and follow-up in a closed workflow.

    AI brand governance should cover both sides of the information boundary: what external systems say about the brand and what the organization publishes with AI assistance. These are related but distinct responsibilities. A company cannot directly edit every model answer, but it can improve authoritative source material, document errors, seek corrections where mechanisms exist, and prepare teams to respond consistently. It has much greater control over its own content, support messages, reports, and automated decisions.

    External monitoring should test realistic questions across discovery, comparison, evaluation, and purchase contexts. Reviews should record the answer, platform, date, cited sources, exact claim at issue, and the type of failure. Separating false claims from stale information, unsupported recommendations, and misleading framing makes remediation more precise.

    Source analysis should follow monitoring. When several answers repeat the same mistake, the next question is whether they rely on an outdated owned page, an ambiguous product description, a third-party article, or an unexplained model inference. Profound’s FactCheck announcement emphasizes this link between claims and contributing sources. Even without a specialized product, maintaining an evidence record helps distinguish a content correction from an escalation to a platform or publisher.

    Internal controls should be based on consequence rather than content volume. Low-risk drafting may need a lighter review, while legal claims, product limitations, health or safety guidance, competitive statements, and customer-specific advice warrant stronger verification and named approval. The responsible reviewer should be identified before deployment, not after an error appears.

    Finally, teams need a correction loop. Confirmed errors should update the relevant source material, prompt or workflow, review checklist, and monitoring set. Repeated failures should be treated as system defects rather than isolated copy edits. Useful reporting can track claim accuracy, contextual accuracy, source quality, correction status, recurrence, and the time required to resolve a material issue.

    Key takeaways

    • AI brand accuracy includes factual truth, freshness, context, comparisons, and the overall impression created by an answer.
    • Greater AI search adoption does not guarantee greater trust; the reported consumer research showed use rising while perceived helpfulness weakened.
    • Brand monitoring is more actionable when each questionable claim is linked to its apparent evidence and classified by failure type.
    • Disclosure can address audience expectations, but it cannot replace factual, legal, compliance, and bias review.
    • Accountability should be assigned to a named owner and scaled to the consequences of an incorrect output.

    As AI answers become part of ordinary brand discovery, the durable advantage will not come from producing the most material or collecting the most mentions. It will come from building an evidence-backed brand record, detecting distortions early, and showing that someone is accountable when automation gets the story wrong.

    References