3 Nov 2026: Migrate Google Business Profile Q&A, UK Agency Playbook
The Q&A API was discontinued on 3 November 2025, and any business still relying on it for automated publishing or reporting needs to stop and move durable answers onto assets it controls. The change is confirmed in Google’s own developer changelog, and Google Maps help documentation shows the shift toward contextual, AI-assisted answers in search results.
TL;DR:
- The Q&A API was discontinued on November 3, 2025, removing the ability to programmatically manage questions and answers, including scheduled publishing and bulk monitoring.
- Businesses must now manually review and update questions and answers, migrating frequent inquiries to structured FAQ pages on their own websites for durability and search visibility.
- Automated alerts and reporting based on the API are no longer reliable, increasing risks of outdated information, unmonitored questions, and lost visibility if not actively managed.
- Google Maps still allows answering questions in some regions, but reliance on that feature is risky due to uneven availability and decreasing prominence amid AI-assisted search results.
- Migrating to owned, well-structured FAQ pages with schema markup ensures long-term visibility and control, reducing dependence on platform features that may be discontinued at any time.
Table of Contents
- What changed: API deprecation, timeline and what removal actually means
- What this means for your business: risks to visibility and reporting
- How to manage customer questions now: a step-by-step checklist
- Alternatives for surfacing and preserving FAQs
- Monitoring, archiving and agency workflows after the API change
- What to prioritise next
- How Blindspot can help migrate your Q&A into owned assets
- Sources
- FAQ
What changed: API deprecation, timeline and what removal actually means
The facts are specific, not vague. Google confirms that the My Business Q&A API was discontinued on 3 November 2025, which means developers and agencies can no longer read or post questions and answers programmatically through that interface. Scheduled publishing, bulk question monitoring and automated answer suggestions that depended on the API all stopped working on that date.
It helps to separate two things that often get confused. The public Q&A feature that customers see on a Google Business Profile or in Google Maps is not necessarily gone everywhere, but the API that let software talk to it is. According to the changelog, Google specifically advises businesses to stop depending on the API and migrate durable information to channels they own, while the underlying Q&A experience itself continues to change.
For context, this is not the first interactive feature Google has quietly scaled back. Business Profile chat and call history were removed on 31 July 2024, with Google pointing businesses toward alternative communication channels. The pattern is consistent: features that required real-time, two-way interaction on Google’s own platform are being retired in favour of simpler, less maintenance heavy formats.
A few timeline points matter for anyone managing a profile or a client portfolio:
- The Q&A API’s read and write endpoints, along with their associated notification types, stopped functioning from 3 November 2025.
- Chat and call history inside Business Profile ended on 31 July 2024, an earlier but related signal of the same direction.
- Older REST documentation describing methods such as locations.questions.list remains online for reference but no longer reflects a working service.
- Community threads on the Google Business Profile Community show businesses and developers still asking whether the feature will return, with no confirmed date from Google.
Anyone building internal tools or client dashboards around Q&A data needs to treat that functionality as retired rather than paused.
What this means for your business: risks to visibility and reporting
The practical consequences land in three places: dashboards, customer-facing presentation and day-to-day monitoring workload. If your reporting stack pulled question counts, answer rates or upvote figures from the API, those fields will now return errors or stale data. Any scheduled publishing tool that posted answers automatically on your behalf has also stopped working, because the write endpoints are part of the same discontinued service.
Search behaviour is shifting alongside the API change. Google Maps still lets people answer questions about a place in certain countries and regions, but the help documentation is explicit that availability is not uniform. Where public Q&A does persist, it increasingly sits alongside AI-generated contextual answers rather than being the primary way information reaches a searcher. That changes how prominent any individual question and answer pair is likely to be.
The most urgent risks to address, in rough order of priority:
- Reporting gaps where question or answer metrics silently stopped updating without anyone noticing.
- Outdated or incorrect public answers that nobody is actively monitoring because the automated alert that used to flag new questions no longer fires.
- Over-reliance on a channel you do not own, meaning any future Google product change can remove visibility built there overnight.
- Customer confusion where a prospective customer asks a question on Maps and receives no reply because the manual check that replaced the automated one has not been scheduled yet.
None of these are catastrophic on their own, but left unaddressed for a few months they compound into a visibility gap that is harder to fix retroactively than to prevent now.
How to manage customer questions now: a step-by-step checklist
The fix is not complicated, but it does require someone to own it rather than assume the old automation is still quietly working. This is the sequence we recommend to local service businesses moving off API-dependent Q&A management.
- Audit what exists. Check every live Google Business Profile for outstanding questions, out-of-date answers and anything a customer has flagged. Where possible, export what you can via Google Takeout or manual screenshots before older entries become harder to find.
- Assign an owner. Someone needs a standing task, weekly at minimum, to check Maps and the profile directly for new questions, since automated alerts from the API no longer exist.
- Identify your durable answers. Pull out the questions that get asked repeatedly: opening hours exceptions, parking, pricing structure, service areas. These are the ones worth migrating properly rather than answering once and forgetting.
- Migrate those answers to your website. Build or update FAQ pages and relevant service pages with the same questions, written as clear, direct answers, and mark them up with FAQPage structured data so search engines can index and potentially surface them as rich results.
- Update other customer channels. Make sure social media bios, pinned posts and any chat widget your business uses reflect the same answers, so a customer gets consistency wherever they ask.
- Change what you report on. Swap API-derived question counts for site metrics: organic impressions and clicks to your FAQ pages, time spent on those pages, and contact form or call conversions originating from them.
- Stop promising automation you can no longer deliver. If a client or internal stakeholder expects auto-published Q&A responses, that expectation needs resetting now, not when someone notices three months of silence.
Pro Tip: Treat every migrated question as a mini landing page, not a buried FAQ entry: a specific, well-answered question about your service area or pricing can rank on its own in search results.
The hardest part of this process is usually step three, because most businesses have never actually reviewed which questions customers ask most often. Pulling twelve months of Google Business Profile questions, email enquiries and even social media comments into one list usually reveals four or five recurring themes that are worth a dedicated page each, rather than a single catch-all FAQ.
Alternatives for surfacing and preserving FAQs
Owned, structured FAQ content is the most reliable replacement for API-managed Q&A, because it does not depend on a Google feature that can be retired without notice. A well-built FAQ page using FAQPage schema gives search engines a machine-readable version of your question and answer pairs, which can appear as expandable results directly in search listings.
Writing them well matters as much as the markup. Each question should be phrased the way a real customer would type or say it, kept to a single topic, and answered in two or three direct sentences before any further detail. Group related questions under the same service page rather than one generic sitewide FAQ, so a page about, say, emergency callouts answers everything relevant to that service in one place.
A durable FAQ page with correct structured data remains discoverable for as long as your site exists, unlike a Q&A entry on a platform feature Google can change or remove, as the changelog advises when it tells businesses to move information to assets they control.
Complementary channels each have trade-offs:
- A knowledge base works well for businesses with complex products but adds another platform to maintain.
- Chat widgets answer individual visitors in real time but rarely create indexable content for future searchers.
- Social media FAQs reach existing followers quickly but get buried in a feed within days.
None of these replace a website FAQ outright. They work best as supporting channels that point back to the same canonical answers you have already written once, properly, on your own site.
Monitoring, archiving and agency workflows after the API change
For agencies and in-house teams managing several profiles, the practical shift is from automated polling to scheduled manual checks. Export existing Q&A content via Google Takeout where available, and keep a simple log of what was asked, answered and migrated, so nothing gets lost in the transition.
A monthly cadence is usually enough once the initial migration is done: check each profile for new questions, confirm existing answers are still accurate, and flag anything recurring for a new FAQ entry.
- Reporting should move from question-and-answer counts to site-side signals: organic traffic to FAQ pages, conversions from those pages and Search Console impressions for FAQ-related queries.
- Any automation still pointed at the old API endpoints should be switched off rather than left to fail silently.
- Tools built around client communication flows, such as Happy Client Flow, can help formalise who checks what and when, particularly across multiple client accounts.
Pro Tip: Build your FAQ migration log in a shared spreadsheet rather than a project tool nobody checks: the goal is a five-minute monthly glance, not another dashboard to maintain.
What to prioritise next
The businesses that come out of this change ahead are the ones that stop treating Google’s interactive features as permanent infrastructure. A question answered on Maps today can vanish from view tomorrow if Google changes the product again, but the same answer on your own FAQ page, properly structured, keeps working for as long as your site does.
Owned content also gives you something the API never did: control over measurement. You can see exactly which questions drive traffic, which pages convert and which answers need rewriting, because the data sits in your own analytics rather than a platform you do not control. Having worked through this exact transition with local service businesses, the pattern is consistent: the sooner the migration starts, the less content gets lost to platform changes nobody can predict.
— Harry
How Blindspot can help migrate your Q&A into owned assets
Moving customer questions off a retired API and onto your own website is exactly the kind of practical fix that pays off slowly and then compounds, and such work is beneficial for local service businesses in Sussex.
If you need help turning old Google Business Profile questions into proper FAQ and service pages, our SEO & GEO service covers the structured data and local search side, while Content Creation and Video Editing handles the actual page copy and assets.
- Audit your existing profile questions and identify which ones deserve a dedicated page.
- Build FAQPage-marked pages that are structured to stay visible in search.
- Turn recurring customer questions into user generated content and testimonials that reinforce the same answers.
Get in touch through Blindspot for a straightforward audit of what needs migrating first.
Sources
- Q&A API | Google Business Profile APIs | Google for Developers
- Answer questions about a place on Google Maps - Computer - Google Maps Help
- Changes to Google Business Profile chat and call history - Google Business Profile Help
FAQ
Can you still add Q&A to a Google Business Profile?
Public Q&A functionality may still appear on some profiles, but the API that let businesses manage it programmatically was discontinued on 3 November 2025. Availability of the Maps question-and-answer feature itself varies by country and region, according to Google’s Maps help documentation.
How do I add FAQs to my Google Business Profile now?
Since the API no longer supports programmatic posting, any new questions on a profile need to be answered manually through the Google Maps interface where that feature is available in your region. For durable, long-term answers, building a proper FAQ page on your own website with FAQPage structured data is the more reliable option.
How do I ask a question on a Google Business Profile?
Customers can still ask questions about a place directly within Google Maps in supported regions, following the steps in Google’s own help article. Businesses should check their own profile and region, since the feature is not available everywhere.
What happened to the Google Business Profile Q&A API?
The My Business Q&A API was discontinued on 3 November 2025, meaning businesses and developers can no longer read or post questions and answers through that interface. Google’s own guidance recommends moving durable answers to assets businesses control rather than relying on the retired API.
What should businesses do instead of relying on the Q&A API?
The most reliable approach is migrating frequently asked questions to your own website as FAQ or service pages, marked up with FAQPage structured data so search engines can index them properly. Pair that with a regular manual check of your Google Business Profile and Maps listing, since automated monitoring through the old API is no longer possible.
