GBP to Website API: Build Sites From Google Profiles With Code

Quick Answer

There is no single Google API that turns a Google Business Profile (GBP) into a website. Google's own free profile websites were shut down in 2024, and the Business Profile APIs are built to read and manage listing data, not to generate sites. A "GBP to website API" is something you assemble: profile data on one side, a site-creation API on the other.

Your options:

1. A site-creation API. Send the business details, get a finished site back. The 1ClickWebsite Site Creation API does this with one POST and creates a full multi-page WordPress site.
2. Google's Business Profile APIs plus your own generator. Pull the data, then write the templates, hosting, and page copy yourself.
3. The Places API plus your own generator. Same idea for businesses you do not manage, with tighter rules on what you can store and show.
4. Skip the code. Use the dashboard, or let an AI agent do it through MCP.

If you want a site live without building a generator, use option 1. The example is below.

What Is a GBP-to-Website API?

It is a way to create a website from a business's profile details using code instead of a button. In practice it is two jobs:

• Get the business facts: name, address, phone, hours, services, and areas served.
• Turn the facts into a site: layout, pages, written copy, images, hosting, and a place to edit it later.

Google's APIs help with the first job only. Everything after that needs a generator you write or a service you call.

This is different from the old Google feature people still search for. Google discontinued its auto-generated Business Profile websites on March 1, 2024, and the redirects from those addresses ended on June 10, 2024, according to Bay State Marketing. It was a product feature, not something you could call from code. For the non-code options, see How to Turn Your GBP Into a Website and our comparison of GBP website builders.

What the Google Business Profile API Does (and Does Not)

Google's Business Profile APIs are for businesses and partners that manage profiles. Google's reference lists separate APIs for account management, business information, performance, lodging, notifications, place actions, and verifications. The Business Profile overview describes uses like managing listings at scale and getting real-time notifications.

That is the key point: they are management APIs. Nothing in that list builds or publishes a website.

What it takes to use them, from Google's setup pages:

• A Google Account and a project in the Google API Console.
• An Organization account.
• A request for access to the APIs, which Google reviews. See Prerequisites.
• OAuth 2.0 credentials and the APIs enabled, covered in Basic setup.
• A business that has authorized you. Google's FAQ covers who can get access and how businesses grant a partner permission to manage a listing.

So the Business Profile API is a good fit if you already manage profiles for clients and want to read their details in code. It is a heavy requirement if you only want to build a website for a business.

The Build-It-Yourself Path

If you want full control, the pipeline looks like this:

1. Get the data. Use the Business Profile APIs for profiles you are authorized to manage. For public details on other businesses, the Places API's Place Details can return things like name, address, hours, rating, and photos. Google restricts how long you can store and how you must credit that data, so read the current Places API policies before you design anything around copying it.
2. Map it to a template. Decide how services, areas, hours, and reviews become pages.
3. Write the pages. A profile lists "Drain cleaning" as a label. A site that ranks needs a real page for it, and one for each town.
4. Generate and host. A static site generator or CMS, a build step, a domain, SSL, and forms.
5. Keep it current. Decide how edits get made after launch.

This path makes sense if you are building a product, or you have very specific requirements. It is also real work. The data is the smallest part of it. The pages, copy, hosting, forms, and ongoing edits are where the time goes.

The alternative is to hand steps 2 to 5 to a site-creation API. Duda, for example, has developer docs for creating sites programmatically. 1ClickWebsite does it for local service businesses specifically, which is the example below.

Create a Site With the 1ClickWebsite API

1ClickWebsite's Site Creation API creates a complete WordPress site from one request, and it is available on every plan. One accepted build uses one site credit, invalid requests are not charged, and a credit is returned automatically if a queued build fails.

The API does not take a profile link. You send the business details, and you can include a googlePlaceId that is used for business data when available. If you want the profile details looked up for you, the MCP server has a find_business tool that finds a business on Google by name and passes the details to create_site.

1. Get an API key

Create a key on the API Keys page. Standard account keys begin with lgen_. Send it as a bearer token, and keep it server-side. Never put it in browser code.

Use the www hostname. The bare domain redirects, and curl does not follow redirects unless you add -L.

2. Create the site

curl -X POST "https://www.1clickwebsite.ai/api/provision" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "templateId": "lightning",
    "builderVersion": "v2",
    "businessName": "Austin Patio Pros",
    "industry": "Patio contractor",
    "email": "owner@example.com",
    "phone": "+15125550123",
    "addressLine1": "123 Main St",
    "addressCity": "Austin",
    "addressRegion": "TX",
    "addressPostalCode": "78701",
    "countryCode": "US",
    "customerModel": "travel_to_customers",
    "businessHoursMode": "open_24_hours",
    "aboutBusiness": "Austin Patio Pros builds patios, outdoor kitchens, and stone walkways.",
    "services": ["Patio installation", "Outdoor kitchens", "Stone walkways"],
    "serviceAreas": ["Austin", "Round Rock", "Cedar Park"],
    "primaryColor": "#D23832",
    "backgroundTheme": "light"
  }'

Only templateId and businessName are required. lightning is the current public template ID. Everything else is optional, and the more of it you map from the profile, the better the first draft: phone, address fields, services, serviceAreas, aboutBusiness, googlePlaceId, logoUrl, primaryColor, and more. By default the build creates service pages, service-area pages, and location pages. You can turn each off with createServicePages, createServiceAreaPages, and createLocationPages.

If the business should not show a street address, set hasPublicBusinessAddress to false and leave out the street fields. That works with travel_to_customers or remote_online. A visit_business or hybrid business needs a public address, and the request returns 400 without one.

A good request returns 202 Accepted and queues the build:

{
  "slug": "c4b09c11-austin-patio-pros",
  "siteId": "6ca4fd0f-1190-4df2-a27d-ad4088344cd2",
  "previewUrl": null,
  "statusUrl": "/api/provision/6ca4fd0f-1190-4df2-a27d-ad4088344cd2"
}

Save the siteId.

3. Poll the build

curl "https://www.1clickwebsite.ai/api/provision/SITE_ID" \
  -H "Authorization: Bearer YOUR_API_KEY"

Use the same key that created the site. Poll every 2 to 5 seconds until status is complete or failed. The statuses are queued, provisioning, live, enhancing, complete, and failed. The site can be reachable while final enhancements still run, so treat complete as done.

4. Get the URL

A finished response includes the site link and the WordPress admin link:

{
  "status": "complete",
  "progressPct": 100,
  "previewUrl": "https://site-name.preview-domain.com",
  "adminUrl": "https://site-name.preview-domain.com/wp-admin/",
  "error": null,
  "creditRefunded": false
}

If a build fails, check error and creditRefunded. A failed standard build normally returns the credit once.

If you use a no-code tool like HighLevel, there is a POST wrapper at /api/integrations/site-status that returns the same status fields for workflow actions. The API reference has it and the error codes (400, 401, 403, 404, 500, 503).

5. Edit it later

The site is a normal WordPress site. A person can edit it in the visual editor or describe changes to the built-in Website Agent. In code, an AI agent connected to the MCP server can edit finished V2 sites, and each edit returns a changeSetId you can roll back. Over plain REST, editing goes through each site's own WordPress API using that site's application password.

White-label agencies have separate agency endpoints and keys (1cw_agency_...) for workspace template rules and an approval queue. Those are in the same reference.

API vs MCP vs Dashboard: Which to Use

The REST API and MCP use the same account key and the same credits. If you are choosing between them, the question is whether your code or an AI agent is driving. Our next post covers connecting an agent in detail.

Pro tip: build demo sites for a whole lead list

If you build sites for many businesses, there is a bulk API too. Mini Sites (formerly Lead Gen) builds a one-page demo site for every business in a list. It is available in the dashboard, over the API, and through MCP.

• POST /api/lead-gen/batches takes up to 500 businesses per batch.
• Each row needs businessName. Optional fields include phone, email, address, logoUrl, and primaryColor.
• One industry per batch, because the services and photos come from it.
• It costs one Mini Site credit per business, plus 5 once for an industry without saved photos.
• GET /api/lead-gen/batches/{batchId} returns the public URL of each finished demo.

curl -X POST "https://www.1clickwebsite.ai/api/lead-gen/batches" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "industry": "Roofing",
    "templateKey": "lightning",
    "rows": [
      { "businessName": "RidgeLine Roofing", "phone": "(555) 010-0199", "address": "1480 Main St, Denver, CO 80202" },
      { "businessName": "Northstar Roofing", "address": "London" }
    ]
  }'

Send each owner the link to their demo and build the full site for the ones who reply, using the request above. The business list can be a CSV from your lead source. See the Mini Sites batch guide and the API docs.

Related GBP Guides

• Turn a Google Business Profile Into a Website With MCP
• How to Sell GBP Websites to Local Businesses

FAQ

Is there a Google API that creates a website from a Business Profile?

No. Google's Business Profile APIs manage listing data, and Google's own profile website feature was discontinued in 2024. You combine profile data with a site-creation API or your own generator.

Can I use the Google Business Profile API to get a business's details?

Yes, if the business has authorized you to manage its profile and Google has approved your API access. Setup needs an API Console project, an Organization account, an access request, and OAuth. For businesses you do not manage, the Places API has its own storage and attribution rules.

Does the 1ClickWebsite API read a Google Business Profile link?

Not as a single field. You send the business details, and you may include a googlePlaceId, which is used for business data when available. The MCP server can look a business up on Google by name before creating the site.

How long does a build take, and what does it cost?

It takes a few minutes, and you poll the status endpoint until it says complete. One accepted build uses one site credit. Invalid requests are not charged, and failed queued builds get the credit back. Check your plan for current credit amounts.

Does the API work on every plan?

Yes. The Site Creation API is available on every 1ClickWebsite plan, with an API key from your account.

Do I need to build it myself instead?

Only if you are making your own product around the data. For building sites for local businesses, a site-creation API covers the pages, copy, hosting, forms, and editing you would otherwise write.

Sources and Review Notes

This post was informed by an LLM Sleuth research run on 2026-11-08 across GPT-6.1 Sol, Claude Sonnet 5.5, Gemini 3.8 Flash, and Perplexity Sonar. 1ClickWebsite API details come from our API and MCP documentation. Google API details come from Google's own pages below. Google's Places API policies were not available to the research run, so check them on Google's site before storing or displaying Places data. API fields, credits, and limits change, so verify them in the current docs.

• 1ClickWebsite API reference
• 1ClickWebsite MCP server docs
• 1ClickWebsite Mini Sites API docs
• Google: Business Profile APIs overview
• Google: Business Profile APIs
• Google: Prerequisites
• Google: Basic setup
• Google: Business Profile API FAQ
• Bay State Marketing: Google Business Profile websites to be discontinued
• Duda: Instant websites