Back to Making Your Website Accessible to AI: Platform Guides
AI Discoverability Foundations·Beginner·Supporting guide

WordPress.com: AI Crawler Access

Check the relevant WordPress.com settings and give your website provider a specific issue to review.

4 minBeginner
What you'll learn
01

Find the public access settings relevant to WordPress.com

02

Identify a specific issue to discuss with your website provider

03

Retest the published website after a change

What you can check yourself

  1. Confirm the production site is set to Public.
  2. Under Settings → Reading, ensure Discourage search engines from indexing this site is not enabled.
  3. Open the important pages while logged out and confirm they display normally without a login or password.
  4. Inspect the live /robots.txt rather than assuming the visibility setting is the only control.
  5. Open https://yourdomain.example/sitemap.xml and confirm the important pages and posts appear.
  6. Check any available page-level SEO controls for an unintended noindex instruction.
  7. Publish changes and rerun the assessment.

What healthy looks like

  • The site is public and search discouragement is off.
  • Important pages return normal public content.
  • The live crawler rules do not block desired search and retrieval access.
  • The WordPress.com sitemap contains the intended pages.

Making a change

Use the assessment's specific finding to decide what needs changing. After the update, check the published page and robots.txt to confirm the settings have taken effect.

Message for WordPress.com support

Our crawler-access assessment found [EXACT ISSUE] on [PAGE URL] for [CRAWLER NAME]. The site is intended to remain public and available for current search and AI-assisted retrieval. Please confirm whether the WordPress.com privacy, search-visibility, robots, page-indexing or domain configuration is producing this result, and tell us the supported change.

Official WordPress.com references

Return to all platform guides.