Your 2026 Blog Audit: A Working Checklist

It's easy to keep publishing on autopilot — same platform, same habits, same mental model of how blogging works — without ever checking whether any of it still matches how people and AI systems actually find and read blogs now. This audit pulls together every concrete check from across this series into one working document. Go through each section with your own site and analytics open. You don't need to fix everything in one sitting — you need to know exactly where you stand, which is the part most bloggers are currently skipping.

Section 1: Can AI systems even reach your content?

This is the most commonly skipped check in any 2026 blog audit, and it's a binary, fixable problem: if AI crawlers can't access your pages at all, nothing else in this checklist matters, because you're invisible to AI search by default rather than by choice. A surprising number of sites are still running a robots.txt file from 2023, written during an early panic about AI scraping, that blocks every AI crawler wholesale — including the ones that would otherwise cite them in ChatGPT or Claude search results (Hyperleap's 2026 guide to checking AI crawler access).

• ☐ Visit yoursite.com/robots.txt directly and check whether it disallows GPTBot, ClaudeBot, PerplexityBot, or Google-Extended.
• ☐ Understand the distinction between crawler types before you decide anything: GPTBot and ClaudeBot gather training data; OAI-SearchBot and Claude-SearchBot power live search citations; ChatGPT-User and Claude-User make one-off fetches when a person pastes your URL into a chat. Blocking a training crawler while allowing the matching search crawler is a coherent choice — blocking both by accident, using one broad "block all AI bots" snippet, is the most common costly mistake (Hartzer's 2026 technical reference on AI crawler directives).
• ☐ If you want to appear in AI citations, explicitly allow the search-facing crawlers. A representative robots.txt block for a blog that wants citation visibility:

User-agent: OAI-SearchBot
Allow: /
User-agent: ChatGPT-User
Allow: /
User-agent: Claude-SearchBot
Allow: /
User-agent: Claude-User
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Perplexity-User
Allow: /
User-agent: GoogleOther
Allow: /

• ☐ Check your hosting provider or CDN separately from robots.txt itself. Managed hosts and CDNs sometimes block AI crawlers at the platform layer before your robots.txt is ever read, returning a 403 or 429 error regardless of what your file says (The Plus Addons' 2026 WordPress AI crawler guide).
• ☐ Grep your server access logs for GPTBot, ClaudeBot, and PerplexityBot user-agent strings over the last 30 days. Zero hits is a strong signal you're being blocked, throttled, or under-linked somewhere upstream of your content itself.
• ☐ Don't over-invest in llms.txt. It's been marketed heavily as "the new robots.txt for AI," but an audit of 300,000 domains found only about 10% adoption, and among the 50 most-cited domains by AI systems, exactly one had an llms.txt file in place — with no measurable correlation between having one and being cited. Google's own search team has stated publicly it doesn't use the file at all. Robots.txt access and genuinely citable content structure matter far more than this file does right now (Godberry Studios' 2026 analysis of llms.txt adoption and impact).

Section 2: Traffic and metrics

• ☐ Have you set up GA4's native AI Assistant channel and a supplementary custom channel group to catch the platforms it misses (Perplexity, referrerless AI app traffic)?
• ☐ Do you know your conversion rate broken out by traffic source — organic search, AI referral, email, social, direct — rather than one blended number?
• ☐ Do you track email list growth and engagement (open rate, click rate, unsubscribe rate) as a core, recurring metric?
• ☐ Can you say, for your top five posts, roughly how much revenue or leads each has generated relative to the time it took to produce?
• ☐ Do you track return-visitor rate, separate from total pageviews?

Section 3: AI citation visibility

• ☐ Have you asked ChatGPT, Perplexity, and Google's AI Overview the exact questions your top posts answer, to check whether you're cited — and checked more than once, given how quickly citation rotation happens?
• ☐ Do your posts contain standalone paragraphs that make sense pulled out of context — passages a system could quote cleanly and attribute correctly?
• ☐ Do your headings state the actual question being answered, rather than a vague or clever label?
• ☐ Where it genuinely fits, do you use FAQ, HowTo, or Article schema markup?
• ☐ Is your most important content narrow and specific enough that an AI system has to rely on your page specifically, rather than falling back on generic pre-existing knowledge about a broad, heavily-covered topic?
• ☐ Have you checked whether your cited content is being represented accurately, not just whether you're cited at all?

Section 4: Content structure and originality

• ☐ Does your best-performing post from a year ago still hold up, or has it quietly gone stale — and is it due for a refresh given how quickly AI citation rotates?
• ☐ Are you leaning on named, credentialed authorship rather than anonymous or generic posting?
• ☐ Do you have at least one original data source of your own (a small survey, a documented test, your own numbers) rather than only synthesizing what other sites already say?
• ☐ When you reread your last three posts, do they sound distinctly like you, or could they have been written by almost anyone covering the same topic?
• ☐ If a large share of your traffic historically came from broad, definitional, or generic how-to content, have you identified a narrower, more specific angle within your niche to shift toward?

Section 5: Owned audience

• ☐ Do you have a structured 4–5 email welcome sequence delivered over 7–10 days, rather than a single generic welcome email?
• ☐ Have you explicitly confirmed SPF, DKIM, and DMARC are configured correctly for your sending domain?
• ☐ Is there a specific, compelling reason to subscribe — a lead magnet, a clear promise — rather than a generic "subscribe" box?
• ☐ Is there anywhere for readers to talk back — comments you actually respond to, a low-cost community space, or a reply-friendly newsletter — or is it entirely one-directional?
• ☐ Have you budgeted for ongoing list decay (roughly 20–30% a year) by treating subscriber growth as continuous, not a one-time project?

Section 6: AI use and disclosure

• ☐ Do you have a clear, deliberate policy on AI disclosure — stated once, somewhere visible — rather than an unconscious default?
• ☐ Are you being more careful about disclosure specifically on posts that claim firsthand experience or testing?
• ☐ Could you defend every specific factual claim in your last three posts if a reader challenged it directly?
• ☐ If you use AI in your drafting process, is a human actually reviewing and substantially reshaping the output, rather than publishing it close to as-generated?

Section 7: Platform and monetization

• ☐ Is your current platform still serving you well, or are you paying — in time, flexibility, or cost — for features you don't use?
• ☐ Does your monetization mix depend entirely on display ad revenue, or do you have at least one other lever (affiliate, digital products, sponsorships, services) in motion?
• ☐ Do you have a content calendar reflecting your current priorities, including dedicated refresh slots for older posts?

Scoring your audit

Count your unchecked items in each section. This isn't a precise science, but it's a useful triage tool:

• 0–2 unchecked in a section: Solid — revisit this section again in your next quarterly audit.
• 3–5 unchecked: A real gap worth addressing this month, not urgently, but deliberately.
• 6 or more unchecked: A section actively working against you. Prioritize this one first, before spreading effort thinly across every section at once.

For most bloggers coming to this fresh, Section 1 (AI crawler access) and Section 3 (citation visibility) turn up the most unchecked items and the most immediately actionable fixes — both are quick to check and often reveal something genuinely unknown about your own site.

Frequently asked questions

How often should I redo this full audit?
Quarterly is a reasonable cadence for the full checklist, given how quickly AI citation patterns and platform features have been changing. Sections 1 and 3 (crawler access and citation visibility) are worth spot-checking monthly, since citation rotation happens faster than most other metrics on this list.

I'm blocking all AI crawlers on purpose because I don't want my content used for training. Is that wrong?
Not necessarily — it's a legitimate, deliberate choice. The mistake isn't blocking training crawlers like GPTBot or Google-Extended; it's blocking search-facing crawlers like OAI-SearchBot or Claude-SearchBot at the same time without realizing it, which removes you from AI citation entirely rather than just opting out of training data use. Decide on each separately.

Should I bother creating an llms.txt file?
Given the current evidence — low adoption, no measured correlation with citation among the most-cited domains, and no support from Google's own systems — it's a low-priority item. Time spent making your existing content more structurally citable will do more for your AI visibility than adding this file.

The point of this audit isn't to feel behind. It's to replace a vague sense that "something's different now" with a specific, prioritized list of things you can actually act on — and then to come back to this same checklist next quarter, because the landscape underneath blogging is still moving.