# Local Landing Page SEO Auditor (`junipr/local-landing-page-seo-auditor`) Actor

Audit city/location landing pages for local SEO completeness, local evidence, service fit, contact clarity, internal links, and conversion readiness

- **URL**: https://apify.com/junipr/local-landing-page-seo-auditor.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** SEO tools, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.50 / 1,000 local page scanneds

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Local Landing Page SEO Auditor

Audit city, location, and service-area landing pages for local SEO completeness, business evidence, service fit, contact clarity, internal links, and conversion readiness.

### What you get

- Fetch supplied pages directly, discover URLs from XML sitemaps, or analyze supplied HTML snapshots.
- Check titles, meta descriptions, H1s, NAP details, LocalBusiness schema, map links, review signals, calls to action, and internal links.
- Verify configured locations, services, NAP profiles, and transparent regular-expression content rules.
- Return a factor-level completeness score, exact missing elements, source evidence, and prioritized remediation.
- Restrict discovery by domain, page count, crawl depth, timeouts, and request delay.

### Input

```json
{
  "startUrls": [
    "https://example.com/locations/austin"
  ],
  "sitemapUrls": [],
  "allowedDomains": [
    "example.com"
  ],
  "maxPages": 5,
  "maxDepth": 1,
  "maxCompetitorPages": 2,
  "targetKeywords": [
    "emergency plumbing"
  ],
  "targetLocations": [
    "Austin"
  ],
  "requiredLocalElements": [
    "phone",
    "address",
    "schema",
    "cta"
  ],
  "napProfiles": [
    {
      "name": "Example Plumbing",
      "address": "100 Main St, Austin, TX",
      "phone": "+1-512-555-0100"
    }
  ],
  "compareAgainstCompetitors": false,
  "localContentRules": [
    {
      "name": "license evidence",
      "pattern": "licensed|insured",
      "severity": "medium"
    }
  ],
  "includeEvidence": true,
  "includeRawSnapshots": false,
  "requestDelayMs": 250,
  "timeoutMs": 15000,
  "userAgentMode": "standard",
  "maxChargeUsd": 15,
  "includeReport": true
}
```

Use `htmlInputs` when you already have source HTML or need deterministic recurring analysis. URL runs accept normal public HTTP(S) pages. Private-network and unsupported URL targets are rejected.

### Dataset output

Each dataset item is a complete, schema-defined record. Fields that are not present in the source remain `null` rather than being guessed.

```json
{
  "sourceUrl": "https://example.com/locations/austin",
  "recordType": "local_landing_page_audit",
  "issueCode": "local_landing_page_seo_auditor_gap_found",
  "severity": "medium",
  "targetLocation": "Austin",
  "targetKeyword": "emergency plumbing",
  "localCompletenessScore": 83,
  "missingElements": [
    "map",
    "reviews"
  ],
  "evidenceSnippet": "Visible page text around the configured local evidence.",
  "recommendation": "Add or correct the missing page-specific local evidence."
}
```

### Reports

A successful run can write:

- `local-landing-page-seo-auditor-summary-report.md`
- `local-landing-page-seo-auditor-records.csv`
- `local-landing-page-seo-auditor-issues.json`
- `local-landing-page-seo-auditor-evidence-samples.json`
- `local-landing-page-seo-auditor-run-metadata.json`

Reports include row counts, issue severities, evidence references, recommendations, and the input fields consumed by the run.

### Pricing and cost controls

This actor uses pay-per-event pricing with Apify platform usage pass-through off:

- actor-start — $0.01000 per run
- local-page-scanned — $0.00650 per page
- local-finding-emitted — $0.00295 per finding
- record-extracted — $0.00295 per extracted record
- audit-report-generated — $0.08000 per report

The default `maxChargeUsd` is $15. The runtime checks the local budget and the Apify charge result before every paid dataset item. If either limit is reached, it stops before emitting unpaid output and writes billing diagnostics to key-value storage.

### Safe crawling behavior

- Public HTTP(S) sources only.
- Private-network, localhost, and unsupported protocol targets are rejected.
- `allowedDomains`, `maxPages`, actor-specific caps, `maxDepth`, `timeoutMs`, and `requestDelayMs` bound discovery.
- Supplied HTML is processed without an external request.
- Protected or authenticated sources are outside the supported public-data scope.

### Limitations

- The score reflects configured on-page evidence; it is not a search ranking prediction.
- JavaScript-only content that is absent from returned HTML may require a supplied snapshot.
- Competitor inputs must be supplied explicitly and marked with `sourceType: competitor`.

### Common use cases

- Audit location pages before a redesign.
- Find missing local proof across service pages.
- Export evidence-backed city-page remediation actions.

# Actor input Schema

## `startUrls` (type: `array`):

Public city, service-area, or location landing pages to audit.

## `sitemapUrls` (type: `array`):

Optional public XML sitemaps used to discover landing pages.

## `htmlInputs` (type: `array`):

Optional source-backed HTML snapshots for deterministic audits.

## `allowedDomains` (type: `array`):

Optional domain allowlist for URL and sitemap discovery.

## `maxPages` (type: `integer`):

Maximum pages fetched or analyzed.

## `maxDepth` (type: `integer`):

Internal-link discovery depth from each start URL.

## `maxCompetitorPages` (type: `integer`):

Maximum HTML inputs marked sourceType=competitor included in comparison rollups.

## `includeEvidence` (type: `boolean`):

Include visible source excerpts in output rows.

## `includeRawSnapshots` (type: `boolean`):

Reserve raw source snapshots in run artifacts when enabled.

## `requestDelayMs` (type: `integer`):

Delay between public HTTP requests in milliseconds.

## `timeoutMs` (type: `integer`):

Per-request timeout in milliseconds.

## `userAgentMode` (type: `string`):

Normal HTTP user-agent profile.

## `targetKeywords` (type: `array`):

Expected services or search phrases checked against visible page text.

## `targetLocations` (type: `array`):

Expected city, county, or service-area modifiers.

## `requiredLocalElements` (type: `array`):

Optional override for completeness checks.

## `napProfiles` (type: `array`):

Optional expected business name, address, and phone records.

## `compareAgainstCompetitors` (type: `boolean`):

Include HTML inputs marked sourceType=competitor in comparison evidence.

## `localContentRules` (type: `array`):

Transparent regular-expression checks for required visible content.

## `maxChargeUsd` (type: `number`):

Maximum estimated PPE spend before a graceful stop.

## `includeReport` (type: `boolean`):

Write Markdown, CSV, JSON evidence, and run metadata to key-value storage.

## Actor input object example

```json
{
  "startUrls": [
    "https://example.com/"
  ],
  "sitemapUrls": [],
  "htmlInputs": [],
  "allowedDomains": [],
  "maxPages": 1,
  "maxDepth": 0,
  "maxCompetitorPages": 3,
  "includeEvidence": true,
  "includeRawSnapshots": false,
  "requestDelayMs": 250,
  "timeoutMs": 15000,
  "userAgentMode": "standard",
  "targetKeywords": [],
  "targetLocations": [],
  "requiredLocalElements": [],
  "napProfiles": [],
  "compareAgainstCompetitors": false,
  "localContentRules": [],
  "maxChargeUsd": 15,
  "includeReport": true
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `report` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("junipr/local-landing-page-seo-auditor").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("junipr/local-landing-page-seo-auditor").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 '{}' |
apify call junipr/local-landing-page-seo-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/local-landing-page-seo-auditor"
        }
    }
}

```

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/lyCHKS4Vxco8Z94fy/builds/fAJd948DMe1gieV2N/openapi.json