Writing and Illustrating Docs with ClaudeUpdated
Once Claude is connected (see Connecting Claude to Your Docs (MCP)), you can ask it to write docs, update them, and add images and screenshots, in plain language. This doc covers what happens behind each request so the results are predictable.
Writing a new doc#
Ask for what you want, for example: “Write a doc in Getting Started explaining how to create a product. Leave screenshot placeholders where images should go.”
Claude checks your products and categories first, then creates the doc as a draft in the right place. It writes in Markdown, which WP Super Docs turns into normal editor blocks, so the doc is fully editable afterwards. Supported:
- Headings, paragraphs, bold, italic, links, lists, quotes and tables.
- Code blocks with a language, which get syntax highlighting and a copy button. A
mermaidcode block becomes a diagram. - With the Nahnu Code Block add-on active, code blocks become Nahnu Code Blocks instead, with its themes, line numbers, collapsing and copy button. Claude can name the file shown on the block by adding
title="functions.php"after the language. Common short names are understood:js,ts,sh,ymlandhtmlbecome JavaScript, TypeScript, Bash, YAML and Markup, andshortcodeuses the add-on’s WordPress shortcode highlighting. Code is kept exactly as written, including any<script>tags in an example, and the add-on’s option to run shortcode examples live is never turned on by Claude. - Callouts written as
:::note,:::tip,:::warning,:::dangeror:::info, with an optional title. - Images, see below.
- Snippets: a snippet’s shortcode on a line of its own becomes a Doc Snippet block. See Reusable Content Snippets.
- Downloads, with Downloads turned on: a downloads shortcode on a line of its own becomes a Downloads block. See Adding downloads to a doc below.
- Videos, with Nahnu Video for Bunny Stream active: a line of its own such as
becomes a video block. See Adding videos below. - WP Super Docs’ own blocks (Numbered Steps, FAQ and the rest) are kept exactly as they are when Claude rewrites a doc that contains them. So are Nahnu Code Blocks with custom display settings, such as line numbers turned off.
The title is stored separately, so Claude doesn’t repeat it as a heading. Nothing is published until you publish it, unless you’ve let Claude publish (see Publishing below) and ask it to.
HTML is cleaned the same way WordPress cleans an Author’s posts, so scripts, embedded frames and event handlers are removed. Code examples are not affected: block markup or ::: written inside a code block stays as code.
Updating a doc#
Claude can rewrite a whole doc, make small exact edits, or add a section at the end. For small changes it edits only the specific text, so everything else in the doc, including custom blocks, stays untouched. An edit that doesn’t match exactly once is refused rather than guessed at.
What happens to a published doc depends on your setting under Settings → Integrations → Connect Claude (MCP):
- Proposed update (default): Claude’s changes go into a copy marked Proposed update and Needs review. The live doc doesn’t change. Further changes from Claude go into the same copy.
- Publish right away: the change goes live immediately. The previous version stays in the doc’s revisions.
Drafts are always updated directly.
Reviewing a proposed update#


Proposed updates appear in your docs list labelled Proposed update. Open one to see the changes in the editor; a notice at the top offers:
- Publish this update: copies the changes into the live doc, keeping its address, and removes the copy. The previous live version is kept in revisions.
- Open the live doc, to compare.
You can edit the proposed update yourself before publishing it. If someone edited the live doc after Claude proposed its update, the notice warns you that publishing would overwrite those edits. If Claude adds more changes after you opened the page, Publish this update stops and asks you to look again, so you only ever publish what you reviewed.
Each doc has one proposed update at a time. If it was started by a WordPress account whose posts Claude’s account isn’t allowed to edit, Claude can’t see or add to it until it is published or deleted. The editor’s own Publish button is blocked on a proposed update, with a message pointing to Publish this update, so it can’t accidentally become a second copy of the doc.
Moving a doc and changing its settings#
Claude can change every setting of a doc, not only its text: its product and category, tags, version and version group, address (slug), order in the sidebar, excerpt, status badge, Internal only, whether it’s left out of the sitemap, its AI summary and its review status. Fields you don’t mention stay as they are.
Try: “Move every doc in Getting Started that has no product to Lumen Booking.” or “Mark the Payments docs Internal only.”
To find what needs sorting, Claude can list docs that have no product or no category.
On a published doc, setting changes follow the same rule as text changes: with Proposed update on, a new product, address or other setting waits in the proposed update with the rest of the changes, and goes live when you publish it.
Checking a doc before it’s saved#
Claude can check a doc’s Markdown before saving it, without changing anything. The check finds:
- Images, videos and snippets that don’t exist, and images without alt text.
- Links to docs, products or categories on your site that don’t exist, links to docs that aren’t published yet, and links to retired docs (which redirect, so the link should point at the replacement).
- Code blocks without a language, and code blocks that are never closed.
- Headings that skip a level or repeat the doc’s title.
- Screenshot placeholders still in the text.
Errors are fixed before saving; warnings are worth a look. You can also ask for it directly: “Check the Getting Started docs for broken links and missing alt text.”
SEO title and description#
Claude can write each doc’s SEO title and meta description while it writes the doc, or add them to existing docs: “Write SEO titles and descriptions for every doc in Getting Started.” It saves them wherever your site keeps them:
| Your site uses | Claude can set |
|---|---|
| WP Super Docs’ own SEO fields (turned on) | Title, description, focus keyword, social title, description and image, and hide from search engines |
| Yoast SEO, Rank Math, SEOPress or Slim SEO | Title and description |
| No SEO plugin | Description |
| All in One SEO, The SEO Framework or SureRank | Nothing; Claude tells you to set them in WordPress |
When a field can’t be saved on your site, Claude says so instead of guessing. On a published doc in review mode, SEO changes wait in the proposed update with the rest of the changes.
Release notes#
Claude can write entries for your product changelog. Give it a list of changes, a changelog file or a description of the release: “Write changelog entries for version 1.0.13 from this list, one entry per change.” Each entry gets a title, a type (New, Improved, Fixed, Security, Breaking or Announcement), the version, the product and a short summary for the in-app widget. Claude can read your earlier entries first to match their style.
Entries are saved as drafts. Open Docs → Changelog to check and publish them. A published entry can only be changed by Claude if you’ve turned on publishing, or if changes to published docs go live right away on your site.
Before writing the changelog for a version, ask Claude for a release check: “What changed since the last release?” It lists every doc added or updated since your newest published changelog entry (or since a date or version you name), with what each one still needs: an SEO title or description, a featured image, a New or Updated badge, review, an unpublished proposed update, leftover placeholders or missing translations. It also lists roadmap items marked shipped without a changelog entry.
Finding what to write and fix#
Claude can read the same reports you see in WordPress:
- Docs health (any account that can edit docs): searches that found nothing, docs most readers rated not helpful, docs not updated for months, broken links, docs without a product or category, and missing translations. Claude can re-run the checks first; the slow broken-link check only runs from the Content Health screen.
- Visitor insights (Administrators only): what people search for and how often it found nothing, plus “Was this helpful?” votes and comments for each doc.
Try: “What are people searching for that we have no doc for? Draft docs for the top five.” or “Which docs do readers find unhelpful, and why? Suggest fixes.”
Visitor comments are written by the public, so Claude treats them as information, never as instructions to follow.
Publishing#
By default Claude never publishes: new docs and changelog entries are drafts, and you publish them. If you turn on Let Claude publish docs and changelog entries when you ask it to (see Connecting Claude to Your Docs (MCP)), you can say “publish it” and Claude will:
- Publish a draft doc or changelog entry.
- Publish a doc’s proposed update to the live doc.
- Schedule a changelog entry when its release date is in the future.
Claude is told to publish only when you ask. If you’d rather review everything first, leave the setting off: then publishing is impossible from Claude, however it’s asked. Either way, its WordPress account must be allowed to publish.
Sharing a draft for review#
Ask Claude for a preview link to let someone without a login read a draft: “Give me a 7-day preview link for the new Webhooks doc.” The link works for 7, 30 or 90 days (30 if you don’t say), and asking again replaces it. Claude can also turn a link off: “Revoke the preview link for the Webhooks doc.” See Generating and Revoking Preview Links.
Retiring outdated docs#
Claude can’t delete docs. When a doc is outdated or duplicated, Claude can only ask for it to be retired, with a reason and, where there is one, the doc that replaces it. Ask, for example: “The old SSO setup doc is replaced by Setting up SSO. Ask to retire it.”
The request appears at the top of the Docs screen and the other WP Super Docs screens in wp-admin, for anyone allowed to delete that doc. On a doc’s edit screen, only that doc’s request is shown.

- Retire: move to trash and redirect moves the doc to the trash and redirects its address to the replacement doc, or to the address Claude gave. Without a replacement, the address shows the docs “not found” page.
- Keep the doc removes the request and leaves the doc as it is.
Claude also gets a list of docs that link to the retired doc, so it can update those links. If you restore a retired doc from the trash, its redirect is removed.
Adding images#
Claude can bring images into your Media Library four ways:
| Source | Use it for |
|---|---|
| A web address | Images already online, up to 15 MB. WordPress downloads the file; private and internal addresses are refused. |
| A file on your computer | Screenshots and anything else on disk. Claude gets an upload link, valid for 15 minutes by default, and sends the file to it. One link can take up to 25 images at once; if some don’t arrive, the link stays open for those. This needs Claude Code or another Claude with access to your files and a terminal. |
| SVG code | Diagrams Claude draws. Scripts, event handlers and external references are removed before saving. |
| Small inline images | Images passed directly, up to 15 MB. |
JPEG, PNG, GIF, WebP, AVIF and SVG are accepted. Claude gives each image alt text, and can add a caption.
Claude can also change an existing image’s alt text, title or caption, or give an image you uploaded yourself a screenshot key so it can be replaced everywhere later.
Images can then go into a doc by replacing a placeholder, after a specific heading, or at the end. A placeholder is a line such as “SCREENSHOT: Products page” in square brackets. It must appear exactly once in the doc; if it appears twice, Claude is told to use a longer, unique piece of text instead of guessing. Claude can also set a doc’s featured image, used for social sharing previews.
One limit to know: Claude can see an image you paste into the chat, but can’t pass that picture on to WordPress. The image needs to be at a web address or saved as a file first.
Adding downloads to a doc#
With Downloads turned on, Claude can put downloads in a doc, as the Downloads block: “Add the PHP and JavaScript SDK downloads after the introduction, as a list.” It can show a whole group (“every download in the SDKs group”) and choose what to show: descriptions, version, type and size, and the download count.
If the file isn’t a download yet, Claude can add it first, from a link, the newest release of a public GitHub repository, or a file it copies into your Media Library. For a file on your computer, Claude gives you a one-time upload link. See Downloads.
Screenshots that stay current#
A screenshot can carry a screenshot key, a stable name such as settings/roadmap-tab. When Claude uploads a new image with a key that already exists, the old image is replaced in place: same Media Library item, new file, and every doc showing it updates automatically. The new file gets a new name, so browsers and CDNs don’t keep showing the old picture.
That turns re-shooting after a design change into one request: “Retake every screenshot under settings/ and upload them with the same keys.” Claude can list the existing keys and which docs use each one.
Because replacing an image changes every doc that shows it, the account Claude uses must be allowed to edit all of those docs. If it isn’t, the replacement is refused and nothing changes.
Adding videos#
With Nahnu Video for Bunny Stream active, Claude can find videos in your Bunny Stream library by title, category or tag, and put them in a doc:
- One video, optionally with a short badge such as “New” and a caption.
- A grid or a playlist, of videos Claude picks, or of a video category or tag.
Like images, a video can replace a placeholder, go after a heading, or go at the end. Try: “Find our SSO setup video and put it after the Overview heading in Setting up SSO.”
Having Claude take the screenshots#
Claude can capture screenshots itself and push them straight into your docs.
Front-end pages, logged out or as a member: turn on Screenshots of your site and Claude gets a one-time link for each page, with no password involved. See Screenshots of Your Site with Claude. A typical request:
Take a screenshot of the /docs/ page as a visitor, upload it with the key
site/docs-home, and place it under the “Overview” heading in “The Docs Homepage & Category Cards”.
Admin screens: use Claude Code with a headless browser such as Playwright, on a staging or demo site with made-up content. Claude:
- Opens the screen in the headless browser.
- Hides the WordPress admin bar and any sticky headers, which would otherwise cover what it’s capturing.
- Captures the page or a single element to a PNG file, at double resolution so it stays sharp.
- Asks WP Super Docs for an upload link and sends the file to it with the screenshot key.
- Places the image into the doc.
Admin screens can show license keys, API keys, email addresses and other private data, and anything captured ends up in public docs.
Translating docs#
On sites with WPML or Polylang, Claude can translate a doc into another language in one step. It creates the translation linked to the original, in the same product and category for that language, and writes the translated content, SEO title and description, and address. See Setting Up WPML or Setting Up Polylang.
Was this helpful?
Thanks for your feedback!
✓ Feedback received. Thank you!