Skip to content
AEOprobe
Platform guide

AEO for WordPress

Start with your WordPress indexing settings and the markup your theme and plugins already publish. Set up that markup before you add another schema plugin.

Updated

Default robots.txt behavior

WordPress core can serve a virtual robots.txt. It disallows /wp-admin/ and allows /wp-admin/admin-ajax.php. Core sitemaps add a sitemap reference to that file. A physical robots.txt file or a plugin can change what the site serves. On current WordPress versions, the “Discourage search engines” setting works through page robots metadata. Checking robots.txt alone is not enough.

Decide whether to permit search and user-fetch crawlers separately from training crawlers, within the controls your platform provides. See how AEOprobe distinguishes crawler roles.

Default structured data

Schema differs between WordPress sites, so check what your theme and plugins output. Yoast SEO defaults to WebPage on pages. On posts it defaults to Article plus WebPage. Its FAQ block is in the free plugin, so you do not need to upgrade for that markup.

Common AEO issues

Common AEO issues, their impact and fixes
IssueImpactFix
A public site still discourages indexingImpactPages can carry noindex even when robots.txt permits crawling.FixCheck Settings → Reading → Search Engine Visibility. Then check the published page’s robots metadata.
Schema describes the wrong content or publisherImpactThe structured data conflicts with the visible page or business details.FixIn Yoast SEO, review Content types → Schema and review Site representation. Then inspect a representative published page.
Plugins and the theme publish conflicting markupImpactDifferent scripts can give inconsistent facts about the same page or entity.FixFind out which plugin or theme produces each JSON-LD script. Make their facts match. Do this before you install another schema plugin.

Plugins and modules

Step-by-step guide

  1. 1

    Check the site’s indexing preference

    Open Settings → Reading → Search Engine Visibility. If the site is public and you want it indexed, clear “Discourage search engines from indexing this site.” Save the change. Then check the published page’s robots meta tag.

  2. 2

    Inspect the served crawler rules

    Open /robots.txt on the public site. If you use Yoast, you can edit the file in Tools → File editor. This needs file editing to be enabled and the file to be writable. Keep the existing system-path rules. Change only the crawler policy you intend to change.

  3. 3

    Configure the markup you already use

    In Yoast, open Settings → Site representation and check your organization or person details. Then open Settings → Content types → Posts or Pages → Schema. Use the editor’s Schema tab for exceptions. Add a FAQ block only where the questions and answers are visible on the page.

  4. 4

    Check a published post and page

    Publish your changes and inspect the JSON-LD on a post and a page. Check that URLs, titles and publisher details match the visible content. Check again after each theme or plugin update.

Official documentation

Questions

Do I need a paid schema plugin?

Not necessarily. First check what your current theme and SEO plugin output. Yoast’s free FAQ block already supplies FAQ markup. Add another tool only for a specific need your setup does not cover.

Why is the robots.txt editor unavailable?

Yoast’s file editor needs WordPress file editing to be enabled. It also needs suitable file permissions. If your host or deployment manages the file, make the change through that workflow instead.

The free audit checks up to 3 public pages with no sign-up. Structured data checks read JSON-LD only. Microdata and RDFa are not parsed. Findings do not guarantee rankings or AI citations.

A saved-site audit costs 20 credits. It covers up to 10 pages on Free, 50 on Watch and 100 on Pro. AEOprobe plans are Free at €0/month, Watch at €7/month and Pro at €21/month. Your account shows what you can buy.

Run the free audit on your site