Index of every page on this site: llms.txt
All skills
coreyhaines31 avatar

/seo-audit

@5b2b400
Run it yourself

When the user wants to audit or diagnose SEO, or asks why traffic dropped, a page won't rank, or whether a setup like canonicals, hreflang, or redirects is right: technical SEO, indexing, Google updates, on-page and titles, Core Web Vitals, local SEO. Start here when someone just says their SEO is bad. For pages at scale, see programmatic-seo. For structured data, see schema. For AI search, see ai-seo.

Use this Skill: https://skilld.dev/gh/coreyhaines31/marketingskills/seo-audit

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesrankings-push.md

≈1.2k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Rankings Push

Audits find what's broken. This reference covers the next step: moving pages that already rank onto page one, and shipping new pages so they start strong. Both are cheaper than winning a query from nothing, because Google has already decided the site is relevant.

Find the candidates

From Search Console, pull query + page pairs for the trailing 28 days (compare with the previous period to filter out spikes):

Bucket Filter Fix type
Striking distance Average position 8–20, impressions above a floor that fits the site (often 100+/month) Content and links
Weak click-through Position 1–5, CTR well below other pages at similar positions Title and meta description
Near the top Position 4–7 on a revenue query Content, links, and featured-snippet format

Data caveat: a Search Console logging error misreported impressions from May 13, 2025 until April 27, 2026, which also affected CTR and average position; clicks were not affected. Don't compare impressions, CTR, or position across April 27, 2026: compare clicks, or keep both periods on the same side of that date. (Google's Search Console data anomalies page, April 2026.)

Prioritize by business value: a position-11 query that drives demos beats a position-9 glossary term with three times the impressions.

Before touching a page, check for cannibalization: if two of your pages rank for the same query, positions often bounce between them and neither climbs. Pick one owner, merge the useful parts of the other into it, and redirect.

Diagnose against the top three

Open the three results above you and write down, for each one, the concrete reason it wins. Usually one of these:

  • Intent match. They answer the question the searcher is asking; your page answers a neighboring one. A pricing query answered with a features page loses.
  • A missing section. They cover a sub-question you skip. The People Also Ask box and the subheadings across the top results show what searchers expect.
  • Freshness. Their facts, screenshots, or year are current and yours aren't.
  • Format. They have the table, steps, or tool the query calls for.
  • Links. They're linked from more, and stronger, pages, inside their site and out.

If you can't name a reason, don't guess with a rewrite. The gap is more likely authority than on-page, and the fix is links (the link-building skill, run weekly as the backlink-prospecting loop in marketing-loops) rather than content.

Make the smallest change that closes the gap

  • Answer the query in the first two sentences, then expand. This is also the passage AI Overviews and assistants tend to quote.
  • Add the missing section, not a rewrite of the whole page. Pages that already rank have signals worth keeping.
  • Put the query in the title and H1 if it reads naturally. If the title is already aligned, leave it.
  • Add internal links to the page from your strongest related pages, with anchor text that describes the target. This is often the biggest single lever and the most neglected.
  • Refresh what's stale: facts, screenshots, the year, broken links.
  • For weak click-through only, change the title and meta description and nothing else, so the result is attributable. Patterns in title-tags.md.

Record the starting position, impressions, and CTR, then wait 3–4 weeks before judging or changing the page again. Rankings take time to settle after an edit, and stacked changes make it impossible to know what worked.

If two rounds move nothing, stop editing. The page is probably limited by intent mismatch (Google wants a different kind of page) or authority, and more on-page work won't fix either.

Shipping a new page

A new page should launch with everything it needs to be found, so it doesn't spend months as an orphan:

  • Internal links from at least three relevant existing pages, with descriptive anchors
  • Unique title and meta description matching the target query
  • One H1, aligned with the title
  • Self-referencing canonical
  • Added to the XML sitemap
  • Structured data where the page type supports it (see schema)
  • Main content present in the server-rendered HTML, not only after JavaScript runs
  • Indexable: no stray noindex, not blocked in robots.txt
  • Linked to the right conversion path (see cro)

After it ships, request indexing once in Search Console. Requesting again doesn't speed anything up. If the page isn't indexed after a few weeks, check the causes in the Indexation section of the audit instead of resubmitting.

Run it on a schedule

The striking-distance push loop in marketing-loops runs this weekly with state, cooldowns, and a stop rule. The SEO operator recipe in the same skill combines it with the other SEO loops.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warningtoday5 checks · Risk SAFE
  • Gen Agent Trust Hubtoday

    This skill provides a technical SEO audit framework for diagnosing site performance. It includes specific security instructions to prevent the agent from following malicious commands found on external websites during audits. No malicious code or suspicious behaviors were detected.

  • Sockettoday

    No alerts

  • Snyktoday

    Risk: MEDIUM · 1 issue

  • Runlayer8mo

    2 files scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 5b2b400. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated yesterday
metadata
{
  "version": "2.2.9"
}
  • SEO
  • technical-seo
  • audit
  • on-page
  • crawlability
  • indexation
  • core-web-vitals
  • mobile-friendly
  • schema-markup

README badge

README badge for coreyhaines31/marketingskills/seo-audit

Diagnoses SEO problems on websites by checking crawlability, indexation, speed, mobile-friendliness, on-page elements, and international configurations. The audit walks through technical foundations first, then on-page optimization, and flags common issues like noindex mistakes, canonical conflicts, hreflang errors, and Core Web Vitals problems.

Generated from the current SKILL.md.

Does this skill check for schema markup and structured data?
The skill can identify schema markup issues, but it has a significant limitation: web_fetch and curl cannot reliably detect JSON-LD injected by client-side JavaScript (common in CMS plugins like Yoast or RankMath). For accurate schema detection, use the Google Rich Results Test, browser DevTools, or Screaming Frog instead.
What does this skill prioritize in an audit?
The skill audits in this order: crawlability and indexation, technical foundations (speed, mobile, HTTPS), on-page optimization (titles, headings, content), content quality, and authority/links. It covers robots.txt, XML sitemaps, Core Web Vitals, canonicals, hreflang for multilingual sites, and internal linking.
Does this skill handle international/multilingual sites?
Yes. The skill includes a full international SEO section covering hreflang setup (including self-referencing entries and reciprocal links), canonicalization across locales, locale URL structure, and detection of common errors like cross-locale canonicals or missing x-default entries.
Does this skill require Search Console or analytics access?
Access to Google Search Console and analytics is helpful but not strictly required. The skill can perform initial crawlability and on-page checks without it, but Search Console provides the most accurate indexation and coverage reports.
Does this skill work with any CMS or is it platform-agnostic?
The skill is platform-agnostic and addresses common SEO issues across any site type (SaaS, e-commerce, blog). It notes CMS-specific behaviors (like client-side schema injection in plugins) but does not assume a particular platform.

Generated from the current SKILL.md. These answers refresh after source changes.