RITNER DIGITAL / Crawling / accessibility / discovery
LET THERIGHT BOTSin.
If your pages are inaccessible, their quality never gets a fair chance. We review search crawler permissions, server responses, rendering, and the technical barriers that stand between your site and AI-assisted discovery.
ACCESS IS NOT A CITATION
See the work.
Different bots serve different purposes. We distinguish search discovery, user-triggered fetching, and model training, then make recommendations that respect your content and privacy preferences.
NOT A LIVE AUDIT ✳
01 / THE PROBLEM WORTH SOLVING
THE PAGE IS
PUBLISHED.
Can it be read?
A visible browser page can still be blocked by robots rules, bot protection, or JavaScript-dependent content. Technical accessibility is a prerequisite for discovery, not proof of citation.
02 / WHAT THE WORK INCLUDES
THE DETAILS
matter.
Six concrete layers of llm crawlability work. Each solves a real problem, with clear scope rather than a vague promise to “rank in AI.”
Crawler-purpose audit
Review relevant bots and document which access decisions match your goals.
Robots.txt & directives
Inspect disallow rules, meta robots, canonicalization, and intended indexing behavior.
Response & security checks
Investigate 403s, rate limits, CDN policies, anti-bot challenges, and redirects.
HTML content accessibility
Check what useful information exists in the initial page response and what requires scripts.
Sitemaps & internal links
Keep important URLs discoverable through a sensible site structure.
Retesting & monitoring
Document each change, confirm the response, and monitor access-related regressions.
03 / INTERACTIVE SERVICE WORKBENCH
SEE IT
in action.
Explore six different parts of the process. Select any tab or use the arrows to see a worked illustration and exactly what gets reviewed.
WORKBENCH / 01
Identify the correct crawler
Search discovery, user-requested fetching, and training are separate concerns. Access decisions should be deliberate.
- Review the crawler’s published purpose
- Define your search visibility preference
- Keep training decisions separate
Not all bots do the same job
Search discovery, user-requested fetching, and training are separate concerns. Access decisions should be deliberate.
WORKBENCH / 02
Read robots.txt
Review wildcard rules, user-agent groups and target paths. A blanket block can unintentionally limit public discovery.
- Check exact user-agent groups
- Examine path-level directives
- Keep a record before changing policy
Look for accidental exclusions
Review wildcard rules, user-agent groups and target paths. A blanket block can unintentionally limit public discovery.
User-agent: OAI-SearchBot Allow: / User-agent: GPTBot Disallow: / # example owner preference
WORKBENCH / 03
Check server responses
Access can be blocked after robots.txt by firewalls, bot defenses, CAPTCHAs, or redirects.
- Investigate legitimate test requests
- Check 200, 301, 403, and 404 behavior
- Coordinate any security-policy change
A 403 stops the visit
Access can be blocked after robots.txt by firewalls, bot defenses, CAPTCHAs, or redirects.
WORKBENCH / 04
Inspect rendered content
JavaScript-only interfaces may make essential content harder for some automated clients to access. Keep critical service information in meaningful page text.
- Check server-delivered content
- Test essential page text without scripts
- Use semantic headings and links
Is the answer in the HTML?
JavaScript-only interfaces may make essential content harder for some automated clients to access. Keep critical service information in meaningful page text.
WORKBENCH / 05
Review discovery paths
Pages also need intentional internal linking, valid destinations, and appropriate sitemaps.
- Audit internal links from hub pages
- Remove avoidable redirect chains
- Check canonical and sitemap alignment
Make important URLs reachable
Pages also need intentional internal linking, valid destinations, and appropriate sitemaps.
WORKBENCH / 06
Re-test and record
Test the relevant pathway and document what changed, without treating an allow rule as a promise of inclusion.
- Capture before/after responses
- Log outstanding blockers
- Recheck after deployment
A fix is only a fix when verified
Test the relevant pathway and document what changed, without treating an allow rule as a promise of inclusion.
All interfaces, descriptions and observations above are illustrative, not actual AI platform analytics or guaranteed results.
04 / THE APPROACH
LESS HYPE.
More method.
Understand.
Document the site, current content, public evidence and the questions that matter.
Diagnose.
Separate genuine blockers and gaps from cosmetic optimizations or assumptions.
Build.
Implement accurate, useful changes with the right person accountable for each.
Learn.
Recheck real-world observations and refine the plan as systems and questions change.
05 / FURTHER READING
FROM THE
Ritner blog.
Relevant writing from Ritner Digital, paired with official documentation where platform-specific claims require care.
06 / COMMON QUESTIONS
GOOD
questions.
An accurate answer beats a sweeping promise. Here is what this service does, and what no agency can control.
Which OpenAI bot affects ChatGPT Search?
Do I need to allow training bots for search visibility?
Can robots.txt guarantee AI citations?
What if my robots.txt already allows bots?
Do I need an llms.txt file?
Can Squarespace pages be accessible to AI crawlers?
What do you deliver?
07 / THE GEO SYSTEM
CONNECTED
DISCIPLINES.
08 / LET'S MAKE IT CLEAR
BETTER SIGNALS.
Better decisions.
Tell me what your business does and which customer questions matter most. We'll start with what can be reviewed, improved, and measured.
RITNER DIGITAL / STRATEGY, CLARITY, & THE WORK BEHIND VISIBILITY.