IntermediateCorey Haines (marketingskills)

SEO Audit

SEO Audit is an ecommerce AI skill for Corey Haines (marketingskills), built for teams working with Codex, Claude Code, OpenClaw. Use it to you are investigating why…

Views
0
Installs
0
Favorites
0
Supported Platforms
Codex · Claude Code · OpenClaw
01

What this Skill does

You are investigating why a product, category, or landing page is missing expected organic traffic. Do not change every step at once: test Diagnosing why organic traffic dropped after a Google algorithm update alongside Running a pre-launch SEO health check on a new marketing… Start with a small test around “Diagnosing why organic traffic dropped after a Google algorithm update”, then check whether “Running a pre-launch SEO health check on a new marketing site” fits the way your team actually works.

02

What makes it different

01

Turns customer feedback into structured output

The source asks the model to group, classify, answer, or prioritize review feedback rather than treating every comment as an isolated case.

02

Creates listing and search-content fields together

The source covers product or listing copy alongside SEO-related fields such as keywords, metadata, or image text when those fields are requested.

03

Structures the analysis before making a recommendation

The source asks for analysis, classification, ranking, or scoring before it reaches a conclusion or next action.

03

Before you use it

Source file or structured data

This instruction refers to file or tabular input. Prepare the requested file and confirm that the model you use can read it.

04

No installation needed

Copy and paste into a model chat
  1. Expand and copy the complete original Skill.md below.
  2. Open a new conversation in a compatible AI model, then paste it into the chat box.
  3. Add verified task details, run one low-risk example, and review the result before using it in store operations.
05

Original Skill.md

The complete source is shown below. Copy it from the top right to use it.

You are an expert in search engine optimization. Audit the site in five priority areas: 1) Crawlability & Indexation — check robots.txt, XML sitemaps, canonicals, noindex tags, redirect chains, and crawl budget for large sites; 2) Technical Foundations — verify HTTPS, mobile-friendliness, Core Web Vitals (LCP <2.5s, INP <200ms, CLS <0.1), URL structure, and site speed; 3) On-Page Optimization — review title tags (50-60 chars), meta descriptions, H1/H2/H3 hierarchy, image alt text, internal linking, and keyword targeting; 4) Content Quality — assess uniqueness, search intent match, E-E-A-T signals, and thin content risks; 5) Authority & Links — evaluate backlink profile and internal link equity distribution. Never report 'no schema found' based on web_fetch alone — use browser tools or Google Rich Results Test for JS-injected JSON-LD. Deliver a prioritized action plan with Critical/High/Medium/Low impact levels and specific remediation instructions.
06

Get started

Starter prompts for the main use cases—copy and use them directly.

01

Start with one real task

Do not begin with a store-wide rollout. Pick one reversible task where SEO Audit can help you create, localize, or check product content and visual assets. Use this when the input boundary, owner, and one primary measure from factual corrections, editing time, approval rate, and conversion quality are written down.

Show prompt and variablesHide prompt and variables
Use the Skill above to help me with this task: Start with one real task.

Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]

Do not begin with a store-wide rollout. Pick one reversible task where SEO Audit can help you create, localize, or check product content and visual assets.

Return a practical result and clearly flag anything that needs human review.

Replace these variables

[TASK_DETAILS]
The facts, context, or source material for this task.
[CONSTRAINTS]
Replace this placeholder with your verified store-specific information.
02

Prepare the input and guardrails

Collect only the verified product facts, source images, brand rules, target channel, and prohibited claims needed for this test. Remove unrelated personal data and state which actions must never run automatically. Use this when every input has a known source, sensitive fields are minimized, and the approver knows what the trial can read or change.

Show prompt and variablesHide prompt and variables
Use the Skill above to help me with this task: Prepare the input and guardrails.

Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]

Collect only the verified product facts, source images, brand rules, target channel, and prohibited claims needed for this test. Remove unrelated personal data and state which actions must never run automatically.

Return a practical result and clearly flag anything that needs human review.

Replace these variables

[TASK_DETAILS]
The facts, context, or source material for this task.
[CONSTRAINTS]
Replace this placeholder with your verified store-specific information.
03

Inspect the source Skill, then run it

Read the source, installation method, and permission notes before adding SEO Audit to a separate test project. Keep commands and Skill text exactly as published. Use this when you have a product-content draft that a responsible operator can inspect, and it stayed inside the approved boundary.

Show prompt and variablesHide prompt and variables
Use the Skill above to help me with this task: Inspect the source Skill, then run it.

Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]

Read the source, installation method, and permission notes before adding SEO Audit to a separate test project. Keep commands and Skill text exactly as published.

Return a practical result and clearly flag anything that needs human review.

Replace these variables

[TASK_DETAILS]
The facts, context, or source material for this task.
[CONSTRAINTS]
Replace this placeholder with your verified store-specific information.
04

Review it against a baseline

Do not judge the result by fluency. Compare it with source data, the current SOP, and the pre-test baseline; record factual errors, omissions, and editing time. Use this when factual corrections, editing time, approval rate, and conversion quality has a pre-test baseline, and errors and exceptions are logged separately.

Show prompt and variablesHide prompt and variables
Use the Skill above to help me with this task: Review it against a baseline.

Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]

Do not judge the result by fluency. Compare it with source data, the current SOP, and the pre-test baseline; record factual errors, omissions, and editing time.

Return a practical result and clearly flag anything that needs human review.

Replace these variables

[TASK_DETAILS]
The facts, context, or source material for this task.
[CONSTRAINTS]
Replace this placeholder with your verified store-specific information.
07

Risks and operating notes

Keep claims tied to verified product facts

When this instruction drafts marketing or product content, review specifications, comparisons, performance claims, and testimonials against approved evidence before publishing.

Treat review patterns as hypotheses to test

The instruction can group and prioritize feedback, but repeated wording is not proof of a product defect or customer-wide preference. Check the underlying sample before changing a product, policy, or campaign.

Community rating results

Task effectiveness
Setup and ease of use
Reliability and guardrails
Documentation clarity
Time to first useful result

No reviews yet.

Leave a review

Rate every dimension, then share your real experience.

Task effectiveness
Setup and ease of use
Reliability and guardrails
Documentation clarity
Time to first useful result
Author / maintainer

Corey Haines

Creator of Marketing Skills, an open-source collection of reusable agent skills for content, SEO, conversion, launch, and growth work.

Risk, permissions, and limitations

Review third-party permission scopes before providing store data. Never paste payment credentials, customer passwords, or unnecessary personal data into a model. Outputs must be checked by the operator responsible for the workflow.

Content checked: