The direct answer

An ANI audit evaluates every technical signal that determines whether AI crawlers can access, correctly read, and accurately attribute your content. This step-by-step audit process covers crawler access, HTML structure, author attribution, structured data, and entity signals — producing a prioritized list of improvements that directly increases AI indexing accuracy.

Before you start — establish your baseline

Before auditing your site for ANI signals, check your server access logs for AI crawler visits. Log into your hosting control panel, find your raw access logs, download the most recent file, and search for GPTBot, PerplexityBot, and ClaudeBot. Record what you find — this is your baseline. After fixing the issues the audit reveals, checking the logs again in 2 to 4 weeks will confirm whether the fixes are working.

Section 1: Crawler Access Audit (15 minutes)

1. Visit yoursite.com/robots.txt in your browser. Confirm GPTBot, PerplexityBot, ClaudeBot, Google-Extended, and OAI-SearchBot each have explicit Allow: / rules.
2. In Rank Math > General Settings > Edit robots.txt, confirm the rules are present and there are no conflicting broad Disallow rules.
3. Check your security plugin (Wordfence, Sucuri, or iThemes) for any bot blocking settings that might affect AI crawlers.
4. Visit yoursite.com/llms.txt — confirm it loads and contains your site description and core page links.

Section 2: HTML Structure Audit (20 minutes)

1. Open your 5 highest-traffic pages. For each one, View Page Source and search for MsoNormal — any results indicate Word paste artifacts.
2. In the same page source, search for <h1 and count occurrences — should be exactly 1 per page.
3. In Gutenberg Document Overview panel, verify heading hierarchy is correctly nested for each page.
4. Search for <main in page source — confirm the primary content is wrapped in a semantic main element.
5. Count instances of <span style= in the content area — more than 5 suggests formatting noise from pasted content.

Section 3: Attribution Audit (20 minutes)

1. Go to Users > Your Profile. Confirm First Name, Last Name, Biographical Info, and Profile Photo are all completed.
2. Go to Rich Results Test and test your homepage — confirm Organization or Person schema is present with green checkmarks.
3. Test your About page — confirm Person schema shows your name, bio, and social profile URLs.
4. Test a blog post — confirm Article schema includes author name (not “admin”) and both datePublished and dateModified.
5. Check that Simple Author Box is displaying on posts and pages with your name and social links visible.

Prioritizing the fixes

Fix crawler access issues first — they block all other ANI signals from working. Then fix attribution issues — they require one-time setup and pay ongoing dividends. Then address HTML structure issues on your highest-traffic pages — these take the most time per page but have the highest citation quality impact. Schedule HTML structure improvements as a rolling monthly task rather than trying to fix everything at once.

How ANI, AEO, GEO, SEO, and ASI work together here

ANI is the technical foundation that makes every other optimization discipline effective. Every improvement you make to your crawler access, HTML structure, or author attribution directly benefits your AEO citation rates, your GEO topical authority recognition, and your SEO technical health simultaneously. ANI work is not siloed — it compounds across all five disciplines at once.

Related ANI guides

ANI audit process · ANI checklist · What happens when AI crawlers can’t read your site

The complete ANI guide library at teachmeoptimization.com/ani covers all 24 topics across five categories — from fundamental concepts to step-by-step implementation and quarterly audit processes.

Common mistakes to avoid

A common audit mistake is trying to fix everything found in a single audit session. An ANI audit produces a prioritized list of improvements, not a to-do list to complete in one day. Crawler access issues should be fixed immediately. Attribution issues should be addressed in the week following the audit. HTML structure issues should be scheduled as a rolling monthly improvement task. This prioritization ensures the most impactful fixes happen first without overwhelming the implementation process.

Quick implementation checklist

• Schedule ANI audit for 90 minutes at the end of each quarter
• Fix crawler access issues (robots.txt, security plugin) within 24 hours of finding them
• Complete attribution fixes (schema, user profile, author box) within one week
• Schedule HTML structure cleanup at one page per week pace
• Re-run Rich Results Test after each attribution fix to verify schema is correct
• Re-check server logs 4 weeks after fixing any crawler access issues

How this connects to the full ANI system

The ANI audit is the quarterly checkpoint that keeps your technical AI accessibility foundation solid as your site grows and your WordPress plugins update. Without regular audits, new blocking issues can accumulate unnoticed. For the complete ANI implementation guide covering all 24 topics in sequence, see the full ANI guide at teachmeoptimization.com/ani.

Measuring improvement

After implementing the steps in this guide, revisit your server access logs in 2 to 4 weeks to confirm AI crawler visits. Run your site through the free TeachMeOptimization scanner to check your ANI score before and after. Track your AI citation rate monthly using the manual Perplexity and ChatGPT audit process described in the ANI audit guide — citation rate improvement is the ultimate measure of whether your ANI implementation is working.

Why this matters for your overall optimization strategy

Every ANI improvement compounds with your AEO and GEO work. When AI crawlers can access your site cleanly, read your HTML correctly, and confidently attribute your content to a named, credentialed author, every piece of content you publish starts from a stronger position. The citation rates you earn from well-optimized AEO pages are higher, the topical authority you build through GEO content architecture is more quickly recognized, and the overall efficiency of your optimization investment improves significantly.

The quarterly ANI maintenance habit

ANI is not a set-and-forget discipline. Security plugin updates can add new bot blocking rules. New AI crawlers emerge that need to be added to your robots.txt allow list. Content editing habits can introduce new HTML artifacts over time. A 30-minute quarterly ANI check — reviewing your robots.txt, checking server logs for crawler visits, running the Rich Results Test on a few key pages, and verifying your author box is displaying correctly — keeps your technical AI accessibility foundation solid as your site grows. The quarterly check is a small time investment that protects the much larger time investment you have made in content creation and optimization.

For the complete ANI audit process covering all three technical layers — crawler access, HTML structure, and attribution — see the full ANI audit guide and the ANI checklist. Together they give you the complete framework for verifying every ANI signal is correctly implemented and maintaining it over time.