I’ve noticed that Google is currently investigating an issue with the Google Search Console. Specifically, this concerns the data logging and reporting of “Job listing” and “Job details” search appearance filters.
On April 16th, a bug began affecting how this data is logged, causing Google to report zero clicks and impressions for job-related reports. Although traffic is still being received, it’s not being recorded correctly.
What Google said. According to an update from Google, “A logging error is preventing Search Console from reporting impressions and clicks for ‘Job listing’ and ‘Job details’ Search appearance types from April 16, 2026 onward. We’re working to resolve this issue. This issue affects data logging only.”
Complaints. I’ve also seen numerous SEOs voicing their concerns on social media, as shared in a tweet by Max Peters. The bug seems to impact impressions and clicks, but the traffic still comes through other measurement methods like google_jobs_apply UTM.
Why we care. If you’ve noticed a decrease in search data for job listings, rest assured, it’s due to this bug on Google’s side. Your listings are likely still active and receiving traffic, although this isn’t reflected in Search Console at the moment.
If your search impressions still look healthy while organic clicks and conversions have flattened, publishing more content may deepen the problem. AI answers have changed which searches produce a visit, but they have not removed the need for useful pages, credible evidence, or clear decisions.
You need to find the exact layer where growth is breaking: discovery, answer visibility, click capture, on-page usefulness, or conversion. Once you separate those layers, you can stop treating every plateau as a rankings problem and make the change that the evidence supports.
Reset what search growth means
The familiar organic growth model is simple: rank for more queries, earn more clicks, and turn those visits into outcomes. AI-generated answers insert another possible stopping point. A search engine may resolve a narrow question on the results page, while a person with a more involved problem still needs to visit a website.
The practical change is to stop using total organic sessions as the only definition of growth. Evaluate four different outcomes:
Discovery: your pages appear for the questions and problems that matter to your audience.
Answer visibility: your brand, explanation, product, data, or page is represented when an AI answer is shown.
Qualified visits: people click because they need depth, proof, a tool, a comparison, or a next step that the results page cannot provide.
Business outcomes: those visits lead to the action the page was built to support, such as a signup, inquiry, purchase, or informed move to another page.
This does not make clicks unimportant. A page does not become valuable merely because an AI system might summarize it. It means a click-through rate decline has more than one possible cause, and you should identify that cause before rewriting titles or adding pages.
Start by labeling your important queries by the job they perform. A closed-answer query asks for a fact or definition. An exploration query helps someone understand a problem. A decision query compares options or constraints. An action query looks for a product, service, process, or implementation path. Closed answers are more exposed to instant resolution. Exploration, decision, and action queries give you more room to earn a meaningful visit, provided the page does more than restate a generic answer.
Your keyword map should preserve that context. A broad term such as “schema markup” identifies a subject. A question such as “which schema should a service-area business use when it has no public storefront?” identifies a decision, a constraint, and the evidence the answer must contain. The second query is easier to turn into a useful content brief because it reveals what could make an answer wrong.
Build each topic cluster from real language found in search performance data, site search, customer questions, sales conversations, support requests, and community discussions available to your team. For every meaningful query or prompt, record:
The exact question, including qualifiers rather than a cleaned-up head term.
The user’s likely stage: learning, evaluating, validating, or acting.
The constraint that changes the answer, such as business type, location, platform, audience, or implementation state.
The decision the person needs to make after receiving the answer.
The evidence or experience required to make the answer credible.
The page and section that should satisfy the need.
The next useful action you want the visitor to take.
Do not turn every wording variation into a separate page. If several prompts have the same intent, require the same evidence, and lead to the same decision, they usually belong on one well-structured page. Split them only when the constraint materially changes the answer or when each audience needs a distinct path.
Then inspect the live result for your priority prompts in a consistent setup. Record the exact query, search surface, date, location context, whether an AI answer appeared, which domains were cited, which brands were mentioned, and what conventional results remained visible. AI Overviews are not activated for every query, so testing a few broad keywords cannot tell you how an entire topic behaves.
Treat this prompt set as a stable observation panel. Reuse the same important prompts when you review visibility, and add new ones only when customer language or search data reveals a genuinely different need. That gives you a comparable record instead of a collection of one-off screenshots.
Make the page valuable after the instant answer
The right response to AI answers is not to hide the answer deeper in the page. Give the reader a direct answer, then provide the judgment, evidence, and implementation help that a short synthesis cannot carry.
A useful page can be built in layers:
Answer the core question in plain language near the beginning.
Name the conditions that would change the answer. This prevents an accurate general rule from becoming bad advice in a specific case.
Explain the decision logic so the reader can apply the answer rather than merely repeat it.
Provide evidence or utility that is difficult to replace with a generic synthesis: an original example, a documented process, a worked configuration, a template, a calculator, a comparison framework, or first-party data you genuinely possess.
Offer the next action that fits the reader’s stage instead of forcing every visitor toward the same conversion.
Use a replacement test during editing: if a generic answer box can reproduce the entire value of the page, the page is not finished. Add the constraint, evidence, or usable asset that a person needs after learning the basic answer. Do not add length for its own sake. More words do not create more value when they repeat the same conclusion.
Machine readability matters, but it cannot rescue an undifferentiated page. Use descriptive headings, stable terminology, explicit relationships between entities, and internal links whose anchor text explains the destination. If you add JSON-LD, choose a valid type that accurately represents the page, keep names and other entity details consistent with visible content, and update the markup when the page changes. Structured data is a machine-readable description, not a relevance generator or a guarantee of inclusion in an AI answer.
Credibility also has to be inspectable. Identify who created or reviewed the material when that identity helps the reader judge expertise. Link claims to the evidence you actually used. Distinguish observed results from editorial recommendations. Display a date when freshness affects the answer, not as decoration. Remove unsupported ratings, fabricated experience, and schema properties that are absent from the visible page.
Mass-producing near-duplicate pages is especially weak in this environment. Google’s stated position is that generative AI has increased the volume of low-quality material while its ranking systems continue trying to suppress it. Whether those systems succeed in every result is a separate question. Your controllable advantage is to publish material that has a clear reason to exist: a different decision, better evidence, a useful tool, or a perspective grounded in real expertise.
Diagnose the stalled layer before choosing a fix
When organic search growth stalls, asking what to publish next is premature. First determine which part of the system stopped moving. Rankings, result-page behavior, content usefulness, conversion, and measurement can produce similar top-line charts while requiring completely different fixes.
Validate the measurement. Confirm that analytics events, search reporting, consent behavior, and conversion definitions have not changed. A tracking break should not become an SEO project.
Check technical access. Review indexing, robots directives, canonicals, redirects, rendering, internal links, and template changes on the affected pages.
Segment the change. Break performance down by query group, page type, intent, device context, market, and brand versus non-brand demand where those dimensions are available. A sitewide total can hide a concentrated loss.
Separate impressions from clicks. Falling impressions point you toward demand, coverage, indexing, or competitive visibility. Stable impressions with falling clicks point you toward the result-page environment, snippet appeal, or changed intent.
Separate visits from outcomes. If qualified traffic is steady but conversions fall, inspect message alignment, page usability, the offer, and event tracking before changing the query strategy.
Inspect representative results. Look for AI Overviews and other result features, note which needs they satisfy, and compare the remaining clickable results. Do this for the query groups that matter rather than whichever examples are easiest to find.
Use the observed pattern to choose the first test:
Observed signal
Start by testing
First useful action
Impressions decline across established query groups
Demand, indexing, coverage, or competitive visibility
Verify technical access, then compare the affected queries and pages instead of rewriting every snippet.
Impressions hold while clicks decline
Result-page changes, instant answers, intent, or snippet appeal
Inspect the live results, classify the lost queries, and strengthen both the search snippet and the page’s beyond-the-answer value.
Visits hold while outcomes decline
Tracking, landing-page alignment, usability, or offer fit
Validate events and compare each landing page with the promise and intent of its incoming queries.
Important customer questions have no relevant visibility
Content coverage or insufficient evidence
Revise the best existing page or create a focused resource only when the question requires a materially different answer.
Maintain a scorecard that matches those layers. Search performance data can show impressions, clicks, click-through rate, queries, and landing pages. A prompt observation log can show sampled AI-answer presence, citations, mentions, and competing domains. On-site analytics can show whether visitors continue to a useful next step or return. Business systems can show qualified inquiries, purchases, signups, or other outcomes where attribution is available.
Keep the limits of each measure visible. Click-through rate without result-page context can mislead you. A brand mention without a citation may not create a visit. A citation may appear for a low-value prompt. A hand-checked prompt panel is a sample, not a complete census of AI visibility. Report the measures together so one flattering metric cannot conceal a broken path.
Key takeaways for your next growth cycle
Classify important queries by the job they perform before assuming every lost click has equal value.
Map conversational prompts with their goals, constraints, required evidence, and next decisions intact.
Answer the core question early, then earn the visit with decision support, credible evidence, or practical utility.
Use valid, visible-content-aligned structured data to clarify meaning, not as a shortcut to rankings or AI inclusion.
Diagnose discovery, click capture, page usefulness, and conversion separately before choosing an intervention.
Measure search performance, sampled AI visibility, visit quality, and business outcomes in the same scorecard.
Start with the query cluster most closely tied to a real audience decision. Record its current result environment, repair the page that should own the problem, and define the outcome you expect before making the change. Your next growth move should come from the failed layer you can see, not from a general fear that AI has made search traffic impossible.
Have you heard the news that OpenAI has introduced CPC ads to ChatGPT? This strategic shift has transformed it into a performance-driven channel, offering advertisers new avenues for engaging intent-driven audiences and tracking ROI.
OpenAI is moving away from a focus purely on impressions in ChatGPT to prioritize performance. This change places OpenAI in direct competition with giants like Google by adopting cost-per-click (CPC) ads, allowing advertisers to pay only when users click on their ads.
What’s happening? OpenAI has started testing CPC ads within ChatGPT, where advertisers only pay when their ads receive clicks. Initial reports highlight that these clicks are priced between $3 to $5. They’re rolling out this feature through a limited ads manager, alongside their existing CPM-based model.
Why now? The main catalyst seems to be pricing pressure. Since its launch, ChatGPT’s CPMs have significantly decreased from around $60 to approximately $25. Switching to CPC helps mitigate this decline by connecting revenue to tangible outcomes rather than mere impressions.
Why do we care? With its evolution into a performance channel, ChatGPT is now not just a branding space. The CPC pricing model makes it easier for us to connect budgets directly to measurable actions, test ROI, and compare these results with channels like Google Search.
I’m excited about the opportunity for advertisers to access what could be a high-intent audience in a new format. This presents a first-mover advantage before competition—and the associated costs—escalate.
The bigger picture: This isn’t just a pricing change; it’s a strategic pivot. By embracing CPC advertising, OpenAI challenges Google’s dominance in the market, thereby positioning ChatGPT as a contender for performance marketing budgets.
Reading between the lines: A major challenge lies in proving user intent. While search advertising is effective because it captures users actively searching for something, ChatGPT’s conversational context needs to generate clicks with equal value. Advertisers will likely compare these results directly with Google, setting a high standard for quality and conversion.
Zoom out: Advertising is becoming integral to OpenAI’s long-term revenue plan, supported by investments in ad infrastructure, measurement tools, and a wider self-serve platform.
Bottom line:By implementing CPC ads, OpenAI is vying for the performance-driven ad dollars that have long supported traditional search platforms.
Your campaign can look more efficient while becoming harder to control. Spend may be compressed into fewer active days, conversion signals may be incomplete, and a polished dashboard may show activity without giving you the controls needed to explain or stop it.
If performance changes without a clear bid, audience, or creative change, audit the control layer first. You need to know what the platform is allowed to do, what data its optimizer can see, and whether your reports describe the same system you configured.
Key takeaways
Budget, schedule, consent, optimization, and reporting are separate controls. Changing or validating one does not validate the others.
A restricted ad schedule may concentrate spending rather than reduce the campaign’s monthly spending limit.
Consent diagnostics should help you locate missing or inconsistent signals. A consent rate is not a target to maximize at the expense of genuine user choice.
A dashboard is not a mature control system unless you can inspect state, enforce changes, verify their effects, and reconstruct who changed what.
Paid placement in an AI interface and earned visibility in a generated answer require separate attribution and reporting.
Audit the whole control chain before touching bids
Campaign optimization is usually treated as a bidding problem. In practice, bidding is only one link in a chain. The platform first determines whether an ad is eligible, then how much it may spend, which signals it can use, what decision automation should make, and what evidence you get afterward.
A weakness anywhere in that chain can produce a misleading result. A schedule can alter the concentration of spend. A consent implementation can reduce observable conversions. A reporting delay can make a stable campaign appear volatile. Raising or lowering a bid before resolving those conditions adds another variable without answering the original question.
Control layer
Question to answer
Evidence to record
Business constraint
What outcome, total cost, or operational load can you accept?
Approved spending ceiling, capacity limit, and stop condition
Eligibility
When is the campaign allowed to enter auctions?
Active days and hours, plus the business reason for each restriction
Delivery
How may the platform allocate spend while the campaign is eligible?
Budget values, bidding mode, spending caps, and documented pacing behavior
Signal
Which conversions and consent states can the optimizer observe?
Conversion definitions, consent diagnostics, and coverage by relevant dimension
Observation
Can you explain what happened after delivery?
Reporting latency, available breakdowns, exports, attribution settings, and change history
Run the audit in that order. Starting with reports is tempting, but a report cannot tell you whether the configured business constraint was correct. Starting with bidding is worse because the optimizer may be responding rationally to a budget, schedule, or signal state you did not intend.
Write down the campaign’s intended result and its hard constraint. Separate a performance target from a limit the platform must not cross.
Capture the current schedule, budget, bidding mode, conversion actions, consent state, targeting, and exclusions. Use actual settings, not what the launch plan says should be configured.
Translate settings into effective exposure. For example, calculate the monthly spending ceiling and inspect how much delivery could be compressed into eligible periods.
Check whether the optimizer receives the signals you expect across apps, platforms, regions, and traffic sources. Treat gaps as unresolved until you have distinguished user choice from an implementation problem.
Verify that important controls are enforceable. A pause button, budget edit, or exclusion is useful only if you can confirm its scope, timing, and effect.
Record each change with the old value, new value, timestamp, reason, expected effect, evaluation window, and stop condition. Where practical, avoid changing another layer before the first change can be evaluated.
This gives you a baseline that optimization can build on. Without it, every performance movement invites a new theory, and several contradictory theories may fit the same aggregate chart.
Scheduled campaigns need a spend-concentration audit
A budget limits spending; a schedule limits eligibility. Those settings may feel interchangeable when a campaign runs only on selected days or hours, but they answer different questions.
The practical correction is simple: do not assume that fewer eligible days will produce a proportionally smaller monthly bill. If you intend to reduce total exposure, set the budget to reflect that intention. Keep the schedule focused on when the business can serve demand or when traffic is valuable.
Find every non-continuous schedule. Include campaigns limited to particular weekdays as well as those restricted to certain hours.
Write down why the restriction exists. A schedule tied to staffing, inventory, response time, or lead quality is an operational guardrail. Do not remove it merely to smooth a spending chart.
Calculate the monthly ceiling. Multiply the average daily budget by 30.4, then compare that amount with the total monthly exposure you actually approved.
Check the active-day boundary. Ask whether spending up to twice the average daily budget on an eligible day would create a cash-flow, inventory, or service-capacity problem.
Review eligible periods directly. Monthly averages can hide concentrated delivery. Inspect spend, conversions, and downstream quality during the windows when ads were allowed to run.
Change the correct control. Lower the budget when the total amount is too high. Narrow or widen the schedule only when eligibility itself is wrong.
This distinction also improves diagnosis. Faster spending during active periods does not automatically mean bidding has become more aggressive or demand has improved. It may be the predictable result of the pacing system trying to use the same monthly allowance within fewer opportunities.
Consent diagnostics tell you whether the optimizer can learn
An optimizer cannot act on a conversion it cannot observe. That makes consent signal quality part of campaign operations, not a separate technical housekeeping task.
Use those dimensions to localize a gap. Do not interpret the account-level rating as a complete diagnosis. A lower rate could reflect genuine user choices, traffic composition, a deployment inconsistency, or missing signal transmission. Those possibilities need different responses.
List the apps and platforms that should be sending consent information. Compare that inventory with the live count shown in the diagnostic.
Locate the narrowest break. Determine whether the difference belongs to one app, one platform, one region, one traffic source, or a wider implementation.
Compare EEA and non-EEA results without assuming geography is the cause. Review the regional consent implementation and the underlying traffic mix separately.
Validate the technical path from the consent choice to the advertising platform. Confirm that the relevant state is collected, transmitted, and associated with the intended conversion setup.
Annotate the release or configuration change that corrected a gap. Keep unrelated budget and bidding edits out of the same evaluation window where possible.
Reassess campaign performance only after the corrected signal flow has had an appropriate observation period for your normal conversion lag.
The overall rating is a diagnostic indicator, not an optimization objective. Do not make a consent experience more coercive just to lift a platform metric. Changes to consent language or interaction design should remain under the appropriate privacy and legal review. The campaign team’s job is to make sure a valid choice is transmitted accurately and that missing instrumentation is not mistaken for user behavior.
This protects decision quality in both directions. You avoid blaming creative when measurement is incomplete, and you avoid treating every consent-rate difference as a tagging failure. Once signal coverage is understood, bidding and conversion reports become easier to interpret.
Prove an AI ads manager can control delivery before scaling it
Evaluate an emerging ad manager by what you can verify, not by how familiar its dashboard looks. For every requirement, distinguish between a control that is promised, a control visible in the interface, and a control whose effect you have confirmed.
Authority: Can the authorized operator pause delivery, edit budgets, and reverse a change at the required account or campaign scope?
Budget semantics: Is the budget daily, monthly, lifetime, or another form? How is pacing described, and what prevents an unexpected concentration of spend?
Eligibility and exclusions: Which scheduling, targeting, placement, brand-safety, and exclusion controls actually exist? Do not assume parity with Google Ads or Meta because the navigation feels familiar.
Measurement: Which event counts as a conversion, what attribution rules apply, how quickly do results appear, and can reported totals be reconciled with your analytics?
Diagnostic depth: Can you break performance down far enough to separate delivery, audience, creative, placement, and signal problems?
Auditability: Is there a change history showing who changed a setting, when it changed, and what the previous value was?
Portability: Can you export campaign, delivery, and conversion data in a form your reporting system can retain and compare?
Governance: Can access be limited by role, and can a second operator review high-impact changes before they affect delivery?
If a required control is missing or unverified, limit the test to exposure your organization can tolerate and define a manual stop path before launch. A report that arrives quickly is helpful, but speed does not replace enforcement, audit history, or the ability to reconcile results.
Keep paid AI advertising separate from GEO and earned AI visibility as well. An ad impression purchased inside an AI experience is not proof that the brand was selected, cited, or recommended organically by a model. Give paid campaigns their own attribution labels, landing-page tracking, and reporting view so an increase in paid traffic cannot be presented as improved generative visibility.
Before your next optimization cycle, open one consequential campaign and record its monthly spending ceiling, the reason for its schedule, its maximum active-day exposure, its consent-signal coverage, the controls that can stop delivery, and the delay in its reporting. Resolve any unknown that could change the meaning of the results. Once those controls are observable and enforceable, bid and creative changes can produce evidence you can actually use.
An AI answer can cite your website and still get your product wrong. It can also describe your brand accurately while sending the reader somewhere else. If your reporting treats both outcomes as a visibility problem, you won’t know what to fix.
You need to evaluate three things separately: whether your brand was selected, whether the cited evidence supports the generated claim, and whether a person would trust the answer enough to act. This framework helps you diagnose each layer without mistaking citation volume for accuracy or brand authority.
Key takeaways
A citation proves that a page was selected as a reference. It does not prove that the generated sentence is accurate, complete, current, or supported by that page.
Audit the relationship between each claim and its citation. Counting links or brand mentions alone hides the errors most likely to damage trust.
Segment testing by platform, query language, market, intent, and phrasing. A blended visibility score can conceal serious gaps in a priority language or buying journey.
Maintain a canonical claim layer with explicit evidence, scope, market, and update information. Align your visible content and JSON-LD with that same version of the truth.
Earn independent confirmation by helping people in the communities and channels where decisions are verified. Repetition from your own properties is not the same as corroboration.
A citation proves selection, not accuracy
Grounding means connecting a generated answer to external evidence. It can reduce unsupported generation, but it does not turn every cited sentence into a verified fact. Retrieval can surface a relevant page while the model overgeneralizes its wording, misses a qualifier, combines incompatible details, or attaches the citation to a broader claim than the page supports.
Suppose an answer says a company provides same-day support in every market. Its citation leads to a support page that promises that service only to selected customers in one region. The link is real and topically relevant, but the generated claim is still wrong. A dashboard that records only citation presence would count that outcome as a success.
That is why an AI visibility audit needs four separate tests:
Layer
Question to ask
Common false conclusion
What to inspect
Citation presence
Was your brand or page selected?
Being cited means being represented correctly.
The cited URL, its position, the surrounding answer, and competing domains.
Claim support
Does the cited passage support the exact generated claim?
A relevant page is sufficient evidence.
Wording, scope, qualifiers, dates, markets, exceptions, and the cited passage itself.
Entity accuracy
Are the brand, product, policy, location, and relationships correct?
A fluent description must be reliable.
Names, attributes, availability, ownership, pricing claims, and product-to-brand relationships.
User trust
Would a reasonable reader accept and act on the answer?
Exposure automatically creates confidence.
Independent corroboration, transparency, review quality, community sentiment, and unresolved contradictions.
The practical unit of analysis is the claim-citation pair. Break an answer into factual claims, then open the citation attached to each one. Grade the pair as supported, partially supported, unsupported, or contradicted. Use a separate label when no citation is provided.
Partial support deserves its own category. It often reveals the most important content problem: your page contains the right concept but leaves enough ambiguity for the model to enlarge its scope. A statement that is correct for one plan, country, customer type, or time period needs that qualifier in the same sentence as the claim. Do not leave the limitation in a footnote, accordion, or unrelated section and expect retrieval to preserve it.
Accuracy and trust also need different owners. A content or product team may be able to correct an outdated policy page. Public relations or community teams may need to address persistent third-party confusion. Technical SEO can improve entity consistency and structured data, but it cannot manufacture independent belief. Your audit should route each failure to the team that can change its underlying cause.
Query language can change who gets cited
You cannot infer global AI visibility from English-language testing. In one large cross-platform analysis, 3.25 billion citations across seven AI models and 14 countries showed query language as the main catalyst changing citation rates. Google AI Overviews and ChatGPT also displayed different response patterns for non-English prompts. That finding should be treated as a strong warning about aggregation, not as a universal rule for every query or brand.
Language changes more than the words in the prompt. It can change the pool of retrievable pages, the entities a model recognizes, the regional sources available to support an answer, and the way a user expresses intent. A literal translation of an English prompt may therefore test translation quality rather than the search behavior of a person in that market.
Build your prompt set from real decisions instead of a list of brand keywords. Include the questions people ask when they are discovering a category, comparing options, checking a claim, assessing risk, resolving a problem, and preparing to buy. Then vary the constraints that matter to the decision: location, use case, customer type, compatibility, availability, policy, or another relevant condition.
Use a segmented test matrix
For every prompt, record the exact wording and the conditions under which the answer appeared. At minimum, preserve:
The user’s underlying intent and the decision the answer is meant to support.
The exact prompt, including follow-up questions and any constraints introduced earlier in the conversation.
The query language and intended market. Keep them separate because a language can span several markets, and a market can contain several languages.
The AI platform or search surface. Do not merge ChatGPT results with Google AI Overviews or another system under a single generic AI ranking.
The date of capture and any visible model or product label, so later retests can be compared with the right context.
Whether the session was signed in, personalized, location-aware, or part of an existing conversation.
The complete answer, every citation URL, and the passage that supports or fails to support each material claim.
Have a fluent local speaker or market specialist adapt important prompts. Ask how a real customer would phrase the problem, what local terminology they would use, and which proof they would expect. The localized prompt should preserve the intent, not the English syntax.
Report results by language and platform before calculating any overall figure. If your brand performs well in English but disappears or becomes inaccurate in another priority language, an average can make the program look healthy while the affected market sees a different brand. The segment is the truth; the blended number is only a summary.
Build a truth layer that models and people can verify
The safest way to improve citation accuracy is to make consequential claims easy to retrieve, hard to misread, and consistent across the properties you control. That work begins before schema markup. A perfectly marked-up contradiction is still a contradiction.
Create a canonical claim ledger
Maintain a working record of the claims that affect whether someone chooses, trusts, or rejects your brand. Each record should contain the entity, approved wording, supporting URL, evidence, scope, exceptions, applicable language and market, content owner, review date, and current status.
Prioritize claims about what a product does, who it is for, where it is available, what it costs, what is included, what it integrates with, and what policies govern its use. These are the statements most likely to change a decision. They are also vulnerable to drift when product pages, help documentation, sales copy, partner listings, and old announcements describe different versions of reality.
Give each consequential claim a clear canonical home. The page should state the fact directly, place its qualifier beside it, explain the evidence, identify the applicable product or market, and make the update status visible. If the answer differs by plan or region, present those differences as structured comparisons rather than scattering them across several pages.
Review conflicting owned pages before publishing more content. A new explainer cannot establish clarity while an old pricing page, support document, or local site still makes the opposite claim. Correct, redirect, archive, or clearly date obsolete material according to its purpose. If an older page must remain accessible, label its historical status where a person and a retrieval system can encounter it.
Use JSON-LD as a consistency layer
JSON-LD can clarify entities, properties, and relationships. It cannot supply evidence that the visible page lacks, resolve disagreement between departments, or make an exaggerated claim trustworthy. Treat structured data as a machine-readable expression of the same facts a reader can verify on the page.
Use the schema type that accurately describes the visible entity or content, such as Organization, Person, Product, or Article where appropriate.
Keep names, canonical URLs, identifiers, brand relationships, and other entity attributes consistent with the page and your canonical claim ledger.
Do not place a material claim only in markup. If it matters enough to encode, it should be supported in the visible content.
Match market- and language-specific markup to the corresponding page. Do not attach a global claim to content that supports only one region.
Update structured data when the underlying fact changes. A stale JSON-LD property can preserve the contradiction you just removed from the copy.
Validate syntax and then inspect meaning. Technically valid markup can still identify the wrong entity or express an unsupported relationship.
This approach gives you one controlled path from approved fact to human-readable evidence to structured representation. It also makes corrections easier: when an AI answer exposes a problem, you can trace the claim to its owner and every place where it appears.
Earn confirmation outside your own website
People rarely make an important decision inside one answer box. The search journey can move through AI tools, marketplaces, reviews, forums, video, friends, and knowledgeable people as the user looks for stronger confirmation. Yext reported that 75% of consumers were using more platforms than a year earlier, while only 10% trusted the first result.
That behavior reflects three judgments: whether people trust themselves to evaluate the subject, whether they trust the platform presenting the answer, and whether they trust the underlying information source. Your citation work can improve the last layer, but brand trust also depends on what people encounter when they leave the generated answer to verify it.
Independent confirmation cannot be produced by repeating the same marketing claim across more company profiles. It comes from useful participation in places where people exchange experience: practitioner communities, customer conversations, events, forums, reviews, social channels, and expert-led media. The operating rule is simple: listen for the unresolved question, help with that question, and let the brand mention remain secondary to the answer.
Track recurring questions, objections, misconceptions, and vocabulary in the communities relevant to your buyers.
Answer with specific, verifiable information. Link to documentation when it genuinely helps rather than treating every interaction as a distribution opportunity.
Turn recurring questions into durable resources on your own site, then keep those resources aligned with the conversations that inspired them.
Make it easy for customers, partners, practitioners, and journalists to verify factual details without copying promotional language.
Correct errors openly and precisely. State which claim is wrong, what the accurate scope is, and where the supporting information lives.
Never manufacture reviews, personas, community conversations, or supposed independent consensus. Discovery gained through deception creates the exact trust problem the program is meant to solve.
The goal is not to control every mention. It is to make the accurate account easier for other people to confirm and repeat in their own words. That creates a healthier evidence environment than a large collection of identical brand-authored claims.
Audit the failure pattern before choosing the fix
A useful AI citation audit should reproduce an answer, isolate the error, identify the controllable cause, and verify the correction. Screenshots of favorable mentions are not enough.
Define the decision. Start with prompts tied to meaningful user actions or material brand risk. Record what a correct answer must help the user understand.
Capture the full context. Save the exact prompt sequence, language, market, platform, date, answer, citations, and visible session conditions.
Split the answer into claims. Separate factual statements from recommendations, opinions, and connective language. Mark the claims that could change a purchase, eligibility, support, compliance, or reputation decision.
Check every citation. Open the linked page, locate the supporting passage, and grade the relationship as supported, partially supported, unsupported, contradicted, or uncited.
Check the entity. Verify names, product relationships, attributes, locations, policies, availability, and other details against the canonical claim ledger.
Trace the likely cause. Look for unclear wording, missing qualifiers, stale owned pages, inconsistent markup, weak localized evidence, entity ambiguity, or repeated third-party misinformation.
Fix the highest-consequence origin. Correct the canonical page and contradictory owned properties first. Then update structured data, partner records, listings, and other controllable representations. Seek corrections from external publishers or platforms where an appropriate process exists.
Retest the original conditions. Use the same prompt and context, then test natural variants. A changed answer may indicate improvement, but it does not prove that every platform, language, or user will now receive the same result.
Measure accuracy and trust separately from reach
Your reporting should preserve the distinction between being visible and being represented well. Useful measures include:
Citation presence: how often your brand, canonical pages, or relevant independent pages appear for eligible prompts.
Claim support rate: how often cited passages fully support the claims attached to them. Keep partial support visible instead of counting it as success.
Brand claim accuracy: how often material statements about your entity match the approved facts and their qualifications.
Uncited material claim rate: how often consequential factual statements appear without a reference a reviewer can inspect.
Cross-platform consistency: whether different AI surfaces agree on the material facts, not whether they use identical wording.
Language and market gap: the difference in citation presence, support, and accuracy between priority segments.
Independent confirmation: whether the answer’s important claims can be verified through credible, non-owned evidence where independent evidence should exist.
Correction latency: how long your organization takes to correct the controlled origin of a material error and complete the relevant retest.
Avoid setting a citation target without a support target. A campaign can increase the number of citations while also increasing the number of confidently misstated claims. That is not improved visibility; it is wider distribution of an accuracy problem.
Let the pattern determine the intervention
High citation presence, low claim support: clarify the canonical content, move qualifiers beside their claims, remove contradictions, and inspect why irrelevant passages are being treated as evidence.
Low citation presence, high brand accuracy: improve retrievability, entity clarity, localized coverage, content distribution, and credible external confirmation without rewriting already-clear facts for novelty.
High accuracy, low user trust: examine reviews, community sentiment, transparency, proof quality, and what a person encounters after clicking. More owned content may not solve this failure.
Strong English results, weak priority-language results: build native-language evidence and entity consistency for that market. Do not rely on literal translation or a global average.
Conflicting answers across platforms: preserve the platform split in reporting, inspect each citation pool, and fix shared contradictions before chasing platform-specific tactics.
A material uncited error: treat the incorrect claim as the incident, even if the rest of the answer is favorable. Prioritize errors that change cost, availability, eligibility, obligations, safety, or a buyer’s ability to make an informed choice.
Start with the decision-heavy query where a wrong answer would cost the most trust. Test it in your primary language and the highest-priority additional language, grade every claim-citation pair, and correct the most consequential contradiction you control. Do that before pursuing a larger citation count. The citation is not the finish line; an accurate, verifiable, and trusted answer is.
You may have watched your AI assistant reject an unsafe request and concluded that its safeguards worked. If you tested only once, you answered the wrong question. An attacker does not need every prompt to succeed. They need one useful failure after enough retries.
Best-of-N jailbreaking turns that model variability into a search process. To manage the risk, you need to evaluate the whole campaign, enforce permissions outside the model, and control every additional chance created by retries, fallback models, tools, and automated agents.
The dangerous unit is the campaign, not the prompt
A Best-of-N attack creates or collects multiple versions of a prohibited request, submits them to an AI system, and selects the response that comes closest to the intended outcome. The essential move is to send many variations and keep the most successful result. The value of N is not fixed, and the selection can be performed by a person, a script, or another model.
This changes the security question. A per-request review asks, “Did this prompt get blocked?” A campaign-level review asks, “Did any related attempt produce a prohibited result?” The second question reflects the attacker’s objective.
The probability principle is straightforward. If each attempt has a nonzero chance of crossing a boundary, repeated opportunities can raise the chance that at least one attempt succeeds. Under the simplified assumption that attempts are independent and have the same success probability p, the probability of any success after N attempts is 1 – (1 – p)^N. Real prompt variants are often correlated, so you should not use that formula as a production risk estimate. Measure complete campaigns against your actual system instead.
Three distinctions prevent confusion during threat modeling:
A normal retry is usually an attempt to clarify a legitimate request after an incomplete or incorrect answer. Repetition alone does not establish malicious intent.
A jailbreak tries to bypass behavioral restrictions placed on a model.
Prompt injection supplies untrusted instructions that compete with the system’s intended instructions, often through user input or retrieved content. Best-of-N is a search strategy that can amplify jailbreaks, prompt injection, or other policy-evasion techniques.
Treat Best-of-N as a threat multiplier, not as the root vulnerability. It finds inconsistent decisions and weak handoffs. It cannot grant a caller a permission that your application enforces deterministically outside the model. That is why authorization architecture matters more than clever safety wording.
Where repeated attempts find extra chances
Your model is only one part of the attack surface. A typical AI workflow also has an identity layer, input filters, a router, one or more models, output checks, retrieval, tools, and application code. Every component that makes a fresh probabilistic decision can give a campaign another route to success.
Layer
Misleading green light
Campaign signal to inspect
Stronger control
Prompt policy
One prohibited request was refused
Related requests are repeatedly rephrased after denials
Aggregate policy events by actor, session, intent cluster, and protected resource
Input moderation
Each prompt remains below an individual alert threshold
Small wording, format, language, or encoding changes accumulate around the same objective
Analyze normalized forms and sequences while retaining the raw input for investigation
Model routing
The primary model refused
A fallback model, alternate endpoint, or retry path returned a different decision
Apply one canonical policy before routing and a final gate after generation
Tools and agents
The assistant’s visible text looks harmless
A tool call requests a broader scope, sensitive record, or irreversible action
Enforce authorization, parameter validation, and action limits in application code
Traffic controls
Each IP address or API key stays within its local limit
Related attempts move across sessions, keys, endpoints, or models
Correlate only the identifiers justified by your threat model, privacy obligations, and retention policy
Logging
Every prompt was stored somewhere
No record connects attempts, decisions, tool calls, and final outcomes
Assign campaign and event identifiers so an investigation can reconstruct the sequence
For an SEO, AEO, or GEO workflow, the highest-consequence result may not be a bad chat response. It may be an unauthorized CMS publication, a destructive edit, exposure of an unpublished campaign, or a tool call made with the application’s credentials. If a model generates page copy or JSON-LD, syntactic validation is necessary but insufficient. Valid structured data can still contain false, disallowed, or unapproved claims. Check the output against business rules and publishing permissions before it reaches a live page.
Build controls that survive repeated attempts
No safety prompt can carry this responsibility alone. Prompts influence model behavior, but they are not security boundaries. Use several controls with different failure modes, and place deterministic checks wherever failure could expose data, spend money, alter content, or trigger an external action.
Put authorization outside the model. Resolve the authenticated principal in application code, grant the least privilege needed for the workflow, and verify permission again when a tool executes. Never let generated text decide whether the caller may read, publish, delete, or export something.
Separate read and write capabilities. An assistant that only needs to draft content should not inherit publishing or deletion rights. When write access is required, constrain the allowed resource, action, fields, and destination.
Normalize for analysis without overwriting evidence. Retain the original request, then create a canonical representation for similarity detection. Normalization can help reveal superficial changes in spacing, character representation, formatting, or casing, but it must not silently change the content executed by downstream systems.
Maintain campaign state. Record the actor or service identity, session, endpoint, model route, normalized intent cluster, policy decision, tool request, and outcome. Look for repeated denials, rapid reformulations, alternate-route probing, and requests that converge on the same protected capability.
Add adaptive friction. As campaign risk rises, reduce retry opportunities, disable expensive fallback routes, introduce a cooldown, require stronger authentication, or move the request to human review. Apply the strongest friction to workflows with data access or irreversible effects rather than imposing the same response on harmless drafting tasks.
Gate outputs and tool calls separately. Check generated content against the output policy, validate structured fields, reject unexpected tool names or parameters, and limit the records or resources returned. A harmless-looking explanation must not conceal a disallowed action request.
Define safe failure behavior. If moderation, identity resolution, authorization, or final validation is unavailable, return a controlled error for protected operations. Do not route around a failed safeguard to preserve a smooth user experience.
Protect the control plane. Restrict who can change system prompts, policy rules, model routes, tool definitions, and safety thresholds. Log those changes and make rollbacks possible, because a campaign can exploit configuration drift as readily as model variability.
There is no universal safe retry count. A blanket limit low enough for a sensitive data-export agent may be needlessly hostile in a public brainstorming tool. Set budgets by consequence, then examine legitimate retry behavior before choosing enforcement thresholds. Track false positives alongside security outcomes so that users who are clarifying ambiguous, multilingual, or accessibility-related requests are not treated automatically as attackers.
Be careful with model-based safety judges as well. A second model can add useful evidence, but it may share blind spots with the model it evaluates. Use deterministic authorization and validation for hard boundaries, with model judgments contributing to risk scoring rather than granting privileged access on their own.
Test the full campaign without publishing an exploit kit
A single-prompt red-team check will miss the defining behavior of Best-of-N. Your evaluation runner should group related attempts, preserve production routing logic, and score whether any attempt reaches a prohibited outcome. Keep testing authorized, isolated, and away from live customer data or publishing systems.
Define the breach before generating tests. Describe prohibited outcomes in observable terms, such as returning a protected field, invoking a disallowed tool, publishing without approval, or producing content that violates a named policy. A vague label such as “unsafe response” produces inconsistent scoring.
Build campaign families. Group sanitized test cases by underlying objective, then vary the permitted dimensions relevant to your system, such as phrasing, format, language, model route, and retry sequence. Keep actionable attack strings in an access-controlled security repository rather than general documentation or analytics dashboards.
Reproduce the production topology. Include the actual order of input checks, retrieval, routing, fallback behavior, output gates, tools, and error handling. Testing the base model alone does not test the application your users can reach.
Run attempts as connected sequences. Carry session and risk state between related requests. Also test whether switching endpoints or invoking an automated agent incorrectly resets that state.
Score outcomes at two levels. Retain per-request decisions for diagnosis, but make campaign-level success the headline measure. A system can have an impressive individual refusal rate while still allowing too many campaigns to obtain one useful failure.
Review the most consequential path first. A policy-breaching paragraph matters, but a tool call that exposes private data or changes a live site demands tighter controls and faster remediation.
Version the evaluation and rerun it after changes. A new model, system prompt, router, retrieval source, guardrail, tool definition, or fallback rule can alter campaign behavior even when the visible feature appears unchanged.
Your evaluation dashboard should include the campaign any-success rate, attempts to the first breach, breach severity, detection and containment outcomes, tool or data-boundary violations, and false-positive friction for legitimate users. Do not collapse these into one average. A small number of severe authorization failures should remain visible rather than being diluted by many harmless refusals.
Stop a test immediately if it begins interacting with real user records, external recipients, paid services, or live publishing. Move the scenario into an isolated environment with synthetic data and inert tools. The purpose of the exercise is to verify containment, not to prove that production damage is possible.
Key takeaways for AI product owners
One successful refusal does not establish safety; measure whether any attempt in a related campaign succeeds.
Best-of-N exploits repeated opportunities and inconsistent decisions, so retries, fallback models, alternate endpoints, and agents all belong in the threat model.
System prompts and model-based judges can support safety, but they cannot replace deterministic authentication, authorization, validation, and tool restrictions.
Aggregate related attempts without assuming every retry is malicious; calibrate friction to the consequence of the requested capability.
Test the production workflow as a sequence, then report campaign-level success and breach severity alongside per-request refusal metrics.
Keep security payloads controlled, use synthetic data and inert tools, and never red-team an external or production system without authorization.
Before your next release, choose the AI workflow with the greatest access to data, tools, or publishing. Trace every place where a rejected request can receive another model call or another route. Then add campaign-level telemetry and a deterministic gate at the highest-consequence handoff.
That review will not eliminate model variability. It will prevent variability from becoming permission.
For years, I’ve been told to stick to a set of guidelines: always use top-notch creatives, maintain a polished brand, follow scripts, and adhere to platform-recommended formats.
Lately, while navigating ad accounts or simply scrolling through feeds, I’ve noticed something intriguing. The ads that grab my attention often defy these rules. They’re less polished, scrappier, and sometimes referred to as ‘ugly ads.’ What’s fascinating is that they’re outperforming the traditional, polished ones.
More brands are deliberately breaking so-called best practices to stand out. It’s important to remember that these practices represent an average of what worked for others in the past. By the time a strategy becomes a platform-recommended rule, it might have already lost its edge.
This is why defying best practices can lead to success — but only if you understand the reasons behind them.
Why Breaking Best Practices Enhances Ad Performance
Before diving into what to change, it’s crucial to understand the rationale behind existing rules. Platforms like Meta and TikTok have dual objectives:
They aim for you to spend money on ads.
They want to keep users engaged on their platforms.
The best practices they promote are designed to ensure a seamless experience, encouraging ads to resemble others. The issue is that familiarity eventually breeds invisibility. When I adhere too closely to the rules, my ads risk blending into the background noise, overlooked by users.
Highly-produced ads often scream ‘this is an ad,’ prompting users to skip them before my message hits home. In contrast, when my ad resembles something a friend might share, users’ defenses remain down longer, potentially transforming a scroll into a conversion.
This is why many top-performing ads today don’t appear traditionally polished or on-brand. They break patterns instead. Consider:
Grainy phone footage.
Notes app screenshots.
Green-screened reactions or commentary videos.
Other lo-fi formats that outperform studio-quality creatives.
To implement this, I started intentionally reducing my production value and experimented with formats like point-of-view (POV) shots tailored to various personas.
Many brands have adopted guidelines that make them seem faceless and untouchable. They refrain from showing a messy office, an unpolished founder, or anything that challenges their corporate script. However, others are discarding that playbook, embracing founder-led ads that deviate from the polished executive version.
There’s a catch.
Breaking the rules works only when it’s genuine. I’ve learned that faking authenticity is easy to spot and can backfire. This was evident in a viral series of videos where McDonald’s CEO appeared to present a new burger, but his execution was criticized for being stiff and unconvincing.
As shown in a Dineline video, his performance appeared staged. Contrarily, Burger King’s president presented their burger with no hesitation, offering a genuine and relatable moment.
The distinction was evident: One was a product pitch, and the other felt authentic.
If my leadership doesn’t genuinely believe in the product, neither will my customers. Rule-breaking should allow us to be real, rather than simply appear unpolished.
You’ve probably encountered video hook best practices like ‘show the product in the first two seconds and state the value prop clearly.’ Sound familiar?
Imagine my ad starting with a screenshot of a negative comment, like one for a skincare product stating, ‘This probably smells like old socks, and does it even work?’ My ad would then show the founder confidently disproving this in an unscripted manner, applying the product.
Though this breaks the positive-association rule, it leverages viewers’ curiosity about digital conflicts. By the time they realize it’s an ad, they might already be engaged.
I learned not to abandon all polished assets just yet.
Rule-breaking is strategic, and often misunderstood when the ’80/20 rule’ is ignored.
Switching completely to shaky phone footage isn’t wise. Keeping 80% of the budget in traditional ads while using 20% for testing unconventional ones can be effective.
Next testing campaign, I plan to try:
The silent test: Running a silent ad with bold captions to stand out in a noisy feed.
The UI ghost: Using static images resembling platform notifications to pause scrolling.
The algorithmic trust fall: Disabling auto-optimizations in a campaign to test creative performance without constraints.
Don’t Follow the Rules; Understand Them
Best practices are a guide, not a strategy. To move beyond them, I do it systematically.
I start by questioning the rule’s existence, evaluating its current relevance, and testing its opposite in a structured manner. Comparing traditional and lo-fi approaches helps me understand user engagement better.
In an environment where brands play it safe, those who understand and strategically break the rules will capture attention and conversions. My goal is to learn faster than the competition, skipping guesswork.
When I think about brand visibility today, it’s clear that being chosen by AI systems is crucial. Authority, unique insights, and consistent signals now determine if my brand makes the cut.
I’ve realized that AI isn’t just reshaping search; it’s deciding which brands are seen and which are ignored.
I learned from Andrew Warden, CMO of Semrush, at the Adobe Summit that visibility is evolving fundamentally, and our brands risk being systematically filtered out by AI systems.
“The idea of standing out is no longer optional. There’s a real risk of sameness,” he pointed out.
With AI systems deciding what to highlight and what to ignore, I know I must compete more fiercely for visibility in AI-generated answers.
AI is Changing How Discovery Works
The change is evident in the data: 60% of Google searches now end without a click to a website. People are still seeking information but aren’t always visiting websites. They’re getting their answers directly from AI systems like Google AI Overviews and ChatGPT.
These AI systems have become, as Warden described, the “new gatekeepers.”
This shift ushers us into the agentic era, where AI systems act as intermediaries, guiding users from inquiry to decision in one seamless interface.
Meanwhile, user behavior is evolving. People engage more in conversational environments, posing follow-up questions, refining queries, and surveying options within the interface, all resulting in fewer clicks but often attracting higher-intent users.
Warden noted that consumers using LLMs convert at least four times higher than those relying solely on search.
SEO is the Foundation
Despite some claims that AI could replace search, Warden reassured us that SEO is not dead.
SEO has become more foundational than ever. It’s essential to ensure my brand exists in the data layer AI systems rely on.
Warden emphasized, “SEO isn’t just for humans anymore. This is a training manual for AI right now.”
This involves ensuring:
Crawlability
Indexability
Structured data
Authority signals
Without these, my brand won’t appear at all.
Research backs this up: 94% of Google AI Overviews cite at least one top organic result, reaffirming that traditional search signals still support AI outcomes.
The Rise of the ‘Bland Tax’
One striking concept from the session was what Warden dubbed the “bland tax.”
AI conditions itself to overlook blandness, causing generic or repetitive content to vanish.
If I’m generic, Warden warned I’m perceived as average, and if I’m bland, I’m effectively invisible.
AI systems don’t reward sameness. Rather than highlighting my brand, they often condense similar content into a single, attribution-lacking response.
“This is an invisible penalty,” Warden noted.
The consequences manifest in several ways:
My brand identity gets erased in AI-generated summaries
My content is filtered out as low-value
My work becomes training data for AI without offering visibility to my brand
“You also become a free training ground for LLMs,” he said.
What Visibility Depends On
Warden redefined brand visibility as a blend of:
Discoverability: Can LLMs easily find me?
Authority: Do they trust my brand enough to include it?
“You absolutely need both,” Warden asserted.
SEO ensures I’m discoverable. Authority determines whether my brand shows up in AI-generated responses.
Without authority, I risk turning into a “commodity that isn’t worth being mentioned.”
How to Win: Three Key Signals
Warden outlined three crucial areas determining whether my brand appears or gets filtered out:
1. Entity Authority
AI systems map entities and relationships, and they must recognize my brand as an authority on a topic.
One key signal is brand demand. If people aren’t seeking out my brand, neither will AI.
Strong brands emphasize their authority across various platforms—owned content, media exposure, and community discussions—demonstrating their niche.
2. Information Density and Originality
AI systems prioritize content that offers new insights. It’s vital to not just publish content but contribute something meaningful.
They emphasize new facts with proprietary data, original research, unique perspectives, and expert insights.
According to Warden, original insights can enhance visibility by 30 to 40%.
3. Signal Alignment
AI evaluates not just what I convey but also what others say about my brand.
This includes reviews, discussions on platforms like Reddit and YouTube, media mentions, and customer conversations.
Warden warned that conflicting signals could prompt AI to flag my brand as unreliable.
Consistency across these channels creates what he called a “consensus signal” that AI systems can trust.
Why Most Organizations Aren’t Ready
One of our biggest challenges is organizational, as visibility isn’t just a channel issue; it’s an organizational one.
Currently, responsibilities are fragmented. SEO teams focus solely on rankings, PR and brand teams manage messaging, and growth teams conduct experiments. This leaves no one clearly owning AI visibility.
This fragmentation leads to inconsistent signals and missed opportunities for us.
To truly compete, we need alignment across teams, working on a shared strategy about how my brand appears wherever LLMs gather data.
The Measurement Problem
Meanwhile, traditional performance metrics are unraveling.
Many marketers, including myself, notice a gap where rankings hold steady, but traffic declines. Meanwhile, leads might increase, yet attribution remains murky.
Warden explained that demand remains, but traffic no longer serves as its proxy. Our content is utilized, but not in ways directing users back to us.
This creates a growing disparity between impact and the ability to measure that impact accurately.
From Rankings to Relevance
The nature of competition has evolved. I’m no longer vying for a mere position; instead, I’m competing to be featured in a synthesized AI answer.
Authority, once easier to influence, now hinges on external validation—emphasizing what others say over what I publish.
Algorithms have shifted from being my allies to arbiters of meaning, marking a significant change in search dynamics since Google itself emerged.
The New Rules of Brand Visibility
AI has not altered what makes a brand strong but has transformed how that strength is measured and rewarded. The brands that win today will build real authority in a focused niche, publish original and high-value content, and ensure consistent messaging across every platform.
The need for consistent third-party validation across an ecosystem is paramount.
As Warden urged, I must make it impossible for LLMs to ignore my brand.
In March 2026, I, along with my research team, delved into the world of solutions used by B2B distributors, manufacturers, and enterprise commerce businesses. Our goal was simple: to find the best tools to connect ERP systems to eCommerce platforms. We studied 34 products spread across three categories: dedicated middleware connectors, ERP-native proprietary storefronts, and general-purpose iPaaS platforms. Each type made our list because they
