REX · Footprint SEO Command Center

REX Radar — November 16, 2026

Persona: REX (Matt Diamante / Get-Found school). Ingest digest 2026-11-16T14:30Z — 8 new RSS items (SER 4, Google Search Central 1, blog.google Search 1, SEJ 1, Growth Memo 1) + search-ingest sweep via Google News RSS fallback (primary provider quota-exhausted, 429). Coverage note: last radar Nov 5; no radar Nov 6–15. Module 99 published today — claiming and running your business profile inside ChatGPT.

Status Board

#SignalTagSourceDate
1ChatGPT Business Hub is live — claim your business, read your ChatGPT clicks. Claimable profile inside ChatGPT with mention counts, website-click counts and discovery topics.HIGHSER (Barry Schwartz) + OpenAINov 10
2ChatGPT Business Agents roll out — the builder pulls from your website. US ecommerce/online-service businesses get a "Start chat" agent; verification check confirms owner control.HIGHSER + Lily Ray / Juozas on XNov 16
3November 2026 core update is mid-rollout; volatility landed Saturday. Announced Nov 10, up to 2 weeks. YMYL chatter reports informational pages displacing commercial ones.HIGHSER flux post + SELNov 10–16
4Search Analytics API adds branded-query, web-multimodal and multi-country/device filters.MEDGoogle Search Central + SERNov 16
5Growth Memo Q4 meta-analysis: 85% of retrieved pages are never cited; 61.7% of domain appearances are ghost citations with no brand mention.MEDGrowth Memo (Kevin Indig)Nov 16
6ChatGPT Ads early data: ~1/3 the revenue per visit of paid search ($0.89 vs $2.45/session; 0.37% vs 1.17% conversion) as cost-target bidding ships.MEDSEJ (Matt G. Southern)Nov 16
7Google tests dropping AI Mode from the search bar / Ask Anything box; AI Mode drops the Gemini label, Gemini 4 Carbon to Pro.MEDSERNov 13–16
8AI Mode ads expand into follow-up questions — single secondary source, unconfirmed.LOWMarkHub24Nov 16
9ChatGPT tests web-only results + "See more" answer button; Bing tests a Web Mode tab.LOWSERNov 16
10Housekeeping: GSC generative-AI report data bug Nov 9–11; AI Mode temporary threads; Google Ads AI Max URL-exclusion clarification; Gemini 4 Hydrogen in Search; Microsoft ad outage notes.LOWMultipleNov 12–16

Signal deep-dives

1. ChatGPT Business Hub: claim the profile, get click data (HIGH — Module 99 basis)

OpenAI launched Businesses in ChatGPT (beta) on Nov 10; Search Engine Roundtable covered it the same day with screenshots. Businesses can claim their business inside ChatGPT, manage the information shown, and see analytics: mention counts, website-click counts, and "discovery topics" — the recurring conversation themes where their site is cited. Verification runs by text, phone call to the main business number, or DNS. Barry's read of the click metric, from the help tooltip: "Number of recorded clicks on links to your website in ChatGPT. Clicks don't confirm website visits or conversions."

REX Take: first time an AI platform has handed us a first-party feedback loop. Until now AI visibility was modeled or inferred — Module 64 and Module 95 both leaned on sampling and proxies. A claimable profile with mention and click counts changes the operating model three ways: (1) accuracy control — the details ChatGPT quotes become something we correct instead of watch go stale; (2) a real denominator — mentions vs clicks separates a retrieval problem (not mentioned) from a brand problem (mentioned, nobody clicks); (3) defensive necessity — an unclaimed profile is a profile someone else can describe for you. The claim flow is 10 minutes. Treat it like GBP in 2015: whoever claims first owns the surface.

Local Watch: all 12 domains are US businesses eligible for the base claim. Start with the properties where an AI answer is the likeliest first touch — xactinsure.net, floridahealthinsuranceweb.com, pattonroofsystems.com, kennesawproroofing.com, acrepairdaily.com, securityservicesroseville.com.

2. Business Agents: the builder reads your own site (HIGH)

SER (Nov 16, 07:31): the ChatGPT Agent builder is rolling out gradually — "starting with eligible ecommerce and online service businesses in the U.S." Profiles with an agent get a "Start chat" button; chats stay private ("Business can't see your chats or your personal info — just overall usage trends"). The Chewy example carried a blue check reading "OpenAI verified that this profile is managed by an owner or authorized representative" — and the agent failed a live product query with "I don't have a live Chewy product catalog connected." Lily Ray on the builder: "it pulls a lot of recommendations out of your website so it's pretty low-effort to get it set up."

REX Take: two operational facts, both ours to use. First, the agent is only as good as what it can reach — the Chewy failure is the tell. No service feed, no pricing, no service-area page, no hours, no plain answers means a polite refusal bot. That's Module 90's feed-first/agent-ready doctrine again: an agent is a conversational front end onto your structured data. Second, the verification checkmark is an ownership signal — the AI-surface equivalent of a verified GBP, and the argument for claiming now rather than watching a squatting profile collect the traffic.

3. November 2026 core update: the flux landed Saturday (HIGH — live)

Started rolling out Tuesday Nov 10, ~1pm ET; Google says up to two weeks. SER's Nov 16 flux post: chatter was muted, then picked up Saturday Nov 14 — "the core update may have kicked in 3-4 days after its announcement" — with third-party volatility tools struggling (their tracking was already degraded) and GSC performance reporting laggy. Google's framing: "a regular update designed to better surface relevant, satisfying content for searchers from all types of sites." The YMYL chatter in that thread is the part to read twice: multiple owners report informational pages displacing commercial pages — "the top 20 is pure info content, no commercial... even if the commercial page is superior in quality, UX, info and helpfulness."

REX Take: do not touch anything for the first 72 hours — Module 96's fix-order doctrine and Module 63's core-update playbook say so, and the reason is now measurable: the tools can't see the update clearly, so any "fix" is a guess against a moving baseline. Freeze content pruning and template changes on the roster until roll-out completes (~Nov 24), snapshot GSC before/after per property, log changes instead of shipping them. The YMYL report is the interesting one: if informational answers outrank commercial pages, the fix for xactinsure.net and floridahealthinsuranceweb.com is not to make pages more salesy — it's to complete the informational layer and carry the next step (quote path, plan comparison, licensed-agent proof). That's Module 92's trust-gap playbook, and it's the right hedge either way.

4. Search Analytics API: branded, multimodal, multi-country/device (MED)

Google Search Central (Nov 16, Daniel Waisberg / Nati Yosephian / Karin Gadasi): the Search Analytics API now supports the three Performance-report filters that were UI-only — brandedClassification for branded vs non-branded, type=webMultimodal for Lens / Circle-to-Search / image-upload performance (also in BigQuery bulk export), and a filterLists field for multiple countries or devices in one request.

REX Take: plumbing for the KPI pivot in Modules 45 and 87. Branded-vs-non-branded in the API automates the single most useful directional metric for AI-era SEO — whether branded demand grows while click share compresses. Multi-country matters for floridahealthinsuranceweb.com's state structure; webMultimodal finally gives visual search an honest baseline. Implementation note: pull the branded split now, while the core update is mid-flight, so you have a pre/post split instead of one blended number.

5. Growth Memo Q4 meta-analysis: retrieval is the bottleneck (MED — doctrine)

REX Take: collapses to one sentence: you cannot optimize your way out of not being retrieved. 85% waste at the retrieval layer means the win is composition, not copy-editing — be in the candidate set for the fan-out queries, not just the head prompt. Practically: Module 4's query fan-out plus Module 70's modifier mastery — build the adjacent pages (cost, comparison, "how long does it take", "is it worth it", "who's best in [city]") because a third of citations come from a query you never targeted. And the number to put in front of clients: 61.7% of the time AI uses your page without naming you. Citation is table stakes; brand mention is the campaign.

6. ChatGPT Ads: a third of the revenue per visit (MED — budget)

SEJ (Matt G. Southern, Nov 16): OpenAI shipped cost-target bidding this week (ads launched February; $1B annualized run rate by Aug 31, >100k advertisers). Measured, pooled across 102 sites: $2.45 revenue per paid-search session vs $0.89 for ChatGPT ad sessions (US), 1.17% vs 0.37% transaction rate per session. The viral "52¢ back per dollar vs $3.40" figure is not measured — it multiplies the measured per-visit metric by average CPCs from one ChatGPT account and 16 paid-search accounts.

REX Take: honest read is "not yet a Google Ads substitute, and don't quote the 52¢ number as data." Sequencing stays: own the free surfaces first (Signal 1 — claim, read click data, fix the description) because that traffic costs nothing and compounds, then treat ChatGPT Ads as a test line item. The methodology point matters as much as the numbers — separate measured from modeled before it reaches a client deck.

7. Surface churn: Google tests removing AI Mode, drops the model label (MED)

SER: Google is testing removing AI Mode from the search tab bar and the "Ask anything" follow-up box inside AI Overviews (Nov 13), after earlier tests removing AI Mode buttons from the homepage. Separately (Nov 16): AI Mode no longer shows which Gemini model it uses in the header, and Gemini 4 Carbon is now available to Pro subscribers (previously Ultra only); Gemini 4 Hydrogen arrived in Search around Nov 14.

REX Take: distribution tuning, not retreat — Google A/B tests how hard to push AI Mode while quietly upgrading the model behind it, which means answer quality changes without an announcement you can track. So: any AI-visibility benchmark is model-version-sensitive (log the date, per Module 64), and content should be written to survive a model swap — clear structure, explicit facts, named entities — not tuned to one model's quirks. The vanishing model label also means Google won't give us a stable measurement surface: build on first-party data (GSC, Business Hub clicks) wherever we can.

8–10. Watch items (LOW)

Local Watch

Task Queue

  1. Claim every managed domain in ChatGPT Business Hub — DNS verification where we control DNS (S1–S2).
  2. Screenshot each claimed profile's baseline: mentions, clicks, discovery topics — day one of the first real AI-visibility time series we own (S1).
  3. Build the post-claim fix list: business description, service list, service areas, hours, pricing ranges — the fields an agent needs to answer instead of deflect (S2).
  4. Freeze all on-site changes on managed domains until the core update completes; snapshot GSC per property today (S3).
  5. Add the branded/non-branded API pull to the reporting script and run it across the roster (S4).
  6. Re-run prompt sampling with the four-column split; report named mentions separately from citations (S5).
  7. Update the client-deck methodology slide: measured vs modeled, and retire the "52¢ per dollar" ChatGPT Ads figure before it gets quoted (S6).

Per-client action items

DomainAction
xactinsure.netClaim the ChatGPT profile (DNS) and record baseline mentions/clicks (S1). During the freeze, identify informational queries where info pages outrank commercial ones and plan a completeness fix, not a sales-pitch rewrite (S3). Add branded/non-branded split to reporting (S4).
floridahealthinsuranceweb.comClaim (DNS) + baseline (S1). Multi-state structure: use the new filterLists country/device filter for state-level reporting (S4). Track ghost citations — count named mentions per state guide, not just citations (S5).
acrepairdaily.comClaim + baseline (S1). Seasonal AC guides are prime agent-answer content — write explicit service-area, pricing-range and "how fast can you come" answers (S2). Booking/quote readiness audit resumes after the update completes (S3 freeze).
growwithfootprint.comClaim + baseline (S1). We own the reporting stack: implement the branded/multimodal API pull first, then template it for clients (S4). Freeze on-site changes during the update (S3).
buildwithng.comClaim + baseline (S1). Portfolio copy is already service-descriptive — verify the business description and service list the agent reads match the site (S2). No rebuild work until the update clears (S3).
pattonroofsystems.comClaim + baseline (S1). Roofing is a clean agent use case: ensure storm-damage/inspection/quote pages carry the facts an agent quotes (S2). Hold proximity-grid and booking audits until post-update (S3).
kennesawproroofing.comClaim + baseline (S1). Add explicit service-area and response-time answers for the agent layer (S2). Review-velocity work continues — off-site, safe during the update (S3).
securityservicesroseville.comClaim + baseline (S1). Security is an "online service business" — build the agent answer set (licensing, response time, monitoring options) before the rollout reaches it (S2).
edricker.comClaim + baseline (S1) — personal-brand profile inside ChatGPT; keep the description consistent with the LinkedIn/knowledge-panel entity work from Nov 5 (S2).
footprintstudioco.comClaim + baseline (S1); portfolio-appropriate description and service list for the agent (S2). Light touch only until the update completes (S3).
gressofab.comEcommerce: claim + baseline now — Business Agents explicitly start with eligible ecommerce, so this property is first wave (S1–S2). Verify the product/service facts the agent can actually reach (S2). Carry forward the Merchant Center feed check.
raybaconstore.comEcommerce: claim + baseline (S1–S2); same first-wave eligibility. Retire the unverified ChatGPT Ads "52¢" figure and any modeled AI-traffic stats from decks (S6).

Sources