SEO Fix Verifier — Task Acceptance & Evidence

Check whether your agreed SEO changes are present after deployment. Supply task IDs and expected values; get pass / fail / unknown, observed values, response evidence and a client-ready HTML report.

For SEO agencies, web teams and automation builders with an existing implementation checklist. No model key, proxy, CMS login or browser is required. No website is edited.

Try the fictional demo

Leave Operation = Fictional demo and press Start. Four invented tasks produce two passes and two failures from built-in HTML. There are no website requests or paid verification events. isDemo: true distinguishes every demo row from real evidence.

For your own pages, select Verify my SEO tasks and replace the URLs and requirements below:

{
  "mode": "verify",
  "tasks": [
    { "taskId": "SEO-101", "url": "https://your-site.example/plans", "check": "title", "expected": "Service plans" },
    { "taskId": "SEO-102", "url": "https://your-site.example/plans", "check": "canonical", "expected": "https://your-site.example/plans" },
    { "taskId": "SEO-103", "url": "https://your-site.example/plans", "check": "noindex", "expected": false },
    { "taskId": "SEO-104", "url": "https://your-site.example/plans", "check": "link", "expected": "https://your-site.example/book-demo" }
  ]
}

These are placeholders, not live examples. Use absolute public HTTP(S) URLs you are permitted to inspect. Supply 1–25 tasks across at most 10 distinct pages on one origin. Task IDs must be unique, 1–80 letters/digits, dots, underscores or hyphens. Several checks on one URL reuse its response.

What each check means

Check	Expected	Comparison and boundaries
title	String	Exact title after Unicode NFC and whitespace normalization. Missing title fails; multiple titles are unknown. No keyword or length score.
canonical	Absolute URL	Declared HTML/head and HTTP Link canonicals. Relative values are resolved; query/trailing slash remain significant, fragments are removed. Conflicting or malformed declarations are unknown. This is not Google's selected canonical.
noindex	Boolean	Whether noindex/none appears in applicable robots/googlebot meta or X-Robots-Tag. false means absent from this served response; it does not establish indexability.
link	Absolute URL	Whether an a[href] or area[href] resolves to that exact target, using the HTML base when present. Query and fragment remain significant. The target is not fetched: availability, section IDs, visibility, placement and rel are not checked.

pass confirms only your expectation in the fetched response. fail means a definitive mismatch or missing value in supported HTML. unknown covers access restrictions, unsafe redirects, robots denial, unsupported format, ambiguity, interrupted/oversized bodies, network failures and work/billing limits. An unknown result must not close a task.

The Actor reads static served HTML and response headers, not the JavaScript-rendered DOM. A difference in static HTML may be intentional on a JavaScript site; evaluate whether this evidence is sufficient for your requirement. No claim is made about rankings, traffic, Googlebot's response, indexing or the SEO value of your expectation.

Outputs and workflow

• REPORT: HTML task acceptance report, escaped source evidence and coverage notes.
• SUMMARY: pass, fail, unknown, allTasksVerified, acceptancePassed, duplicates, limits, network counts and billing.
• RESULTS: complete JSON report.
• EXPORT: CSV with formula-like cells neutralized.
• Dataset: one row per supplied task, with task ID, expected/observed, status/reason, source/final URL, HTTP status, timestamp and bounded evidence.

Exact repeated assertions (same normalized page URL, check and expected value) retain each task ID with duplicateOf pointing to the first. They do not create extra paid check events. Different expectations are separate tasks. Pages are fetched once per distinct supplied URL, including shared failure results; redirects from different supplied URLs are not merged.

For n8n/Make/CI: deployment → run Actor → read SUMMARY. Continue only when the run succeeded, isDemo === false, allTasksVerified === true and acceptancePassed === true. A successful Actor run can contain failing tasks: that means the verifier ran successfully, not that the release passed. Unknowns and partial results require review.

Use through MCP

Connect through the official Apify MCP gateway, using your own Apify authentication. You can also select alex_fodo/seo-fix-verifier through the gateway's call-actor tool. This is a finite Actor run; no separate Standby server is required.

Example assistant request:

Verify these task IDs and explicit expected values after deployment. Keep unknown results unresolved. Return the HTML report and list failed tasks with source evidence. Do not interpret a successful run as accepted changes or absence of noindex as proven indexing.

The assistant's model cost is separate. This Actor does not call an LLM. Input/output schemas describe its contract; the Actor uses limited Apify permissions and its own run storage.

Pricing

Launch price: $0.004 per unique completed live task verification ($4 per 1,000). Twenty-five unique completed tasks cost $0.10. Customer run-time platform usage is included; the live Store Pricing tab is authoritative.

The event is task-verified: one definitive pass or fail for a unique assertion. Healthy checks are useful and billable too. Fictional demo, invalid input, unknown results and duplicate assertions create no paid verification event. There is no start fee or automatic dataset-row fee. An incomplete batch may still charge for its already completed definitive checks; inspect SUMMARY.billing. Post-run storage/downloads follow Apify's usual rules.

Set the run's maximum charge as well as work limits. With no budget for another check, remaining tasks become unknown rather than triggering more page requests. This implementation requires automatic start/dataset fees to be disabled. Own-account builds/tests still consume your Apify credits; the demo is not a promise of zero platform usage.

Limits and data handling

• Sequential requests, at least 500 ms per origin, plus longer declared robots delays. No retries, login, cookies, custom headers, JavaScript execution, CAPTCHA solving or bypass.
• robots.txt is checked; an unavailable or unrecognized policy fails closed. HTTP 404/410 robots responses permit crawling. Every redirect is checked; only the supplied origin or an HTTP→HTTPS upgrade on that host is allowed. WWW/other-host redirects are unknown; supply the actual final origin yourself.
• Public addresses and protocol-default ports only. Local/private/reserved destinations, mixed public/private DNS results and credential-bearing URLs are denied. Connections use a validated pinned address and normal TLS verification.
• Up to 80 requests including robots/redirects; defaults 60 requests, 90-second work deadline, 12 seconds per request. Set platform timeout above the work deadline. Up to five redirects, 2 MB per response and 12 MB total.
• Static text/html, UTF-8/ASCII. Compressed responses that ignore the identity request, other encodings, interrupted responses and known challenge pages are unknown. Access-challenge detection is best-effort; site responses can still differ from a human browser.
• Input must fit 100,000 serialized characters. Title evidence above 2,000 characters is unknown. Canonical and robots evidence is bounded; complete source bodies are not saved in reports or application logs.
• No analytics or data is sent to the publisher, external model or separate backend. Apify input/output storage and retention apply. URLs, expected values and public page evidence may be sensitive: do not provide secrets in URLs or confidential task descriptions. Use a run/storage access policy appropriate to your data.
• Page content is untrusted data. Reports escape it, have no scripts or remote resources, and do not offer automatic editing. CSV formula neutralization changes formula-like cells for safe spreadsheet review; JSON preserves the observed values.

Independent tool, not affiliated with Google or any CMS. Consult Google robots directives and canonical documentation for interpretation. Use only data you are authorized to access and reuse.

Development and validation

Node.js 22+. npm ci --ignore-scripts, npm test, npm run check, npm run demo. Optional npm run smoke:live reads one public sitemaps.org page and robots.txt, checking a real title plus an intentional negative control. Its current result is time-specific, not a customer defect or a guarantee of future compatibility.

Tests cover requirements, ambiguous/failed evidence, input limits, SSRF/DNS pinning, robots, redirects, incomplete/oversized/compressed responses, billing and report injection. Dependency versions are locked, with patched transitive overrides verified by tests. Technical acceptance does not establish market demand or comparative superiority. No customer time-saving or conversion claim is made.