# Local SEO Site Generator for Any Niche + City (`gp005/local-service-site-generator`) Actor

Generates a complete local-SEO static-site package for any niche + city: original home/services/about/FAQ copy, LocalBusiness JSON-LD, meta tags, sitemap.xml and a citations outline — fresh LLM copy per run, no invented business identity. One run = one ready-to-host site.

- **URL**: https://apify.com/gp005/local-service-site-generator.md
- **Developed by:** [Geo](https://apify.com/gp005) (community)
- **Categories:** Business, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6,000.00 / 1,000 site package generateds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Local Service Site Generator

Generate a complete local-SEO static website for a local service business in one run: original home, services, about and FAQ pages, LocalBusiness JSON-LD, meta/OG tags, sitemap.xml, robots.txt and a citations outline — for any niche and city (plumber in Austin, roofer in Tampa, electrician in Seattle, HVAC in Phoenix…).

Copy is written fresh by an LLM on every run for your exact niche + city + service list — no shared templates, no copied competitor text, and **no invented business identity**. If you do not supply a business name, phone or address, the package ships clean `[PLACEHOLDER]` tokens and a completion checklist instead of fabricating one.

### What this Actor does

You provide a trade (niche) and a city. The actor returns one dataset item containing a ready-to-host static-site package:

| File | Purpose |
|---|---|
| `index.html` | Home page: hero, intro, top services, FAQ preview, **LocalBusiness JSON-LD** |
| `services.html` | Full service catalog with descriptions and benefit bullets |
| `about.html` | About copy + "why choose us" + service-area statement |
| `faq.html` | Five city- and niche-specific Q\&As |
| `sitemap.xml` | XML sitemap for Google Search Console submission |
| `robots.txt` | Robots file with sitemap reference |
| `citations-outline.md` | Local-citation checklist (Google Business Profile, Bing Places, Yelp…) |
| `site-setup-notes.md` | Placeholder-completion + hosting + post-publish steps |

All pages share a single embedded responsive stylesheet, real meta description/OG tags, and inter-page navigation. No external CSS, no build step, no tracking.

### Why use it

- Launch a local-SEO site for a service business or client in minutes instead of hours.
- Agencies: white-label starter sites for new local clients — each run produces original, niche- and city-specific copy.
- Business owners: get a clean, honest foundation site and hand it to any static host (Netlify, Cloudflare Pages, GitHub Pages, cPanel).
- Test local-keyword variations: run the same niche against different cities for market research.
- No scraping, no databases, no infrastructure — one API call, one priced event, one site.

### Local-SEO compliance: what is (and is not) generated

- **Schema.org type is mapped from your niche** — e.g. `plumber` → `Plumber`, `electrician` → `Electrician`, `roofer` → `RoofingContractor`, `hvac` → `HVACBusiness`, falling back to `LocalBusiness`.
- **Identity facts are never invented.** Name, phone, email, street address, hours and domain are taken only from your input. Anything missing ships as a `[PLACEHOLDER]` token and is listed in `completionRequired` — you fill it before hosting.
- **No fake reviews, ratings, credentials, licenses, awards or "years in business".** The generation prompt enforces this and the package stays clean of unsupportable claims.
- Service-area claims are confined to the city you specify.

### Quick start

Default input (already prefilled — one click runs it):

```json
{
  "niche": "plumber",
  "city": "Austin",
  "stateCode": "TX"
}
```

Start the run. When it finishes, open the dataset — the single item contains `files` with the complete site package plus `siteTitle`, `completionRequired`, `jsonLdType` and usage metadata.

**One key is required:** copy is generated by an LLM on **your own** OpenAI-compatible key. Add `llmApiKey` to the input (field docs below) before starting — a run without it returns a structured `error` item that names the missing key, never a package.

### Input

| Field | Required | Description |
|---|---|---|
| `niche` | yes | Trade, e.g. `plumber`, `roofer`, `electrician`, `hvac`, `dentist`, `landscaper` |
| `city` | yes | Primary service city, e.g. `Austin`, `Tampa`, `Seattle` |
| `stateCode` | no | State/region code, e.g. `TX`, `FL` |
| `serviceList` | no | Exact services to feature (max 25). Empty → the generator proposes 6 typical services |
| `businessName` | no | Real business name → placed in headings, JSON-LD, footer |
| `businessPhone` | no | Real contact phone |
| `businessEmail` | no | Real contact email |
| `streetAddress` | no | Real street address → structured into PostalAddress JSON-LD |
| `businessHours` | no | Real opening hours |
| `websiteUrl` | no | Live domain → used for canonical URLs and sitemap |
| `tone` | no | `professional` (default), `friendly`, or `expert` |
| `llmModel` | no | OpenRouter model slug (default `openai/gpt-4o-mini`) |
| `llmApiKey` | **yes** (secret) | Your own OpenAI-compatible key — required, you pay the provider directly |
| `llmBaseUrl` | no | OpenAI-compatible base URL used with `llmApiKey` (default `https://api.openai.com/v1`) |

### Output

One dataset item per run = one complete site package:

```json
{
  "recordType": "data",
  "status": "succeeded",
  "niche": "plumber",
  "city": "Austin",
  "stateCode": "TX",
  "siteTitle": "…",
  "pages": 4,
  "completionRequired": ["[PHONE]", "[EMAIL]", "…"],
  "jsonLdType": "Plumber",
  "files": { "index.html": "…", "services.html": "…", "…": "…" },
  "generatedAt": "…"
}
```

Invalid input (missing `niche`/`city`) or an LLM failure produces a structured `error` record instead — never a silent empty run.

### LLM key: bring your own (required)

Copy generation is billed to **you**, on **your** key:

1. Pass `llmApiKey` — any OpenAI-compatible key (OpenAI, OpenRouter, Groq, Together, a local gateway…). It is a secret input field: it is never written to the dataset and never logged.
2. Optionally set `llmBaseUrl` (default `https://api.openai.com/v1`) and `llmModel` (default `openai/gpt-4o-mini`; the `openai/` prefix is stripped for native OpenAI endpoints).
3. Typical cost is tiny — two calls per package, roughly 1.2k prompt and 4–5k completion tokens, about **$0.003 per package** at gpt-4o-mini rates.

**The Apify-managed OpenRouter proxy fallback is disabled for this Actor** (the publishing account does not have public-actor LLM access). A run without `llmApiKey` therefore returns a structured `error` dataset item naming the missing key — it never runs silently for free and never ships a half-built package.

### Pricing

Pay-per-event: one `actor-start` event ($0.005) when a run starts and one `site-package-generated` event ($6.00) per delivered site package — 1 event = 1 complete package (8 files). LLM usage is separate and billed by your own provider (≈$0.003 per package at gpt-4o-mini rates); Apify compute for a typical run is a few seconds at 1 GB.

### Limitations

- The generated copy is original but general trade knowledge — it does not know your licensing, insurance, service radius or pricing. Review the copy and complete all placeholders before publishing.
- The actor does not register you with Google, Yelp or any directory, and does not host the site. Citations and hosting are buyer actions documented in the package.
- LLM output is non-deterministic: two runs on the same input produce different (but equivalent-quality) copy. Re-run until you like the result; supply `serviceList` for control over featured services.
- The sitemap and robots files reference `[YOUR-DOMAIN]` until you supply `websiteUrl` — replace it before submission.
- Non-US cities work, but citation guidance and schema defaults are US-oriented.

### Use with automation

Run it from Apify API, the Apify MCP server, Make/n8n/Zapier webhooks, or schedule it via the Apify Scheduler. Each run returns the full package in the default dataset — fetch it with `?format=json` and pipe the `files` into your storage, CMS or client delivery workflow.

# Actor input Schema

## `niche` (type: `string`):

The local service trade the website is for, e.g. plumber, roofer, electrician, HVAC, dentist, landscaper. Used to scope all copy and the schema.org business type.

## `city` (type: `string`):

The primary service city, e.g. Austin, Tampa, Seattle. Appears in headings, meta tags and the LocalBusiness service area.

## `stateCode` (type: `string`):

State or region code, e.g. TX, FL, WA, or a country for non-US (optional).

## `serviceList` (type: `array`):

Exact services to feature, e.g. \["drain cleaning", "water heater repair", "leak detection"]. When empty, the generator proposes 5-8 typical services for the niche in that city.

## `businessName` (type: `string`):

Real business name to place into headings, JSON-LD and citation placeholders. Leave empty to ship \[BUSINESS NAME] placeholders instead — the generator never invents one.

## `businessPhone` (type: `string`):

Real contact phone, e.g. (512) 555-0142. Left empty, \[PHONE] placeholders are emitted instead.

## `businessEmail` (type: `string`):

Real contact email. Left empty, \[EMAIL] placeholders are emitted instead.

## `streetAddress` (type: `string`):

Real street address for the LocalBusiness schema. Left empty, \[ADDRESS] placeholders are emitted instead.

## `businessHours` (type: `string`):

Real opening hours, e.g. Mon-Fri 8:00-18:00. Left empty, \[HOURS] placeholders are emitted instead.

## `websiteUrl` (type: `string`):

If the business already has a domain, include it so canonical URLs, sitemap and JSON-LD use real links instead of \[YOUR-DOMAIN].

## `tone` (type: `string`):

Voice of the generated copy.

## `llmModel` (type: `string`):

Model slug for copy generation on your endpoint. Defaults to openai/gpt-4o-mini; the openai/ prefix is stripped for native OpenAI endpoints. Use your provider's own slug with a custom llmBaseUrl.

## `llmApiKey` (type: `string`):

REQUIRED for a successful run: your own OpenAI-compatible API key (OpenAI, OpenRouter, Groq, Together, local gateway). Copy generation runs on this key and you pay the provider directly. The Apify-managed LLM proxy is disabled for this Actor, so a run without a key returns a structured error item naming the missing key instead of a package. Stored as a secret input; never written to the dataset or logs.

## `llmBaseUrl` (type: `string`):

OpenAI-compatible base URL used together with llmApiKey, e.g. https://api.openai.com/v1 (the default) or https://openrouter.ai/api/v1. Ignored when llmApiKey is empty.

## Actor input object example

```json
{
  "niche": "plumber",
  "city": "Austin",
  "stateCode": "TX",
  "businessName": "Bluebonnet Plumbing Co",
  "businessPhone": "(512) 555-0142",
  "businessEmail": "hello@exampleplumbing.com",
  "streetAddress": "1200 S Congress Ave, Austin, TX 78704",
  "businessHours": "Mon-Fri 08:00-18:00",
  "websiteUrl": "https://www.bluebonnetplumbing.com",
  "tone": "professional",
  "llmModel": "openai/gpt-4o-mini",
  "llmBaseUrl": "https://api.openai.com/v1"
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "niche": "plumber",
    "city": "Austin",
    "stateCode": "TX",
    "tone": "professional",
    "llmModel": "openai/gpt-4o-mini"
};

// Run the Actor and wait for it to finish
const run = await client.actor("gp005/local-service-site-generator").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "niche": "plumber",
    "city": "Austin",
    "stateCode": "TX",
    "tone": "professional",
    "llmModel": "openai/gpt-4o-mini",
}

# Run the Actor and wait for it to finish
run = client.actor("gp005/local-service-site-generator").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "niche": "plumber",
  "city": "Austin",
  "stateCode": "TX",
  "tone": "professional",
  "llmModel": "openai/gpt-4o-mini"
}' |
apify call gp005/local-service-site-generator --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,gp005/local-service-site-generator"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/HPigtg0QSpZDMIu3G/builds/HNvv6kuWn1McwPd2T/openapi.json