There are two ways to check a site’s schema and AEO setup. An outside checker is a website or service that requests your pages over the internet and reports what it finds. A plugin inside WordPress, like AEO Ultimate, reads your site from the inside.
Both are useful, and neither sees everything. The short version: use the plugin as your day-to-day source of truth, and run an outside checker now and then as a second opinion. Here is what each can and can’t see, including where our own plugin falls short.
Why outside checkers get blocked
An outside checker has to get through the same defences as any other visitor. To a firewall, a tool requesting dozens of pages a minute from a cloud server looks just like a scraper.
- Cloudflare and other CDNs. Bot Fight Mode, Super Bot Fight Mode and managed challenges can block or challenge automated traffic. The checker gets a 403 error, a 429 error or a challenge page instead of your content.
- Shopify. Store owners can’t change Shopify’s Cloudflare settings, and Shopify rate-limits fast requests. A full catalog scan can start getting 429 errors partway through.
- WordPress security plugins. Wordfence, Solid Security (formerly iThemes Security) and Sucuri can rate-limit or ban an IP address that requests many pages quickly, which is exactly what a site audit does.
- Hosts. Many managed WordPress hosts filter bots at the server, before WordPress even loads.
A good checker tells you it was blocked. A weaker one just reports “no schema found”, which looks like a problem with your site.
The unblocking hassle
To get a blocked checker working, you have to find out which layer blocked it, then allowlist the tool’s IP addresses or user agent there. That might mean a Cloudflare WAF rule, a Wordfence allowlist entry or a ticket to your host. Some checkers publish their IP ranges to make this easier. Either way, it is setup work, and your firewall is now set to trust one more outside service.
What a plugin inside WordPress can see
AEO Ultimate runs inside WordPress, so it doesn’t knock on the front door at all.
- Nothing to unblock. Its checks don’t pass through Cloudflare, your security plugin or your host’s firewall, so there are no allowlists to set up and no audits cut short by a ban.
- Every page, not a sample. It reads your content straight from WordPress, including drafts, private and password-protected pages, noindexed pages and the thousandth product. There’s no crawl limit.
- The cause, not just the symptom. AEO Ultimate generates your schema itself, so when something is missing it can point to the setting, the page or the conflicting plugin responsible.
- No outside service. The schema and page checks need no outside service to sign up for or hand your URLs to.
- Ongoing, not one-off. Checks such as the daily index check run on a schedule, so problems show up without you remembering to run an audit.
Where AEO Ultimate can miss things
Being inside WordPress has its own blind spots, and it’s better you hear them from us.
- What WordPress makes isn’t always what visitors get. Caching plugins, CDN optimisation, HTML and JavaScript minification and other plugins can change a page after WordPress builds it. If one of them strips or rewrites schema, the plugin’s view of the page and the delivered page differ.
- Some code isn’t ours to see. Schema hard-coded into a theme template, or injected by a tag manager in the browser, may not show up in a check that reads WordPress content directly.
- Our own outside fetch can be blocked too. Bot View fetches your live page so you can see what a crawler gets. That request leaves your server and comes back through the same CDN, firewall and cache as everyone else’s, so it can be blocked or served a stale cached copy. It happens less often than with an outside service, but it happens.
- Full checks are for your own site. Chunk View can look at any URL, including a competitor’s, but the full checks only cover the WordPress site the plugin is installed on.
We’re actively testing AEO Ultimate alongside popular caching and optimisation plugins to find where they change its output, and fixing what we find.
Where outside checkers are better
Outside checkers have real strengths, and they’re worth keeping in your toolkit.
- They see what a stranger gets. If your CDN, cache or minifier changes the page, an outside checker sees the final result.
- They work anywhere. Any URL, any platform, nothing to install. Handy for a competitor, a client prospect or a site you don’t run.
- They test your defences. If a checker is blocked, that tells you how your firewall treats automated visitors, which is useful to know.
- They’re quick for a one-off look. Paste a URL and get an answer in seconds.
Side by side
| AEO Ultimate (inside WordPress) | Outside checker | |
|---|---|---|
| Blocked by Cloudflare, WAFs or security plugins | No, for its content checks | Often, depending on your settings |
| Setup | Install the plugin | Sometimes allowlisting in your firewall |
| Pages covered | Every page, including drafts and private pages | Public pages it can reach, often up to a plan limit |
| Explains why something is missing | Yes | Rarely |
| Sees changes made by caching, CDN or minification | Not in content checks; Bot View can | Yes |
| Sees schema added by JavaScript | Not always | Only if it renders JavaScript |
| Works on any site or platform | No, WordPress only | Yes |
| Runs on a schedule | Yes | Depends on the service |
How to use both
- Day to day, use the plugin. It covers every page, runs on its own schedule and tells you what to fix.
- Now and then, run an outside checker on a few key pages, such as your homepage, a top product and a top article. It catches anything your caching or CDN changes on the way out.
- When the two disagree, look between them. Schema present in the plugin but missing outside usually means a cache, an optimisation plugin, a firewall or a JavaScript problem.
- If the outside checker was blocked, decide whether that’s what you want. You may be happy to keep it out. Just make sure it was blocked on purpose.
One more reason to check: the settings that block an outside checker can also block AI crawlers such as GPTBot and ClaudeBot. AI engines can only cite pages their crawlers can read, so a blocked checker is a good prompt to look at your firewall’s bot settings. AEO Ultimate’s AI Crawler Watch shows which AI crawlers actually reach your site.
Frequently asked questions
Why does an outside checker say my schema is missing when I can see it?
Usually the checker was blocked by a firewall, CDN or security plugin, or your schema is added by JavaScript the checker didn’t run. Open View Page Source and search for application/ld+json. If it’s there, the checker most likely didn’t get the real page.
Do I need to allowlist an outside checker?
Only if it’s being blocked and you want to keep using it. Check your Cloudflare security events or your security plugin’s block list to see which layer stopped it, then allowlist the tool’s published IP addresses or user agent there.
Does AEO Ultimate get blocked by Cloudflare?
Its content and schema checks run inside WordPress, so they don’t go through Cloudflare. Bot View does fetch your live page, so a strict firewall or cache can affect that one feature.
Is an outside checker more accurate than a plugin?
Neither is more accurate across the board. An outside checker shows what the public receives. A plugin shows what your site is meant to publish and why. When they agree, you can trust the result. When they don’t, the difference tells you where to look.
Can AEO Ultimate check sites that aren’t on WordPress?
The full plugin is WordPress only. AEO Ultimate is also available for other platforms; see the docs for what each version covers.