Description
IndexMesh for WordPress gives you one control layer for the public signals that help crawlers and AI systems discover and interpret your site.
Use it to set crawler policy, build and publish llms.txt, manage business and author entity context, coordinate schema with your SEO plugin, and verify what your site serves publicly.
IndexMesh works with Yoast SEO, Rank Math, AIOSEO, SEOPress, or plain WordPress. It does not replace your SEO plugin and never writes to another provider’s settings.
Explore IndexMesh | View all features | Read the documentation
Start on IndexMesh > Home for setup and anything that needs attention. Use AI Discovery, Robots, and Schema & Entities to make changes; Status to verify live output; and Help for task guides, troubleshooting, and support links.
One workflow across four connected surfaces
Specialist plugins can solve one part of AI discovery. IndexMesh connects the parts that site operators need to review together:
- Configure crawler access,
llms.txt, and entity context. - Preview the exact output before publishing.
- Publish through virtual routes or an explicitly managed file.
- Verify the live routes, schema output, and ownership state.
This is governance and verification, not surveillance. IndexMesh does not track crawler visits, monitor citations, score AI visibility, or send site telemetry to a hosted IndexMesh service.
AI crawler controls
Manage robots.txt through structured controls instead of editing one undifferentiated text box.
- Review presets for WordPress routes, shop pages, sitemaps, search engines, social crawlers, AI crawlers, files, and scrapers.
- Set individual Allow, Block, or Off decisions for supported crawler groups.
- Preview the exact IndexMesh-managed block before saving.
- Add advanced per-crawler rules and advisory Content Signals.
- Protect staging or headless sites only after an administrator confirms the change.
- Use virtual output by default or explicitly adopt a physical
robots.txtfile. If an IndexMesh-owned saved file exists, switching to virtual-only warns that the file stays in place until you remove it. - Keep an IndexMesh-owned physical file synchronized without deleting files that IndexMesh did not create.
Guided llms.txt publishing
Build a curated description of your site instead of publishing only an automatic URL list.
- Work through Site Identity, Core Offerings, Positioning, Key Pages, Authority, and AI Guidance.
- Prefill suitable values from WordPress settings and existing Organization schema.
- Pin important public content and exclude unsuitable items.
- Preview the generated Markdown, byte count, line count, and route state.
- Publish
/llms.txtas a saved file in the site root or serve it from WordPress./.well-known/llms.txtis always served by WordPress; IndexMesh does not create a file there. - Keep the default layout, or opt in to a spec-aligned (llms.txt v2) layout. Import an existing file and see which lines were not placed.
- Optionally point pages to your
llms.txtwith a<link rel="describedby">tag or aLink:response header (both off by default). - Optionally publish an AI Information page with a shortcode. It is a plain description of your business; IndexMesh makes no claim that it affects citations or visibility.
- Settings you have not saved yet are previews. Saving makes them live, including the defaults the form already shows.
- Detect physical files and recognized competing owners before IndexMesh takes control.
- Verify that the live response matches the intended output.
IndexMesh treats llms.txt as a publishing and ownership workflow. It does not claim that an AI provider will use the file or cite the site.
Schema and entity context
Manage business and author context while respecting the schema graph already owned by your SEO plugin.
- Add Organization details (a description found on your site is offered as a suggestion, never written until you save), identifiers, founders, related businesses, offices, service areas, and publishing-principle URLs.
- Add author expertise, credentials, profile links, identifiers, and optional archive metadata through native WordPress user profiles.
- Preview Organization output and review local schema health checks, with a completeness indicator for each profile.
- Enrich supported provider graphs where public filters allow it.
- Publish distinct supplemental nodes only when required and safe.
- Suppress IndexMesh output when ownership is ambiguous, multiple schema providers are active, or the content is not publicly indexable.
See how schema ownership works
SEO plugin coexistence
IndexMesh uses read-only provider detection and public integration points for:
- Yoast SEO
- Rank Math
- AIOSEO
- SEOPress
- plain WordPress
The plugin reports which provider is active, applies a provider-specific schema policy, and avoids writing to provider data. If more than one schema provider is active, IndexMesh suppresses its own schema output instead of guessing which graph to modify.
Live-route and output checks
The Status screen checks the site’s own public routes for:
robots.txt/llms.txt/.well-known/llms.txt- the active sitemap route
- homepage schema
These checks target only the site’s own hostname. A copyable support report helps administrators share versions, provider state, routes, and results without sending the report automatically.
Local-first and free
IndexMesh is a complete, standalone WordPress plugin. It requires no IndexMesh account, subscription, API key, or hosted IndexMesh service.
Settings and business and author context remain in WordPress. The plugin’s real HTTP checks target only public URLs on the same site. IndexMesh does not send plugin data to IndexMesh or to any third party.
What IndexMesh does not promise
IndexMesh helps a site publish clear machine-readable signals and verify its own output. It cannot guarantee rankings, crawler behavior, rich results, answer-engine inclusion, AI citations, or provider attribution.
Learn more
- Plugin overview
- Feature overview
- Documentation
- Compatibility
- WordPress.org plugin page
- WordPress.org support forum
IndexMesh is developed and owned by IndexMesh Pvt. Ltd, an India-incorporated company (CIN U62013KL2026PTC105133), which controls the indexmesh.ai domain.
Screenshots



llms.txt from structured business facts, public summaries, and selected pages.

llms.txt.
robots.txt, llms.txt, sitemaps, and homepage schema.

Installation
- Install and activate IndexMesh from Plugins > Add New, or upload the plugin zip.
- Open the IndexMesh menu in wp-admin.
- Use the optional setup wizard to confirm your business name, crawler access, and whether to publish
llms.txt. - Open Robots to choose crawler controls and preview
/robots.txt. - Open AI Discovery to curate, preview, and publish
llms.txt. - Open Schema & Entities to add business and author context and review Schema Health.
- Open Home > Compatibility to confirm ownership beside your SEO plugin.
- Open Status to verify the live routes and copy a support report if needed.
For detailed setup guidance, read the IndexMesh documentation.
FAQ
-
Does IndexMesh require an external service or account?
-
No. IndexMesh does not require an account, API key, subscription, or hosted IndexMesh service. Its HTTP health checks target public routes on the same WordPress site.
-
Does IndexMesh replace my SEO plugin?
-
No. IndexMesh handles crawler policy,
llms.txt, entity context, ownership decisions, and live verification. It is designed to work beside Yoast SEO, Rank Math, AIOSEO, SEOPress, or plain WordPress. -
Is this only an llms.txt editor?
-
No. The guided
llms.txteditor is one part of the plugin. IndexMesh also manages AI and search crawler policy forrobots.txt, coordinates schema/entity context, checks public routes, and applies provider-aware coexistence rules. -
What happens if another plugin or file already owns llms.txt?
-
IndexMesh checks for a physical root file and recognized competing providers and shows who owns each surface on the Home ownership card. It does not take over a surface it detects as owned by another file or plugin until you decide. If you decide that IndexMesh should take control of a physical file, the import and managed-file workflow requires explicit confirmation and keeps a reviewable backup.
Virtual-route ownership can vary by provider, cache, and hosting setup. Always inspect the live
/llms.txtresponse after changing ownership. -
Will IndexMesh duplicate schema from my SEO plugin?
-
IndexMesh uses a provider-specific policy. It enriches supported graphs through public filters where possible, publishes distinct supplemental nodes only where required, and suppresses itself when ownership is unsafe. It never writes to an SEO provider’s stored data.
-
Does IndexMesh track AI crawler visits or citations?
-
No. IndexMesh contains a local, read-only crawler taxonomy used for controls and diagnostics, but it does not store crawler visits, request logs, IP addresses, citation events, rankings, or attribution data.
-
Does llms.txt guarantee AI citations?
-
No.
llms.txtis a public, machine-readable way to describe and prioritize site resources. Each crawler or AI provider decides whether and how to use it. -
Does IndexMesh make external requests?
-
IndexMesh does not send site data to IndexMesh or to third parties. Its live verification and rendered-schema checks request public URLs on the same site. See the documentation for the exact call sites and scheduled checks.
-
What data does IndexMesh store?
-
Settings are stored in one WordPress option. Schema Health and Trust Review can keep a findings history in a small database table (
indexmesh_findings): open findings are kept until resolved, resolved findings are removed after 90 days, and a setting called “Save findings history” turns it off. Author profile fields and per-post options are stored as user and post meta. Deactivating or uninstalling with the default setting keeps your data. The opt-in “Delete data on uninstall” setting removes IndexMesh options, transients, and custom tables; user and post meta, taxonomy terms, AI Information content, and saved root files remain. IndexMesh does not register a WordPress personal-data exporter or eraser. Findings can include author display names. See the privacy documentation for the full list. -
Does IndexMesh work on multisite?
-
No. IndexMesh does not support WordPress multisite. On a subdirectory network every site shares one robots.txt and one llms.txt in the WordPress root, so a saved physical file would be served to all of them. Keep each site on virtual mode (do not save a real file).
-
Which languages does IndexMesh support?
-
The admin interface is prepared for translation, but only English ships with this release.
-
Where can I get help?
-
Read the IndexMesh documentation, open IndexMesh > Help, or use the WordPress.org support forum for public setup questions and reproducible issues. For private support details, email support@indexmesh.ai. Never post passwords, API keys, nonces, cookies, or private customer data in a public support request.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“IndexMesh – AI Discovery Controls for llms.txt, Crawlers & Schema” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “IndexMesh – AI Discovery Controls for llms.txt, Crawlers & Schema” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
0.3.0
- Improved Home, Status, and Help with shorter, clearer guidance and direct links to the live IndexMesh documentation.
- Fixed Home counting one undecided public-file ownership problem twice.
- Fixed Status naming both
llms.txtandrobots.txtwhen only one file needs an ownership decision, and stopped it from claiming IndexMesh manages a file before the user chooses its publisher. - Added safer support-report sharing guidance and direct access to the WordPress.org support forum.
- Added an opt-in spec-aligned (llms.txt v2) layout for
llms.txt; the default layout is unchanged. - Added a “Not placed from your file” list when importing an existing
llms.txt, and a stricter import that keeps link items in Guidance, Citations and Focus sections out of key pages. - Added optional
<link rel="describedby">andLink:header hints forllms.txt(off by default). - Added a non-blocking notice when AI guidance contains promotional directive phrases.
- Added an AI Information shortcode, tab and draft-page helper.
- Added GoogleOther, Google-CloudVertexBot, bedrockbot, Google-InspectionTool and OAI-AdsBot (reference only) to the crawler list.
- Added a findings history table with a “Save findings history” switch and 90-day retention for resolved findings.
- Added a Yoast SEO schemamap hint, a multisite-not-supported notice, and a warning when virtual-only mode leaves an IndexMesh-owned saved file in place.
- Added a translatable admin interface (English only ships) and
languages/indexmesh.pot. - Changed “Schema Score” to “Completeness”, and the Organization description found on your site is now a suggestion.
- Changed the ownership wording, admin contrast, labels and heading order for accessibility.
- Fixed FAQ detection when a post has several question and answer pairs,
llms.txtimporter mapping, untranslated table row labels, the Gutenberg document panel (nowwp.editor), and REST URLs built from the site’s REST prefix. - Fixed an empty ContactPoint without a telephone, the MCP manifest media type, a cleared Organization field being refilled from site data, and added a warning when a saved value is shortened to its limit.
- Removed the unused entity-store and page-class code, the empty
indexmesh_entities,indexmesh_entity_aliasesandindexmesh_url_classestables (dropped only when empty; database version 4), thedecision_coverage,entity_taxonomy,entity_idandurl_class_hashpayload keys, and theindexmesh_manage_entity_storecapability. - Downgrade note: version 0.2.0 ignores the findings table and its setting and recreates the entity and alias tables; 0.3.0 reruns its migration on the next admin load.
- Tested up to WordPress 7.1 on PHP 8.1 to 8.4.
0.2.0
- Added a new Home dashboard, consolidated Status report, public-route checks, contextual Help, WordPress Site Health integration, and redirect-loop detection.
- Added context-aware provider compatibility, an ownership summary, optional supported-provider suggestions on plain WordPress, multiple-provider warnings, and public-output issue states.
- Added an invited setup wizard, per-user Developer view, and Plugins-screen Settings and Get started links.
- Renamed admin navigation around operator outcomes: AI Discovery, Schema Health, Status, and Help.
- Improved managed
llms.txtstatus, provider-specific sitemap detection, provider-neutral admin copy, and redirects from retired admin URLs.
0.1.0
- Added crawler governance with preset groups, AI crawler policy, per-crawler rules, Site Access Protection, and guarded physical
robots.txtmanagement. - Added guided
llms.txtpublishing, virtual and managed-file delivery, well-known routing, a read-only REST payload, a discovery manifest, caching, and conflict detection. - Added Organization and author entity context, per-post Article context, opt-in FAQ schema, Schema Health, and provider-aware output decisions.
- Added read-only compatibility adapters for Yoast SEO, Rank Math, AIOSEO, SEOPress, and plain WordPress.
0.0.1
- Initial repository setup.
