Tag: Compliance

Google Ads Image Carousels and Phone Number Fraud Controls

Google Ads now puts two very different jobs on the same campaign manager’s desk. The mobile Images tab can carry horizontally scrollable ads built from images, headlines and links, creating another route into visual discovery. But a phone number associated with fraud or earlier policy violations can cause an ad to be disapproved under Destination requirements. One change expands your reach; the other can shut it down.

If you manage paid search, do not leave compliance until after the creative is ready. Treat the query, image, headline, destination and phone number as one chain. Your practical goal is not merely to activate a new format. You need to know that the ad is relevant, the contact identity is defensible and a delivery problem will not be mistaken for a performance problem.

Key takeaways

Use an image carousel when the visual answers a real customer question. A decorative image may fill the format without helping someone choose.
AI-driven matching can connect visuals with searches beyond traditional shopping categories, but it cannot make an unclear offer useful.
Manage every advertised phone number as an identity asset. Its history can matter even when your current ad and landing page look compliant.
Confirm approval and delivery before judging performance. A disapproved ad tells you nothing about whether its creative would have worked.
When possible, do not change the phone number and the main creative idea in the same test. Staging those changes makes the cause of a failure much easier to identify.

Design the carousel around a visual decision

A designer arranges five coordinated image cards in a horizontal sequence beside a smartphone on a dark worktable.

The Images tab serves people who are already exploring through visuals. The carousel format can put your brand in front of someone while they compare and investigate options, before their behavior narrows to a conventional text-ad click. That makes the placement useful for discovery, but only when the image carries information.

Google’s matching technology can align an ad’s visuals with a search and can surface the format outside retail shopping, including categories such as law and insurance. That expanded availability is not proof that every advertiser needs an image campaign. A generic courthouse, handshake or office photo may signal a category, but it rarely explains why the searcher should choose one result over another.

Write a four-part creative brief

Before anyone selects an image, require the brief to answer four questions:

What is the searcher trying to see? Name the visual question, not merely the keyword. The person may need to recognize a product, compare alternatives, understand a process or verify a visible attribute.
What does the image resolve? State what someone should understand before reading the headline. If the answer is only that your company exists, the asset is probably too generic.
What context must the headline add? Use the headline for the qualification, distinction or next step that the visual cannot communicate reliably. Repeating the image wastes limited attention.
Does the destination continue the same thought? The linked page should immediately confirm the subject and promise shown in the carousel. A visually relevant ad that opens an unrelated or overly broad page creates a broken handoff.

Keep those answers together in the campaign record. If AI matching places the visual beside a relevant search, you can then inspect the whole path rather than debating the image in isolation.

Test a decision, not a decoration

Organize creative variants around different reasons a person might choose. One version might demonstrate the offering itself; another might make a comparison easier; a third might explain a process visually. Changing only the crop, background color or ornamental treatment may produce a different-looking ad without testing a meaningful customer question.

Give each variant a one-sentence hypothesis: what the image should help the searcher understand or decide.
Keep the destination aligned with that hypothesis. Do not send every visual idea to the same generic page merely because the URL is convenient.
Change one major idea at a time when learning matters. If the subject, headline, destination and contact method all change together, the result will be difficult to interpret.
Define the intended action before launch, such as a qualified visit, call or lead. Increased visual exposure is not automatically business value.

AI matching is distribution logic, not your creative strategy. Google can decide that a visual corresponds to a search; you still have to decide whether the match expresses the right promise and attracts the right person.

Audit the phone number as a campaign identity

A magnifying lens examines a telephone handset token in a connected campaign chain with clean green and tangled red pathways.

Google set December 10, 2025 as the effective date for rejecting phone numbers tied to fraud or previous policy violations, with enforcement scheduled to increase over roughly the following eight weeks. That ramp described how enforcement would be introduced; it was not a guaranteed grace period for every account. Your campaign controls should already treat the rule as a baseline.

Do not misclassify this as click-fraud prevention. The change sits under Google’s Destination requirements and concerns the reputation and policy history associated with a phone number. It is not a measurement of invalid traffic. A clean-looking ad or landing page therefore does not neutralize a flagged contact number.

A phone number is more than a line of copy. It connects the ad to the identity, routing and history of the business presented to the user. Treat it like a governed asset by maintaining a simple registry for every number placed in an ad or ad asset. If the same number appears on the destination, record that placement as well so the complete contact path remains traceable.

Registry field	What to record	Decision it supports
Exact phone number	The complete number as it appears in the campaign	Prevents formatting variants or duplicates from escaping review
Campaign placement	Every ad, asset or destination where your team uses it	Shows the likely scope if the number is rejected
Owner and provider	The business owner, vendor or partner responsible for the number	Identifies who can investigate its use and history
Provenance check	Whether the number is dedicated, shared or reassigned, plus what the provider can confirm about prior use	Exposes uncertainty before the number reaches a campaign
Routing check	The business, team or call flow that answers the number	Confirms that the contact experience matches the advertiser represented
Review state	Verified, pending investigation or rejected, with the review date	Stops an old assumption from being treated as a current check

Pay particular attention to numbers supplied by agencies, tracking vendors, franchises, call centers or other partners. The fact that your team did not create a number’s history does not remove the operational risk when Google evaluates its association with fraud or past policy breaches. Ask who controls it, whether it has been shared or reassigned, and who can investigate a flag. Those answers do not guarantee Google’s approval, but they give you a responsible escalation path.

Do not respond to uncertainty by cycling through unverified numbers until one is accepted. That destroys traceability and preserves the same control gap. A replacement should have a known owner, correct routing and documented provenance before it enters another campaign.

Separate policy eligibility from creative performance

A campaign can fail before the audience ever evaluates it. If you treat that failure as weak demand, you may discard a sound visual idea. The safer release sequence has two stages: establish eligibility first, then measure performance.

Stage one: prove that the campaign can serve

Freeze the proposed package: image, headline, destination and any advertised phone number. Give each item a clear owner.
Confirm that the visual answers the intended search task and that the linked page continues the same promise.
Check every included phone number against your registry. Resolve unknown ownership, routing or provider history before launch.
After submission, verify approval and delivery status before increasing exposure or interpreting performance.
If a phone-related disapproval appears, record the exact notice, number and affected placements. Stop adding that number to new ads while it is being investigated.
Verify the number with its owner or provider, then follow the remediation route supplied in the disapproval notice and Google’s Help Center. Replace the number only with another contact that has passed your ownership, routing and provenance checks.
Once the issue is resolved, review other campaigns that use the same number. Fixing a single rejected ad does not remove the shared dependency elsewhere.

Avoid rewriting unrelated headlines or swapping landing pages while investigating a phone-specific rejection unless the notice identifies those elements too. Unrelated changes create more possible causes and make the final resolution harder to document.

Stage two: prove that the creative earns its place

Once the campaign is eligible to serve, evaluate the visual hypothesis against the action you defined. Keep the approved phone number and destination stable while comparing major image ideas whenever possible. This separates three conditions that are often blurred together:

Low or interrupted delivery: first check eligibility and policy status. There may not be enough audience exposure to judge the creative.
Exposure without useful engagement: inspect whether the image answers a meaningful question or only signals the category.
Engagement without the intended action: inspect the handoff among the image, headline, destination and contact path. The ad may attract attention while promising something the next step does not confirm.

An approved ad can still be irrelevant, and an AI-matched visual can still be weak. A disapproved ad, however, cannot prove or disprove the creative idea. Keeping those judgments separate prevents you from abandoning useful visual direction because a contact asset blocked delivery, or scaling an attractive ad while its phone-number governance remains unresolved.

Before your next image-carousel test, require two approvals. The creative owner should confirm the image, headline and destination in one sentence. The operational owner should identify the exact phone number, its controller and its review state just as quickly. If either owner cannot answer, the campaign is not ready to scale.

References

November 11, 2025

Google Advertiser Verification Policy: An Accuracy Checklist
You have a Google advertiser verification request open, several people can supply the details, and at least two records do not match. The dangerous move is to choose the answer that seems most likely to pass. Google can treat false or misleading verification information as an attempt to circumvent its compliance checks, with immediate account suspension as a possible consequence.

Your safest next step is an accuracy gate: define exactly who the advertiser is, map each answer to evidence, stop when records conflict, and approve the complete submission before anything reaches Google. Here is a practical way to do that without turning verification into a guessing exercise.

Why a verification mismatch is now a suspension risk

In November 2025, Google revised its Circumventing Systems policy with an explicit example covering false or misleading information submitted during advertiser verification. The change matters because it places dishonest verification details in a serious enforcement category rather than treating them as ordinary incomplete paperwork. A violation can lead to immediate suspension.

The practical danger is classification. Your team may see a mismatched name as a typo, an old address as stale account administration, or an unsupported answer as a temporary placeholder. Google receives the submitted representation, not the internal explanation you never supplied. You should not rely on the platform inferring that an inaccurate answer was harmless.

This does not mean you should panic over punctuation. It means you need to treat every factual answer as a claim that must be truthful, supportable, and responsive to the field Google actually asked you to complete. Plausible is not the same as accurate.

Define the advertiser before completing individual fields

A verification form becomes risky when each field is answered in isolation. The brand on a website, the person managing campaigns, the agency operating the account, and the business legally responsible for the advertising can be related without being interchangeable. Start by identifying the person or business the verification request is asking about.

Create a canonical verification record before opening the submission form. This is an internal working record, not an extra document for Google. It should contain the exact values your evidence supports, along with the record used to support each value. Preserve spelling, corporate suffixes, address elements, and other identifiers exactly where they are material.
1. Copy the field labels exactly. Do not answer from memory or from a colleague’s paraphrase. A request for a legal entity is not the same as a request for a public-facing brand.
2. Name the advertiser precisely. Decide whether the relevant identity is an individual or a business, then record the complete supported name.
3. Assign evidence to each factual answer. Use the authoritative business or identity record that directly addresses the field. Do not use an unrelated record merely because it contains a convenient value.
4. Compare the proposed answers with account-level business information. Flag differences instead of silently choosing one version.
5. Quarantine every unresolved conflict. Move the submission into a pending state until the responsible person confirms which record is authoritative and why.
6. Review and preserve the final package. Save the submitted values, the evidence used, the approver, and the submission date so that you can reconstruct what happened later.
The key control is traceability. Someone reviewing your internal record should be able to move from a Google field to the proposed answer and then to the evidence without filling in a missing step with an assumption.

Resolve mismatches by cause, not convenience

A mismatch tells you that two values differ. It does not tell you which value is correct or whether the difference is harmless. Resolve the cause before deciding what to submit.

Formatting differences

Capitalization, punctuation, abbreviations, unit numbers, and corporate suffixes can create apparent inconsistencies. Compare the precise wording of the field with the precise wording of the relevant record. Do not normalize a value simply because the cleaner version looks more professional. If an authoritative record contains a material error, correct that record through its proper process rather than disguising the conflict in the verification form.

Stale account information

If Google Ads contains an old business detail while your current records support a different value, determine which system needs an authorized update. Do not repeat stale information merely to make the form match the account, because consistency does not make a false answer truthful. Equally, do not claim that an update has occurred until the underlying record actually supports the new information.

Document the old value, the supported current value, who authorized the change, and when the change became valid. That creates a coherent explanation if the discrepancy later needs to be addressed.

Unclear identity, ownership, or authority

Stop the submission when your team cannot agree on which entity is being verified or who is authorized to represent it. Do not solve a structural ambiguity by selecting the most recognizable brand name. Ask the person responsible for corporate or identity records to establish the correct relationship. If ownership or authority is genuinely disputed, obtain appropriate legal advice before making a representation that could affect the account.

The same caution applies to agencies. Managing an advertiser’s campaigns does not automatically make the agency the advertiser for every verification question. Read each field literally, confirm the client’s supported answer, and retain the client’s approval.

Give the submission an owner, a submitter, and an approver

Verification often goes wrong at the handoff. A client supplies a trading name, an account manager copies an older address, and an operations employee submits both without seeing the conflict. Nobody intends to mislead Google, but the final package still contains unsupported information.
- The record owner confirms the authoritative identity and business details. For an agency-managed account, this will usually require input from the advertiser rather than an agency assumption.
- The submitter maps each Google field to the approved value and evidence. This person should record uncertainties instead of resolving them informally.
- The approver compares the completed submission with the evidence as a whole. Approval should cover the exact package being submitted, not an earlier draft.
One person can perform all three functions in a small business, but the passes should remain separate. First establish the records, then complete the form, then review it from the beginning. A second pass is useful because familiarity makes it easy to read what you expected to type rather than what is actually on screen.

After approval, prevent undocumented last-minute substitutions. If a value must change, reopen the check for that field and any related fields. An address change, for example, may affect more than one answer or supporting record. The goal is not bureaucracy; it is one internally consistent and evidentially supported submission.

What to do if you already submitted incorrect information

Do not invent a cleaner explanation after discovering an error. Record the facts while they are still clear: the exact value submitted, the value you now believe is correct, the evidence supporting the correction, the cause of the discrepancy, and the person authorized to confirm it.

If Google provides a correction or response route in the account or enforcement notice, follow that route and answer concisely. Make the correction truthful and evidence-based. Avoid a sequence of speculative changes that produces several incompatible versions of the advertiser’s identity.

If the account has been suspended, follow the instructions in the suspension notice. Campaign downtime can create pressure to improvise, but substituting another unsupported identity or altering records merely to get through verification creates more circumvention risk. When the dispute involves legal ownership, authorization, or conflicting corporate records, involve a qualified professional before responding.

Key takeaways
- Google’s November 2025 policy clarification treats false or misleading advertiser verification information as a potential Circumventing Systems violation.
- The possible consequence is immediate account suspension, so verification should receive the same control as other high-risk account changes.
- Build one canonical record that maps every proposed answer to authoritative evidence.
- Stop when records conflict. Resolve the underlying identity or data problem instead of selecting the value most likely to pass.
- If you discover an error after submission, preserve the facts and use the response route Google provides rather than producing a new unsupported explanation.
Before your next verification request arrives, create the canonical record and assign its owner. Then make verification a controlled submission, not an urgent form-filling task. That small operational change gives your team a defensible answer to the question that matters most: what evidence supported every detail sent to Google?

References
- CrushPress.AI — Google’s Policy Update: Zero Tolerance for False Advertiser Info
November 7, 2025

How to Choose an SEO Expert Witness for a Legal Dispute

Your case may turn on an organic traffic loss, a disputed site migration, an allegation that an agency damaged rankings, or a claim that lost search visibility caused lost revenue. The wrong expert will bring impressive charts. The right one will show what the evidence supports, what it does not support, and where uncertainty remains.

If you are choosing an SEO expert witness, start with the disputed mechanism rather than the most recognizable name. You need someone whose experience fits the actual claim, whose analysis can be reproduced, and whose explanation will remain coherent under cross-examination.

Start with the opinion you need, not the expert’s profile

An SEO expert witness is not simply an experienced marketer. The role requires technical competence, a defensible method, independence, and the ability to explain search systems without turning uncertainty into false certainty.

Before making a shortlist, write the proposed assignment in one paragraph. Identify the disputed event, the relevant period, the alleged consequence, and the opinion the expert may be asked to support. A useful starting formulation is: “Determine whether the identified website changes are consistent with the documented organic visibility loss, while evaluating other plausible causes.”

That formulation is narrower and more defensible than asking whether someone “ruined the SEO.” It also exposes the evidence you will need. A well-scoped SEO engagement commonly separates four layers:

Fact reconstruction: What changed, who authorized it, when it entered production, and what search or analytics signals changed afterward?
Technical interpretation: How could redirects, canonical tags, robots directives, rendering, internal links, metadata, structured data, or server behavior affect discovery and visibility?
Causal analysis: Is the alleged act a credible explanation for the observed change after competing explanations are examined?
Consequence analysis: What can the available search and analytics data establish about visits, leads, transactions, or other outcomes?

Do not let the last layer expand silently into accounting, valuation, or legal conclusions. An SEO specialist may be able to explain how organic visibility connects to recorded sessions and conversions. That does not automatically qualify the same person to calculate legally recoverable damages or interpret the contract. Counsel should allocate each opinion to a properly qualified expert.

Counsel should also decide whether the initial role is consulting, testifying, or potentially both before confidential strategy and work product are shared. Discovery, disclosure, privilege, and admissibility rules depend on the jurisdiction and procedural posture. Do not assume that copying a lawyer on an email protects it; have the lawyer handling the matter establish the engagement and communication protocol.

Match the expert to the mechanism actually in dispute

SEO is broad enough that two credible practitioners can have materially different strengths. You have a genuine field to choose from: 23 SEO and internet-marketing professionals accepting expert-witness work were identified in 2025, with comparison criteria that included experience, credentials, public case outcomes, and other performance dimensions. That breadth makes a directory or reputation-based ranking a starting point, not a substitute for matching expertise to the claim.

For a migration or technical implementation dispute, look for hands-on experience with redirect maps, crawl behavior, canonicalization, indexing controls, rendering, sitemaps, server responses, and deployment validation. Ask the candidate to describe how they would reconstruct the change from configuration files, crawls, logs, tickets, and release records.
For an agency performance or standard-of-care dispute, look for experience evaluating scopes of work, recommendations, approvals, reporting practices, implementation ownership, quality controls, and remediation. The expert must distinguish between advice that was given, work that was approved, and changes that were actually deployed.
For a ranking or algorithm attribution dispute, look for someone who is disciplined about uncertainty. A traffic decline occurring near a public search change does not establish causation by itself. The expert should examine page and query patterns, indexing status, site changes, measurement gaps, demand shifts, and other plausible explanations.
For a lost-traffic or lost-revenue claim, look for strong analytics and measurement experience. The analysis may need to reconcile channel definitions, attribution settings, tracking changes, paid and organic overlap, conversion instrumentation, inventory, pricing, promotions, seasonality, and changes in market demand.
For a reputation or branded-search dispute, look for experience with branded query behavior, result-page composition, content visibility, historical capture, entity confusion, and brand protection. Current search results cannot reliably prove what a user saw during an earlier disputed period.

Ask each candidate which part of the proposed assignment falls outside their expertise. A careful boundary is a positive signal. Someone who claims equal authority over technical crawling, consumer surveys, financial damages, trademark confusion, and legal standards may be describing a résumé rather than a defensible scope.

Vet expertise, witness readiness, and method separately

A strong SEO operator can still be a poor witness, while an experienced witness can be a weak fit for a specialized technical question. Score the candidate in separate categories so that general confidence does not conceal a material gap.

Criterion	Evidence to request	Warning sign
Technical fit	Relevant implementation, diagnostic, analytics, or audit work tied to the disputed mechanism	Broad marketing experience with little evidence of work on the systems at issue
Witness readiness	Specific deposition, hearing, trial, report, rebuttal, or consulting roles, stated accurately	A large engagement count with no explanation of what the candidate actually did
Methodological discipline	Versioned data, documented filters, repeatable calculations, and explicit alternative hypotheses	A conclusion formed before the candidate has identified the required data
Communication	A clear explanation of a technical issue in language a non-specialist can follow	Jargon, analogies that distort the mechanism, or answers that exceed the question
Independence	Willingness to revise or narrow an opinion when contrary evidence appears	Promises about the desired conclusion, admissibility, settlement pressure, or case outcome

During the interview, give every candidate the same short, neutral case summary. Do not disclose which answer the retaining side wants. Then ask:

What precise opinions might fall within your expertise?
What facts and data would you need before reaching any opinion?
Which alternative explanations would you test?
How would you handle missing historical data?
Which tools would you use, and how would you document their settings and limitations?
Which parts of the work would you perform personally?
Can another qualified person reproduce the material calculations from your work papers?
What prior testimony, publications, statements, or business relationships could be used to challenge your independence or consistency?
Are there conflicts involving the parties, counsel, agencies, vendors, or relevant platforms?
What would cause you to change your initial view?

Ask for a current CV and an accurate description of prior expert roles, then let counsel perform the jurisdiction-appropriate record and conflict review. Public case outcomes deserve context: an outcome can depend on evidence, legal rulings, other witnesses, settlement decisions, and issues outside one expert’s control. Treat an unexplained win rate as a marketing claim, not a measure of methodological quality.

Build the evidentiary record before requesting a conclusion

SEO disputes become harder when analysis begins with screenshots, recollections, and exported summaries. Preserve the underlying material first. Do not repair, reconfigure, delete, or “clean up” relevant accounts before counsel has addressed preservation. Those actions can overwrite history and create a second dispute about the reliability of the record.

Have counsel define the question and engagement structure. State the assignment, relevant period, known limits, expected deliverables, and communication rules. The lawyer should make jurisdiction-specific decisions about preservation, privilege, discovery, disclosures, and admissibility.
Preserve native records. Collect read-only originals where possible from Google Search Console, analytics platforms, rank trackers, crawling systems, server logs, content systems, source control, ticketing tools, email, contracts, reports, and relevant vendor accounts. Record who collected each item, when it was collected, the covered period, the account or property, and any filters applied.
Create a unified timeline. Align deployments, redirects, template changes, content removals, tracking edits, approvals, incidents, search visibility changes, conversion changes, promotions, inventory constraints, and other relevant events. Use one stated time zone and retain the original timestamps.
Define every metric. A data dictionary should identify the source, owner, date range, collection method, dimensions, filters, attribution settings, known gaps, and meaning of terms such as click, session, user, lead, conversion, ranking, visibility, and revenue. Similar labels from different systems are not necessarily interchangeable.
Test competing explanations. The expert should write down the plausible causes before selecting among them. Depending on the claim, those may include technical changes, content changes, tracking failures, demand shifts, seasonality, paid-media changes, site outages, inventory, pricing, competitors, indexing issues, and broader search-result changes.
Make the analysis reproducible. Preserve input files, query parameters, filters, scripts, calculations, tool settings, export dates, and working versions. Rank observations should include the recorded date, location, device, query, and measurement method because search results can vary across those conditions.
Challenge each conclusion before reporting it. For every chart and opinion, ask what evidence contradicts it, what assumptions it requires, whether the time sequence fits the proposed mechanism, and how the result changes when questionable inputs are removed. Counsel can then prepare the required report or disclosure without asking the expert to conceal genuine limitations.

Use screenshots to illustrate preserved evidence, not as a replacement for it. A screenshot may omit the property, filter, comparison period, time zone, sampling condition, or surrounding interface needed to interpret the number. Likewise, a present-day crawl or search result can show current conditions but cannot, by itself, establish historical conditions.

Causation deserves particular discipline. A sequence in which an SEO change occurs and traffic later falls is relevant, but sequence alone does not show that the change produced the entire loss. A defensible opinion explains the mechanism, checks whether affected pages and queries follow that mechanism, evaluates competing causes, and states what cannot be resolved from the available record.

Key takeaways

Define the disputed event, period, consequence, and proposed opinion before searching for an expert.
Choose for direct fit with the mechanism at issue: technical implementation, agency conduct, ranking attribution, analytics, revenue linkage, or reputation.
Evaluate technical expertise, witness readiness, communication, method, and independence as separate criteria.
Reject guarantees and conclusions offered before the candidate has identified the necessary evidence and alternative explanations.
Preserve native data and historical configurations before anyone repairs the site, changes account settings, or relies on present-day screenshots.
Have counsel control the engagement and make jurisdiction-specific decisions about privilege, discovery, disclosure, admissibility, and the division of opinions among experts.

Your next step is simple: write the one-paragraph assignment, list the records that can prove or disprove it, and use the same evidence-focused questions with every candidate. The best SEO expert witness for your matter is the person who can narrow the claim to what the record can actually establish.

References

November 5, 2025

How to Choose a US SEO Agency by Specialization and Fit

You’re not trying to hire a generically ‘good’ SEO agency. You’re trying to find a partner that can solve your particular search problem inside your industry’s constraints, your technology, and your approval process. An agency can know the vocabulary of your market and still lack the technical depth, content operation, or implementation discipline your program needs.

The fastest way to improve your shortlist is to stop treating specialization as a single label. Match each candidate against three things: the market it understands, the problem it is equipped to solve, and the environment in which it must deliver. That turns an agency search from a logo comparison into a decision you can defend.

Key takeaways

Choose an agency around your hardest constraint, not the breadth of its service menu.
Separate industry expertise from technical, content, local, ecommerce, authority-building, AEO, and GEO expertise. You may need more than one dimension.
Ask for evidence that connects context, diagnosis, action, implementation, and outcome. A client logo or traffic chart alone does not prove fit.
Treat AI search visibility as an extension of strong content, entity clarity, structured data, authority, and measurement processes, not as an isolated campaign.
Settle implementation ownership, approvals, access, measurement, and exit terms before work begins. Strategy without an accountable delivery path is only a document.

Define the specialization your search problem actually needs

Three specialists examine technical connections, content clusters, and discovery signals around a shared digital business ecosystem.

The phrase ‘industry specialist’ collapses several different capabilities into one claim. A useful agency brief separates them. Start by identifying the failure that would be most expensive: misunderstanding the customer, mishandling a regulated claim, missing a technical dependency, producing content that cannot be approved, or delivering recommendations your team cannot implement.

The US market is broad enough to support specialist leaders across 10 different niches. That makes specialization a practical filter, but it does not tell you which kind should lead your decision.

Vertical specialization: understanding the market

A vertical specialist should understand how buyers describe the problem, which claims require care, where subject-matter expertise comes from, and what makes a page trustworthy in that market. It should also know that two companies in the same broad sector can have very different search journeys.

Do not stop at ‘Have you worked in our industry?’ Ask whether the agency has worked with your type of customer, offer, sales motion, and review environment. A financial technology platform, a wealth manager, an insurer, and a retail bank all sit near the same industry label, but their audiences, conversion paths, content risks, and internal stakeholders are not interchangeable.

Problem specialization: solving the actual bottleneck

Your vertical may not be the hardest part of the assignment. A site with uncontrolled faceted navigation may need ecommerce and technical depth. A multi-location organization may need local data governance. A B2B company with strong expertise but weak search coverage may need a content operation that can extract knowledge from busy specialists. A replatforming project may make migration planning more important than prior work in the sector.

Name the primary problem before you review agency positioning. Otherwise, every candidate can appear relevant by repeating your industry name while avoiding the capability that will determine whether the engagement works.

Operating-model specialization: delivering inside your organization

Execution conditions are a third form of specialization. Enterprise governance, founder-led decision-making, distributed regional teams, regulated review, and a small in-house marketing department each require different workflows. An agency that performs well when it controls publishing may struggle when every change crosses product, engineering, brand, legal, and compliance teams.

Scalability is not simply headcount. It is the ability to maintain decision quality, review standards, ownership, and reporting as the number of pages, stakeholders, markets, or workstreams grows. Ask how the operating model changes when scope expands, not merely whether more people can be assigned.

Your main situation	Specialization to prioritize	Evidence to request
Financial or another regulated, high-trust offer	Vertical SEO with compliance-aware content operations	A workflow showing how subject-matter input, claim review, revision, approval, and publication are handled without losing search intent
Complex ecommerce catalog	Ecommerce and technical SEO	Work involving category architecture, faceted navigation, indexation controls, templates, internal linking, and coordination with merchandising
Multi-location organization	Local and multi-location SEO	Location-page governance, business-data ownership, duplication controls, and a process for changes across locations
Large site or platform change	Enterprise technical SEO or migration expertise	Prelaunch inventories, redirect and canonical decisions, quality assurance, monitoring, and clear handoffs to engineering
B2B offer with specialist buyers	B2B content strategy and subject-matter extraction	A path from buyer questions and expert input to approved pages, internal distribution, and qualified-demand measurement
Weak authority or brand recognition	Link earning, digital PR, and authority development	Asset selection, link-quality standards, outreach governance, reputational safeguards, and the agency’s exact role in earned results
Low visibility in AI-generated answers	AEO and GEO supported by core SEO	A query framework, source-page plan, entity and schema work, citation analysis, and an evaluation method that acknowledges output variability

Use the table as a starting point, not a set of exclusive categories. Your primary specialization should address the constraint most likely to stop progress. Secondary specializations should cover the dependencies. Write your requirement in one sentence: ‘We need a US agency with [primary specialization], experience in [operating environment], capable of [business outcome], while working within [critical constraint].’ If you cannot complete that sentence, the shortlist is premature.

Demand proof of fit, not proof of proximity

Specialization is credible only when it changes how an agency diagnoses and executes the work. For financial SEO, a sensible initial screen includes sector expertise, established client work, and the ability to scale. Those criteria narrow the field, but each still needs context before it can support a buying decision.

A recognizable client name proves that some relationship existed. It does not tell you whether the agency owned strategy, wrote content, fixed templates, supported a migration, provided a narrow audit, or inherited growth created by another channel. Ask every candidate to explain its remit and the work performed by the client or other vendors.

The most useful case evidence follows a chain you can inspect:

Context: the business model, audience, search environment, site type, and relevant starting condition.
Constraint: the technical, editorial, regulatory, organizational, or competitive issue that limited progress.
Diagnosis: why the agency selected that issue instead of the other plausible priorities.
Decision: what it chose to change, what it deliberately left alone, and what tradeoff it accepted.
Implementation: who performed the work, which dependencies had to be cleared, and how quality was checked.
Evidence: the observable change and the business measure used to judge whether it mattered.
Transferability: which parts of the approach apply to your situation and which depended on conditions you do not share.

Confidentiality may prevent an agency from disclosing a client name or sensitive performance data. It should not prevent the team from explaining its reasoning, workflow, ownership, and deliverables in a sanitized example. If all detail disappears behind confidentiality, mark the capability as unproven rather than assuming it exists.

Use questions that force the pitch away from rehearsed credentials:

Which part of our brief would make you change your usual playbook?
What information would you need before recommending a strategy?
Which work would you advise us not to fund yet, and why?
What would your team own, and what would remain with our content, engineering, legal, compliance, or product teams?
Show us a deliverable similar to the one we would receive. What decision is it meant to unlock?
Describe a recommendation that could not be implemented as planned. How did the team adapt?
What evidence would cause you to change the initial strategy?

For regulated financial content, an SEO agency can organize expert input, search intent, editorial controls, and the path to publication. It should not decide whether a financial claim is legally permissible. Keep final approval with qualified legal or compliance owners, and make that boundary explicit in the workflow and contract.

Test scalability with the same discipline. Ask who joins when technical, content, local, or AI-search work expands; how quality reviews are assigned; what happens if a key person becomes unavailable; and where client-side bottlenecks typically appear. You are looking for a repeatable operating system, not a promise that resources will somehow be found.

Test SEO, AEO, and GEO capability without buying jargon

Modern search terminology gives weak agencies several places to hide. A long list of services can mask shallow technical work. A polished AI-search pitch can mask weak content and entity foundations. Ask candidates to connect every label to a deliverable, an implementation owner, an observable signal, and a business decision.

Core SEO must still work as an operating system

A credible plan should connect discovery, indexation, page architecture, internal linking, templates, content quality, authority, and conversion paths. The precise emphasis depends on the site, but the agency should be able to show how its technical and editorial decisions reinforce each other.

Ask for the first diagnostic questions rather than a premature answer. What evidence would distinguish an indexation issue from a demand issue? How would the team determine whether a content gap, a page-quality problem, an internal-linking problem, or weak authority is limiting a topic? Which recommendations require engineering, and which can be executed by the content team? A specialist should expose the decision tree before prescribing the work.

AEO and GEO should extend the same foundations

AEO and GEO overlap, and agencies do not always use the labels consistently. The useful distinction is operational. Answer engine optimization focuses on making accurate answers easy to identify, extract, and support. Generative engine optimization focuses on improving how clearly a brand, entity, and body of evidence can be understood and selected within generated responses. Neither replaces technical SEO or helpful source content.

A substantive AEO or GEO plan may include:

A defined set of audience questions connected to search intent, business relevance, and suitable source pages.
Content that answers the question directly while preserving the evidence, qualifications, and context needed for trust.
Clear entity naming and consistent facts across important owned pages and profiles.
Structured data that describes visible, supported content instead of making claims the page cannot substantiate.
Primary evidence, expert attribution, definitions, and citations where the subject requires them.
Analysis of which brands and domains appear for the target questions and why those pages may be usable as sources.
A repeatable evaluation protocol for generated answers, cited domains, destination pages, and changes over time.

Schema markup can help machines interpret explicit page content. It cannot make an unsupported claim true, repair a weak page, or force an independent search or answer system to cite the site. Treat guaranteed AI citations, recommendations, or placements as a disqualifying claim. An agency can improve clarity, eligibility, and evidence quality; it does not control the generated answer.

Measurement must preserve the conditions of the observation

Generated results can vary with the wording of a question, the answer surface or model, the date, the locale, and account context. A useful monitoring method records those conditions alongside the response, cited domains, linked pages, brand treatment, and any referral or conversion evidence that is available. Otherwise, a reported visibility change may simply reflect a changed test.

Ask the agency to separate different layers of performance:

Technical eligibility: whether important pages can be discovered, processed, and interpreted as intended.
Search visibility: whether the site appears for relevant non-branded and branded searches.
Answer visibility: whether the brand or its pages appear, are cited, or are represented accurately for the monitored questions.
Engagement: whether people who reach the site continue to useful pages or actions.
Commercial value: whether the work contributes to qualified leads, sales, revenue, retention, or another agreed business outcome.

A single composite AI visibility score can be a reporting convenience, but it is not self-explanatory. Require the query set, scoring method, tested surfaces, observation conditions, and underlying examples. The score should help you investigate performance, not prevent you from seeing how it was produced.

Run a selection process that exposes fit before the contract

Client and agency teams collaborate on a tabletop search problem using blank cards, website blocks, and branching pathways.

A strong procurement process gives every candidate the same problem to solve and the same evidence to work from. It also protects you from being swayed by the most polished presentation rather than the most appropriate delivery model.

Write the decision brief. State the business model, audience, geographic scope, priority conversions, site or platform conditions, planned changes, internal resources, approval requirements, available performance evidence, and constraints that cannot be changed. Identify the primary and secondary specializations you need.
Build the shortlist around those requirements. Record why each agency belongs. ‘Well known’ is not a specialization. Note possible client conflicts, geographic limits, platform dependencies, and any capability that remains unverified.
Give candidates the same scoped scenario. Use a redacted data pack or a safe sample rather than production credentials or unnecessary confidential information. Ask for diagnostic reasoning, likely priorities, dependencies, and the evidence needed to confirm or reject each hypothesis.
Inspect the evidence chain. Review case work, sample deliverables, role clarity, and implementation detail. Where appropriate and permitted, verify the agency’s role with client references rather than asking only whether the client was satisfied.
Meet the delivery team. Confirm who will lead strategy, perform technical analysis, create or edit content, implement schema, manage outreach, analyze AI visibility, and communicate with your stakeholders. Clarify when specialists join and whether named people are committed or illustrative.
Normalize the proposals. Put every scope into the same columns: agency-owned work, client-owned work, third-party work, dependencies, deliverable acceptance criteria, exclusions, and additional costs. Two similar retainers may cover materially different amounts of implementation.
Score the unresolved risk. Mark specialization fit, diagnostic quality, implementation realism, measurement, team fit, commercial clarity, and governance as strong, acceptable, or unproven. Weight the areas that can actually block your program.

A paid, tightly scoped diagnostic can reveal more than an expansive speculative pitch when the decision is close. Define what the diagnostic must produce, who owns the output, what access is permitted, and whether either party is obligated to continue. Do not let a trial quietly become an open-ended engagement.

Put implementation and risk ownership into the agreement

The statement of work should be specific enough that your team can tell whether a deliverable is finished and what happens next. Resolve these points before kickoff:

Scope and acceptance: define the expected artifact, level of analysis, revision process, and acceptance owner for each deliverable.
Implementation: state who changes templates, publishes content, adds structured data, fixes defects, manages redirects, performs outreach, and validates completed work.
Team and continuity: identify key roles, escalation paths, quality reviewers, and the process for replacing personnel.
Access and security: use approved accounts and least-privilege access. Define who authorizes permissions, handles sensitive data, and removes access at the end.
Editorial and compliance approval: specify which material requires subject-matter, brand, legal, or compliance review and who has final authority.
Measurement: document the baseline, data inputs, attribution limits, reporting definitions, observation conditions, and decisions each report should support.
Change control: define how new requests, site changes, delayed dependencies, and priority shifts affect scope and fees.
Conflicts and exclusivity: make any sector or competitor restrictions precise rather than relying on a broad promise.
Ownership and exit: settle ownership of content, research, schema, accounts, dashboards, datasets, documentation, and in-progress work. Require an orderly handoff and access removal process.

Contract terms involving liability, confidentiality, data processing, intellectual property, exclusivity, and termination can create legal and financial exposure. Have qualified counsel review those provisions for your situation. The SEO team should help define operational responsibilities, but it should not substitute for legal advice.

Make the opening phase produce evidence and shipped work

The opening phase should do more than produce a long audit. It should establish a trustworthy baseline, validate the highest-priority constraints, assign implementation owners, move a deliberately limited queue of changes into production, and create a review loop that updates the roadmap as evidence arrives.

Watch for warning signs before the relationship becomes difficult to unwind:

Guaranteed rankings, citations, recommendations, or AI placements.
A confident diagnosis made before the agency has requested the evidence needed to distinguish competing causes.
Case results without the original mandate, implementation role, constraint, or measurement definition.
An AI-search package disconnected from technical SEO, source content, entity clarity, authority, and business measurement.
A strategy that ends with recommendations but does not assign an implementation owner.
Dependence on a senior salesperson who will not participate in delivery, paired with no access to the actual team.
A plan to publish regulated or high-stakes claims without qualified review.
Reporting built around output volume while qualified demand and commercial outcomes remain undefined.

Take your current shortlist and write each agency’s name beside the constraint it is supposed to solve. Then add the evidence that proves it can solve that constraint in your operating environment. Remove any candidate for which you cannot complete both lines. Send the remaining agencies the same decision brief, and let the quality of their diagnosis, proof, and delivery model decide the next step.

References

November 5, 2025

Tag: Compliance

Google Ads Image Carousels and Phone Number Fraud Controls

Key takeaways

Design the carousel around a visual decision

Write a four-part creative brief

Test a decision, not a decoration

Audit the phone number as a campaign identity

Separate policy eligibility from creative performance

Stage one: prove that the campaign can serve

Stage two: prove that the creative earns its place

References

Google Advertiser Verification Policy: An Accuracy Checklist

Why a verification mismatch is now a suspension risk

Define the advertiser before completing individual fields

Resolve mismatches by cause, not convenience

Formatting differences

Stale account information

Unclear identity, ownership, or authority

Give the submission an owner, a submitter, and an approver

What to do if you already submitted incorrect information

Key takeaways

References

How to Choose an SEO Expert Witness for a Legal Dispute

Start with the opinion you need, not the expert’s profile

Match the expert to the mechanism actually in dispute

Vet expertise, witness readiness, and method separately

Build the evidentiary record before requesting a conclusion

Key takeaways

References

How to Choose a US SEO Agency by Specialization and Fit

Key takeaways

Define the specialization your search problem actually needs

Vertical specialization: understanding the market

Problem specialization: solving the actual bottleneck

Operating-model specialization: delivering inside your organization

Demand proof of fit, not proof of proximity

Test SEO, AEO, and GEO capability without buying jargon

Core SEO must still work as an operating system

AEO and GEO should extend the same foundations

Measurement must preserve the conditions of the observation

Run a selection process that exposes fit before the contract

Put implementation and risk ownership into the agreement

Make the opening phase produce evidence and shipped work

References