GEO Auditor — AI Search Readiness 🔍

foXLabs AI-visibility series: GEO benchmark · AI brand monitor

🎉 Audit any site for AI-search (GEO) readiness — no login, no API key, one row per page, with structured-data, answerability and citability checks. Built for SEO/GEO and content teams.

🔍 What is the GEO Auditor — and when should you use it?

Give this actor URLs or domains and it returns matching pages from a website’s content and structure (generative-engine optimisation audit) — as clean, deduplicated rows you can filter, export or feed to an AI agent. Every run reads the source live.

Use it when you need: a company list for outreach; a quick profile before a call; or a starting point for account research.

Use something else when: you need live AI-answer visibility — use the GEO Benchmark actor; this audits your own pages.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/geo-auditor.

Your agent can pay for its own runs. This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire — no Apify account or API token of its own. Billing is the same either way: per delivered record, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want to pull site company records using the Apify Actor `foxlabs/geo-auditor`.
Input: `websiteUrl`, `maxPages` — see the Input table below. 
Start with: {"websiteUrl":"https://www.notion.so"}
Ask me what to look up, run the Actor, then summarise the rows as a table.

The machine-readable API, MCP config and OpenAPI definition live at apify.com/foxlabs/geo-auditor.md.

📋 Overview

Everything you need to turn a website’s content and structure (generative-engine optimisation audit) into clean, structured data — in one actor, with no login, cookies or API key.

Why teams pick this actor:

• ✅ Whole audit, one call — name or ID in, matching pages out.
• 🧹 No empty-promise columns — only fields this registry actually fills; degenerate columns are removed.
• 🔗 Stable identifiers — every row carries the source's own IDs, ready to join across runs and to other Fox Labs actors.
• 💰 Per-row pricing — a minimal price per delivered row, no subscription.
• 🤖 Agent-ready — MCP + x402 agentic payments.

✨ Features

• 🔍 Name or ID lookup — relevance-ranked name search or exact registry-ID lookup.
• 🏢 Full entity profile — status, legal form, formation date, address and the registry’s own contact fields.
• 🧹 Clean schema — deduplicated camelCase rows, ready for CSV/Excel/JSON.

🎬 Quick Start

curl -X POST "https://api.apify.com/v2/acts/foxlabs~geo-auditor/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"websiteUrl":"https://www.notion.so"}'

🚀 Getting Started (3 steps)

1. Choose your targets — URLs or domains.
2. Review the options — every field is optional unless marked required.
3. Run and export — get a clean dataset as JSON, CSV or Excel.

📥 Input

{"websiteUrl":"https://www.notion.so"}

Field	Type	Description
websiteUrl	string	The website to audit for AI-search readiness (e.g. "https://www.notion.so"). We crawl this page and, up to your page limit, internal pages linked from it —…
maxPages	integer	How many internal pages to crawl & score (starting from the URL above). 1 = audit just that page. More pages = a fuller site picture, slightly higher cost.
proxyConfiguration	object	Leave OFF for fast, free audits — most sites work directly (we already auto-retry the www↔non-www variant). Turn on Apify Proxy with the RESIDENTIAL group ONLY…

📤 Output

One row per result, saved to the dataset. Every row carries scrapedAt. Lookups that cannot be completed are reported in the run log rather than silently dropped.

Field	Description
type	Type
url	Url
geoScore	Geo Score
band	Band
title	Title
wordCount	Word Count
hasJsonLd	Has Json Ld
headingOutlineText	Heading Outline Text
jsRenderedRisk	Js Rendered Risk
hasCanonical	Has Canonical
hasDates	Has Dates
accessScore	Access Score
structuredScore	Structured Score
extractabilityScore	Extractability Score
speedScore	Speed Score
trustScore	Trust Score
topIssuesText	Top Issues Text
domain	Domain
startUrl	Start Url
pagesAudited	Pages Audited
overallGeoScore	Overall Geo Score
dimensionScores	Dimension Scores
weakestDimensionsText	Weakest Dimensions Text
aiAccessText	Ai Access Text
blockedAiBotsText	Blocked Ai Bots Text
blockedTrainingBotsText	Blocked Training Bots Text
hasLlmsTxt	Has Llms Txt
robotsTxtFound	Robots Txt Found
prioritizedFixes	Prioritized Fixes
prioritizedFixesText	Prioritized Fixes Text
generatedAtIso	Generated At Iso

💼 Use cases

1. GEO audit — score a site’s AI-search readiness. Input: domains or URLs. Output: per-page checks. Use: a prioritised fix list.

2. Content QA — catch missing structured data. Input: URLs. Output: structured-data checks. Use: a QA report.

3. Migration checks — verify GEO signals after a change. Input: URLs. Output: readiness checks. Use: a before/after view.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/geo-auditor').call({"websiteUrl":"https://www.notion.so"});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/geo-auditor').call(run_input={"websiteUrl":"https://www.notion.so"})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Automation (n8n / Zapier / Make): schedule or webhook → HTTP request to the actor API with your input → handle the JSON dataset → push to a sheet, CRM or dashboard.

📊 Pricing

Pay-per-event: per delivered record. Empty or failed lookups are never billed. View current pricing.

❓ FAQ

Do I need an account, login or API key? No. This reads a website’s content and structure (generative-engine optimisation audit).

What do I search by? URLs or domains.

How current is the data? Every run queries the source live, so results are as fresh as the registry.

What does it check? Structured data, answerability, citability and content signals that affect how AI assistants read a page.

Can I export to CSV / Excel / JSON? Yes — directly from the Apify dataset.

🐛 Troubleshooting

• Fewer rows than expected — raise the result cap, or refine the input.
• A name returns an unexpected entity — it matched a similar registered name; search the exact registry ID.
• No rows for a name — try the entity’s exact legal name or its registry ID.

⚖️ Is it legal to scrape this data?

This actor fetches public web pages and audits them for AI-search readiness. Results can still contain personal data (e.g. a person’s name); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify’s blog post on the legality of web scraping.

🤝 Support & contact

• 🌐 Website: data.foxlabs.com.tr
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor’s Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

Changelog

0.1.19 — 2026-09-20 — README examples corrected against the real input schema

• The README's code examples did not match this Actor. They used queries and maxResultsPerQuery — keys that do not exist in this Actor's input schema — with a placeholder value, and the input table listed those same phantom fields. Anyone who copied the AI-agent, cURL, JavaScript or Python example got a failing run. Every example now uses the real schema and matches the Console prefill: {"websiteUrl":"https://www.notion.so"}
• The input table is regenerated from input_schema.json, so it lists the fields the Actor actually accepts.
• Removed claims carried over from the same generator template where present: "formation / status monitoring", "a canonical registry record for KYB and due diligence", "every row carries query", and industry described as a NACE code.
• No code, output field or pricing change.

0.1 — 2026-09-07

• Dropped empty-promise columns. Removed structuredDataText — a website’s content and structure (generative-engine optimisation audit) does not carry them, so they were shipped as always-null columns. Only fields this source actually fills are now emitted.
• Enabled AI-agent payments (x402) + rebuilt the README to the full standard (What-is / when, AI-agents + x402 agentic payments + MCP, Overview, Features, Use cases, Integration, FAQ, Troubleshooting, Support & contact).

0.0

• Initial release: data from a website’s content and structure (generative-engine optimisation audit) by name or registry ID.