# How to let ChatGPT find your WordPress website
> Check WordPress visibility, crawler rules, caching and public page content, with separate steps for hosted and self-hosted sites and a repeatable test.
- Page to cite: https://aeolookup.com/ai-for-small-firms/let-chatgpt-crawl-wordpress/
- Publisher: AEO Lookup (https://aeolookup.com/)
- Section: AI for small firms, Putting it to work
- Published 30 October 2026
- Key fact: A public page, a permissive crawler rule and a citation are three different observations. Record each separately.
- Sources: WordPress.org Reading settings; WordPress.com SEO issues; OpenAI crawler documentation, linked in the article; checked 30 October 2026. Worked examples are illustrative unless a source is named.
To make a WordPress page available to ChatGPT search, publish it publicly and check that your site does not block the relevant search crawler. WordPress settings, SEO plugins, hosting rules and security services can each affect the result.
Start with one useful page, such as your main service description, rather than changing every setting at once. A UK firm's location, service area and contact route should be readable without a login.
## Which WordPress version am I using?
WordPress.com is a hosted service; self-hosted WordPress runs on hosting selected by the site owner. Their dashboards and available controls differ. A managed host may also add its own cache or security panel.
Identify who controls the domain, hosting and SEO settings before making a change. If an agency manages the site, send it the affected URL and the exact result from the AI crawler checker. A reproducible observation is more useful than asking it to enable all AI.
Keep a note of the original settings and who approved the change. This makes it possible to reverse an unintended effect without rebuilding the site.
## Which visibility settings should I check first?
For self-hosted WordPress, the [Reading settings documentation](https://wordpress.org/documentation/article/settings-reading-screen/) identifies the search-engine visibility control:
1. Open Settings, then Reading.
2. For a production site intended for discovery, clear the option discouraging search engines.
3. Save the change, then test a published page while signed out.
On [WordPress.com](https://wordpress.com/support/seo/seo-issues/), check the site's Public setting as well as the search-engine discouragement option. A draft, private or password-protected page is a separate issue from a crawler rule.
Do not expose a staging site or client area merely to clear a warning. Choose a public production page as the test target. A search setting is not an access-control system for confidential material.
## Should I change robots.txt or install a plugin?
Inspect the file served at your primary HTTPS domain followed by /robots.txt. Record whether the checker found an explicit restriction, a fetch failure or no matching rule. Those outcomes need different remedies.
OpenAI's [crawler documentation](https://developers.openai.com/api/docs/bots) distinguishes OAI-SearchBot for search from GPTBot for training. Decide those permissions separately. A generic AI toggle may group several bots together, so check the rules it actually publishes.
| Layer | What to inspect | Who may control it |
|---|---|---|
| WordPress visibility | Public page and site settings | Site editor or administrator |
| SEO plugin | Output rules and page indexing directives | WordPress administrator |
| Host or security service | Denied requests, challenges or rate limits | Hosting administrator |
| Cache | Whether the public response reflects the change | Host or performance plugin |
Avoid installing another plugin before identifying a missing capability. Two tools trying to generate the same rules can make the effective result harder to understand. If a managed host owns the file, use its documented editing method.
## Why does it work for me but fail for a crawler?
Your logged-in browser may bypass a restriction or serve a different cached response. Test signed out and compare the final URL, status and visible content. A page that redirects to a login has not become public because an administrator can read it.
After an authorised change, clear the relevant cache through the host's normal controls and rerun the same URL. If a security service rejects a verified crawler, ask the host to investigate its logs. Keep protection for private areas in place.
[Our general crawl guide](https://aeolookup.com/ai-for-small-firms/can-chatgpt-see-my-website/) explains how access differs from being selected as a source. A successful test establishes access at the time of the check.
## What should I improve once access works?
Make the public page answer the customer's question directly. For a UK repair firm, useful facts include the repairs offered, actual service area, booking route and any conditions on a quoted call-out price. Use real business details rather than invented examples presented as customers.
Check the answer-readiness report against the text a signed-out reader sees. Then keep a small list of relevant questions and [record actual citations](https://aeolookup.com/ai-for-small-firms/measure-ai-search-visibility/) separately. A readable page is a foundation for discovery, not a promise that an assistant will recommend the firm.
## Which questions come up most often?
### Does clearing the WordPress setting guarantee a citation?
It removes one possible access barrier. Search systems still decide whether to index and use the page.
### Should I make a private client area public?
Keep private information behind proper access controls. Test a page deliberately published for customers.
### Must I buy a WordPress AEO plugin?
Identify the specific missing function first. Visibility and crawler checks do not by themselves establish a need for another paid plugin.
---
General information for UK small firms, not legal, tax or financial advice.