Skip to content
cccskills
FreePublished on GitHub

on-page-seo-audit

Audit a page the way a search engine reads it: what it is about, whether that is obvious, and the three fixes worth doing before anything else.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

On-page SEO audit

Use this when someone asks why a page is not ranking, or before a page goes live.

Read the page as a machine would

Strip the design away and ask what the page is about using only the title, the URL, the H1, the first paragraph and the subheads. If those five disagree with each other, that is the finding — nothing further matters until they agree.

The checks that pay

Work down this list. Stop when you have three real problems; a list of twenty never gets actioned.

  • Title — the phrase near the front, under about 60 characters, and different from the H1. A title that reads like a filename is a fix.
  • H1 — one of them, and it says what the page does for the reader.
  • First paragraph — answers the query, does not warm up to it.
  • Subheads — scannable alone. If the H2s read as a table of contents that makes sense without the body, the page is structured.
  • Internal links — does anything on the site point here, using words that describe the page? An orphan page is a ranking problem disguised as a content problem.
  • Meta description — not a ranking factor; it is the ad. Write it as the reason to click, under about 155 characters.
  • Images — alt text that describes the image, file sizes that do not stall the page.
  • One page per intent — if two pages target the same phrase, they compete. Say which one should win and what happens to the other.

How to report it

Three findings, each with the current state quoted, the fix written out ready to paste, and one line on why it matters. Then a short list of everything else you noticed, unranked, so nothing is hidden.

What not to do

Never guess at traffic, ranking positions or search volume — if the data is not in front of you, say what you would need. Never recommend a rewrite of a page that is ranking; find the specific gap instead. Never report a checklist of passes; the user asked what is wrong.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Write ad variants that each test one idea, within platform limits and supported claims.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

See all skills by Significant-Gravitas

Report a problem with this skill