Google AdsOfficial01
Google Ads Is Moving Away From Required Language Targeting
Google officially states that starting in September 2026, campaign language settings are no longer required for Search campaigns. The system increasingly determines language from the search term itself, user language settings, and previous language behaviour, while AI-based ad group prioritization is intended to select the most relevant creative for the query language. For Toronto and the GTA, this matters because of the highly multilingual audience: an English-only campaign structure can no longer be treated as a firm boundary separating English, Russian, French, or other users. This does not mean advertisers should mix every language into one ad group without control. The landing page, headline, offer, and call handling still need to match the user's language. Search-term review and multilingual creative coverage therefore become more important than the old campaign-language checkbox.
Business impactLocal lead-generation accounts may capture valuable demand outside their primary campaign language, but they also face a higher risk of serving mismatched creative or landing experiences.
Google Ads Help — About language targeting ↗
Do this nextReview Search Terms from the past 30 days in one Toronto account and identify commercially relevant queries outside the primary language. Add appropriate RSA and landing experiences where justified, then compare conversion rate and qualified leads by language group.
AnalyticsOfficial02
Google Expands First-Party Measurement Through Data Manager and Data Strength
Google announced on September 10 an expansion of its measurement stack. Data Manager is being integrated more deeply into Google Analytics and Display & Video 360, enhanced conversions are expanding, and the Data Manager API now follows the IAB Tech Lab Event and Conversions API standard. Google Ads is also introducing the Data Strength Uplift Metric to estimate additional conversions recovered through an advertiser's first-party data setup. Meridian GeoX has moved out of beta and into global availability for causal geographic experiments. For local-service businesses, the larger shift is clear: advertising systems increasingly depend on high-quality first-party signals rather than cookie-based attribution alone. A recovered conversion is not automatically a qualified lead, however. If the CRM cannot distinguish a genuine booking from spam, duplicate forms, or low-value calls, automated bidding will still optimize toward the wrong business outcome.
Business impactCRM integration, call tracking, offline conversion imports, and lead-quality validation become increasingly valuable parts of an ongoing marketing retainer rather than optional analytics work.
Google Ads & Commerce Blog — Data Strength updates ↗
Do this nextChoose one Google Ads client and audit the chain from Google Ads to GA4, forms or call tracking, CRM, and qualified-lead status. Confirm that a qualified outcome can be separated from a generic conversion and, where possible, returned to Google Ads.
WebsitesOfficial03
WordPress Prepares for Its Next Cycle and Agent-Driven Workflows
The WordPress Developer Blog published its September developer roundup following WordPress 7.1. Gutenberg 23.8 and 23.9 improve schema support for responsive and pseudo-class states, add declarable keyboard shortcuts, update DataViews, and continue groundwork for WordPress 7.2. More strategically, WordPress Playground now supports WebMCP, a draft browser API that can expose actions as tools an AI agent may call inside a browser-based WordPress environment. This is developer infrastructure rather than a production-ready website feature, but the direction is significant: WordPress is gradually becoming an environment where agents can perform controlled actions rather than only read site content. For agencies today, the immediate priorities remain WordPress 7.1 compatibility, theme.json validation, and safe testing of Gutenberg-dependent functionality rather than deploying experimental agent tooling directly to client sites.
Business impactFor Allsite Studio, this is an early signal toward agent-ready WordPress operations including page generation, QA, controlled maintenance, and content workflows that rely less on brittle UI automation.
WordPress Developer Blog — What’s new for developers? September 2026 ↗
Do this nextDo not deploy WebMCP to production yet. Create a staging or Playground test for one internal workflow such as reading site structure, calling a safe custom ability, or checking a generated page. In parallel, run existing sites through a WordPress 7.1 compatibility checklist.
AI SearchOfficial04
Cloudflare Will Change AI Crawler Defaults on September 15
Cloudflare is preparing updated AI bot defaults for September 15. For new domains, bots classified as Training or Agent will be blocked on pages displaying advertising while Search use remains allowed; mixed-purpose crawlers are also subject to stricter restrictions. Cloudflare says similar defaults will apply to existing free customers who have not changed their settings. This creates an important operational issue for AI visibility: a site owner may believe the site is open to AI discovery while the CDN policy permits a search crawler but blocks an agent or training crawler. For ordinary local-service sites, content monetization is rarely the primary objective, so overly broad blocking may cost more visibility than it protects. Checking robots.txt alone is therefore no longer sufficient when Cloudflare or another edge layer is actively classifying and filtering AI bots.
Business impactAI crawler accessibility becomes a technical visibility layer alongside crawling, indexing, structured data, and conventional robots controls.
Cloudflare Docs — Block AI Bots ↗
Do this nextBefore September 15, open Cloudflare Bot settings for at least one priority domain. Record the policy for Search, Training, and Agent bots, align it with the site's business objective, and avoid indiscriminately blocking AI Search on lead-generation websites.
Local SEOIndependent Test05
Citations Are Becoming More Relevant Again — This Time for AI Recommendations
Whitespark published a September 10 playbook arguing that citations are becoming strategically important again in the AI Search era. The model is different from old mass-directory submission: value comes from appearing on sources that real users encounter and that AI systems surface or cite. Whitespark separates structured citations on directories and review platforms from unstructured mentions on news sites, blogs, industry resources, podcasts, sponsorship pages, and similar third-party sources. This is local SEO research and expert analysis, not an official Google or OpenAI ranking-factor statement. The practical point is still strong: consistent business facts and independent third-party corroboration help systems understand who a company is, what it does, whom it serves, and why it might deserve recommendation. Quality, relevance, and visibility of the source matter more than building hundreds of low-value listings.
Business impactLocal SEO and AI visibility are converging. Citation work can be repositioned as entity and AI visibility work based on real competitor-source research instead of commodity NAP submissions.
Whitespark — 2026 Playbook: How to Optimize Citations for AI Visibility ↗
Do this nextRun five best-service-in-city prompts in Google AI, ChatGPT, and Gemini for one client. Record domains used to support competitor recommendations and identify high-value sources where competitors appear but the client does not.
Business OpportunityIndependent Test06
Industrial AI Search Shows That Mentions and Citations Are Different Problems
Semrush published manufacturing-focused AI Search research on September 8 showing an important distinction between brand mentions and cited websites in AI answers. In its tracked dataset, AI Overviews appeared across 57% of manufacturing-related search volume, up from 38%, while the brands most frequently mentioned were not necessarily the domains most frequently cited. AI referral traffic remained a small share of overall website traffic. This is Semrush research rather than Google data for Ontario, so the percentages should not be transferred directly to steel fabrication or data-centre contracting. The strategic model is highly relevant, however. A company can have a technically authoritative website that earns citations while still being weak in the recommendation layer, or it can be a well-known brand whose own pages are rarely used as sources.
Business impactFor Weld Rich & Steel and the data-centre vertical, AI visibility should be separated into entity prominence and source authority rather than treated as one generic score.
Semrush — AI search and manufacturing SEO study ↗
Do this nextTest five commercial prompts around structural steel and data-centre construction in Ontario. Separately record companies recommended and URLs cited, then determine whether the gap is brand/entity prominence, technical authority content, or both.