Google Search mein “near me” ya local service query sirf ten blue links ka game nahi hai. User ko direct providers, directories, booking platforms, comparison services aur map-style options ek hi decision journey mein mil sakte hain. Google ne ab apne EEA-focused aggregator and supplier units mein local-business queries ka support document kiya hai.
Indian marketers ke liye sabse important clarification geography hai. Yeh India Search rollout nahi hai. Feature users in the European Economic Area ke liye documented hai. Relevance un Indian companies ko hai jo EEA users serve karte hain—such as travel and local-discovery aggregators, directories, comparison platforms, or Indian-owned businesses with genuine EEA operations and local inventory.
Opportunity real hai, but participation automatic nahi. Aggregators need approval, suitable content and data integration; direct suppliers have a different path. Is guide mein confirmed Google requirements and professional analysis clearly separate hain.
Google ne kya change confirm kiya?
Google Search Central changelog ne Sep 18, 2026 ko state kiya that aggregator and supplier units now support local-business queries. The corresponding documentation lists local businesses alongside hotels, flights, long-distance ground transportation and products.
Aggregator unit multiple eligible providers ko surface kar sakta hai. Top-ranked provider ka result set expanded by default ho sakta hai, and user another aggregator choose kar sakta hai. Clicks aggregator website par jaate hain.
Supplier unit direct providers ke liye hai—such as an individual hotel, airline, brick-and-mortar business owner or service provider. It appears alongside the aggregator unit and only when the aggregator unit itself appears.
This is not a general ranking update, a new Google Business Profile feature or a promise that every EEA local query will display these units.
Aggregator unit aur supplier unit mein difference
Aggregator unit
This is designed for Vertical Search Services, including online travel agencies, comparison services, metasearch engines and directories. Eligible aggregator apne unit ko query-relevant results se populate karta hai.
For local-business participation, Google says a business must be approved as a Vertical Search Service, have relevant content, provide necessary data and meet quality standards. Interest is submitted through Google’s Search Aggregator Features form.
The expression-of-interest form explicitly says submission does not guarantee participation in early access testing. It also asks whether the company is based in or serves users in the EEA or Türkiye, and treats each query type separately.
Supplier unit
Supplier unit direct providers ke liye dedicated visibility hai. Website must serve EEA users and business must be a direct provider relevant to the supported query.
Google says no additional data beyond what is accessible through web crawling is required for eligibility, although feeds can enhance supplier results where available. That is materially different from the aggregator path.
Why the distinction matters
A directory representing hundreds of restaurants is not the same participant as one restaurant. A marketplace listing plumbers is not the same as a plumbing company. Indian firms should identify their actual role before planning technical work or filling any form.
Calling a direct business an “aggregator” to gain access can create eligibility and data-governance problems. Similarly, an aggregator cannot assume ordinary crawling alone is enough when Google expects direct feed or API integration for that feature.
Feature availability: what is and is not confirmed
Google documents the aggregator and supplier units for users in EEA countries. Local-business queries are now among the supported query types.
The documentation does not confirm:
• Availability in Indian Google Search results.
• Automatic acceptance of every applicant.
• A universal display frequency for eligible queries.
• A special ranking boost for normal organic results.
• Guaranteed leads, bookings or revenue.
• A dedicated Search Console performance filter for these units.
Analysis: Indian agencies should resist turning an EEA feature into a generic “new local SEO hack.” The correct service angle is market eligibility, entity-data readiness, feed quality and landing-page consistency for businesses with a legitimate EEA use case.
Which Indian businesses should pay attention?
Travel, hospitality and local-discovery platforms
Indian OTAs, city directories, attraction platforms and local-experience marketplaces that serve EEA travellers or operate European inventory should review the aggregator path. Their value depends on structured, current and contractually supported merchant data—not merely on having category pages.
Comparison and booking marketplaces
Platforms comparing restaurants, appointments, services, venues or local providers may have a use case if they qualify as a Vertical Search Service and serve EEA users. Google’s form and documentation, not marketing assumptions, should decide whether an application is appropriate.
Indian-owned businesses operating in Europe
An Indian group may own hotels, restaurants, retail outlets or service branches in EEA countries. Those direct local entities could assess the supplier path. The page serving users should clearly represent the actual local provider, location, hours, services and booking or contact journey.
Agencies serving European clients
Indian SEO and web agencies can add readiness audits for existing EEA clients. This is not permission to promise placement. A responsible deliverable would document participant type, crawlability, data sources, entity accuracy, feed capability, policy risks and measurement plan.
Businesses operating only in India
A local Delhi, Mumbai or Bengaluru company without EEA operations should not treat this as an immediate Indian visibility feature. The update is still strategically useful as a signal of how Google is structuring regional search experiences, but an implementation project may not be justified.
Aggregator readiness requirements
1. Prove the business model
Document whether the platform is an aggregator, directory, OTA, comparison service or direct provider. For local vertical integrations, Google’s related Actions Center criteria say partners should be aggregators rather than an individual chain and should have direct contractual relationships with merchants.
Do not submit scraped listings as if they were authorised inventory. Merchant relationship, data rights and correction process need evidence.
2. Maintain relevant local content
Category or city pages should contain useful entity-level information, not just thin lists. Google recommends rich details such as images, descriptions, verified ratings and review counts, specific categories, amenities, features and operating hours.
3. Prepare reliable data integration
Google’s aggregator documentation points local-business participants to a Local Point of Interest Feed. Related onboarding typically involves setup, sandbox feed implementation, review, production implementation, production review and launch.
That process requires product, engineering, data and policy ownership. It should not be sold as a one-day schema-markup task.
4. Keep titles and media accurate
Google recommends factual, descriptive titles in title case and advises against all caps, excessive punctuation, emoji or promotional wording in entity names. Images should be clear, original and free from distracting watermarks or promotional badges.
5. Synchronise price, availability and landing pages
Where price or availability applies, feed and landing page should match as closely as possible. Expired, unavailable or incorrectly priced listings create user frustration and can undermine quality review.
Direct-supplier readiness requirements
Make the entity crawlable
Google says supplier eligibility can use information accessible through web crawling. Business name, address or service area, category, hours, contact or booking route and the relationship between location pages should therefore be unambiguous.
Build location pages for people, not only search engines
A useful location page answers practical questions: what is offered, where, when, at what price or booking condition, who operates it, and how the user completes the next step. Copy-pasted city pages with only a place name changed create weak evidence.
Keep Business Profile and website facts aligned
Google’s supplier document does not say Google Business Profile is a formal requirement for this unit. Still, inconsistent names, addresses, hours, categories or URLs across owned sources can confuse customers and internal teams. Treat consistency as operational hygiene, not a guaranteed eligibility trick.
Use structured data carefully
LocalBusiness structured data can help machines understand page entities in ordinary search contexts, but Google does not state that adding schema alone enrolls a supplier in this unit. Mark up only visible, accurate information and test implementation without promising appearance.
A practical audit for Indian teams
Create a sheet with one row per entity or merchant and these columns:
• Legal or trading name.
• Participant type: aggregator or direct supplier.
• EEA market and language served.
• Contract or inventory authority.
• Primary category and specific subcategory.
• Address or service area.
• Hours and temporary closures.
• Images and usage rights.
• Ratings source and verification method.
• Price, availability and refresh frequency.
• Canonical landing page.
• Booking or contact destination.
• Feed status and last successful validation.
• Owner for corrections and user complaints.
Analysis: This inventory is valuable even if Google access is not granted. It exposes duplicate entities, stale hours, broken booking links, unsupported reviews and mismatched categories that can hurt ordinary local discovery and conversion.
A 30-day action plan
Week 1 — Eligibility: Confirm EEA use case, countries, participant type and supported query. Read the official aggregator and supplier pages. Do not submit interest until the company can explain its data and merchant relationships.
Week 2 — Data audit: Sample at least the highest-value entities. Compare platform record, website page, merchant source and current customer journey. Flag missing rights, weak categories, stale hours and broken destinations.
Week 3 — Technical readiness: For aggregators, assess feed ownership, sandbox capability, refresh frequency, monitoring and correction workflow. For suppliers, improve crawlability, internal linking and location-page clarity. Validate analytics and consent setup for EEA users.
Week 4 — Pilot decision: If eligible, submit a carefully documented expression of interest or begin the relevant partner process. Define baseline organic traffic, referral sessions, booking or lead quality and support issues. If eligibility is weak, record the gap and stop rather than forcing an application.
Confirmed facts versus professional analysis
Confirmed facts
• Google documented local-business query support for aggregator and supplier units on Sep 18, 2026.
• Both units are documented for users in EEA countries.
• Aggregators need approval, relevant content, necessary data and compliance with Google policies.
• Direct suppliers must serve EEA users; extra data beyond crawlable website information is not required, although feeds may enhance results.
• Supplier units appear only when an aggregator unit appears.
• Expressing interest does not guarantee participation.
Professional analysis
• Indian firms with real EEA users, inventory or operations should assess eligibility; India-only local businesses generally should not launch an implementation project yet.
• Merchant authority, entity accuracy and feed operations will matter more than isolated markup changes.
• Agencies can offer readiness and governance work, but should not guarantee placement.
• The feature signals a more modular, region-specific search-results architecture, making market-by-market SEO documentation increasingly important.
Common mistakes to avoid
Do not announce this as an India rollout. Do not confuse aggregator and supplier roles. Do not submit scraped or unauthorised merchant inventory. Do not treat structured data as automatic enrollment. Do not promise traffic from an expression-of-interest form. And do not build a feed without an owner for updates, errors, merchant corrections and landing-page mismatches.
Conclusion
Google’s local-business support inside EEA aggregator and supplier units creates a meaningful opportunity for qualified platforms and direct providers. Indian companies can benefit when they genuinely serve European users, maintain trustworthy local inventory and can support the required data or crawlable entity experience.
The right first step is not “add schema everywhere.” It is eligibility clarity, data rights, entity quality, technical readiness and honest measurement. Market-specific precision will protect both performance and client trust.
Sources and verification notes
1. Google Search Central documentation updates, local-business query support, updated Sep 18, 2026:
https://developers.google.com/search/updates
2. Google Search Central, Aggregator unit:
https://developers.google.com/search/docs/appearance/aggregator-unit
3. Google Search Central, Supplier unit:
https://developers.google.com/search/docs/appearance/supplier-unit
4. Google Search Central, Regional differences in Search experience:
https://developers.google.com/search/docs/appearance/aggregator-features
5. Google Search Aggregator Features interest form:
https://support.google.com/websearch/contact/search_aggregator_features
6. Google Actions Center, Local Vertical Search Service overview:
https://developers.google.com/actions-center/verticals/local_vss/integration-steps/overview
Editorial note: This draft does not claim India availability, automatic acceptance, guaranteed placement or a dedicated Search Console filter.