Skip to skills
AI Craft Pad
Menu
Home/Skills/Skill Kits/WordPress & SEO Kit
Curated workflows

WordPress & SEO Kit

Audit a WordPress page, prioritize technical fixes and verify the published result with a source-linked plan.

AI CRAFT PAD TASK KIT

Your outcome

A URL-by-URL issue list, a staging change plan and a checked release record.

Best for: Site owners, WordPress developers and editors working on an existing site.

Editorial update: 2026-11-02 · Suggested sequence; components have not been runtime-tested together.

Before you start

  • Use a project, files or media you are authorized to inspect. Start with copies or a staging environment.
  • Check the selected skill source, license, agent support and local dependencies before installing it.
  • Agree on a small acceptance example and preserve the original input before changing anything.

Costs, licenses and data

The runbook has no server-side AI charge. Your agent, WordPress hosting, optional audit services and selected skills have their own terms. WordPress skill license metadata is currently Unknown in this catalog; inspect the source terms before reuse.

Follow the workflow

Begin with one representative page and an inventory of the WordPress theme, plugins and existing SEO controls. Separate a crawl or rendering problem from an editorial improvement. Use the WordPress router to choose the correct implementation path and the SEO reference to inspect page semantics and discovery controls. Propose small fixes with explicit expected behavior. Recheck the actual public URL after the normal release process. The SEO reference is broader than WordPress and does not replace the site’s installed plugin documentation. No ranking improvement or Google indexing is guaranteed.

  1. STEP 1

    Inventory the page and WordPress context

    Record the URL, page purpose, theme or block ownership and the component controlling metadata. Identify whether a change belongs in content, a plugin or theme code. Preserve the current header and routing behavior.

    Review wordpress-router →
  2. STEP 2

    Build an evidence-based issue list

    Inspect title, heading hierarchy, canonical, robots directives, sitemap inclusion and internal links. Distinguish an intentional noindex page from an accidental exclusion. Match structured data to the visible content rather than adding unsupported types.

    Review seo-aeo-best-practices →
  3. STEP 3

    Recheck the user journey

    Exercise the page and its important links on desktop and phone widths. Inspect redirects, long headings, the primary call to action and form errors in an isolated browser session. Avoid changing live records during the first check.

    Review webapp-testing →
  4. STEP 4

    Validate the released URL

    Use the site’s approved backup, release and cache-purge procedure. Fetch the final URL and compare its canonical, robots, source links and visible layout with the acceptance list. Keep search-engine indexing as a separate later observation.

    Review verification-before-completion →

Try a small example

Synthetic planning fixture. The expected result is a target to verify, not a claimed live execution.

Input

Synthetic staging page /services/example/: title="Services"; two H1 elements; canonical points to /old-services/; page is intended to be indexable. One internal link returns 404.

Expected result

A four-item findings table with observed evidence and proposed owners. The release check confirms one descriptive title, one main heading, the intended canonical and a corrected link. Search Console indexing remains a separate measurement.

CHECKED LOCAL EXAMPLE

See the example we checked

Four explicit findings before correction; zero after correction.

  • Generic title, two main headings, incorrect canonical and broken fixture link reproduced.
  • Corrected local HTML clears those four checks.

Check limits: Static HTML with a supplied response map; no live WordPress, plugin configuration, structured-data validator or Google indexing test.

Environment and source evidence

Python 3.13.13 on Windows; standard-library example checker

Checked 2026-11-02. First-party synthetic examples and the stated browser/media checks; not end-to-end execution of the selected external skills.

Fixture source SHA-256: eeb2f88773e99de6a3d86aa64b38141958ff321210fa34f06793ce5b4abbeb8c

ZIP SHA-256: 7112ec98504ee65d35f97d2eed5019aef20473a91d9bf7481d30ef70e4f17dcd

Try it on your computer

  1. Download and extract the example into a new disposable folder. Read README.md and the source files.
  2. With Python 3.10 or newer, run the command below from that folder. It uses the standard library; no API key, agent or package installation is needed for this check.
  3. Open example-output/report.html or report.md and inspect result.json. The form and optional video-render instructions are in README.md.
  4. For your own task, review the selected skills below, install one appropriate component through your agent, then adapt the brief to your project.
python check.py wordpress-seo --source . --output example-output
Download example (.zip)Use the task brief

6.8 KB · Original AI Craft Pad fixtures and code under MIT. The ZIP does not install external skills. Read it before running code. Existing files in example-output may be replaced.

Start with this brief

Copy this starting point into your agent, then supply the agreed project or files. Copying does not install a skill or run an external action.

Download runbook (.md)

Check the deliverable

  • The intended canonical and robots policy are recorded for each sample URL.
  • Titles, main headings and internal links match the real page purpose.
  • Structured data describes visible content and passes a relevant validator.
  • The changed route, redirects and mobile layout work after cache purge.
  • Search-engine indexing and ranking are reported only when actually observed.

Complete the checks below against the actual deliverable and preserve enough evidence for another person to repeat the important steps. Record the environment, source dates and anything that could not be checked. These components were selected from source documentation; this catalog has not executed them together as an integrated system.

Review the selected skills

Open each source review for installation, license, compatibility and safety signals. Select the components relevant to your task; the kit is not an automatic installer.

Development75/100

wordpress router

WordPress/agent-skills

Choose a WordPress development workflow after identifying the repository and intended change.

First-party sourceUnknownEditorial review

Repository star change: +3 over 24.12 hours. 2026-11-02

2,320 repo stars0 text flagsReview ↗
Marketing & SEO84/100

seo aeo best practices

sanity-io/agent-toolkit

A technical SEO reference router for metadata, crawl controls, structured data and answer-oriented content.

First-party sourceMITEditorial review

Repository star change: +0 over 24.12 hours. 2026-11-02

194 repo stars0 text flagsReview ↗
Testing & QA86/100

webapp testing

anthropics/skills

A browser-testing workflow with Playwright-oriented examples and server-lifecycle helpers for checking local web application behavior.

First-party sourceComplete terms in LICENSE.txtEditorial review2 matching source records

Repository star change: +478 over 24.12 hours. 2026-11-02

186,432 repo stars2 text flagsReview ↗
Testing & QA88/100

verification before completion

obra/superpowers

A completion-check workflow that ties a claim such as fixed, passing or deployed to fresh evidence from the relevant system.

Community sourceMITEditorial review

Repository star change: +587 over 24.12 hours. 2026-11-02

310,731 repo stars0 text flagsReview ↗

Continue with useful tools

Reference material

AI Craft Pad authored this runbook. Source software, skills and media retain their own licenses.