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

{
  "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.

{
  "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.