Find what's broken. Your agent fixes it. LogNorm verifies.
A crawl-based SEO audit and a GEO audit for AI crawlers and agents, with every finding tied to its URL. Your agent fixes the cause in your codebase, and LogNorm re-checks the live pages until the move closes.
- criticalBroken internal links14 pages
- criticalAnswer-engine crawlers blockedGEO1 site
- warningMissing meta description23 pages
- warningThin contentAI-judged84%6 pages
- warningPages aren't available as markdown to AI agentsGEO1 site
Illustrative example. acme.com is a sample site.
- Sam's Panda commented on Fix broken internal linksRedirects added in next.config.ts
- Sam's Panda picked up Fix broken internal linksClaimed from this week's plan
- LogNorm found 934 pages returning 404SEO audit · critical
Audits are easy. Fixing is the hard part.
Audits list problems nobody has time to fix.
Fixes live in the codebase, far from the SEO tool.
Nobody checks whether the fix worked.
Found, fixed and verified in one loop
- 01Decide which fixes to take this week
- 02Review the pull request
- 03Merge and deploy
- 01Read every affected URL and the rule
- 02Fix the template, metadata or redirects
- 03Ship it, then ask LogNorm to re-check
- 01Crawl and audit on your schedule
- 02Check what AI crawlers and agents can read
- 03Re-check fixes on the live site
Every finding keeps its URL, so you can check it yourself
- Export all affected URLs for any rule as CSV.
- AI-judged checks are labelled as LogNorm's call, with a confidence.
- Each issue becomes a move with its pages attached.
- acme.com/blog/invoice-templateslinks to/templates/retainer404
- acme.com/pricinglinks to/features/multi-currency404
- acme.com/docs/getting-startedlinks to/docs/api-keys410
- + 11 more URLs in the export
Know what every page is for, and which pages you're missing
- Problem, solution, use case, integration, comparison, alternatives and pricing.
- Competitor coverage comes from analysing their sites.
- Each call shows its confidence and what it was based on.
Check whether AI crawlers can reach you and quote you
- Search, user-triggered and training crawlers are reported separately.
- Structured data, trust signals and freshness are checked too.
- The lowest-scoring pages get suggested rewrites.
- AllowedOAI-SearchBotOpenAI · Search
- AllowedClaude-SearchBotAnthropic · Search
- BlockedPerplexityBotPerplexity · Search
- AllowedChatGPT-UserOpenAI · User
- BlockedGPTBotOpenAI · Training
- acme.com/8/10
- acme.com/pricing7/10
- acme.com/features/recurring4/10
- acme.com/blog/late-payments2/10
See what AI agents find when they visit your site
- Markdown for agentsAccept: text/markdown returns HTML
- Content Signalssearch=yes, ai-input=yes, ai-train=no
- Link headersNo rel="describedby" or api-catalog link
- API catalog/.well-known/api-catalog
- MCP server card/.well-known/mcp/server-card.json
- A2A agent card/.well-known/agent-card.json
- OAuth discoveryShown for context, not scored
Generate the files that fix what the audit found
- llms.txt, llms-full.txt and a robots.txt AI section.
- A validated JSON-LD bundle, a fact sheet for AI assistants and the agent discovery kit.
- Definition, FAQ, comparison and glossary pages as starting drafts.
Content-Signal: search=yes, ai-input=yes, ai-train=no
User-agent: PerplexityBot
Allow: /
Validate a fix without a full re-audit
- Up to 1,500 affected pages re-fetched per validation.
- Daily, weekly or monthly schedules per website.
- Audit pages, exports and moves show only open findings.
An audit built to be acted on
29 SEO rules
Index status confirmed
Per-page detail
Score history
Findings become moves
Crawl coverage shown
From crawl to fixed, in four steps
Details in the site audit docs and the GEO audit docs.
- 1
Crawl
Add your website. LogNorm crawls it, classifies every page and runs the SEO audit. - 2
Run the GEO audit
Check AI crawler access, answerability, structured data and agent readiness. - 3
Fix
Work the moves, export URLs for your team, or build the GEO assets. - 4
Validate
Re-check one rule on the live site, or let the scheduled audit catch it.
SEO and GEO audit questions, answered
What does the SEO audit check?
LogNorm crawls your site and runs 29 rules: status codes and redirects, broken and redirected internal links, titles, meta descriptions and H1s, indexability and canonicals, thin and duplicate content, orphan and deep pages, image alt text, structured data on key pages, slow pages, sitemap, robots.txt and possible keyword cannibalisation.
How is a GEO audit different from an SEO audit?
An SEO audit asks whether search engines can crawl, index and rank your pages. A GEO audit asks whether AI assistants and agents can reach your pages, understand who you are and quote a clear answer: AI crawler access in robots.txt and at your CDN, llms.txt, structured data, entity clarity, answer-first content, trust signals and agent readiness.
Which findings are judged by AI, and how can I tell?
Thin content, keyword cannibalisation, page answerability and entity clarity need judgement rather than a count. Those findings are labelled as LogNorm's call and show its confidence. Everything else is a direct check of what the crawler fetched, such as a status code, a missing tag or a robots.txt rule.
Can I export the findings?
Yes. Every SEO rule and every GEO check exports all affected URLs as CSV, one rule at a time or everything at once. Exports only include findings that are still open.
Do I have to re-run the whole audit after fixing something?
No. Validate fix re-checks one rule on the live site: it re-fetches the affected pages (and link targets or duplicates where the rule needs them), marks fixed findings as resolved and updates the move with what is left. Robots and sitemap rules re-check the file. Orphan and depth rules need a full crawl, and site-wide or AI-judged GEO checks re-run the GEO audit.
What is agent readiness?
It checks what AI agents find when they visit your site through open standards: whether pages are served as markdown on request, whether robots.txt declares Content Signals, whether your home page sends useful Link headers, and whether you publish an API catalog, an MCP server card, an A2A agent card, an Agent Skills index or an AI catalog. OAuth discovery, auth.md, Web Bot Auth and DNS agent discovery are shown for context and not scored.
Can audits run on a schedule?
Yes. Per website, you can re-run the crawl and SEO audit daily, weekly or monthly on a paid plan or during the trial. The next run is counted from the last one, so a manual run pushes it out. If a scheduled run can't start, for example because you are out of credits, the reason is shown.
Can an AI agent fix the issues the audit finds?
Yes. Connect Claude Code, Codex or Cursor in the codebase that builds your site. It reads each finding with every affected URL, fixes the cause (templates, metadata, redirects, robots.txt, sitemaps, llms.txt), comments what it changed, and asks LogNorm to re-check the live pages. The move closes when everything passes.
Works with the rest of LogNorm
Audit your site for search and AI.
Start with a free growth scan, or create a workspace and run the full crawl, SEO audit and GEO audit.
Paste this into Claude Code, Codex, Cursor or Claude. It connects itself; you click Allow once.