SEO Auditor & Rank Tracker — BrightEdge Alternative

Audit a public website and optionally check Google keyword ranks. Get one report with technical issues, page evidence, prioritized fixes, robots and sitemap checks, and keyword observations for an SEO repair plan. For SEO consultants and launch teams, the dataset returns one combined site-audit and optional keyword-rank report.

Workflow: put the results to work

Start with the website you need to improve and a bounded crawl. Add the priority keywords when a rank snapshot will inform the repair plan. Review issue counts with the affected page evidence, then turn the proposed fixes into a scoped implementation queue.

Best fit for this Actor

• Audit a known public website through a bounded sample of 1–50 same-origin HTML pages.
• Review titles, meta descriptions, canonicals, headings, crawl directives, structured-data presence, image alt text, HTTP status, and initial response time.
• Check up to 10 supplied keywords in a current top-10 Google organic-result window for a chosen location, language, and device.
• Return one concise or detailed report that preserves evidence URLs, collection timestamps, scope notes, and warnings.

Choose BrightEdge when the work requires enterprise-scale crawling, historical rank tracking, collaborative dashboards, managed support, or a broader ongoing SEO program. This Actor focuses on one repeatable audit-and-rank-check workflow.

How this workflow compares with BrightEdge

This Actor is a focused BrightEdge alternative for an on-demand public-site audit plus optional current keyword checks. BrightEdge remains the broader platform for estate-scale crawling, long-term reporting, and enterprise SEO operations.

Decision	This Actor	BrightEdge	Best fit
Scope	One public site, a 1–50 page HTML sample, and up to 10 supplied queries	Broader ContentIQ crawling and enterprise SEO workflows	Use this Actor for a scoped checkpoint; use BrightEdge for larger programs
Billing	Pay per completed report plus Apify platform usage	Enterprise purchasing process	Match the billing model to the frequency and breadth of the work
Output	One structured report with findings, fixes, page observations, and rank statuses	Dashboards and reports across a broader platform	Use the format that fits the next review or handoff
Effective efficiency	One report concentrates page evidence, query statuses, and prioritized actions	Wider workflows coordinate a broader SEO program	Use this Actor when one scoped report can drive the next action
Automation	Repeatable JSON input, dataset output, API, and CLI execution	Wider managed platform workflows	Use this Actor for a bounded programmatic run
Freshness and provenance	Evidence URLs and collection timestamps are included in each report	Broader monitoring and reporting operations	Use this Actor when the immediate observation trail matters
Broader product	No historical rank series, collaboration suite, or full-estate crawler	Designed for wider enterprise SEO management	Keep BrightEdge for suite-level requirements

What the audit checks

Area	Observed signals
Crawl access	Starting-page response, robots.txt, wildcard blocks, sitemap reachability, and same-origin discovery
On-page SEO	Title, meta-description, canonical, noindex, H1 count, and document language
Media and markup	Images missing non-empty alt text and JSON-LD presence in the initial HTML
Response evidence	HTTP status and initial server response time for sampled pages
Rank context	Optional current top-10 organic result status, observed position, result URL, title, and SERP features per supplied keyword

The technical score is a transparent triage signal derived from the observed findings. Google ranking performance remains a separate measurement.

Example workflow

A technical marketer starts with a public launch URL and the queries that matter to the release. The Actor samples the chosen site scope, records crawlability and on-page evidence, and returns findings, recommendations, pageObservations, and rankSnapshots. The marketer can then assign each evidence-linked fix to a developer or use the report as a documented launch checkpoint.

Quick start input

{
    "siteUrl": "https://example.com",
    "keywords": ["technical seo audit", "seo site audit"],
    "includeRankSnapshot": true,
    "locationCode": 2840,
    "languageCode": "en",
    "device": "desktop",
    "maxPages": 10,
    "checkLinks": true,
    "respectRobotsTxt": true,
    "requestTimeoutSecs": 20,
    "responseFormat": "concise"
}

Use maxPages to control the HTML sample size. The optional keywords list defines the current visibility questions; each query receives an explicit found, not_found, or unavailable status.

Input reference

Field	What it controls
siteUrl	Required public HTTP or HTTPS starting URL; credentials and private-network hosts are rejected
maxPages	Same-origin HTML sample from 1 to 50 pages; defaults to 10
keywords	Up to 10 plain-language queries for optional current rank checks
includeRankSnapshot	Enables or skips keyword-provider requests
locationCode	Google location identifier used only for rank checks
languageCode	Google language code used only for rank checks
device	Desktop or mobile rank-check context
checkLinks	Discovers same-origin links until the page cap is reached
respectRobotsTxt	Applies wildcard robots directives to discovered pages
requestTimeoutSecs	Per-request timeout from 5 to 60 seconds
responseFormat	Concise decision report or detailed page observations

Output data you receive

One dataset item represents one SEO audit and rank-check report for the supplied public site.

Field	Meaning
siteUrl, auditedAt	Normalized site origin and report collection time
overallScore, issueCounts	Transparent technical triage score and severity totals
findings	Technical observations with severity, code, evidence URL, and recommended action
recommendations	Prioritized action queue derived from observed findings and rank statuses
pageObservations	Sampled response, metadata, heading, image, indexation, and structured-data signals
rankSnapshots, rankSummary	Per-query current result evidence and found/not-found/unavailable totals
robots, sitemap	Crawl-policy and sitemap reachability observations
provenance, limitations, warnings	Source boundaries and interpretation context

{
    "siteUrl": "https://example.com",
    "auditedAt": "2026-09-07T12:00:00.000Z",
    "overallScore": 76,
    "pagesRequested": 10,
    "pagesAudited": 8,
    "issueCounts": { "critical": 0, "warning": 2, "info": 4 },
    "findings": [
        {
            "severity": "warning",
            "code": "canonical-missing",
            "evidenceUrl": "https://example.com/",
            "recommendation": "Add an intentional canonical URL when this page should be indexed."
        }
    ],
    "rankSnapshots": [
        {
            "keyword": "technical seo audit",
            "status": "not_found",
            "position": null,
            "resultUrl": null
        }
    ],
    "provenance": {
        "technicalSource": "public-http-html-and-same-origin-sitemap-sample",
        "rankSource": "live-google-organic-results"
    },
    "limitations": ["The crawl is a bounded sample, not a full-site crawl."],
    "warnings": []
}

The dataset, OUTPUT, and RUN_SUMMARY support deterministic readback. Preserve the provenance, evidence URLs, and timestamps when passing findings into another workflow.

Use through the API

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~brightedge-alternative/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"siteUrl":"https://example.com","keywords":["technical seo audit"],"maxPages":5}'

Read the run’s default dataset for the report and inspect OUTPUT or RUN_SUMMARY for the terminal outcome and charge diagnostics.

AI agent and MCP prompt card

Use the prompt with an Apify agent workflow, then inspect the terminal outcome and dataset readback. Preserve provenance, collection time, scope notes, and the billing summary when paginating or passing the report onward.

Run khadinakbar/brightedge-alternative for https://example.com with a 10-page scope and the supplied priority keywords. Return the terminal outcome, overall score, issue counts, source-linked recommendations, rank statuses, collection time, and billing summary. Preserve unavailable statuses and scope notes instead of guessing missing evidence.

Limits and interpretation

• The crawler reads public initial HTML and follows same-origin discovery within the page cap. Browser-rendered and enterprise-scale crawling remain separate workflows.
• Link discovery supports sampling within the page cap; complete broken-link inventories require a dedicated crawl.
• Rank checks cover a current top-10 organic-result window. Historical series and search-ranking outcomes remain separate measurements.
• When configured provider responses are unavailable, rank entries retain an explicit unavailable status while the technical audit still returns useful evidence.
• Initial response time is a server observation; Core Web Vitals and browser performance remain separate measurements.

Best results

• Start with the canonical public URL for the site or launch surface you need to review.
• Use a concise report for triage and detailed output when a developer needs more page observations.
• Supply only decision-relevant keywords and choose the location, language, and device that match the intended market.
• Compare later runs by their timestamps and source evidence rather than treating the score as a search-engine metric.

Builder's note

While testing this workflow, I found that a standalone score was much less useful than an evidence trail. That is why every report keeps source URLs, explicit collection times, scope notes, and prioritized actions together: the next person can see what was observed before deciding what to change.

Responsible use

Use this Actor on public sites you own or are authorized to assess. Follow applicable laws, site terms, and robots directives, and handle any collected information according to your organization’s policies.

Brand disclosure

BrightEdge is a trademark of its owner. This independent Actor is not affiliated with, associated with, or endorsed by BrightEdge.

Pricing and run costs

This Actor uses Pay per event plus Apify platform usage. The Pricing tab lists the current event rates and billing terms.

Event	Billing unit	When it applies
apify-actor-start	Actor Start	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
seo-opportunity-report	SEO opportunity report	One persisted, source-linked technical SEO opportunity report for one public website.

Run cost combines the charged events and Apify platform usage. Review the run charge limit and requested result count before starting.

Connect an AI agent

Use the Apify MCP configurator to choose an available client connection. Inspect this Actor’s current input schema and required credentials before running it.