Skip to content

New in the free AI Suite SEO plugin

Can ChatGPT and Claude find your WordPress website?

Check AI search access, plan customer answers, publish FAQs, and record manual citation tests inside WordPress. Free GEO tools with no account connection or AI credits needed.

Included in AI Suite SEO 0.1.12. Requires the free AI Suite Core plugin, WordPress 6.5+ and PHP 7.4+.

Start with access, useful answers, and evidence

To help AI search services find and cite a WordPress website, make important public pages accessible and answer the questions customers actually ask. Explain what you offer, who it fits, what it costs, and the evidence behind your claims. Connect the answers with relevant internal links.

FounderPostAI’s free AI Visibility check helps with the access and page-signal checks. Content quality and an assistant’s source selection still require separate evaluation. Start with one important service page or existing post, then work through its related pages.

Search crawler access

See the robots.txt rules that apply to ChatGPT search, Claude search and Claude user requests for your selected page. Search access and model-training preferences are shown separately.

Indexing and snippet restrictions

Find WordPress search-visibility settings and page directives such as noindex that deserve attention before you expect a public page to be discovered.

Public page and canonical URL

Check the page response and whether a canonical link is missing, duplicated or pointing elsewhere. Each finding explains what to review in your existing SEO plugin or hosting settings.

Headings and structured data

See whether headings and JSON-LD markup appear in the returned HTML. Presence is reported separately from quality or validity, with guidance on clear answers and accurate author or business details.

Do you need a plugin or a manual check?

You can inspect a small site manually using WordPress settings, your SEO plugin, robots.txt, and the public page’s HTML and response headers. FounderPostAI brings selected checks together inside WordPress and explains the findings. Neither method measures whether an assistant actually cites you.

  • Keep your existing SEO plugin to manage its titles, canonicals, schema, and sitemaps.
  • Use AI Visibility for a repeatable, read-only check of one public page without connecting an account.
  • Test real assistant answers separately when you want evidence of a mention, citation, or recommendation.

Compare WordPress SEO tools by the job you need done →

Get your first report in WordPress

  1. Install and activate AI Suite Core from WordPress.org, then install and activate the free AI Suite SEO plugin from the same directory.
  2. Open AI Suite → AI Visibility. Check your homepage or paste the public permalink of a published post or page.
  3. Select Run visibility check. Review the evidence, follow the relevant guidance, and run it again after making changes.

Already using the older direct ZIP edition? Remove that SEO copy before installing the directory edition. The installation guide has the current steps.

Useful findings, with clear limits

Each run checks one public page and its robots.txt rules. The report also lists same-site sitemaps advertised in robots.txt, so you can open them and check your important pages.

This is a setup check. It cannot confirm that an AI service has indexed, cited or recommended your site. It does not verify actual crawler IP access, run JavaScript, validate schema or inspect sitemap contents.

Your settings stay in your hands

The check gives you evidence and next steps. It does not edit robots.txt, privacy settings, content or schema. Training preferences are informational and never count as visibility problems.

Your server reads your own public page and robots.txt. Only the latest report is cached locally for 24 hours; page bodies are not saved or sent to an AI service.

What to do with a visibility finding

Review the evidence before changing a setting. A restriction may be intentional for a private page, and a missing signal is not automatically an error. Recheck the same public URL after making a relevant change.

  • Search access restricted: review the named crawler rule with your host. Decide search access separately from training preferences; do not remove protections from private content.
  • Noindex or snippet restriction: check WordPress Settings → Reading and the page’s settings in your SEO plugin. Keep intentional exclusions in place.
  • Canonical points elsewhere: confirm which URL should represent the page. An alternate canonical can be correct for duplicated content.
  • No headings or JSON-LD found: inspect the returned page and your theme. Write clear headings and add only accurate structured data. This check does not validate markup.
  • Unknown or incomplete result: ask your host about the response, redirects, and firewall logs. A successful fetch from your own server does not prove access from actual AI crawler IPs.

Turn customer questions into better pages

AI Suite SEO 0.1.12 adds a free GEO Planner. Open AI Suite → GEO Planner, choose your topic, audience, and desired next step, then customize four questions covering discovery, comparison, fit, and the buying decision.

  1. Map questions to existing pages. Assess each answer and write a brief with facts, examples, and sources. The planner puts missing decision and qualification answers first.
  2. Write visible answers. Add the FounderPostAI GEO FAQ block in the WordPress editor. Mix questions about the page with useful follow-ups, then publish through the usual save action. Follow the FAQ block tutorial to inspect the matching markup and avoid duplicate schema.
  3. Keep evidence of actual assistant tests. Record exact prompts, engine, model, mode, date, mentions, and cited URLs in the manual AI answer log. Export the plan and observations as Markdown.

These tools need no account or credits. One editable plan and up to 100 observations stay in your WordPress database until removed or the plugin is uninstalled. They do not generate answers or run assistant tests automatically. Saved FAQ text remains readable after deactivation.

Make your important pages easier to discover

Make each important page useful across a customer’s follow-up questions. Open with the answer, then explain the alternatives, compatibility, price, and limitations. Include an original example or demonstration and identify who is responsible for the content. Update facts when they change.

For example, a WordPress plugin page should answer “What does it do?”, “Does it work with Yoast?”, “What is actually free?”, and “Can I undo a change?” in visible text. See how our AI Suite product reference answers those questions. Find pages with no incoming content links, then use descriptive internal links to connect supporting guides.

The same free plugin can also suggest titles, descriptions and internal links for you to review. Those AI-generated suggestions use managed credits or your own Anthropic key; the visibility check remains free to run.

How to tell whether your site appears in AI answers

Check the answers themselves. A crawler report, sitemap submission, or ordinary search impression cannot establish that ChatGPT or Claude recommended your business.

  1. Choose a small, fixed set of real customer questions. Start without your brand name, then ask natural comparison, compatibility, and buying questions in the same conversation.
  2. Run the conversations in the assistants your customers use. Record the date, engine, search mode, exact prompts, brand mentions, and cited page URLs. Keep brand-supplied prompts separate.
  3. Repeat monthly. Compare the share of your tested questions with a mention or citation, by conversation turn. Treat missing access as untested, not a zero.
  4. Track referral visits and useful enquiries separately. Referrers can be missing, answers vary, and changes in traffic can also reflect other marketing work.

The GEO Planner’s manual AI answer log keeps these observations together. Its summaries use the current prompt set, separate engines, models, modes, and conversation turns, and exclude unavailable tests and brand-supplied prompts. Historical records remain available for review and export.

Built around published crawler guidance

OpenAI and Anthropic document separate crawlers for search discovery and model training. Read their guidance when deciding which access you want to allow: OpenAI crawlers and Anthropic crawlers.

Google’s AI features guidance says standard SEO practices apply to AI Overviews and AI Mode, with no special AI text file or schema required. Structured data should match visible content. Guidance checked September 13, 2026.

Questions before your first check

What does GEO mean for a WordPress website?

Generative engine optimization (GEO) means improving information that AI search services can discover, understand, and use in answers. Start with accessible pages, customer questions, accurate business details, and evidence. FounderPostAI adds free setup checks, a four-turn conversation planner, an editable FAQ block, and a manual citation log to WordPress. These tools support your work; an assistant still chooses its own sources.

How can I check WordPress AI visibility for free?

Install FounderPostAI AI Suite Core and the free AI Suite SEO plugin from WordPress.org, then open AI Suite → AI Visibility. Run a check on your homepage or a public published post or page. The report needs no account connection, API key, or AI credits. WordPress 6.5 or later and PHP 7.4 or later are required.

Can I allow AI search while blocking model-training crawlers?

Yes. OpenAI documents OAI-SearchBot for search separately from GPTBot for training. Anthropic distinguishes Claude-SearchBot and Claude-User from its training crawler, ClaudeBot. Review each purpose independently in your crawler policy. FounderPostAI reports those distinctions without treating a training restriction as a visibility problem. Your host or firewall can still block requests even when robots.txt allows them.

Will the visibility check replace Yoast or change my settings?

No. FounderPostAI’s AI Visibility check reads public page signals and gives guidance; it does not edit robots.txt, content, schema, or privacy settings. Keep your existing SEO plugin responsible for its settings. The separate metadata suggestion workflow supports Yoast SEO, Rank Math, AIOSEO, and SEOPress by saving approved values into native fields and avoiding duplicate frontend tags.

Do I need llms.txt or special schema for Google’s AI results?

No. Google says its AI Overviews and AI Mode require no special AI text file or schema. Focus on crawlable pages, useful text, and structured data that accurately represents visible content. A JSON-LD presence check cannot establish validity or eligibility. Treat an llms.txt file as an optional reference, not evidence that Google, ChatGPT, or Claude has indexed or cited you.

Does a clear report mean ChatGPT or Claude recommends my website?

No. A clear FounderPostAI report means selected setup checks found no obstacle on the fetched page. It does not establish indexing, mentions, citations, or recommendations. Run consistent customer questions in each assistant yourself and record the results in the GEO Planner’s manual AI answer log. Compare eligible observations over time, and track referral visits and useful enquiries separately. Answers can vary between runs.

Published · Updated