Skip to content

EP Txt Files

EP Txt Files lets you write your site’s /robots.txt and /llms.txt in the PageMotor admin. Save your text, open the settings page again, then publish it with one click on its status card.

After that, each save updates your site.

Published by ElmsPark Studio.

Tells search engines which parts of your site they may crawl. It must sit at the top of your domain, at exactly /robots.txt.

If PageMotor is installed in a subfolder, such as example.com/blog/, the file ends up at example.com/blog/robots.txt. Search engines ignore it there, so add your rules to example.com/robots.txt yourself.

A newer convention: a short Markdown summary of your site, with links to the pages you most want AI assistants to read. See llmstxt.org for the format.

PageMotor 0.10 and later write their own robots.txt and llms.txt in your site root. Each starts with a line containing BEGIN PageMotor.

PageMotor leaves a file alone if it has that line. If the line is missing, PageMotor adds its own block to the end of the file.

EP Txt Files writes your text into the file between two marker lines of its own. In llms.txt they look like this:

<!-- BEGIN PageMotor — managed by EP Txt Files (do not remove this line) -->
# Your Site
…your text…
<!-- END PageMotor — managed by EP Txt Files -->

In robots.txt the marker lines start with # instead. You never type them: the plugin adds them every time it writes the file.

PageMotor 0.9 and earlier don’t write these files, so the plugin serves your text straight from its settings. See Older PageMotor.

  • PageMotor 0.11.5 or later
  • EP Suite base class (bundled)
  1. Download the latest EP Txt Files zip. The download starts straight away.
  2. In the admin, go to Plugin Settings, then Manage Plugins. Click Upload a New Plugin and drop in the zip.
  3. Tick EP Txt Files in the list and click Save Plugins.
  4. Go to Plugin Settings and click Settings next to EP Txt Files. Two status cards at the top show the state of the robots.txt and llms.txt files on your server.

These steps are for PageMotor 0.10 and later. On 0.9 and earlier, clicking Save Settings is all you need.

Before you start, open your current /robots.txt and /llms.txt and copy any lines you want to keep. Use my custom content replaces the whole file without asking, and nothing on the settings page brings back a file you uploaded.

PageMotor’s robots.txt blocks /admin/, /api/, /mcp/ and /oauth/, and its llms.txt lists your API and MCP addresses. Generate Default leaves out /api/, /mcp/ and /oauth/.

  1. Open the robots.txt or llms.txt section. Type or paste your text into the box and click Save Settings.
  2. Open the settings page again: click Plugins at the top of the page, then Settings next to EP Txt Files. The cards don’t change until you do.
  3. The card says PageMotor default and now has a Use my custom content button. Click it to replace the whole file with your text.
  4. The card says Active (file). Open /llms.txt or /robots.txt on your site and press your browser’s refresh button to check.

After that, edit the text and click Save Settings. The plugin rewrites the file on your site for you.

Save Settings doesn’t update the cards, so open the page again to see what it did. A button on a card updates that card straight away.

CardWhat it meansWhat to do
Active (file)Your text is on your site and matches what you saved.Nothing.
Out of dateThe file is the plugin’s, but it doesn’t match your saved text.Click Update file.
PageMotor defaultPageMotor’s own file is on disk, or a file you uploaded with PageMotor’s block added to the end.If you uploaded the file yourself, copy anything you want to keep first: there’s no way to restore it. Then save your text, open this page again and click Use my custom content.
Existing fileA file the plugin didn’t create is on disk. You’ll mostly see this on PageMotor 0.9.Copy anything you want to keep first: the plugin keeps a copy, but there’s no button to restore it. Then save your text, open this page again and click Overwrite with my content.
Active (dynamic)There’s no file on disk, so the plugin serves your text itself. This is normal on PageMotor 0.9.On 0.10 and later, open this page again.
EmptyNo text is saved and there’s no file on disk.Add text and click Save Settings.
Symlink — refusingThe file is a symbolic link. The plugin won’t write through it.Replace it with a normal file.

Edit the text and click Save Settings. If the plugin already manages the file, it rewrites it straight away.

If the file can’t be written, Save Settings still says “Settings saved!”. Open the page again: an Out of date card means your site didn’t change.

Don’t change the file directly over FTP or in a file manager. The next time you click Save Settings, the plugin rewrites the file from the box, and the direct edit is lost.

If the file has been edited directly, the card says Out of date. Click Update file to put your saved text back.

If the edit removed the marker lines, for example by replacing the whole file, the card says PageMotor default instead. Click Use my custom content.

Generate Default and Generate from Site replace whatever is in the box, without asking. Nothing on your site changes until you click Save Settings.

Clicked one by mistake? Open the settings page again without saving, and your saved text comes back.

Revert to PageMotor default deletes the file the plugin wrote, after asking you to confirm. On PageMotor 0.10 and later, PageMotor puts its own default back on the next page load.

Straight after the click, the card says Active (dynamic) and offers Write physical file. Ignore that button: open the page again and the card says PageMotor default.

If you open the file on your site straight away, you may see your own text once more. Refresh it and PageMotor’s file appears.

Your text stays saved in the box. Click Use my custom content to publish it again.

Revert never deletes a file the plugin didn’t create. Emptying a box and clicking Save Settings also reverts that box’s file, if the plugin wrote it.

Don’t revert robots.txt while Staging Mode is on. PageMotor then writes a robots.txt that blocks all crawlers, and it stays after you switch Staging Mode off.

Deactivating or deleting EP Txt Files doesn’t delete the files it wrote. Because of the marker line, PageMotor leaves them alone, so visitors keep getting your text.

To go back to PageMotor’s own files, click Revert to PageMotor default on each card first. Then deactivate the plugin.

If the plugin is already gone, delete robots.txt and llms.txt from your site root by FTP. On PageMotor 0.10 and later, PageMotor writes fresh ones on the next page load.

A box for your robots.txt. It starts empty.

Generate Default fills it with a starting point for your site:

User-agent: *
Allow: /
Disallow: /admin/
Disallow: /user-content/uploads/
# Sitemap: https://yoursite.com/sitemap.xml

The Sitemap line starts switched off. On PageMotor 0.10 and later your site already has a sitemap at /sitemap.xml, so remove the # and the space after it.

On 0.9 and earlier, remove it only if you have a sitemap, for example from EP Sitemap.

EP Sitemap’s Add Sitemap Line button adds the line to this box, but doesn’t update the file on your site. If the robots.txt card then says Out of date, click Update file.

The settings page also has a Quick Reference with patterns for blocking one bot, or all AI crawlers.

Staging Mode. PageMotor’s Staging Mode doesn’t change a robots.txt that EP Txt Files manages, though PageMotor still marks every page noindex.

To block crawlers while staging, copy your text somewhere safe. Then replace everything in the box with these two lines and click Save Settings:

User-agent: *
Disallow: /

Adding Disallow: / under the generated Allow: / line isn’t enough. Both rules match every page equally, and crawlers then follow Allow.

When you go live, paste your text back and click Save Settings.

A box for your llms.txt, written in Markdown. It starts empty, because a good llms.txt is specific to your site.

Generate from Site builds a first draft from your site title and published pages:

# Your Site
> Your Site website.
## Pages
- [About](https://yoursite.com/about/)
- [Contact](https://yoursite.com/contact/)

The links come without descriptions. Add a short one after each link, for example - [About](https://yoursite.com/about/): Who we are and what we do.

The settings page has a ready-made prompt that adds them for you. Click the prompt to copy it, or select and copy it by hand, then paste it into any AI assistant with your draft.

PageMotor’s own llms.txt lists your API, MCP and sitemap addresses. Copy those lines into your text if you want AI agents to find them.

Your llms.txt is public. Only link pages you are happy for AI assistants to read and repeat.

PageMotor 0.9 and earlier don’t write these files. The plugin serves your text straight from its settings, so changes show as soon as you save.

With no file in your site root and your text saved, the card says Active (dynamic). A file the plugin didn’t create, for example one uploaded by FTP, takes priority, and the card then says Existing file.

On 0.9, a write button may report “Could not write the file: Write failed.” even if the file was written. Open the page again: the card shows what is on disk.

Refresh /llms.txt or /robots.txt in your browser. If it still shows the old text, open the settings page again: the cards don’t change when you click Save Settings.

Check your text is still in the box, then check the card:

  • Out of date: click Update file.
  • PageMotor default: click Use my custom content.
  • A pop-up starting “Could not write the file”: PageMotor isn’t allowed to write that file. Send your host the full message and ask them to make your site root, robots.txt and llms.txt writable.
  • A CDN in front of your site may still be serving the old file. Purge it.

“My file shows odd characters where a dash should be”

Section titled ““My file shows odd characters where a dash should be””

The file on your server is fine. Your server doesn’t tell browsers the file is UTF-8, so the browser guesses the wrong encoding and shows the dash as —.

To fix it, ask your host to serve .txt files as UTF-8. On nginx, that’s the line charset utf-8;.

“PageMotor’s own text appears under mine”

Section titled ““PageMotor’s own text appears under mine””

PageMotor adds its block to the end of robots.txt or llms.txt whenever the file has no BEGIN PageMotor line. That happens if the first marker line was deleted, or the file was replaced by hand.

If you replaced the file by hand, copy anything you want to keep into the box and click Save Settings first. Then open the settings page again and click Update file, or Use my custom content if that’s what the card shows.

“Staging Mode is off, but robots.txt still blocks everything”

Section titled ““Staging Mode is off, but robots.txt still blocks everything””

PageMotor doesn’t replace its own robots.txt when you switch Staging Mode off. The card shows PageMotor default.

Make sure your text is in the box and saved. Then open this page again and click Use my custom content.

“Cloudflare’s rules appear above mine”

Section titled ““Cloudflare’s rules appear above mine””

If Cloudflare is in front of your site, it can add its own rules to the top of your robots.txt. Purging the cache won’t remove them.

Your text is still there underneath. Cloudflare’s bot settings control whether it adds them.

“I broke robots.txt and search engines can’t crawl my site”

Section titled ““I broke robots.txt and search engines can’t crawl my site””

Correct the text in the box and click Save Settings. Or click Revert to PageMotor default to go back to PageMotor’s own robots.txt, unless Staging Mode is on.

Search engines can take up to a day to notice the corrected file.

“I don’t know what to put in llms.txt”

Section titled ““I don’t know what to put in llms.txt””

Click Generate from Site, then add a short description to each link. The spec at llmstxt.org has examples.

For a quick question about this plugin, EP Support inside your admin is the fastest option. The chat widget sits on every EP plugin settings page and knows which one you’re on.

For anything bigger, like a bug report, a feature request, or a “how do I…” that needs a real reply, open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply, usually within a few hours.

  • Settings language menu. The language menu in this plugin’s settings now lists only the languages it is actually translated into, plus English, so you can no longer pick a language that changes nothing.
  • Danish. Adds a Danish translation.
  • Stops a PHP 8 deprecation warning filling your error log. Automated scanners often request addresses that begin with two slashes (for example //something.php). On those requests the plugin passed an empty value into a text function, and PHP logged a warning every time. It now treats the empty value as an empty address. Your pages behave exactly as before.
  • Also brings the shared ElmsPark admin layout up to date: the brand-colour control has moved out of the page header into a Branding section in Settings. Nothing else about your settings changes.
  • Fixes “Your session has expired. Please reload to ensure your security.” on PageMotor 0.11. The message appeared on this plugin’s admin screens even though you were signed in perfectly normally, and whatever you were doing failed to save.
  • Nothing was wrong with your session. PageMotor 0.11 started handling part of the security check that this plugin was already handling itself, and the two together made every save look invalid. The plugin now checks whether PageMotor has already done it.
  • Visitors who were not signed in were never affected, on any version.
  • There is nothing to reconfigure, and nothing else changed.