Month: August 2026

Link Building Strategy for 2027: Earn Authority, Not Volume

If your link building plan still begins with a target number of backlinks, 2027 is going to be expensive. You may fill a report with placements while earning little attention, trust, referral traffic, or visibility in the searches that influence buyers.

A stronger plan starts with a different question: what can your brand publish, reveal, or explain that an editor would independently choose to reference? That shift turns link building from an inventory exercise into a disciplined combination of content strategy, digital PR, audience research, and relationship building.

Key takeaways

Treat a backlink as one possible result of earning editorial attention, alongside brand mentions, referral traffic, social discovery, journalist relationships, and leads.
Build campaigns around original evidence, useful expertise, or a timely consequence. A company announcement is not automatically a story.
Evaluate publications by topical relevance, audience fit, editorial standards, and narrative fit. A third-party authority score cannot replace those checks.
Use competitor backlinks to find publications and recurring interests, then develop an angle competitors cannot reproduce.
Use AI to accelerate research, organization, and controlled drafting. Keep story selection, factual review, personalization, and final approval under human judgment.
Measure business and editorial outcomes separately from link counts. A placement should have a credible route to attention, trust, discovery, or demand.

Set the outcome before choosing the link tactic

Links still matter, but a link is not the whole return. A genuinely earned placement can expose your brand to a publication’s audience, create a relevant brand mention, attract referral visits, support social discovery, and associate your expertise with a subject. That is why earned placements can produce value beyond the hyperlink itself.

Choose a primary campaign outcome before you create anything. If the goal is authority in a category, you need relevant editorial association. If the goal is qualified referral traffic, you need a publication read by potential buyers and a natural reason for them to continue to your site. If the goal is leads, the referenced page must help a visitor take the next step. If the goal is AI-search visibility, you need clear, public, topical evidence about your brand, while recognizing that no individual link can guarantee a citation in an AI-generated answer.

This distinction changes prospecting. A site with an impressive authority metric but no real editorial process, topical connection, or relevant readership is not equivalent to a respected publication that covers the problem you solve. The first may add a row to a spreadsheet. The second can make your brand easier for people and systems to understand in context.

Decision factor	Proceed when	Reject or revise when
Topical relevance	The publication regularly covers the question your campaign answers.	The only attraction is a high third-party domain metric.
Audience fit	Its readers include people who influence, use, or recommend your category.	You cannot explain why its audience would care.
Editorial credibility	Editors select, shape, and verify what appears.	Placement is effectively for sale and editorial scrutiny is absent.
Story fit	Your evidence or expertise advances an existing beat or timely conversation.	The pitch merely announces that your company did something.
Compounding value	The coverage can earn referrals, mentions, relationships, reuse, or demand as well as a link.	The placement has no plausible value after the backlink is logged.

Write these criteria into the campaign brief. They give your team permission to decline an irrelevant placement even when it looks attractive in a link report.

Build an asset around a story someone else can use

The hardest part of link building is not sending the email. It is creating a defensible reason for the email to exist.

A new hire, product launch, funding event, or executive profile is an announcement until you connect it to a consequence that matters outside your company. The usable story might be a problem the product exposes, an unexpected change visible in company data, a practical answer from a qualified expert, or a timely pattern affecting the publication’s readers. Product praise is not evidence, and an executive biography is not a reader benefit.

Apply the story test before producing the asset

Reader value: What can the publication’s audience understand, decide, or do after seeing this?
Novelty: What does your brand know, observe, or possess that is not already available in interchangeable articles?
Proof: Can an editor inspect the underlying data, method, example, or expert reasoning?
Timing: Why is this useful in the current conversation rather than at an arbitrary publishing date?
Editorial independence: Would the central insight remain interesting if the company description were reduced to a short attribution?
Reference value: Is there a specific chart, finding, explanation, tool, or page worth citing?

If the idea fails several of these checks, polishing the pitch will not rescue it. Improve the evidence or choose a more useful angle before outreach begins.

Originality does not require spectacle. Your strongest inputs are often the ones already inside the organization: proprietary data, recurring customer questions, specialist knowledge, product usage patterns, or a company decision that reveals a broader market change. The important condition is that you can support the claim and explain why it matters to someone who is not buying from you.

Run a deliberate production sequence

Write the reader’s question in plain language.
Identify the evidence or expertise that can answer it.
Check what has already been published so you do not recreate a familiar asset with a new headline.
Define the finding, consequence, and appropriate limitations before drafting promotional copy.
Create the referenceable page, including enough context for an editor to verify and accurately describe the point.
Develop distinct pitch angles for the relevant publication types and beats.
Prepare a concise fact sheet so every pitch, interview, social post, and follow-up uses consistent claims.

Do not manufacture overlapping assets merely to maintain a publishing cadence. Repeating the same idea across multiple weak pages divides attention and leaves journalists with no clear canonical resource to cite. A durable asset that can be refreshed when new evidence or a relevant news event appears is usually more useful than a queue of near-duplicates.

Schema markup can clarify the entity, author, dates, and content type represented on your own page. It cannot turn recycled material into original evidence or convert a purchased placement into an editorial endorsement. Structured data supports clarity; the story still has to earn attention.

Prospect for editorial fit, then pitch with restraint

Competitor backlink profiles remain useful, but treat them as maps rather than instructions. They can reveal publications covering your market, journalists with relevant beats, recurring story formats, and subjects that attract citations. They cannot give you a distinctive reason to be covered.

For every promising competitor placement, ask what was actually newsworthy. Then look for the missing question, newer evidence, stronger method, different audience consequence, or expert perspective your organization can credibly supply. The direction is supported by a reported survey in which 66.6% of SEO professionals favored finding unique opportunities over replicating competitors’ backlink profiles.

Your prospect list should record why each contact belongs on it. Capture the journalist’s beat, relevant previous coverage, the audience connection, the angle you intend to offer, and the evidence that makes the pitch credible. If the only personalization available is a first name and publication name, the prospecting is not finished.

Put AI behind an editorial gate

AI can help cluster coverage themes, organize prospect notes, extract common questions, compare angle variants, and turn an approved brief into draft outreach. That speed is useful only after the strategy is sound.

Do not let an automated system invent personalization, infer facts about a journalist, or send unreviewed pitches at scale. Inboxes already contain large volumes of similar machine-written outreach. Increasing output without improving relevance scales rejection and can damage the relationships you need for future campaigns.

Give the system an approved evidence pack rather than unrestricted permission to create claims.
Require every draft to state the finding and reader consequence before mentioning the company.
Remove empty compliments, generic trend language, exaggerated adjectives, and invented familiarity.
Verify names, beats, publication fit, claims, and links before sending.
Keep the final decision with a person who can judge whether the pitch deserves the recipient’s attention.

A strong pitch makes the editorial decision easy to evaluate. Lead with the relevant finding or consequence. Explain why that contact’s readers are affected. State what evidence, expert access, or usable material is available. Then stop. A long company history, feature list, or generic offer to collaborate forces the recipient to search for the story you should already have identified.

Relationship building happens through repeated relevance, not repeated reminders. Record useful feedback, respect a clear rejection, and return only when you have a genuinely suitable angle. A journalist who trusts your accuracy and restraint is a more durable asset than a large list of contacts receiving interchangeable messages.

Measure whether the campaign earned real authority

A raw link count cannot tell you whether a campaign worked. It treats an editorial citation read by your market as equivalent to a placement on a site created to sell links. Your reporting should preserve the difference.

Record the immediate editorial result: publication, topical context, linked or unlinked brand mention, destination page, publication audience fit, and whether the placement produced referral activity. Then track the outcomes tied to the campaign brief, such as qualified visits, leads, branded discovery, subsequent coverage, social distribution, or reuse of the asset.

For AI-search monitoring, use a stable set of relevant questions and record whether your brand, domain, or campaign evidence appears. Treat movement as a visibility observation, not proof that a particular backlink caused an answer to change. AI outputs vary, and an isolated appearance is not a reliable attribution model.

Also measure what the team learned. Note which angles earned replies, which evidence editors questioned, which publications produced useful audiences, and which relationships opened a credible path to later coverage. Feed those observations into the next campaign. The value of disciplined digital PR compounds partly because your team stops repeating weak ideas and begins recognizing the structures that work for its market.

Use clear stop and continue rules

Continue: The asset remains accurate, distinctive, and useful, and new events create legitimate reasons to revisit it.
Revise: Well-matched contacts understand the topic but consistently cannot see the finding, consequence, or evidence.
Consolidate: Multiple campaign pages compete to explain the same idea and none is the obvious reference. Preserve valuable URLs and existing search equity when planning any consolidation.
Stop: The tactic depends on undisclosed purchasing, fabricated authority, irrelevant placements, or volume that the team cannot review responsibly.

Purchased links can create impressive-looking metrics while providing no genuine audience, editorial judgment, or relationship. Sites with backlink profiles dominated by purchased placements were among those reported as hardest hit during the second wave of Google’s March 2026 spam update. Even before algorithmic risk enters the calculation, a placement with no reader or editorial value is a poor use of budget.

Start your 2027 plan with the market question your organization is best equipped to answer. Build the most defensible version of that answer, choose publications whose readers genuinely need it, and give editors a precise reason to reference it. When the story, evidence, audience, and outreach align, the link becomes evidence of authority rather than a substitute for it.

References

Search Engine Land – Link building in 2027: 13 ways to win or fail

August 28, 2026

Google’s EEA Site Reputation Abuse Change: An SEO Plan

If your site attracts searchers inside and outside the European Economic Area, one site reputation abuse notice can now produce two different visibility outcomes. From August 30, 2026, the affected section can remain visible to EEA searchers while losing placement elsewhere.

That isn’t an amnesty for parasite SEO. It is a regional change to the effect of one type of manual action. You still need to audit the flagged section, separate regional performance in your reporting, and fix the underlying publishing model if you want durable visibility.

Key takeaways

From August 30, 2026, a site reputation abuse manual action will not directly affect results shown to searchers in the EEA.
The same action can still reduce visibility for the affected portion of the site when people search from outside the EEA.
The searcher’s location determines which treatment applies. The site owner’s address, company location, hosting region, or domain extension is not the deciding distinction described by the change.
Within the EEA, Google may separate the third-party section from the host site in its systems so that the section eventually ranks on its own merits.
Search Console notices, reconsideration requests, broader spam enforcement, and the business risk of relying on borrowed domain authority all remain relevant.

One manual action now has two regional outcomes

Site reputation abuse generally refers to third-party material placed on an established site to exploit the host’s ranking reputation. The obvious risk pattern is deceptive pay-to-play publishing: an outside party gains access to a trusted domain, while the resulting pages compete with an authority they may not have earned independently.

The August change is narrower than the phrase “Google is ending site reputation abuse enforcement in Europe” would imply. It changes how a manual action affects results for a particular audience. It does not abolish the policy, prevent notices from being issued, or suspend Google’s other spam systems in the EEA.

Question	Searchers inside the EEA	Searchers outside the EEA
Does the site reputation abuse manual action directly affect the result?	No	Yes, for the affected portion of the site
Is the rest of the site directly included in that manual action?	The manual-action impact does not apply	No; the action applies to the affected portion
Can the affected section still lose the host site’s ranking advantage?	Potentially. Google may separate it in its systems and assess it independently over time	The manual action can directly affect its placement
Can the site owner still receive a Search Console notice?	Yes	Yes

The location test is about the person searching. A publisher based in the EEA can still be affected when its pages are shown to users elsewhere. Likewise, an operator outside the EEA can receive the EEA treatment for searches originating within the region. Treat this as an audience-level rule, not a headquarters-level exemption.

There is also an important difference between avoiding a direct manual-action effect and retaining the host domain’s authority. In the EEA, Google may separate the implicated section in its systems so that it ranks independently from the rest of the site. If that happens, the section should not be assumed to keep benefiting from the reputation that made the arrangement attractive. It could retain, gain, or lose visibility according to how it performs when assessed more independently; no guaranteed outcome or fixed separation timetable has been given.

The practical conclusion is simple: an EEA traffic line that remains stable does not prove that the publishing model is safe. It may only show that the direct manual-action effect is not being applied to that audience.

Audit the publishing model, not just the flagged URLs

A page-by-page cleanup is too narrow if the commercial arrangement keeps producing the same kind of content. Your audit needs to connect URLs to ownership, editorial control, payment, and audience. Use the following sequence.

Inventory third-party sections by template and directory. Include sponsored areas, partner publishing programs, white-labelled experiences, affiliate-led sections, and any other URL group substantially supplied or operated by an outside party. Third-party involvement alone does not establish abuse; the inventory tells you where to investigate.
Record who actually operates each section. Note who selects topics, produces the material, approves publication, handles corrections, and controls the user experience. A host logo or final approval checkbox can hide the fact that the outside party is making every meaningful decision.
Document the value exchange. Identify whether access, placement, leads, sales, or rankings are tied to payment or another commercial benefit. This is where a seemingly ordinary content partnership can reveal a pay-to-play ranking strategy.
Test the role of the host’s reputation. Ask whether the section has a credible reason to live on this domain beyond gaining its authority and distribution. If the business case collapses without the ranking advantage, treat that as a serious warning.
Map the section’s audience by region. Establish how much organic demand comes from the EEA and how much comes from elsewhere. A globally viewed page can have a manual action whose visible effect appears only in the non-EEA segment.
Choose a section-level response. Depending on what the audit finds, that may mean ending the arrangement, removing affected material, changing who controls publication, or rebuilding the section around genuine first-party editorial responsibility. A new folder name by itself does not address an unchanged publishing model.

Do not convert those questions into a superficial compliance form. The point is to identify whether an outside party is borrowing the site’s reputation while the host contributes little beyond access to the domain. Evidence of real editorial work should appear in the workflow: named decision-makers, substantive review, correction ownership, and a defensible reason the content belongs with the site’s primary purpose.

Be equally careful not to classify every contributor, syndication agreement, or commercial relationship as abuse. Start with the mechanism. The concern is the use of third-party content and established site authority as a ranking shortcut, especially in deceptive pay-to-play arrangements. Evaluate the whole arrangement before making removal decisions that could affect revenue, contractual obligations, or useful content.

Measure EEA and non-EEA visibility separately

A global organic-traffic total will conceal the effect you are trying to diagnose. One region can improve while another declines, leaving the combined line looking deceptively calm. Build the regional split before you need it.

Set up a monitoring view that exposes the difference

Annotate August 30, 2026. Use the effective date as a reporting marker, not as proof that every later movement was caused by the policy change.
Create EEA and non-EEA country groups. Apply the same grouping consistently in Search Console exports, analytics, rank tracking, and internal reports.
Split the affected section from the rest of the domain. Track its directories, page templates, or URL patterns separately. Domain-wide averages are not a reliable proxy for a section-specific action.
Compare page and query groups. Look for the same affected URLs losing impressions or positions outside the EEA while behaving differently within it.
Keep manual and system-level effects distinct. A change outside the EEA may align with the direct action. A gradual movement inside the EEA may be consistent with independent section assessment, but timing alone cannot prove the cause.
Preserve the notice and remediation timeline. Record when the action appeared, which section it named, what changed, and when a reconsideration request was submitted. That chronology is more useful than a screenshot of total traffic.

Use annotations and segmented comparisons to form a diagnosis, not to manufacture certainty. The disclosed treatment says separation can happen “over time”; it does not provide a fixed number of days or a guaranteed ranking pattern. Core updates, demand changes, technical faults, and ordinary competition can still move the same metrics.

Respond to a Search Console notice even if EEA traffic holds

Sites can continue receiving site reputation abuse notifications in Search Console, including sites based in the EEA. Ignoring one because local traffic looks unchanged leaves non-EEA visibility exposed and does nothing to strengthen a section that may be assessed independently.

Read the notice closely and identify the exact portion of the site it covers.
Match that scope to your third-party content inventory. Check sibling pages and templates that use the same operating model, not only the example URLs you noticed first.
Decide whether the action appears mistaken or whether the underlying arrangement needs correction. Preserve the facts supporting that decision.
Complete the remediation across the relevant section before requesting review. Partial changes make it harder to show that the underlying pattern has ended.
Submit a reconsideration request if you believe the action was erroneous or after the issue has been corrected. Eligible sites may also have access to mediation following the reconsideration process.
Continue monitoring both regional groups. Removal of the action and recovery of every previous ranking are not the same claim, especially where a section may be evaluated independently.

Build sections that do not depend on borrowed authority

The regional enforcement split changes the immediate consequence, but it does not improve a weak content operation. The safer strategic test is whether the section deserves to exist and compete when detached from the host domain’s accumulated reputation.

Use these governance questions before approving a new partnership or renewing an existing one:

Would you publish this material if it brought no shortcut to search visibility?
Does it serve the same audience and purpose as the site’s first-party content?
Can your editorial team verify claims, reject topics, require changes, and correct errors?
Is the commercial relationship clear enough for internal reviewers to understand why the section exists?
Would the pages remain useful if users and search systems assessed them without the halo of the host brand?
Can one accountable owner explain the section’s editorial, commercial, technical, and search risks?

These are governance checks, not a substitute for Google’s policy language or a promise of compliance. Their value is that they expose the business dependency behind parasite SEO. A section built primarily to rent domain authority remains fragile even where a regional manual action does not directly suppress it.

Before your next search performance review, add two rows to the report: affected-section visibility inside the EEA and the same visibility outside it. Then assign an owner to every third-party URL group. That small change will tell you whether you are looking at a genuine recovery, a regional enforcement difference, or a publishing model that still needs to be rebuilt.

References

Search Engine Land — Google won’t respect manual actions for site reputation abuse in European Economic Area

August 28, 2026

Leading RevOps Firms: How to Choose a Fractional Agency

You are not buying RevOps in the abstract. You are deciding whether an outside team can repair your revenue engine without slowing sales, damaging CRM data, or leaving you with an expensive system nobody internally knows how to run.

The difficult part is that fractional leadership, managed operations, CRM implementation, enablement, and AI automation are often sold under the same label. The right choice depends less on which firm tops a general leaderboard and more on the work you need someone to own. This guide helps you identify that work, match it to leading RevOps firms, and test whether a candidate can deliver it.

Key takeaways

Choose the engagement model before the agency. Embedded fractional ownership, managed RevOps, project implementation, and coaching solve different problems.
Match lifecycle breadth to the actual break. A problem spanning marketing, sales, onboarding, retention, and expansion needs broader coverage than a contained CRM or outbound project.
Do not mistake a long platform list for operational depth. Test the candidate against a real workflow, data model, integration, or handoff from your environment.
Make every AI claim concrete. Require a named workflow, defined data access, approval rules, evaluation criteria, logs, failure handling, and a human owner.
Replace generic ranking weights with your own priorities. Published 2026 methodologies give substantially different weight to leadership, platforms, AI implementation, and lifecycle scope.
Treat recognizable client logos as context, not proof of fit. Even the ranking methodologies used for this shortlist assigned notable clients only 5% of the total score.

Choose the RevOps engagement model before the firm

A leadership team compares three visual pathways representing fractional leadership, managed operations, and technical implementation services.

Fractional describes how you access leadership or operating capacity. It does not guarantee that a senior operator will be embedded in your team, that the agency will configure systems, or that it will cover the complete customer lifecycle. Confirm the operating model in the contract rather than relying on the label.

Embedded fractional ownership: Choose this when no internal leader owns the revenue system across functions. The outside operator should make decisions, coordinate stakeholders, prioritize work, and remain accountable for implementation rather than merely recommend changes.
Managed RevOps or RevOps as a Service: Choose this when you have an ongoing queue of administration, reporting, automation, data, and process work but do not want to assemble an internal team. The central buying question is how strategic decisions and recurring execution are divided.
Project-based specialist: Choose this for a bounded migration, CRM rebuild, routing redesign, CPQ implementation, outbound system, or integration. A contained scope should have explicit deliverables, acceptance tests, change controls, and a handoff owner.
Coaching, methodology, or enablement: Choose this when your internal team can implement but needs a common sales process, operating language, management cadence, or training system. Do not buy advisory work if your real constraint is a lack of hands-on capacity.

Map the failure before contacting vendors. Trace the customer path from acquisition through qualification, opportunity management, closed-won, onboarding, adoption, renewal, and expansion. Mark the point where ownership becomes unclear, data stops moving, or teams begin using conflicting definitions.

If failures appear across Marketing Operations, Sales Operations, and Customer Success Operations, favor a full-lifecycle team. If the problem stays inside a known system or workflow, a specialist may be faster and easier to govern. If your team knows what to do but applies it inconsistently, coaching may be sufficient. If nobody has authority to decide what should happen, you need an accountable fractional leader before you need more tools.

A useful buying brief fits in one sentence: We need an accountable owner to improve this lifecycle handoff in these systems, with success judged by these business and operational measures. If you cannot complete that sentence, use discovery to define the problem before committing to a large implementation.

Leading RevOps firms, organized by the work they fit

No firm is the universal best choice. The table below treats leading RevOps companies as a fit map: what each appears equipped to handle, followed by the issue you should validate before signing.

Firm	Consider it when	What to validate
Domestique	You are a B2B SaaS company seeking embedded, full-lifecycle coverage across Marketing Operations, Sales Operations, Customer Success Operations, platform implementation, and agentic infrastructure. Its reported capabilities include more than 60 senior operators, work with more than 250 B2B organizations, and hands-on AI agents and MCP integrations.	Confirm which senior operators will work on your account, their allocated capacity, and the leadership participation expected from your team. The fractional-agency assessment specifically notes that active client leadership involvement is important at the strategy layer.
Go Nimbly	You run a Salesforce- or HubSpot-centered growth-stage SaaS environment and need revenue architecture, technical execution, AI readiness work, or RevOps coaching. Its positioning combines AI-enabled GTM strategy with Salesforce, HubSpot, Outreach, and Salesloft experience.	Define how much hands-on Customer Success Operations coverage is included. Also identify the exact team composition because reported delivery pace can depend on scope and staffing.
Skaled	You need a modular intervention rather than complete outsourced ownership. Available services span fractional CRO or VP leadership, CRM and automation support, revenue enablement, outbound performance, and an AI GTM system. A NoFraud case study reports a 126% pipeline increase and 95% MQL growth over eight months, but that result is case-specific rather than a forecast for another company.	Ask who coordinates work when your scope crosses leadership, administration, enablement, and AI practices. Confirm which result from the relevant case work is transferable to your market, team, and funnel.
RevPartners	You are committed to HubSpot and want an ongoing RevOps-as-a-Service model, lifecycle measurement, GTM engineering, or Clay-powered outbound automation. Its Revenue Performance Model connects acquisition, conversion, retention, and expansion.	Test the required depth outside HubSpot and Clay. Salesforce-primary companies and teams requiring extensive hands-on Customer Success Operations should define those needs explicitly before assuming they are covered.
FullFunnel	You need broad B2B GTM strategy plus Sales Operations, Marketing Operations, or managed RevOps. Its listed platform footprint includes HubSpot, Salesforce, Clay, Apollo, and n8n.	Ask which lifecycle stages the proposed team will own, which it will support, and which remain with you. Platform breadth should be converted into named deliverables and accountable operators.
Operatus	Your requirements center on Salesforce CPQ, MuleSoft, systems integration, or managed RevOps in a stack that may also include HubSpot, Apollo, Salesloft, LeanData, Outreach, or Marketo. Those platform and consulting specialties distinguish its systems-oriented offer.	Verify whether your scope needs a technical implementation partner, a cross-functional operating leader, or both. Do not assume CPQ and integration expertise automatically includes deep marketing and post-sale ownership.
Winning By Design	You already have people who can execute and primarily need GTM methodology, the SPICED framework, revenue coaching, or certification. Its listed specialty is methodology training and advisory rather than comprehensive outsourced operations.	Separate enablement deliverables from system-building deliverables. If you need CRM administration, integration work, data remediation, or ongoing workflow ownership, identify who will perform it.
Think RevOps	You want RevOps as a Service or stack optimization across HubSpot, Salesforce, and Gainsight. The inclusion of Gainsight makes it worth considering when customer-success tooling is part of the operating problem.	Request direct evidence for any AI implementation requirement. AI or agentic capability was not listed for the firm in the 2026 fractional-agency comparison.
RevOps Automated	You need GTM strategy, system integration, managed services, or AI-powered workflow automation in HubSpot and Salesforce. Its positioning emphasizes automation and AI-powered GTM workflows.	Ask to see the architecture, controls, and operational results of a comparable workflow. Also define the required Customer Success Operations depth rather than inferring it from the managed-services label.
Process Pro Consulting	You have a focused HubSpot build, cleanup, or optimization requirement and prefer a specialist over a broad multi-platform firm. Its listed proficiency and specialty are centered on HubSpot.	Inventory every system that must exchange data with HubSpot. If Salesforce, customer-success platforms, or agentic automation are material to the scope, determine whether another specialist will be needed.

Your preferred order can change simply by changing the scoring weights. The fractional-agency methodology assigned 30% to platform proficiency and 30% to AI and agentic capability. The broader RevOps methodology assigned 30% to leadership, 25% to platforms, 20% to customer reviews, and 10% each to AI capability and lifecycle scope. A company prioritizing AI infrastructure could therefore reach a different answer from one prioritizing executive leadership or full-lifecycle operations.

Rewrite those weights around your own risk. If your CRM is unstable, architecture and implementation depth should dominate. If functions disagree about stages, ownership, or forecasting, leadership and lifecycle scope matter more. If you already have strong operators and need a repeatable selling method, coaching quality should carry more weight than platform breadth.

Do not let a logo wall override this work. Notable clients accounted for only 5% in the fractional-agency methodology and 5% in the broader company methodology. A famous client proves that some relationship existed; it does not establish that the agency handled your use case, systems, lifecycle stage, or engagement model.

Use a buying process that exposes delivery risk

Client and agency teams test a modular revenue workflow together while reviewing handoffs, system access, and contingency paths.

Give every candidate the same written brief and ask for the same evidence. Otherwise, the most polished pitch will seem like the strongest capability even when candidates are solving different versions of your problem.

Identify the operator who will actually own the work

A senior leadership page does not tell you who will attend your operating meetings, make architecture decisions, configure systems, or resolve conflicts between marketing, sales, finance, and customer success. Ask the candidate to name the proposed operator and explain the delivery chain.

Who is accountable for the business outcome, and who performs the implementation?
Which proposed team members are employees, contractors, specialists, or executive sponsors?
How much concurrent client work does each assigned operator carry?
Who has authority to approve process, data-model, and automation decisions?
What happens when a requirement crosses practice areas or falls outside the original platform specialty?
Which responsibilities remain with your internal leaders, administrators, analysts, and front-line managers?

Listen for clear ownership, not a large roster. A fractional executive who cannot direct implementation may leave you coordinating multiple delivery teams. An administrator without authority may complete tickets while the underlying operating disagreement remains untouched.

Test platform depth with one of your real workflows

Partner status and certifications are useful screening signals, but they do not prove that the proposed operator has solved your specific architecture problem. Bring a representative workflow to the evaluation: lead routing, account matching, opportunity-stage governance, CPQ approval, marketing attribution, closed-won handoff, renewal management, or expansion identification.

Ask the candidate to map the systems of record, objects, fields, triggers, dependencies, permissions, exception paths, and reporting effects. Strong operators will surface ambiguities before proposing automation. Weak answers jump directly to a tool or produce a generic diagram that could apply to any company.

Protect production data during implementation. Do not permit bulk CRM writes, object changes, routing changes, destructive merges, or new automations without an approved backup or export, a test environment where the platform supports one, defined validation checks, a release owner, and a rollback plan. A failed routing rule can hide demand; a poorly governed merge or overwrite can destroy history needed for attribution, forecasting, or account management.

Trace ownership through the complete customer lifecycle

Full-funnel language can describe measurement rather than hands-on ownership. Ask each candidate to walk through the lifecycle and identify who designs, implements, monitors, and improves every important handoff.

Acquisition to qualification: Who defines fit, intent, routing, response expectations, and rejection reasons?
Qualification to opportunity: Who governs stage entry, required fields, ownership changes, and pipeline reporting?
Closed-won to onboarding: Which data crosses the handoff, where is it stored, and who checks completeness?
Onboarding to adoption: How do product, service, or customer-success signals become visible to the revenue team?
Adoption to renewal: Who owns renewal dates, risk signals, commercial actions, forecasts, and escalation?
Renewal to expansion: How are expansion opportunities identified, assigned, measured, and separated from retention?

If the answer becomes vague after closed-won, you are probably evaluating a sales-and-marketing operations firm rather than a complete lifecycle partner. That may be the right fit, but it should be an explicit decision rather than a discovery made after the engagement begins.

Turn AI positioning into an auditable system design

AI readiness, AI strategy, agent deployment, and agentic infrastructure are different deliverables. Domestique lists MCP server deployments, a deterministic harness framework, and Claude and Clay agents. Go Nimbly emphasizes AI-enabled architecture and readiness. Skaled combines maturity benchmarking, deployment, training, and certification. RevPartners focuses on Clay-powered allbound automation, while RevOps Automated emphasizes AI-powered GTM workflows. Put the exact capability you need into the scope instead of purchasing the broadest label.

Use case: What specific decision or task will the system assist, automate, or execute?
Inputs: Which CRM records, conversations, documents, enrichment data, or customer-success signals can it read?
Permissions: Can it only recommend an action, or can it create, update, route, message, or delete?
Control: Which actions require human approval, and who is accountable for that approval?
Evaluation: How will you test accuracy, completeness, consistency, and business usefulness before release?
Observability: What prompts, tool calls, outputs, errors, and record changes are logged?
Failure handling: What happens when the model is unavailable, uncertain, wrong, or given incomplete data?
Ownership: Who maintains instructions, integrations, permissions, evaluations, and vendor dependencies after launch?

A working demo is more valuable than an AI strategy slide. Use representative but non-sensitive data and ask the candidate to show the complete path from input through reasoning or rules to the resulting CRM action. If the workflow can change customer records, routing, forecasts, or outbound messages, require approval boundaries and a recoverable path before production access is granted.

Read reviews for engagement similarity, not just stars

Review averages compress important differences. One 2026 methodology aggregated verified G2, Clutch, and Google ratings and rounded them to the nearest half star; the broader methodology weighted RevOps-specific engagements and rounded ratings to whole stars. Neither treatment tells you whether a positive review came from an embedded transformation, a migration, a small administration project, or executive coaching.

Ask for references that match your company stage, primary platform, lifecycle problem, and engagement model. Questions about setbacks are more revealing than requests for general satisfaction: what slipped, which assumption proved wrong, how scope changed, who resolved cross-functional conflict, and what the client had to own internally.

Scope the first engagement so you can judge real progress

A strong statement of work turns RevOps language into operating commitments. It should make clear what will change, how you will accept it, who can decide, and how your team will run the result after the agency leaves.

Problem boundary: Name the lifecycle failure, affected teams, systems, records, and processes. Also state what is out of scope.
Baseline and outcome: Record the current operational and business measures that matter. Distinguish outputs such as workflows built from outcomes such as cleaner routing, more reliable stage data, better handoff completeness, or usable renewal visibility.
Target operating design: Define stages, ownership, systems of record, required data, decision rights, and escalation paths before automating them.
Deliverables: List the actual artifacts and system changes: architecture maps, data dictionaries, lifecycle definitions, configured workflows, dashboards, documentation, training, and governance procedures.
Acceptance criteria: State how each deliverable will be tested and who can approve it. Completion should not depend solely on the agency declaring a task done.
Change control: Specify test procedures, production permissions, release approval, backups, rollback, and incident ownership.
Internal participation: Name the executive sponsor, operational owner, system administrator, subject-matter experts, and front-line users whose decisions or feedback are required.
Handoff: Require accessible documentation, administrator training, unresolved-risk tracking, credential and integration ownership, and a prioritized backlog for work that remains.
Commercial boundaries: Clarify which work is included, what triggers additional fees or a change request, and how staffing changes affect delivery.

If your problem is still poorly defined, make the first phase a diagnostic with implementation-ready outputs: a current-state map, target-state design, prioritized backlog, ownership model, dependencies, risks, and acceptance criteria. Do not accept a generic strategy presentation that forces the implementation team to rediscover the same requirements.

Before your next agency call, write the one-sentence problem, list the systems involved, mark the affected lifecycle handoffs, and identify the proof you need to see. Send the same brief to each candidate. The safer choice is usually the firm that sharpens your scope, names tradeoffs, assigns an accountable operator, and makes its implementation testable.

References

August 27, 2026

How to Prepare for Google’s Demand Gen Campaign Expansion

If your Demand Gen campaigns already attract attention but lose people between the ad and the next meaningful step, Google’s expansion matters. The new capabilities change how a viewer can respond, how a travel offer can be matched to demand, and how quickly your team can produce the video formats a campaign needs.

The useful question is not whether to activate everything. It is which constraint currently limits growth: a long lead path, generic travel merchandising, or too little usable video. Identify that constraint first, then test the corresponding capability against a customer outcome.

Treat the expansion as a change to the conversion path

Demand Gen begins in a discovery context, but its expansion brings several later-stage functions closer to the ad. That distinction matters because each function solves a different problem.

Google is testing direct messaging from Demand Gen ads on YouTube. A person who discovers your brand through a video may be able to begin a conversation through a messaging app instead of navigating through a conventional website journey first. This can shorten the path for a prospect who already has a specific question or strong intent.

Travel advertisers are getting a different kind of expansion. Demand Gen can surface local activities, events and real-time offers while personalizing hotel selections for audiences Google considers relevant. Here, the opportunity is not a new contact method. It is a closer match between what a traveler may want and what the advertiser can offer.

Creative teams have a third option. Multimodal Video Creation in Asset Studio is generally available, with a workflow that can move from storyboarding to horizontal and vertical video production. This addresses creative supply, not conversion-path friction by itself.

Capability	Availability described	Problem it can address	Readiness requirement
Messaging from YouTube ads	Testing	Too much friction between high-intent discovery and direct contact	A team and process that can receive, qualify and advance conversations
Travel activities, events, offers and personalized hotels	Expanding	Generic merchandising that does not reflect what a traveler may want to do or book	Accurate, current and fulfillable offer information
Multimodal Video Creation	Generally available in Asset Studio	Insufficient horizontal and vertical video assets	A creative brief, brand controls and human review

These are not interchangeable optimizations. Adding video will not fix an unanswered message. Messaging will not make a stale travel offer relevant. Personalization will not rescue a weak proposition. Match the feature to the blockage you can actually observe.

Choose the bottleneck before you choose the feature

Strategist choosing among three visual bottlenecks representing a long response path, generic travel offers, and too few adaptable video assets.

Use messaging only when a conversation can move the sale forward

A shorter route helps only if the conversation has somewhere to go. Before entering the messaging test, map the entire handoff from the ad promise to the business outcome:

State what the prospect is being invited to discuss. A vague invitation may produce activity without useful intent.
Define the information that makes a conversation qualified, such as the need, intended purchase, service fit or booking question.
Assign responsibility for receiving and advancing the conversation. An opened thread that sits unanswered is not a customer-acquisition improvement.
Specify the outcome that matters after the conversation begins: a completed purchase, accepted lead, confirmed appointment or another business result already used by your organization.
Preserve a route for people who prefer the website. The messaging path should remove friction for the right prospect, not force every prospect into the same behavior.

Messaging is a sensible test when interested prospects regularly need clarification before acting and the existing site journey makes that clarification difficult. If the real problem is weak demand, an unclear offer or slow internal follow-up, changing the contact channel will expose that problem rather than solve it.

Make travel personalization earn its relevance

Travel personalization increases the importance of offer quality. A locally relevant activity or timely event can make discovery more useful, but only if the advertised experience is current, available and consistent with what the traveler reaches next.

Audit the material that could appear before expanding:

Confirm that each promoted activity, event, offer or property can still be booked or purchased.
Check that the location and audience context fit the offer. Geographic proximity is not the same as traveler relevance.
Make the destination page continue the same promise, price context and experience shown in the ad.
Remove or update offers promptly when availability changes. Real-time promotion creates little value if the underlying information is stale.
Measure activity discovery and hotel selection as different decisions. They may sit within the same campaign type, but they do not necessarily represent the same customer intent.

Personalization should narrow the gap between the traveler’s situation and the offer. If your team cannot keep the offer layer accurate, broader personalization may create more mismatches at scale.

Use AI video creation to build a testable asset system

The practical benefit of Multimodal Video Creation is not simply that it can generate video. It can help a team carry one concept from storyboard into horizontal and vertical executions within a single workflow. That can reduce the production friction involved in supplying multiple formats.

Do not turn that production speed into uncontrolled variation. For the first asset set, keep the offer and desired action consistent. Change one major creative dimension at a time, such as the opening frame, narrative emphasis or orientation. You will have a better chance of learning why one execution performs differently.

Every generated asset still needs human review. Check factual claims, brand presentation, cropping, text legibility, the destination and the relationship between the creative promise and the next step. General availability means the workflow is broadly accessible; it does not make every output ready to spend against.

Measure customer quality instead of celebrating new activity

Google attributes the hundreds of Demand Gen improvements made during the second half of 2025 to an average 30% increase in conversions or conversion value. Treat that as a platform-reported aggregate, not a forecast for your account or for any one new feature. Conversion count and conversion value are also different outcomes; an increase in one does not establish an increase in the other.

Write a measurement contract before launch so that a new interaction cannot quietly redefine success:

Choose the business outcome. Use the result that matters to the campaign, such as a purchase, booked stay or qualified lead, rather than a generic engagement signal.
Name the feature-level behavior. This could be a conversation started, an offer explored or a video execution viewed, but treat it as an intermediate signal unless it is itself the business outcome.
Define quality. For messaging, decide what makes a conversation qualified. For travel, distinguish a fulfilled booking from interest in an unavailable offer. For video, judge the asset against the same acquisition goal as the campaign.
Preserve a meaningful comparison. Keep the audience, offer and desired outcome as consistent as the campaign design allows while introducing the capability you want to evaluate.
Set the decision in advance. State what evidence would justify expansion, revision or a pause. Do not invent the rule after seeing the most flattering metric.

The pattern of the results should tell you where to look next:

If conversion volume rises but customer quality falls, inspect qualification and the action being optimized before increasing exposure.
If messaging creates more conversations but few advance, check the ad promise, opening response and sales handoff.
If video engagement improves without a customer outcome, the creative may be earning attention without establishing intent.
If travel interactions rise around activities but bookings do not, inspect availability, offer continuity and the booking path rather than assuming the audience is wrong.

This prevents a common measurement mistake: treating the new behavior made possible by a feature as proof that the feature produced valuable demand.

Run a controlled rollout instead of a broad switch-on

Marketing team observing baseline and limited-test campaign assets moving through parallel customer-outcome pathways.

A controlled rollout gives you a clear reason for making each change and a better chance of learning from it. Use this sequence:

Write the constraint in one sentence. For example: interested viewers need answers before converting, travel offers are too generic, or the campaign lacks enough video formats.
Apply a readiness gate. Messaging requires response ownership; travel personalization requires current offers; AI video requires a brief and an approval process.
Select the capability that directly addresses the constraint. Do not add unrelated features to the same initial test.
Prepare the downstream path before launch. Check the conversation handoff, booking destination or creative-to-landing-page continuity from beginning to end.
Record volume and quality separately. More interactions can increase workload without increasing valuable customers.
Expand only after the downstream outcome supports it. If the result is ambiguous, revise the handoff or creative variable before broadening the test.

This sequence is especially important for messaging because it remains a test, while Multimodal Video Creation is generally available. Feature status should affect how cautiously you operationalize a capability, but availability alone should never be the business case for using it.

Key takeaways

Demand Gen’s expansion addresses three different constraints: contact friction, travel-offer relevance and video-production capacity.
Messaging can shorten the route from a YouTube ad to a brand conversation, but it needs qualification, ownership and a defined downstream outcome.
Travel personalization is only as useful as the accuracy, availability and continuity of the activities, events, offers and properties being promoted.
AI video creation can supply horizontal and vertical assets more efficiently, but generated output still requires controlled variation and human review.
Google’s reported average lift is useful context, not an account-level promise. Base your decision on customer quality and business value.

Your next move is deliberately small: write down the single constraint limiting your current Demand Gen campaign, choose the one expansion capability that addresses it, and define the downstream result before changing the campaign. That turns the expansion from a bundle of new options into a test your team can understand and act on.

References

Search Engine Land — Google expands Demand Gen with messaging ads, travel tools and AI video creation

August 27, 2026

Image Optimization for AI Search: A Practical Workflow

Your images can be attractive, fast and conventionally SEO-friendly yet still be unclear to an AI system. If the system cannot identify the main object, read an important label or connect the scene to the claims on the page, the image contributes little to a multimodal answer.

Fixing that problem does not mean putting more keywords into filenames. It means making the pixels, alternative text and visible page copy tell the same specific story. The workflow below will help you decide what each image must communicate, test whether that meaning survives machine interpretation and correct the failures that matter.

AI search needs an image it can retrieve and explain

Visual search is no longer a secondary way to browse an image index. People run roughly 20 billion visual searches through Google Lens each month. A search can begin with a camera, an uploaded image or a screenshot when the user cannot easily describe the object in words.

That changes the optimization target. The old question was whether an image could rank for a text query. The additional question is whether a system can use the image to understand the query, retrieve the associated page and assemble a supported answer.

Google filed a patent application in 2023, published in April 2026, describing a flow in which an image match identifies a cited page before surrounding text is used to construct an answer. That is not confirmation of a live production ranking process. Patent applications may never be implemented as written. It is still a useful design signal: an image may help a system discover the page whose text supplies the explanation.

Treat every important image as a paired asset: the visual evidence and the page evidence. Before publishing it, ask four questions:

Can the system access and render the image when it retrieves the page?
Can it identify the primary product, person, place, condition or process without relying on the filename?
Can it read any visible text that is necessary to distinguish a model, package, measurement or state?
Does the surrounding HTML text confirm what the image shows and explain why it matters?

If the image fails the second or third question, fix the asset or choose another one. Metadata cannot rescue a photograph whose subject is tiny, obscured or visually ambiguous. If it fails the fourth question, improve the page copy. A model should not have to infer a critical fact from pixels alone.

Run two audits: what is visible, then what it implies

An orange trail shoe is shown under a magnifying lens on one side and beside a rocky path, mud, and a water bottle on the other.

A useful image audit separates literal recognition from implied meaning. Combining them too early hides the cause of a failure. You may think an image communicates expert installation, for example, when a machine sees only a person standing beside a cabinet.

Audit the literal contents without page context

Start with denotation: the objects and attributes that can actually be pointed to in the frame. Hide the headline, caption, filename and surrounding copy. Then write a neutral inventory of what is visible.

For a product photograph, that inventory might include a stainless steel coffee maker, a thermal carafe, a control panel and a visible model label. For a service photograph, it might include a leaking pipe joint, a wrench and a technician wearing protective gloves. Keep interpretation out of this first pass. Words such as premium, reliable and professional are conclusions, not visible objects.

Now ask a capable multimodal model for a literal description using a neutral instruction such as: “List the objects, visible text, materials, conditions and relationships in this image. Do not infer facts that are not visually supported.” Compare its output with your own inventory and with the visual brief.

This is a diagnostic check, not a simulation of any particular search engine. Different models can produce different descriptions, and one successful response does not prove retrieval or citation. The test is still valuable because a missed primary object exposes an avoidable ambiguity in the image.

When an essential object or attribute is missed, inspect the likely visual cause:

The primary subject occupies too little of the frame.
Another object has stronger contrast and becomes the apparent subject.
The item is partly hidden, cropped or viewed from an angle that conceals its defining shape.
Several similar objects overlap, making their boundaries unclear.
Glare, shallow focus or compression makes packaging text unreadable.
The rendered website crop removes information that was present in the original file.

Fix composition before metadata. Use a clearer angle, tighter crop, simpler background, additional close-up or separate detail image. Product galleries should not make one wide lifestyle photograph perform every recognition task.

Audit the meaning created by the composition

The second pass examines connotation: what the combination of objects, people and setting implies. This is where co-occurrence matters. A wrench beside a visibly damaged fitting tells a different service story from the same wrench lying on a spotless workbench. A team portrait in an identifiable office says something different from anonymous people in a generic meeting room.

Write the intended meaning in one sentence. Then underline the visible evidence that supports every part of it. If the intended meaning is “a technician diagnosing a leaking kitchen connection,” the frame should contain a technician, a relevant connection and evidence of the leak. If only the kitchen is visible, the image is decorative context rather than proof of the service.

Use these questions to expose weak or accidental implications:

What is the most prominent entity, and is it the entity the page is about?
What relationship between the visible entities would a neutral viewer infer?
Which object introduces an unrelated interpretation?
Does the setting support the intended use case, location or audience?
Are you asking the image to prove a credential, performance claim or identity that only text can establish?

Original imagery matters most when the image is supposed to establish identity or evidence. A stock photograph can illustrate a general concept, but it cannot reliably prove what your product looks like, who works on your team, where your business operates or how your service is performed. Use visible page copy to name people, roles, credentials and locations rather than expecting a model to infer them from appearance.

Give each page type a deliberate visual job

An image should be briefed against the decision a visitor is making on that page. The same attractive photograph will not serve a homepage, product page and technical explainer equally well. Different page types require different visual evidence, especially when a multimodal system may use that evidence to interpret the surrounding content.

Page type	Primary visual job	What the image should make detectable	What the page text should confirm
Homepage	Establish the brand and offering	An original product, location, team or use context rather than an interchangeable mood image	The brand name, principal offering and relationship between the visible entities
Product page	Support identification and comparison	The complete product, multiple angles, distinctive parts, packaging and legible model or variant text	Product name, variant, materials, dimensions and other attributes relevant to the image
Blog or information page	Explain a concept, process or claim	Clearly labelled steps, components, states or relationships in a diagram or infographic	Every substantive claim shown in the graphic, written as ordinary machine-readable HTML text
About or team page	Connect a person with an organization and role	A clear portrait or authentic workplace context	The person’s name, role, credentials and authorship relationship where relevant
Service page	Show the problem, work or outcome	The actual condition, equipment, process or clearly differentiated before-and-after states	The service performed, the meaning of each state and any necessary limitations
Contact or location page	Reinforce physical identity and place	The exterior, entrance, interior or recognizable local context	The business name, address and relationship between the pictured place and the business

Give each image one primary job even when it can support several queries. A product hero can establish the overall shape; a second image can expose controls; a third can make the package label readable. This is clearer than forcing a single distant photograph to carry every attribute.

Be especially careful with infographics and before-and-after images. Do not leave the claim inside the graphic. Repeat it in the page copy, identify which state is which and explain what changed. The image can demonstrate the relationship, while the text supplies the exact claim and its qualifications.

Publish the image and page as one semantic unit

A red insulated bottle, its studio photograph, a blank article layout, and a transparent lens are connected by soft blue light on a desk.

Write a visual brief before choosing the asset

A useful visual brief is short enough to apply during a content review. For each important image, record:

Target question: the query or decision the visual should help resolve.
Primary entity: the product, person, place, condition or process that must be recognized.
Must-detect details: the visible attributes needed to distinguish the entity or explain the answer.
Must-read text: labels or packaging copy that must remain legible in the delivered image.
Intended implication: the relationship or use case the composition should communicate.
Supporting sentence: the nearby HTML text that names and explains what the image shows.
Failure condition: the omission or misreading that would make the image misleading or useless.

This brief prevents a common mismatch: copy written around a concrete answer paired with an image selected for atmosphere. It also gives designers, photographers, writers and SEO teams one set of acceptance criteria.

Preserve meaning through the technical delivery

Traditional image hygiene still matters, but each choice should preserve recognition as well as performance. Use a descriptive filename because it provides context, not because a keyword-rich filename can override the pixels. Supply responsive dimensions and an appropriate format, then inspect the image as it actually appears on the page.

Compression deserves a visual check at every important breakpoint. A package label that is crisp in the master file may become unreadable in a smaller responsive variant. Performance optimization should preserve the legibility of product text, labels and diagram annotations that a system needs to interpret the image.

Use loading settings that improve page performance while keeping the image available when the page is rendered and retrieved. Check the delivered page rather than assuming the media library preview represents what a crawler or visitor receives.

Write alternative text for accuracy and accessibility

Alternative text should describe the image’s purpose in its page context. Keep it natural and factual. Do not turn it into a string of search terms, and do not insert claims the pixels do not support.

For example, “Stainless steel coffee maker beside its thermal carafe, with the model name visible on the front panel” is useful when those details help the reader understand the product. “Coffee maker, best thermal brewer, premium coffee machine” is neither a reliable description nor good accessible text.

Complex diagrams need more than a long alt attribute. Give the image a concise accessible description, then explain the important steps, comparisons or claims in visible HTML text. A decorative image that contributes no information should use the appropriate empty alternative text rather than forcing irrelevant keywords onto screen-reader users.

Run the final check on the rendered page

Use this sequence before publishing or replacing a high-value image:

Write the target question and the one visual fact that helps answer it.
List the entities, attributes and text that must be detectable in the frame.
Inspect the image without page context and record a literal human description.
Run the same blind description through at least one multimodal model and note omissions or competing interpretations.
Correct the crop, angle, clutter, visibility or export quality before changing metadata.
Confirm that the alt text and nearby page copy accurately name what is visible and carry every important claim.
Test the delivered image at the page’s actual responsive sizes, including the legibility of labels and annotations.
Save the intended query, observed description and corrections so that later asset changes can be reviewed against the same brief.

After publication, use a fixed set of visual and text queries when checking search or AI-answer visibility. Record whether the image appears, whether the associated page is cited and whether the answer describes the intended attributes accurately. An appearance is evidence of visibility, not proof that one metadata change caused it, so compare repeated checks rather than drawing a conclusion from a single result.

Key takeaways

Optimize the visual evidence and the page evidence together; neither should contradict or depend on the other to repair ambiguity.
Test literal recognition before judging brand meaning. If the primary entity is missed, fix the composition first.
Control co-occurrence deliberately. Every prominent object and person in the frame contributes to the meaning a model may infer.
Assign images different jobs by page type: identification on product pages, explanation on information pages and entity confirmation on team or location pages.
Repeat substantive graphic claims in visible HTML text. Important facts should not exist only inside pixels or alternative text.
Compress for performance while checking the actual delivered crop, resolution and text legibility.
Treat multimodal model descriptions as diagnostic observations, not guarantees of ranking, retrieval or citation.

Start with five pages that matter commercially or editorially. Hide the copy, inspect each rendered image and ask what a neutral observer can actually identify. Replace or recompose the images that fail that blind test, then align the alternative text and nearby copy with what remains. That small, documented audit gives you a repeatable standard for every visual you publish next.

References

Search Engine Land — Your images have a new job in AI search

August 27, 2026

Reddit-Driven Keyword Research: A Practical SEO Workflow

If your keyword list keeps returning minor variations of the same head terms, it is probably missing the questions people ask when a decision becomes complicated. Reddit’s Google rankings expose those questions, along with the objections, conditions and comparisons that conventional keyword lists often flatten.

The goal is not to copy Reddit, manufacture a discussion or treat anonymous comments as evidence. You are using Reddit’s organic footprint as a query-discovery layer: find conversations that search engines already surface, identify the need behind each query and publish a more accountable answer on the right page.

Key takeaways

A Reddit ranking is a demand signal, not proof that the discussion is accurate. It tells you that Google currently considers the conversation relevant to the query.
Validate Reddit’s importance in your market before building a large report. Some narrow, regulated and highly technical categories produce very little useful data.
Start with three to five non-brand themes, export Reddit’s top-10 rankings and tighten the filter to the top three when a theme produces an unmanageable list.
Do not turn every keyword into a new URL. Group queries by the decision, obstacle or outcome behind them, then choose between updating a page, creating a page, adding a useful FAQ or skipping the opportunity.
Your advantage is editorial accountability: a direct answer, explicit conditions, verified claims and a structure that helps the reader make a decision. You do not need to imitate a thread.

Decide whether Reddit deserves a place in your dataset

Reddit is large enough to justify a test. An August Semrush snapshot put reddit.com at roughly 166 million ranking keywords, including more than 10 million in position one, 31 million in the top three and 65 million on page one. Those numbers explain why Reddit can matter; they do not prove that it matters in your particular market.

The useful question is narrower: does Reddit rank prominently for non-brand queries that your customers use while researching, comparing, troubleshooting or validating a decision? Run a small feasibility check before you commit time to a full gap analysis.

Run a 30-minute feasibility check

Choose two or three core non-brand themes tied directly to what you sell or explain. Use customer language, not an internal product taxonomy.
In Semrush, enter reddit.com in Domain Overview and open its Organic Research data.
Filter keywords for one theme at a time and restrict positions to the top 10.
Review the results for relevance. Do not judge the opportunity from the raw row count alone.
Record a go, narrow or stop decision for each theme before exporting anything at scale.

Proceed when the results contain several distinct customer problems, prominent Reddit rankings and questions your organization can answer credibly. Narrow the theme when a broad word creates unrelated meanings, locations, brands or acronym collisions. Stop when the list is thin, mostly irrelevant or disconnected from any useful reader action.

This gate matters because Reddit’s influence is uneven. Consumer products, software, travel and other categories with opinionated buying decisions can generate extensive gaps, while niche B2B, highly technical, regulated or unusually narrow subjects may produce much smaller ranking sets. A small set is not a failed analysis. It is evidence that your time may be better spent on another discovery channel.

You do not need to create a Reddit account or participate in a community for this workflow. The ranking analysis can be completed with a Semrush login and an initial time box of about two hours. Participation, community management and keyword discovery are separate jobs; do not bundle them into one strategy by default.

Build a focused export instead of a keyword warehouse

A sorting sieve filters a large stream of blank query cards into a small, organized tray of selected research cards.

A useful export is deliberately constrained. If you begin with every Reddit ranking that loosely touches your industry, you will spend the session cleaning rows rather than learning what people need. Work theme by theme and preserve the context that produced each set.

Use a repeatable report recipe

Open Semrush Domain Overview for reddit.com and move to Organic Research.
Under Advanced Filters, select Include, Keyword and Containing.
Enter one core non-brand phrase. A specific category phrase is usually easier to judge than a single broad word.
Set the position filter to Top 10 and apply it.
Export the results to Excel.
Repeat the process for each of your three to five initial themes.

The top-10 filter is a practical starting point because it captures queries where Reddit already has meaningful first-page visibility. If a broad theme returns far more rows than you can review, restrict it to the top three. If a narrow theme is genuinely relevant but sparse, loosen the position cutoff. The right filter is the one that leaves you with a list a person can inspect, not the one that produces the largest spreadsheet.

Keep the first pass to three to five themes. You need enough variety to see patterns, but not so much data that you begin making decisions from volume and position alone. Once you have classified one batch consistently, you can expand with better judgment.

Add the columns that turn rankings into decisions

Keep an untouched tab containing the raw export. In a working tab, retain the exported metrics and add these editorial columns:

Capture date: Reddit’s visibility can change, so every export needs a timestamp.
Theme: preserve the filter that surfaced the query, even after files are merged.
Query: keep the wording exactly as exported.
Reddit position and ranking URL: record the result that created the opportunity.
Search intent: label the job as learning, comparing, selecting, troubleshooting or validating.
Audience and context modifiers: note experience level, use case, constraint, location or other condition present in the query.
Underlying question: rewrite the query as the full question a reader appears to need answered.
Current site URL: identify the best existing page, if one exists.
Coverage: mark the question as fully answered, partially answered, mentioned only or missing.
Recommended action: update, create, add to an FAQ, monitor or skip.
Priority reason: state in one sentence why the opportunity deserves resources.

When a query appears in more than one theme, keep one working row and retain all relevant theme labels. Do not erase the overlap: it may reveal that the same customer question connects product categories your site currently treats as separate silos.

Start with non-brand themes because they expose category demand without assuming the searcher already knows you. Branded Reddit analysis can be valuable later for reputation, support and product-feedback work, but mixing it into the first export makes content-discovery decisions harder to interpret.

Convert ranking rows into defensible content decisions

An analyst aligns transparent layers of search results, discussion patterns and editorial brief cards to isolate one highlighted content opportunity.

A keyword is not a content brief, and a ranking gap is not an automatic instruction to publish. The row only earns a place on your roadmap after you understand what the ranking result is satisfying and whether your site has an appropriate answer.

Inspect the conversation behind priority queries

Open the ranking result for the most relevant, highest-positioned queries. You are not looking for sentences to reuse. You are looking for the anatomy of the problem:

What did the person ask in the title, and what additional constraint appeared in the body?
Which comparison criteria recur across the useful replies?
What objection, failure mode or exception changes the answer?
Where do participants disagree, and does the disagreement come from different circumstances?
Which terms do people use naturally that your current page avoids or replaces with internal language?
What remains unresolved after reading the conversation?

Treat personal experiences as clues about questions and conditions, not as verified facts. A repeated anecdote may justify investigating an issue, but it does not justify repeating the claim on an accountable brand page. Verify factual, technical, financial, legal or health-related statements with suitable authoritative evidence before publishing them.

Cluster by the reader’s job, not by shared words

Two queries belong on the same page when one answer can satisfy both without changing the audience, primary decision or required evidence. They probably need separate pages when they ask different primary questions, apply to materially different situations or lead to different next actions.

Use broad intent labels only as a first cut. Within a comparison cluster, for example, distinguish between choosing an option, understanding a tradeoff and checking whether a prior choice was a mistake. Those may contain the same nouns while requiring very different answers.

Run Semrush Keyword Gap between your domain and reddit.com for each retained theme. Use it to separate three practical states: Reddit ranks and you do not; both domains rank but Reddit is stronger; or your site already performs competitively. Then inspect the actual page before declaring a gap. A ranking URL can exist while answering the wrong intent, burying the answer or mentioning the subject without resolving it.

Choose the smallest content action that fully answers the need

What you find	Content decision	What to change
An existing page serves the same audience and primary intent but leaves an important condition unanswered.	Update the existing page.	Add the direct answer, decision criteria, exceptions and supporting evidence without creating a competing URL.
The query represents a distinct primary problem and no current page can own it cleanly.	Create a new page.	Build the page around the reader’s complete task, then connect it to relevant parent and sibling pages.
The question is narrow, recurring and subordinate to a broader page.	Add a visible FAQ or supporting section.	Answer it where readers already need it. Add it to a reusable FAQ library only if the same answer remains valid across the intended contexts.
Your page ranks, but its format or opening does not match the apparent intent.	Rework the existing answer.	Move the conclusion forward, clarify who it applies to and restructure the page around the actual decision.
The query is irrelevant, outside your expertise or impossible to answer without unsupported claims.	Skip it.	Record the reason so the row is not reconsidered every time the analysis is refreshed.

Prioritize the rows where four signals align: Reddit ranks prominently, the query fits your audience, your current coverage is weak and you can produce a materially better answer. Search volume can help order otherwise similar opportunities, but it should not rescue a query with poor business fit or tempt you into a thin page.

For each approved cluster, write a one-page brief containing the target problem, audience conditions, direct answer, required evidence, content action, relevant internal links and the result you will measure. This forces the team to fund an answer rather than a keyword count.

Publish the missing answer and measure the right change

Reddit often earns visibility because a conversation addresses the messy version of a question: the tradeoffs, failed attempts and contextual details that polished category copy omits. You cannot reproduce peer discussion on demand, and you should not pretend to. You can produce a clearer, better-supported answer that accepts responsibility for its claims.

Answer the primary question in the opening paragraph. Do not make the reader cross a history lesson before reaching the conclusion.
State who the answer applies to and which conditions could change it.
Organize comparisons around criteria a reader can use, not a list of products followed by interchangeable descriptions.
Convert anecdotal concerns into questions to verify. Publish the verified conclusion and preserve any real uncertainty.
Address the strongest objection or failure mode in the main body rather than hiding it in a closing FAQ.
Use the audience’s natural terminology where it is accurate, but do not force every exported wording variation into headings.
Give each distinct subquestion one direct, self-contained answer. This helps readers scan the page and gives search and answer systems an unambiguous passage to interpret.
If you add structured data, make it describe the visible page accurately. Markup can clarify structure; it cannot compensate for an answer the page never provides.

The same opportunity set matters beyond conventional results. More than 35 million of Reddit’s ranking keywords in the August snapshot triggered AI Overviews, with Reddit cited in more than 15 million of them, a reported citation rate of about 46%. That makes the export a useful list of queries to monitor in generative search. It does not mean that copying Reddit’s phrasing, adding FAQ markup or publishing a page will cause an AI system to cite you.

Create a baseline before changing content. For each approved cluster, record the date, query, Reddit URL and position, your ranking URL and position, the presence of an AI Overview and the page action you intend to take. Preserve that snapshot alongside the brief.

Publish or update one coherent cluster at a time, and annotate the release date.
Recheck the same query set after search engines have had time to recrawl the affected pages and your normal reporting window contains usable data.
Compare rankings, impressions, qualified visits and the conversion or engagement action appropriate to the page.
Check the relevant generative results separately. Record whether your brand or URL appears, but do not merge that observation with ordinary organic position.
Keep, expand, consolidate or retire the work based on the intended outcome. Do not declare success merely because the page was indexed.

Reddit does not have to disappear from the result for your work to succeed. A useful outcome may be a stronger existing URL, ownership of an adjacent intent, qualified traffic or a page that becomes eligible for citation alongside community discussion. Measure the opportunity you chose, not a blanket promise to displace an entire platform.

Start with three non-brand themes and give the first pass two hours. If the feasibility check is thin, close the file and redirect the effort. If it is rich, choose the first cluster where relevance, coverage gap and answer credibility all line up, then fix that answer before expanding the spreadsheet.

References

Search Engine Land – Reddit is the keyword research tool you’re probably not using

August 27, 2026

Google August 2026 Spam Update: A Practical Recovery Plan

If pages that reliably ranked in Google’s top 10 disappeared around August 17-22, don’t start deleting content or rebuilding the site. The August 2026 spam update produced unusually severe ranking movement, but a missing URL in a rank tracker is not proof that Google deindexed it, penalized the domain, or identified a particular spam tactic.

Your first job is to classify the loss correctly. Verify it in your own search and business data, rule out technical failures, find the pattern connecting affected pages, and then make the smallest set of changes that tests a clear diagnosis.

How abnormal was the August 2026 ranking movement?

Across the same 100,000 U.S. organic keywords, 16.71% of URLs that ranked in the top 10 on August 17 were outside the top 100 by August 22. During a July 26-31 comparison period with no confirmed ranking update, that happened to 9.2% of top-10 URLs. In relative terms, a top-10 result was about 1.8 times as likely to disappear beyond position 100 during the update, an 82% increase over the baseline period.

The movement created new winners as well as sharp losses. The share of post-update top-three URLs that had previously failed to reach the top 20 was 12% higher than in the baseline comparison. That matters when you inspect your competitors: the replacement page may not have been gradually gaining on you. It may have jumped from relative obscurity while Google reassessed the result set.

Volatility reached all 20 tracked industries. Top-10 movement ranged from 74.64% in real estate to 85.55% in fashion and beauty. Real estate and healthcare, both YMYL categories, were among the steadier industries, but even the low end of that range represents substantial rearrangement. Industry stability is relative here, not evidence that a vertical was unaffected.

Those figures establish that the update was disruptive. They do not identify its targets. The measurement did not classify losing pages by content type, production method, backlink pattern, structured data, domain history, or alleged spam tactic. It also tracked only positions 1 through 100. A URL that disappeared could have moved to position 101, fallen much farther, or left the index entirely.

Key takeaways for an affected site

A top-10 URL falling beyond position 100 was unusually common during the update, so one dramatic loss does not by itself prove a sitewide penalty.
Rank-tracker disappearance and deindexing are different failure modes. Check index status before changing the content.
Broad volatility affected every tracked industry, so your vertical alone is not a sufficient explanation.
No available page-level analysis identifies a particular tactic, CMS, schema type, or use of AI as the cause.
Recovery work should follow a documented diagnosis. Mass deletion, indiscriminate rewriting, and sitewide schema changes destroy evidence before they establish what failed.

Prove the loss in your own data before diagnosing it

A laptop, phone, server device, and blank webpage cards are connected on an investigation table, with one group of pages illuminated for closer inspection.

A third-party volatility benchmark tells you when to investigate. It cannot tell you what happened to your site. Build an incident view that connects rankings to impressions, clicks, index status, templates, and business outcomes.

Build a page-query incident sheet

Identify the affected landing pages. Export the pages with the largest losses in Google Search Console impressions and clicks. Include average position as a directional measure, but do not treat an account-wide average as a diagnosis.
Use August 17 and August 22 as external volatility anchors. Compare suitable pre-update and post-update windows in your own data, while checking individual days for when each page began to move. Keep day-of-week effects and normal demand changes visible.
Map losses at the page-query level. A page may lose one competitive query while retaining the rest of its search footprint. Separate a narrow query displacement from a pagewide collapse.
Validate tracker losses against first-party signals. If a rank tracker shows a disappearance but Search Console impressions, organic sessions, and conversions remain stable, you do not yet have evidence of a business-impacting loss.
Record index status. Inspect representative affected URLs in Google Search Console. Classify each as indexed, excluded, blocked, redirected, canonicalized elsewhere, or unresolved. Do not use a position-beyond-100 report as a substitute for this check.
Overlay your own change history. Mark deployments, migrations, template edits, canonical changes, robots directives, internal-link changes, content updates, redirects, and analytics releases that occurred near the loss.

Your working sheet should include the URL, query cluster, pre-update visibility, post-update visibility, clicks, impressions, conversions, index status, page type, template, last material edit, and known technical changes. Add stable peer pages from the same section. A comparison group helps you distinguish a template problem from a weakness limited to individual pages.

Separate four problems that can look identical in a dashboard

Ranking displacement: the URL remains indexed, but competing pages now rank above it for the same queries.
Indexing or canonicalization failure: Google cannot index the intended URL, selects another canonical, or encounters a directive that changes eligibility.
Demand or search-result change: search volume, query mix, or result presentation changes while the page’s underlying eligibility remains intact.
Measurement failure: analytics, rank-tracker configuration, country, device, search type, or reporting logic changes without a matching loss in first-party search visibility.

Each problem requires a different response. Rewriting an accidentally non-indexable page does not fix the directive. Reversing a technical deployment does not help when the page remains indexed but no longer earns its previous position. Classification prevents that kind of expensive mismatch.

Audit weak patterns without inventing an update target

The public numbers do not reveal why particular URLs lost. Treat every proposed cause as a hypothesis to test against your affected and unaffected pages. Start with the differences that repeat across a meaningful cluster.

Check whether every page has a distinct job. Group pages by search intent, not merely by keyword. If several URLs offer substantially the same answer, identify which one should be the primary destination and whether the others serve a genuinely separate need.
Compare affected pages with stable peers. Look for repeated differences in specificity, completeness, factual support, authorship, maintenance, navigation, and the clarity of the answer. A single weak page proves little; a pattern across one template or content program is actionable.
Inspect scaled-content footprints. Review pages produced from the same template, feed, database, localization process, or generation workflow. Check whether their unique sections materially change the answer or merely swap names, locations, products, or keywords.
Verify claims and accountability. Pages making consequential claims should make their basis visible. Confirm that citations support the adjacent statement, dates are current where freshness matters, and author or organizational responsibility is clear when it helps the reader judge the information.
Test the path from query to answer. The title, opening, headings, main answer, and supporting detail should serve the same intent. Remove detours that exist only to cover adjacent keywords, and make the decision-critical answer easy to locate.
Check structured data against visible content. JSON-LD should describe the page that users can actually see. Resolve mismatched names, entities, authors, dates, breadcrumbs, products, reviews, FAQs, or other properties. Adding more schema is not a substitute for repairing a weak or redundant page.
Inspect internal signals. Confirm that important pages are reachable through useful internal links, sit in a coherent information architecture, and are not competing with multiple near-duplicate URLs for the same role.

Do not automatically classify AI-assisted content as the cause. The available measurement did not divide pages by how they were written. Evaluate the published result: whether it is accurate, distinct, accountable, maintained, and useful for the query. The same standard applies to human-written, generated, translated, programmatic, and hybrid workflows.

Competitor analysis needs the same discipline. For each important lost query, compare the page now winning with yours. Record the concrete difference: a better-aligned format, more direct answer, stronger evidence, clearer entity coverage, more usable tool, or a genuinely different intent. Do not reduce the comparison to word count, schema volume, or domain authority without evidence that the factor explains the repeated pattern.

Stage recovery work so every change teaches you something

A modular website model moves through separate work zones from an untouched baseline to a single-component repair and a stable reconnected structure.

Prioritize by certainty and reversibility. A confirmed technical defect is a more defensible first repair than a speculative sitewide rewrite. A concentrated group of affected pages is a safer test cohort than the entire domain.

Evidence you have	Best next action	What to avoid
Unexpected noindex, robots blocking, redirect, canonical mismatch, or broken rendering	Repair the technical defect and verify representative URLs	Rewriting content before restoring index eligibility
Losses concentrated in one template or directory	Compare affected pages with stable peers, repair a small cohort, and validate the template	Changing unrelated sections of the site
Several indexed pages overlap on the same intent	Choose a primary destination and consolidate only where the pages do not serve distinct needs	Mass deletion or blanket redirection without a URL-level map
Winning pages repeatedly satisfy an intent yours misses	Close the specific content, evidence, or format gap on a test cohort	Copying competitors or expanding every page indiscriminately
Only a third-party tracker shows a decline	Confirm the loss in Search Console, analytics, and index checks	Launching recovery work from one measurement alone

Before editing, save the baseline for every test URL and write down the reason for the change. Keep the first cohort internally consistent: the same template, intent class, or identified defect. Avoid mixing content rewrites, URL changes, schema expansion, navigation changes, and redirect work in one release. If visibility changes afterward, a bundled release leaves you unable to tell which intervention mattered.

Monitor direction frequently, but make decisions from comparable windows rather than a single day’s rank. Track impressions and query coverage first, then clicks, qualified sessions, and conversions. A partial ranking return that brings no valuable traffic is not the same as business recovery.

No recovery timetable can be derived from the August measurement. It compares rankings before and after the update; it does not follow repaired sites or establish when Google will reassess a changed page. Treat promises of recovery within a fixed number of days as unsupported.

Your next move is concrete: export the 20 largest page-query losses and place them beside 20 stable peers. Mark index status, template, intent, recent changes, and conversions. That sheet should tell you whether you have a technical emergency, a concentrated content problem, or tracker noise. Make one cohort-sized change from that evidence and preserve the baseline for the next decision.

References

Search Engine Land – Google’s August 2026 spam update hit rankings harder than normal

August 27, 2026

Google Display to Demand Gen Migration: A Practical Runbook

If your standalone Google Display campaigns depend on Manual CPC, portfolio bidding, HTML5 ads or tightly constrained audience targeting, the move to Demand Gen is not a simple campaign rename. Some of those controls will not survive the migration, and pretending they will can leave you diagnosing a strategy change as if it were a temporary performance dip.

Your safest approach is to separate migration from expansion. First reproduce the campaign as closely as Demand Gen allows. Confirm that bidding, creative, audiences, conversion signals and spending behave as expected. Only then test Discover, Maps, additional formats or other Demand Gen capabilities.

The deadline matters, but the unspecified date matters more

The ability to create new standalone Display campaigns will be disabled permanently in January 2027. Google expects automatic migrations later in 2027, but it has not specified when those migrations will begin.

That gap is a planning risk. Waiting for automatic migration means you may lose control over whether the change lands near a product launch, seasonal promotion, reporting deadline or peak sales period. Migrating deliberately gives you a chance to resolve incompatibilities and choose a period when your team can watch the account closely.

The migration tool began appearing through a phased rollout in June after the May announcement, so availability can differ between accounts. When the tool is available, it can update a live campaign while preserving the previous 42 days of performance history. That continuity is intended to reduce the new campaign’s learning period, not eliminate performance volatility.

You also do not have to adopt every Demand Gen network during the move. Demand Gen supports individual network selection, and the migration tool initially creates a Google Display Network-only Demand Gen campaign. Other networks can be added afterward. Use that separation: migration should answer whether the replacement works; expansion should answer whether new inventory adds value.

Audit the features that will not transfer cleanly

Campaign components are sorted on a workbench, with compatible modules passing through an inspection gate and incompatible controls set aside in amber trays.

Build a compatibility sheet before touching the migration control. For every Display campaign, record its current bid strategy, targeting logic, creative formats, data dependencies, measurement studies and business objective. Then mark every feature that requires a replacement.

Display campaign dependency	Demand Gen status	Decision to make before migration
Target CPA, Target ROAS or Maximize Clicks	Supported	Confirm the selected strategy still matches the campaign objective and that its conversion inputs remain appropriate.
Manual CPC, Viewable Impressions or Pay for Conversions	Not supported	Select a replacement strategy and document how success will now be judged.
Bid adjustments, seasonality adjustments or portfolio bidding	Not supported	Identify what business rule each control handled and decide how you will manage that requirement without it.
Business Data feeds	Not currently supported	Do not migrate a feed-dependent execution until you have a supported alternative. Availability has been described as coming, but without a specific date.
Uploaded HTML5 ads or third-party ads	Not currently supported	Rebuild the creative in a supported format or wait. Support is planned for late 2026, but a roadmap date should not be treated as a delivery guarantee.
Brand Lift or Search Lift studies for GDN	Not supported	Decide whether the campaign can move without those studies or requires a different measurement plan.

The supported bidding options are Target CPA, Target ROAS and Maximize Clicks. That does not make them interchangeable. Maximize Clicks is aligned with traffic acquisition. Target CPA requires a meaningful conversion action and a cost-per-acquisition objective. Target ROAS makes sense only when the conversion values being supplied reflect the value you actually want the system to pursue.

Do not choose the nearest-looking setting just to clear the migration screen. Write down what the old strategy controlled and what the replacement will optimize. A campaign moving from Manual CPC to automated conversion bidding, for example, is undergoing a buying-strategy change as well as a platform change. Its before-and-after results need to be interpreted accordingly.

Creative needs the same discipline. Business Data feeds, uploaded HTML5 ads and third-party ads are not currently supported. HTML5 and third-party ad support is planned for late 2026, while no precise availability date is stated for Business Data feeds. If one of those formats is essential to the campaign, the missing replacement is a migration blocker, not a minor setup detail.

Use a controlled six-step migration runbook

Six connected workstations show campaign inventory, duplication, configuration, verification, launch, and monitoring while the original setup remains on a parallel rail.

A controlled migration gives you a clean baseline and limits the number of explanations for any change in performance. Use the same runbook for each campaign so that results are comparable across the account.

Capture the baseline. Export at least the same 42-day performance window the migration tool can retain. Record the campaign budget, bidding method and target, conversion actions, audiences, creative formats and any account-level process that depends on the campaign. Save the date and time of the export.
Map every unsupported dependency. Use the compatibility table above. Assign a replacement, owner and decision date to each unsupported bid strategy, adjustment, feed, creative format or lift study. Do not begin while an essential dependency remains unresolved.
Choose the cutover window. Performance may fluctuate after migration, so avoid placing the first move immediately before a peak trading period. Pick a time when someone can inspect delivery and spending during the rest of that day and over the following reporting periods.
Account for same-day spending. The newly migrated campaign will not respect the amount the old campaign already spent earlier that day. That creates a risk of more combined same-day spend than you expected. Watch total account spend at the cutover rather than assuming the new campaign knows how much daily budget has already been consumed.
Verify the migrated campaign before expanding it. Confirm that the new Demand Gen campaign is restricted to Google Display Network inventory, as the migration tool is designed to configure it. Check the budget, bid strategy, conversion inputs, audience setup and live creative against your migration sheet.
Hold expansion until the replacement is interpretable. Let the Display-only campaign establish a usable post-migration pattern before adding Discover, Maps or materially different creative. When you do expand, change one major dimension at a time and record the date.

The fourth step deserves special attention. If a Display campaign has spent a large portion of its daily budget before migration, the new campaign can still begin without credit for that earlier spending. You do not need to predict the exact effect. You do need an operator watching the combined spend and authorized to respond if delivery departs from the day’s plan.

During the first post-migration review, compare more than totals. Look at spend, delivery, conversion volume, conversion value and the metric tied to the chosen bid strategy. Annotate the migration so nobody later mistakes the cutover for an unexplained market movement. If you change the bid target, network mix and creative simultaneously, you will have no reliable way to tell which change produced the result.

Rebuild audience and measurement assumptions for Demand Gen

The deepest change is not in the interface. Demand Gen uses audiences and conversion signals as inputs to a more automated buying system, so controls that once acted as boundaries may now act as guidance.

Treat Lookalike Audiences as signals, not fences

As of March 2026, Lookalike Audiences changed from restrictive targeting to audience suggestions. Your first-party seed still informs the model, but Google can reach high-intent users outside the similarity thresholds associated with the seed.

If you previously relied on a Lookalike segment to define who could receive an ad, revise that assumption before migration. The segment now supplies direction rather than a hard perimeter. Judge it by the outcomes it helps generate, and use the campaign’s available network controls to govern where ads can run.

Create required Lookalike segments well before the campaign needs them. A new segment can take up to 96 hours to populate. Building it on the day of migration can leave you troubleshooting a campaign whose intended audience signal is not yet ready.

Decide whether view-through conversions belong in optimization

Demand Gen can optimize bids toward users who view a YouTube or Discover ad, do not click it, and convert later. This view-through-conversion optimization can provide an additional signal when click-led conversion volume is too limited for conversion-focused bidding.

That capability is not automatically an improvement for every account. Decide whether a later conversion following an ad view represents an outcome you want the bidding system to pursue. Make the decision explicitly, document it and avoid comparing a view-through-optimized campaign with a click-focused predecessor as though their optimization inputs were identical.

Billing also changes in a specific configuration. Google has announced that Demand Gen campaigns running on Discover with view-through-conversion optimization will move from CPC to CPM billing. In other words, cost is tied to impressions rather than clicks. This does not affect a Demand Gen campaign serving only on the Display network, but it becomes relevant as soon as you add Discover under that optimization setup.

Before enabling that combination, update the reporting brief. Stakeholders should know that a change in click volume or CPC no longer describes the entire buying model. Mark the billing transition date and evaluate delivery, cost and conversions within the new setup rather than forcing a direct CPC-era comparison.

Add new reach as a test, not a migration default

Demand Gen can extend reach into Discover and Maps, offers formats unavailable in standalone Display, and includes additional generative image tools. It also provides more ways to use YouTube creative. An Affiliate Partnership boost for organic YouTube affiliate videos is in pilot, so it should be treated as an emerging option rather than a dependency in your migration plan.

Test those capabilities after the Display replacement is stable. State one hypothesis for each expansion: the audience you expect to reach, the conversion signal the campaign will optimize and the result that would justify continued spend. Add one network or major creative approach at a time. Otherwise, Demand Gen’s wider inventory can obscure whether the migration itself succeeded.

Key takeaways

New standalone Display campaign creation ends in January 2027; automatic migration is expected later in 2027, but its start date remains unspecified.
The migration tool can retain 42 days of history and initially creates a Display Network-only Demand Gen campaign.
Manual CPC, Viewable Impressions, Pay for Conversions, bid adjustments, seasonality adjustments and portfolio bidding require alternatives.
Business Data feeds, uploaded HTML5 ads, third-party ads, Brand Lift studies and Search Lift studies have support gaps that may block some migrations.
Same-day spend from the old campaign is not credited against the newly migrated campaign’s budget, so the cutover needs active spending oversight.
Lookalike Audiences are suggestions rather than restrictive targeting, and a new segment can take up to 96 hours to populate.
Discover inventory using view-through-conversion optimization is moving from CPC to CPM billing; Display-only delivery is not affected by that billing change.

Start by opening your highest-spend standalone Display campaign and marking every compatibility-table row as supported, replaceable or blocked. If a blocked item has no approved alternative, solve that first. If the campaign is clear, choose a monitored migration window, preserve the Display-only network setup and put any Discover, Maps or creative expansion into a separate test plan.

References

Search Engine Land — Moving from Google Display to Demand Gen: What you’ll lose and gain

August 27, 2026

AI Watermarks: What Actually Matters for Search Quality

You are about to publish an AI-assisted page, and a watermark or detector score has turned an editorial decision into an SEO worry. The useful question is not whether a machine touched the draft. It is whether the finished page earns its place in search results and AI-generated answers.

Treat the watermark as a clue about production, then audit the work itself. That keeps your attention on the failure modes that can damage visibility and trust: unsupported claims, recycled ideas, generic advice, near-duplicate pages, and automation without accountable review.

A watermark describes provenance, not quality

A machine-readable watermark associated with Claude-generated text can indicate that AI participated in the production process. It cannot tell a reader who originated the idea, how much of the finished work came from the model, whether its claims are correct, or whether the page is useful.

Those questions belong to three separate layers:

Signal	What it can tell you	What it cannot establish
AI watermark or provenance marker	An AI system participated somewhere in generation	Originality, accuracy, usefulness, or the extent of human contribution
AI detector score	A tool estimates that the text resembles patterns it checks	Certain authorship, reader value, or search quality
Byline or author markup	A named person or organization accepts ownership	That the information is distinctive or deserves citation

Conflating these layers leads to the wrong work. A team may rewrite sound sentences solely to reduce a detector percentage while leaving weak reasoning, unverified claims, and duplicated ideas untouched. The page then looks less detectable without becoming more valuable.

AI use also is not one uniform editorial practice. Asking a model to organize your notes, challenge an argument, expose missing questions, or improve a draft is materially different from publishing its first response. In both cases, however, the publisher remains responsible for the result. If you would be uncomfortable defending the page once its AI involvement became visible, send it back through editorial review instead of trying to disguise the workflow.

Search risk comes from low-value automation, not AI involvement alone

Google has not treated AI authorship as an automatic reason to penalize content. Its relevant distinction is what automation produces and why it was produced. Generative AI can help with research and structure. The problem emerges when automation is used to manufacture large amounts of low-value material primarily to manipulate rankings.

That is the mechanism behind the SEO risk. Giving a model broad publishing autonomy makes it cheap to produce generic recommendations, unsupported assertions, lightly altered pages, and summaries of information already present throughout the search results. Scaling those defects does not create authority. It multiplies reasons for search systems and readers to ignore the site.

There is likewise no universal rule that a Claude watermark excludes a page from AI-generated answers. Answer engines still need material worth retrieving, citing, or synthesizing. A process signal does not erase original evidence, firsthand knowledge, a useful framework, or a defensible opinion. It also cannot rescue a page that merely repeats the prevailing consensus in slightly different words.

Hold publication when any of these conditions is true:

Your editor cannot name the page’s unique contribution in one sentence.
A group of pages differs mainly by replacing a location, product, industry, or target keyword.
The copy makes factual claims that no reviewer has traced and verified.
The only reason for creating the page is that a keyword exists, not that a defined reader needs the answer.
No named person owns the final decision to publish, correct, or withdraw the content.
The page would lose nothing important if it were replaced by a generic search-results summary.

This test applies equally to human and AI writing. A human-written page does not gain a competitive advantage merely by being human if it offers the same information as a thousand other pages. A watermarked page does not lose a genuine advantage merely because AI helped shape its presentation.

Use a citation-worthiness audit before publication

An article page surrounded by reference materials, with visual lines linking parts of the page to supporting sources and one area under a magnifying lens.

A normal copy edit is not enough for AI-assisted work. You need a release process that tests why the page should exist, which claims deserve trust, and what an answer engine could retrieve from it. Use this sequence for every page, whether AI wrote one sentence or most of the first draft.

Define the page’s job. Complete this sentence before drafting: This page helps a specific reader complete a specific task under a specific constraint. A broad topic such as AI content quality is not a job. Deciding whether to publish an AI-assisted landing page after detecting a watermark is.
Name the unique contribution. Write down what the reader can obtain here that is difficult to obtain elsewhere. It could be original data you actually collected, a documented procedure, firsthand operational knowledge, a new comparison, or a reasoned interpretation. New wording is not new value.
Build an evidence ledger. Record the support for every claim on which the reader might base a decision. Include the relevant URL, named authority, date or product version when needed, verification status, and reviewer. Do not ask a model to invent citations or treat its confidence as verification.
Give AI bounded roles. Decide in advance whether the model may organize notes, propose an outline, challenge assumptions, generate alternatives, or improve clarity. Do not let the same automated process generate a claim, declare it verified, approve the page, and publish it without independent review.
Run the genericity test. Replace the important nouns with those from another company or topic. If the paragraph still sounds equally plausible, it probably contains interchangeable advice. Cut it or add the missing evidence, constraint, example, or point of view.
Make the useful answer retrievable. Put the direct answer close to the heading that asks the question. Keep its supporting evidence adjacent. Use stable entity names, descriptive headings, and a table only when the reader is genuinely comparing fields. Appropriate structured data can clarify what a page contains, but it cannot turn recycled copy into evidence.
Assign a real owner. Name the person responsible for checking the claims and maintaining the page. Use a byline, credentials, and author markup only when they accurately represent that ownership. A byline can support identity consistency for AI crawlers, but it cannot make repetitive information citation-worthy.

The release gate: can you defend the finished page?

Before the page enters your CMS workflow, require clear answers to four questions:

Is it accurate? Every consequential claim has traceable support, and uncertainty is visible instead of being edited away.
Is it original enough to justify existing? The unique contribution is information, reasoning, or experience, not merely different phrasing.
Is it useful to the intended reader? That reader can make a decision, complete a task, avoid a mistake, or understand a meaningful distinction after reading it.
Will someone stand behind it? A named owner is prepared to explain the reasoning, correct errors, and accept scrutiny of the production process.

If one answer is missing, the page is not ready. A lower AI score would not change that decision.

Measure the finished page instead of chasing an AI percentage

A layered page passing through a transparent inspection frame while a stack of nearly identical thin pages fades into the background.

An AI score cannot tell you whether a reader finished the page, trusted it, shared it, subscribed, or completed the intended action. It also cannot tell you whether an answer engine cited the page accurately. Those are outcomes a detector percentage does not measure.

Build reporting around the page’s actual job:

Outcome	What to observe	What to do when it fails
Search discovery	Index status, impressions for relevant queries, and qualified organic visits	Check technical access, intent alignment, internal discovery, and whether the page adds enough value to compete
AI-answer visibility	Whether relevant answer surfaces cite, link to, or accurately represent the page	Strengthen distinctive facts, make the answer easier to extract, and keep evidence beside the claim it supports
Reader usefulness	Completion of the action the page was designed to support, plus meaningful shares, subscriptions, or return visits where relevant	Find the unanswered question, missing proof, or unnecessary friction instead of adding more generic copy
Editorial trust	Corrections, challenged claims, review failures, and substantive reader feedback	Repair the evidence and workflow before increasing production volume

Do not mislabel all of these observations as direct ranking factors. They serve different purposes: search metrics show discoverability, citation checks show retrievability, and reader or business outcomes show whether the page fulfilled its intended role. Together, they provide a more useful diagnosis than a single AI-likelihood score.

A detector result can still trigger a process check. An unexpected score may prompt you to confirm how a draft was produced, whether your editorial policy was followed, and whether required review occurred. It should not become a target that writers optimize at the expense of clarity. Rewriting accurate text until a detector approves its style is not content improvement.

The same logic applies to watermark-removal tools. If removal is the only change, the page gains no new evidence, insight, or usefulness. Review the claims, eliminate sameness, add the missing contribution, and document accountable ownership before spending effort on the provenance signal.

Key takeaways

An AI watermark can indicate something about production; it cannot determine accuracy, originality, usefulness, or search quality.
AI involvement is not an automatic search penalty. Low-value content produced at scale to manipulate rankings is the relevant risk.
Use AI for bounded tasks such as organization, critique, and editing, while keeping evidence checks and publication approval independent.
Bylines, author markup, headings, and schema can clarify ownership and meaning, but they cannot make generic information worth citing.
Judge a page by search discovery, answer-engine citations, reader usefulness, and editorial trust rather than an AI detector percentage.
If revealing AI involvement would make your team reluctant to defend the work, improve the work before publishing it.

For your next AI-assisted page, require four fields before publication: the intended reader, the unique contribution, the evidence ledger, and the accountable owner. Leave the page in draft if any field is blank. If all four withstand scrutiny, publish the work and stand behind it, watermark or not.

References

Search Engine Land — If an AI watermark scares you, your content may be the real issue

August 27, 2026

Google Search Result URL Redirects: What SEOs Should Check
If your rank tracker suddenly disagrees with what you can see in Google, pause before changing the page. Google is inserting a Google-owned redirect between some search results and their destination pages, and that can disrupt the measurement layer without changing the ranking itself.

Your first job is to identify which link in the chain changed: Google’s result, your tracking provider’s collection process, or your site’s actual search performance. A short, structured audit can keep a reporting incident from turning into an unnecessary content, schema, or technical SEO project.

Read this as a link-delivery change, not a site redirect

A conventional organic result used to expose the destination page’s full URL as its clickable target. Under the new behavior, the result can point first to a Google URL resembling google.com/goto?url=[hashURL]. Google processes that intermediate request and then sends the searcher to the destination.

That extra hop matters because software inspecting the result may initially see a Google-owned URL instead of your page URL. The searcher can still see the displayed site URL under the result title, but the browser’s link preview may no longer reveal the complete destination before the click.

Google describes the rollout as part of its technical response to evolving abuse and an effort to protect its services and users. That explanation is broad. It does not identify every type of abuse involved, so claims about one specific target or enforcement method should be treated as interpretation rather than confirmed implementation detail.

Most importantly, this is not a redirect configured on your server. It does not, by itself, show that Google changed your canonical URL, replaced your indexed page, altered your structured data, or applied a ranking penalty. Your 301 and 302 rules remain separate from the redirect Google places inside its own result interface.
- Do not add a site redirect to compensate. You cannot remove Google’s intermediate hop from your server, and another redirect would only add complexity to the destination path.
- Do not change canonical tags or JSON-LD because a tracker exposes a Google URL. First confirm whether the tool is merely failing to resolve the final destination.
- Do not treat the redirect as evidence of an algorithm update. A ranking change requires ranking evidence; a changed link target is not enough.
Identify which part of your search stack is exposed

The effect depends on how you interact with the result. A person clicking normally may notice little beyond the obscured link preview. A system that parses result-page links, classifies domains, or associates positions with landing URLs has more ways to fail.
- Searchers: Watch for the displayed domain and page label under the result title. The visible destination cue remains available even when the clickable target is routed through Google.
- SEO teams: Expect possible discontinuities in third-party rank, visibility, competitor, and landing-page reports. An abrupt dashboard change may reflect collection behavior rather than a change to your pages.
- Rank-tracking providers: A parser that assumes every organic link exposes the publisher’s URL may return a Google URL, an unknown destination, or no recognized result. Tools that resolve the redirect may face a different collection path than tools that only inspect the original markup.
- SERP scrapers and AI systems: The redirect can create additional friction for systems gathering destinations from Google results. That does not automatically affect an AI crawler visiting your website directly; the two access paths are different.
- Google Search Console users: The working expectation is that Search Console is not affected by this result-link change, but Google’s public confirmation does not provide an explicit guarantee. Use it as an independent comparison signal, not as proof that every third-party observation is wrong.
This distinction is especially important for AI visibility reporting. If a platform builds part of its dataset by scraping Google results, its measurements may inherit the redirect problem. A decline in that platform does not establish that your pages became less accessible to ChatGPT, other frontier models, or direct web crawlers. Ask how the vendor collects each reported signal before you combine those signals into one visibility score.

Audit tracker anomalies before changing the site

The redirect is being rolled out rather than appearing as a single universal switch. Different providers, locations, and collection environments may encounter it at different points. That makes the shape and timing of the anomaly more useful than one isolated keyword check.
1. Preserve the last clean comparison. Export the affected dashboard before filters, recalculation, or vendor corrections change the historical view. Record the date you first noticed the discrepancy, the search engine, market, device configuration, project, and affected keyword set.
2. Localize the break. Check whether the anomaly affects every tracked keyword or only one market, device type, project, or provider. A sitewide overnight gap confined to one tool looks different from a gradual decline concentrated in a group of pages.
3. Separate position collection from URL resolution. Determine whether the tool lost the result entirely, still reports a position but cannot identify the landing page, or now attributes the result to google.com. Those are different failures and should not be combined into a generic rankings-down label.
4. Inspect a small set of affected results manually. Confirm that the result is visible, the displayed domain is yours, the click reaches the intended page, and the underlying result link uses the new Google redirect. Manual checks are samples, not a replacement for tracking, but they can expose an obvious collection mismatch.
5. Compare independent signals by direction, not exact totals. Review Search Console queries, pages, clicks, impressions, and average position around the same period. Search Console and a rank tracker measure search differently, so their numbers need not match. You are looking for a shared break in timing and scope.
6. Send the provider reproducible evidence. Include the first affected date, search engine, market, device setting, several example queries, the expected destination, the reported destination, and screenshots or exports. Ask whether the goto redirect affects position detection, landing-page resolution, or both.
Avoid making broad on-page changes while this audit is open. Rewriting titles, altering internal links, replacing schema, and changing canonicals at the same time will create new variables. If the original problem is external data collection, those edits cannot repair it and may make the real diagnosis harder.

Separate a collection failure from an SEO loss

No single metric settles the diagnosis. Use several observations to decide which explanation currently has the strongest support.
- The result appears manually, the click reaches the right page, and only one tracker loses it: a collection or parsing problem is more plausible than a ranking loss.
- The tracker still reports a position but loses the landing URL: destination resolution is the leading suspect. Check whether the reported URL is a Google goto address before touching your canonical setup.
- Several third-party reports change at the same time but share a collection provider: they may not be independent confirmations. Establish whether the products depend on the same underlying data source.
- Search Console and third-party visibility decline across similar queries and pages: investigate a genuine search-performance problem. The goto redirect alone is not a sufficient explanation for agreement across independent signals.
- The result is present but the click fails or lands on the wrong page: treat that as a user-facing path problem. Verify your own redirects, final response, and destination separately from the tracker issue.
- Nothing changed outside the underlying link target: document the rollout and keep monitoring. A technical change in Google’s interface does not require a technical change on your site.
Be equally careful with competitive reporting. If a tool starts classifying goto URLs as Google domains, domain-level share-of-voice data can become distorted across many sites at once. Before concluding that a competitor gained visibility, check whether the report also shows more unknown URLs, missing domains, or unresolved landing pages.

Your schema strategy does not need a special markup response. Structured data describes entities and page content on your site; it does not control the outbound link wrapper Google uses on its own search page. Continue validating schema for its intended purpose, but do not use a JSON-LD deployment as a remedy for off-site rank-tracker collection.

Key takeaways
- Google can route an organic result through a google.com/goto URL before sending the searcher to the publisher’s page.
- The redirect is a Google-side link-delivery measure, not a redirect you need to reproduce or counteract on your server.
- Third-party tools that extract or resolve result URLs have more direct exposure than ordinary searchers or your site’s canonical configuration.
- A tracker anomaly becomes actionable SEO evidence only when independent signals support the same timing, pages, and queries.
- Preserve the affected data, classify the failure, compare Search Console directionally, and give your provider reproducible examples before editing the site.
Add the rollout to your measurement-change log and keep first-party performance signals separate from vendor-collected visibility data. If a discrepancy appears, ask the provider whether it can recognize the result and whether it can resolve the final URL. Those two answers will tell you whether you have a reporting repair to wait for or an SEO problem to investigate.

Until the evidence points to your site, leave the content, internal links, canonicals, redirects, and structured data alone. The safest next move is a cleaner diagnosis, not a larger deployment.

References
- Search Engine Land – Google confirms deploying goto URL redirects to search results links
August 27, 2026