Skip to content
Kiragu MainaSystems workspace
Systems onlineSend a brief
All tools

SEO Content Maintenance Kit

Fix an outdated instruction or broken link with a source-backed edit you approve, while keeping a copy you can restore.

Founders and writers with useful articles stored as Markdown, text files with simple formatting.

Visual examples. Plain language. Go at your own pace.

SEO Content Maintenance Kit

Package preview. Illustrations use sample data.

Pages kept currentExample
Your getting-started article

Old link: /start-old

New link: /getting-started

Review before publishing Keep a way back
The challengeOld information and broken links
Illustration only. These are sample screens and values.

Slide 1 / 6

A reader reaches the wrong next step

Imagine an article you wrote last year still brings people to your site. They follow its setup link and land on a missing page.

  • An outdated instruction can get in the way of otherwise useful advice.
  • Changing the article’s date does not repair it.
1 of 6

What this means for your project

Keep the pages you already have useful and up to date. SEO means helping people find your site through search.

An old link meets a new reader.

An article you wrote months ago still brings people to your site. Today, its most useful link goes nowhere. Instead of rewriting the whole page, your AI finds the problem, proposes a small correction, and shows what supports it. You decide what changes.

How would I use this with AI?

A skill is a set of instructions and examples for your AI coding assistant. You bring your idea and your project. The skill gives the assistant a process to follow.

  1. Tell your AI what you want to build and share the package instructions.
  2. Work through the setup together. You may need accounts or tools listed below.
  3. Review the changes and test them before putting them on your live site.

This is a package you use while building, not a finished website or a service that runs it for you.

Not sure where to start? Ask about a project like yours.

Explore the example

Made-up example
  1. Check article
  2. Review edit
  3. Approve version
  4. Apply edit

Starting point

Broken link: /docs/start-old

What changes

Reviewed link: /docs/getting-started

Try approving an edit, then changing the article version. You must approve the new version before the edit can go ahead. You can undo an applied edit.

Follow an imagined correction to an existing article. Sources and changes in the preview are sample data.

See how it works

Step 1 of 6

A reader reaches the wrong next step

Imagine an article you wrote last year still brings people to your site. They follow its setup link and land on a missing page.

Starting situationAn article links to a page that has moved
Where it breaksEditing without review can change facts or text you meant to keep
Made-up example. Try the interactive preview to see what changes.
  • An outdated instruction can get in the way of otherwise useful advice.
  • Changing the article’s date does not repair it.
About this example: Inspect the sample

Step 2 of 6

Fix the sentence that lets them continue

Check the current source, propose a precise correction, and review it beside the original. Keep the useful article and a copy of what changed.

BeforeBroken link: /docs/start-old
AfterReviewed replacement: /docs/getting-started
Made-up example. Try the interactive preview to see what changes.
  • Separate checked facts from suggestions.
  • Leave text marked as protected untouched.
About this example: Inspect the sample

Step 3 of 6

Keep approval attached to the edit you saw

Review the evidence and the proposed change. Apply it only while the page still matches the version you approved.

  1. Check the article
  2. Review the exact edit
  3. Approve this version
  4. Apply or undo the edit
Steps shown in the example.
  • If someone edits the page after approval, review it again.
  • Save the previous version so you can restore it.
About this example: Inspect the sample

Step 4 of 6

Read it as the next visitor would

Compare the sample article with its proposed correction. Can you see what changed, why it changed, and what a person still needs to verify?

What to tryTry approving a version, changing it, then applying the edit
Expected resultThe edit is blocked until you review and approve the changed version
Made-up example. Try the interactive preview to see what changes.
  • The sample sources and figures are invented.
  • The kit updates local files; it never publishes pages.
Try the example
About this example: Inspect the sample

Step 5 of 6

Give your AI a careful maintenance routine

Start with tools that list your content, find broken references, and prepare small edits for review. Practice with the included outdated and protected pages.

SKILL.md
Instructions for checking sources and maintaining existing pages
scripts/
Tools to check, review, apply, and undo edits
examples/
Sample content and a proposed correction
tests/
Checks for changed pages and text that must stay untouched
What the package contains. Check the release details for the exact file list.
  • Checks for page details, such as titles, and links between pages
  • A worksheet for supporting sources
  • Tools to apply an approved edit and restore the earlier version
About this example: Inspect the sample

Step 6 of 6

For a library you want to keep useful

This fits a founder or writer with existing Markdown articles. You bring the sources and judgment; the kit helps keep the correction reviewable.

What you need
  • Existing Markdown content, text files with simple formatting, in a local folder you can edit
  • Node.js 20 or later and a local POSIX filesystem, such as the file setup on macOS or Linux; consult the compatibility record for tested setups
  • Reliable source material for factual changes and a person to review it
  • Version control, such as Git, to track file changes alongside the kit’s saved copies
Limits to knowFixing a page does not guarantee better search rankings
Check what you need and what the product can do before choosing it.
  • A matching quote does not prove a source is trustworthy. A person must check it.
  • The local file connector supports limited Markdown formatting. Other content systems need separate integration tests.
  • No ranking result or large collection of newly generated pages is promised.
About this example: Inspect the sample

What you receive

  • A list of content files, with checks on links and page details such as titles
  • A worksheet for supporting sources and proposed edits you can review
  • Checks that the page has not changed since approval, plus apply and restore tools
  • A sample site with outdated content and text marked to stay unchanged
See the files in the package
SKILL.md
Instructions for checking sources and maintaining existing pages
scripts/
Tools to check, review, apply, and undo edits
examples/
Sample content and a proposed correction
tests/
Checks for changed pages and text that must stay untouched

What you need to get started

  • Existing Markdown content, text files with simple formatting, in a local folder you can edit
  • Node.js 20 or later and a local POSIX filesystem, such as the file setup on macOS or Linux; consult the compatibility record for tested setups
  • Reliable source material for factual changes and a person to review it
  • Version control, such as Git, to track file changes alongside the kit’s saved copies

What you can check here

Package version 1.0.0 / page version 3

  • Inspect the sample

    The interactive preview uses invented data to explain the steps. It does not show customer results or evidence of increased sales.

Will it work with your tools?

Codex and Node.jsExample setup only
Paid package version 1.0.0. Check the package compatibility record for the exact setups tested. Other tools, hosting services, and live provider connections need validation in your own setup.

Before you choose

Read the paid skill terms for permitted use, what your purchase includes, help, and refunds.

  • One purchase licenses one individual or organisation to use and modify this version in unlimited own and client projects, including commercial work. Do not resell the standalone package, sublicense it as a competing package, redistribute it publicly, or share it with unrelated purchasers. Later releases may be sold separately; no lifetime updates are promised.
  • The first connector works with local content files. Connections to other content management systems need separate testing.
  • No search-ranking improvement or large-scale page generation is promised.
How is this different from the pSEO publisher?

This kit checks and updates existing local content files. Chat-to-pSEO Publisher is a separate product for editing and publishing pages through an AI chat connection.

Will it improve search rankings?

No ranking result is promised. The kit helps prepare reviewed content corrections.