# SEO/GEO Launch Config Pack (`bread-kim/seo-geo-launch-config-pack`) Actor

Generate launch-ready SEO and GEO configuration files from your page list. Create meta tags, canonical URLs, sitemap data, structured data, and a downloadable ZIP package for implementation. No ranking or AI visibility guarantee.

- **URL**: https://apify.com/bread-kim/seo-geo-launch-config-pack.md
- **Developed by:** [bread kim](https://apify.com/bread-kim) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$20.00 / 1,000 results

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

## SEO/GEO Launch Config Pack

This private Apify Actor turns an authoritative owned-site inventory into an actual binary `SEO_GEO_CONFIG.zip`: coordinated `sitemap.xml`, a conservative new-site `robots.txt` template, metadata mapping, per-page head snippets, application instructions, QA evidence, and a byte-accurate manifest. It never crawls, deploys, calls a model, or accesses the submitted origin.

### Use

Submit `site` and 1–100 `pages` following [`examples/input.json`](examples/input.json). Paths and IDs must be unique. `indexable` is always explicit. Omitted `canonicalPath` means self-canonical. An alias may reference only an indexable self-canonical page in the same inventory. A noindex page may only self-canonicalize. `lastModified` is optional and never invented.

For valid input the Actor stores the authoritative `OUTPUT` record, exactly one identical dataset item, the binary ZIP, and separately accessible component records. For invalid input it stores only a generic `INVALID_INPUT` OUTPUT without echoing submitted data. Outputs are capped at 2 MiB.

### Apply safely

Read `APPLY.md` first. Compare existing robots, sitemap, privacy/security rules, and head policy. Replace only the corresponding per-page title, meta, canonical, Open Graph, and reviewed WebPage JSON-LD instead of appending duplicates. Preserve Product, Article, Organization, and all other unrelated structured-data scripts. Confirm visible facts and canonical equivalence, then verify deployed HTTP status, content types, actual rendered head, robots, and sitemap. Search Console submission is manual.

This is a configuration proposal, not a website builder or live-site proof. It does not verify ownership/content, enforce privacy, or guarantee indexing, rank, rich results, or AI citations. Normal SEO practices remain relevant to AI search features; no special schema or `llms.txt` is generated.

### Local verification

Requires Node.js 22.23.3.

```sh
npm ci --ignore-scripts
npm test
npm run typecheck
npm run build
AUTOMATON_CONTAINER_SMOKE=1 node dist/main.js
```

For local storage execution, set `CRAWLEE_STORAGE_DIR` to an absolute disposable directory containing `key_value_stores/default/INPUT.json`. No runtime dependencies are installed.

Official background: [AI features and your website](https://developers.google.com/search/docs/appearance/ai-features), [AI optimization guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide), [canonical URLs](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls), [sitemaps](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap), [structured-data policies](https://developers.google.com/search/docs/appearance/structured-data/sd-policies), and [robots.txt](https://developers.google.com/search/docs/crawling-indexing/robots/intro).

# Actor input Schema

## `site` (type: `object`):

Owned public HTTPS site and its factual name.

## `pages` (type: `array`):

One to 100 authoritative page facts. Every page explicitly declares indexability.

## Actor input object example

```json
{
  "site": {
    "origin": "https://example.com",
    "name": "Example Studio"
  },
  "pages": [
    {
      "id": "home",
      "path": "/",
      "title": "Example Studio — Design and development",
      "description": "Example Studio designs and develops websites.",
      "language": "en",
      "indexable": true
    },
    {
      "id": "guide",
      "path": "/guides/launch",
      "title": "Site Launch Checklist",
      "description": "A practical checklist for launching a website.",
      "language": "en",
      "indexable": true,
      "lastModified": "2026-10-01"
    },
    {
      "id": "alias",
      "path": "/old-guide",
      "title": "Site Launch Checklist",
      "description": "An older address for the site launch checklist.",
      "language": "en",
      "indexable": true,
      "canonicalPath": "/guides/launch"
    },
    {
      "id": "thankyou",
      "path": "/thank-you",
      "title": "Thank you",
      "description": "Confirmation that a requested action was received.",
      "language": "en",
      "indexable": false
    }
  ]
}
```

# Actor output Schema

## `output` (type: `string`):

The authoritative configuration result.

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

Exactly one copy of the authoritative OUTPUT record for valid input.

## `zip` (type: `string`):

Real binary ZIP containing coordinated launch files.

## `sitemap` (type: `string`):

Generated indexable self-canonical URL set.

## `robots` (type: `string`):

Permissive new-site template requiring policy review.

## `apply` (type: `string`):

Owner/developer integration and verification steps.

## `manifest` (type: `string`):

SHA-256 and exact byte size of each ZIP member except the manifest itself.

# 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 = {
    "site": {
        "origin": "https://example.com",
        "name": "Example Studio"
    },
    "pages": [
        {
            "id": "home",
            "path": "/",
            "title": "Example Studio — Design and development",
            "description": "Example Studio designs and develops websites.",
            "language": "en",
            "indexable": true
        },
        {
            "id": "guide",
            "path": "/guides/launch",
            "title": "Site Launch Checklist",
            "description": "A practical checklist for launching a website.",
            "language": "en",
            "indexable": true,
            "lastModified": "2026-10-01"
        },
        {
            "id": "alias",
            "path": "/old-guide",
            "title": "Site Launch Checklist",
            "description": "An older address for the site launch checklist.",
            "language": "en",
            "indexable": true,
            "canonicalPath": "/guides/launch"
        },
        {
            "id": "thankyou",
            "path": "/thank-you",
            "title": "Thank you",
            "description": "Confirmation that a requested action was received.",
            "language": "en",
            "indexable": false
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("bread-kim/seo-geo-launch-config-pack").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 = {
    "site": {
        "origin": "https://example.com",
        "name": "Example Studio",
    },
    "pages": [
        {
            "id": "home",
            "path": "/",
            "title": "Example Studio — Design and development",
            "description": "Example Studio designs and develops websites.",
            "language": "en",
            "indexable": True,
        },
        {
            "id": "guide",
            "path": "/guides/launch",
            "title": "Site Launch Checklist",
            "description": "A practical checklist for launching a website.",
            "language": "en",
            "indexable": True,
            "lastModified": "2026-10-01",
        },
        {
            "id": "alias",
            "path": "/old-guide",
            "title": "Site Launch Checklist",
            "description": "An older address for the site launch checklist.",
            "language": "en",
            "indexable": True,
            "canonicalPath": "/guides/launch",
        },
        {
            "id": "thankyou",
            "path": "/thank-you",
            "title": "Thank you",
            "description": "Confirmation that a requested action was received.",
            "language": "en",
            "indexable": False,
        },
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("bread-kim/seo-geo-launch-config-pack").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 '{
  "site": {
    "origin": "https://example.com",
    "name": "Example Studio"
  },
  "pages": [
    {
      "id": "home",
      "path": "/",
      "title": "Example Studio — Design and development",
      "description": "Example Studio designs and develops websites.",
      "language": "en",
      "indexable": true
    },
    {
      "id": "guide",
      "path": "/guides/launch",
      "title": "Site Launch Checklist",
      "description": "A practical checklist for launching a website.",
      "language": "en",
      "indexable": true,
      "lastModified": "2026-10-01"
    },
    {
      "id": "alias",
      "path": "/old-guide",
      "title": "Site Launch Checklist",
      "description": "An older address for the site launch checklist.",
      "language": "en",
      "indexable": true,
      "canonicalPath": "/guides/launch"
    },
    {
      "id": "thankyou",
      "path": "/thank-you",
      "title": "Thank you",
      "description": "Confirmation that a requested action was received.",
      "language": "en",
      "indexable": false
    }
  ]
}' |
apify call bread-kim/seo-geo-launch-config-pack --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bread-kim/seo-geo-launch-config-pack"
        }
    }
}
```

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/Ba9a8Ea4iTjEs2wO5/builds/cmY9018PbL5LSYAN1/openapi.json