AEOmatic — AEO, AI SEO, llms.txt & Schema
AEO and AI SEO for WordPress: 21 schema types, a visual JSON-LD editor, llms.txt, and AI crawler control. Reads Elementor, Divi and ACF.
Solid choice
AEOmatic is a solid plugin choice in 2026, with a few things worth checking first. It runs on 10+ sites, is rated 5/5 and was last updated 3 days ago, and scores 73/100 on our health check.
- Actively developed — last update 3 days ago
- Tested with the latest WordPress (7.1)
- Momentum — downloads up 148.3% vs the previous 30 days
- Small user base (10+ active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where AEOmatic stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| aeo | #21 |
| ai search | >100 |
| ai-crawler | #94 |
| JSON-LD | >100 |
| structured data | >100 |
Version adoption
Share of active sites per release.
Rating breakdown
★★★★★★★★★★ 5 from 2 reviews
About AEOmatic
From the official readme · v1.2.5Description
Answer Engine Optimization (AEO) for WordPress. AI search engines cannot cite what they cannot parse. AEOmatic makes your WordPress content machine-readable — then shows you what the crawlers actually got.
It does three jobs:
- Publishes the signals AI systems read. JSON-LD structured data across 21 schema types, an
llms.txtindex at your site root, a/llms-full.txtfull-text endpoint, and per-bot crawl directives inrobots.txt. - Scores how extractable your content is. A site-wide AI readiness score across three categories, plus per-post audits that name the specific thing to fix rather than handing you a number.
- Reports what actually happened. A server-side log of every recognised AI crawler request — which bot, which URL, and the HTTP status your site returned. If you are quietly serving 404s to GPTBot, this is where you find out.
It reads your page builder, not just Gutenberg
Most AI SEO plugins parse post_content and stop. If your pages are built in Elementor or Divi, or your copy lives in ACF fields, that means your schema and your scores are computed against an almost-empty string.
AEOmatic runs one normalising extraction pass that understands Gutenberg, the Classic Editor, Elementor, Divi, Beaver Builder, Bricks, Oxygen and WPBakery, plus ACF text, textarea, wysiwyg, repeater and flexible-content fields. Everything downstream — schema generation, the audit, readiness scoring, llms.txt — reads that single extraction, so a page assembled in a builder is scored on what it actually renders.
This work goes by several names — Answer Engine Optimization (AEO), Generative Engine Optimization (GEO), LLM SEO, AI search optimization. Same underlying job.
Built to sit beside your SEO plugin, not replace it
AEOmatic writes only its own settings and its own post meta. It never touches your titles, meta descriptions, canonicals or XML sitemaps, and it never modifies another plugin’s configuration.
It detects Yoast SEO, Rank Math, All in One SEO, SEOPress and The SEO Framework, can import your organisation details from whichever you run, and flags the case where two plugins would emit the same JSON-LD type on one page — with a one-click fix that adjusts AEOmatic’s output, never theirs.
Scores you can check yourself
AEOmatic measures what is verifiable on your own install: whether AI crawlers can reach your pages, whether those pages carry structured data a machine can parse, and whether your content is shaped so an answer can be lifted out of it. Every check tells you whether it is a direct check or a heuristic, so you can see which is which.
The dashboard is labelled AI Readiness rather than AI Visibility, because that is what it measures — your site’s preparation, not whether an engine has cited you.
Check what AI crawlers actually get
Settings pages tell you what you asked for. AI Access tells you what happens:
- Crawler check — reads the robots.txt your site is really serving (including a physical file that overrides WordPress), then requests your home page and recent pages as OAI-SearchBot, ChatGPT-User, Claude-SearchBot, PerplexityBot, Googlebot, Bingbot, GPTBot, ClaudeBot and more, and compares each answer with a normal browser. A firewall, CDN or security plugin that blocks AI crawlers, a bot challenge page, or a crawler-specific noindex shows up by name.
- What AI sees — ChatGPT, Claude and Perplexity crawlers do not run JavaScript. This shows the text they get for a page and lists the sentences from your editor that only appear after JavaScript runs.
Everything included, no account and no API key
-
AI readiness audit, three levels. Site-wide across three categories (Technical readiness, Content readiness, AI crawler access), per post across five categories (Content, Trust, Authority, Entities, Technical), and a per-post 0–100 content rubric of thirteen weighted checks. Every category states whether it is a direct check or a heuristic.
-
Visual schema editor for 21 types — Article, BlogPosting, NewsArticle, TechArticle, Recipe, Review, Product, SoftwareApplication, Service, LocalBusiness, Event, JobPosting, Course, Dataset, Book, Movie, WebPage, AboutPage, ContactPage, CollectionPage, ProfilePage. Fields Google requires are marked, and every node links by @id to one Organization, WebSite and WebPage. The type is auto-detected from your content and every field is editable in the block-editor sidebar with a live JSON-LD preview.
-
Type-specific property extraction — Recipe posts get ingredients and instructions, JobPosting posts get salary ranges, Event posts get dates and venue, LocalBusiness gets address and opening hours. Not generic Article schema on everything.
-
/llms.txtgenerator — a spec-compliant Markdown index at your site root: site summary, curated key pages from your nav menu, then every published item grouped by post type. -
/llms-full.txtendpoint — the extracted body text of your published content at one URL, so an AI crawler can ingest the site in a single request. Bounded and cached so it cannot become a load problem. -
AI crawler control — per-bot Allow/Disallow toggles in
robots.txtfor 18 AI crawlers: GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot, Perplexity-User, Google-Extended, CCBot, Bytespider, Amazonbot, Applebot-Extended, meta-externalagent, Meta-ExternalFetcher, DeepSeekBot, Cohere-AI, DuckAssistBot. Twenty user agents recognised in the visit log. -
AI crawler log and breakdown — which AI bots requested which URLs, what HTTP status you served them, and when. A 404 or 403 being served to OAI-SearchBot is the kind of thing you want to know. Records bot name, URL, user agent and status only: no IP addresses, no cookies, no visitor data, nothing leaves your server.
-
Page-builder support — content is read from Gutenberg, Classic Editor, Elementor, Divi, Beaver Builder, Bricks, Oxygen and WPBakery, plus ACF text, textarea, wysiwyg, repeater and flexible-content fields. Scoring reflects what your pages actually render.
-
WooCommerce Product schema — price, availability, SKU, brand, ratings and sale dates auto-filled; variable products get AggregateOffer with a min/max range.
-
Answer-first fixes — finds answers buried below filler under a question heading (“What is X?” answered in the fourth sentence) and moves them to the top of the section in one click on block-editor and Classic posts. WordPress keeps a revision, so you can undo it.
-
AI Citation Gaps — seventeen local rules-based checks that name why a page is unlikely to be quoted: orphan pages, no opening answer, thin body, no FAQ block, no question heading, schema type mismatch, missing author signal, missing from llms.txt, low outbound links, low alt coverage, no citation hook, no related links, sibling-topic gaps by category, question headings without a snippet-length answer, steps not in a numbered list, missing meta description, buried answers. Three ship a one-click fix.
-
Entity Scanner — scans content, schema, headings and metadata for Organization, Person, Service, Product, LocalBusiness and FAQ entities, returning a coverage score with per-entity confidence, detected signals, missing signals and recommendations.
-
FAQ block — a native Q&A block producing accessible
<details>/<summary>markup, written for featured snippets.[aeo_faq]/[aeo_qa]shortcodes for the Classic Editor. -
Setup wizard with a real first audit — six skippable steps: welcome, import from your existing SEO plugin, organisation details, AI crawler access, your first readiness audit, verify. The audit step shows your score and the three highest-value fixes with direct links, so you finish onboarding knowing what to do next.
-
SEO plugin conflict detection — detects Yoast SEO, Rank Math, All in One SEO, SEOPress and The SEO Framework, and checks whether each is currently emitting overlapping schema. One click disables only the overlapping types in AEOmatic; your other plugin’s configuration is never modified.
-
AI HTTP discovery headers — optional
X-AI-Crawl,X-AI-Citeable,X-Content-License,X-AI-Content-Type,X-AI-Speakableheaders plus aLink: rel="ai-context"pointer to your llms.txt. These are proposed conventions, not a ratified standard, and no AI vendor has committed to reading them — so they ship as a setting you can switch off. -
Live verification panel — makes HTTP requests to your own site and shows what is actually being served: llms.txt with size and line count, robots.txt with AI bot count, schema blocks on your latest post with a direct Google Rich Results Test link.
-
VideoObject, Speakable, WebSite and WebPage schema, an author-profile panel, a wp-admin dashboard widget, and a bulk re-audit action on post list screens.
AI crawlers recognised
- ChatGPT / ChatGPT Search (OpenAI) — GPTBot, OAI-SearchBot, ChatGPT-User
- Claude / Claude Search (Anthropic) — ClaudeBot, Claude-User, Claude-SearchBot
- Perplexity — PerplexityBot, Perplexity-User
- Google AI Overviews / Gemini — Google-Extended controls Gemini training; AI Overviews retrieval uses Googlebot
- Microsoft Copilot — no dedicated AI user agent; retrieves from the Bing index via Bingbot
- Meta AI — meta-externalagent, Meta-ExternalFetcher
- DeepSeek — DeepSeekBot
- Apple Intelligence — Applebot-Extended
- Cohere — Cohere-AI
- DuckDuckGo AI answers — DuckAssistBot
- Common Crawl — CCBot
Controlling a crawler’s access controls whether it can read you. It does not control whether an engine cites you.
Runs entirely on your own server
Schema and metadata generate server-side and cache in post meta. There are no external API calls on the front end, no account, no API key, no credit limits, and no content sent to a vendor cloud. The verification panel only ever requests URLs on your own site, and only for logged-in administrators. No third-party analytics, no telemetry.
Who it is for
- Publishers and media who want to be quoted by AI as a source
- Businesses and SaaS companies who want their entity data to be unambiguous to AI systems
- Local businesses who want correct LocalBusiness signals
- E-commerce stores on WooCommerce
- SEO professionals and content teams who need an AI layer on top of their existing stack
- Agencies running a repeatable audit across client sites
- WordPress developers — 11 filters, a documented REST namespace, and analyzer interfaces to extend
Privacy Policy
AEOmatic does not collect, store, or transmit any personal data to external servers.
Schema, llms.txt, /llms-full.txt and the AI discovery headers are generated server-side on your own site. The verification panel makes HTTP requests only to your own site, only for logged-in administrators, to confirm public output.
The AI crawler visit log records, in your own database only: the matched bot name, the requested URL, the user-agent string (truncated to 255 characters), the HTTP status your site returned, and a timestamp. It records no IP addresses, no cookies, no referrers and no human-visitor data, and only logs requests whose user agent matches a known AI crawler. Retention is configurable from 7 to 365 days (default 90) with a 500-entry ceiling and a daily purge. Nothing in the log ever leaves your site.
AEOmatic makes no external API calls on the front end and ships with no third-party analytics or telemetry.
Installation
- Install from Plugins → Add New and search for “AEOmatic”, or upload the
aeomaticfolder to/wp-content/plugins/, or use Plugins → Add New → Upload Plugin. - Activate through the Plugins menu. Activation registers the
/llms.txtand/llms-full.txtendpoints and flushes rewrite rules for you. - The setup wizard opens automatically. Six skippable steps, ending with your first readiness audit and top three fixes.
- Visit AEOmatic → Dashboard for your site AI readiness score, category breakdown, top recommendations and AI crawler activity.
- Open any post in the block editor and click the AEOmatic icon in the top-right toolbar for the schema editor, audit breakdown, citation gaps, AI readiness and entity coverage.
Requirements: WordPress 6.4+, PHP 7.4+, and pretty permalinks (any structure other than “Plain”).
You do not normally need to re-save permalinks after installing or updating — the plugin flushes rewrite rules on activation and again automatically when it detects a version change. If /llms.txt returns a 404, confirm Settings → Permalinks is not set to “Plain”, then click Save Changes there once.
Frequently asked questions
Will this get me cited by ChatGPT or ranked in AI search?
No plugin can promise that, and AEOmatic does not. What it does is fix the technical and content signals you control: crawler access, parseable structured data, an llms.txt index, and content shaped so an answer can be extracted. Whether an AI engine then cites you depends on that engine’s own ranking and retrieval, which nobody outside those companies controls. Any plugin promising guaranteed AI citations is guessing.
What is the difference between AI readiness and AI visibility?
AI readiness is how well-prepared your site is — measurable from your own database and settings, which is what AEOmatic scores. AI visibility is whether AI systems actually surface or cite you — measurable only by querying those engines from outside your site, which AEOmatic does not do. The dashboard is labelled “AI Readiness” for that reason.
Why does the crawler check say a crawler is blocked when the crawler log shows it visiting?
The check sends requests from your own server using each crawler’s name. Some firewalls also verify a crawler’s IP address, so they block this test while letting the real crawler in. When the AI crawler log shows successful real visits from that crawler, the check says so and marks it for review instead of blocked.
Does the crawler check contact any AI company?
No. Every request goes to your own site. The test requests are tagged so the AI crawler log does not record them as real visits.
Does the crawler log tell me if a page was cited?
No. It tells you a crawler requested a URL and what status you served. Whether that page was retained, used, or quoted in an AI answer is not visible in crawler traffic, and no AI vendor exposes it there. Treat crawler visits as access evidence, not citation evidence.
Does this conflict with Yoast SEO or Rank Math?
It is designed to run beside them. AEOmatic writes only its own settings and its own post meta and never modifies another plugin’s configuration. Because several SEO plugins also emit Article, Organization and Breadcrumb schema, AEOmatic detects that overlap and offers a one-click fix that disables only the overlapping types in AEOmatic. The detector checks whether the other plugin’s schema module is actually switched on, so it does not nag you about a conflict that is not happening. Until you resolve a real overlap, both plugins emit their types and the site readiness score reports it as a…
Can I import my existing SEO plugin’s settings?
Yes — organisation name, logo and social profiles from Yoast SEO, Rank Math, SEOPress, All in One SEO or The SEO Framework. Import is per-plugin, opt-in, one-directional, and never overwrites a value you have already set in AEOmatic.
What is /llms-full.txt?
A single URL returning the extracted body text of your published content, so an AI crawler can ingest the site in one request instead of following dozens of links. It is capped at 200 items per post type by default and says so in its own output when it truncates; raise or remove the cap with the aeomatic_llms_full_max_items filter.
My llms.txt or /llms-full.txt shows a 404. How do I fix it?
Check that Settings → Permalinks is not set to “Plain” — the endpoints need a rewrite rule, which plain permalinks do not support. Then click Save Changes on that screen once. Also confirm llms.txt is enabled under AEOmatic → Settings.
Does the plugin work with Elementor, Divi, or other page builders?
Content extraction does. AEOmatic reads content from Gutenberg, Classic Editor, Elementor, Divi, Beaver Builder, Bricks, Oxygen and WPBakery, plus ACF fields, so schema and scoring reflect what your pages actually render. It does not add builder-native widgets.
Will this slow down my site?
Schema is generated server-side and cached in post meta. /llms.txt and /llms-full.txt are cached for an hour and flushed when content changes. The crawler log writes only when a recognised AI bot requests a page, and defers its single database write to the end of that request. There are no external requests and no third-party assets on public pages. Admin CSS and JS load only on AEOmatic screens.
What schema types does it support?
Twenty-one page-level types (Article, BlogPosting, NewsArticle, TechArticle, Recipe, Review, Product, SoftwareApplication, Service, LocalBusiness, Event, JobPosting, Course, Dataset, Book, Movie, WebPage, AboutPage, ContactPage, CollectionPage, ProfilePage) plus Organization, WebSite, WebPage, Author/Person, Breadcrumb, VideoObject and Speakable. FAQPage, HowTo and the sitelinks search box are not emitted: Google no longer shows them.
Does it work with WooCommerce?
Yes. Product schema with price, availability, SKU, brand and ratings; variable products get AggregateOffer with a min/max price range.
How do I know the schema is actually working?
Open AEOmatic → What did we do? for the live verification panel. It fetches your own URLs and shows what is being served, with a direct link to Google’s Rich Results Test for your latest post.
Does the plugin send my data anywhere?
No. No external API calls on the front end, no telemetry, no analytics, no account. The only server-side HTTP requests are the verification panel fetching your own site, for administrators only.
Is the audit score reliable?
It is a rubric, and it is honest about which parts are heuristic. The Technical and AI crawler access categories are direct checks — a setting is either on or off. Content readiness is explicitly labelled a heuristic: it uses pattern matching to estimate how answer-shaped your content is. Category scores are combined with an unweighted mean, because no public evidence supports specific relative weights and inventing some would be false precision.
What happens when I uninstall AEOmatic?
Deleting the plugin removes every option, transient, scheduled task and post-meta key it created. Deactivating alone leaves your settings intact so reactivating does not lose your configuration.
Changelog
Fixes the Search Console error "Missing field 'item' (in 'itemListElement')" in breadcrumb schema on author, date and post-type archives. Recommended update.
1.2.5
- Fix: “Missing field ‘item’ (in ‘itemListElement’)” in breadcrumb schema. Every breadcrumb now carries its URL. Author, date and post-type archives link to themselves, and a breadcrumb whose link cannot be found is left out instead of printed without one.
- Fix: breadcrumbs with no name. An untitled post or an empty archive title uses the page title instead, so the schema no longer fails with “Missing field ‘name'”.
1.2.4
- New: AI Access → Crawler check. Requests your pages as each AI and search crawler, using the robots.txt your site actually serves, and compares the result with a normal browser visit. Flags robots.txt blocks, firewall and CDN blocks (403, 429, bot challenges), pages that return “not found” only to crawlers, stripped pages and crawler-specific noindex. Warns when a physical robots.txt file overrides AEOmatic’s crawler settings, and cross-checks results with the AI crawler log.
- New: AI Access → What AI sees. Shows the text a crawler that does not run JavaScript receives, the heading outline, title and description, and which sentences from the editor are missing from the HTML.
- New: answer-first fix. A citation gap finds answers buried below a question heading or question-style title, and a one-click fix moves them to the top of the section on block-editor and Classic posts. A revision is saved. Page-builder pages get the suggestion only.
- New: SoftwareApplication and Dataset schema types.
- New: Organization details in Settings — legal name, address, contact details and registry IDs (D-U-N-S, LEI, NAICS, VAT, tax ID).
- New: live page check. After you save a published post, AEOmatic loads the live page in the background. FAQs printed by your theme, templates or other plugins then count in the audit, citation gaps and entity scan, and duplicate structured data is recorded.
- New: citation gaps for question headings without a short (40–50 word) answer, and for steps not in a numbered list. They replace the FAQ and HowTo schema gaps.
- New: the site readiness score includes the last AI Access crawler check.
- Improved: schema follows Google’s current required fields for every type, and Organization, WebSite, WebPage and each post are linked into one graph.
- Improved: FAQs are recognised from any editor, theme or plugin — Elementor (including nested accordions), ACF, Yoast, Rank Math, Spectra, Kadence and ARIA accordions no longer trigger “No FAQ” warnings.
- Improved: runs on PHP 7.4 and later (was 8.0).
- Fix: /llms.txt and /llms-full.txt no longer redirect to a trailing-slash URL.
- Fix: llms.txt is plain text again — no more “>” or HTML codes for apostrophes, and no empty summary line.
- Fix: cached results no longer break when text contains a quote mark — citation gaps, AI readiness, entity scan, audit and saved schema field edits. Cached citation gaps could show an empty list.
- Fix: the “Set schema type” quick fix always failed.
- Fix: “cssSelector” errors in schema validators — Speakable now points at a paragraph that exists on the page.
- Fix: the AEOmatic sidebar loads on WordPress 6.6 and later.
- Fix: AEOmatic’s own test requests are no longer recorded in the AI crawler log.
- Fix: replaced a deprecated WordPress user query argument.
- Fix: uninstall now also removes AI Access data, live page check data and a leftover citation-gap timestamp.
- Changed: honest wording. Hints no longer claim that FAQ or HowTo schema, meta descriptions, author bios or freshness are proven AI citation factors.
- Removed: FAQPage, HowTo, Q&A page and sitelinks search box schema, and their Settings options — Google no longer shows them. FAQ blocks still display on the page.
1.2.3
- New: edit schema inside page builders — Elementor, Beaver Builder, Bricks, Divi, Oxygen and WPBakery get a floating AEOmatic button that opens the full editor.
- Improved: wider Gutenberg sidebar with all tabs visible, plus an Expand button for a large view.
- Fix: Schema type dropdown keeps your selection — it reverted to the auto-detected type.
- Fix: edited schema fields no longer go blank after saving — including Average rating, Review count, Item reviewed and dates. Values saved by earlier versions reappear.
- Fix: dropdown fields show “— Select —” when unset instead of an option that was never saved.
- Fix: saving the Schema tab keeps unedited fields automatic, so the modified date and WooCommerce price and rating stay up to date.
- Fix: FAQ Q&A pairs, postcodes, SKUs, ISBNs and phone numbers now save correctly — FAQ pairs were stored as “Array” and leading zeros and “+” were dropped.
- Fix: the page now outputs the schema type you chose straight after saving, instead of the default type.
1.2.2
- New: visual editor now uses a tab layout — Schema, Audit, Gaps, Readiness, Entities, Ask AI. Same layout in the Gutenberg sidebar and the Classic Editor metabox.
- New: Classic Editor gets the full visual editor as a metabox below the content area.
- Fix: JSON-LD preview updates in real time — was showing the last-saved state.
- Fix: setup wizard “not allowed to access” error on WordPress 6.5+ / Playground. Now a visible submenu under AEOmatic → Setup wizard.
1.2.1
- Fixed: JSON-LD output is now readable. Schema was emitted as a single unbroken line with every
&written as&, every<as<, every/as/, and every accented or non-Latin character as an escape sequence. It was valid and search engines accepted it, but it looked broken in page source and in validators — and on non-English sites a headline became nothing but escape codes. Output is now pretty-printed with slashes and Unicode intact. Nothing about which schema is generated has changed, only how it is written.
1.2.0
- Fixed: custom post types now stay selected under Settings → Content coverage. Your saved selections were never lost, only displayed wrongly — nothing needs re-saving.
- Fixed: page-builder and ACF pages are no longer scored as empty. Six readiness checks were reading the post body directly and missing Elementor, Divi, Bricks, Oxygen, Beaver Builder and WPBakery content. Expect readiness scores to rise on those sites — that is the correction, not new optimisation.
- Fixed: Elementor headings and widget links are now visible to the analysers.
- Fixed: post types whose slug is not plain lowercase (for example MyCPT) can now be disabled.
- Fixed: the setup wizard no longer promises AI citations, and no longer triggers a PHP deprecation notice.
- Fixed: saving settings no longer leaves the upgrade routine re-running on every admin page load.
- Renamed to “AEOmatic — AEO, AI SEO, llms.txt & Schema”.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best AEOmatic alternatives
All aeo plugins →
FAQ
AEOmatic: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 5, 2026
Is AEOmatic free?
Yes. AEOmatic is free to download and use from the official WordPress.org plugin directory.
Is AEOmatic safe to use in 2026?
AEOmatic is a solid plugin choice in 2026, with a few things worth checking first. It runs on 10+ sites, is rated 5/5 and was last updated 3 days ago, and scores 73/100 on our health check.
How many websites use AEOmatic?
AEOmatic is active on 10+ WordPress websites and has been downloaded 2,320 times since it launched in June 2026. It was downloaded 1,214 times in the last 30 days.
Does AEOmatic work with WordPress 7.1?
Yes. The developer has tested AEOmatic up to WordPress 7.1.2, the latest release. It requires WordPress 6.4 or newer.
What PHP version does AEOmatic need?
AEOmatic requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was AEOmatic last updated?
The latest version, 1.2.5, was released on October 2, 2026 (3 days ago).
Who makes AEOmatic?
AEOmatic is developed and maintained by Tushar Makwana.
What are the best alternatives to AEOmatic?
The most popular alternatives to AEOmatic are GEO Plugin by Squirrly SEO (30K+ installs), Xagio SEO & AEO (10K+ installs) and LovedByAI (1K+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
