A single sentence added to a Google help page today put a number on something agencies had been operating without: the maximum quantity of client accounts that can sit beneath one Merchant Center for Agencies login. The figure is 1,000, and until now it was absent from the documentation entirely.

The addition appeared in the help article covering user access inside Merchant Center for Agencies, in the section dealing with client account connections. According to the revised text, an Agency Admin "can link up to 1000 client Merchant Center accounts." The number is written without a thousands separator in the help page body, though the accompanying interface screenshot highlights the same figure.

Search Engine Roundtable flagged the revision at 7:31 am on August 14, 2026. According to the publication, the change was straightforwardly additive: the ceiling was simply not stated before, and now it is. No policy language accompanied it, no effective date was attached, and no notification went to agency account holders.

That last detail is characteristic. Google routinely revises Merchant Center documentation without alerting the merchants and agencies who depend on it, a pattern that has surfaced repeatedly in coverage of the platform. When Google clarified that identical product IDs can be reused across multiple Merchant Center accounts, the change reached practitioners only because feed specialists monitor the help pages line by line.

What the limit actually governs

The 1,000-account figure applies to a specific structure, and the distinction matters operationally.

Merchant Center for Agencies is a separate account layer that sits above individual client accounts. It is not the multi-client account, or MCA, that agencies have used for years to manage product data across several merchants. The agency layer adds a portfolio overview, a cross-account diagnostics page, a client optimization surface and an ads opportunities page. The MCA remains a parent-child feed structure. The two coexist, and the newly published ceiling attaches to the former.

The linking procedure described in the documentation is short. From the agency Merchant Center account, an admin opens the "All client accounts" page and selects "Add an account". The Merchant Center ID of the client is entered into a text field. Selecting "Next" initiates the link request.

An MCA can be linked through the identical process. Sub-accounts inside a linked MCA may inherit labels assigned at the parent level, and additional labels can be applied to individual sub-accounts. The documentation does not state whether a linked MCA counts as one account against the 1,000 ceiling or whether its sub-accounts are counted individually. For agencies serving marketplaces or multi-brand retailers, where a single MCA can contain hundreds of sub-accounts, that ambiguity carries real weight.

Unlinking runs through the same page. An admin locates the client account and selects the unlink icon in the "Remove link" column.

Two roles, and a ceiling on both

The access architecture published in June 2026 defines two user types on the agency account, and the 1,000-account limit interacts with both.

Admin users hold comprehensive control. They receive automatic access to every linked account, add and remove users from the agency account, link and unlink client Merchant Center accounts, request and approve links to accounts the agency already owns, and provision access for other employees through labels.

Standard users operate under a narrower grant. They can only view portfolios for accounts an admin has explicitly assigned to them. They can link accounts to which they already hold user-based access, but they cannot link a new account. That restriction places the 1,000-account ceiling squarely in the hands of Agency Admins, since they are the only class that can grow the portfolio.

Client accounts themselves carry two permission tiers. An agency user can hold Admin access within a specific client account, covering data sources, users and settings, or Standard and performance and insights, which provides view-only or limited editing capability alongside visibility into performance metrics.

Above both sits a constraint the documentation flags explicitly. According to the help page, "The maximum access level an agency user can have to a client's account is limited by the access level the Merchant Center for Agencies account itself has to that client's account." The worked example given is direct: if the agency holds Standard plus performance and insights access to a client, an agency user assigned Admin client account access for that same client still operates at Standard level.

The linking approval path

Two mechanisms exist for connecting a client account, and they differ in who has to act.

Automatic account linking approves the connection without merchant intervention, but only when the requester already holds Admin status on the merchant's account. Accounts connected this way appear in the agency's "All client accounts" page. Where the agency user holds only Standard access to the client's Merchant Center account, the merchant's admin must still approve the connection manually.

The manual request path requires the agency to specify one of the two access levels at the point of request. Once sent, the merchant's Merchant Center administrator receives notification in two places: by email, and inside the "People and access" page under a table labelled "Partners". The administrator approves or rejects. An approval grants the exact access level originally requested. A rejection updates the agency's "All client accounts" view to show a status of "Rejected".

One consequence of an approved link is worth isolating, because it inverts what many merchants expect. According to the documentation, after a link is approved, individual users from the agency will not be listed on the merchant's "People and access" page. The client sees the agency as a single partner entity, not as a roster of named individuals. Control is exercised at the agency level, not the user level, and the merchant can revoke it at any time through the "Partners" section.

That design has a direct antecedent. In March 2026, an agency that had retained super admin access to a client's Merchant Center account for roughly six years after the relationship ended closed its own account and, in doing so, wiped the client's account entirely, deleting primary feeds, feed rules, supplemental feeds and third-party linkages including Google Ads, Google Analytics and PayPal connections. The account was restored within 24 hours. The partner-level model in Merchant Center for Agencies gives merchants a single lever to sever an agency relationship, which the older user-level model did not.

Three configurations, scaled to headcount

The documentation lays out three ways an agency can structure its own account, and the 1,000-account ceiling becomes materially different in each.

The universal setup adds every team member as an Admin, which automatically grants full access to all linked client accounts. It is described as suited to small agencies where every team member needs access to every client and granular permissions are unnecessary.

The permission control setup designates a subset of employees as Admin and the rest as Standard, with Standard users receiving either Admin or Standard access across all client accounts. It targets small to medium agencies that need everyone to reach every client while retaining a controlled level of administrative privilege.

The advanced setup is the label-based model, and it is the only configuration built for scale. Agency Admins create labels, apply them to groups of client accounts, and assign Standard users to one or more labels. A Standard user then reaches every client account sharing a label they hold. Example label names given in the documentation are "High priority" and "Clients - Region West".

Labels can be edited in name and description, assigned individually or in bulk, and deleted. Deletion removes the tag from all client accounts and revokes access for any user whose access rested solely on that label, with a confirmation step normally required first. If a client account loses its last label, the agency retains the link and its own access, since that is governed by the linking relationship rather than the label, but Standard users who relied on the label lose their access.

An agency approaching a four-figure client count would be operating in the advanced configuration by necessity. Admins bypass labels entirely and see all client accounts by default, which means the label system exists precisely to prevent a Standard user at a 1,000-client agency from seeing all 1,000.

Why the figure carries weight

Published account ceilings shape agency economics in a way that is easy to underestimate. They determine whether a network can consolidate operations under one login or must fragment across several, which in turn drives headcount, tooling and reporting architecture. The absence of a stated figure meant agencies building on the platform were extrapolating from behaviour rather than from documentation.

The number arrives at a moment when Merchant Center data feeds an expanding set of surfaces. Product data now supplies AI Mode, AI Overviews and the Gemini app, and Merchant Center added performance insights covering those surfaces in May 2026. The reporting layer is also shifting: Google is separating YouTube affiliate traffic, revising organic traffic definitions and expanding product-level reporting from August 24, 2026, changes that will restate historical figures across a six-week window. Agencies reconciling that restatement across a large client roster are doing so inside the same interface the 1,000-account ceiling governs.

The programmatic dimension compounds it. The Merchant API reached general availability in August 2025, and the Content API for Shopping shuts down on August 18, 2026, four days after the ceiling was published. Merchant API support arrived inside the Google Ads scripts editor on April 22, 2026. Google confirmed in June 2026 that the agency user access model is available through the API, which means user creation, label assignment and account linking can be automated rather than executed manually. At 1,000 accounts, manual execution is not a realistic option.

Dates that do not fully agree

The rollout chronology carries a discrepancy worth noting.

According to Search Engine Roundtable, Google rolled out Merchant Center for Agencies in the United States and Canada after beta testing it in October 2025, and released the product globally in May. PPC Land dated general availability in the United States and Canada to March 11, 2026, confirmed the same day by the Google Ads Liaison account on Bluesky at 16:37 UTC, and dated the global rollout to May 17, 2026. The October 2025 beta reference does not appear in that earlier coverage.

The two accounts are compatible on the substantive sequence and differ on the beta window. Neither source states when the 1,000-account limit was first enforced in the product, as distinct from when it was written down.

A further tension sits inside the help page itself. Despite the global rollout in May, the documentation still carries a caveat stating that the feature is currently available on a limited basis and may not apply to all users. Google also dropped the "Next" suffix from the Merchant Center name in July 2026, part of a naming cleanup that followed two years of infrastructure layering on top of the 2024 platform consolidation.

What remains unstated

Several questions survive the update. The documentation does not say what happens when an agency attempts to link account number 1,001, whether the ceiling can be raised on request, whether it is enforced through the API as well as the interface, or how MCA sub-accounts are counted. Nor does it address whether the limit applies per agency account or per organisation, a distinction that matters for holding companies operating multiple agency brands.

Access hygiene inside Google's advertising products has been tightening on a parallel track. Google began pausing ads for individual accounts linked to manager accounts found in violation of its third-party policy in June 2025, and introduced a second-admin approval requirement in Google Ads in July 2026 that leaves solo administrators unable to complete certain changes alone. The Merchant Center for Agencies permission model, with its approval steps and partner-level revocation, sits inside that same pattern.

For now, agencies have one figure they did not have yesterday.

Timeline

Summary

Who: Google, through an edit to the Merchant Center help documentation. The change was reported by Barry Schwartz of Search Engine Roundtable. It affects agencies, freelancers and consultancies operating a Merchant Center for Agencies account, and the merchants whose accounts they link.

What: A sentence added to the "Managing user access in Merchant Center for Agencies" help page states that an Agency Admin can link up to 1,000 client Merchant Center accounts. The figure was previously absent from the documentation. The surrounding guide sets out two agency user roles, two client account permission tiers, three account setup configurations, a label-based access system, an automatic linking mechanism and a manual approval path routed through the merchant administrator.

When: The documentation change was reported on August 14, 2026 at 7:31 am. It follows general availability in the United States and Canada on March 11, 2026, a global rollout on May 17, 2026, and publication of the user access guide on June 26, 2026. The Content API for Shopping shuts down on August 18, 2026, and Merchant Center reporting definitions change on August 24, 2026.

Where: Inside the Google Merchant Center Help Center, in the client account connections section of the agency user access article. The product itself is available globally, though the help page retains a caveat that the feature is available on a limited basis and may not apply to all users.

Why: The ceiling determines whether an agency network can consolidate its entire client roster under a single agency login or must fragment across multiple accounts, with consequent effects on staffing, tooling and reporting. Google did not attach a policy statement, effective date or notification to the change, and the documentation does not address what happens at the limit, whether multi-client account sub-accounts count individually, or whether the ceiling can be raised.