FAQ

Does this replace my SEO plugin?

No. The plugin audits what your site actually outputs - whichever SEO plugin, theme or page builder produces it. It does not manage or change your metadata.

Will it change my content or metadata?

No. It is read-only. It renders your pages and reads what they output; it never edits posts, settings or metadata. The only things it stores are its own scan results and your plugin settings.

Does it crawl my site?

No. It audits only your known WordPress content (pages, posts and - on paid plans - custom post types and products). It never follows links or discovers URLs like a crawler. It also reads two of your site's own files once per scan, /robots.txt and /llms.txt, for the AI access panel - your own URLs, on your own server.

Can I see which AI engines are allowed to read my site?

Yes, in every plan. After a scan, the Site checks: robots.txt, AI access, favicon row on the Findings tab carries an AI access badge. It opens a panel listing every AI crawler the major providers document - OpenAI, Anthropic, Perplexity and Google - with whether your robots.txt allows or blocks it, the exact robots.txt lines behind that verdict, and what each provider documents that rule as controlling. The free plugin also warns you if your robots.txt is served with a status that makes its rules ineffective, because that is a plain misconfiguration rather than an AI question. The findings that interpret crawler rules and page directives are paid. See AI readiness.

If I block an AI crawler, does that remove my site from that AI product?

Not something anyone can promise you, and the plugin does not say it does. What it reports is what each provider documents: for example, OpenAI documents that sites opted out of OAI-SearchBot are not shown in ChatGPT search answers, and Anthropic documents its crawlers as honoring robots.txt. That is documented policy, not observed behaviour, and two of the fetchers (OpenAI's ChatGPT-User and Perplexity's Perplexity-User) are documented by their own providers as possibly ignoring robots.txt when a person asked for the page. Rules at your CDN or firewall sit upstream of robots.txt and are invisible to this audit. Any tool offering you an "AI visibility score" is guessing; this one reports what your site serves and what the vendors publish.

Can I exclude pages from the audit in bulk?

Yes. As well as the Exclusions screen inside the plugin, the standard Posts and Pages screens (and any audited custom post type) gain two bulk actions: "Appearance audit: Exclude" and "Appearance audit: Include". Select the rows you want, choose the action, and apply. Because bulk actions work on whatever is currently filtered or selected, you can combine them with any list filter - including filters added by other plugins (for example, filtering to one plugin's generated content and excluding the whole set at once). Both screens stay in sync with the plugin's Exclusions screen. Paid plans can also auto-exclude pages by rule (URL pattern, category or tag, author, post type) - see Excluding content.

How do I see why a page was flagged, and can I ignore an issue?

Click the page's Issues, Warnings or Notices badge, or any row on the Findings tab, to open the issue-details popup. It lists each problem with the exact evidence taken from the rendered page (the actual title, description, canonical, robots directive or image URL that shipped), plus quick actions to view the page, edit it, or re-scan just that page after a fix. From the popup you can also ignore an individual issue - on that one page or sitewide - and it stops counting while staying visible; reverse it any time from the Ignored view. See Reviewing your results for the full walkthrough.

Why is a finding on my noindex page only a notice?

Because a page set to noindex cannot appear in a search result, so a point about how it would look there is describing something that will never be shown. On those pages, findings like meta description length, a missing canonical or a hidden search thumbnail are listed as notices, and each one carries a line explaining why. They are still listed and still counted in the page's finding total - nothing is hidden. They just stop being counted as problems. Findings about the noindex itself, and title findings, keep their full severity. So do social findings: a noindexed page shared in a chat still shows a link preview. See Reviewing your results.

My issue count dropped after an update. Did something get hidden?

No. From version 1.4.0, search findings on pages you have set to noindex are listed as notices rather than issues or warnings, because a noindexed page cannot appear in a search result at all. The findings are all still there and still counted in each page's finding total - they moved out of the Issues and Warnings columns, which is where the drop comes from. Each demoted finding says on itself why it was set aside. A page's stored severities are rewritten when that page is next scanned, so the change appears page by page as your next scan runs rather than all at once.

If the drop is site-wide and dramatic, check the Site checks row for a critical "Whole site hidden from search" finding - see below.

Why does my whole site show a critical "hidden from search" alert?

Because "Discourage search engines from indexing this site" is switched on under Settings > Reading. WordPress then adds a noindex tag to every page, so no page on the site can appear in search results. That is intentional on a staging or holding site, and it is a common leftover when a live site was copied from one. If this site is live, clear the setting under Settings > Reading and re-scan. Social sharing is unaffected either way - link previews still work.

Why does a preview image look cropped?

Search and social platforms crop images to their own fixed shapes. Click any preview image to see it full size with the exact area the platform keeps highlighted and the trimmed edges dimmed - so you can check nothing important is cut off. Facebook and similar use a 1.91:1 crop; Google's mobile thumbnail is square.

Are private or password-protected pages audited?

No. Private and password-protected content is excluded automatically. Search engines and social platforms can never see it - a crawler or a social "share" preview only ever reaches a login screen, a password form, or a "not found" response, never the page itself. Auditing how such pages "appear" in search or social would be meaningless, so they are left out of every scan, count and report. If you later make a page public (or remove its password), it is picked up on the next scan like any other published page.