Hire an AI answer visibility architect

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A scorecard for discovery, readability and actions, with pass, partial or fail on each check.
• A robots.txt block for AI crawlers that follows your allow or block choices.
• An llms.txt file that lists your key pages with one line each.
• A page-length worksheet that flags pages too long to read in one go, with a way to split them.
• A fix plan in five phases over about 30 days.
• A recheck list for after you publish.

How it does the job well

• Audit foundations before any citation or content advice. Do not suggest content changes until discovery and readability are checked.
• Do not block AI crawlers by default. An unchanged old robots.txt that blocks them by accident is the first thing to flag. Blocking on purpose is the user's call, so present options and implement the choice.
• Be exact about maturity. llms.txt is a community convention, not an official standard. Do not claim any AI tool reads it. Separate what AI tools are known to do from what is only proposed.
• Only use pages the user gave. Do not invent page titles, URLs or token counts.
• Do not say a file is live or fixed. You only draft. The user publishes.
• Audit foundations before optimizations. Never recommend citation fixes, content restructuring, or WebMCP implementation until the discovery and parsability layer is verified. Foundations first.
• Never block AI crawlers by default. The default posture should be allowing AI crawlers unless the business has a specific, documented reason to block. Blocking by ignorance (unchanged legacy robots.txt) is the most common AEO failure.

Mistakes it avoids

• Generic copy that could fit any brand.
• Comparing periods or campaigns that are not comparable, such as different dates, budgets or tracking.
• Calling a test winner before there is enough data.

What a good result looks like

An example, not your task: You never touched your robots.txt and wonder if ChatGPT or Perplexity can read your site.

• Foundations scorecard. Pass, partial or fail on discovery, readability and action checks, with the detail behind each.
• robots.txt for AI crawlers. A ready draft with a rule for each AI crawler, following your allow or block choices.
• llms.txt. A site name, a one-line description and your key pages with a line on each.
• Page-length worksheet. Each page type with a size target, an estimate for now and what to split or trim.
• Fix plan. Five phases in order, from robots.txt on day one to action files by about day 30.
• Recheck list. How to confirm AI crawlers get a good response and how often to review the files.

How the work is checked

• Every claim traces to the brand brain or supplied evidence.
• Each recommendation states the expected effect, the cost and how it will be measured.
• Copy fits the platform's length limits and the brand voice.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Neil Patel would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Check discovery. It reads your robots.txt for AI crawler rules, looks for llms.txt, and checks your sitemap and any crawl logs you share.
• Check readability. It tests if key pages work without JavaScript, estimates page length, and checks heading order and FAQ markup.
• Check actions. It looks for any file or markup that tells AI agents what they can do on the site. These are new ideas and marked as such.
• Write the fixes. It drafts the robots.txt block and the llms.txt file, and a plan to split pages that are too long.
• Plan and recheck. It orders the fixes by phase and lists how to confirm AI tools can now reach and read the site.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id marketing-aeo-foundations only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/marketing-aeo-foundations/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your site address.
• The text of your robots.txt. Open yoursite.com/robots.txt and copy it.
• The addresses or text of your 5 to 10 most important pages.
• Your choice on AI crawlers, such as allow all, allow search only or block training (optional).
• Server log lines that show AI crawler visits (optional).

Helpful context (optional)

• Your sitemap address.
• A week of server logs, to see which AI crawlers visit and what they are refused.
• Your site platform, such as Shopify or WordPress, so file steps fit.

Tools and access

• Claude, ChatGPT or Gemini with web browsing: An AI that can open your robots.txt and pages checks them itself instead of from pasted text.

Functions and deliverables

• AI answer visibility architect: Check if AI crawlers can find and read your site. Get a scorecard, a robots.txt for AI bots and an llms.txt file. Paste your robots.txt.
  • A scorecard for discovery, readability and actions, with pass, partial or fail on each check.
  • A robots.txt block for AI crawlers that follows your allow or block choices.
  • An llms.txt file that lists your key pages with one line each.
  • A page-length worksheet that flags pages too long to read in one go, with a way to split them.
  • A fix plan in five phases over about 30 days.
  • A recheck list for after you publish.
  Source: Michael Sitarzewski and Agency Agents contributors.
• llms.txt writer: Share your site. Get an llms.txt file that tells AI tools which pages and facts matter most.
  • A finished llms.txt file
  • Page notes of the right length
  • Key facts stated clearly
  • Placement steps for your site
  • A check of an existing file
  Source: sickn33.
• Site search basics checker: Paste your site address and page list. Get a short fix list for duplicate titles, a missing sitemap and dead-end 404 pages.
  • Duplicate titles and descriptions grouped by pattern
  • Whether a sitemap exists, is submitted and how many pages are indexed
  • Each 404 with a suggested destination
  • A score out of 100 and a fix list ranked by pages affected
• Search and AI answer visibility auditor: Share a website. Get search and AI access checks, observed answer results and ready-to-use fix files. Connected site edits need review.
  • A crawl report of what was and was not reachable
  • Results from real assistant questions
  • The top five fixes in order
  • A corrected robots.txt and an llms.txt
  Source: Anthropic.
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one
• Neil Patel: Plan search content using Neil Patel’s recorded approach. Start with customer questions, review useful gaps and set a realistic publishing and measurement plan.
  • Your problem worked on the way Neil Patel would: their questions, their method, their push-back
  • The answer or the work, in Neil Patel's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• You never touched your robots.txt and wonder if ChatGPT or Perplexity can read your site.
• You want an llms.txt file and do not know what goes in it.
• Your site is built with JavaScript and the pages look empty without it.
• You plan to chase AI mentions and want the groundwork checked first.

Limits to check before starting

• You only want the llms.txt file. Use the llms.txt writer.
• You want to know if AI tools mention you now and why rivals win. Use the AI citation visibility planner.
• You want a full technical SEO crawl with every broken link. Use the Technical SEO auditor.
• You want to know if an AI browsing agent can book or buy on your site. Use the AI search visibility reviewer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Add the pack to your AI as a skill. In a plain chat, paste SKILL.md first.
• Open yoursite.com/robots.txt and copy the text. Add your site address and your 5 to 10 key pages. An AI that can browse the web may fetch them itself. If not, paste them.
• Say what you want for AI training crawlers and AI search crawlers, or ask it to show the options.
• Say "Run the AEO foundations check."
• Read the scorecard, then review the robots.txt and llms.txt drafts. Nothing is published for you.
• Publish the files yourself, or hand them to your developer. A few weeks later, ask AI tools about your business, check your crawl logs and run the scorecard again.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/marketing-aeo-foundations for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.